Hi! On Sat, 2021-12-04 at 23:09:19 +0000, Ian Jackson wrote: > Joachim: > > I'm aware of that. And "shortly" definitely means "before the > > autoremoval" (which is currently scheduled for 2022-01-01). > > The real deadline is when I ought to take action myself, as someone > adversely affected by an RC bug.
Sorry for not having updated the report before, but I didn't see the urgency either, and was planning on dealing with it before this had any further effect. I'd have appreciated more a request for a status update, instead of wielding the NMU around though… > The timeline for fixing this is: > > NMU DELAYED-10 upload of fixed dpkg > wait 10 days > wait ?? days for dpkg to migrate, say 5 (I think there are tests) > NMU DELAYED-10 upload of no-change cppcheck > wait 10 dayhs > wait 10 days for cppcheck to migrate > > Total waiting time here is 35 days plus time I spend doing the work. There's another RC in dpkg, which I have a fix for, but had pending reviewing it again and checking whether some of the cases from the report are handled right. And then there are also autopkgtest failures which I've also got fixed locally. My intention is to get this uploaded this weekend. > If I want to fix this without having to manually restart the > autoremoval clock and/or ask for help from the release team, I should > have NMU'd dpkg at least a week ago. (Where either of these first options, if they would be required at all, seem like way less effort and way less disruptive anyway…) Regards, Guillem
