On Fri, Jun 13, 2008 at 02:05:48AM +0200, Witold Baryluk wrote: > Package: fam > Version: 2.7.0-13.3 > Severity: important > > > # ps aux | grep famd | grep -v grep > 4189 ? Ss 0:00 /usr/sbin/famd -T 0 > > # LC_ALL=C dpkg --configure fam > Setting up fam (2.7.0-13.3) ... > * Starting file alteration monitor FAM > invoke-rc.d: initscript fam, action "start" failed. > dpkg: error processing fam (--configure): > subprocess post-installation script returned error exit status 1 > Errors were encountered while processing: > fam > # ps aux | grep famd | grep -v grep > (empty) > # /etc/init.d/fam start > * Starting file alteration monitor FAM > # echo $? > 1 > # ps aux | grep famd | grep -v grep > 4189 ? Ss 0:00 /usr/sbin/famd -T 0 > # > > # /etc/init.d/fam stop > * Stopping file alteration monitor FAM [ OK ] > # ps ax | grep famd | grep -v grep > # LC_ALL=C dpkg --configure fam > Setting up fam (2.7.0-13.3) ... > * Starting file alteration monitor FAM [ OK ] > # > > > Mayby change /var/lib/dpkg/info/fam.postinst line 7 and 9 to call > "restart" not "start" ?
Nope, this does not seem the proper fix. It looks in some cases when upgrading fam it is not stopped and you run into this problem, so you have to finish the installation by hand (stopping fam and running dpkg --configure), no idea where is the issue exactly but i have met another user with the same problem after upgrading to 2.7.0-13.3 too, so it might be worth it check the lastest NMU. And http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=377039 seems to be a similar issue. Could be this considered as seriuos? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
