On 2018-01-11 14:54:26 [+0100], Ondřej Surý wrote: > I commented at salsa.d.o, but for consistency, I am resending my comment here:
… > The conflict here means that all r-depends will have to migrate at once, and > absolutely no backports would be possible. I wish there would be a way where > libcurl3 and libcurl4 would be co-installable, but so far I haven't come up > with anything that would make it possible and still align the packages with > upstream names. You could do a proper transition and rename libcurl.so.4 to libcurl-ssl11.so.4 and provide a symlink libcurl.so.4 -> libcurl-ssl11.so.4 once the transition is over and the library out of unstable. *However* this symlink is dangerous since everything not shipped Debian wise would be suddenly linked againt libssl-1.1 while it might have been compiled against an earlier version. Maybe it would be wise to suggest to upstream to bump major 4 to a 5 to signal that this libcurl exposes the libssl1.1 ABI now. > The fact that the symbols were versioned with GNUTLS_*_3 complicates the > transition even more. > > But I guess it's a good time to finally bite the bullet and finish the > transition, I just wish there would be a less intrusive way. > > Ondrej Sebastian
