Please backport rkhunter 1.4.0-2 (universe) from raring
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Precise Backports |
Won't Fix
|
Undecided
|
Unassigned | ||
Quantal Backports |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Please backport rkhunter 1.4.0-2 (universe) from raring to precise, quantal.
Reason for the backport:
=======
The rkhunter version 1.3.8 which is included in precise can't be configured
in a way to support the symlink /dev/.initramfs pointing to /run/initramfs,
it always causes annoying false positive warnings,
see https:/
Especially for precise backporting the 1.4.0-2 version seems to be a good idea, as
precise is an LTS release and thus likely used on servers for a longer time period.
Testing:
========
Mark off items in the checklist [X] as you test them, but please leave the checklist so that backporters can quickly evaluate the state of testing.
You can test-build the backport in your PPA with backportpackage:
$ backportpackage -u ppa:<lp username>/<ppa name> -s raring -d precise rkhunter
$ backportpackage -u ppa:<lp username>/<ppa name> -s raring -d quantal rkhunter
* precise:
[X] Package builds without modification
[X] rkhunter installs cleanly and runs
* quantal:
[X] Package builds without modification
[X] rkhunter installs cleanly and runs
Reverse dependencies:
=======
The following reverse-
rkhunter
--------
* unhide.rb
[ ] precise (Reverse-Suggests)
[ ] quantal (Reverse-Suggests)
* unhide
[ ] precise (Reverse-Suggests)
[ ] quantal (Reverse-Suggests)
Changed in precise-backports: | |
status: | New → Confirmed |
Changed in quantal-backports: | |
status: | New → Confirmed |
Changed in precise-backports: | |
status: | Incomplete → Won't Fix |
The bug you mentioned seems to have a minimal patch attached that fixes the problem.
This is much better suited as a stable release update instead of a backport: /wiki.ubuntu. com/StableRelea seUpdates
https:/