On 14 October 2021 at 10:55, Paul Gevers wrote:
| Source: gsl
| Version: 2.6+dfsg-2
| Severity: serious
| Control: close -1 2.7+dfsg-2
| 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:gsl 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.

I believe this to be an issue in the three packages listed here:

    https://qa.debian.org/excuses.php?package=gsl

As we see here, the package itself is just fine

    https://buildd.debian.org/status/package.php?p=gsl

Dirk

| Paul
| 
| [1] https://lists.debian.org/debian-devel-announce/2020/02/msg00005.html
| [2] https://qa.debian.org/excuses.php?package=gsl
| 
| 
| x[DELETED ATTACHMENT OpenPGP_signature, application/pgp-signature]

-- 
https://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Reply via email to