Bug#716880: Solutions for the Apache upgrade hell
At Sun, 13 Jul 2014 13:17:24 +0200,
Arno Töll wrote:
> What would you do in our situation? Side note 2: We kinda expected this
> situation and added a trapdoor in Wheezy [1], but it turned out, that
> even that is not good enough to prevent havoc with --purge-unused.
It's not really ideal either, but another option would be doing an
update in the next wheezy point release preparing this migration. For
example moving the configuration files from apache2.2-common to
apache2 or apache2.2-bin in wheezy shouldn't cause any problem and
after the files have been moved apache2.2-common can be safely purged
during upgrade.
Moving them to apache2 package would mean you won't have to move them
again in the upgrade to apache 2.4, but it would create a new and
circular dependency of apache2.2-common on apache2. Given that
apache2.2-common already depends on apache2.2-bin and there exists a
transitional package in jessie it might be a better candidate. Then
you would have to move it again in the jessie package, but I'm afraid
there aren't any easy solutions.
Kind regards,
Jeroen Dekkers
Reply to: