Re: Bug#900511: libcurl4 Conflicts: libcurl3
On Sun, Jun 03, 2018 at 10:12:22AM -0400, Marvin Renich wrote:
> * Russ Allbery <rra@debian.org> [180602 22:41]:
>...
> > or we'd need to call our version libcurl5 or something,
> > which would break compatibility with everyone else.
>
> That's almost what I meant. Upstream should recognize that in spite of
> their strong statements about not _ever_ breaking ABI, their exposure of
> openssl 1.1 structure has, indeed, broken ABI and they should be
> responsible and admit it and bump SONAME. (This is all based on my
> much-less-than-expert understanding of the discussion; my opinion might
> be way off here.) If I'm right, though, this would make everyone happy;
> all distributions would have libcurl5, our libcurl3/4 mix could stay as
> is, and no Conflicts would be necessary.
This would have been a valid point 2 years ago when OpenSSL 1.1 support
was added to libcurl.
Today with everyone else (including the current Ubuntu LTS)
already using libcurl4 with OpenSSL 1.1 this is moot.
> ...Marvin
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
Reply to: