Your message dated Sun, 10 Jun 2018 00:54:04 +0100
with message-id <20180609235404.GA24375@pinky>
and subject line Re: Bug#900511: libcurl4 Conflicts: libcurl3
has caused the Debian Bug report #900511,
regarding libcurl4 Conflicts: libcurl3
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
900511: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900511
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libcurl4
Version: 7.60.0-2
Severity: serious
libcurl4 conflicts with libcurl3, which violates the stated purpose of
the "must" clause at Policy 8.1 (to allow multiple versions of a shared
library to be co-installable), even though it doesn't violate the letter
of the must (binary package name must change when SONAME changes).
Without the second sentence at Policy 8.1, the MUST requirement serves
no purpose, so I have given this severity serious.
This means that, regardless of what Debian does with packages depending
on libcurl, libcurl4 cannot be installed if the user has third party or
home brew software that requires libcurl3.
I found this because I have netsurf-gtk installed, which Depends:
libcurl3. netsurf-gtk is currently the same version in stable and
unstable, but has been removed from testing.
...Marvin
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'stable-updates'), (500, 'stable'), (200,
'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.15.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
On Mon, Jun 04, 2018 at 12:33:09AM +0200, Richard B. Kreckel wrote:
> On Sat, 2 Jun 2018 23:14:40 +0300 Adrian Bunk <b...@debian.org> wrote:
> > libcurl3 is not part of buster, and using libraries from previous
> > releases that are no longer present in a new stable Debian release is
> > not strictly supported - it works most of the time, but when problems
> > are reported a Breaks/Conflicts against that library is usually the
> > solution.
>
> Yeah, I have read this:
> https://salsa.debian.org/debian/curl/merge_requests/2.
>
> Still, the question remains: Why can different libssl packages coexist
> fine (even if they are from a previous Debian version) but libcurl
> packages cannot?
This transition has already been discussed at length in #858398, but long story
short, both libcurl3 and libcurl4 provide the "libcurl.so.4" library (libcurl3
did so for historical reasons), so both packages can't be installed at the same
time. On the other hand the libssl packages provide different libraries
("libssl.so.1.0.2" and "libssl.so.1.1") so they are co-installable.
Cheers
signature.asc
Description: PGP signature
--- End Message ---
