Your message dated Fri, 26 Jun 2026 20:37:19 +0000
with message-id <[email protected]>
and subject line Bug#1139198: fixed in rdma-core 63.0-1.1
has caused the Debian Bug report #1139198,
regarding src:rdma-core: 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.)


-- 
1139198: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1139198
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: rdma-core
Version: 61.0-2
Severity: serious
Control: close -1 63.0-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:rdma-core 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=rdma-core

Current text from [2]:
Migration status for rdma-core (61.0-2 to 63.0-1): BLOCKED: Maybe temporary, 
maybe blocked but Britney is missing information (check below)
Issues preventing migration:
∙ ∙ Missing build on armhf
∙ ∙ Lintian check waiting for test results on armhf - info
∙ ∙ Reproducibility check deferred on armhf: missing builds - info
Additional info (not blocking):
∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rdma-core.html
∙ ∙ Not reproduced on amd64 (not a regression): libibmad-dev, libibnetdisc-dev, 
libibumad-dev, libibverbs-dev, librdmacm-dev
∙ ∙ Not reproduced on arm64 (not a regression): libibmad-dev, libibnetdisc-dev, 
libibumad-dev, libibverbs-dev, librdmacm-dev
∙ ∙ Not reproduced on i386 (not a regression): libibmad-dev, libibnetdisc-dev, 
libibumad-dev, libibverbs-dev, librdmacm-dev
∙ ∙ 31 days old (needed 5 days)

--- End Message ---
--- Begin Message ---
Source: rdma-core
Source-Version: 63.0-1.1
Done: Sebastian Ramacher <[email protected]>

We believe that the bug you reported is fixed in the latest version of
rdma-core, 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.
Sebastian Ramacher <[email protected]> (supplier of updated rdma-core 
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: Wed, 24 Jun 2026 22:02:48 +0200
Source: rdma-core
Architecture: source
Version: 63.0-1.1
Distribution: unstable
Urgency: medium
Maintainer: Benjamin Drung <[email protected]>
Changed-By: Sebastian Ramacher <[email protected]>
Closes: 1139198 1140611
Changes:
 rdma-core (63.0-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload
 .
   [ Sascha Steinbiss ]
   * Fix duplicate symbols for fcntl64/sendfile64 when building for ARM
     with _TIME_BITS=64 (Closes: #1139198, #1140611).
Checksums-Sha1:
 546a31799793bb277dd091f84a8f0a1ebb6e87e1 2761 rdma-core_63.0-1.1.dsc
 53b98eacabf503d47d6f4797adaecf7f62cbaec4 25516 rdma-core_63.0-1.1.debian.tar.xz
 e8750622af2b25bc5438001765ed2e2d59b9e3a9 7935 
rdma-core_63.0-1.1_source.buildinfo
Checksums-Sha256:
 a95dbb42f0e4feb858e41e8187cd23594b15d88c48642b0e2b88f415d7ed5053 2761 
rdma-core_63.0-1.1.dsc
 5672d2a3b6d011cdfd9c6f47b4dbbc1dd2fdee1d543f5b91b1d9ed7f7f03b807 25516 
rdma-core_63.0-1.1.debian.tar.xz
 3c528e1921f0a486d79f8fbbdebea05ccfa60183016a5425b67390d2faae68f3 7935 
rdma-core_63.0-1.1_source.buildinfo
Files:
 560b836a375a2a91eb447d9d529f515a 2761 net optional rdma-core_63.0-1.1.dsc
 76b3d474ef0f7822f1d9914ec90bfe90 25516 net optional 
rdma-core_63.0-1.1.debian.tar.xz
 a91a8671ad559ff44a92c2ef10520206 7935 net optional 
rdma-core_63.0-1.1_source.buildinfo


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

wr0EARYKAG8Fgmo8OOYJECGTazZgD82JRxQAAAAAAB4AIHNhbHRAbm90YXRpb25z
LnNlcXVvaWEtcGdwLm9yZ+i/CbgIQMk/vBlkxUTD4TcexgM4xXqbKWiFkDBAWEBC
FiEEQmJ+hB2ZZ9qD4fqQIZNrNmAPzYkAALdAAP9hT6sDZOM1PFzoTchzwEQkiNCx
x0/CjiFe2d04lHBLxgEA7W2a5BCgfJEzIHNX/XiUHMUGvlum1jgx449EeQ8HUQM=
=KXX7
-----END PGP SIGNATURE-----

Attachment: pgp7ylzHM91R1.pgp
Description: PGP signature


--- End Message ---

Reply via email to