Source: openhft-chronicle-wire Version: 1.1.13-1 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20181229 ftbfs-buster
Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules build > dh build --buildsystem=maven > dh_update_autotools_config -O--buildsystem=maven > dh_auto_configure -O--buildsystem=maven > mh_patchpoms -plibopenhft-chronicle-wire-java --debian-build > --keep-pom-version --maven-repo=/<<PKGBUILDDIR>>/debian/maven-repo > dh_auto_build -O--buildsystem=maven > /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 > WARNING: An illegal reflective access operation has occurred > WARNING: Illegal reflective access by > com.google.inject.internal.cglib.core.$ReflectUtils$1 > (file:/usr/share/maven/lib/guice.jar) to method > java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain) > WARNING: Please consider reporting this to the maintainers of > com.google.inject.internal.cglib.core.$ReflectUtils$1 > WARNING: Use --illegal-access=warn to enable warnings of further illegal > reflective access operations > WARNING: All illegal access operations will be denied in a future release > [INFO] Scanning for projects... > [INFO] > [INFO] ---------------------< net.openhft:chronicle-wire > >--------------------- > [INFO] Building OpenHFT/Chronicle-Wire 1.1.13 > [INFO] -------------------------------[ bundle > ]------------------------------- > [WARNING] The POM for org.easymock:easymock:jar:debian is missing, no > dependency information available > [INFO] > ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] > ------------------------------------------------------------------------ > [INFO] Total time: 1.064 s > [INFO] Finished at: 2018-12-29T13:59:39Z > [INFO] > ------------------------------------------------------------------------ > [ERROR] Failed to execute goal on project chronicle-wire: Could not resolve > dependencies for project net.openhft:chronicle-wire:bundle:1.1.13: Cannot > access central (https://repo.maven.apache.org/maven2) in offline mode and the > artifact org.easymock:easymock:jar:debian 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 > 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 returned exit code 1 > make: *** [debian/rules:4: build] Error 1 The full build log is available from: http://aws-logs.debian.net/2018/12/29/openhft-chronicle-wire_1.1.13-1_unstable.log 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! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures.
