Bug#716880: apache2 upgrade failed
On Sun, Jul 14, 2013 at 02:39:41PM +0200, Arno Töll wrote:
> > * The only way to ship a package named apache2.2-common is to add a
> > Breaks header listing every single reverse dependency with correct
> > version information.
>
> That would be 100+ Breaks. I do not think that is feasible but that may
> need a wider discussion.
How did you reach that conclusion? I looked at the current testing
distribution, and the only direct dependency on apache2.2-common is
libapache2-svn, which may go away when subversion is able to
transition to testing.
Or are you saying that a Breaks would be needed on every depending
package in stable? That is a larger number (66 in main), consisting
only of libapache2-* modules. It seems a bit of a hassle to have to
list almost all of these as Breaks (7 have precisely versioned Depends
so won't need it), but it's a one-off hassle; one could simply take
the current versions of these packages in testing (where they exist)
or specify that they break all versions (where they have been removed
from unstable/testing). The hard cases are the five packages which
have still not been fixed to deal with apache2.4 but are still in
unstable.
A list of all of these is below.
Also, it is important to realise that without a dependency from
apache2.4 on apache2.2-common, apache2.2-common could be purged by
apt(itude) before the first apache2.4 package is even unpacked:
looking at my dpkg log, this is exactly what happened. So the
mechanism in apache2.2-common.postrm of checking for
/etc/apache2/upgrade-to-2.4-in-progress doesn't provide any benefit in
this case :-(
So it seems like having a dependency on a dummy apache2.2-common would
be the sensible (if annoying) thing to do.
Anyhow, here's that list of packages which apache2.2-common
could/should Break:
apache2-suexec (<< 2.4.6-2)
apache2-suexec-custom (<< 2.4.6-2)
libapache2-mod-apparmor (<< 2.8.0-1+b1)
libapache2-mod-apreq2 (<< 2.13-2.1)
libapache2-mod-auth-cas (<< 1.0.9.1-4)
libapache2-mod-auth-kerb (<< 5.4-2.1)
libapache2-mod-auth-memcookie (<< 1.0.2-8)
libapache2-mod-auth-ntlm-winbind (<< 0.0.0.lorikeet+svn+801-4)
libapache2-mod-auth-openid (<< 0.7-1)
libapache2-mod-auth-plain (<< 2.0.52)
libapache2-mod-auth-pubtkt (<< 0.8-3)
libapache2-mod-auth-radius (<< 1.5.8-1.2)
libapache2-mod-auth-tkt (<< 2.1.0-8)
libapache2-mod-authnz-external (<< 3.3.1-0.1)
libapache2-mod-authz-unixgroup (<< 1.1.0-0.1)
libapache2-mod-bw (<< 0.92-9)
libapache2-mod-dacs (<< 1.4.28b-3)
libapache2-mod-defensible (<< 1.4-3.1)
libapache2-mod-encoding (<< 20040616-5.2)
libapache2-mod-evasive (<< 1.10.1-2)
libapache2-mod-fcgid (<< 1:2.3.7-0.1)
libapache2-mod-geoip (<< 1.2.8-2)
libapache2-mod-jk (<< 1:1.2.37-2)
libapache2-mod-ldap-userdir (<< 1.1.19-2.1)
libapache2-mod-lisp (<< 1.3.1-1.3)
libapache2-mod-macro (<< 1:2.4.6-2)
libapache2-mod-mono (<< 2.11+git20130708.6b73e85-2)
libapache2-mod-nss (<< 1.0.8-3)
libapache2-mod-ocamlnet (<< 3.5.1-2)
libapache2-mod-parser3 (<< 3.4.2-7)
libapache2-mod-perl2 (<< 2.0.8+httpd24-r1449661-5)
libapache2-mod-php5 (<< 5.5.1+dfsg-1)
libapache2-mod-php5filter (<< 5.5.1+dfsg-1)
libapache2-mod-proxy-html (<< 1:2.4.6-2)
libapache2-mod-python (<< 3.3.1-11)
libapache2-mod-qos (<< 10.16-1)
libapache2-mod-removeip (<< 1.0b-5.1)
libapache2-mod-scgi (<< 1.13-1.1)
libapache2-mod-spamhaus (<< 0.7-1.1)
libapache2-mod-suphp (<< 0.7.1-3.1)
libapache2-mod-upload-progress (<< 0.2-2)
libapache2-mod-vhost-ldap (<< 2.4.0-1)
libapache2-mod-wsgi (<< 3.4-3+b1)
libapache2-mod-wsgi-py3 (<< 3.4-3+b1)
libapache2-mod-xsendfile (<< 0.12-2)
libapache2-modsecurity (<< 2.7.4-1)
libapache2-webauth (<< 4.5.3-5)
libapache2-webkdc (<< 4.5.3-5)
The following have been removed from unstable, so we can Break all
versions:
libapache2-mod-auth-pam
libapache2-mod-auth-sys-group
libapache2-mod-layout
libapache2-mod-random
libapache2-mod-speedycgi
libapache2-mod-vhost-hash-alias
Packages still in unstable but not yet ready for apache 2.4:
The version for libapache-svn is assuming that no future version will
reintroduce the dependency on apache2.2-common;
the version for libapache2-mod-ruby assumes that the bugs will
actually be fixed and that it won't be dropped from Debian completely;
the versions for the others are for the version beyond the one
currently in unstable, assuming that the next version will close the
bug (though that may be overly hopeful).
libapache2-mod-musicindex (<< 1.3.7-3)
libapache2-svn (<< 1.7.9-1+nmu3)
libapache2-mod-auth-pgsql (<< 2.0.3-6)
libapache2-mod-auth-mysql (<< 4.3.9-13.2)
libapache2-mod-ruby (<< 1.2.6-3)
Julian
Reply to: