tag 493095 + wontfix -- On Thu, Jul 31, 2008 at 02:50:53PM +0400, Alexandra N. Kossovsky wrote: > Well, I do have NFS mounts, and it is great to avoid breaking them, but > as far as I can see, aptitude has no hints like "upgrade nfs-common > before mount".
Exactly. Post lenny, we get 'Breaks:' which would do the right thing, and isn't usable in lenny. > I think that mount should "Conflicts: nfs-common < 1:1.0.9" or something > like it. If such approach is not possible, please, put some words about > this issue in release notes (sorry, I've failed to find Lenny release > notes -- may be, such information is already here). The conflicts option you have would result in the removal of nfs-common, which would (1) not fix the problem and (2) remove things you might otherwise want. As far as I know, the release notes for Lenny will include a "install nfs-utils prior to upgrading mount" note. > This bug is very user-unfriendly, because broken "aptitude dist-upgrade" > is a hard thing to resolve for an ordinary user... The ordinary user is not using NFS. Given all of the options (the last one being to force-install portmap and nfs on every machine in the Debian universe - not a viable option unless I want to turn in my security badge), the conclusion of several developers, the security team, and the release team, was that the best option was to assert that users of NFS were clever enough to fix the issue themselves, or had someone who was that was managing their upgrades. So, in short: yeah, it's a bug, it sucks, and the bug of aborting in the preinst and thereby assuring a working system that a competent admin can fix, is the best solution available to the problem at hand. lamont -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
