Your message dated Sun, 04 Oct 2026 10:05:26 +0000
with message-id <[email protected]>
and subject line Bug#1134475: fixed in nbd 1:3.27.1-4
has caused the Debian Bug report #1134475,
regarding src:nbd: 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.)


-- 
1134475: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1134475
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: nbd
Version: 1:3.26.1-6.1
Severity: serious
Control: close -1 1:3.27.1-1
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:nbd 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. Blocked packages can have impact on other packages, which makes 
preparing for the release more difficult. The situation that caused this bug 
report might even be the result of such an issue. We expect maintainers to fix 
issues that hamper the migration of their package in a timely manner. If your 
package in this situation due to another package, consider helping out.

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

Current text from [2]:
Migration status for nbd (1:3.26.1-6.1 to 1:3.27.1-1): BLOCKED: 
Rejected/violates migration policy/introduces a regression
Issues preventing migration:
∙ ∙ Updating nbd would introduce bugs in testing: #1133143
∙ ∙ Autopkgtest for dracut/110-12: amd64: Regression ♻ (reference ♻), riscv64: 
Test triggered (failure will be ignored)
∙ ∙ Autopkgtest for dracut/110-8: arm64: Regression ♻ (reference ♻), ppc64el: 
Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
∙ ∙ Autopkgtest for nbd/1:3.27.1-1: amd64: Regression ♻ (reference ♻), arm64: 
Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), riscv64: 
Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
∙ ∙ Missing build on i386
∙ ∙ Autopkgtest deferred on i386: missing arch:i386 build
∙ ∙ Lintian check waiting for test results on i386 - info
∙ ∙ Reproducibility check deferred on i386: missing builds
Additional info (not blocking):
∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nbd.html
∙ ∙ Lintian issues ignored as requested by elbrus
∙ ∙ Reproduced on amd64
∙ ∙ Reproduced on arm64
∙ ∙ Reproduced on armhf
∙ ∙ Reproduced on ppc64el
∙ ∙ 10 days old (needed 5 days)

--- End Message ---
--- Begin Message ---
Source: nbd
Source-Version: 1:3.27.1-4
Done: Wouter Verhelst <[email protected]>

We believe that the bug you reported is fixed in the latest version of
nbd, 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.
Wouter Verhelst <[email protected]> (supplier of updated nbd 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: SHA384

Format: 1.8
Date: Sun, 04 Oct 2026 11:42:14 +0200
Source: nbd
Architecture: source
Version: 1:3.27.1-4
Distribution: unstable
Urgency: medium
Maintainer: Wouter Verhelst <[email protected]>
Changed-By: Wouter Verhelst <[email protected]>
Closes: 1134475
Changes:
 nbd (1:3.27.1-4) unstable; urgency=medium
 .
   * Cherry-pick two commits from git master to fix LFS-related test suite
     failures on 32-bit architectures; Closes: #1134475, for real
     (hopefully) this time :)
Checksums-Sha1:
 77ed26eaa4ef2beadadc9306df54acd5cb85308b 1624 nbd_3.27.1-4.dsc
 026fa9a274ce978cc8f331209580af67837db06a 144484 nbd_3.27.1-4.debian.tar.xz
 1235ee03bcd91b0215f89f710e9d39652d76f0e8 12522 nbd_3.27.1-4_source.buildinfo
Checksums-Sha256:
 63e89d453ca394dd93d77daba56dc22c82a7908d3c22345ca824a9dc42d45eab 1624 
nbd_3.27.1-4.dsc
 885c96b24578f9ccaabe6276defec17a24ee6b9ad774493efeb41db1560ee9ac 144484 
nbd_3.27.1-4.debian.tar.xz
 b549c4551400e3399222688e78aae1d86f759938dc4ec36200346bf45bce8ffb 12522 
nbd_3.27.1-4_source.buildinfo
Files:
 7ad95b1ea1fc28a45356b2162b8aa548 1624 admin optional nbd_3.27.1-4.dsc
 cb2fb48e0c51508c7b2356dd8558cbad 144484 admin optional 
nbd_3.27.1-4.debian.tar.xz
 3d5443bc6466eff608a25dc4b15c8c84 12522 admin optional 
nbd_3.27.1-4_source.buildinfo

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

iKgEARMJADAWIQQZhIYJILYM7Y0TCTdH038p5i64/wUCasIjQBIcd291dGVyQGRl
Ymlhbi5vcmcACgkQR9N/KeYuuP8eNAGA4pwvk759z0nJuKXuQ44tIkwRxLMHXYeh
pgABEcZuwQdr56HxCAdwzr2km8kRa5xeAX4terPiYxJmQYEu9jx9h5MxF/sF/sMT
RUbwLrhUzAShjdY9GM2pfgu0DQzAIwmic3c=
=BZEv
-----END PGP SIGNATURE-----

Attachment: pgpRtEYjmzG8U.pgp
Description: PGP signature


--- End Message ---

Reply via email to