Your message dated Thu, 5 Feb 2026 19:56:40 +0100
with message-id <[email protected]>
and subject line Re: Bug#1125508 closed by Debian FTP Masters
<[email protected]> (reply to Rob Browning
<[email protected]>) (Bug#1125508: fixed in guile-3.0 3.0.11-2)
has caused the Debian Bug report #1126579,
regarding guile-3.0: 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.)
--
1126579: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1126579
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 ---
Version: 3.0.11-2
On 2/3/26 22:33, Debian Bug Tracking System wrote:
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)
The changelog closed the original (and closed) bug instead of this
cloned version.
Paul
OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
