On Mon, 11 Sep 2006, Petter Reinholdtsen wrote: > > Sysvinit's changelog implies that the recovery script is shipped by > > that package, not by sysv-rc. > > Ah, not I see what you mean. the sysvinit changelog applies to the > sysvinit source package, which produces three binary packages, > sysvinit, sysv-rc and initscripts. It does not apply only to the > sysvinit binary package.
Correct. This one of these things one must be quite well aware of when running unstable. > Right. Perhaps we should thighten the dependency. Will need to think > about that one. No, sysvinit works with both sysv-rc and file-rc initscript subsystems, and that should not be broken. And if sysvinit does not need a newer sysv-rc, the deps should not be tightened either. > > That's not sufficient to force onto the system a version of sysv-rc > > that will contain the fix. If sysvinit caused the problem, then it > > should be the solution as well. > > Well, it was the sysv-rc binary package that caused the problem, and > because of that I put the fix into it as well. The NEWS file was I'd be better to have the fix *only* in sysv-rc, then. That includes NEWS files for it. The only thing that should be shared is the changelog. > new one, so I added an entry to that existing file. Perhaps that was > a mistake? I am quite new to handling NEWS files. It's easy enough to fix. Just add a NEWS file for sysv-rc with the proper info, and remove what you placed there from the other NEWS files. Unlike changelogs, NEWS files can and should be fixed retroatively when this improves the situation (just be aware that older NEWS entries are not redisplayed just because they were modified). -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
