On Saturday 14 July 2007 18:46, Steinar H. Gunderson wrote: > I'm a bit unsure why this suddenly started going to debian-devel; I'm > Cc-ing the bug again, at least. Because I CCed it there, but you only replied to d-devel :-) > The question here is: When initscripts is broken, and a new version of > nfs-common exposes that breakage, what is the right course of action? > I'd say it is to fix initscripts. Note that this is not a simple code > change in nfs-utils; it is a major move of functionality from one code > base (util-linux) to a different one (nfs-utils). The right cause of action should at least include preventing the breakage from migrating to testing! After all, testing is supposed to be a usable distribution. Suddenly losing all you NFS mounts on reboots after a routine package upgrade is IMO a serious regression. Which means that ATM an RC bug against nfs-common should be present as nothing else will prevent its migration. (Possibly blocked by the bugs against initscripts.) > Try this patch: The patch works for me. Thanks.
Description: PGP signature