Your message dated Mon, 29 Dec 2025 20:36:43 +0000
with message-id <[email protected]>
and subject line Bug#1124260: fixed in rust-rust-decimal 1.39.0-3
has caused the Debian Bug report #1124260,
regarding src:rust-rust-decimal: 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 [email protected]
immediately.)


-- 
1124260: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1124260
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: rust-rust-decimal
Version: 1.39.0-1
Severity: serious
Control: close -1 1.39.0-2
Tags: sid forky
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:rust-rust-decimal has been trying to migrate for 32 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 forky, 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=rust-rust-decimal

Current text from [2]:
Migration status for rust-rust-decimal (1.39.0-1 to 1.39.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
Issues preventing migration:
∙ ∙ Autopkgtest for rust-pyo3/0.27.2-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Test triggered (failure will be ignored), s390x: Pass ∙ ∙ Autopkgtest for rust-rust-decimal/1.39.0-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Regression ♻ (reference ♻) ∙ ∙ Autopkgtest for rust-sqlx-core/0.8.3-3: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Pass
Additional info (not blocking):
∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-rust-decimal.html ∙ ∙ Reproducible on amd64 - info ♻ ∙ ∙ Reproducible on arm64 - info ♻ ∙ ∙ 32 days old (needed 5 days)

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature


--- End Message ---
--- Begin Message ---
Source: rust-rust-decimal
Source-Version: 1.39.0-3
Done: Fabian Grünbichler <[email protected]>

We believe that the bug you reported is fixed in the latest version of
rust-rust-decimal, 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.
Fabian Grünbichler <[email protected]> (supplier of updated 
rust-rust-decimal 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: SHA512

Format: 1.8
Date: Mon, 29 Dec 2025 20:58:37 +0100
Source: rust-rust-decimal
Architecture: source
Version: 1.39.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers 
<[email protected]>
Changed-By: Fabian Grünbichler <[email protected]>
Closes: 1124260
Changes:
 rust-rust-decimal (1.39.0-3) unstable; urgency=medium
 .
   * Team upload.
   * Package rust_decimal 1.39.0 from crates.io using debcargo 2.7.11
   * skip test case on s390x (Closes: #1124260)
Checksums-Sha1:
 83237d9ad601f73b4334dc42047e7f957972f64e 3199 rust-rust-decimal_1.39.0-3.dsc
 ace15574d08d40af59d39024d35ce8649f200871 6540 
rust-rust-decimal_1.39.0-3.debian.tar.xz
 e2818b999a84068861b43ca6edb898b09232a8ad 7937 
rust-rust-decimal_1.39.0-3_source.buildinfo
Checksums-Sha256:
 50ed95c5d3c66ccdfb3d61756e3f8e1dc82f0efd5a1d5ecbe619bb2d3daeb044 3199 
rust-rust-decimal_1.39.0-3.dsc
 fab8d9f96075cad93170d50f09267ca1bc14294f8c6425e10237179227bb7108 6540 
rust-rust-decimal_1.39.0-3.debian.tar.xz
 d322eb5a645213f7ddf8383d5fe70a89f547d6854937776423fe9d8da27daeb7 7937 
rust-rust-decimal_1.39.0-3_source.buildinfo
Files:
 eb9d6567f41faedd6fc2c5dc8d833e09 3199 rust optional 
rust-rust-decimal_1.39.0-3.dsc
 d30c3b218f9ec11d0f359ff9780cfdc1 6540 rust optional 
rust-rust-decimal_1.39.0-3.debian.tar.xz
 f51e6ebe8236a08f3cb8b88f682a76e8 7937 rust optional 
rust-rust-decimal_1.39.0-3_source.buildinfo

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

iQJVBAEBCgA/FiEEbdkGe7ToK0Amc9ppdh5TKjcTRTAFAmlS3XEhHGRlYmlhbkBm
YWJpYW4uZ3J1ZW5iaWNobGVyLmVtYWlsAAoJEHYeUyo3E0UwI8EQAJqlwcGuNr0q
TFs70g3KMZA82UxWgZlKQ6oflmGc94XEh1z1vCEBzNjkZ2HRHflQ7akfrvwyI8BK
F4+h9oT6VU10QnRgXMYERc5NjLJCp6s3HEZE6JqmJPVlDW8n4cL2SBFToQxJosH8
H44ifxjfj5N6L8e/L9wR2gIVzGcM9KC7JAz52oMGGmdi7XUMSJDQS5kB+eFF9e0W
WRIITjxBLWi8drGuYkhBUGTtNHIRR7EmT33h1pOC5TBWBCKtNpj47I2+qdsrSEHY
I9lb/A7gczPBE6wmf9s6SY6dU7slnI74O04woDyRlM/DiQ/dlrnCGbuIPkMWzo7T
Q2Nk1NAlXVQnrOKLsZxk+OHqGgtDbJl3gHvOBdmrvpiLcdrFcyrr181WugCDs3WR
c09P0wJgJca95OP2UC0UnWsn0J2uNdCrDdhYFrKQMS9zadKheP1RVK7NYQhXexO5
7wtaitKZ3e/Z7hHF8+6hl2jXue/RPWbML5yerPa2WfUrJyRM2peMKHBJXRYPestY
666kBusZyoS0c6M0LqhCRKZ74/LTQQHPq6QnzPy6Wrev+0wy5uiI825gYv11NRUl
7HtPOH98YvVPuub0GXYPKY0jcM4+LradPwiMTViftClORwyLZLW3vEiR5FE96ZEh
ugptEO50tm8oP+1UFROc21TO+sZ2os/r
=/ftS
-----END PGP SIGNATURE-----

Attachment: pgpkS1gtNuD1L.pgp
Description: PGP signature


--- End Message ---

Reply via email to