Source: warzone2100 Version: 3.3.0-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200926 ftbfs-bullseye
Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[4]: Entering directory '/<<PKGBUILDDIR>>/doc' > a2x -f manpage ./warzone2100.6.asciidoc > a2x -f xhtml ./quickstartguide.asciidoc > wkhtmltopdf ./quickstartguide.html ./quickstartguide.pdf > QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-user42' > Loading page (1/2) > [> ] 0% > [========> ] 14% > Warning: Blocked access to file /<<PKGBUILDDIR>>/doc/docbook-xsl.css > Warning: Blocked access to file /<<PKGBUILDDIR>>/doc/images/www.png > Warning: Blocked access to file /<<PKGBUILDDIR>>/doc/images/logo.png > Warning: Blocked access to file /<<PKGBUILDDIR>>/doc/images/interface.jpg > Warning: Blocked access to file /<<PKGBUILDDIR>>/doc/images/minimap.jpg > Warning: Blocked access to file /<<PKGBUILDDIR>>/doc/images/powerbar.jpg > Warning: Blocked access to file /<<PKGBUILDDIR>>/doc/images/oilresource.jpg > Warning: Blocked access to file /<<PKGBUILDDIR>>/doc/images/cheapweapon.png > Warning: Blocked access to file > /<<PKGBUILDDIR>>/doc/images/expensiveweapon.png > Warning: Blocked access to file /<<PKGBUILDDIR>>/doc/images/powerupgrade.png > Warning: Blocked access to file /<<PKGBUILDDIR>>/doc/images/unitordersmenu.jpg > Warning: Blocked access to file /<<PKGBUILDDIR>>/doc/images/attackrange.jpg > Warning: Blocked access to file > /<<PKGBUILDDIR>>/doc/images/retreatthreshold.jpg > Warning: Blocked access to file /<<PKGBUILDDIR>>/doc/images/firing.jpg > Warning: Blocked access to file /<<PKGBUILDDIR>>/doc/images/movement.jpg > Warning: Blocked access to file /<<PKGBUILDDIR>>/doc/images/return.jpg > Warning: Blocked access to file /<<PKGBUILDDIR>>/doc/images/recycling.jpg > Warning: Blocked access to file /<<PKGBUILDDIR>>/doc/images/commandpanel.png > Warning: Blocked access to file > /<<PKGBUILDDIR>>/doc/images/manufacture-select.jpg > Warning: Blocked access to file /<<PKGBUILDDIR>>/doc/images/manufacture.jpg > Error: Failed to load about:blank, with network status code 301 and http > status code 0 - Protocol "about" is unknown > Warning: Blocked access to file /<<PKGBUILDDIR>>/doc/images/rallypoints.jpg > Warning: Blocked access to file > /<<PKGBUILDDIR>>/doc/images/research-select.jpg > Warning: Blocked access to file /<<PKGBUILDDIR>>/doc/images/research.jpg > Warning: Blocked access to file > /<<PKGBUILDDIR>>/doc/images/building-select.jpg > Warning: Blocked access to file /<<PKGBUILDDIR>>/doc/images/building.jpg > Warning: Blocked access to file /<<PKGBUILDDIR>>/doc/images/design.jpg > Warning: Blocked access to file /<<PKGBUILDDIR>>/doc/images/design-unit.jpg > Warning: Blocked access to file /<<PKGBUILDDIR>>/doc/images/design-more.png > Warning: Blocked access to file /<<PKGBUILDDIR>>/doc/images/design-screen.jpg > Warning: Blocked access to file /<<PKGBUILDDIR>>/doc/images/design-bars.jpg > Warning: Blocked access to file > /<<PKGBUILDDIR>>/doc/images/intelligencedisplay.jpg > Warning: Blocked access to file /<<PKGBUILDDIR>>/doc/images/commander.png > Warning: Blocked access to file > /<<PKGBUILDDIR>>/doc/images/commander-panel.jpg > Warning: Blocked access to file > /<<PKGBUILDDIR>>/doc/images/commander-factory-assignment.jpg > Warning: Blocked access to file > /<<PKGBUILDDIR>>/doc/images/indirect-fire-support.jpg > Warning: Blocked access to file /<<PKGBUILDDIR>>/doc/images/sensor.png > Warning: Blocked access to file > /<<PKGBUILDDIR>>/doc/images/artillery-sensor.jpg > Warning: Blocked access to file > /<<PKGBUILDDIR>>/doc/images/artillery-far-away.jpg > Warning: Blocked access to file /<<PKGBUILDDIR>>/doc/images/cb-sensor.png > Warning: Blocked access to file /<<PKGBUILDDIR>>/doc/images/cb-sensor-vtol.png > Warning: Blocked access to file /<<PKGBUILDDIR>>/doc/images/hq.png > Warning: Blocked access to file /<<PKGBUILDDIR>>/doc/images/sensor-tower.png > Warning: Blocked access to file > /<<PKGBUILDDIR>>/doc/images/satellite-uplink.png > Warning: Blocked access to file /<<PKGBUILDDIR>>/doc/images/wss.png > Warning: Blocked access to file /<<PKGBUILDDIR>>/doc/images/transport.jpg > Warning: Blocked access to file /<<PKGBUILDDIR>>/doc/images/awaymission.jpg > Error: Failed to load about:blank, with network status code 301 and http > status code 0 - Protocol "about" is unknown > Error: Failed to load about:blank, with network status code 301 and http > status code 0 - Protocol "about" is unknown > Error: Failed to load about:blank, with network status code 301 and http > status code 0 - Protocol "about" is unknown > Error: Failed to load about:blank, with network status code 301 and http > status code 0 - Protocol "about" is unknown > Error: Failed to load about:blank, with network status code 301 and http > status code 0 - Protocol "about" is unknown > Error: Failed to load about:blank, with network status code 301 and http > status code 0 - Protocol "about" is unknown > Error: Failed to load about:blank, with network status code 301 and http > status code 0 - Protocol "about" is unknown > Error: Failed to load about:blank, with network status code 301 and http > status code 0 - Protocol "about" is unknown > Error: Failed to load about:blank, with network status code 301 and http > status code 0 - Protocol "about" is unknown > Error: Failed to load about:blank, with network status code 301 and http > status code 0 - Protocol "about" is unknown > Error: Failed to load about:blank, with network status code 301 and http > status code 0 - Protocol "about" is unknown > Error: Failed to load about:blank, with network status code 301 and http > status code 0 - Protocol "about" is unknown > Error: Failed to load about:blank, with network status code 301 and http > status code 0 - Protocol "about" is unknown > Error: Failed to load about:blank, with network status code 301 and http > status code 0 - Protocol "about" is unknown > Error: Failed to load about:blank, with network status code 301 and http > status code 0 - Protocol "about" is unknown > Error: Failed to load about:blank, with network status code 301 and http > status code 0 - Protocol "about" is unknown > Error: Failed to load about:blank, with network status code 301 and http > status code 0 - Protocol "about" is unknown > Error: Failed to load about:blank, with network status code 301 and http > status code 0 - Protocol "about" is unknown > Error: Failed to load about:blank, with network status code 301 and http > status code 0 - Protocol "about" is unknown > Error: Failed to load about:blank, with network status code 301 and http > status code 0 - Protocol "about" is unknown > Error: Failed to load about:blank, with network status code 301 and http > status code 0 - Protocol "about" is unknown > Error: Failed to load about:blank, with network status code 301 and http > status code 0 - Protocol "about" is unknown > Error: Failed to load about:blank, with network status code 301 and http > status code 0 - Protocol "about" is unknown > Error: Failed to load about:blank, with network status code 301 and http > status code 0 - Protocol "about" is unknown > Error: Failed to load about:blank, with network status code 301 and http > status code 0 - Protocol "about" is unknown > Error: Failed to load about:blank, with network status code 301 and http > status code 0 - Protocol "about" is unknown > Error: Failed to load about:blank, with network status code 301 and http > status code 0 - Protocol "about" is unknown > Error: Failed to load about:blank, with network status code 301 and http > status code 0 - Protocol "about" is unknown > Error: Failed to load about:blank, with network status code 301 and http > status code 0 - Protocol "about" is unknown > Error: Failed to load about:blank, with network status code 301 and http > status code 0 - Protocol "about" is unknown > Error: Failed to load about:blank, with network status code 301 and http > status code 0 - Protocol "about" is unknown > Error: Failed to load about:blank, with network status code 301 and http > status code 0 - Protocol "about" is unknown > Error: Failed to load about:blank, with network status code 301 and http > status code 0 - Protocol "about" is unknown > Error: Failed to load about:blank, with network status code 301 and http > status code 0 - Protocol "about" is unknown > Error: Failed to load about:blank, with network status code 301 and http > status code 0 - Protocol "about" is unknown > Error: Failed to load about:blank, with network status code 301 and http > status code 0 - Protocol "about" is unknown > Error: Failed to load about:blank, with network status code 301 and http > status code 0 - Protocol "about" is unknown > Error: Failed to load about:blank, with network status code 301 and http > status code 0 - Protocol "about" is unknown > Error: Failed to load about:blank, with network status code 301 and http > status code 0 - Protocol "about" is unknown > Error: Failed to load about:blank, with network status code 301 and http > status code 0 - Protocol "about" is unknown > Error: Failed to load about:blank, with network status code 301 and http > status code 0 - Protocol "about" is unknown > Error: Failed to load about:blank, with network status code 301 and http > status code 0 - Protocol "about" is unknown > Error: Failed to load about:blank, with network status code 301 and http > status code 0 - Protocol "about" is unknown > Error: Failed to load about:blank, with network status code 301 and http > status code 0 - Protocol "about" is unknown > Error: Failed to load about:blank, with network status code 301 and http > status code 0 - Protocol "about" is unknown > [============================================================] 100% > Printing pages (2/2) > [> ] > Done > Exit with code 1 due to network error: ProtocolUnknownError > make[4]: *** [Makefile:652: quickstartguide.pdf] Error 1 The full build log is available from: http://qa-logs.debian.net/2020/09/26/warzone2100_3.3.0-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.
