Re: Bug#900511: libcurl4 Conflicts: libcurl3
Marvin Renich <mrvn@renich.org> writes:
> * Russ Allbery <rra@debian.org> [180602 18:24]:
>> Adrian is of course correct.
>> The libcurl situation is exceptional and warranted a project-wide
>> discussion looking for cleaner migration paths (to no avail), so I
>> think
> Okay, I must have missed this discussion. Can you point me to the
> thread (on debian-devel?) related to this?
I don't have links to the previous (probably a dozen) discussions handy,
although you may be able to find them by searching for the OpenSSL 1.1
transition. The core reasons are summarized fairly succinctly here,
though:
https://salsa.debian.org/debian/curl/merge_requests/2
The core problem is that libcurl exposed an OpenSSL data structure, so
rebuilding against 1.1 changed the ABI without changing the SONAME, and
everything was made moderately more complicated (or at least confusing) by
the SONAME history of the library.
We've been going back and forth on this for something like a year, and
it's part of the reason (although not all of the reason) why the last
Debian stable shipped with both OpenSSL 1.0 and 1.1.
--
Russ Allbery (rra@debian.org) <http://www.eyrie.org/~eagle/>
Reply to: