Guillem Jover:
> Bug #1000421 in package dpkg reported by you has been fixed in
> the dpkg/dpkg.git Git repository
Thanks for the investigation. What a nuisance.
Joachim Reichel (cppcheck maintainer):
> I'll upload a new version cppcheck with a workaround shortly
Would you mind both prioritising this fix ? FTAOD it's not just
cppcheck that is scheduled for autoremoval. Any package which
transitively [build-]depends on any package whose .debs are affected
will be scheduled for autoremoval (assuming some bug has been filed).
I noticed this problem because my own package `dgit` is scheduled for
autoremoval due to this bug and I don't even know what the dependency
chain is that links dgit to cppcheck. When this happens to me it
usually involves git-buildpackage, so perhaps gbp is scheduled for
autoremoval too.
I also think that when the fixed dpkg-shlibdeps is in unstable:
1. We should consider backporting the dpkg-shlibdeps fix in a
stable point release, since it seems people might have new
binutils (via a Debian backports suite or from upsteam)
2. We should consider trying to detect this situation in existing
.debs and requesting .deb rebuilds or something. Do we have a
plausible way of doing that ? Possibly we could look for the
combination of new binutils and old dpkg-dev, in buildinfo files.
Thanks,
Ian.
--
Ian Jackson <ijack...@chiark.greenend.org.uk> These opinions are my own.
Pronouns: they/he. If I emailed you from @fyvzl.net or @evade.org.uk,
that is a private address which bypasses my fierce spamfilter.
