On Tue, Nov 27, 2012 at 06:36:06PM -0600, Rob Browning wrote: > Andreas Beckmann <deb...@abeckmann.de> writes: > > > I'm currently doing piuparts upgrade tests lenny -> squeeze -> wheezy to > > check whether long grown systems may successfully update to wheezy. > > Several emacs addons (or however you may call them, I'm not an emacs > > user) fail to install if the old emacs22 package from lenny is still > > installed. This seems to cause no harm in squeeze, but is no longer > > compatible with the updated addons to be installed in wheezy. There is > > currently nothing conflicting with emacs22 in squeeze or wheezy, so apt > > keeps the old packages installed. > > > > I would suggest to add a > > Breaks: emacs22 > > or > > Conflicts: emacs22 > > to some central emacs package in wheezy. That should be easier than to > > identify all addons that may break (or might break only in some > > arbitrary combination with other addons). > > I suppose we could do that -- just put the conflicts in emacsen-common, > but I'm wondering why these packages break in the first place. If the > add-ons are no longer compatible with emacs22, then perhaps they > (assuming they're current packages) shouldn't be setting themselves up > for emacs22. > > An add-on knows which package it's being installed for, and it could > (and perhaps should) just ignore the emacs22 flavor.
> Thoughts? Hi, Rob, I agree with you that are the add-ons packages who should make sure that they do not try byte-compiling for unsupported flavours. Users can have old emacs versions installed for some legitimate reasons (Some Emacs developers do, see e.g. http://bugs.debian.org/610574) and adding a Conflict/Break with emacs22 in a centralized package would break that. Since this add-ons misbehaviour cause upgrade failures I'd go with RC bugs against them. Regards, -- Agustin -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
