Bug#1002857: libgoogle-glog-dev: Dependency on libunwind-dev

[Marc Glisse]

Package: libgoogle-glog-dev
Version: 0.5.0+really0.4.0-2
Severity: normal

Dear Maintainer,

with the switch to llvm-13 in testing, installing libgoogle-glog-dev has
become problematic, it depends on libunwind-dev, but that conflicts with
libunwind-13-dev. I couldn't find an official doc on what the LLVM
maintainers expect, but it looks like depending on libunwind-x.y-dev may
work. I didn't test it though, some libunwind files seem to have moved,
and I may have completely misunderstood the relation between the various
libunwind packages.

-- System Information:
Debian Release: bookworm/sid
APT prefers testing-debug
APT policy: (500, 'testing-debug'), (500, 'stable-security'), (500, 'stable-debug'), (500, 'testing'), (500, 'stable'), (50, 'unstable-debug'), (50, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.15.0-2-amd64 (SMP w/16 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libgoogle-glog-dev depends on:
ii libgflags-dev 2.2.2-2
ii libgoogle-glog0v5 0.5.0+really0.4.0-2
ii libunwind-dev 1.3.2-2

libgoogle-glog-dev recommends no packages.

libgoogle-glog-dev suggests no packages.

-- no debconf information

[Michael Weghorn]

Hi,

On Thu, 30 Dec 2021 11:11:43 +0100 Marc Glisse
<marc....@normalesup.org> wrote:
> Package: libgoogle-glog-dev
> Version: 0.5.0+really0.4.0-2
> Severity: normal
>
> Dear Maintainer,
>
> with the switch to llvm-13 in testing, installing libgoogle-glog-dev has
> become problematic, it depends on libunwind-dev, but that conflicts with
> libunwind-13-dev.
> I couldn't find an official doc on what the LLVM
> maintainers expect, but it looks like depending on libunwind-x.y-dev may
> work. I didn't test it though, some libunwind files seem to have moved,
> and I may have completely misunderstood the relation between the various
> libunwind packages.

I have run into a similar problem with the libgstreamer1.0-dev package,
which can no longer be installed in parallel with libc++-dev because

* libc++-dev depends on libc++-13-dev, which depends on
libunwind-13-dev, which breaks libunwind-dev
* libgstreamer1.0-dev depends on libunwind-dev

As far as I can see, two relevant commits in the LLVM packaging git repo
on the way to the current situation are:

* Commit c72a6c0e50e318c83e6bff901dd0e2e591f65145 [1], "Generate
libunwind-12 & libunwind-12-dev packages", which added the
libunwind-<VERSION>-dev package with a "Breaks" on libunwind-dev
* Commit 103cb1357c55b508e283d329083119d2429029ca [2], "libc++-13-dev
should depends on libunwind-13-dev (Closes: #995810)", which added the
corresponding dependency

Can the LLVM packaging team possibly give a hint what is the intended
way to deal with the situation?
(I would then open a bug report for libgstreamer1.0-dev with the
relevant information as well if something has to be done there)?

Best regards,
Michael


[1]
https://salsa.debian.org/pkg-llvm-team/llvm-toolchain/-/commit/c72a6c0e50e318c83e6bff901dd0e2e591f65145
[2]
https://salsa.debian.org/pkg-llvm-team/llvm-toolchain/-/commit/103cb1357c55b508e283d329083119d2429029ca