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.

Hi,

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