[Bug 1861304] Re: libmysqlclient-dev will not install with libssl1.0-dev

2020-03-10 Thread David Cunningham
I see, thank you. It's a shame that MySQL would make such a change within a major version. We have worked as follows, though it's a bit of a nasty solution: apt install libmysqlclient-dev # will install libssl-dev as a dependency apt download libssl1.0-dev # download required package manually

[Bug 1861304] Re: libmysqlclient-dev will not install with libssl1.0-dev

2020-03-10 Thread Robie Basak
Some further information. libmysqlclient-dev as released in Bionic originally did not depend on libssl-dev as MySQL at that time used an embedded version of yassl. However MySQL upstream moved to OpenSSL in their stable 5.7 series, so Ubuntu had to switch to building against the packaged OpenSSL.

[Bug 1861304] Re: libmysqlclient-dev will not install with libssl1.0-dev

2020-03-10 Thread Robie Basak
I see. There were changes related to OpenSSL 1.1 - see bug 1797386. I didn't realise libssl1.0-dev actually shipped original in Bionic. In that case, I think your report could be a valid regression report during Bionic's lifetime itself, so I'll adjust the bug metadata accordingly. Unfortunately

[Bug 1861304] Re: libmysqlclient-dev will not install with libssl1.0-dev

2020-03-09 Thread David Cunningham
Asterisk 11 will not compile against libssl-dev. What seems strange is I believe we previously had both libssl1.0-dev and libmysqlclient-dev installed on an Ubuntu 18 server. Was the conflict introduced in an update to Ubuntu 18? If so then changing such things within a version doesn't seem

[Bug 1861304] Re: libmysqlclient-dev will not install with libssl1.0-dev

2020-03-09 Thread Robie Basak
> It's causing us big problems because when compiling Asterisk 11 from source it requires both. Does anyone know of a solution? Please see the previous comments. You can build against libssl-dev, not libssl1.0-dev. Ubuntu Bionic builds against OpenSSL 1.1 for almost everything. If you must use

[Bug 1861304] Re: libmysqlclient-dev will not install with libssl1.0-dev

2020-03-05 Thread Carlos Quiros
Any idea when this could be fixed? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861304 Title: libmysqlclient-dev will not install with libssl1.0-dev To manage notifications about this bug go to:

[Bug 1861304] Re: libmysqlclient-dev will not install with libssl1.0-dev

2020-03-05 Thread David Cunningham
When was this conflict between libmysqlclient-dev and libssl1.0-dev introduced? It's causing us big problems because when compiling Asterisk 11 from source it requires both. Does anyone know of a solution? -- You received this bug notification because you are a member of Ubuntu Bugs, which is

Re: [Bug 1861304] Re: libmysqlclient-dev will not install with libssl1.0-dev

2020-01-29 Thread Chris Salch
Thanks for the technical aspect there. That's not something I'd run into in other cases. On Wed, Jan 29, 2020, 12:01 Colin Watson wrote: > Runtime libraries can't usefully use metapackages the way you're > proposing, and it's not conventional to do so. Whether a dependency is > on libssl1.0.0

[Bug 1861304] Re: libmysqlclient-dev will not install with libssl1.0-dev

2020-01-29 Thread Colin Watson
Runtime libraries can't usefully use metapackages the way you're proposing, and it's not conventional to do so. Whether a dependency is on libssl1.0.0 or libssl1.1 depends on what the binaries depending on them were built against; forcibly dropping in libssl1.1 would result in broken programs.

[Bug 1861304] Re: libmysqlclient-dev will not install with libssl1.0-dev

2020-01-29 Thread Chris Salch
So, the fact that there is not libssl package doesn't constitute a naming problem? My expectation has been that there should be a and matching -dev but that's not the case here unless I'm very mistaken. -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 1861304] Re: libmysqlclient-dev will not install with libssl1.0-dev

2020-01-29 Thread Dimitri John Ledkov
There are no naming issues. src:openssl transitioned from providing 1.0.2x series to providing 1.1.1x series by default. In bionic, when src:openssl moved to provide 1.1.1x series, a separate src:openssl1.0 package was introduced to provide (temporarily) libssl1.0-dev in bionic only, which is

[Bug 1861304] Re: libmysqlclient-dev will not install with libssl1.0-dev

2020-01-29 Thread Chris Salch
We have an automated install script that was carried across from 16.04 based systems. I suspect that this may boil down to the odd naming convention on the libssl pacakages (i.e. the lack of a libssl package while there is a dev one ...). I'm trying out the libssl1.1 package right now and it looks

[Bug 1861304] Re: libmysqlclient-dev will not install with libssl1.0-dev

2020-01-29 Thread Marc Deslauriers
Ubuntu 18.04 contains two versions of Openssl: openssl 1.1 and openssl 1.0. Unfortunately, upstream MySQL now requires it to be linked against OpenSSL 1.1, where previously it used an internal ssl library. It is no longer possible to use openssl 1.0 concurrently with MySQL. What is requiring

[Bug 1861304] Re: libmysqlclient-dev will not install with libssl1.0-dev

2020-01-29 Thread Dave Chiluk
Targeting for bionic, but I haven't checked the other releases. I will say it's odd that there's a libssl-dev and libssl-doc but not a libssl only a libssl1.0 and a libssl1.1. I'm sure there's reasons, and I'm not privy to them. -- You received this bug notification because you are a member

[Bug 1861304] Re: libmysqlclient-dev will not install with libssl1.0-dev

2020-01-29 Thread Dave Chiluk
** Changed in: mysql-5.7 (Ubuntu) Importance: Undecided => High ** Also affects: mysql-5.7 (Ubuntu Bionic) Importance: Undecided Status: New ** Tags added: regression-release ** Changed in: mysql-5.7 (Ubuntu Bionic) Milestone: None => bionic-updates ** Changed in: mysql-5.7