Source: libquartz2-java
Version: 2.3.2-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230113 ftbfs-bookworm

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
>  debian/rules binary
> dh binary --with javahelper
>    dh_update_autotools_config
>    dh_autoreconf
>    dh_auto_configure
>       mh_patchpoms -plibquartz2-java --debian-build --keep-pom-version 
> --maven-repo=/<<PKGBUILDDIR>>/debian/maven-repo
>    jh_linkjars
>    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 
> -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] Reactor Build Order:
> [INFO] 
> [INFO] quartz-parent                                                      
> [pom]
> [INFO] quartz-core                                                        
> [jar]
> [INFO] quartz-commonj                                                     
> [jar]
> [INFO] quartz-jobs                                                        
> [jar]
> [INFO] quartz-plugins                                                     
> [jar]
> [INFO] quartz                                                             
> [jar]
> [INFO] 
> [INFO] -----------------< org.quartz-scheduler:quartz-parent 
> >-----------------
> [INFO] Building quartz-parent 2.3.2                                       
> [1/6]
> [INFO] --------------------------------[ pom 
> ]---------------------------------
> [INFO] 
> [INFO] -------------< org.quartz-scheduler.internal:quartz-core 
> >--------------
> [INFO] Building quartz-core 2.3.2                                         
> [2/6]
> [INFO] --------------------------------[ jar 
> ]---------------------------------
> [WARNING] The artifact 
> org.apache.maven.plugins:maven-resources-plugin:jar:2.6 has been relocated to 
> org.apache.maven.plugins:maven-resources-plugin:jar:3.3.0
> [WARNING] The POM for log4j:log4j:jar:1.2.x is missing, no dependency 
> information available
> [WARNING] The artifact org.hamcrest:hamcrest-library:jar:debian has been 
> relocated to org.hamcrest:hamcrest:jar:debian
> [INFO] 
> ------------------------------------------------------------------------
> [INFO] Reactor Summary for quartz-parent 2.3.2:
> [INFO] 
> [INFO] quartz-parent ...................................... SUCCESS [  0.001 
> s]
> [INFO] quartz-core ........................................ FAILURE [  0.074 
> s]
> [INFO] quartz-commonj ..................................... SKIPPED
> [INFO] quartz-jobs ........................................ SKIPPED
> [INFO] quartz-plugins ..................................... SKIPPED
> [INFO] quartz ............................................. SKIPPED
> [INFO] 
> ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] 
> ------------------------------------------------------------------------
> [INFO] Total time:  0.215 s
> [INFO] Finished at: 2023-01-13T20:30:37Z
> [INFO] 
> ------------------------------------------------------------------------
> [ERROR] Failed to execute goal on project quartz-core: Could not resolve 
> dependencies for project org.quartz-scheduler.internal:quartz-core:jar:2.3.2: 
> Cannot access terracotta-snapshots 
> (http://www.terracotta.org/download/reflector/snapshots) in offline mode and 
> the artifact log4j:log4j:jar:1.2.x has not been downloaded from it before. -> 
> [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 :quartz-core
> 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 
> -DskipTests -Dnotimestamp=true -Dlocale=en_US returned exit code 1
> make: *** [debian/rules:6: binary] Error 25


The full build log is available from:
http://qa-logs.debian.net/2023/01/13/libquartz2-java_2.3.2-3_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230113;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20230113&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.

Reply via email to