Your message dated Tue, 06 Oct 2020 21:49:39 +0000 with message-id <e1kpuq3-000dvn...@fasolo.debian.org> and subject line Bug#971194: fixed in warzone2100 3.3.0-3 has caused the Debian Bug report #971194, regarding warzone2100: FTBFS: Exit with code 1 due to network error: ProtocolUnknownError to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 971194: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971194 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---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.
--- End Message ---
--- Begin Message ---Source: warzone2100 Source-Version: 3.3.0-3 Done: Markus Koschany <a...@debian.org> We believe that the bug you reported is fixed in the latest version of warzone2100, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 971...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Markus Koschany <a...@debian.org> (supplier of updated warzone2100 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 1.8 Date: Tue, 06 Oct 2020 22:57:35 +0200 Source: warzone2100 Architecture: source Version: 3.3.0-3 Distribution: unstable Urgency: medium Maintainer: Debian Games Team <pkg-games-de...@lists.alioth.debian.org> Changed-By: Markus Koschany <a...@debian.org> Closes: 971194 Changes: warzone2100 (3.3.0-3) unstable; urgency=medium . * Team upload. * Add wkhtmltopdf.patch and grant wkhtmltopdf access to local files in order to prevent a FTBFS. (Closes: #971194) * Switch to debhelper-compat = 13. * Declare compliance with Debian Policy 4.5.0. * Install the appdata file. Checksums-Sha1: ba8d2a375c91ec3bfe92205766215d7b9317ae97 2767 warzone2100_3.3.0-3.dsc f3351bb0cf822c53e4153827b8fbc35dfec9765f 27304 warzone2100_3.3.0-3.debian.tar.xz c08e6f2519926d3e3870a32d2c4dfc0129a987f3 16324 warzone2100_3.3.0-3_amd64.buildinfo Checksums-Sha256: 102c6192cc6d56237dbf2dc31fb26b6a1e10a99f276336d5d8d306f1de775e38 2767 warzone2100_3.3.0-3.dsc 3fc18cfdc35b465db5df8b39aef519db418c3c07b7c4b4e9a5da41e297a71c32 27304 warzone2100_3.3.0-3.debian.tar.xz d132739b0a31672e86878f5c54a5ca16aa98ff6e579e2bb0b2a7a8931d610860 16324 warzone2100_3.3.0-3_amd64.buildinfo Files: 010937c071afe070d34acd5b61115b6d 2767 games optional warzone2100_3.3.0-3.dsc 14e80f418080117eb45cc192e7bb19fd 27304 games optional warzone2100_3.3.0-3.debian.tar.xz 4366f341450603619211737fb827b36e 16324 games optional warzone2100_3.3.0-3_amd64.buildinfo -----BEGIN PGP SIGNATURE----- iQKjBAEBCgCNFiEErPPQiO8y7e9qGoNf2a0UuVE7UeQFAl984ZZfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEFD RjNEMDg4RUYzMkVERUY2QTFBODM1RkQ5QUQxNEI5NTEzQjUxRTQPHGFwb0BkZWJp YW4ub3JnAAoJENmtFLlRO1HkRmgP/1h90uluWxB9ds0CJlK17A6vabMNuElKGasA mX9K95rmgz+xUh+2onkWCPBBbRk4/RggWS/3mFjPOrmHaZVxknQdIr2xNenGCQ/k AuDyxfu21wgNJW+mOq/OmYi2TOEVuq5CnDFA00em35BANpQS7Z87NHVbiSq/5x94 GNFXsVLa3ZjfLCeD9HjKQmE8C18rUDwwFToL6H3PDQqA/JteuVDdE+67L/yq+OVd Uas2NOvV66OoGeyvwXVMa5zrg0ouCV1P9/DqBWdIJWmCKgpXnh0KAM9n9KljlSG6 uK/y+rnNRXBrrZJDidq8v+wRSOtIxrwVz+rDBH0cSAiP5Ek656wCbdflUitWIXem 8ObqStPsEaJkICc0v+QQylS+o6uHWtQ1p+kVW69cre51Wt0H2dewtl3wvSOLNS5a rjUiZJKrrupFhljWLYpwLGC19qI0YY0eg7OjbPrUb7rnXy3qFDcs6UInPDSwit68 SFFcuHOgExC+8H14eGCCWXZS0wIeZGkt+2cSjzaz+O4bSltOAiXqshWlLns0wbLz 2B7ABkgdy2do/sNhgZo/GQTwnajTMuqGTIEeYr7GIRm3ImttbmORjyeWSF/gU1ET p2DD+3DAXHzEIt/EDqkP/9+m6BnX9qv9WNjynsWLXfcucMu9nbxkHczif7y0Lq42 u1dvEAcn =LRMA -----END PGP SIGNATURE-----
--- End Message ---
