Your message dated Fri, 03 Jul 2026 15:55:07 +0000
with message-id <[email protected]>
and subject line Bug#1139198: fixed in rdma-core 63.0-2
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-2
Done: Benjamin Drung <[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.
Benjamin Drung <[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: Fri, 03 Jul 2026 17:26:47 +0200
Source: rdma-core
Built-For-Profiles: derivative.ubuntu noudeb
Architecture: source
Version: 63.0-2
Distribution: unstable
Urgency: medium
Maintainer: Benjamin Drung <[email protected]>
Changed-By: Benjamin Drung <[email protected]>
Closes: 1139198 1140611
Changes:
rdma-core (63.0-2) unstable; urgency=medium
.
[ Andreas Tille ]
* Migrate packaging repository to Debian team on Salsa
* d/watch: version=5
.
[ Benjamin Drung ]
* librdmacm/preload.c: fix duplicate LFS symbols definitions
(Closes: #1139198, #1140611)
Checksums-Sha1:
c8bec8b302075ff166fe56f4793bab6322cf71dc 3245 rdma-core_63.0-2.dsc
23ba495b05244158a1ba6ffd38b3ecb7893c2fff 25796 rdma-core_63.0-2.debian.tar.xz
35b6feecf57f5fb9d7a0cf3bbb6de7509020b7f1 10449
rdma-core_63.0-2_source.buildinfo
Checksums-Sha256:
aed35f1b49d7422fc98ff15ce5756c015f05ff3647707cc3ff38702313eb2420 3245
rdma-core_63.0-2.dsc
1ae9959e68ef44b4dec4ed3d008c7321a7b93fec1ea49a50a9bf1b66a9f647cd 25796
rdma-core_63.0-2.debian.tar.xz
48d7c449d558df182d734c76ccd3b8275ba62f2c8dd152a0ac1a09c90d5a1112 10449
rdma-core_63.0-2_source.buildinfo
Files:
1385e3dadb8740b2e6d211874962602e 3245 net optional rdma-core_63.0-2.dsc
d75490c199118896fdc356756f9deea0 25796 net optional
rdma-core_63.0-2.debian.tar.xz
1d01717bec6bb2c2ee2fdfa55ba2c272 10449 net optional
rdma-core_63.0-2_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEpi0s+9ULm1vzYNVLFZ61xO/Id0wFAmpH1dcACgkQFZ61xO/I
d0xx1w/7B1I3wa9ha7WoCNd20BI455rSzgRtIFnCZwyWDq4kVKNg+9kAIq4b9v54
tQzKKzaNK5ghpHixm9/gL3u9Y5S+Ftlpl5oLf0u+XytX1aM60mxOO+F2fbGJlx7g
aC1BnCA3Urt4nAaUYDvjyt3Fs+T2uVGK73ol+tkQQpBlV520mspS3qxLcGtB0gvl
1HKA4ahNrHl84+5JTyoUwemMySUXfY1YG78aGjA8zJUYurePV4UNnfP0O/2qG4nD
ptV9OiqqzwOYCwcq0EOn82vBw2lBBtJ0HfrpRC1m/9aEQKUZJIeEudr/5M7cBI58
Ax4uIb1dJjjhcP0/70gF+6jzVVlpqs3IUYCOCgkB79SRzKvCrh+gsrF4MthPZakb
WtRTrRWpsFFZz+AXUgNaKdRYeIh+SMGOzgtyqr6FMQ09e8UfhsdZOMcvqiOzqpio
pX5s8whJQXewW+sFaK/pvySzvLlpCoWmdHx5SeSyQX7jRoHNH4+gWFNC2C0U3DHm
AwdhiXQgHNVhgwflK2MBuZfLHDnv7cFSuhE2PSQ4MgYrIYatEQJSt6e4+l36uwFV
Prj5AzNaHOzWFKkV46EALasSiVj0lNv0WWmgSoO6S0azRlObwFzwPYXEgNebRsQ8
0tp44ReGKVRo7FEaGT8mC10z0GKbjqzj4MQN8MJ6Q8f1h5tt1X4=
=BX6s
-----END PGP SIGNATURE-----
pgpitI8ZBjg3g.pgp
Description: PGP signature
--- End Message ---
