Le 25/04/2025 à 12:03, Simon McVittie a écrit :
Control: tags 1100481 + pending
On Mon, 21 Apr 2025 at 15:18:49 +0200, Chris Hofstaedtler wrote:
On Fri, Mar 14, 2025 at 12:53:26PM +0200, Adrian Bunk wrote:
On Sat, Dec 31, 2022 at 07:24:51PM +0100, Jakub Wilk wrote:
This package has "libunwind-dev" in Provides, but it's not fully compatible
with the real libunwind-dev package. Notably, it lacks the pkg-config file,
and there are quite a few users of that:
https://codesearch.debian.net/search?q=%5CbPKG_CHECK_MODULES%5Cb.%2A%5Cblibunwind%5Cb
...
This is a constant source of confusion and FTBFS, e.g.:
https://buildd.debian.org/status/logs.php?pkg=frr&ver=10.2.1-4
Please remove the Provides: libunwind-dev before trixie.
Will this happen for trixie? If not, is this bug (and #1027451,
#1100481, #1100483) really release-critical?
I see that commit 1585b88b "Remove "Provides: libunwind-dev"
(Closes: #1100481)" has been staged in llvm-toolchain git in the 18
branch, so I'm marking that bug as pending. Is the intention that its
fix will be uploaded before trixie?
yeah, i was waiting to have more contents before upload but I will just go ahead
today.
The 19 branch doesn't appear to have an equivalent commit, which would
resolve #1100482. If llvm-toolchain-19 might also need an upload for
#1095866, perhaps that would be a good opportunity to fix #1100482 in
the same upload?
sure
#1027451 is the equivalent bug for llvm-toolchain-17, which the
maintainers and release team are trying to remove (#1081250) in order to
reduce proliferation of versions, but that removal seems to be blocked
by reinstating the AMD gcn offload target (#1092643) so that
amdgcn-tools, which is required by gcc-13, can upgrade to LLVM 18 or 19
(#1084066). So fixing this in the 17 branch as well might be best.
ok, i will have a look to fix #1092643
S
