Your message dated Fri, 29 May 2026 10:02:29 +0100
with message-id <[email protected]>
and subject line Resolved in version 3
has caused the Debian Bug report #1137198,
regarding src:loggerhead: fails to migrate to testing for too long
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1137198: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1137198
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: loggerhead
Version: 2.0.3-3
Severity: serious
Control: close -1 2.0.3+dfsg-1
Tags: sid forky
User: [email protected]
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:loggerhead has been trying to migrate for 33 days [2], hence
this bug report. The current output of the migration software for this package
is copied to the bottom of this report and should list the reason why the
package is blocked.
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. Blocked packages can have impact on other packages, which makes
preparing for the release more difficult. The situation that caused this bug
report might even be the result of such an issue. We expect maintainers to fix
issues that hamper the migration of their package in a timely manner. If your
package in this situation due to another package, consider helping out.
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.
This bug submission immediately closes the bug with the version in unstable, so
if that version or a later version migrates, this bug will no longer affect
testing. This bug is also tagged to only affect sid and forky, 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.
This bug report has been automatically generated. If you have any comments with
regards to the content or the process, please reach out to me.
Paul
[1] https://lists.debian.org/debian-devel-announce/2023/06/msg00001.html
[2] https://qa.debian.org/excuses.php?package=loggerhead
Current text from [2]:
Migration status for loggerhead (2.0.3-3 to 2.0.3+dfsg-1): BLOCKED:
Rejected/violates migration policy/introduces a regression
Issues preventing migration:
∙ ∙ Updating loggerhead would introduce bugs in testing: #1083464
Additional info (not blocking):
∙ ∙ Piuparts tested OK -
https://piuparts.debian.org/sid/source/l/loggerhead.html
∙ ∙ Reproduced on amd64 - info
∙ ∙ Reproduced on arm64 - info
∙ ∙ Reproduced on armhf - info
∙ ∙ Reproduced on i386 - info
∙ ∙ 32 days old (needed 5 days)
--- End Message ---
--- Begin Message ---
Version: 3.0.1+dfsg-1
This is fixed in the new version of loggerhead, which ports it from
Python to Rust.
--- End Message ---
