Your message dated Sun, 23 Mar 2025 05:49:08 +0000
with message-id <e1twecq-008ovo...@fasolo.debian.org>
and subject line Bug#1101052: fixed in systraq 20201231-3
has caused the Debian Bug report #1101052,
regarding src:systraq: 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 ow...@bugs.debian.org
immediately.)


-- 
1101052: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1101052
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: systraq
Version: 20201231-1
Severity: serious
Control: close -1 20201231-2
Tags: sid trixie
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 30 days as having a Release Critical bug in testing [1]. Your package src:systraq has been trying to migrate for 31 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. 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.

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

This bug report has been automatically generated and has only been sent manually. 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=systraq

Current text from [2]:
Migration status for systraq (20201231-1 to 20201231-2): BLOCKED: Rejected/violates migration policy/introduces a regression
Issues preventing migration:
∙ ∙ Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/s/systraq.html
Additional info:
∙ ∙ Reproducible on amd64 - info ♻ ∙ ∙ Reproducible on arm64 - info ♻ ∙ ∙ Reproducible on armhf - info ♻ ∙ ∙ Reproducible on i386 - info ♻ ∙ ∙ 30 days old (needed 5 days)

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature


--- End Message ---
--- Begin Message ---
Source: systraq
Source-Version: 20201231-3
Done: Joost van Baal-Ilić <joos...@debian.org>

We believe that the bug you reported is fixed in the latest version of
systraq, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1101...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Joost van Baal-Ilić <joos...@debian.org> (supplier of updated systraq package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Sat, 22 Mar 2025 18:05:01 +0100
Source: systraq
Architecture: source
Version: 20201231-3
Distribution: unstable
Urgency: medium
Maintainer: Joost van Baal-Ilić <joos...@debian.org>
Changed-By: Joost van Baal-Ilić <joos...@debian.org>
Closes: 1101052
Changes:
 systraq (20201231-3) unstable; urgency=medium
 .
   * d/control: replace heirloom-mailx dependency as alternative for bsd-mailx
     with s-nail: At around 2016 Debian stopped shipping heirloom-mailx and
     started shipping s-nail.  See Bug #809609: "RM: heirloom-mailx --
     unmaintained upstream, successor available". Fixes "src:systraq: fails to
     migrate to testing for too long".  Thanks Paul Gevers. Closes: #1101052
Checksums-Sha1:
 d172931fc4cf6b8a42681db1493caf97f7642fb4 2088 systraq_20201231-3.dsc
 bdfda6d97d097a70352187aeb17f13ad0991280e 233164 
systraq_20201231-3.debian.tar.xz
 5a58613c96af9b2128e1b9bd4ddcddb21b9456dc 5432 
systraq_20201231-3_source.buildinfo
Checksums-Sha256:
 41f6d51a11315c39e327c72594eae1d3316bf4bef63ac3c21fb75c207cb49081 2088 
systraq_20201231-3.dsc
 20749474d4f5e0ae9e53d710b36e5888a2c69477202a3d917442c544efd4a24a 233164 
systraq_20201231-3.debian.tar.xz
 50c9819942f490b1147ce29c67ce43808c7b84c0534a12e5320bc35ffd6eb1eb 5432 
systraq_20201231-3_source.buildinfo
Files:
 e8bff0f44044ebb4458feb82f6e008b2 2088 admin optional systraq_20201231-3.dsc
 92622544342c814ed3906cbf6ffaa011 233164 admin optional 
systraq_20201231-3.debian.tar.xz
 a144a51c61f09c280158125aaea37143 5432 admin optional 
systraq_20201231-3_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEkqrZAbIbS8eaR6AwVPGmYxdIZxMFAmffm24ACgkQVPGmYxdI
ZxOdZhAAxwvaoMMJQHqbct0aavfHk0ZZWY7RPWWh4j9JdQrJekGeVwztFSS/3lQc
sSEGjseozwAnjGeTUso+UIO2Dj1GUNSPUR2M3LyKVltwxi0zhTNRqSjafPTTuxK8
6trhGBiIyr8PRAUgdA13vr3xXnAr8heocXXQ9SXmmJ9oAQlSER+urFy3a/n3Jl74
XxonLxpIvqIxphE0mbALiYGnj8paQ6h/4bQOA+SP/bwXj262DGx7KT6z+IWyFA8S
9sPIU6RDjR2P32M4A4/kJjbQCUUoXAPebBILOkKSncQ12Sq+DJGGLjYeKdS4EnPO
4F7qCgNXYxrxWvYFyWvwFexQG9mDetsTBYHHB08UkJMb5KraFDELgBsfss7RGW7d
u1T2Yg0PgrbLhjfE1D6q0rU4dcILBoVxZQNVqKr+Ry8l/FHh9luE5kaKEOpfRvwP
ZTpnIx/WB5KgqM4KiE9avSVj6LiS8sU/vvEEZS+qMO4PrPsKkcUulzuyL/YrlPnv
26Ll+3R/GMYE1YE0CvhoMqU17B3CjdUKO6YtmZX8OeZ9hF/NqKiOJXOiJjaSNPzi
8jjSDu8UASC0MMCFCr4l5laMOp+lNVyLu2zWynvjXfLOiz0hwUuwPOxYvc9Dg3JJ
q7+kYt69oetkwN5zPQoe/A59g/Kkj/sa9qiYvx7Uc3uPwoMdXto=
=2xwT
-----END PGP SIGNATURE-----

Attachment: pgpJykoDPlnLL.pgp
Description: PGP signature


--- End Message ---

Reply via email to