Source: guacamole-client Version: 0.8.3-1.2 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20160728 qa-ftbfs Justification: FTBFS on amd64
Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/«PKGBUILDDIR»' > dh_auto_build -- install > /usr/lib/jvm/default-java/bin/java -noverify -cp > /usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.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 install -DskipTests > -Dnotimestamp=true -Dlocale=en_US > [INFO] Scanning for projects... > [INFO] > ------------------------------------------------------------------------ > [INFO] Reactor Build Order: > [INFO] > [INFO] guacamole-common > [INFO] guacamole-ext > [INFO] guacamole-common-js > [INFO] guacamole > [INFO] guacamole-client > [INFO] > > [INFO] > ------------------------------------------------------------------------ > [INFO] Building guacamole-common 0.8.0 > [INFO] > ------------------------------------------------------------------------ > [WARNING] The POM for javax.servlet:servlet-api:jar:debian is missing, no > dependency information available > [INFO] > ------------------------------------------------------------------------ > [INFO] Reactor Summary: > [INFO] > [INFO] guacamole-common ................................... FAILURE [ 0.142 > s] > [INFO] guacamole-ext ...................................... SKIPPED > [INFO] guacamole-common-js ................................ SKIPPED > [INFO] guacamole .......................................... SKIPPED > [INFO] guacamole-client ................................... SKIPPED > [INFO] > ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] > ------------------------------------------------------------------------ > [INFO] Total time: 0.281 s > [INFO] Finished at: 2016-07-28T10:36:20+00:00 > [INFO] Final Memory: 7M/153M > [INFO] > ------------------------------------------------------------------------ > [ERROR] Failed to execute goal on project guacamole-common: Could not resolve > dependencies for project org.glyptodon.guacamole:guacamole-common:jar:0.8.0: > Cannot access central (https://repo.maven.apache.org/maven2) in offline mode > and the artifact javax.servlet:servlet-api: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:/usr/lib/jvm/default-java/lib/tools.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 install -DskipTests > -Dnotimestamp=true -Dlocale=en_US returned exit code 1 > make[1]: *** [override_dh_auto_build] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2016/07/28/guacamole-client_0.8.3-1.2_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.
