severity 446631 serious tags 446631 +patch severity 451344 serious tags 451344 +patch severity 465345 serious tags 465345 +patch forcemerge 446631 451344 forcemerge 446631 465345
thanks Hi, fam does not install in a buildd chroot due to this error, thus bumping its severity. Fixing the egrep call is sufficient (a depends on openbsd-inetd would theoretically fix it too). The missing pid handling by the init script which Petter raised is another issue (which is usually circumvented by creating policy-rc.d) and thus not a serious problem when fam is pulled-in in a chroot, but an important one. Without reaction from the maintainer, I intend to NMU fam next week, the diff is attached. Regards, Daniel
diff -Naurp OLD/fam-2.7.0/debian/changelog NEW/fam-2.7.0/debian/changelog --- OLD/fam-2.7.0/debian/changelog 2008-06-08 05:43:37.000000000 +0000 +++ NEW/fam-2.7.0/debian/changelog 2008-06-08 05:43:25.000000000 +0000 @@ -1,3 +1,11 @@ +fam (2.7.0-13.3) unstable; urgency=low + + * Non-maintainer upload. + * Fix grep call in init.d script to not fail if /etc/inetd.conf isn't + present (Closes: #446631, #451344, #465345). + + -- Daniel Baumann <[EMAIL PROTECTED]> Sun, 8 Jun 2008 07:43:00 +0200 + fam (2.7.0-13.2) unstable; urgency=low * Non-maintainer upload. diff -Naurp OLD/fam-2.7.0/debian/fam.init NEW/fam-2.7.0/debian/fam.init --- OLD/fam-2.7.0/debian/fam.init 2008-06-08 05:43:37.000000000 +0000 +++ NEW/fam-2.7.0/debian/fam.init 2008-06-08 05:44:00.000000000 +0000 @@ -19,7 +19,7 @@ FAMOPTS="-T 0" test -x $DAEMON || exit 0 # Stop if we are running from inetd -egrep -q "^(sgi_fam|391002)" /etc/inetd.conf && exit 0 +egrep -qs "^(sgi_fam|391002)" /etc/inetd.conf . /lib/lsb/init-functions
