Your message dated Fri, 21 Nov 2025 12:09:00 +0000
with message-id <[email protected]>
and subject line Bug#1116920: fixed in test-chuck-clojure 0.2.13-3.1
has caused the Debian Bug report #1116920,
regarding test-chuck-clojure: 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.)
--
1116920: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1116920
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:test-chuck-clojure
Version: 0.2.13-3
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:test-chuck-clojure, so that this is still
visible in the BTS web page for this package.
Thanks.
--------------------------------------------------------------------------------
[...]
debian/rules clean
dh clean --with javahelper --with maven_repo_helper
jh_clean
Duplicate specification "u=s" for option "u"
debian/rules override_dh_clean
make[1]: Entering directory '/<<PKGBUILDDIR>>'
rm -f debian/maven-repo
rm -Rf target
rm -f debian/pom.xml
dh_clean
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
debian/rules binary
dh binary --with javahelper --with maven_repo_helper
dh_update_autotools_config
dh_autoreconf
debian/rules override_dh_auto_configure
make[1]: Entering directory '/<<PKGBUILDDIR>>'
cd debian && ln -sf /usr/share/maven-repo .
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
jh_linkjars
debian/rules override_dh_auto_build
make[1]: Entering directory '/<<PKGBUILDDIR>>'
lein pom debian/pom.xml
Wrote /<<PKGBUILDDIR>>/debian/pom.xml
lein jar
Cannot access central (https://repo1.maven.org/maven2/) in offline mode and the
artifact instaparse:instaparse:jar:debian has not been downloaded from it
before.
Cannot access clojars (https://repo.clojars.org/) in offline mode and the
artifact instaparse:instaparse:jar:debian has not been downloaded from it
before.
This could be due to a typo in :dependencies, file system permissions, or
network issues.
If you are behind a proxy, try setting the 'http_proxy' environment variable.
make[1]: *** [debian/rules:18: override_dh_auto_build] Error 1
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
make: *** [debian/rules:11: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
--------------------------------------------------------------------------------
--- End Message ---
--- Begin Message ---
Source: test-chuck-clojure
Source-Version: 0.2.13-3.1
Done: Adrian Bunk <[email protected]>
We believe that the bug you reported is fixed in the latest version of
test-chuck-clojure, 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.
Adrian Bunk <[email protected]> (supplier of updated test-chuck-clojure 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, 19 Nov 2025 22:37:00 +0200
Source: test-chuck-clojure
Architecture: source
Version: 0.2.13-3.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Clojure Maintainers <[email protected]>
Changed-By: Adrian Bunk <[email protected]>
Closes: 1116920
Changes:
test-chuck-clojure (0.2.13-3.1) unstable; urgency=medium
.
* Non-maintainer upload.
* Apply patch from Santiago Vila to fix FTBFS with the nocheck
build profile. (Closes: #1116920)
Checksums-Sha1:
374b7e86ff6dff9a2e3061732cd5112d5a5b03c7 2397 test-chuck-clojure_0.2.13-3.1.dsc
f08ce64082dceed6e8c2c157e77fe66aa6b3c67a 7080
test-chuck-clojure_0.2.13-3.1.debian.tar.xz
Checksums-Sha256:
5521ba81d73ed4d528248be1cd0c3e70d0de1b46043c61217a74b0541f3ddb65 2397
test-chuck-clojure_0.2.13-3.1.dsc
526af021f07a54b0d3ff200ed9560e702730e15690f6003c783c65b7296e144f 7080
test-chuck-clojure_0.2.13-3.1.debian.tar.xz
Files:
f4893e915b04163beea00a75541044e9 2397 java optional
test-chuck-clojure_0.2.13-3.1.dsc
7de37a57d29f79e4cfaa43506739b801 7080 java optional
test-chuck-clojure_0.2.13-3.1.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmkeVSYACgkQiNJCh6LY
mLGz4A/+N2Cl+n7WBzYLkU9eZiVNfLHiUzBFDLPLRok0tgwn54ONgjWjMEm13H7l
Lez0Hd01ZmU5IOcgXPU4Tr3KT9eil2JLXEgtO24PmMo98d3rHDM3rQY8I6PXe7QF
0ACcFG45S0HTKqOY0HCcFJVJH3r6DmfNuDrh7Cy4WdlRFHpnClSyeUQLlsgZord9
zh8spLn7WXQPb+LQNQhdUATNlVTyK61x2fVNe+SJzmKzz9U5w1c/lJkXByU/Cvsa
sbFV/2/3yJYFeMwWCaNKXiIPOepGDSgbCMvLVAJPUC2S+reJEUdMf4pFxN76Pswi
AChZenEbjT9EturfazEbMvk54a4hkF70x1GPAGTdJwBtSXvwoVQf5Xi+uSZTGjY5
PTao0Nho2P1HyhxFTl2Vh8LEY0YjkZvePrclwHPLF4v4/R1IY2t8iC9kzza2M2qR
IBZdu+2ociub262ZW3zvpEd6HmEPrfG0ruA4tKL3WjIqVn0ex5K0rl5ET3mdLpr3
tmOmiJSdLced0iJVHHEJFlnAs3vLYn/8XizGikdahpizrdbemciy8z6BqL5LR0l/
Iu8Snsq2EPeif0tXn0UQln4fHBgK0tVH/slBW783P7/z06nnatpiBtw50PEWRnoi
5jJDH66uIjJ/SUVAI38j67k13rRPuvSE4hKTFwgU5KI6BudAsnA=
=4dRo
-----END PGP SIGNATURE-----
pgpJbDJ8YVhcG.pgp
Description: PGP signature
--- End Message ---
