Hi, On 14.07.2013 09:47, Helmut Grohne wrote: > As far as I can tell the only way to fix this issue is to introduce a > transitional apache2.2-common package containing no files. apache2 would > need to depend on apache2.2-common for one release (skipping a release > is not supported).
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. -- with kind regards, Arno Töll IRC: daemonkeeper on Freenode/OFTC GnuPG Key-ID: 0x9D80F36D -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
