Arch teams, please test and mark stable: =net-firewall/psad-2.2.3 Targeted stable KEYWORDS : alpha amd64 ppc x86
x86 stable
amd64 stable. Shouldn't this package RDEPEND on sys-apps/iproute2? When I try to start the service I get: Starting init script * Starting psad ... [*] Could not find ip, edit /etc/psad/psad.conf at /usr/sbin/psad line 10697. * start-stop-daemon: failed to start `/usr/sbin/psad' * Failed to start psad * ERROR: psad failed to start Emerging iproute2 fixes the problem.
(In reply to Chema Alonso from comment #2) > amd64 stable. Why is it stable when: > Shouldn't this package RDEPEND on sys-apps/iproute2? No. > When I try to start the service I get: > > Starting init script > * Starting psad ... > [*] Could not find ip, edit /etc/psad/psad.conf at /usr/sbin/psad line 10697. > * start-stop-daemon: failed to start `/usr/sbin/psad' > * Failed to start psad > * ERROR: psad failed to start > > Emerging iproute2 fixes the problem. Or editing /etc/psad/psad.conf like it tells you to. It even defaults to: ### What type of interface configuration do you use? Set this variable to ### "iproute2" if you want to use the iproute2 type configuration. ### iproute2 does not use aliases for multi-homed interfaces and ### ifconfig does not show secondary addresses for multi-homed interfaces. #IFCFGTYPE iproute2; IFCFGTYPE ifconfig;
(In reply to Jeroen Roovers from comment #3) > Or editing /etc/psad/psad.conf like it tells you to. It even defaults to: > Ok, good to know. Thanks.
Stable on alpha.
*** Bug 527930 has been marked as a duplicate of this bug. ***
ppc stable. Please drop old.
(In reply to Mikle Kolyada from comment #7) > Please drop old. Done.