libxmltooling7 depends on libcurl3, which has been replaced by libcurl4 in Bionic

Bug #1776489 reported by Neil Hoggarth on 2018-06-12
94
This bug affects 18 people
Affects Status Importance Assigned to Milestone
moonshot-gss-eap (Ubuntu)
Undecided
Unassigned
opensaml2 (Ubuntu)
Undecided
Unassigned
shibboleth-resolver (Ubuntu)
Undecided
Unassigned
shibboleth-sp2 (Ubuntu)
Undecided
Unassigned
xmltooling (Ubuntu)
Undecided
Unassigned

Bug Description

I am attempting to make use of libapache2-mod-shib2 on Ubuntu 18.04 LTS.

Shibboleth installs and works as expected on top of a minimal Ubuntu install. However it has a dependency on libcurl3 (via libxmltooling7).

Almost all of the other libcurl using packages on Ubuntu 18.04 depend on libcurl4.

libcurl4 is declared to conflict with libcurl3.

Therefore, almost no other libcurl using packages in 18.04 can co-exist with the Shibboleth packages.

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in xmltooling (Ubuntu):
status: New → Confirmed

Neil Hoggarth <email address hidden> writes:

> I am attempting to make use of libapache2-mod-shib2 on Ubuntu 18.04 LTS.

> Shibboleth installs and works as expected on top of a minimal Ubuntu
> install. However it has a dependency on libcurl3 (via libxmltooling7).

> Almost all of the other libcurl using packages on Ubuntu 18.04 depend on
> libcurl4.

Shibboleth upstream doesn't support OpenSSL 1.1, and libcurl4 is probably
built against OpenSSL 1.1.

There aren't many good solutions to this problem until Shibboleth releases
a version that supports OpenSSL 1.1. I think the Shibboleth packages have
beem removed from Debian testing for the same reason.

--
Russ Allbery (<email address hidden>) <http://www.eyrie.org/~eagle/>

tags: added: bionic packaging
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in shibboleth-sp2 (Ubuntu):
status: New → Confirmed
Bert Van de Poel (bhack) wrote :

This bug really messed up our webworker upgrades to 18.04. We are forced to do this rather messy workaround/hack for now: https://depts.washington.edu/bitblog/2018/06/libcurl3-libcurl4-shibboleth-php-curl-ubuntu-18-04/

Dimitri John Ledkov (xnox) wrote :

We have tried to migrate everything to libcurl4 api/abi with openssl1.1 and managed to do that for everything but http://people.canonical.com/~ubuntu-archive/transitions/html/curl4.html xmltooling.... unfortunately we couldn't just kick out xmltooling as that is needed to build a few packages.

Maybe we should have simply kicked out xmltooling and the reverse deps.

Adam Bishop (adam-omega) wrote :

OpenSSL 1.1 support should have been in the 3.0 release earlier this month.

https://issues.shibboleth.net/jira/browse/CPPXT-110

Bert Van de Poel (bhack) wrote :

@adam-omega Shibboleth 3.0 isn't packaged by Ubuntu or Debian yet and will most certainly never land in 18.04.

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in moonshot-gss-eap (Ubuntu):
status: New → Confirmed
Changed in opensaml2 (Ubuntu):
status: New → Confirmed
Changed in shibboleth-resolver (Ubuntu):
status: New → Confirmed
Tom Misilo (tmisilo) wrote :

Hi, just seeing if there is a timeline for resolution on this issue? Thanks!

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers