Your message dated Mon, 2 Feb 2026 16:00:46 +0100
with message-id <[email protected]>
and subject line Re: Bug#1014259: sscg: ftbfs on riscv64: (create_csr_test
TIMEOUT 30.10s killed by signal 15 SIGTERM)
has caused the Debian Bug report #1014259,
regarding sscg: ftbfs on riscv64: (create_csr_test TIMEOUT 30.10s killed by
signal 15 SIGTERM)
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.)
--
1014259: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014259
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: sscg
Version: 3.0.2-1
Severity: wishlist
Tags: ftbfs, confirmed
User: [email protected]
Usertags: riscv64
X-Debbugs-Cc: [email protected]
Dear sscg Maintainer,
The sscg package has a ftbfs issue on riscv64 arch, the full buildd
log is here:
https://buildd.debian.org/status/fetch.php?pkg=sscg&arch=riscv64&ver=3.0.2-1%2Bb1&stamp=1652893331&raw=0
But I build the package successfully on my locally Unmatched board
without any modify. So I want to give back to the package and
confirm it.
But I noticed the package version failed on udd page is 3.0.2-1+b1,
and I can't get the source code for that version.
So I will close this bug if this is false possitive and need me to
do more test please let me know.
Bo
--
Best Regards,
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 3.0.8-1
Martin Pitt [2022-07-12 8:55 +0200]:
> Control: forwarded -1 https://github.com/sgallagher/sscg/pull/60
> Control: tag -1 upstream pending
>
> Hello Bo,
>
> Bo YU [2022-07-03 10:33 +0800]:
> > The sscg package has a ftbfs issue on riscv64 arch, the full buildd
> > log is here:
> >
> > https://buildd.debian.org/status/fetch.php?pkg=sscg&arch=riscv64&ver=3.0.2-1%2Bb1&stamp=1652893331&raw=0
>
> Thanks for your report! I sent an upstream PR to increase the test timeout. As
> a short-term workaround I gave back the package build, and it succeeded:
>
> https://buildd.debian.org/status/fetch.php?pkg=sscg&arch=riscv64&ver=3.0.2-1%2Bb1&stamp=1657605907&raw=0
The recent builds are fine:
https://buildd.debian.org/status/logs.php?pkg=sscg&arch=riscv64
I just forgot to close this bug via changelog in 3.0.8-1.
Thanks,
Martin
--- End Message ---