Bug#998703: src:gnuastro: fails to migrate to testing for too long: ftbfs on mips64el

[Mohammad Akhlaghi]

Dear Paul,

Thank you very much for noticing this and marking the bug as fixed. 
Also, I really appreciate the great explanation of the significance of 
such situations, I completely agree.


The delay originated from the Debian version freezing: version 0.15 of 
Gnuastro came in that time slot (so it couldn't be updated in Debian). 
By the time the freeze was lifted, Gnuastro had significantly grown (and 
almost ready for version 0.16). But we pushed version 0.15 only to keep 
continuity.


It was only after uploading version 0.15 that we noticed the bug in 
'mips64el'. So we fixed it and pushed it with all the other bug fixes 
that had been found as version 0.15.54. Because the library had changed 
in this time, the new upload went to the NEW stack (on September 22nd). 
However, it was stuck in the NEW list for about 1.5 months (with one 
rejection due to bad copyright statement that was immediately fixed and 
re-submitted). Ultimately it was approved this morning!


Version 0.16 of Gnuastro is already released upstream [1], so as soon as 
Gnuastro 0.15.54 passes on all CPU architectures in the experimental 
branch [2], we will upload version 0.16 to 'testing'.


Thanks again,
Mohammad

[1] https://lists.gnu.org/archive/html/info-gnuastro/2021-10/msg0.html
[2] 
https://buildd.debian.org/status/package.php?p=gnuastro=experimental

Bug#998703: src:gnuastro: fails to migrate to testing for too long: ftbfs on mips64el

[Paul Gevers]

Source: gnuastro
Version: 0.14-1
Severity: serious
Control: close -1 0.15-1
Tags: sid bookworm
User: release.debian@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 60 days as having a Release Critical bug in
testing [1]. Your package src:gnuastro has been trying to migrate for 61
days [2]. Hence, I am filing this bug.

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 bookworm, 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.

Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=gnuastro




OpenPGP_signature
Description: OpenPGP digital signature