Your message dated Mon, 14 Nov 2022 20:44:41 +0000
with message-id <e1ougjt-00cmlp...@fasolo.debian.org>
and subject line Bug#1023152: fixed in jupyter-packaging 0.12.3-1.1
has caused the Debian Bug report #1023152,
regarding src:jupyter-packaging: fails to migrate to testing for too long: 
uploader built arch:all binary
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.)


-- 
1023152: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023152
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jupyter-packaging
Version: 0.12.2-2
Severity: serious
Control: close -1 0.12.3-1
Tags: sid bookworm pending
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:jupyter-packaging 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.

Your package is only blocked because the arch:all binary package(s) aren't built on a buildd. Unfortunately the Debian infrastructure doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will shortly do a no-changes source-only upload to DELAYED/15, closing this bug. Please let me know if I should delay or cancel that upload.

Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg00005.html
[2] https://qa.debian.org/excuses.php?package=jupyter-packaging

Attachment: OpenPGP_signature
Description: OpenPGP digital signature


--- End Message ---
--- Begin Message ---
Source: jupyter-packaging
Source-Version: 0.12.3-1.1
Done: Paul Gevers <elb...@debian.org>

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

Debian distribution maintenance software
pp.
Paul Gevers <elb...@debian.org> (supplier of updated jupyter-packaging 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: Sun, 30 Oct 2022 20:04:17 +0100
Source: jupyter-packaging
Architecture: source
Version: 0.12.3-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team <team+pyt...@tracker.debian.org>
Changed-By: Paul Gevers <elb...@debian.org>
Closes: 1023152
Changes:
 jupyter-packaging (0.12.3-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * source only upload to enable migration (Closes: #1023152)
Checksums-Sha1:
 0e318c7221e6a1d0eb537b4627a39b15c55431eb 2061 jupyter-packaging_0.12.3-1.1.dsc
 3978c552e5f59bf5efb0a3c5b3a61ec4ac7e9d9a 3544 
jupyter-packaging_0.12.3-1.1.debian.tar.xz
Checksums-Sha256:
 b4ddd53d86d685f0801f009b04f5fb1dfba0b70e7fcf6e7d8b47ad84115028b5 2061 
jupyter-packaging_0.12.3-1.1.dsc
 804c324d31b173d70ae16ed782a809e4d0d2efa4e8fd3b0d9241eb4dec6ace1e 3544 
jupyter-packaging_0.12.3-1.1.debian.tar.xz
Files:
 aae99126e96439ccfa7bdec0c5d3009d 2061 python optional 
jupyter-packaging_0.12.3-1.1.dsc
 b84cb0a64ce7ac8923837946e3de87bb 3544 python optional 
jupyter-packaging_0.12.3-1.1.debian.tar.xz

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

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAmNey9cACgkQnFyZ6wW9
dQpHVwf/SZVTrmX2Wyt5tK6LpFIj9bXv9ryIKkVp1C87QwaZJtzWyj3xU+3dcuOw
XwynYVghcBL/d4kZ6bbW6Z5hhfLEUYheOAEvgE3KIu4zUqQf9O4CkqGT7hwyW6Bk
S+MyUjsaiymiTGVyrMPdan7YGVZOD8zQokU6fKs54HqZaLmbVFf5WGxz1NxUHnei
yW4kc6lxu9Wp78//2jKfiHLDbTfJ2C9Y20kUXKy8QiOMGH2LGN+XN/PV9ZJzcA4L
QtA7ZOD3RY7p7iCwJcejULKhwF/TNLEj92+ls3w7f4xKwsmnE05b+Mohmazf9/tJ
tz8v1U5Q8cbub2cS8rEd4IzXy3F6Gg==
=B9Jq
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to