Your message dated Thu, 12 Jan 2023 17:23:19 +0000
with message-id <e1pg1in-00cvvu...@fasolo.debian.org>
and subject line Bug#1027930: fixed in xml2rfc 3.15.3-1
has caused the Debian Bug report #1027930,
regarding src:xml2rfc: fails to migrate to testing for too long: autopkgtest 
regression
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.)


-- 
1027930: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027930
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xml2rfc
Version: 3.13.1-1
Severity: serious
Control: close -1 3.15.2-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:xml2rfc has been trying to migrate for 61 days [2]. Hence, I am filing this bug. Your package is blocked because the autopkgtest regressed on all architectures we run it on.

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/msg00005.html
[2] https://qa.debian.org/excuses.php?package=xml2rfc

Attachment: OpenPGP_signature
Description: OpenPGP digital signature


--- End Message ---
--- Begin Message ---
Source: xml2rfc
Source-Version: 3.15.3-1
Done: Daniel Kahn Gillmor <d...@fifthhorseman.net>

We believe that the bug you reported is fixed in the latest version of
xml2rfc, 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 1027...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Daniel Kahn Gillmor <d...@fifthhorseman.net> (supplier of updated xml2rfc 
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: SHA256

Format: 1.8
Date: Thu, 12 Jan 2023 09:38:22 -0500
Source: xml2rfc
Architecture: source
Version: 3.15.3-1
Distribution: unstable
Urgency: medium
Maintainer: Daniel Kahn Gillmor <d...@fifthhorseman.net>
Changed-By: Daniel Kahn Gillmor <d...@fifthhorseman.net>
Closes: 1027930
Changes:
 xml2rfc (3.15.3-1) unstable; urgency=medium
 .
   * New upstream release
   * Work around brittle test (Closes: #1027930)
Checksums-Sha1:
 07717a4a530f804e2fd22ba0d7e44b287aa90f58 2067 xml2rfc_3.15.3-1.dsc
 da9f31835b09eaa13749a8b3c52e8c3f456f1e59 2645561 xml2rfc_3.15.3.orig.tar.gz
 cac4111f0a1d3eb5b58cb781cf3c4175b36120ef 850 xml2rfc_3.15.3.orig.tar.gz.asc
 6d0766a97434f9e12ad161e55556824d6afef915 24020 xml2rfc_3.15.3-1.debian.tar.xz
 b52d619f35238ca72d96eceff109e8766f263d9f 8572 xml2rfc_3.15.3-1_amd64.buildinfo
Checksums-Sha256:
 09b45a6afcad25a7f95656fb6248bff3d51d9b4e4e1d7ad51c21a067d45cedee 2067 
xml2rfc_3.15.3-1.dsc
 5d1c1d6f0bcaa7f53221b5fe712213d65d8a69ac84c6c64b16e6f88aee595788 2645561 
xml2rfc_3.15.3.orig.tar.gz
 fc7f49edeacbe7ad34433977779ca66bbc1f2ae746d5ec5d874e0b5d617ea35f 850 
xml2rfc_3.15.3.orig.tar.gz.asc
 516cc4ea8a7a23b0e1c796bba7be40f78de7452b32c34196c506e2facd35814e 24020 
xml2rfc_3.15.3-1.debian.tar.xz
 5292f7eedad6f7ae758eb72e1efdc4d6da817f2955044d8593297a75e1f1d860 8572 
xml2rfc_3.15.3-1_amd64.buildinfo
Files:
 9bce7741e3faf2bfc58908e52434593a 2067 non-free/text optional 
xml2rfc_3.15.3-1.dsc
 d83972610d018427e594ad6b6af6208b 2645561 non-free/text optional 
xml2rfc_3.15.3.orig.tar.gz
 285d7d1b6359379bc6f00295d95cb400 850 non-free/text optional 
xml2rfc_3.15.3.orig.tar.gz.asc
 cb11d8aaa5c61c11d36332a1bd56335f 24020 non-free/text optional 
xml2rfc_3.15.3-1.debian.tar.xz
 e2931d6dfc0d30b3569fc2c807b0df86 8572 non-free/text optional 
xml2rfc_3.15.3-1_amd64.buildinfo

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

iHUEARYIAB0WIQQttUkcnfDcj0MoY88+nXFzcd5WXAUCY8A64wAKCRA+nXFzcd5W
XOfAAQD5HY3kXGm+VAq+yL12Me58x2LUAR/fTCDs+1IAlm1RsQD+N5rXEDYwK1Wd
RtHVz/tY1WtJWqCcWX+MU5K07MoNGQw=
=+kkL
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to