Hi Sylvestre et al, On Fri, Mar 14, 2025 at 12:53:26PM +0200, Adrian Bunk wrote: > Control: severity -1 serious > Control: tags -1 ftbfs > Control: reassign -1 libunwind-17-dev > Control: retitle -1 libunwind-17-dev: Please remove Provides: libunwind-dev > Control: clone -1 -2 -3 -4 > Control: reassign -2 libunwind-18-dev > Control: retitle -2 libunwind-18-dev: Please remove Provides: libunwind-dev > Control: reassign -3 libunwind-19-dev > Control: retitle -3 libunwind-19-dev: Please remove Provides: libunwind-dev > Control: reassign -4 libunwind-20-dev > Control: retitle -4 libunwind-20-dev: Please remove Provides: libunwind-dev > > 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? It seems like it would be possible to do this, so I'm wondering why it wasn't done. Probably there's some hidden blocker which I've missed. If so, it'd be nice to not have these bugs show up on the UDD search for trixie. Chris
