Bug#435223: Also breaks policy
On Mon, Jul 30, 2007 at 05:48:32PM +0200, Moritz Muehlenhoff wrote: > That's fairly fragile. IMO nfs-common should split off a separate nfs-mount > binary package, on which util-linux will depend. (The priority of nfs-mount > would need to be dumped to required, of course) And that nfs-mount package would Depend: portmap, which gets us right back where we were. lamont -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#435223: Also breaks policy
On Mon, Jul 30, 2007 at 07:53:03AM -0600, LaMont Jones wrote: > On Mon, Jul 30, 2007 at 04:15:26PM +0300, Black Dew wrote: > > This also breaks debian policy "Packages must not depend on packages > > with lower priority values" as nfs-common is Priority: standard. > > Which is to say that if mount truly requires nfs-common, then nfs-common > would be required, not standard. > > Nonetheless, the current thinking is to Recommend nfs-common (which > would break partial upgrades, so this would be a release-critical defect), > and have mount's preinst abort the upgrade if /usr/sbin/mount.nfs isn't > present on the system (a current nfs-common is at least unpacked), so > that the admin of an nfs-mount using machine can fix the issue. That's fairly fragile. IMO nfs-common should split off a separate nfs-mount binary package, on which util-linux will depend. (The priority of nfs-mount would need to be dumped to required, of course) Cheers, Moritz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#435223: Also breaks policy
On Mon, Jul 30, 2007 at 04:15:26PM +0300, Black Dew wrote: > This also breaks debian policy "Packages must not depend on packages > with lower priority values" as nfs-common is Priority: standard. Which is to say that if mount truly requires nfs-common, then nfs-common would be required, not standard. Nonetheless, the current thinking is to Recommend nfs-common (which would break partial upgrades, so this would be a release-critical defect), and have mount's preinst abort the upgrade if /usr/sbin/mount.nfs isn't present on the system (a current nfs-common is at least unpacked), so that the admin of an nfs-mount using machine can fix the issue. lamont -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#435223: Also breaks policy
This also breaks debian policy "Packages must not depend on packages with lower priority values" as nfs-common is Priority: standard. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
