On Tue, Aug 15, 2017 at 10:11:36PM +0200, Emilio Pozuelo Monfort wrote: > On 08/08/17 03:56, James McCoy wrote: > > Package: release.debian.org > > Severity: normal > > User: release.debian....@packages.debian.org > > Usertags: transition > > > > I'd like to upload the new msgpack-c to unstable. I did a test rebuild > > in July and filed bugs[0] against the packages which fail to build with > > the new API changes. > > > > [0]: > > https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=msgpac...@packages.debian.org;tag=msgpack-c-2.x;dist=unstable > > > > The below Ben settings will detect the packages using the C library > > which need to be rebuilt, but the C++ library is header-only. I'm not > > sure the how that should be tracked, other than FTBFS bugs. > > > is_affected = .depends ~ "libmsgpackc2"; > > is_good = .depends ~ /libmsgpackc2 \(>= 2\.1\.0)/ | .depends ~ > > /libmsgpackc2 \(>= 0\.5\.7); > > is_bad = .depends ~ /libmsgpackc2 \(>= 1\.0\.0\)/; > > Why do the C library rdeps need to be rebuilt if the SONAME didn't change?
Hmm, you have a good point there. :) There are incompatible API changes for the (header only) C++ library, but no ABI changes for the C library. Maybe I need to split the C++ headers out into their own APIv1 and APIv2 packages. Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
