Comment 1 for bug 1770242

Revision history for this message
Andreas Hasenack (ahasenack) wrote :

I'm dropping this because of a complicated chain of dependencies in the archive. It's even hard to explain, but let's try, so that others who stumble across this will have some context.

From excuses:
trying: apache2
skipped: apache2 (0, 56, 7)
    got: 15+0: a-8:a-1:a-1:i-1:p-3:s-1
    * ppc64el: libapache2-mod-proxy-uwsgi-dbg, libapache2-mod-shib2

IRC discussion started here:

 <slangasek> ahasenack: in cosmic, libapache2-mod-shib2 is installable (though not coinstallable with other things)
 <slangasek> ahasenack: in cosmic-proposed, it is not installable because apache2-bin now depends on libcurl4 where it did not previously

So apache2-bin now ships a new module called mod-mo ( This module we (and debian) have been carrying in the archive as its own source. In the apache build it links with libcurl4, which is fine and good. But it does add a libcurl4 dependency to apache2-bin which wasn't there before.

Cue in libapache2-mod-shib2, from the shibboleth-sp2 source. It requires libxmltooling7, which in the archive is built with libcurl-openssl1.0-dev that is provided by a special curl3 source linked with openssl 1.0. That brings in libcurl3, which cannot be coinstalled with libcurl4. The curl package is a bit weird, because even though it's called libcurl3, it does not ship libcurl3:

$ apt-file search
libcurl3: /usr/lib/x86_64-linux-gnu/
libcurl3: /usr/lib/x86_64-linux-gnu/
libcurl4: /usr/lib/x86_64-linux-gnu/
libcurl4: /usr/lib/x86_64-linux-gnu/

And we have explicit conflicts between libcurl3 and libcurl4.

I don't know how to solve this, so I'm unassigning myself from the bug.