Your message dated Tue, 03 Feb 2026 21:30:19 +0000
with message-id <[email protected]>
and subject line Bug#1125508: fixed in guile-3.0 3.0.11-2
has caused the Debian Bug report #1125508,
regarding src:guile-3.0: fails to migrate to testing for too long: segfaults on
riscv64
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.)
--
1125508: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1125508
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: guile-3.0
Version: 3.0.10+really3.0.10-6
Severity: serious
Control: close -1 3.0.11-1
Tags: sid forky
User: [email protected]
Usertags: out-of-sync
User: [email protected]
Usertag: riscv64
X-Debbugs-CC: [email protected]
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:guile-3.0 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. I noted that in both
regressions there's a segfault reported, hence the riscv64 porters in CC.
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=guile-3.0
Current text from [2]:
Migration status for guile-3.0 (3.0.10+really3.0.10-6 to 3.0.11-1):
BLOCKED: Rejected/violates migration policy/introduces a regression
Issues preventing migration:
∙ ∙ Autopkgtest for guile-3.0/3.0.11-1: amd64: Pass, arm64: Pass, i386:
Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
∙ ∙ Autopkgtest for guile-fibers/1.4.2-2: amd64: Pass, arm64: Pass,
i386: Pass, ppc64el: Pass, riscv64: Regression ♻ (reference ♻), s390x: Pass
∙ ∙ Autopkgtest for shepherd/1.0.9-2: amd64: Pass, arm64: Pass, i386:
Pass, ppc64el: Pass, riscv64: Regression ♻ (reference ♻), s390x: Pass
Additional info (not blocking):
∙ ∙ Piuparts tested OK -
https://piuparts.debian.org/sid/source/g/guile-3.0.html
∙ ∙ Reproducible on amd64 - info ♻ ∙ ∙ Reproducible on arm64 - info ♻ ∙
∙ 33 days old (needed 5 days)
OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: guile-3.0
Source-Version: 3.0.11-2
Done: Rob Browning <[email protected]>
We believe that the bug you reported is fixed in the latest version of
guile-3.0, 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.
Rob Browning <[email protected]> (supplier of updated guile-3.0 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: Tue, 03 Feb 2026 13:30:07 -0600
Source: guile-3.0
Architecture: source
Version: 3.0.11-2
Distribution: unstable
Urgency: medium
Maintainer: Rob Browning <[email protected]>
Changed-By: Rob Browning <[email protected]>
Closes: 1125508
Changes:
guile-3.0 (3.0.11-2) unstable; urgency=medium
.
* debian/rules: disable the riscv64 JIT for now; risv64 support was
added in 3.0.11, but it's causing (at least) the guile-fibers tests to
segfault. Thanks to Paul Gevers for reporting the problem.
(Closes: 1125508)
Checksums-Sha1:
9c5d41496fabfb6f25c8bbd023fe33d1b1994801 2191 guile-3.0_3.0.11-2.dsc
0773beb29a344f3f61dd30a4f9315a929dec7e98 37728 guile-3.0_3.0.11-2.debian.tar.xz
1f8c7006099573d017754855452ce67a0f556e9e 7921
guile-3.0_3.0.11-2_amd64.buildinfo
Checksums-Sha256:
44e9a1ad54301ba2fa0a8639c7f9ab86baccd44dac3b8884e75bad317d8ea9d0 2191
guile-3.0_3.0.11-2.dsc
e8cd3c211a54c9aea95512fbf7aeb2dafe708f85a05f3d1e16c63fdbc49c6272 37728
guile-3.0_3.0.11-2.debian.tar.xz
36f4e4c290446751866ad3d12ee8a404166583c4518b53826a97bf4b165420a6 7921
guile-3.0_3.0.11-2_amd64.buildinfo
Files:
46d5f2904ca4ca33b524db0247331196 2191 interpreters optional
guile-3.0_3.0.11-2.dsc
50bc3424998925ac1ccf9221b21643f4 37728 interpreters optional
guile-3.0_3.0.11-2.debian.tar.xz
0c25796aa3200c3c65ccb2e621b343d9 7921 interpreters optional
guile-3.0_3.0.11-2_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJJBAEBCgAzFiEEPTFSABe5ruOuhW+97vEWxVpaQvEFAmmCZMYVHHJsYkBkZWZh
dWx0dmFsdWUub3JnAAoJEO7xFsVaWkLxPkYP/A6+sjk+qF3x+3BLvIXsHQqRjWRu
Lhx63JPd3xBTaN2pWE4IejCZFbcCdrc+2taXU00ha+tTgyz9hAeOJmVqJQqfIRmg
gKn+9/gQjcAA+dBFzNUb0umiBiXJjEq419cTg8RdmCR4onlfcXnx3XYylhb8Z8zf
ruuvjr/4QQqpwxX3+G+fKSY8+tR8BUL4D75Ejv6A/Z4mdRVbx1n9LmJuisoomEnT
oizgRQs3N1gC/jor0DXm2waXyLrg1e1XiRQrxkwnxyoTTR8TBFpUt1IKfevzSOPH
7EgnfW/c11AoYfkpOt5wwsI06kjt2zlzuWKLhh/bjm4lbb9zLdgfFo+WFnG3cfHQ
avzIAHJPL0pFH7ZHMv7ASKD4JGDkXFxlBQ335TwFoZGNtnFaJ1ghMxemXM6OvO99
N/y3595XdaOkbsW/fK6/fnXdVxDZmoQjMk0KtdTjhLyKItAnlTLylmWSCBK2ZAWk
I3+Bcdm15gwY/eUMKJGDYy31G3FqhuvMKXAhcNjXLKj+Ff6lleyal8w2SH44zDWz
PnJ93J36AaebRs5mu1RTac0Xhy/5eT/1OoYoaMy0ZlZMo2t17n6p8CFzyIqVqgQe
sh9vW5IbP1WLeJlTttRZvaaiG4aiyhLwkTI39Ftr8TiaZt0Yg7HOfx5E7rFf+kLN
GBKGMv8NSIX73Xoo
=IoSW
-----END PGP SIGNATURE-----
pgpYxjdpaZJeS.pgp
Description: PGP signature
--- End Message ---
