Bug#1061232: src:coq: fails to migrate to testing for too long: triggers autopkgtest issues
Hi,
Le dimanche 21 janvier 2024 à 08:42 +0100, Paul Gevers a écrit :
> Source: coq
> Version: 8.17.0+dfsg-1
> Severity: serious
> Control: close -1 8.18.0+dfsg-1
> Tags: sid trixie
> User: release.debian.org@packages.debian.org
> Usertags: out-of-sync
>
> Dear maintainer(s),
>
> The Release Team considers packages that are out-of-sync between
> testing and unstable for more than 30 days as having a Release
> Critical bug in testing [1]. Your package src:coq has been trying to
> migrate for 31 days
> [2]. Hence, I am filing this bug. The version in unstable causes
> autopkgtest failures in multiple reverse (test) dependencies:
> mathcomp-analysis (affected by FTBFS bug 1060988) and mathcomp-finmap
> (which has a newer version in unstable with issues).
>
> If a package is out of sync between unstable and testing for a longer
> period, this usually means that bugs in the package in testing cannot
> be fixed via unstable. Additionally, blocked packages can have impact
> on other packages, which makes preparing for the release more
> difficult.
> Finally, it often exposes issues with the package and/or
> its (reverse-)dependencies. We expect maintainers to fix issues that
> hamper the migration of their package in a timely manner.
>
> This bug will trigger auto-removal when appropriate. As with all new
> bugs, there will be at least 30 days before the package is auto-
> removed.
>
> I have immediately closed this bug with the version in unstable, so
> if
> that version or a later version migrates, this bug will no longer
> affect
> testing. I have also tagged this bug to only affect sid and trixie,
> so
> it doesn't affect (old-)stable.
>
> If you believe your package is unable to migrate to testing due to
> issues beyond your control, don't hesitate to contact the Release
> Team.
I fixed the mathcomp-finmap issue in unstable, so in two days (too
young excuse) that will leave only mathcomp-analysis blocking Coq-
related packages from migrating as far as I can tell.
The problem with mathcomp-analysis is that:
- I had understood upstream would release a version compatible with "MC
2" (ssreflect package in Debian) by the end of december, so I started
uploading the whole set (about fifty packages) even though I didn't
have that good version yet, pretty confident the breakage would be
transitory, perhaps even invisible since it's a leaf package ;
- but then the new compatible release would come in january ;
- and now january is coming to an end without it ;
- in fact there was a new release three days ago to add compatibility
with the yet-unreleased next Coq... but still "MC 1"!
The conclusion is: I shouldn't have jumped the gun.
Would kicking the mathcomp-analysis package out of testing allow the
migration of the rest of the Coq-related packages and at least give a
coherent set there? That would still leave mathcomp-analysis broken in
unstable, of course, but that's a lesser evil.
If the issue isn't cleared for testing by february first, I'll just ask
for a full RM of mathcomp-analysis : a brutal fix, but an efficient
one.
Thanks,
J.Puydt
Reply to: