Package: src:libgoby-java
Version: 3.3.1+dfsg2-11
Severity: serious
Tags: ftbfs trixie sid
User: [email protected]
Usertags: unshare

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:

--------------------------------------------------------------------------------
[...]
[ERROR] Failed to execute goal on project goby-io: Could not resolve 
dependencies for project org.campagnelab.goby:goby-io:jar:3.3.1
[ERROR] dependency: org.sharegov:mjson:jar:debian (compile)
[ERROR]         Cannot access central (https://repo.maven.apache.org/maven2) in 
offline mode and the artifact org.sharegov:mjson: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
[ERROR] 
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn <args> -rf :goby-io
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=/<<BUILDDIR>>/libgoby-java-3.3.1\+dfsg2 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml 
-Ddebian.dir=/<<BUILDDIR>>/libgoby-java-3.3.1\+dfsg2/debian 
-Dmaven.repo.local=/<<BUILDDIR>>/libgoby-java-3.3.1\+dfsg2/debian/maven-repo 
--batch-mode package -DskipTests -Dnotimestamp=true -Dlocale=en_US returned 
exit code 1
make: *** [debian/rules:6: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
--------------------------------------------------------------------------------

The above is just how the build ends and not necessarily the most relevant part.
If required, the full build log is available here:

https://people.debian.org/~sanvila/build-logs/202412/

Note: You can reproduce this easily by trying to build the package using
sbuild unshare backend.

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 affects, so that this is still visible in the BTS web
page for this package.

Thanks.

Reply via email to