Your message dated Fri, 21 Nov 2025 12:04:47 +0000
with message-id <[email protected]>
and subject line Bug#1116723: fixed in cryptacular 1.2.7-1.1
has caused the Debian Bug report #1116723,
regarding cryptacular: 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.)


-- 
1116723: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1116723
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:cryptacular
Version: 1.2.7-1
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:cryptacular, so that this is still
visible in the BTS web page for this package.

Thanks.

--------------------------------------------------------------------------------
[...]
 debian/rules clean
dh clean
   dh_auto_clean
        bash -c "for dir in \$(find . -name target -type d); do if [ -f \$(echo 
\$dir | sed -e s/target\$/pom.xml/) ]; then rm -Rf \$dir; fi done"
        mh_unpatchpoms -plibcryptacular-java
   dh_clean
 debian/rules binary
dh binary
   dh_update_autotools_config
   dh_autoreconf
   dh_auto_configure
        mh_patchpoms -plibcryptacular-java --debian-build --keep-pom-version 
--maven-repo=/<<PKGBUILDDIR>>/debian/maven-repo
   dh_auto_build
        /usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/<<PKGBUILDDIR>> 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/<<PKGBUILDDIR>>/debian/maven.properties 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/<<PKGBUILDDIR>>/debian 
-Dmaven.repo.local=/<<PKGBUILDDIR>>/debian/maven-repo --batch-mode package 
javadoc:jar javadoc:aggregate -DskipTests -Dnotimestamp=true -Dlocale=en_US
OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were 
deprecated in JDK 13 and will likely be removed in a future release.
[INFO] Scanning for projects...
[INFO] 
[INFO] --------------------< org.cryptacular:cryptacular >---------------------
[INFO] Building Cryptacular Library 1.2.7
[INFO]   from pom.xml
[INFO] --------------------------------[ jar ]---------------------------------
[WARNING] The POM for org.testng:testng:jar:debian is missing, no dependency 
information available
[INFO] 
[INFO] ------------------------------------------------------------------------
[INFO] Skipping Cryptacular Library
[INFO] This project has been banned from the build due to previous failures.
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  0.185 s
[INFO] Finished at: 2025-09-30T11:33:06Z
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project cryptacular: Could not resolve 
dependencies for project org.cryptacular:cryptacular:jar:1.2.7
[ERROR] dependency: org.testng:testng:jar:debian (test)
[ERROR]         Cannot access central (https://repo.maven.apache.org/maven2) in 
offline mode and the artifact org.testng:testng:jar:debian has not been 
downloaded from it before.
[ERROR] -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
dh_auto_build: error: /usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/<<PKGBUILDDIR>> 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/<<PKGBUILDDIR>>/debian/maven.properties 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/<<PKGBUILDDIR>>/debian 
-Dmaven.repo.local=/<<PKGBUILDDIR>>/debian/maven-repo --batch-mode package 
javadoc:jar javadoc:aggregate -DskipTests -Dnotimestamp=true -Dlocale=en_US 
returned exit code 1
make: *** [debian/rules:4: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
--------------------------------------------------------------------------------

--- End Message ---
--- Begin Message ---
Source: cryptacular
Source-Version: 1.2.7-1.1
Done: Adrian Bunk <[email protected]>

We believe that the bug you reported is fixed in the latest version of
cryptacular, 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 cryptacular 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 21:41:55 +0200
Source: cryptacular
Architecture: source
Version: 1.2.7-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 
<[email protected]>
Changed-By: Adrian Bunk <[email protected]>
Closes: 1116723
Changes:
 cryptacular (1.2.7-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Apply patch from Santiago Vila to fix FTBFS with the nocheck
     build profile. (Closes: #1116723)
Checksums-Sha1:
 1422aec717bf3d86c6d32e31afeb63e426cf9864 3778 cryptacular_1.2.7-1.1.dsc
 9fb73a4854320e652a7d1d8ca403b72541edbd13 3928 
cryptacular_1.2.7-1.1.debian.tar.xz
Checksums-Sha256:
 0a4256d5f8e0686d7c35a3a1692548915774cce013a57a6cc80d22b53d12939d 3778 
cryptacular_1.2.7-1.1.dsc
 746aafdbd836b1ed4e7ad83f95154b224d6c1d9c4b27f486c4f0a0f89cbcdf18 3928 
cryptacular_1.2.7-1.1.debian.tar.xz
Files:
 269e25dc7a9dcb7cf9604eefaaab631d 3778 java optional cryptacular_1.2.7-1.1.dsc
 69ead2c27ce645e192049581e9497f04 3928 java optional 
cryptacular_1.2.7-1.1.debian.tar.xz

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmkeSMMACgkQiNJCh6LY
mLHo3g/+MHCb19XHHpE9+VrW7ZFPCNF4UcfQrRnxHWDP3b8y3Hjs6a+OXlY6OmUb
sWvfFhKPwNLZk75gEtEUJGYhm8WQRtqaAOOH8w1BgjfgSaCTalV4tt+KEOAj+Iaj
kYP9dhKpDEi2zUG0H7h0zqWYn/r+XnGGHcdNL1WRkd2C9AhHRk+Khe7MhzzbRJvM
vrpxrmgfPHJY+76/vp6KI0WekghLVJ4nXXn/+aNqOwfBtvhhJsL1CC7fIpBjfokd
F+WSbYrt/gvJ94srX2N8IeURJrTMZPxT1Qjt+4rZRrEk/fNX4D5oXgTXwF/UuO96
QaW58W6ZOFbei81EzdJJfjfga1xShcnuGGnhQjzf/gmo0tNbRhlFuA+USgFMPfk7
6IhXbwX3Fht0SpsjCRxJ9G/4HOZlJViPtCMgNyIHTgU4KQzRqJX4BEhnLUoxj1A+
TPEKIlkhooAi8aaKzns+WjypgpYeere27fN2v0U368rkcmaH7lpyXLFHBksIH7kK
pgxNFXJPlHFUkAyB97Ohn5284MjrqFiIXuruuN1jWQEPQRjwYQBqj1pvSf+HmDF0
tlXKnqfhLeFUACaXJz+f6Eo8w70bEb5pPv+OAmzcEHMBhj2vAkWlPfcd2RbZmv6q
pdteqiM2OCCXuV46AZLZ5ZMJirb1Xd7tQ4NYEgfeBhEvSe7XLsE=
=eao1
-----END PGP SIGNATURE-----

Attachment: pgpfbdNMvaJUt.pgp
Description: PGP signature


--- End Message ---

Reply via email to