Hi Ian,
On 28.11.21 19:21, Ian Jackson wrote:
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'm aware of that. And "shortly" definitely means "before the autoremoval"
(which is currently scheduled for 2022-01-01). Is there a particular reason for
the urgency that I'm missing? Note that cppcheck is not a library, i.e., this
wrong dependency should not spread out by delaying the upload a bit.
(Fixing dpkg-shlibdeps and binNMUs is a different topic and is probably better
discussed in #100421.)
Best regards,
Joachim
