Your message dated Sat, 26 Oct 2024 16:34:33 +0000
with message-id <[email protected]>
and subject line Bug#1057351: fixed in hypercorn 0.17.3-2
has caused the Debian Bug report #1057351,
regarding src:hypercorn: fails to migrate to testing for too long: new 
Dependency not in testing
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.)


-- 
1057351: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057351
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: hypercorn
Version: 0.14.4-1
Severity: serious
Control: close -1 0.15.0-1
Tags: sid trixie
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:hypercorn has been trying to migrate for 33 days [2]. Hence, I am filing this bug. The version in unstable has a Depends on an RC buggy package: node-mermaid.

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

Paul

[1] https://lists.debian.org/debian-devel-announce/2023/06/msg00001.html
[2] https://qa.debian.org/excuses.php?package=hypercorn

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature


--- End Message ---
--- Begin Message ---
Source: hypercorn
Source-Version: 0.17.3-2
Done: Nilesh Patra <[email protected]>

We believe that the bug you reported is fixed in the latest version of
hypercorn, 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 [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Nilesh Patra <[email protected]> (supplier of updated hypercorn 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 [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Sat, 26 Oct 2024 21:40:58 +0530
Source: hypercorn
Architecture: source
Version: 0.17.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team <[email protected]>
Changed-By: Nilesh Patra <[email protected]>
Closes: 1057351
Changes:
 hypercorn (0.17.3-2) unstable; urgency=medium
 .
   * Team Upload.
   * Partially Revert "Use local mermaid.js file instead of the
     CDN one to prevent a privacy breach." (Closes: #1057351)
Checksums-Sha1:
 1a3b62fb64c386e937a432e11555bf8975c8ac03 2053 hypercorn_0.17.3-2.dsc
 d97178912ff2c827e9009478562f1b470a990633 5016 hypercorn_0.17.3-2.debian.tar.xz
 f7fb5954bd888aabb8ea5edfaae7f45d01d659bc 9234 
hypercorn_0.17.3-2_amd64.buildinfo
Checksums-Sha256:
 99c7512b8aab70b60607f7e377e23f3e59eb69e28cd3bd170d0e59f682d5997a 2053 
hypercorn_0.17.3-2.dsc
 b9d5c4dacccbe81307ced6255aea811fc72254c3b07b37f93608f16b4d321cf9 5016 
hypercorn_0.17.3-2.debian.tar.xz
 3598d21cd13bfa5e4f878829d44ee4c8e5e1384508744c7668e67c8de457c645 9234 
hypercorn_0.17.3-2_amd64.buildinfo
Files:
 6a56bebb0833c245a0ef44c4d01cfd9e 2053 python optional hypercorn_0.17.3-2.dsc
 5693258b2037d1ae850ff8ad746bd25b 5016 python optional 
hypercorn_0.17.3-2.debian.tar.xz
 6a6b33f9a132ee6dde754dc067e49eb8 9234 python optional 
hypercorn_0.17.3-2_amd64.buildinfo

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

iIgEARYIADAWIQSglbZu4JAkvuai8HIqJ5BL1yQ+2gUCZx0ZiRIcbmlsZXNoQGRl
Ymlhbi5vcmcACgkQKieQS9ckPtpawwD/eAuXXmIfUZM80TVskxPdtI1G/x0rpLXY
2z95j4f7an0BAKeOEY//axnwrb4lCjbG3ow/fee9K9dYf4dH6UE5ID0E
=jAJD
-----END PGP SIGNATURE-----

Attachment: pgp6Xq72NNzG5.pgp
Description: PGP signature


--- End Message ---

Reply via email to