Your message dated Wed, 01 Oct 2025 10:26:28 +0000
with message-id <[email protected]>
and subject line Bug#1116909: fixed in sccache 0.10.0-10
has caused the Debian Bug report #1116909,
regarding sccache: FTBFS with the nocheck build profile
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.)
--
1116909: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1116909
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:sccache
Version: 0.10.0-9
Severity: important
Tags: forky sid ftbfs
User: [email protected]
Usertags: ftbfs-nocheck-profile
Dear maintainer:
During a rebuild of all packages in unstable using the nocheck build profile,
your package failed to build.
Below you will find how the build ends (probably the most relevant part,
but not necessarily). If required, the full build log is available here:
https://people.debian.org/~sanvila/build-logs/202509/
A wiki page discussing how to reproduce bugs in this category and
possible solutions is available here:
https://wiki.debian.org/qa.debian.org/FTBFS/Nocheck
(It's a wiki, so you are welcome to contribute)
[ Note: This is RC, but I will wait at least two weeks before raising
the severities, there are a lot of gcc-15 and CMake 4 bugs open now ].
About the archive rebuild: The build was made on virtual machines from AWS,
using sbuild and a reduced chroot with only build-essential packages.
If you could not reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.
If this is really a bug in one of the build-depends, please use
reassign and add an affects on src:sccache, so that this is still
visible in the BTS web page for this package.
Thanks.
--------------------------------------------------------------------------------
[...]
debian/rules clean
dh clean
dh_auto_clean --buildsystem=rust
/usr/share/dh-rust/bin/cargo clean
debian cargo wrapper: options, profiles, parallel, lto: ['parallel=2',
'nocheck'] ['nocheck'] ['-j2'] 0
debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu,
x86_64-linux-gnu
debian cargo wrapper: running subprocess (['env', 'RUST_BACKTRACE=1',
'/usr/bin/cargo', 'clean', '--verbose', '--verbose'],) {'check': True}
Removed 0 files
dh_clean -XCargo.toml.orig
debian/rules binary
dh binary
dh_update_autotools_config
dh_autoreconf
dh_auto_configure --buildsystem=rust
/usr/share/dh-rust/bin/cargo prepare-debian debian/cargo_registry
debian cargo wrapper: options, profiles, parallel, lto: ['parallel=2',
'nocheck'] ['nocheck'] ['-j2'] 0
debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu,
x86_64-linux-gnu
debian cargo wrapper: linking /usr/share/cargo/registry/* into
/<<PKGBUILDDIR>>/debian/cargo_registry/
cargo update
error: no matching package named `assert_cmd` found
location searched: directory source `/<<PKGBUILDDIR>>/debian/cargo_registry`
(which is replacing registry `crates-io`)
required by package `sccache v0.10.0 (/<<PKGBUILDDIR>>)`
dh_auto_configure: error: cargo update returned exit code 101
make: *** [debian/rules:36: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
--------------------------------------------------------------------------------
--- End Message ---
--- Begin Message ---
Source: sccache
Source-Version: 0.10.0-10
Done: Jonas Smedegaard <[email protected]>
We believe that the bug you reported is fixed in the latest version of
sccache, 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.
Jonas Smedegaard <[email protected]> (supplier of updated sccache 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, 01 Oct 2025 10:51:49 +0200
Source: sccache
Architecture: source
Version: 0.10.0-10
Distribution: unstable
Urgency: medium
Maintainer: Jonas Smedegaard <[email protected]>
Changed-By: Jonas Smedegaard <[email protected]>
Closes: 1116909
Changes:
sccache (0.10.0-10) unstable; urgency=medium
.
* drop patch 2001_assert_cmd,
obsoleted by Debian packaging changes
* declare build-dependencies unconditionally,
i.e. drop broken nocheck annotations;
closes: bug#1116909, thanks to Helmut Grohne
Checksums-Sha1:
2c8ba7f5b5f04d1f0f9d86272581b18ef0ad48dc 4821 sccache_0.10.0-10.dsc
8b9bd5da5a68d6e250b184da1669d710e9bfd784 16908 sccache_0.10.0-10.debian.tar.xz
8b8ab2e1b6821f76cd978da44ed40582bb7f6a86 25912
sccache_0.10.0-10_amd64.buildinfo
Checksums-Sha256:
2e77646b2d0ed59c296deec9f76f4582a90af6ba9c941bb2a5e41c41fca7a4d8 4821
sccache_0.10.0-10.dsc
8e3b270a1bae2697581a6e04f916d7029550314a83d30577270869d602e021ec 16908
sccache_0.10.0-10.debian.tar.xz
982c77135c8b7eb1bc1bcd71cb772e5a46a779fcac2281769441706a63564d9e 25912
sccache_0.10.0-10_amd64.buildinfo
Files:
e250af52b57737f1fea52ca7e0ba9e68 4821 devel optional sccache_0.10.0-10.dsc
d06dbcabcc5b589503c7c095ca1cd55a 16908 devel optional
sccache_0.10.0-10.debian.tar.xz
2e909759ad70cd783df23d0c5be3efa6 25912 devel optional
sccache_0.10.0-10_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
wsG7BAEBCgBvBYJo3PFACRAsfDFGwaABIUcUAAAAAAAeACBzYWx0QG5vdGF0aW9u
cy5zZXF1b2lhLXBncC5vcmd4rWotwuj1hsglUG71kmA2RwUBMKhdhihW4+pJAoXJ
PhYhBJ/j6cNmkaaf9TzGhCx8MUbBoAEhAADMcg//Tn3b8QtvDvEUOnhZ5jQjdvSS
QaCCfU7waIvOzerFmO5dwqkmgFT9mEuBNCNr1ric9EBOoYFQvlRG9wTJJMvK9XyD
XOa5I8zPNMdMIlgFxDY8mxPjutxXoSQu/o/NyOrJX8qACjAV56glfdz2VwVIV8oN
nm/sTi1sIo7YMFuB+NNvhrbTyxj2oskm5c3sx/fKOViTWnhnOsyuw2AFScia8IOw
D5hXSJZzh9AjO7itW5bbDN2st2gll9NAAYtV+aWwHApSTY3kTubuSkD2/4ojPx3A
pIL26gHFboOn0UX2XBMjS2f5yRsKtb5Obyqtf77tSp3qHhoIbI+Vt7D0OfAYlIVy
/rxvW7trkMo4E7w1BYzcba/w8soKnGbBS8qANd/7rF9MQ+nxfMlzJK6NkVf/P7QI
k2xOVZwcsmfGApsQr+qTEW+BnQb03j+ohZACHA1MVZK2mFxnZgy9Uomu86HRvgvc
2bQZjrtdexvb6cN8jsId21aoVEeMHZTkv70aLnVF8S8804G4tRffuVb1O3Mt9qv8
TGZF/RwoOj0gyCYPn7Xk0Ey01PsceUMKcnqbRKpOEhxTwQHja4NLEw1tiXB/nn0p
/PYrdLAsJLL6X5Ziynl3ncwIjCGbFE/8YZ7D6MNPrOjKadYmqa/Ms1n4vcYBTZdc
qRx+quF/Ull7dBzTdwo=
=bk7E
-----END PGP SIGNATURE-----
pgp_BxsPBid6T.pgp
Description: PGP signature
--- End Message ---
