Your message dated Sun, 04 May 2025 15:38:37 +0000
with message-id <e1ubbql-00gr5w...@fasolo.debian.org>
and subject line Bug#1104151: fixed in python-xarray 2025.03.1-5
has caused the Debian Bug report #1104151,
regarding src:python-xarray: 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.)


-- 
1104151: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1104151
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-xarray
Version: 2025.01.2-1
Severity: serious
Control: close -1 2025.03.1-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:python-xarray 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. 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=python-xarray

Current text from [2]:
Migration status for python-xarray (2025.01.2-1 to 2025.03.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
Issues preventing migration:
∙ ∙ autopkgtest for python-xarray/2025.03.1-2: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻ (reference ♻)
Additional info:
∙ ∙ Updating python-xarray will fix bugs in testing: #1100293
∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-xarray.html ∙ ∙ No reference result, but not reproducibility on amd64 - info ♻ ∙ ∙ No reference result, but not reproducibility on arm64 - info ♻ ∙ ∙ Waiting for reproducibility test results on armhf - info ♻ ∙ ∙ 15 days old (needed 10 days)

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature


--- End Message ---
--- Begin Message ---
Source: python-xarray
Source-Version: 2025.03.1-5
Done: Julian Gilbey <j...@debian.org>

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

Debian distribution maintenance software
pp.
Julian Gilbey <j...@debian.org> (supplier of updated python-xarray 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: Sun, 04 May 2025 13:53:03 +0100
Source: python-xarray
Architecture: source
Version: 2025.03.1-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 
<debian-science-maintain...@lists.alioth.debian.org>
Changed-By: Julian Gilbey <j...@debian.org>
Closes: 1104151
Changes:
 python-xarray (2025.03.1-5) unstable; urgency=medium
 .
   * Team upload
   * Skip failing tests using PYBUILD_TEST_ARGS so they are skipped at both
     build and autopkgtest time (closes: #1104151)
Checksums-Sha1:
 95b70fb4f2c44f31e366d785bf51edd607660ec7 3942 python-xarray_2025.03.1-5.dsc
 e562676426c3d44e92826d6ae4f0a267181fbc79 20492 
python-xarray_2025.03.1-5.debian.tar.xz
 34661f60187978a9d76652f1519528f6c499d7be 23685 
python-xarray_2025.03.1-5_amd64.buildinfo
Checksums-Sha256:
 78fc51847869b94a87b6dd93e98018ab43a0ff119d07d7c572dcb09321fc41d8 3942 
python-xarray_2025.03.1-5.dsc
 b7029756877f21fa6e3ef8030f401277493e98763a18027c2011106dbd45c9b0 20492 
python-xarray_2025.03.1-5.debian.tar.xz
 bd01a195278d372a58672b4982968e307199a16dfa8fff61784c28ff8ddc7e40 23685 
python-xarray_2025.03.1-5_amd64.buildinfo
Files:
 ee2737c57da962b247c4f8a17f7a6fa5 3942 python optional 
python-xarray_2025.03.1-5.dsc
 ac2a5805381a8f4addf43e3b52990662 20492 python optional 
python-xarray_2025.03.1-5.debian.tar.xz
 531e041e1588fe18c18c03e1ec019971 23685 python optional 
python-xarray_2025.03.1-5_amd64.buildinfo

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

iQIzBAEBCgAdFiEEfhrD+iemSShMMj72aVxCkxbAe/4FAmgXhicACgkQaVxCkxbA
e/6YWQ/9EPbdWbejMTFwQX8PgkXzHzkKGLbfrOMqqNIgxFHUARatQ6VGgnHIVvBd
7SKKAKJ5V7hZ24knhATYj6LkFxFcIVLc6WAkKV+jHydpbeDsKbsbVKcTVDHngCp4
WM3HT4jiPiQRyTAA+3l7ukQV06gtKdzmCIU4ESOwpV6xMzxnZxknfrMchbFEbNrR
ATuUSBwF36T2MQUDpgNnQZzh7fZFg0fz1nc1FFrfupZoaGKMgX6xNBHPBVD2owzc
TZRz0GDVJ7rbqhnCJffewc38whk5mFRRVsi8AOv1inRJoQsORSZWvoZkhv7h5B+n
rEuR5M6KjvIUhYKazxLWWIe9jvSFsqVnApkJHbQs/Mh3KYyNq3uHSfqPo7pQG3OB
BFTLLUOGqjaclCRa12NQ3CVlZc3vtU+FxKTmYVN1qFHjooLSNakEgBAI46r+jhgY
dT4jKQLoWh0mlw3FITaud7AImcEiA6e2//fzms9BfFH+CzEwX66SoooLVSl0j7Be
oFm+fnmxeYTLsDO2UgXZI6LfULj1R3Oet/4dg4wenmJgQ9lxAS6PqUlxhBk4bsYa
JbVPlm5QXvQapN1pFKcdfSiH37kJPSDqWzL8Kte98+URY5C1GvlPK+T6zMtItDpY
TEOOnrUYK0YlKWpEtonOmVdRAkOVNuqukSeg7Z4mqiVTh7S0Lv0=
=V3pv
-----END PGP SIGNATURE-----

Attachment: pgpxxoxGzlNUU.pgp
Description: PGP signature


--- End Message ---

Reply via email to