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? -- Rob Browning rlb @defaultvalue.org and @debian.org GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
