On Sat, 14 Jul 2007 the mental interface of Steinar H. Gunderson told: > On Sat, Jul 14, 2007 at 06:17:13PM +0200, Frans Pop wrote: > > I'm not all that interested in what the right long-term fix is, I'm > > concerned about a change in nfs-common breaking something semi essential > > that has worked for ages, accidentally or not. > > I'm a bit unsure why this suddenly started going to debian-devel; I'm Cc-ing > the bug again, at least. > > > If something like that is reported, IMHO the only correct course of action > > is first to make sure that the breakage is fixed, and then to start > > talking with maintainers of other involved packages about the correct > > structural fix and migration path, and only implementing your own change > > again _after_ other packages have made the necessary modifications. > > 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). > > Try this patch:
Doesn't work in addition to nfs-common 1.1.0-9. Elimar -- Excellent day for drinking heavily. Spike the office water cooler;-) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
