On Sun, Jul 14, 2013 at 11:50:55AM +0200, Arno Töll wrote: > we cannot do this as long as the transition is ongoing. Sadly lots of > packages reverse-depends on on apache2.2-common. Satisfying this > dependency would create (even more) havoc on such systems as apt would > not force a removal of packages depending ob not provided ABIs.
I do not see how the transition is affecting this option. If it breaks during the transition, it can also break a partial upgrade. Introducing apache2.2-common later can cause a broken wheezy->jessie upgrade when a user fails to upgrade the corresponding apache module. Is this correct or am I missing something? So as far as I can tell the only way to reintroduce apache2.2-common would be to add a huge pile for Breaks. I am not claiming that this is feasible. Long breaks headers tend to confuse apt/aptitude during large upgrades and might make things worse. Updating release notes to tell people not to purge apache2.2-common might simply be the best option. Helmut -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org