Bug#924583: spamassassin: razor2 had unknown error during get_server_info at /usr/share/perl5/Mail/SpamAssassin/Plugin/Razor2.pm line 186
telnet discovery.razor.cloudmark.com 2703 Trying 208.83.139.205... Connected to discovery.razor.cloudmark.com. Escape character is '^]'. sn=C&srl=43882&a=l&a=cg a=g&pm=csl err=240 ... a=g&pm=nsl err=240 ... a=g&pm=state -sn=C sv=4.007 zone=razor2.cloudmark.com ac=21 srl=43882 lm=4 bql=50 bqs=329 dre=8 srf=FF sa=2FB se=F2380 to=15 nmp=2 ep8=20 ep10=20 ep19=5 ep20=5 ep21=5 ep22=5 crt=90 immdi=1 imsio=0 lsp=3 lsp10=0 mps=300 mhs=15 mphs=4 cp=7 1 16 6 5 4 3 2 0 cs=1
Processed: Bug #924733 in pyqwt3d marked as pending
Processing control commands: > tag -1 pending Bug #924733 [src:pyqwt3d] pyqwt3d: FTBFS (SIP failed to generate the C++ code) Added tag(s) pending. -- 924733: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924733 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#924733: Bug #924733 in pyqwt3d marked as pending
Control: tag -1 pending Hello, Bug #924733 in pyqwt3d reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/modules/pyqwt3d/commit/280511aac5da610b7e37a0ccefebbf0655f3c8ab Add patch for fixing FTBS with sip >= 4.19.14 (Closes: #924733) (this message was generated automatically) -- Greetings https://bugs.debian.org/924733
Bug#924807: [Pkg-javascript-devel] Bug#924807: Bug#924807: Bug#924807: Bugs come from conflict between node-uglify and node-uglify-js
Le 18/03/2019 à 06:19, Xavier a écrit : > Le 18/03/2019 à 00:02, Jonas Smedegaard a écrit : >> Quoting Jonas Smedegaard (2019-03-17 23:48:57) >>> Quoting Xavier (2019-03-17 23:12:51) Control: reassign 924807 uglify-js Control: reassign 924809 uglify-js Control: merge 924807 924809 Bug seems to come from conflict between https://tracker.debian.org/pkg/uglify-js and https://tracker.debian.org/pkg/uglifyjs: webpack can't now be installed with uglifyjs >>> >>> Problem is packages depending on uglifyjs and webpack together: webpack >>> depends indirectly on node-uglify 2.x, whereas uglifyjs is either a >>> virtual package provided by node-uglify 2.x or (since recently) a real >>> package depending on node-uglyfy-js 3.x. >>> >>> Yes, the problem emerged when node-uglify was introduced as a real >>> package, but the fix is for those packages depending on uglifyjs and >>> webpack together to depend on node-uglify 2.x instead of the virtual >>> package. >>> >>> Please revert these reassignments: This cannot be fixed in uglifyjs 3.x. >> >> Put differently, the problem is packages depending both unversioned and >> transitively versioned on uglifyjs - that works only as long as the >> transitive dependency happens to be newest major release of uglifyjs. >> >> - Jonas > > List of packages that are affected by this change: > > node-uglify > Build Reverse Depends: > ... > > node-uglify > Reverse Depends: > node-uglifyjs-webpack-plugin > emscripten > python3-webassets > python-webassets > uglifyjs > node-uglify-js > python3-livereload > python-livereload > node-with > node-grunt-contrib-uglify > node-transformers > lava-dev > node-dryice > node-constantinople If I understand (but maybe I'm wrong), this means that in buster it is not possible to have uglifyjs installed with one of these 14 packages or their dependencies (`apt-cache rdepends --recurse node-uglify` returns several thousands package names).
Bug#924807: [Pkg-javascript-devel] Bug#924807: Bug#924807: Bugs come from conflict between node-uglify and node-uglify-js
Le 18/03/2019 à 00:02, Jonas Smedegaard a écrit : > Quoting Jonas Smedegaard (2019-03-17 23:48:57) >> Quoting Xavier (2019-03-17 23:12:51) >>> Control: reassign 924807 uglify-js >>> Control: reassign 924809 uglify-js >>> Control: merge 924807 924809 >>> >>> Bug seems to come from conflict between >>> https://tracker.debian.org/pkg/uglify-js and >>> https://tracker.debian.org/pkg/uglifyjs: webpack can't now be installed >>> with uglifyjs >> >> Problem is packages depending on uglifyjs and webpack together: webpack >> depends indirectly on node-uglify 2.x, whereas uglifyjs is either a >> virtual package provided by node-uglify 2.x or (since recently) a real >> package depending on node-uglyfy-js 3.x. >> >> Yes, the problem emerged when node-uglify was introduced as a real >> package, but the fix is for those packages depending on uglifyjs and >> webpack together to depend on node-uglify 2.x instead of the virtual >> package. >> >> Please revert these reassignments: This cannot be fixed in uglifyjs 3.x. > > Put differently, the problem is packages depending both unversioned and > transitively versioned on uglifyjs - that works only as long as the > transitive dependency happens to be newest major release of uglifyjs. > > - Jonas List of packages that are affected by this change: node-uglify Build Reverse Depends: sizzle sockjs-client twitter-bootstrap3 twitter-bootstrap3 underscore.string wax.js witty asciimathtml coffeescript d3-tip.js diff-match-patch elycharts.js es-module-loader-0.17.js explorercanvas flightgear-phi highlight.js icingaweb2 impress.js isso jquery-coolfieldset jquery-geo jquery-goodies jquery-lazyload jquery-minicolors jquery-reflection jquery-simpletreemenu jquery-watermark jsrender languages4translatewiki ldap-account-manager leaflet-geometryutil leaflet-image libjs-chosen libjs-cssrelpreload libjs-img.srcset libjs-jquery-scrollto libjs-jsxc libjs-term.js lintian mgrs modernizr node-babel node-bowser node-browser-pack node-browserify-lite node-eventemitter2 node-events node-fuzzaldrin-plus node-hooker node-htmlparser node-ipaddr.js node-is-typedarray node-iscroll node-jquery-textcomplete node-jsonselect node-lodash node-lunr node-markdown-it-html5-embed node-marked node-matrix-js-sdk node-merge node-n3 node-pinkyswear node-q node-sdp-transform node-shiny-server-client node-sink-test node-sprintf-js node-turbolinks node-tweetnacl node-typedarray-to-buffer node-umd pegjs polymaps prefixfree proj4js rainbow.js raphael requirejs rickshaw rtcninjajs ruby-rails-assets-favico.js ruby-rails-assets-jquery-fullscreen-plugin ruby-rails-assets-perfect-scrollbar sax.js sizzle slick sockjs-client spip underscore.string wax.js twitter-bootstrap3 twitter-bootstrap3 almond asciimathtml coffeescript d3-tip.js diff-match-patch elycharts.js emscripten es-module-loader-0.17.js explorercanvas flightgear-phi highlight.js icingaweb2 impress.js isso jquery-coolfieldset jquery-geo jquery-goodies jquery-lazyload jquery-minicolors jquery-reflection jquery-simpletreemenu jquery-watermark jsrender languages4translatewiki ldap-account-manager leaflet-geometryutil leaflet-image libjs-chosen libjs-cssrelpreload libjs-img.srcset libjs-jquery-scrollto libjs-jsxc libjs-term.js lintian mgrs modernizr node-babel node-bowser node-browser-pack node-browserify-lite node-eventemitter2 node-events node-fuzzaldrin-plus node-hooker node-htmlparser node-ipaddr.js node-is-typedarray node-iscroll node-jquery-textcomplete node-jsonselect node-lodash node-lunr node-markdown-it-html5-embed node-marked node-matrix-js-sdk node-merge node-mocha node-n3 node-pinkyswear node-q node-sdp-transform node-shiny-server-client node-sink-test node-sprintf-js node-turbolinks node-tweetnacl node-typedarray-to-buffer node-umd pegjs polymaps prefixfree proj4js rainbow.js raphael requirejs rickshaw rtcninjajs ruby-rails-assets-favico.js ruby-rails-assets-jquery-fullscreen-plugin ruby-rails-assets-perfect-scrollbar sax.js sizzle slick sockjs-client spip underscore.string wax.js witty freeipa node-grunt-contrib-uglify node-jquery proj4js icingaweb2 lintian twitter-bootstrap3 coffeescript jquery-goodies jupyter-notebook libjs-term.js mustache.js node-bowser node-events node-is-typedarray node-merge node-sdp-transform node-semver node-typedarray-to-buffer requirejs rtcninjajs twitter-bootstrap3 highlight.js jquery-minicolors less.js libjs-chosen node-iscroll node-marked pegjs almond angular.js backbone colors.js elycharts.js highlight.js ie7-js impress.js jquery jquery-coolfieldset jquery-geo jquery-goodies jq
Bug#888935: [Pkg-javascript-devel] Bug#888935: node-xterm FTBFS: error TS2339: Property 'parentElement' does not exist on type 'never'
On 2019, മാർച്ച് 18 2:33:00 AM IST, Ximin Luo wrote: >On Thu, 08 Mar 2018 17:53:27 + Ghislain Vaillant > wrote: >I had an attempt at this, but it is getting a bit hairy and I think it >may be time to call it quits. My recommendation is for jupyter-notebook >to patch out this functionality and not depend on node-xterm, and for >this package to be RM from Debian. Just wanted to make a note here that this package is also required for gitlab (right now gitlab takes it from npmjs.com and in contrib). Since gitlab is not in buster, we can remove it from buster, but I'd like to try fixing it for next release (I'd like to move gitlab to main in next release). -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
Bug#866421: marked as done (comix: depends on obsolete python-imaging (replace with python3-pil or python-pil))
Your message dated Mon, 18 Mar 2019 05:19:06 + with message-id and subject line Bug#866421: fixed in comix 4.0.4-4 has caused the Debian Bug report #866421, regarding comix: depends on obsolete python-imaging (replace with python3-pil or python-pil) 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.) -- 866421: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866421 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:comix Version: 4.0.4-3 Severity: important Tags: sid buster User: d...@debian.org Usertags: imaging-pillow One or more binary packages built from this source depends on or recommends python-imaging, which is obsolete for some years now. Please build the source using the python-pil package. If your package doesn't need to be built with Python2, please consider using Python3 and depend on python3-pil. Planning to remove python-imaging for the buster release, so the severity of this issues might be raised. --- End Message --- --- Begin Message --- Source: comix Source-Version: 4.0.4-4 We believe that the bug you reported is fixed in the latest version of comix, 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 866...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Emfox Zhou (supplier of updated comix 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: SHA256 Format: 1.8 Date: Mon, 18 Mar 2019 12:03:08 +0800 Source: comix Binary: comix Architecture: source all Version: 4.0.4-4 Distribution: unstable Urgency: medium Maintainer: Emfox Zhou Changed-By: Emfox Zhou Description: comix - GTK Comic Book Viewer Closes: 866421 913420 Changes: comix (4.0.4-4) unstable; urgency=medium . * It is highly recommended to switch to mcomix, comix is in fact not maintained for long, but still Thanks to Thomas Walz for the patch: added patch import PIL rather than Imaging (Closes: #866421) * Discard gconf support. (Closes: #913420) Checksums-Sha1: 3f3a292c8133c4485c637930baafe529f525ad0f 1672 comix_4.0.4-4.dsc b76c19421e5e39540c0a96591a73bbc27a0a9ac2 5492 comix_4.0.4-4.debian.tar.xz a0a910c92354cfc14928de4cecd4cd7ee436c43a 165784 comix_4.0.4-4_all.deb 2b8ff226f2507a524ff6927baec2b509381dbe0b 5577 comix_4.0.4-4_amd64.buildinfo Checksums-Sha256: aaf0368c9310023b127ca1ec1e46847efe38a34e1e8eeea84b05d7f356f37376 1672 comix_4.0.4-4.dsc 6788255366a58df6e1dbb4d5180c16b5674fd3cbe59a9efa37dbae23007c0a34 5492 comix_4.0.4-4.debian.tar.xz f77e9269f72d743d3ea1a27f47e9569f702b0430753d532d4b90ae1a2c528770 165784 comix_4.0.4-4_all.deb b68682730f563fb4943d6623f378e7c2e428124441e3739ec34e1f2782ff9c15 5577 comix_4.0.4-4_amd64.buildinfo Files: 20baa5920081e944fb8f9883db01620c 1672 x11 optional comix_4.0.4-4.dsc 8c71965ded7ad28d18256f0f05f56c02 5492 x11 optional comix_4.0.4-4.debian.tar.xz 9d60f94b76f578b6ecc59368b221e704 165784 x11 optional comix_4.0.4-4_all.deb d09f37068679d091628996336423f035 5577 x11 optional comix_4.0.4-4_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEGSauJtItZVqOiaNpgImbv9t7vZQFAlyPJdQACgkQgImbv9t7 vZS6Og/+O/RzwZ58XPKYkK4Q9SwU56eRL4f4nPhy2TH3euZ1gEoaN1hEswOZUmeJ aiTaKlKZfm/rqQR+KVRTKCTA2xzt8mRrorbhzeIQowCqSucGX7W+NxEjhMfoVAHy UDO++UtribqHXylTZcfr59ZCH7oH7PwAS8Oa6Tg3SqS1vTGgVaBELUiERElF91/u FdjZQX0YTOrZwAaOYc7KFObBDpibdA0G1jK4/HUsD6R/FSWARXJ5r3DAUr4SVEih yqZxYCghXEHcQIYR3NH8HUJbc9BmzUC49UtOSd1I5ypIMogIgLYeSMmRQ75mxHmO 26DZPU5hYbYrdVVVTPNlYM5xqco326KaXuj7Ln+gwesf+fgEL5XLJFjsryoTFrSD KFT01j/Ciq1h2V6GWATHxymKORXNNGjJiKIqdrRopf1isqHZh1s3IHfxgEuz4DXb Tcaog2okg9dqf3b9r8XONMol8gr41W+AnPS2feusY1pQmR5989knvPVRctuv7ECy Z7tZUylnuLXWKN05jjTgMAAnKrCipfiPs/8S8XitpnrS2lRisTQLiNKD0rinBaKa k3lZKDts+hnEAlI8Cs1pDpyK1HGh+53PZ/5F4F6Flse2Oo4qZWs1oPcHS7xuKRaw QgZwmBH5DlyssPATEIjjqyNey8PHzIsRHtiYabmtCDDTQa2S8PM= =0dkb -END PGP SIGNATURE End Message ---
Bug#924206: control
Control: reassign -1 src:rust-failure 0.1.3-1 Control: fixed -1 0.1.5-1 -- GPG: ed25519/56034877E1F87C35 GPG: rsa4096/1318EFAC5FBBDBCE https://github.com/infinity0/pubkeys.git
Processed: Re: control
Processing control commands:
> reassign -1 src:rust-failure 0.1.3-1
Bug #924206 {Done: Ximin Luo } [rust-failure]
rust-opener: FTBFS (method `name` is not a member of trait `failure::Fail`)
Bug reassigned from package 'rust-failure' to 'src:rust-failure'.
No longer marked as found in versions 0.1.3-1.
No longer marked as fixed in versions 0.1.5-1.
Bug #924206 {Done: Ximin Luo } [src:rust-failure]
rust-opener: FTBFS (method `name` is not a member of trait `failure::Fail`)
Marked as found in versions rust-failure/0.1.3-1.
> fixed -1 0.1.5-1
Bug #924206 {Done: Ximin Luo } [src:rust-failure]
rust-opener: FTBFS (method `name` is not a member of trait `failure::Fail`)
Marked as fixed in versions rust-failure/0.1.5-1.
--
924206: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924206
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#924206: control
Control: reassign -1 rust-failure 0.1.3-1 Control: fixed -1 0.1.5-1 -- GPG: ed25519/56034877E1F87C35 GPG: rsa4096/1318EFAC5FBBDBCE https://github.com/infinity0/pubkeys.git
Processed: control
Processing control commands:
> reassign -1 rust-failure 0.1.3-1
Bug #924206 {Done: Ximin Luo } [src:rust-opener]
rust-opener: FTBFS (method `name` is not a member of trait `failure::Fail`)
Bug reassigned from package 'src:rust-opener' to 'rust-failure'.
No longer marked as found in versions rust-opener/0.3.0-1.
No longer marked as fixed in versions 0.1.5-1 and rust-opener/0.3.2-1.
Bug #924206 {Done: Ximin Luo } [rust-failure]
rust-opener: FTBFS (method `name` is not a member of trait `failure::Fail`)
There is no source info for the package 'rust-failure' at version '0.1.3-1'
with architecture ''
Unable to make a source version for version '0.1.3-1'
Marked as found in versions 0.1.3-1.
> fixed -1 0.1.5-1
Bug #924206 {Done: Ximin Luo } [rust-failure]
rust-opener: FTBFS (method `name` is not a member of trait `failure::Fail`)
There is no source info for the package 'rust-failure' at version '0.1.5-1'
with architecture ''
Unable to make a source version for version '0.1.5-1'
Marked as fixed in versions 0.1.5-1.
--
924206: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924206
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#921792: closing 921792
close 921792 1.2.1-3 thanks The bug is fixed by the recent texlive update.
Processed: closing 921792
Processing commands for cont...@bugs.debian.org: > close 921792 1.2.1-3 Bug #921792 [src:log4c] log4c: FTBFS (LaTeX error) Marked as fixed in versions log4c/1.2.1-3. Bug #921792 [src:log4c] log4c: FTBFS (LaTeX error) Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 921792: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921792 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#924665: marked as done (xymon: Upgrade fails if /etc/xymon/critical.cfg.bak is deleted by local admin)
Your message dated Mon, 18 Mar 2019 04:04:21 + with message-id and subject line Bug#924665: fixed in xymon 4.3.28-5 has caused the Debian Bug report #924665, regarding xymon: Upgrade fails if /etc/xymon/critical.cfg.bak is deleted by local admin 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.) -- 924665: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924665 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: xymon Version: 4.3.28-3 Severity: serious Control: found -1 4.3.28-2 4.3.28-4 4.3.0~beta2.dfsg-9.1 Justification: upgrades fail under some valid and realistic circumstances Originally reported in Ubuntu at https://bugs.launchpad.net/ubuntu/+source/xymon/+bug/1819378 under a slightly obscure setup. Context: The package xymon ships /etc/xymon/critical.cfg.bak on purpose because it is needed initially so that the user www-data can write backup copies of /etc/xymon/critical.cfg into it without needing the directory /etc/xymon/ being writable for www-data. This is upstream design and present in the (upstream) xymon RPMs as well. It is more or less documented in the critical.cfg(5) man page shipped with xymon. Issue: To achieve the proper permissions in the Debian package, /etc/xymon/critical.cfg.bak is shipped as conffile and xymon's postinst executes "cd /etc/xymon; chgrp www-data critical.cfg critical.cfg.bak; chmod g+w critical.cfg critical.cfg.bak" unconditionally. So if a local admin sees the .bak file and removes it because it doesn't look relevant, the next package upgrade or security update will fail unless a file named critical.cfg.bak has been created again. Thanks to sukhvirz on Launchpad for the initial bug report in Ubuntu and Thomas K Jones on Launchpad for giving me the right hint to understand the cause of this issue. While the upstream design is debatable with no doubt, the proper and unintrusive fix is to make the chown and chgrp in postinst conditional by checking the existence of the two files first. And despite this issue seems to have not been noticed by us (the package maintainers) or reported for quite a while(*), it's neverless a rather _common_ thing to clean up .bak files from /etc/, especially if /etc/ is tracked in a VCS, e.g. via etckeeper. Hence the RC severity. Will come up with a fixed package latest the upcoming weekend. Footnotes: (*) I see the relevant code even in the xymon package in Wheezy, just with different file names as this was the last release before the big conffile renaming. Regards, Axel -- ,''`. | Axel Beckert , https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE --- End Message --- --- Begin Message --- Source: xymon Source-Version: 4.3.28-5 We believe that the bug you reported is fixed in the latest version of xymon, 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 924...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Axel Beckert (supplier of updated xymon 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: Mon, 18 Mar 2019 01:28:51 +0100 Source: xymon Binary: xymon xymon-client xymon-client-dbgsym xymon-dbgsym Architecture: source amd64 Version: 4.3.28-5 Distribution: unstable Urgency: medium Maintainer: Christoph Berg Changed-By: Axel Beckert Description: xymon - monitoring system for systems, networks and applications xymon-client - client for the Xymon network monitor Closes: 924665 Changes: xymon (4.3.28-5) unstable; urgency=medium . * xymon.postinst: Check for file existence before calling chgrp/chmod on critical.cfg and critical.cfg.bak. (Closes: #924665, LP: #1819378) Checksums-Sha1: c91b7c13700407319598c5a5d01c1210a23a02c3 2062 xymon_4.3.28-5.dsc ff6853f324b2a2aff8afcd8a348647b193241519 45252 xymon_4.3.28-5.debian.tar.xz a6fc0dd590b978c7a7160f00f964585263e607bd 1078204 xymon-client-dbgsym_4.3.28-5_amd64.deb 5d3a886f51f2d195fd78c270df02896da9674b34 293892 xymon-client_4.3.28-5_amd64.deb 701c1b0
Bug#924806: marked as done (ruby-moneta: FTBFS: build-dependency not installable: ruby-fog)
Your message dated Mon, 18 Mar 2019 03:34:08 + with message-id and subject line Bug#924806: fixed in ruby-moneta 1.0.0-5 has caused the Debian Bug report #924806, regarding ruby-moneta: FTBFS: build-dependency not installable: ruby-fog 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.) -- 924806: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924806 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-moneta Version: 1.0.0-3 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20190315 qa-ftbfs Justification: FTBFS in buster on amd64 Hi, During a rebuild of all packages in buster (in a buster chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper (>= 11~), gem2deb, lsof, mariadb-server, > netcat, ruby-activesupport (>= 2:3.2.11~), ruby-fog, ruby-multi-json, > ruby-mysql2, ruby-rack, ruby-rack-cache, ruby-rspec (>= 2.11), > ruby-rspec-retry, ruby-sequel, ruby-setup, ruby-sqlite3, ruby-tokyocabinet, > ruby-activerecord > Filtered Build-Depends: debhelper (>= 11~), gem2deb, lsof, mariadb-server, > netcat, ruby-activesupport (>= 2:3.2.11~), ruby-fog, ruby-multi-json, > ruby-mysql2, ruby-rack, ruby-rack-cache, ruby-rspec (>= 2.11), > ruby-rspec-retry, ruby-sequel, ruby-setup, ruby-sqlite3, ruby-tokyocabinet, > ruby-activerecord > dpkg-deb: building package 'sbuild-build-depends-ruby-moneta-dummy' in > '/<>/resolver-Us1BuN/apt_archive/sbuild-build-depends-ruby-moneta-dummy.deb'. > dpkg-scanpackages: warning: Packages in archive but missing from override > file: > dpkg-scanpackages: warning: sbuild-build-depends-core-dummy > sbuild-build-depends-ruby-moneta-dummy > dpkg-scanpackages: info: Wrote 2 entries to output Packages file. > Ign:1 copy:/<>/resolver-Us1BuN/apt_archive ./ InRelease > Get:2 copy:/<>/resolver-Us1BuN/apt_archive ./ Release [963 B] > Ign:3 copy:/<>/resolver-Us1BuN/apt_archive ./ Release.gpg > Get:4 copy:/<>/resolver-Us1BuN/apt_archive ./ Sources [626 B] > Get:5 copy:/<>/resolver-Us1BuN/apt_archive ./ Packages [698 B] > Fetched 2287 B in 0s (0 B/s) > Reading package lists... > Reading package lists... > > Install ruby-moneta build dependencies (apt-based resolver) > --- > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > sbuild-build-depends-ruby-moneta-dummy : Depends: ruby-fog but it is not > installable > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://aws-logs.debian.net/2019/03/15/ruby-moneta_1.0.0-3_testing.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: ruby-moneta Source-Version: 1.0.0-5 We believe that the bug you reported is fixed in the latest version of ruby-moneta, 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 924...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. HIGUCHI Daisuke (VDR dai) (supplier of updated ruby-moneta 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 MES
Processed: Bug #924806 in ruby-moneta marked as pending
Processing control commands: > tag -1 pending Bug #924806 [src:ruby-moneta] ruby-moneta: FTBFS: build-dependency not installable: ruby-fog Added tag(s) pending. -- 924806: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924806 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#924806: Bug #924806 in ruby-moneta marked as pending
Control: tag -1 pending Hello, Bug #924806 in ruby-moneta reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/ruby-team/ruby-moneta/commit/b2e6386c5b5623490380ff2a0612919c791159f4 depends fog-core instead of fog (Closes: #924806) (this message was generated automatically) -- Greetings https://bugs.debian.org/924806
Bug#924820: marked as done (fltk1.3: FTBFS: cp: cannot stat 'latex/refman.pdf': No such file or directory)
Your message dated Sun, 17 Mar 2019 23:03:45 -0400
with message-id
and subject line Re: Bug#924820: fltk1.3: FTBFS: cp: cannot stat
'latex/refman.pdf': No such file or directory
has caused the Debian Bug report #924820,
regarding fltk1.3: FTBFS: cp: cannot stat 'latex/refman.pdf': No such file or
directory
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.)
--
924820: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924820
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fltk1.3
Version: 1.3.4-7
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20190315 qa-ftbfs
Justification: FTBFS in buster on amd64
Hi,
During a rebuild of all packages in buster (in a buster chroot, not a
sid chroot), your package failed to build on amd64.
Relevant part (hopefully):
> make[2]: Entering directory '/<>/documentation'
> echo "Generating Doxyfile ..."
> Generating Doxyfile ...
> sed -e's,@FL_VERSION@,1.3.4,' \
> -e's,@GENERATE_HTML@,YES,' \
> -e's,@GENERATE_LATEX@,NO,' \
> -e's, @LATEX_HEADER@,,' \
> -e's,@CMAKE_CURRENT_SOURCE_DIR@/,,' \
> -e's,@CMAKE_SOURCE_DIR@/,../,' \
> < Doxyfile.in > Doxyfile
> echo "Generating HTML documentation..."
> Generating HTML documentation...
> rm -rf html
> /usr/bin/install -c -d html
> /usr/bin/doxygen
> if test "x/usr/bin/doxygen" = "x" ; then \
> echo "Sorry - doxygen not found. Please install doxygen and run
> configure."; \
> fi
> test -d html && cp src/tiny.png html/
> echo "Generating Doxybook ..."
> Generating Doxybook ...
> sed -e's,@FL_VERSION@,1.3.4,' \
> -e's,@GENERATE_HTML@,NO,' \
> -e's,@GENERATE_LATEX@,YES,' \
> -e's,@LATEX_HEADER@,src/fltk-book.tex,' \
> -e's,@CMAKE_CURRENT_SOURCE_DIR@/,,' \
> -e's,@CMAKE_SOURCE_DIR@/,../,' \
> < Doxyfile.in > Doxybook
> DOXY_VERSION=`/usr/bin/doxygen --version`; \
> YEAR=`date -ud'Thu, 15 Mar 2018 22:20:20 -0400' +%Y`; \
> FLTK_VERSION=`cat ../VERSION`; \
> TODAY=`date -ud'Thu, 15 Mar 2018 22:20:20 -0400' +'%B %e, %Y'`; \
> sed -e"s/@YEAR@/$YEAR/g" \
> -e"s/@FL_VERSION@/1.3.4/g" \
> -e"s/@DOXY_VERSION@/$DOXY_VERSION/g" \
> -e"s/today{}/$TODAY/g" \
> < src/fltk-book.tex.in > src/fltk-book.tex
> rm -rf latex
> echo "Generating PDF documentation ..."
> Generating PDF documentation ...
> /usr/bin/doxygen Doxybook
> ./make_pdf
> cp -f latex/refman.pdf fltk.pdf
> cp: cannot stat 'latex/refman.pdf': No such file or directory
> make[2]: *** [Makefile:178: pdf] Error 1
The full build log is available from:
http://aws-logs.debian.net/2019/03/15/fltk1.3_1.3.4-7_testing.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: fltk1.3
Version: 1.3.4-9
Lucas Nussbaum writes:
> During a rebuild of all packages in buster (in a buster chroot, not a
> sid chroot), your package failed to build on amd64.
Hi, Lucas.
Thanks for the report, which I will however close as a duplicate of
#921294 (in turn fallout from texlive-latex-extra bug #920459). I
definitively addressed this failure in unstable with 1.3.4-9 on Feb. 27.
At the time of the freeze, the only thing keeping this version from
migrating was the fact that I addressed the failure by insisting on a
fixed version of texlive-latex-extra, which turned out to be blocked for
unclear reasons (and still is, alas).
I presume we won't release with a broken texlive-latex-extra, so my plan
at this point is to file an unblock request once TeX Live migrates.
--
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu--- End Message ---
Bug#924800: marked as done (git-annex: FTBFS: dh_auto_test: make -j1 test returned exit code 2)
Your message dated Sun, 17 Mar 2019 19:46:59 -0700 with message-id <87imwgew64@iris.silentflame.com> and subject line Re: Bug#924800: git-annex: FTBFS: dh_auto_test: make -j1 test returned exit code 2 has caused the Debian Bug report #924800, regarding git-annex: FTBFS: dh_auto_test: make -j1 test returned exit code 2 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.) -- 924800: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924800 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: git-annex Version: 7.20190129-2 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20190315 qa-ftbfs Justification: FTBFS in buster on amd64 Hi, During a rebuild of all packages in buster (in a buster chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > ./Setup build -j1 > Preprocessing executable 'git-annex' for git-annex-7.20190129.. > Building executable 'git-annex' for git-annex-7.20190129.. > if [ "./Setup" = stack ]; then \ > ln -sf $(stack path --dist-dir)/build/git-annex/git-annex git-annex; \ > else \ > ln -sf dist/build/git-annex/git-annex git-annex; \ > fi > ln -sf git-annex git-annex-shell > ./git-annex test > Tests > QuickCheck > prop_encode_decode_roundtrip: OK (0.04s) > +++ OK, passed 1000 tests. > prop_encode_c_decode_c_roundtrip: OK (0.03s) > +++ OK, passed 1000 tests. > prop_isomorphic_key_encode: OK (0.03s) > +++ OK, passed 1000 tests. > prop_isomorphic_shellEscape: OK (0.02s) > +++ OK, passed 1000 tests. > prop_isomorphic_shellEscape_multiword:OK (0.92s) > +++ OK, passed 1000 tests. > prop_isomorphic_configEscape: OK (0.02s) > +++ OK, passed 1000 tests. > prop_parse_show_Config: OK (0.05s) > +++ OK, passed 1000 tests. > prop_upFrom_basics: OK (0.02s) > +++ OK, passed 1000 tests. > prop_relPathDirToFile_basics: OK (0.03s) > +++ OK, passed 1000 tests. > prop_relPathDirToFile_regressionTest: OK > +++ OK, passed 1 tests. > prop_cost_sane: OK > +++ OK, passed 1 tests. > prop_matcher_sane:OK > +++ OK, passed 1 tests. > prop_HmacSha1WithCipher_sane: OK > +++ OK, passed 1 tests. > prop_VectorClock_sane:OK > +++ OK, passed 1 tests. > prop_addMapLog_sane: OK > +++ OK, passed 1 tests. > prop_verifiable_sane: OK (0.10s) > +++ OK, passed 1000 tests. > prop_segment_regressionTest: OK > +++ OK, passed 1 tests. > prop_read_write_transferinfo: OK (0.04s) > +++ OK, passed 1000 tests. > prop_read_show_inodecache:OK (0.02s) > +++ OK, passed 1000 tests. > prop_parse_build_log: OK (1.56s) > +++ OK, passed 1000 tests. > prop_read_show_TrustLevel:OK > +++ OK, passed 1 tests. > prop_parse_build_TrustLevelLog: OK > +++ OK, passed 1 tests. > prop_hashes_stable: OK > +++ OK, passed 1 tests. > prop_mac_stable: OK > +++ OK, passed 1 tests. > prop_schedule_roundtrips: OK > +++ OK, passed 1000 tests. > prop_past_sane: OK > +++ OK, passed 1 tests. > prop_duration_roundtrips: OK > +++ OK, passed 1000 tests. > prop_metadata_sane: OK (4.69s) > +++ OK, passed 1000 tests. > prop_metadata_serialize: OK (4.35s) > +++ OK, passed 1000 tests. > prop_branchView_legal:OK (1.31s) > +++ OK, passed 1000 tests. > prop_viewPath_roundtrips: OK (0.03s) > +++ OK, passed 1000 tests. > prop_view_roundtrips: OK (1.04s) > +++ OK, passed 1000 tests. > prop_viewedFile_rountrips:
Bug#924897: openjdk-12-jre-headless: fails to install: breaks configuration of ca-certificates-java
Package: openjdk-12-jre-headless Version: 12~33-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): Setting up ca-certificates-java (20190214) ... head: cannot open '/etc/ssl/certs/java/cacerts' for reading: No such file or directory /var/lib/dpkg/info/ca-certificates-java.postinst: line 89: java: command not found dpkg: error processing package ca-certificates-java (--configure): installed ca-certificates-java package post-installation script subprocess returned error exit status 127 dpkg: dependency problems prevent configuration of openjdk-12-jre-headless:amd64: openjdk-12-jre-headless:amd64 depends on ca-certificates-java; however: Package ca-certificates-java is not configured yet. dpkg: error processing package openjdk-12-jre-headless:amd64 (--configure): dependency problems - leaving unconfigured Processing triggers for libc-bin (2.28-8) ... Processing triggers for ca-certificates (20190110) ... Updating certificates in /etc/ssl/certs... 0 added, 0 removed; done. Running hooks in /etc/ca-certificates/update.d... /etc/ca-certificates/update.d/jks-keystore: 82: /etc/ca-certificates/update.d/jks-keystore: java: not found E: /etc/ca-certificates/update.d/jks-keystore exited with code 1. done. Errors were encountered while processing: ca-certificates-java openjdk-12-jre-headless:amd64 cheers, Andreas openjdk-12-jre-headless_12~33-1.log.gz Description: application/gzip
Bug#924896: lttng-modules-dkms: fails to build module for Linux 4.19.0-4
Package: lttng-modules-dkms Version: 2.10.9-1 Severity: serious Justification: fails to build from source User: debian...@lists.debian.org Usertags: piuparts Hi, installation fails because a module cannot be built. make.log starts like this: DKMS make.log for lttng-modules-2.10.9 for kernel 4.19.0-4-amd64 (x86_64) Mon Mar 18 02:28:53 UTC 2019 make: Entering directory '/usr/src/linux-headers-4.19.0-4-amd64' find: '/var/lib/dkms/lttng-modules/2.10.9/build/extra_version/patches/': No such file or directory mv: cannot move '/tmp/tmp.1Xt4Fnx2zB' to '/var/lib/dkms/lttng-modules/2.10.9/build/extra_version/patches.i': No such file or directory CC [M] /var/lib/dkms/lttng-modules/2.10.9/build/lttng-ring-buffer-client-discard.o CC [M] /var/lib/dkms/lttng-modules/2.10.9/build/lttng-ring-buffer-client-overwrite.o CC [M] /var/lib/dkms/lttng-modules/2.10.9/build/lttng-ring-buffer-metadata-client.o CC [M] /var/lib/dkms/lttng-modules/2.10.9/build/lttng-ring-buffer-client-mmap-discard.o CC [M] /var/lib/dkms/lttng-modules/2.10.9/build/lttng-ring-buffer-client-mmap-overwrite.o find: '/var/lib/dkms/lttng-modules/2.10.9/build/probes/../extra_version/patches/': No such file or directory mv: cannot move '/tmp/tmp.ttNlU3nnfe' to '/var/lib/dkms/lttng-modules/2.10.9/build/probes/../extra_version/patches.i': No such file or directory /var/lib/dkms/lttng-modules/2.10.9/build/probes/Kbuild:41: File /usr/src/linux-headers-4.19.0-4-common/arch/x86/kvm/lapic.h not found. Probe "kvm" x86-specific is disabled. Use full kernel source tree to enable it. find: '/var/lib/dkms/lttng-modules/2.10.9/build/tests/../extra_version/patches/': No such file or directory mv: cannot move '/tmp/tmp.mp7m3WVY3W' to '/var/lib/dkms/lttng-modules/2.10.9/build/tests/../extra_version/patches.i': No such file or directory find: '/var/lib/dkms/lttng-modules/2.10.9/build/lib/../extra_version/patches/': No such file or directory CC [M] /var/lib/dkms/lttng-modules/2.10.9/build/tests/probes/lttng-test.o mv: cannot move '/tmp/tmp.N4D75vdmjy' to '/var/lib/dkms/lttng-modules/2.10.9/build/lib/../extra_version/patches.i': No such file or directory /var/lib/dkms/lttng-modules/2.10.9/build/probes/Kbuild:166: Files /usr/src/linux-headers-4.19.0-4-common/fs/btrfs/*.h not found. Probe "btrfs" is disabled. Use full kernel source tree to enable it. /var/lib/dkms/lttng-modules/2.10.9/build/probes/Kbuild:182: Files /usr/src/linux-headers-4.19.0-4-common/fs/ext4/*.h not found. Probe "ext4" is disabled. Use full kernel source tree to enable it. /var/lib/dkms/lttng-modules/2.10.9/build/probes/Kbuild:215: File /usr/src/linux-headers-4.19.0-4-common/drivers/base/regmap/trace.h not found. Probe "regmap" is disabled. Need Linux 4.1+ kernel source tree to enable it. CC [M] /var/lib/dkms/lttng-modules/2.10.9/build/lib/ringbuffer/ring_buffer_backend.o /var/lib/dkms/lttng-modules/2.10.9/build/probes/Kbuild:265: Files /usr/src/linux-headers-4.19.0-4-common/kernel/trace/trace.h not found. Probe "ftrace" is disabled. Use full kernel source tree to enable it. CC [M] /var/lib/dkms/lttng-modules/2.10.9/build/probes/lttng-probe-sched.o CC [M] /var/lib/dkms/lttng-modules/2.10.9/build/probes/lttng-probe-irq.o CC [M] /var/lib/dkms/lttng-modules/2.10.9/build/lttng-ring-buffer-metadata-mmap-client.o CC [M] /var/lib/dkms/lttng-modules/2.10.9/build/probes/lttng-probe-timer.o CC [M] /var/lib/dkms/lttng-modules/2.10.9/build/probes/lttng-probe-kmem.o CC [M] /var/lib/dkms/lttng-modules/2.10.9/build/lttng-clock.o CC [M] /var/lib/dkms/lttng-modules/2.10.9/build/lttng-events.o CC [M] /var/lib/dkms/lttng-modules/2.10.9/build/tests/clock-plugin/lttng-clock-plugin-test.o CC [M] /var/lib/dkms/lttng-modules/2.10.9/build/probes/lttng-probe-module.o CC [M] /var/lib/dkms/lttng-modules/2.10.9/build/lttng-abi.o LD [M] /var/lib/dkms/lttng-modules/2.10.9/build/tests/lttng-test.o /var/lib/dkms/lttng-modules/2.10.9/build/lttng-events.c:2893:10: fatal error: extra_version/patches.i: No such file or directory #include "extra_version/patches.i" ^ compilation terminated. Andreas
Bug#919875: Info received ()
My phone has been hacked for years eden matthews gary reid Brandon brooks clay matthews katelyn brooks . On Sun, Mar 17, 2019, 10:15 PM Debian Bug Tracking System < ow...@bugs.debian.org> wrote: > Thank you for the additional information you have supplied regarding > this Bug report. > > This is an automatically generated reply to let you know your message > has been received. > > Your message is being forwarded to the package maintainers and other > interested parties for their attention; they will reply in due course. > > Your message has been sent to the package maintainer(s): > Debian Java Maintainers > > If you wish to submit further information on this problem, please > send it to 919...@bugs.debian.org. > > Please do not send mail to ow...@bugs.debian.org unless you wish > to report a problem with the Bug-tracking system. > > -- > 919875: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919875 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems >
Bug#919875:
Bug#921904: win-iconv: FTBFS (wine: chdir to /tmp/wine-I6miLw/server-29-3583b06 : No such file or directory)
On Sun 2019-03-17 13:14:54 +0100, Tim Rühsen wrote: > Fixed it by building my own libiconv on MinGW systems. It really is > straight forward and possibly no extra Debian package is needed. Thanks for the feedback, Tim. For your fix, are you building libiconv itself, or win-iconv for MinGW systems? --dkg
Bug#924894: human-icon-theme: Installs translation files in /usr/locale
Package: human-icon-theme Version: 0.28.debian-6 Severity: serious Justification: Policy 9.1.1 It installs .mo files at the /usr/locale path. These are the files: /usr/locale: total 12 drwxr-xr-x 3 root 4096 feb 28 23:45 fr drwxr-xr-x 3 root 4096 feb 28 23:45 it drwxr-xr-x 3 root 4096 feb 28 23:45 pt_BR /usr/locale/fr: total 4 drwxr-xr-x 2 root 4096 feb 28 23:45 LC_MESSAGES /usr/locale/fr/LC_MESSAGES: total 4 -rw-r--r-- 1 root 468 dic 28 16:34 human-icon-theme.mo /usr/locale/it: total 4 drwxr-xr-x 2 root 4096 feb 28 23:45 LC_MESSAGES /usr/locale/it/LC_MESSAGES: total 4 -rw-r--r-- 1 root 484 dic 28 16:34 human-icon-theme.mo /usr/locale/pt_BR: total 4 drwxr-xr-x 2 root 4096 feb 28 23:45 LC_MESSAGES /usr/locale/pt_BR/LC_MESSAGES: total 4 -rw-r--r-- 1 root 495 dic 28 16:34 human-icon-theme.mo -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-2-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE=es_ES.UTF-8:es:en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages human-icon-theme depends on: ii gnome-icon-theme 3.12.0-3 ii tangerine-icon-theme 0.26.debian-5 human-icon-theme recommends no packages. human-icon-theme suggests no packages. -- no debconf information
Bug#924706: marked as done (icedtea-netx: javaws symlink is broken)
Your message dated Mon, 18 Mar 2019 00:19:18 + with message-id and subject line Bug#924706: fixed in icedtea-web 1.7.2-2 has caused the Debian Bug report #924706, regarding icedtea-netx: javaws symlink is broken 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.) -- 924706: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924706 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: icedtea-netx Version: 1.7.2-1 Severity: grave Dear Maintainer, The files in /usr/share/icedtea-web/bin have the wrong file names in the new package and this breaks javaws. itweb-settings and policyeditor are also broken. In the old 1.7.1-1 package: lrwxrwxrwx 1 root root 33 Mar 15 23:53 /etc/alternatives/javaws -> /usr/share/icedtea-web/bin/javaws* lrwxrwxrwx 1 root root 24 Mar 15 23:53 /usr/bin/javaws -> /etc/alternatives/javaws* -rwxr-xr-x 1 root root 5432 Oct 24 08:42 /usr/share/icedtea-web/bin/javaws* In the new 1.7.2-1 package: ls: cannot access '/usr/share/icedtea-web/bin/javaws': No such file or directory lrwxrwxrwx 1 root root 33 Mar 15 23:53 /etc/alternatives/javaws -> /usr/share/icedtea-web/bin/javaws lrwxrwxrwx 1 root root 24 Mar 15 23:53 /usr/bin/javaws -> /etc/alternatives/javaws This is because the file is (presumably incorrectly) named with a .sh suffix in the new package: -rwxr-xr-x 1 root root 6287 Mar 15 18:44 /usr/share/icedtea-web/bin/javaws.sh* If you do a fresh install instead of an upgrade you don't get any symlinks at all: ls: cannot access '/usr/bin/javaws': No such file or directory ls: cannot access '/etc/alternatives/javaws': No such file or directory ls: cannot access '/usr/share/icedtea-web/bin/javaws': No such file or directory -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) LSM: AppArmor: enabled Versions of packages icedtea-netx depends on: ii default-jre 2:1.11-71 ii librhino-java1.7.7.1-1 ii libtagsoup-java 1.2.1+-1 icedtea-netx recommends no packages. icedtea-netx suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: icedtea-web Source-Version: 1.7.2-2 We believe that the bug you reported is fixed in the latest version of icedtea-web, 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 924...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Emmanuel Bourg (supplier of updated icedtea-web 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: Mon, 18 Mar 2019 00:57:12 +0100 Source: icedtea-web Architecture: source Version: 1.7.2-2 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers Changed-By: Emmanuel Bourg Closes: 706306 924706 Changes: icedtea-web (1.7.2-2) unstable; urgency=medium . * Team upload. * Fixed the installation of the CLI tools alternatives (Closes: #924706) * Improved the package description (Closes: #706306) Checksums-Sha1: b022a55a5cb514f492bf3a157e6c460e0112dc3a 2050 icedtea-web_1.7.2-2.dsc d5b105c440556aa931a3640454e872a9a1c5d7d2 25256 icedtea-web_1.7.2-2.debian.tar.xz a2f8d80e48c04b92c58a0586a35157fd2a6faab8 10369 icedtea-web_1.7.2-2_source.buildinfo Checksums-Sha256: e46f0832bff9a30285bf466e63de1decbca41d75b3a701b558324f45f957 2050 icedtea-web_1.7.2-2.dsc 00e68394451cbd298ad52b0b2af60d5e50b700d31e10a056b69cab81232951a7 25256 icedtea-web_1.7.2-2.debian.tar.xz b320ea6d4c8fc191989f02ce728d80a3d7fc066299a9dadf34623c64ee6f176a 10369 icedtea-web_1.7.2-2_source.buildinfo Files: 4b4bbcd99c2494a058a8d912ef4a707d 2050 java optional icedtea-web_1.7.2-2.dsc cdeb23c52962b8264ef0e3d4cdbbe4f8 25256 java optional icedtea-web_1.7.2-2.debian.tar.xz 988ae02b1e34838eae3cfe84e6640f64 10369 java optional icedtea-web_1.7.2-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEuM5N4hCA3PkD4WxA9RPEGeS50KwFAlyO38A
Bug#924706: Bug #924706 in icedtea-web marked as pending
Control: tag -1 pending Hello, Bug #924706 in icedtea-web reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/java-team/icedtea-web/commit/5c158c34dfca44d235256a18dcd4e756d2864de1 Fixed the installation of the CLI tools alternatives (Closes: #924706) (this message was generated automatically) -- Greetings https://bugs.debian.org/924706
Processed: Bug #924706 in icedtea-web marked as pending
Processing control commands: > tag -1 pending Bug #924706 [icedtea-netx] icedtea-netx: javaws symlink is broken Added tag(s) pending. -- 924706: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924706 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#924348: marked as done (CVE-2019-7629)
Your message dated Sun, 17 Mar 2019 23:05:21 + with message-id and subject line Bug#924348: fixed in tintin++ 2.01.5-2 has caused the Debian Bug report #924348, regarding CVE-2019-7629 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.) -- 924348: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924348 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: tintin++ Severity: grave Tags: security Please see http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-7629 Cheers, Moritz --- End Message --- --- Begin Message --- Source: tintin++ Source-Version: 2.01.5-2 We believe that the bug you reported is fixed in the latest version of tintin++, 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 924...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jozsef Nagy (supplier of updated tintin++ 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: Thu, 14 Mar 2019 20:27:42 +0100 Source: tintin++ Architecture: source Version: 2.01.5-2 Distribution: unstable Urgency: high Maintainer: Jozsef Nagy Changed-By: Jozsef Nagy Closes: 924348 Changes: tintin++ (2.01.5-2) unstable; urgency=high . * Add security patch - backport fix of the following security bug: - CVE-2019-7629: Stack-based buffer overflow in the strip_vt102_codes function allows remote attackers to execute arbitrary code by sending a long message to the client. (Closes: #924348) Checksums-Sha1: 261363c5fe93231929b88cfafd8b6b71f984dc2c 1756 tintin++_2.01.5-2.dsc e5f9d52c524a8812610695ff28bc01db18ae464b 20732 tintin++_2.01.5-2.debian.tar.xz 76a926ab901265753d6c5861e917d3986f828cc8 5945 tintin++_2.01.5-2_source.buildinfo Checksums-Sha256: 42e95fcc6c99faae1577db77686dae023b748d5eebe368aca00f94e2fcef16c0 1756 tintin++_2.01.5-2.dsc b8c4dbaa957e8a97768a3e3e918fcb6eb33a871a74994b4c576157095fd449d3 20732 tintin++_2.01.5-2.debian.tar.xz ec049774173bf1725388cace309e0a9f924d2676e5036676bf9e6f11f625f2de 5945 tintin++_2.01.5-2_source.buildinfo Files: 08519b6665a77a9fa4cec2b08938297d 1756 games optional tintin++_2.01.5-2.dsc cf40a00831c2cae40a38c3e46db1cee9 20732 games optional tintin++_2.01.5-2.debian.tar.xz 2b80fefee1067747b976f4f93413cfef 5945 games optional tintin++_2.01.5-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAlyOzq8ACgkQweDZLphv fH77Zg/+Jhyal96+llviU/c7LaLwcUDSo9XN/JdlTzyNGQpTZydp+HHBnq2j256b L9Whs+/B6jDExurXU9ZEN51O9+E4PS2JlORtpG7RMLRdXo3YgvAn/BY7cHQH0+LZ t/7Rojbr9b3fd2f2bLLKD2dkyGZOxvsHRG+ZtYX/NVTTjjBjjJMBWnyy2PzU78tT dE6vAUt2j28a/ILHHm8b8zan3YCLGr+gYyZ4SWlPLPZHiIVpxMDBIuVbuIJsMjxN +1ZiFAY2JylY+VDb1PkdhB9VR6cPNHrY16mC2JCZB7nQf+97/SrovzoHMIIHUjEp NPjbOQUCfnCPp2fSkewsF61lqGdWfQrViGIiDfV8KbblUBWfZh1cXdcqs65SQ9a+ 4KoNpqvD2qsser87GzBIFxWUF7YFZ4du01DWFPp+1sRaoSnckxIGZC03/140QXdS 5LmLEKG9+LJxbZTikO9zqv8F0gyRQexi88nUa0UzXsa/98grkqFyBUoLFraihjgw 7l4fbZRgNgdkm1UWvIbX3aG58gFMPHQ1Ee96B7CyCBTUIwnbhD3FpGBrEK318e5j Sqs/TJ2jmQrhqv/d2a7IMt/CjrANf/vQG5gojJEf30XtoPBTs7IzSt0MVtHjucDx 37c/lneMzdUQG6yQ4ri8xsOTUnsRuQWzkr76Tu6Ttdsr0WWBb2o= =7ZAC -END PGP SIGNATURE End Message ---
Bug#924807: [Pkg-javascript-devel] Bug#924807: Bugs come from conflict between node-uglify and node-uglify-js
Quoting Jonas Smedegaard (2019-03-17 23:48:57) > Quoting Xavier (2019-03-17 23:12:51) > > Control: reassign 924807 uglify-js > > Control: reassign 924809 uglify-js > > Control: merge 924807 924809 > > > > Bug seems to come from conflict between > > https://tracker.debian.org/pkg/uglify-js and > > https://tracker.debian.org/pkg/uglifyjs: webpack can't now be installed > > with uglifyjs > > Problem is packages depending on uglifyjs and webpack together: webpack > depends indirectly on node-uglify 2.x, whereas uglifyjs is either a > virtual package provided by node-uglify 2.x or (since recently) a real > package depending on node-uglyfy-js 3.x. > > Yes, the problem emerged when node-uglify was introduced as a real > package, but the fix is for those packages depending on uglifyjs and > webpack together to depend on node-uglify 2.x instead of the virtual > package. > > Please revert these reassignments: This cannot be fixed in uglifyjs 3.x. Put differently, the problem is packages depending both unversioned and transitively versioned on uglifyjs - that works only as long as the transitive dependency happens to be newest major release of uglifyjs. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#924807: [Pkg-javascript-devel] Bug#924807: Bugs come from conflict between node-uglify and node-uglify-js
Quoting Xavier (2019-03-17 23:12:51) > Control: reassign 924807 uglify-js > Control: reassign 924809 uglify-js > Control: merge 924807 924809 > > Bug seems to come from conflict between > https://tracker.debian.org/pkg/uglify-js and > https://tracker.debian.org/pkg/uglifyjs: webpack can't now be installed > with uglifyjs Problem is packages depending on uglifyjs and webpack together: webpack depends indirectly on node-uglify 2.x, whereas uglifyjs is either a virtual package provided by node-uglify 2.x or (since recently) a real package depending on node-uglyfy-js 3.x. Yes, the problem emerged when node-uglify was introduced as a real package, but the fix is for those packages depending on uglifyjs and webpack together to depend on node-uglify 2.x instead of the virtual package. Please revert these reassignments: This cannot be fixed in uglifyjs 3.x. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#924808: lua-nvim: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity
On Sun, Mar 17, 2019 at 07:09:44PM +0100, Lucas Nussbaum wrote: > Source: lua-nvim > Version: 0.1.0-1-1 > Severity: serious > Tags: buster sid > User: debian...@lists.debian.org > Usertags: qa-ftbfs-20190315 qa-ftbfs > Justification: FTBFS in buster on amd64 Hello Lucas. I was able to reproduce this hang too, but I believe it's fixed in 0.1.0-1-2 which is now in testing. Can you double-check with version 0.1.0-1-2? Thanks.
Processed: tagging 924764, tagging 924651
Processing commands for cont...@bugs.debian.org:
> tags 924764 + sid buster
Bug #924764 [src:mingw-ocaml] mingw-ocaml: FTBFS (cp: cannot stat
'objinfo_helper': No such file or directory)
Added tag(s) buster and sid.
> tags 924651 + sid buster
Bug #924651 {Done: gud...@gudjon.org (Gudjon I. Gudjonsson)} [src:pyqwt5]
pyqwt5: FTBFS (An internal error occured. Please report all the output)
Added tag(s) buster and sid.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
924651: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924651
924764: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924764
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#807666: reopen 807666, it should be fixed properly
Hi Alastair, On Thu, 14 Mar 2019 22:37:45 +0100 Ana Guerrero Lopez wrote: > I have sent a patch to upstream that should fix the issue: > https://lists.mpich.org/pipermail/discuss/2019-March/011160.html I've queued up this patch in my anbe/alternatives branch that hasn't been acted upon, yet. If you want, I can go ahead with an upload of mpich. There are also some Breaks missing against mpich in openmpi (I've just rebased the corresponding commit on master, also to be found in anbe/alternatives) and for lam I also sent corresponding patches, hopefully camm finds some time for it. So with three more mpi uploads we should hopefully be ready for buster :-) Andreas
Bug#924807: [Pkg-javascript-devel] Bug#924807: Bugs come from conflict between node-uglify and node-uglify-js
Le 17/03/2019 à 23:12, Xavier a écrit : > Bug seems to come from conflict between > https://tracker.debian.org/pkg/uglify-js and > https://tracker.debian.org/pkg/uglifyjs: webpack can't now be installed > with uglifyjs node-jscharset build-depends on both webpack and uglifyjs: * webpack depends on node-uglify via node-uglifyjs-webpack-plugin (and some other), provided by src:uglifyjs renamed later to src:uglify-js * uglifyjs is now provided by src:uglify-js, conflicts with node-uglify * src:uglify-js does not provide node-uglify but node-uglify-js instead
Processed: Re: libxml-twig-perl: expand_external_ents fails to work as documented
Processing commands for cont...@bugs.debian.org: > severity 842893 grave Bug #842893 [src:libxml-twig-perl] libxml-twig-perl: CVE-2016-9180: expand_external_ents fails to work as documented Severity set to 'grave' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 842893: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842893 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#898634: marked as done (kmail: efail attack against S/MIME)
Your message dated Sun, 17 Mar 2019 23:24:13 +0100 with message-id <4145727.q3mdy22fzh@tuxin> and subject line Re: Bug#898634: kmail: efail attack against S/MIME has caused the Debian Bug report #898634, regarding kmail: efail attack against S/MIME 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.) -- 898634: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898634 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: kmail Severity: grave Tags: security Justification: user security hole Hi, as you may already know, a paper was published this morning describing a vulnerability known as efail against S/MIME and PGP/MIME implementations in various mail clients. This vulnerability allows an attacker with read/write access to encrypted mail to retrieve the plaintext provided HTML mails are enabled, as well as loading of remote content. The paper indicates that the PGP/MIME implementation in kmail is not vulnerable, but the S/MIME is. It might be possible that the vulnerability is in an underlying library, so feel free to reassign if needed. It's likely we'll have to issue a DSA for this. Regards, -- Yves-Alexis -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (450, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.16.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), LANGUAGE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Hey Salvatore, > According to the update in the security-tracker done by Moritz for > https://salsa.debian.org/security-tracker-team/security-tracker/commit/ed21b > b0c20a2272745fb959f4c1da58a44ce32e7#4716ef5aa8f2742228ba3b3633215c8b808565e3 > _72290_72286 > > we might close this related issue for kmail, but not doing so, prefer > to leave it to you in case you agree. Thanks for finding one of the left overs of efail. This one can be closed. The both sub issues (#899127, #899128) fixed the issue inside Debian. hefee signature.asc Description: This is a digitally signed message part. --- End Message ---
Bug#924807: Bugs come from conflict between node-uglify and node-uglify-js
Control: reassign 924807 uglify-js Control: reassign 924809 uglify-js Control: merge 924807 924809 Bug seems to come from conflict between https://tracker.debian.org/pkg/uglify-js and https://tracker.debian.org/pkg/uglifyjs: webpack can't now be installed with uglifyjs Le 17/03/2019 à 19:05, Lucas Nussbaum a écrit : > Source: node-jschardet > Version: 1.6.0+dfsg-1 > Severity: serious > Tags: buster sid > User: debian...@lists.debian.org > Usertags: qa-ftbfs-20190315 qa-ftbfs > Justification: FTBFS in buster on amd64 > > Hi, > > During a rebuild of all packages in buster (in a buster chroot, not a > sid chroot), your package failed to build on amd64. > > Relevant part (hopefully): >> +--+ >> | Install package build dependencies >> | >> +--+ >> >> >> Setup apt archive >> - >> >> Merged Build-Depends: debhelper (>= 9), dh-buildinfo, nodejs, uglifyjs, >> webpack >> Filtered Build-Depends: debhelper (>= 9), dh-buildinfo, nodejs, uglifyjs, >> webpack >> dpkg-deb: building package 'sbuild-build-depends-node-jschardet-dummy' in >> '/<>/resolver-wJ4w5E/apt_archive/sbuild-build-depends-node-jschardet-dummy.deb'. >> dpkg-scanpackages: warning: Packages in archive but missing from override >> file: >> dpkg-scanpackages: warning: sbuild-build-depends-core-dummy >> sbuild-build-depends-node-jschardet-dummy >> dpkg-scanpackages: info: Wrote 2 entries to output Packages file. >> Ign:1 copy:/<>/resolver-wJ4w5E/apt_archive ./ InRelease >> Get:2 copy:/<>/resolver-wJ4w5E/apt_archive ./ Release [963 B] >> Ign:3 copy:/<>/resolver-wJ4w5E/apt_archive ./ Release.gpg >> Get:4 copy:/<>/resolver-wJ4w5E/apt_archive ./ Sources [518 B] >> Get:5 copy:/<>/resolver-wJ4w5E/apt_archive ./ Packages [600 B] >> Fetched 2081 B in 0s (0 B/s) >> Reading package lists... >> Reading package lists... >> >> Install node-jschardet build dependencies (apt-based resolver) >> -- >> >> Installing build dependencies >> Reading package lists... >> Building dependency tree... >> Reading state information... >> Some packages could not be installed. This may mean that you have >> requested an impossible situation or if you are using the unstable >> distribution that some required packages have not yet been created >> or been moved out of Incoming. >> The following information may help to resolve the situation: >> >> The following packages have unmet dependencies: >> sbuild-build-depends-node-jschardet-dummy : Depends: webpack but it is not >> going to be installed >> E: Unable to correct problems, you have held broken packages. >> apt-get failed. > > The full build log is available from: > > http://aws-logs.debian.net/2019/03/15/node-jschardet_1.6.0+dfsg-1_testing.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. >
Processed: Bugs come from conflict between node-uglify and node-uglify-js
Processing control commands: > reassign 924807 uglify-js Bug #924807 [uglify-js] node-jschardet: FTBFS: build-dependency not installable: webpack Bug #924809 [uglify-js] node-timeago.js: FTBFS: build-dependency not installable: webpack Ignoring request to reassign bug #924807 to the same package Ignoring request to reassign bug #924809 to the same package > reassign 924809 uglify-js Bug #924809 [uglify-js] node-timeago.js: FTBFS: build-dependency not installable: webpack Bug #924807 [uglify-js] node-jschardet: FTBFS: build-dependency not installable: webpack Ignoring request to reassign bug #924809 to the same package Ignoring request to reassign bug #924807 to the same package > merge 924807 924809 Bug #924807 [uglify-js] node-jschardet: FTBFS: build-dependency not installable: webpack Bug #924809 [uglify-js] node-timeago.js: FTBFS: build-dependency not installable: webpack Bug #924809 [uglify-js] node-timeago.js: FTBFS: build-dependency not installable: webpack Merged 924807 924809 -- 924807: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924807 924809: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924809 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bugs come from conflict between node-uglify and node-uglify-js
Processing control commands: > reassign 924807 uglify-js Bug #924807 [src:node-jschardet] node-jschardet: FTBFS: build-dependency not installable: webpack Bug reassigned from package 'src:node-jschardet' to 'uglify-js'. No longer marked as found in versions node-jschardet/1.6.0+dfsg-1. Ignoring request to alter fixed versions of bug #924807 to the same values previously set > reassign 924809 uglify-js Bug #924809 [src:node-timeago.js] node-timeago.js: FTBFS: build-dependency not installable: webpack Bug reassigned from package 'src:node-timeago.js' to 'uglify-js'. No longer marked as found in versions node-timeago.js/3.0.2+dfsg-1. Ignoring request to alter fixed versions of bug #924809 to the same values previously set > merge 924807 924809 Bug #924807 [uglify-js] node-jschardet: FTBFS: build-dependency not installable: webpack Bug #924809 [uglify-js] node-timeago.js: FTBFS: build-dependency not installable: webpack Merged 924807 924809 -- 924807: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924807 924809: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924809 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: unblock: kaddressbook/4:18.08.3-3
Processing control commands:
> block 910731 by -1
Bug #910731 {Done: Sandro Knauß } [kaddressbook] KAdressebook
missing to dependency on akonadi
910731 was not blocked by any bugs.
910731 was not blocking any bugs.
Added blocking bug(s) of 910731: 924882
--
910731: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910731
924882: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924882
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#923416: marked as done (advancecomp: CVE-2019-9210)
Your message dated Sun, 17 Mar 2019 21:49:10 + with message-id and subject line Bug#923416: fixed in advancecomp 2.1-2 has caused the Debian Bug report #923416, regarding advancecomp: CVE-2019-9210 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.) -- 923416: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923416 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: advancecomp Version: 2.1-1 Severity: important Tags: security upstream Forwarded: https://sourceforge.net/p/advancemame/bugs/277/ Hi, The following vulnerability was published for advancecomp. CVE-2019-9210[0]: | In AdvanceCOMP 2.1, png_compress in pngex.cc in advpng has an integer | overflow upon encountering an invalid PNG size, which results in an | attempted memcpy to write into a buffer that is too small. (There is | also a heap-based buffer over-read.) If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2019-9210 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-9210 [1] https://sourceforge.net/p/advancemame/bugs/277/ Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: advancecomp Source-Version: 2.1-2 We believe that the bug you reported is fixed in the latest version of advancecomp, 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 923...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Piotr Ożarowski (supplier of updated advancecomp 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: Sun, 17 Mar 2019 22:28:03 +0100 Source: advancecomp Binary: advancecomp advancecomp-dbgsym Architecture: source amd64 Version: 2.1-2 Distribution: unstable Urgency: high Maintainer: Piotr Ożarowski Changed-By: Piotr Ożarowski Description: advancecomp - collection of recompression utilities Closes: 923416 Changes: advancecomp (2.1-2) unstable; urgency=high . [ Salvatore Bonaccorso ] * Fix a buffer overflow with image of invalid size (CVE-2019-9210) (Closes: #923416) Checksums-Sha1: 260ea90be67369fe0af83d66da2ba8880cdfbd1d 1755 advancecomp_2.1-2.dsc d1cf5f57ec0d69a7e83d853ab2ad0e51e44265c7 3840 advancecomp_2.1-2.debian.tar.xz aef3fe4e9df8c5883ef96426cb8ce98a89cc8ee8 2466472 advancecomp-dbgsym_2.1-2_amd64.deb 908db7aa1b8647b0512cec43f817841b2f2429cd 5819 advancecomp_2.1-2_amd64.buildinfo ed97750bc87482d9ff0de0ff0e2b952c245fc02c 205300 advancecomp_2.1-2_amd64.deb Checksums-Sha256: 691395e99618b5d7602682a92a2c99b553f092c7dc49e29456fcac2c7911c534 1755 advancecomp_2.1-2.dsc 0412a369bc6a7aef2ac6b7a7c8dc6934c4908db52de288a668999b818b91c701 3840 advancecomp_2.1-2.debian.tar.xz 9529f9413296dbf93989a11342e0aff14c60213f160c35c5e82c764df9f8e470 2466472 advancecomp-dbgsym_2.1-2_amd64.deb 019623fd9a9695de0db96cd41a1856ac3192603f1843b68f6609037078dd4c3b 5819 advancecomp_2.1-2_amd64.buildinfo 8e3984df8f5fe496b662bb2d44beeca3ee592534dd69b1ca92132cb181b0d330 205300 advancecomp_2.1-2_amd64.deb Files: 4a5ded0aa13b337b47c3ccfc2366bca5 1755 utils optional advancecomp_2.1-2.dsc 9aaa9a34ee28472fdb2e62a9240879e1 3840 utils optional advancecomp_2.1-2.debian.tar.xz 5dc903a62d10e972b2927a910b881c74 2466472 debug optional advancecomp-dbgsym_2.1-2_amd64.deb d80cefecf64c11ea0c82df7549bf919e 5819 utils optional advancecomp_2.1-2_amd64.buildinfo 8e73051898e51c91d7ab612c593fe8b4 205300 utils optional advancecomp_2.1-2_amd64.deb -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEHS+omFjar2IXhi33rvbxoqdFdkUFAlyOvWsACgkQrvbxoqdF dkXwKhAAtymL8WttnZEf66CQp70W8pcKo2+fwjFWdZpX1PwpYlBZv/x+5oZg1vN6 /B6i68FUD2au8Dwms3IHbV//tPOMXdJAfsv1wT5exala3y+a+TS8bxVrBo92t0Mw FwpA9PYtoFpvoGuaCbvE6HhhM4FCXLoFE2NBsqoyZuuQoGodQBjZMhyzUC8Yn2yq P2W/Kk/nL1a0eLBpMagASI+LC6YWDxDHq8+QsSxbxnKS6lTUkoDHBxQga4DX171V 9BHydGKbsaJv8zHVeFviA64kMC5KRGRjXD7czBEXEEwh/xtJdkhxNOs9NTgcubKf tsDIgXjsU5baSZ7J/RmfQdddCRIRlx1SLSSz47rt8jTVy0n0mlFObTExNF/tPIEl +x91V3KkWyZcPj+jmW8OJgYu3HNZRL9433lx0qgoQL3AyfY75xPowxD7Rn7NN5Zk yWWQqhNOL4LLpyM0m
Bug#853016: marked as done (nodm: regression: restarts during upgrade, causing data loss)
Your message dated Sun, 17 Mar 2019 21:36:18 +
with message-id
and subject line Bug#853016: fixed in nodm 0.13-5
has caused the Debian Bug report #853016,
regarding nodm: regression: restarts during upgrade, causing data loss
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.)
--
853016: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853016
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nodm
Version: 0.13-1
Upon doing an aptitude etc. full-upgrade etc.
one of the packages being upgraded is nodm.
Upon reaching nodm, the entire X-windows is lost and the user thinks the
computer has rebooted and all his work in other windows is lost.
He then sees a tty1 prompt and realizes it is not a complete reboot.
Later nodm restarts and he is back in X-windows. But his work is still
lost.
Can't you warn (via whiptail) or delay restarting or something?
--- End Message ---
--- Begin Message ---
Source: nodm
Source-Version: 0.13-5
We believe that the bug you reported is fixed in the latest version of
nodm, 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 853...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Mike Gabriel (supplier of updated nodm 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: SHA256
Format: 1.8
Date: Sun, 17 Mar 2019 22:18:29 +0100
Source: nodm
Binary: nodm
Architecture: source
Version: 0.13-5
Distribution: unstable
Urgency: medium
Maintainer: Mike Gabriel
Changed-By: Mike Gabriel
Description:
nodm - automatic display manager
Closes: 853016
Changes:
nodm (0.13-5) unstable; urgency=medium
.
[ Simon McVittie ]
* Non-maintainer upload
* d/rules: Don't restart nodm, fixing regressions from the move to
debhelper compat level 12 (Closes: #853016)
* d/control: Add missing ${misc:Pre-Depends} needed in compat level 12
* postinst: Create reboot-required flag file to notify apt frontends
that the user should reboot when convenient
Checksums-Sha1:
c2ee63c1b953cef51d093edd7145fe347d632e2e 2000 nodm_0.13-5.dsc
2f1d2465b61dab51d7345a8da5305c1eb41714e7 31856 nodm_0.13-5.debian.tar.xz
9c55bc56712557df6e6b587909ef7888c453800d 6709 nodm_0.13-5_source.buildinfo
Checksums-Sha256:
bbc289fd04e3ce074c7fb0e5f6409d38b45d0ebb1f8ac1923df5c47c73a0dc6c 2000
nodm_0.13-5.dsc
3060ed5cc3c7c6a9ea05eedfd98487c759ff074d70522bcfc514e430061ec90d 31856
nodm_0.13-5.debian.tar.xz
5c96b5dee9710ee0e416bbcfb8f9d583a4940eb5206a49f8e15f7f5d840223f2 6709
nodm_0.13-5_source.buildinfo
Files:
b62943f0d31c475e8dd105993f775c33 2000 misc optional nodm_0.13-5.dsc
6d819af13cf7c15bc5a5796fb777679c 31856 misc optional nodm_0.13-5.debian.tar.xz
9d408df3409d0267ca77b29ef9af3d40 6709 misc optional
nodm_0.13-5_source.buildinfo
-BEGIN PGP SIGNATURE-
iQJJBAEBCAAzFiEEm/uu6GwKpf+/IgeCmvRrMCV3GzEFAlyOucIVHHN1bndlYXZl
ckBkZWJpYW4ub3JnAAoJEJr0azAldxsx9AwP/1n6PCQynYtH5J6RQ9Bmmke/nIkS
S9zJjdni1PaMz7M527gMPuRIEi9D7gAYo1Bi2wGR0QEdLPq13mPQY5gbwDD/2w6o
/fhOoaq3njGUXHML6P4+WEL/DrcKbqKxkms3jVCvWnluY4TxejC6bLkhLoxrxhlT
X5K33lJwYq6hyeCpf4rJUCepjxs9CNbIPhtyXabNKBRmtHPrWcdpA+uI6F4D9FlH
xAkGv08NZttHdjMJb6jOR7EZdYHv0/HduyYH9NdWaFInTurKXerc6zFUBHkgmw4b
Aag1vvR64YIhT3fBIut37aBovPHEbVMV6IBVEQupmWELuJ+zyyQ274NrVpvS1ltX
IcU3k9D1Yvwpc3igOg0kLDGAbp7X6/s6BRSm+ORxp00Tdev+1dCUIa6jpyQsAHEX
B473Nui0R2oMa7urmHr7hmAVwF9rLG1e1PLWAOkq/UuoBxTInohd0NpOsyIgsCPG
ojY36Azh6S/2KNIDP46fQnmZcVCSqgGCdQL3It109jhGTLPSkwPRU7xbMHhiD3iv
hw8nb8CoYS0j5BGIQZkuDIJ5RgrUqU1pycqFRsoWOo4ds35wp7HcPThgKiVNtVTO
sSoFSk2C7VZDK2cCFQWzURQeEoAf+x2SkZHPLDPt7Xqrl0MXsxOIAx30BDaR5P4M
s9r9XmN8cqeg9wDz
=p98x
-END PGP SIGNATURE End Message ---
Bug#919980: marked as done (nodm: regression: restarts during upgrade, causing data loss)
Your message dated Sun, 17 Mar 2019 21:36:18 +
with message-id
and subject line Bug#853016: fixed in nodm 0.13-5
has caused the Debian Bug report #853016,
regarding nodm: regression: restarts during upgrade, causing data loss
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.)
--
853016: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853016
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nodm
Got an idea:
As there is a very high chance the user is using nodm at the time he
runs apt-get upgrade etc. thinking ho-hum, just another upgrade of 50
packages...
and an even higher chance if pidof nodm returns positive,
and a good chance that he was browsing something important, and editing
several files,
so instead of making it like the power went out and restarted,
why not have the update script,
kindly ask the user "Ready to update nodm? First close all your
windows" via dialog(1) etc.
--- End Message ---
--- Begin Message ---
Source: nodm
Source-Version: 0.13-5
We believe that the bug you reported is fixed in the latest version of
nodm, 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 853...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Mike Gabriel (supplier of updated nodm 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: SHA256
Format: 1.8
Date: Sun, 17 Mar 2019 22:18:29 +0100
Source: nodm
Binary: nodm
Architecture: source
Version: 0.13-5
Distribution: unstable
Urgency: medium
Maintainer: Mike Gabriel
Changed-By: Mike Gabriel
Description:
nodm - automatic display manager
Closes: 853016
Changes:
nodm (0.13-5) unstable; urgency=medium
.
[ Simon McVittie ]
* Non-maintainer upload
* d/rules: Don't restart nodm, fixing regressions from the move to
debhelper compat level 12 (Closes: #853016)
* d/control: Add missing ${misc:Pre-Depends} needed in compat level 12
* postinst: Create reboot-required flag file to notify apt frontends
that the user should reboot when convenient
Checksums-Sha1:
c2ee63c1b953cef51d093edd7145fe347d632e2e 2000 nodm_0.13-5.dsc
2f1d2465b61dab51d7345a8da5305c1eb41714e7 31856 nodm_0.13-5.debian.tar.xz
9c55bc56712557df6e6b587909ef7888c453800d 6709 nodm_0.13-5_source.buildinfo
Checksums-Sha256:
bbc289fd04e3ce074c7fb0e5f6409d38b45d0ebb1f8ac1923df5c47c73a0dc6c 2000
nodm_0.13-5.dsc
3060ed5cc3c7c6a9ea05eedfd98487c759ff074d70522bcfc514e430061ec90d 31856
nodm_0.13-5.debian.tar.xz
5c96b5dee9710ee0e416bbcfb8f9d583a4940eb5206a49f8e15f7f5d840223f2 6709
nodm_0.13-5_source.buildinfo
Files:
b62943f0d31c475e8dd105993f775c33 2000 misc optional nodm_0.13-5.dsc
6d819af13cf7c15bc5a5796fb777679c 31856 misc optional nodm_0.13-5.debian.tar.xz
9d408df3409d0267ca77b29ef9af3d40 6709 misc optional
nodm_0.13-5_source.buildinfo
-BEGIN PGP SIGNATURE-
iQJJBAEBCAAzFiEEm/uu6GwKpf+/IgeCmvRrMCV3GzEFAlyOucIVHHN1bndlYXZl
ckBkZWJpYW4ub3JnAAoJEJr0azAldxsx9AwP/1n6PCQynYtH5J6RQ9Bmmke/nIkS
S9zJjdni1PaMz7M527gMPuRIEi9D7gAYo1Bi2wGR0QEdLPq13mPQY5gbwDD/2w6o
/fhOoaq3njGUXHML6P4+WEL/DrcKbqKxkms3jVCvWnluY4TxejC6bLkhLoxrxhlT
X5K33lJwYq6hyeCpf4rJUCepjxs9CNbIPhtyXabNKBRmtHPrWcdpA+uI6F4D9FlH
xAkGv08NZttHdjMJb6jOR7EZdYHv0/HduyYH9NdWaFInTurKXerc6zFUBHkgmw4b
Aag1vvR64YIhT3fBIut37aBovPHEbVMV6IBVEQupmWELuJ+zyyQ274NrVpvS1ltX
IcU3k9D1Yvwpc3igOg0kLDGAbp7X6/s6BRSm+ORxp00Tdev+1dCUIa6jpyQsAHEX
B473Nui0R2oMa7urmHr7hmAVwF9rLG1e1PLWAOkq/UuoBxTInohd0NpOsyIgsCPG
ojY36Azh6S/2KNIDP46fQnmZcVCSqgGCdQL3It109jhGTLPSkwPRU7xbMHhiD3iv
hw8nb8CoYS0j5BGIQZkuDIJ5RgrUqU1pycqFRsoWOo4ds35wp7HcPThgKiVNtVTO
sSoFSk2C7VZDK2cCFQWzURQeEoAf+x2SkZHPLDPt7Xqrl0MXsxOIAx30BDaR5P4M
s9r9XmN8cqeg9wDz
=p98x
-END PGP SIGNATURE End Message ---
Bug#924630: marked as done (golang-1.11: CVE-2019-9741: CRLF injection in net/http)
Your message dated Sun, 17 Mar 2019 21:34:53 + with message-id and subject line Bug#924630: fixed in golang-1.11 1.11.6-1 has caused the Debian Bug report #924630, regarding golang-1.11: CVE-2019-9741: CRLF injection in net/http 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.) -- 924630: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924630 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: golang-1.11 Version: 1.11.5-1 Severity: grave Tags: security upstream Hi, The following vulnerability was published for golang-1.11. CVE-2019-9741[0]: | An issue was discovered in net/http in Go 1.11.5. CRLF injection is | possible if the attacker controls a url parameter, as demonstrated by | the second argument to http.NewRequest with \r\n followed by an HTTP | header or a Redis command. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2019-9741 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-9741 [1] https://bugzilla.redhat.com/show_bug.cgi?id=1688230 Regards, Salvatore --- End Message --- --- Begin Message --- Source: golang-1.11 Source-Version: 1.11.6-1 We believe that the bug you reported is fixed in the latest version of golang-1.11, 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 924...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Hudson-Doyle (supplier of updated golang-1.11 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: SHA256 Format: 1.8 Date: Mon, 18 Mar 2019 09:37:17 +1300 Source: golang-1.11 Binary: golang-1.11-go golang-1.11-src golang-1.11-doc golang-1.11 Architecture: source Version: 1.11.6-1 Distribution: unstable Urgency: medium Maintainer: Go Compiler Team Changed-By: Michael Hudson-Doyle Description: golang-1.11 - Go programming language compiler - metapackage golang-1.11-doc - Go programming language - documentation golang-1.11-go - Go programming language compiler, linker, compiled stdlib golang-1.11-src - Go programming language - source files Closes: 924630 Changes: golang-1.11 (1.11.6-1) unstable; urgency=medium . * New upstream version 1.11.6, fixing CVE-2019-9741. (Closes: #924630) * Delete d/patches/0005-fix-MIPS-SGTconst-with-shift-rules.patch, applied upstream. * Refreshed other patches. Checksums-Sha1: ccfb8fa4ba8fb92c4d3a454047f5f6155b0c 2583 golang-1.11_1.11.6-1.dsc 3da44308ca85c4b78b62b735060ebb2479ec1dcf 21113406 golang-1.11_1.11.6.orig.tar.gz 65377dd926fc2ea317ad89bcf4e5f29a63a15809 29452 golang-1.11_1.11.6-1.debian.tar.xz 1292e3dece03973a4d17333ad93b2b982ef67a2b 6310 golang-1.11_1.11.6-1_source.buildinfo Checksums-Sha256: 32f66ed7023c65cfd17f28d74c995b8e3ce73c9a3ae42258e5f5c18367275c65 2583 golang-1.11_1.11.6-1.dsc a96da1425dcbec094736033a8a416316547f8100ab4b72c31d4824d761d3e133 21113406 golang-1.11_1.11.6.orig.tar.gz cdcef4a84a37012c8eb30c4317ae3192f746bd83bcf801783e316450598c97b4 29452 golang-1.11_1.11.6-1.debian.tar.xz fe7bf90fc14ca917dff9110dd92fa75fd9e8a720e8bbfa6704ba1eb7782cda91 6310 golang-1.11_1.11.6-1_source.buildinfo Files: 8fcbe514aef4b58831ae20bef82297d6 2583 devel optional golang-1.11_1.11.6-1.dsc 1d1304eb9f2d0de162b46e17ed51baf1 21113406 devel optional golang-1.11_1.11.6.orig.tar.gz d745be6826b64a9039a61faabff955e1 29452 devel optional golang-1.11_1.11.6-1.debian.tar.xz 66f95cf4084d700cef442c3b07690acf 6310 devel optional golang-1.11_1.11.6-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEiiBE+E9xaoW3f/djEd9ClMyjmJMFAlyOtsAACgkQEd9ClMyj mJPwlw//d/Ped+hFBkY8w6uhMmX8o6Wvz8qt67JpM+E/vvr53mPcbNtvwylLUHmT 8qm/6S14V4nrqRL97Z1Nb4qRbzC8iT7biNnzfIreeexxcf5yk1OMX5uPmfe1ZpUM QFFHri83n+U1fYnk88iYez6UxIyismbgc+3sxqfeR2A1hj4Dzn/Dh+AM7rr2zN4b rNQXCWg9Q1mD4MzSdl2iCn2+sX68rXhNb3j9+Bq5cNI0OhF/9kTKVjkanPeK4mYm 57BjU33fkCMZYp74//i7zMdtA0LkwsepWhq2qEbEInwGryQCEBEIpdzaWt2w3kwg M77PdfaN+jXp+b5VS1Dz9mgvvrz1/rwp72MjF1/B682dnkJiwzaoJjKcC3mwodl2 dvxUpA/ou8d1/6SpStMRpstV9SvQOIWGNkcsg2K3z75OHBKRn6qgbjY5KSrLDJHX Fp32sqshJkPEMW1dalYbGZfq5
Bug#924799: qtspeech-opensource-src: FTBFS: dh_auto_test: make -j4 check -Ctests/auto QT_HASH_SEED=0 QT_QPA_PLATFORM=minimal returned exit code 2
El domingo, 17 de marzo de 2019 18:06:30 -03 Lisandro Damián Nicanor Pérez Meyer escribió: > The problem seems to be different, as I can reproduce it on a porterbox > (except barriere also has no audio). Also FTBFS in a server with audio setup, unstable chroot. Something has changed since we last built this package. -- No hay preguntas tontas, solo tontos que no preguntan. personaje, en un mail del LugFi. Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
Bug#855686: icedtea-web: FTBFS: configure: error: Package requirements (mozilla-plugin) were not met
Control: tags -1 - pending Control: tags -1 + wontfix Control: close -1 The browser plugin has been removed in 1.7.1-1.
Processed: fix ftbfs bug metadata
Processing commands for cont...@bugs.debian.org: > # fix up reassign without affects > affects 923759 + src:mtj Bug #923759 [netlib-java] mtj: FTBFS in buster/sid Added indication that 923759 affects src:mtj > thanks Stopping processing here. Please contact me if you need assistance. -- 923759: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923759 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: icedtea-web: FTBFS: configure: error: Package requirements (mozilla-plugin) were not met
Processing control commands: > tags -1 - pending Bug #855686 [src:icedtea-web] icedtea-web: FTBFS: configure: error: Package requirements (mozilla-plugin) were not met Removed tag(s) pending. > tags -1 + wontfix Bug #855686 [src:icedtea-web] icedtea-web: FTBFS: configure: error: Package requirements (mozilla-plugin) were not met Added tag(s) wontfix. > close -1 Bug #855686 [src:icedtea-web] icedtea-web: FTBFS: configure: error: Package requirements (mozilla-plugin) were not met Marked Bug as done -- 855686: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855686 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug #924630 in golang marked as pending
Processing control commands: > tag -1 pending Bug #924630 [src:golang-1.11] golang-1.11: CVE-2019-9741: CRLF injection in net/http Ignoring request to alter tags of bug #924630 to the same tags previously set -- 924630: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924630 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#924630: Bug #924630 in golang marked as pending
Control: tag -1 pending Hello, Bug #924630 in golang reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/go-team/compiler/golang/commit/71582deb22213b82603e44203245ada54977355f New upstream version 1.11.6, fixing CVE-2019-9741. (Closes: #924630) * New upstream version 1.11.6, fixing CVE-2019-9741. (Closes: #924630) * Delete d/patches/0005-fix-MIPS-SGTconst-with-shift-rules.patch, applied upstream. * Refreshed other patches. (this message was generated automatically) -- Greetings https://bugs.debian.org/924630
Bug#924630: Bug #924630 in golang marked as pending
Control: tag -1 pending Hello, Bug #924630 in golang reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/go-team/compiler/golang/commit/71582deb22213b82603e44203245ada54977355f New upstream version 1.11.6, fixing CVE-2019-9741. (Closes: #924630) * New upstream version 1.11.6, fixing CVE-2019-9741. (Closes: #924630) * Delete d/patches/0005-fix-MIPS-SGTconst-with-shift-rules.patch, applied upstream. * Refreshed other patches. (this message was generated automatically) -- Greetings https://bugs.debian.org/924630
Processed: Bug #924630 in golang marked as pending
Processing control commands: > tag -1 pending Bug #924630 [src:golang-1.11] golang-1.11: CVE-2019-9741: CRLF injection in net/http Ignoring request to alter tags of bug #924630 to the same tags previously set -- 924630: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924630 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#924630: Bug #924630 in golang marked as pending
Control: tag -1 pending Hello, Bug #924630 in golang reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/go-team/compiler/golang/commit/0c508f9cd760bd475f41b8d067359da313cbd05c New upstream version 1.11.6, fixing CVE-2019-9741. (Closes: #924630) * New upstream version 1.11.6, fixing CVE-2019-9741. (Closes: #924630) * Delete d/patches/0005-fix-MIPS-SGTconst-with-shift-rules.patch, applied upstream. * Refreshed other patches. (this message was generated automatically) -- Greetings https://bugs.debian.org/924630
Processed: Bug #924630 in golang marked as pending
Processing control commands: > tag -1 pending Bug #924630 [src:golang-1.11] golang-1.11: CVE-2019-9741: CRLF injection in net/http Ignoring request to alter tags of bug #924630 to the same tags previously set -- 924630: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924630 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug #924630 in golang marked as pending
Processing control commands: > tag -1 pending Bug #924630 [src:golang-1.11] golang-1.11: CVE-2019-9741: CRLF injection in net/http Added tag(s) pending. -- 924630: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924630 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#924630: Bug #924630 in golang marked as pending
Control: tag -1 pending Hello, Bug #924630 in golang reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/go-team/compiler/golang/commit/0c508f9cd760bd475f41b8d067359da313cbd05c New upstream version 1.11.6, fixing CVE-2019-9741. (Closes: #924630) * New upstream version 1.11.6, fixing CVE-2019-9741. (Closes: #924630) * Delete d/patches/0005-fix-MIPS-SGTconst-with-shift-rules.patch, applied upstream. * Refreshed other patches. (this message was generated automatically) -- Greetings https://bugs.debian.org/924630
Bug#924799: qtspeech-opensource-src: FTBFS: dh_auto_test: make -j4 check -Ctests/auto QT_HASH_SEED=0 QT_QPA_PLATFORM=minimal returned exit code 2
El domingo, 17 de marzo de 2019 17:54:39 -03 Lisandro Damián Nicanor Pérez Meyer escribió: > Hi Lucas! > > El domingo, 17 de marzo de 2019 15:20:23 -03 Lucas Nussbaum escribió: > > Source: qtspeech-opensource-src > > Version: 5.11.3-2 > > Severity: serious > > Tags: buster sid > > User: debian...@lists.debian.org > > Usertags: qa-ftbfs-20190315 qa-ftbfs > > Justification: FTBFS in buster on amd64 > > > > Hi, > > > > During a rebuild of all packages in buster (in a buster chroot, not a > > sid chroot), your package failed to build on amd64. > > [snip] > > This: > > > "Failed to start audio output (error 1)" BFAIL : > And then: > > > FAIL! : tst_QTextToSpeech::volume() 'tts.volume() > 0.65' returned > > > FALSE. > > Makes me think if the test is failing due to no audio setup in your VMs. > Maybe we have hit an interesting bug which was never caught on the buildds? > Should a buildd have audio setup? The problem seems to be different, as I can reproduce it on a porterbox (except barriere also has no audio). Non the less I'm still interested in knowing if your VMs provide an audio setup. -- Mi experiencia me dice que lo que la gente quiere y necesita -en Indonesia, en Turquía, en Italia, en los Estados Unidos, en Brasil, en la Argentina o donde sea- es básicamente lo mismo. La gente quiere comida en la mesa, una vivienda básica, un gobierno que funcione, que en las fuerzas de seguridad haya personas confiables, a las que no tengan que tenerles miedo, educación y salud. ¡La gente de todo el mundo quiere lo mismo! Padre Thomas Michel, jesuita, especialista en diálogo interreligioso, en una entrevista de Elisabetta Piqué para La Nación, 27/09/2006. http://www.lanacion.com.ar/844069 Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
Bug#924825: marked as done (preggy: FTBFS: build-dependency not installable: python-tox)
Your message dated Sun, 17 Mar 2019 21:04:56 + with message-id and subject line Bug#924825: fixed in preggy 1.3.0-2 has caused the Debian Bug report #924825, regarding preggy: FTBFS: build-dependency not installable: python-tox 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.) -- 924825: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924825 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: preggy Version: 1.3.0-1 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20190315 qa-ftbfs Justification: FTBFS in buster on amd64 Hi, During a rebuild of all packages in buster (in a buster chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper (>= 9), dh-python, python-all, python-nose, > python-setuptools, python-six, python-tox, python-unidecode > Filtered Build-Depends: debhelper (>= 9), dh-python, python-all, python-nose, > python-setuptools, python-six, python-tox, python-unidecode > dpkg-deb: building package 'sbuild-build-depends-preggy-dummy' in > '/<>/resolver-ls7MMD/apt_archive/sbuild-build-depends-preggy-dummy.deb'. > dpkg-scanpackages: warning: Packages in archive but missing from override > file: > dpkg-scanpackages: warning: sbuild-build-depends-core-dummy > sbuild-build-depends-preggy-dummy > dpkg-scanpackages: info: Wrote 2 entries to output Packages file. > Ign:1 copy:/<>/resolver-ls7MMD/apt_archive ./ InRelease > Get:2 copy:/<>/resolver-ls7MMD/apt_archive ./ Release [963 B] > Ign:3 copy:/<>/resolver-ls7MMD/apt_archive ./ Release.gpg > Get:4 copy:/<>/resolver-ls7MMD/apt_archive ./ Sources [528 B] > Get:5 copy:/<>/resolver-ls7MMD/apt_archive ./ Packages [605 B] > Fetched 2096 B in 0s (0 B/s) > Reading package lists... > Reading package lists... > > Install preggy build dependencies (apt-based resolver) > -- > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > sbuild-build-depends-preggy-dummy : Depends: python-tox but it is not > installable > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://aws-logs.debian.net/2019/03/15/preggy_1.3.0-1_testing.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: preggy Source-Version: 1.3.0-2 We believe that the bug you reported is fixed in the latest version of preggy, 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 924...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Marcelo Jorge Vieira (supplier of updated preggy 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: SHA256 Format: 1.8 Date: Sun, 17 Mar 2019 16:37:32 -0300 Source: preggy Binary: python-preggy Architecture: source all Version: 1.3.0-2 Distribution: unstable Urgency: high Maintainer: Debian Python Modules Team Changed-By: Marcelo Jorge Vieira Description: python-preggy - Assertion library for Python Closes: 924825 Changes: preggy (1.3.0-2) unstable; urgency=high . * d/control: Remov
Bug#888935: node-xterm FTBFS: error TS2339: Property 'parentElement' does not exist on type 'never'
On Thu, 08 Mar 2018 17:53:27 + Ghislain Vaillant wrote:
> > Source: node-xterm
> > Version: 2.7.0+ds1-1
> > Severity: serious
> >
> > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/no
> > de-xterm.html
> >
> > ...
> >debian/rules override_dh_auto_build
> > make[1]: Entering directory '/build/1st/node-xterm-2.7.0+ds1'
> > tsc --project .
> > src/utils/Mouse.ts(30,80): error TS2339: Property 'parentElement'
> > does not exist on type 'never'.
> > debian/rules:19: recipe for target 'override_dh_auto_build' failed
> > make[1]: *** [override_dh_auto_build] Error 2
>
> No idea how to fix this. The package used to build fine.
>
> Without further context, I am clueless about what to do about it.
>
I had an attempt at this, but it is getting a bit hairy and I think it may be
time to call it quits. My recommendation is for jupyter-notebook to patch out
this functionality and not depend on node-xterm, and for this package to be RM
from Debian.
Details:
The steps I am taking:
1. https://salsa.debian.org/js-team/typescript-types/tree/wip/node-xterm-fix
- update typescript-types to include the missing modules
- there is an issue with jsdom which can't use the newest parse5 so we have
to forcibly use parse5 v4.0.0, which involves some extra tweaks to the
typescript-types package.
2. apply this patch to node-xterm
diff --git a/debian/rules b/debian/rules
index a981410..eb56bcc 100755
--- a/debian/rules
+++ b/debian/rules
@@ -8,7 +8,7 @@
override_dh_auto_configure:
mkdir -p node_modules/@types
- set -e; for i in chai jquery jsdom mocha node; do \
+ set -e; for i in chai glob jquery jsdom minimatch mocha node parse5
sizzle tough-cookie; do \
ln -sf /usr/lib/nodejs/@types/$$i node_modules/@types/$$i; done
COPY_AUX_FILES = \
@@ -16,7 +16,7 @@ COPY_AUX_FILES = \
cd $(1) && find -name *.css -exec cp --parents '{}' ../$(2) \; \
override_dh_auto_build:
- tsc --project .
+ tsc --moduleResolution Classic --project .
$(call COPY_AUX_FILES,src,lib)
# Otherwise browserify-lite complains
touch lib/addons/index.js
The next error is:
src/Terminal.integration.ts:13:22 - error TS2307: Cannot find module 'node-pty'.
13 import * as pty from 'node-pty';
~~
which looks like this repo: https://github.com/Microsoft/node-pty
However, I really have no idea why this should be necessary, since we didn't
need it in the previous version. Perhaps it used to be part of the standard
nodejs distribution and then they split it off?
Anyways this is getting into the realms of JS crap that I wanted to leave
behind forever.
X
--
GPG: ed25519/56034877E1F87C35
GPG: rsa4096/1318EFAC5FBBDBCE
https://github.com/infinity0/pubkeys.git
Bug#924799: qtspeech-opensource-src: FTBFS: dh_auto_test: make -j4 check -Ctests/auto QT_HASH_SEED=0 QT_QPA_PLATFORM=minimal returned exit code 2
Hi Lucas! El domingo, 17 de marzo de 2019 15:20:23 -03 Lucas Nussbaum escribió: > Source: qtspeech-opensource-src > Version: 5.11.3-2 > Severity: serious > Tags: buster sid > User: debian...@lists.debian.org > Usertags: qa-ftbfs-20190315 qa-ftbfs > Justification: FTBFS in buster on amd64 > > Hi, > > During a rebuild of all packages in buster (in a buster chroot, not a > sid chroot), your package failed to build on amd64. [snip] This: > > "Failed to start audio output (error 1)" BFAIL : And then: > > FAIL! : tst_QTextToSpeech::volume() 'tts.volume() > 0.65' returned FALSE. Makes me think if the test is failing due to no audio setup in your VMs. Maybe we have hit an interesting bug which was never caught on the buildds? Should a buildd have audio setup? -- Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
Processed: your mail
Processing commands for cont...@bugs.debian.org:
> forcemerge 923282 924797
Bug #923282 [freezegun] freezegun breaks cached-property autopkgtest
Bug #923282 [freezegun] freezegun breaks cached-property autopkgtest
Added tag(s) buster and sid.
Bug #924797 [freezegun] cached-property: FTBFS: dh_auto_test: pybuild --test -i
python{version} -p 3.7 returned exit code 13
Merged 923282 924797
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
923282: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923282
924797: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924797
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: found 923416 in 1.20-1
Processing commands for cont...@bugs.debian.org: > found 923416 1.20-1 Bug #923416 [src:advancecomp] advancecomp: CVE-2019-9210 Marked as found in versions advancecomp/1.20-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 923416: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923416 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: your mail
Processing commands for cont...@bugs.debian.org:
> reassign 924797 freezegun 0.3.11-0.1
Bug #924797 [src:cached-property] cached-property: FTBFS: dh_auto_test: pybuild
--test -i python{version} -p 3.7 returned exit code 13
Bug reassigned from package 'src:cached-property' to 'freezegun'.
No longer marked as found in versions cached-property/1.5.1-2.
Ignoring request to alter fixed versions of bug #924797 to the same values
previously set
Bug #924797 [freezegun] cached-property: FTBFS: dh_auto_test: pybuild --test -i
python{version} -p 3.7 returned exit code 13
There is no source info for the package 'freezegun' at version '0.3.11-0.1'
with architecture ''
Unable to make a source version for version '0.3.11-0.1'
Marked as found in versions 0.3.11-0.1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
924797: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924797
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#924797: cached-property: FTBFS: dh_auto_test: pybuild --test -i python{version} -p 3.7 returned exit code 13
* Lucas Nussbaum: " Bug#924797: cached-property: FTBFS: dh_auto_test: pybuild
--test -i python{version} -p 3.7 returned exit code 13" (Sun, 17 Mar 2019
19:07:51 +0100):
Hi Lucas,
> Source: cached-property
> Version: 1.5.1-2
> Severity: serious
> Tags: buster sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20190315 qa-ftbfs
> Justification: FTBFS in buster on amd64
>
> Hi,
>
> During a rebuild of all packages in buster (in a buster chroot, not a
> sid chroot), your package failed to build on amd64.
>
> Relevant part (hopefully):
> > debian/rules build
> > dh build --with python2,python3 --buildsystem=pybuild
> >dh_update_autotools_config -O--buildsystem=pybuild
> >dh_autoreconf -O--buildsystem=pybuild
> >dh_auto_configure -O--buildsystem=pybuild
> > I: pybuild base:217: python2.7 setup.py config
> > running config
> > I: pybuild base:217: python3.7 setup.py config
> > running config
> >dh_auto_build -O--buildsystem=pybuild
> > I: pybuild base:217: /usr/bin/python setup.py build
> > running build
> > running build_py
> > copying cached_property.py
> > -> /<>/.pybuild/cpython2_2.7_cached-property/build running
> > egg_info writing cached_property.egg-info/PKG-INFO
> > writing top-level names to cached_property.egg-info/top_level.txt
> > writing dependency_links to cached_property.egg-info/dependency_links.txt
> > reading manifest file 'cached_property.egg-info/SOURCES.txt'
> > reading manifest template 'MANIFEST.in'
> > warning: no previously-included files matching '__pycache__' found under
> > directory '*' warning: no previously-included files matching '*.py[co]'
> > found under directory '*' warning: no files found matching '*.rst' under
> > directory 'docs' warning: no files found matching 'conftest.py' under
> > directory 'docs' warning: no files found matching 'Makefile' under
> > directory 'docs' warning: no files found matching 'make.bat' under
> > directory 'docs' writing manifest file
> > 'cached_property.egg-info/SOURCES.txt' I: pybuild
> > base:217: /usr/bin/python3 setup.py build running build
> > running build_py
> > copying cached_property.py
> > -> /<>/.pybuild/cpython3_3.7_cached-property/build running
> > egg_info writing cached_property.egg-info/PKG-INFO
> > writing dependency_links to cached_property.egg-info/dependency_links.txt
> > writing top-level names to cached_property.egg-info/top_level.txt
> > reading manifest file 'cached_property.egg-info/SOURCES.txt'
> > reading manifest template 'MANIFEST.in'
> > warning: no previously-included files matching '__pycache__' found under
> > directory '*' warning: no previously-included files matching '*.py[co]'
> > found under directory '*' warning: no files found matching '*.rst' under
> > directory 'docs' warning: no files found matching 'conftest.py' under
> > directory 'docs' warning: no files found matching 'Makefile' under
> > directory 'docs' warning: no files found matching 'make.bat' under
> > directory 'docs' writing manifest file
> > 'cached_property.egg-info/SOURCES.txt' dh_auto_test -O--buildsystem=pybuild
> > I: pybuild base:217:
> > cd /<>/.pybuild/cpython3_3.7_cached-property/build; python3.7
> > -m unittest discover -v test_cached_property
> > (tests.test_async_cached_property.TestCachedProperty) ... ok
> > test_none_cached_property
> > (tests.test_async_cached_property.TestCachedProperty) ... ok
> > test_reset_cached_property
> > (tests.test_async_cached_property.TestCachedProperty) ... ok
> > test_cached_property (tests.test_cached_property.TestCachedProperty) ... ok
> > test_none_cached_property
> > (tests.test_cached_property.TestCachedProperty) ... ok
> > test_reset_cached_property
> > (tests.test_cached_property.TestCachedProperty) ... ok
> > test_set_cached_property
> > (tests.test_cached_property.TestCachedProperty) ... ok test_threads
> > (tests.test_cached_property.TestCachedProperty) ... ok test_cached_property
> > (tests.test_cached_property.TestCachedPropertyWithTTL) ... ok
> > test_none_cached_property
> > (tests.test_cached_property.TestCachedPropertyWithTTL) ... ok
> > test_reset_cached_property
> > (tests.test_cached_property.TestCachedPropertyWithTTL) ... ok
> > test_set_cached_property
> > (tests.test_cached_property.TestCachedPropertyWithTTL) ... ok test_threads
> > (tests.test_cached_property.TestCachedPropertyWithTTL) ... ok
> > test_threads_ttl_expiry
> > (tests.test_cached_property.TestCachedPropertyWithTTL) ... FAIL
> > test_ttl_expiry (tests.test_cached_property.TestCachedPropertyWithTTL) ...
> > ok test_cached_property
> > (tests.test_cached_property.TestThreadedCachedProperty) ... ok
> > test_none_cached_property
> > (tests.test_cached_property.TestThreadedCachedProperty) ... ok
> > test_reset_cached_property
> > (tests.test_cached_property.TestThreadedCachedProperty) ... ok
> > test_set_cached_property
> > (tests.test_cached_property.TestThreadedCachedProperty) ... ok test_threads
> > (tests.test_cached_property.TestThreadedCachedProperty) ... ok
> > test_cac
Bug#924866: marked as done (elpa-geiser: incompatible with emacs 26)
Your message dated Sun, 17 Mar 2019 20:37:23 + with message-id and subject line Bug#924866: fixed in geiser 0.8.1-4 has caused the Debian Bug report #924866, regarding elpa-geiser: incompatible with emacs 26 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.) -- 924866: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924866 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: elpa-geiser Version: 0.8.1-3 Severity: serious Tags: upstream Justification: does not load Control: tag -1 pending geiser 0.8.1 has upstream issue #207 [1], which makes it unable to load in emacs 26. To duplicate: emacs -q M-x package-initialize M-x toggle-debug-on-error C-x C-f foo.rkt backtrace starts Debugger entered--Lisp error: (invalid-function (lambda (&rest) geiser-racket--binding-forms*)) (lambda (&rest) geiser-racket--binding-forms*)() geiser-impl--set-buffer-implementation(nil t) geiser-mode(1) [1] https://gitlab.com/jaor/geiser/issues/207 -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-2-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages elpa-geiser depends on: ii emacs1:26.1+1-3.2 ii emacs-gtk [emacsen] 1:26.1+1-3.2 ii emacsen-common 3.0.4 ii install-info 6.5.0.dfsg.1-4+b1 elpa-geiser recommends no packages. Versions of packages elpa-geiser suggests: ii racket 7.2+dfsg1-2 -- no debconf information --- End Message --- --- Begin Message --- Source: geiser Source-Version: 0.8.1-4 We believe that the bug you reported is fixed in the latest version of geiser, 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 924...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. David Bremner (supplier of updated geiser 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: SHA256 Format: 1.8 Date: Sun, 17 Mar 2019 16:57:31 -0300 Source: geiser Architecture: source Version: 0.8.1-4 Distribution: unstable Urgency: medium Maintainer: Debian Emacs addons team Changed-By: David Bremner Closes: 924866 Changes: geiser (0.8.1-4) unstable; urgency=medium . * Cherry pick commit ae895088 from upstream to restore compatibility with emacs 26 (Closes: #924866) * Point Vcs-* to salsa Checksums-Sha1: ad6321f418fd1a4e2321e1650c0135f1aaed2545 1831 geiser_0.8.1-4.dsc 6538456d2cac78c56ed7e4fa2d35fabc2a82b1a8 6140 geiser_0.8.1-4.debian.tar.xz 3175dce3bbaeeb8f9d0e55421f6ecd84ed019406 7484 geiser_0.8.1-4_amd64.buildinfo Checksums-Sha256: 81eb576d356794bc7e995178ab849d81a078812ef0a15fdd61bdfe2859de83b3 1831 geiser_0.8.1-4.dsc bc7a7f4266a40497392358980bb5b96709003e009c740e02ee85556e0a3da4fd 6140 geiser_0.8.1-4.debian.tar.xz e5670a2d3663f019d59b9a8b507765245f9c45a4b89a7cd767ee4920ab3802ae 7484 geiser_0.8.1-4_amd64.buildinfo Files: 35606362f1633bf7859f34439d443083 1831 lisp optional geiser_0.8.1-4.dsc c0170c8aebbe29fcd4e951e0e4ffe03f 6140 lisp optional geiser_0.8.1-4.debian.tar.xz 3313c535f1c1af1577641e8907da3a95 7484 lisp optional geiser_0.8.1-4_amd64.buildinfo -BEGIN PGP SIGNATURE- iQGzBAEBCAAdFiEE3VS2dnyDRXKVCQCp8gKXHaSnniwFAlyOp80ACgkQ8gKXHaSn nix1RAv+Kizf9ZMVQMobCbq8eZj7qEeLZ0hnjpezSWsS3R2suVDCwxrtSGB7OVW2 3ME5WNMbYo6S+5EMGtM8azxfo85GzhJtdQwdP9wL2PZ4OGzdu8scf5qQNEAfsMcP k6qv8dpq6p6k5GxdbASdOQYZfUxQaOB823Oqx8IBRCCEuGyvmjEyQ7ploekNg1zm Fk2mzMo9tkgd20ejwjEpdgYKxMcIxiKqaEjbU+s4kWB0RbgCOm6TvrdFffztw5Pd oQ5MUQaCUMlRMqjJ8MV3PdOKYo6uReKV+H9f6nFs+Q4nZzWyORdR67aC+MDwN66+ J1YPVjxy8hK6m996DJJpuHyxXvyflj4YY1JdYEudxgbQ/0Gbeb4OffSBmw0OaSPF uKOI6vl+712AkJVwPrBiROeZtAJPTwo9dY9MNw5yPdy9YLVkbLjI1pNY7PlWGN2M eN3OQow5SV4GsvHz0NkENlUQ7SHmY/QDN+TLTOFUEJbae7VK7VFLiQ+StKiMDr1t +/Aqh9E0 =AXan -END PGP SIGNATURE End Message ---
Processed: advancecomp: diff for NMU version 2.1-1.1
Processing control commands: > tags 923416 + patch Bug #923416 [src:advancecomp] advancecomp: CVE-2019-9210 Added tag(s) patch. > tags 923416 + pending Bug #923416 [src:advancecomp] advancecomp: CVE-2019-9210 Added tag(s) pending. -- 923416: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923416 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#923416: advancecomp: diff for NMU version 2.1-1.1
Control: tags 923416 + patch
Control: tags 923416 + pending
Dear maintainer,
I've prepared an NMU for advancecomp (versioned as 2.1-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
Regards,
Salvatore
diff -Nru advancecomp-2.1/debian/changelog advancecomp-2.1/debian/changelog
--- advancecomp-2.1/debian/changelog 2018-02-13 09:40:50.0 +0100
+++ advancecomp-2.1/debian/changelog 2019-03-17 21:26:16.0 +0100
@@ -1,3 +1,11 @@
+advancecomp (2.1-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix a buffer overflow with image of invalid size (CVE-2019-9210)
+(Closes: #923416)
+
+ -- Salvatore Bonaccorso Sun, 17 Mar 2019 21:26:16 +0100
+
advancecomp (2.1-1) unstable; urgency=high
* New upstream release
diff -Nru advancecomp-2.1/debian/patches/Fix-a-buffer-overflow-with-image-of-invalid-size.patch advancecomp-2.1/debian/patches/Fix-a-buffer-overflow-with-image-of-invalid-size.patch
--- advancecomp-2.1/debian/patches/Fix-a-buffer-overflow-with-image-of-invalid-size.patch 1970-01-01 01:00:00.0 +0100
+++ advancecomp-2.1/debian/patches/Fix-a-buffer-overflow-with-image-of-invalid-size.patch 2019-03-17 21:26:16.0 +0100
@@ -0,0 +1,29 @@
+From: Andrea Mazzoleni
+Date: Fri, 1 Mar 2019 20:40:25 +0100
+Subject: Fix a buffer overflow with image of invalid size
+Origin: https://github.com/amadvance/advancecomp/commit/fcf71a89265c78fc26243574dda3a872574a5c02
+Bug-Debian-Security: https://security-tracker.debian.org/tracker/CVE-2019-9210
+Bug-Debian: https://bugs.debian.org/923416
+Bug: https://sourceforge.net/p/advancemame/bugs/277/
+
+---
+
+diff --git a/lib/png.c b/lib/png.c
+index cbf140b2ca6d..f888a28519d5 100644
+--- a/lib/png.c
b/lib/png.c
+@@ -656,6 +656,11 @@ adv_error adv_png_read_ihdr(
+ }
+ *pix_pixel = pixel;
+
++ if (width_align < width) {
++ error_unsupported_set("Invalid image size");
++ goto err;
++ }
++
+ if (data[10] != 0) { /* compression */
+ error_unsupported_set("Unsupported compression, %d instead of 0", (unsigned)data[10]);
+ goto err;
+--
+2.11.0
+
diff -Nru advancecomp-2.1/debian/patches/series advancecomp-2.1/debian/patches/series
--- advancecomp-2.1/debian/patches/series 1970-01-01 01:00:00.0 +0100
+++ advancecomp-2.1/debian/patches/series 2019-03-17 21:26:16.0 +0100
@@ -0,0 +1 @@
+Fix-a-buffer-overflow-with-image-of-invalid-size.patch
Bug#924706: icedtea-netx: javaws symlink is broken
On 16/03/2019 05:08, Jon DeVree wrote: > The files in /usr/share/icedtea-web/bin have the wrong file names in the > new package and this breaks javaws. itweb-settings and policyeditor are > also broken. Hi Jon, Thank you for reporting this issue. I'll upload a fix shortly. Emmanuel Bourg
Processed: tagging 924859
Processing commands for cont...@bugs.debian.org: > tags 924859 + confirmed Bug #924859 [src:libfurl-perl] libfurl-perl: FTBFS: tests failed Added tag(s) confirmed. > thanks Stopping processing here. Please contact me if you need assistance. -- 924859: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924859 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#924866: elpa-geiser: incompatible with emacs 26
Package: elpa-geiser Version: 0.8.1-3 Severity: serious Tags: upstream Justification: does not load Control: tag -1 pending geiser 0.8.1 has upstream issue #207 [1], which makes it unable to load in emacs 26. To duplicate: emacs -q M-x package-initialize M-x toggle-debug-on-error C-x C-f foo.rkt backtrace starts Debugger entered--Lisp error: (invalid-function (lambda (&rest) geiser-racket--binding-forms*)) (lambda (&rest) geiser-racket--binding-forms*)() geiser-impl--set-buffer-implementation(nil t) geiser-mode(1) [1] https://gitlab.com/jaor/geiser/issues/207 -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-2-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages elpa-geiser depends on: ii emacs1:26.1+1-3.2 ii emacs-gtk [emacsen] 1:26.1+1-3.2 ii emacsen-common 3.0.4 ii install-info 6.5.0.dfsg.1-4+b1 elpa-geiser recommends no packages. Versions of packages elpa-geiser suggests: ii racket 7.2+dfsg1-2 -- no debconf information
Bug#924824: marked as done (rust-cargo: FTBFS: dh_auto_test: /usr/share/cargo/bin/cargo build returned exit code 101)
Your message dated Sun, 17 Mar 2019 19:41:00 +
with message-id <62f68e14-41af-8ebc-6399-b620ad525...@debian.org>
and subject line fixed by #924752
has caused the Debian Bug report #924824,
regarding rust-cargo: FTBFS: dh_auto_test: /usr/share/cargo/bin/cargo build
returned exit code 101
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.)
--
924824: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924824
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-cargo
Version: 0.32.0-2
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20190315 qa-ftbfs
Justification: FTBFS in buster on amd64
Hi,
During a rebuild of all packages in buster (in a buster chroot, not a
sid chroot), your package failed to build on amd64.
Relevant part (hopefully):
> debian/rules build
> dh build --buildsystem cargo
>dh_update_autotools_config -O--buildsystem=cargo
>dh_autoreconf -O--buildsystem=cargo
>dh_auto_configure -O--buildsystem=cargo
> debian cargo wrapper: options, profiles, parallel: ['parallel=4'] [] ['-j4']
> debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu,
> x86_64-linux-gnu
> debian cargo wrapper: linking /usr/share/cargo/registry/* into
> /<>/debian/cargo_registry/
>dh_auto_build -O--buildsystem=cargo
>dh_auto_test -O--buildsystem=cargo
> debian cargo wrapper: options, profiles, parallel: ['parallel=4'] [] ['-j4']
> debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu,
> x86_64-linux-gnu
> debian cargo wrapper: running subprocess (['env', 'RUST_BACKTRACE=1',
> '/usr/bin/cargo', '-Zavoid-dev-deps', 'build', '--verbose', '--verbose',
> '-j4', '--target', 'x86_64-unknown-linux-gnu'],) {}
>Compiling proc-macro2 v0.4.27
>Compiling cc v1.0.28
>Compiling pkg-config v0.3.14
>Compiling libc v0.2.48
> Running `rustc --crate-name build_script_build
> /<>/debian/cargo_registry/proc-macro2-0.4.27/build.rs --color
> never --crate-type bin --emit=dep-info,link -C debuginfo=2 --cfg
> 'feature="default"' --cfg 'feature="proc-macro"' -C metadata=4386f0ca6bd23fd4
> -C extra-filename=-4386f0ca6bd23fd4 --out-dir
> /<>/target/debug/build/proc-macro2-4386f0ca6bd23fd4 -L
> dependency=/<>/target/debug/deps --cap-lints warn`
> Running `rustc --crate-name cc
> /<>/debian/cargo_registry/cc-1.0.28/src/lib.rs --color never
> --crate-type lib --emit=dep-info,link -C debuginfo=2 -C
> metadata=efe142e21115be96 -C extra-filename=-efe142e21115be96 --out-dir
> /<>/target/debug/deps -L
> dependency=/<>/target/debug/deps --cap-lints warn`
> Running `rustc --crate-name build_script_build
> /<>/debian/cargo_registry/libc-0.2.48/build.rs --color never
> --crate-type bin --emit=dep-info,link -C debuginfo=2 --cfg
> 'feature="default"' --cfg 'feature="use_std"' -C metadata=0fc686cfe788da40 -C
> extra-filename=-0fc686cfe788da40 --out-dir
> /<>/target/debug/build/libc-0fc686cfe788da40 -L
> dependency=/<>/target/debug/deps --cap-lints warn`
> Running `rustc --crate-name pkg_config
> /<>/debian/cargo_registry/pkg-config-0.3.14/src/lib.rs --color
> never --crate-type lib --emit=dep-info,link -C debuginfo=2 -C
> metadata=84662dc169fd5356 -C extra-filename=-84662dc169fd5356 --out-dir
> /<>/target/debug/deps -L
> dependency=/<>/target/debug/deps --cap-lints warn`
> warning: use of deprecated item 'std::ascii::AsciiExt': use inherent methods
> instead
> --> /<>/debian/cargo_registry/pkg-config-0.3.14/src/lib.rs:65:5
>|
> 65 | use std::ascii::AsciiExt;
>|
>|
>= note: #[warn(deprecated)] on by default
>
>Compiling unicode-xid v0.1.0
> Running `rustc --crate-name unicode_xid
> /<>/debian/cargo_registry/unicode-xid-0.1.0/src/lib.rs --color
> never --crate-type lib --emit=dep-info,link -C debuginfo=2 --cfg
> 'feature="default"' -C metadata=d0685fa25ab49bda -C
> extra-filename=-d0685fa25ab49bda --out-dir /<>/target/debug/deps
> -L dependency=/<>/target/debug/deps --cap-lints warn`
>Compiling memchr v2.1.3
> Running `rustc --crate-name build_script_build
> /<>/debian/cargo_registry/memchr-2.1.3/build.rs --color never
> --crate-type bin --emit=dep-info,link -C debuginfo=2 --cfg
> 'feature="default"' --cfg 'feature="libc"' --cfg 'feature="use_std"' -C
> metadata=1581720b2bf328f4 -C extra-filename=-1581720b2bf328f4 --out-dir
> /<>/target/debug/build/memchr-1581720b2bf328f4 -L
> dependency=/<>/target/debug/deps --cap-lints warn`
>Compiling matches v0.1.8
> Running `rustc --crate-name matches
> /<>/debian/cargo_registry
Bug#924827: marked as done (rust-debcargo: FTBFS: dh_auto_test: /usr/share/cargo/bin/cargo build returned exit code 101)
Your message dated Sun, 17 Mar 2019 19:41:00 +
with message-id <62f68e14-41af-8ebc-6399-b620ad525...@debian.org>
and subject line fixed by #924752
has caused the Debian Bug report #924827,
regarding rust-debcargo: FTBFS: dh_auto_test: /usr/share/cargo/bin/cargo build
returned exit code 101
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.)
--
924827: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924827
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-debcargo
Version: 2.2.10-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20190315 qa-ftbfs
Justification: FTBFS in buster on amd64
Hi,
During a rebuild of all packages in buster (in a buster chroot, not a
sid chroot), your package failed to build on amd64.
Relevant part (hopefully):
> debian/rules build
> dh build --buildsystem cargo
>dh_update_autotools_config -O--buildsystem=cargo
>dh_autoreconf -O--buildsystem=cargo
>dh_auto_configure -O--buildsystem=cargo
> debian cargo wrapper: options, profiles, parallel: ['parallel=4'] [] ['-j4']
> debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu,
> x86_64-linux-gnu
> debian cargo wrapper: linking /usr/share/cargo/registry/* into
> /<>/debian/cargo_registry/
>dh_auto_build -O--buildsystem=cargo
>dh_auto_test -O--buildsystem=cargo
> debian cargo wrapper: options, profiles, parallel: ['parallel=4'] [] ['-j4']
> debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu,
> x86_64-linux-gnu
> debian cargo wrapper: running subprocess (['env', 'RUST_BACKTRACE=1',
> '/usr/bin/cargo', '-Zavoid-dev-deps', 'build', '--verbose', '--verbose',
> '-j4', '--target', 'x86_64-unknown-linux-gnu'],) {}
>Compiling proc-macro2 v0.4.27
>Compiling pkg-config v0.3.14
>Compiling libc v0.2.48
>Compiling unicode-xid v0.1.0
> Running `rustc --crate-name build_script_build
> /<>/debian/cargo_registry/proc-macro2-0.4.27/build.rs --color
> never --crate-type bin --emit=dep-info,link -C debuginfo=2 --cfg
> 'feature="default"' --cfg 'feature="proc-macro"' -C metadata=4386f0ca6bd23fd4
> -C extra-filename=-4386f0ca6bd23fd4 --out-dir
> /<>/target/debug/build/proc-macro2-4386f0ca6bd23fd4 -L
> dependency=/<>/target/debug/deps --cap-lints warn`
> Running `rustc --crate-name pkg_config
> /<>/debian/cargo_registry/pkg-config-0.3.14/src/lib.rs --color
> never --crate-type lib --emit=dep-info,link -C debuginfo=2 -C
> metadata=84662dc169fd5356 -C extra-filename=-84662dc169fd5356 --out-dir
> /<>/target/debug/deps -L
> dependency=/<>/target/debug/deps --cap-lints warn`
> Running `rustc --crate-name build_script_build
> /<>/debian/cargo_registry/libc-0.2.48/build.rs --color never
> --crate-type bin --emit=dep-info,link -C debuginfo=2 --cfg
> 'feature="default"' --cfg 'feature="use_std"' -C metadata=0fc686cfe788da40 -C
> extra-filename=-0fc686cfe788da40 --out-dir
> /<>/target/debug/build/libc-0fc686cfe788da40 -L
> dependency=/<>/target/debug/deps --cap-lints warn`
> Running `rustc --crate-name unicode_xid
> /<>/debian/cargo_registry/unicode-xid-0.1.0/src/lib.rs --color
> never --crate-type lib --emit=dep-info,link -C debuginfo=2 --cfg
> 'feature="default"' -C metadata=d0685fa25ab49bda -C
> extra-filename=-d0685fa25ab49bda --out-dir /<>/target/debug/deps
> -L dependency=/<>/target/debug/deps --cap-lints warn`
> warning: use of deprecated item 'std::ascii::AsciiExt': use inherent methods
> instead
> --> /<>/debian/cargo_registry/pkg-config-0.3.14/src/lib.rs:65:5
>|
> 65 | use std::ascii::AsciiExt;
>|
>|
>= note: #[warn(deprecated)] on by default
>
>Compiling cc v1.0.28
> Running `rustc --crate-name cc
> /<>/debian/cargo_registry/cc-1.0.28/src/lib.rs --color never
> --crate-type lib --emit=dep-info,link -C debuginfo=2 -C
> metadata=efe142e21115be96 -C extra-filename=-efe142e21115be96 --out-dir
> /<>/target/debug/deps -L
> dependency=/<>/target/debug/deps --cap-lints warn`
>Compiling memchr v2.1.3
> Running `rustc --crate-name build_script_build
> /<>/debian/cargo_registry/memchr-2.1.3/build.rs --color never
> --crate-type bin --emit=dep-info,link -C debuginfo=2 --cfg
> 'feature="default"' --cfg 'feature="libc"' --cfg 'feature="use_std"' -C
> metadata=1581720b2bf328f4 -C extra-filename=-1581720b2bf328f4 --out-dir
> /<>/target/debug/build/memchr-1581720b2bf328f4 -L
> dependency=/<>/target/debug/deps --cap-lints warn`
>Compiling cfg-if v0.1.6
> Running `rustc --crate-name cfg_if
> /<>/debian/cargo_regi
Bug#924810: marked as done (rust-cargo-lichking: FTBFS: dh_auto_test: /usr/share/cargo/bin/cargo build returned exit code 101)
Your message dated Sun, 17 Mar 2019 19:41:00 +
with message-id <62f68e14-41af-8ebc-6399-b620ad525...@debian.org>
and subject line fixed by #924752
has caused the Debian Bug report #924810,
regarding rust-cargo-lichking: FTBFS: dh_auto_test: /usr/share/cargo/bin/cargo
build returned exit code 101
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.)
--
924810: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924810
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-cargo-lichking
Version: 0.7.0-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20190315 qa-ftbfs
Justification: FTBFS in buster on amd64
Hi,
During a rebuild of all packages in buster (in a buster chroot, not a
sid chroot), your package failed to build on amd64.
Relevant part (hopefully):
> debian/rules build
> dh build --buildsystem cargo
>dh_update_autotools_config -O--buildsystem=cargo
>dh_autoreconf -O--buildsystem=cargo
>dh_auto_configure -O--buildsystem=cargo
> debian cargo wrapper: options, profiles, parallel: ['parallel=4'] [] ['-j4']
> debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu,
> x86_64-linux-gnu
> debian cargo wrapper: linking /usr/share/cargo/registry/* into
> /<>/debian/cargo_registry/
>dh_auto_build -O--buildsystem=cargo
>dh_auto_test -O--buildsystem=cargo
> debian cargo wrapper: options, profiles, parallel: ['parallel=4'] [] ['-j4']
> debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu,
> x86_64-linux-gnu
> debian cargo wrapper: running subprocess (['env', 'RUST_BACKTRACE=1',
> '/usr/bin/cargo', '-Zavoid-dev-deps', 'build', '--verbose', '--verbose',
> '-j4', '--target', 'x86_64-unknown-linux-gnu'],) {}
>Compiling proc-macro2 v0.4.27
>Compiling pkg-config v0.3.14
>Compiling cc v1.0.28
>Compiling unicode-xid v0.1.0
> Running `rustc --crate-name build_script_build
> /<>/debian/cargo_registry/proc-macro2-0.4.27/build.rs --color
> never --crate-type bin --emit=dep-info,link -C debuginfo=2 --cfg
> 'feature="default"' --cfg 'feature="proc-macro"' -C metadata=4386f0ca6bd23fd4
> -C extra-filename=-4386f0ca6bd23fd4 --out-dir
> /<>/target/debug/build/proc-macro2-4386f0ca6bd23fd4 -L
> dependency=/<>/target/debug/deps --cap-lints warn`
> Running `rustc --crate-name pkg_config
> /<>/debian/cargo_registry/pkg-config-0.3.14/src/lib.rs --color
> never --crate-type lib --emit=dep-info,link -C debuginfo=2 -C
> metadata=84662dc169fd5356 -C extra-filename=-84662dc169fd5356 --out-dir
> /<>/target/debug/deps -L
> dependency=/<>/target/debug/deps --cap-lints warn`
> Running `rustc --crate-name cc
> /<>/debian/cargo_registry/cc-1.0.28/src/lib.rs --color never
> --crate-type lib --emit=dep-info,link -C debuginfo=2 -C
> metadata=efe142e21115be96 -C extra-filename=-efe142e21115be96 --out-dir
> /<>/target/debug/deps -L
> dependency=/<>/target/debug/deps --cap-lints warn`
> Running `rustc --crate-name unicode_xid
> /<>/debian/cargo_registry/unicode-xid-0.1.0/src/lib.rs --color
> never --crate-type lib --emit=dep-info,link -C debuginfo=2 --cfg
> 'feature="default"' -C metadata=d0685fa25ab49bda -C
> extra-filename=-d0685fa25ab49bda --out-dir /<>/target/debug/deps
> -L dependency=/<>/target/debug/deps --cap-lints warn`
> warning: use of deprecated item 'std::ascii::AsciiExt': use inherent methods
> instead
> --> /<>/debian/cargo_registry/pkg-config-0.3.14/src/lib.rs:65:5
>|
> 65 | use std::ascii::AsciiExt;
>|
>|
>= note: #[warn(deprecated)] on by default
>
>Compiling libc v0.2.48
> Running `rustc --crate-name build_script_build
> /<>/debian/cargo_registry/libc-0.2.48/build.rs --color never
> --crate-type bin --emit=dep-info,link -C debuginfo=2 --cfg
> 'feature="default"' --cfg 'feature="use_std"' -C metadata=0fc686cfe788da40 -C
> extra-filename=-0fc686cfe788da40 --out-dir
> /<>/target/debug/build/libc-0fc686cfe788da40 -L
> dependency=/<>/target/debug/deps --cap-lints warn`
>Compiling memchr v2.1.3
> Running `rustc --crate-name build_script_build
> /<>/debian/cargo_registry/memchr-2.1.3/build.rs --color never
> --crate-type bin --emit=dep-info,link -C debuginfo=2 --cfg
> 'feature="default"' --cfg 'feature="libc"' --cfg 'feature="use_std"' -C
> metadata=1581720b2bf328f4 -C extra-filename=-1581720b2bf328f4 --out-dir
> /<>/target/debug/build/memchr-1581720b2bf328f4 -L
> dependency=/<>/target/debug/deps --cap-lints warn`
>Compiling cfg-if v0.1.6
> Running `rustc --crate-name cfg_if
> /<>/debian
Bug#924815: marked as done (rust-cargo-vendor: FTBFS: dh_auto_test: /usr/share/cargo/bin/cargo build returned exit code 101)
Your message dated Sun, 17 Mar 2019 19:41:00 +
with message-id <62f68e14-41af-8ebc-6399-b620ad525...@debian.org>
and subject line fixed by #924752
has caused the Debian Bug report #924815,
regarding rust-cargo-vendor: FTBFS: dh_auto_test: /usr/share/cargo/bin/cargo
build returned exit code 101
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.)
--
924815: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924815
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-cargo-vendor
Version: 0.1.22-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20190315 qa-ftbfs
Justification: FTBFS in buster on amd64
Hi,
During a rebuild of all packages in buster (in a buster chroot, not a
sid chroot), your package failed to build on amd64.
Relevant part (hopefully):
> debian/rules build
> dh build --buildsystem cargo
>dh_update_autotools_config -O--buildsystem=cargo
>dh_autoreconf -O--buildsystem=cargo
>dh_auto_configure -O--buildsystem=cargo
> debian cargo wrapper: options, profiles, parallel: ['parallel=4'] [] ['-j4']
> debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu,
> x86_64-linux-gnu
> debian cargo wrapper: linking /usr/share/cargo/registry/* into
> /<>/debian/cargo_registry/
>dh_auto_build -O--buildsystem=cargo
>dh_auto_test -O--buildsystem=cargo
> debian cargo wrapper: options, profiles, parallel: ['parallel=4'] [] ['-j4']
> debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu,
> x86_64-linux-gnu
> debian cargo wrapper: running subprocess (['env', 'RUST_BACKTRACE=1',
> '/usr/bin/cargo', '-Zavoid-dev-deps', 'build', '--verbose', '--verbose',
> '-j4', '--target', 'x86_64-unknown-linux-gnu'],) {}
>Compiling proc-macro2 v0.4.27
>Compiling pkg-config v0.3.14
>Compiling unicode-xid v0.1.0
>Compiling libc v0.2.48
> Running `rustc --crate-name build_script_build
> /<>/debian/cargo_registry/proc-macro2-0.4.27/build.rs --color
> never --crate-type bin --emit=dep-info,link -C debuginfo=2 --cfg
> 'feature="default"' --cfg 'feature="proc-macro"' -C metadata=4386f0ca6bd23fd4
> -C extra-filename=-4386f0ca6bd23fd4 --out-dir
> /<>/target/debug/build/proc-macro2-4386f0ca6bd23fd4 -L
> dependency=/<>/target/debug/deps --cap-lints warn`
> Running `rustc --crate-name pkg_config
> /<>/debian/cargo_registry/pkg-config-0.3.14/src/lib.rs --color
> never --crate-type lib --emit=dep-info,link -C debuginfo=2 -C
> metadata=84662dc169fd5356 -C extra-filename=-84662dc169fd5356 --out-dir
> /<>/target/debug/deps -L
> dependency=/<>/target/debug/deps --cap-lints warn`
> Running `rustc --crate-name unicode_xid
> /<>/debian/cargo_registry/unicode-xid-0.1.0/src/lib.rs --color
> never --crate-type lib --emit=dep-info,link -C debuginfo=2 --cfg
> 'feature="default"' -C metadata=d0685fa25ab49bda -C
> extra-filename=-d0685fa25ab49bda --out-dir /<>/target/debug/deps
> -L dependency=/<>/target/debug/deps --cap-lints warn`
> Running `rustc --crate-name build_script_build
> /<>/debian/cargo_registry/libc-0.2.48/build.rs --color never
> --crate-type bin --emit=dep-info,link -C debuginfo=2 --cfg
> 'feature="default"' --cfg 'feature="use_std"' -C metadata=0fc686cfe788da40 -C
> extra-filename=-0fc686cfe788da40 --out-dir
> /<>/target/debug/build/libc-0fc686cfe788da40 -L
> dependency=/<>/target/debug/deps --cap-lints warn`
> warning: use of deprecated item 'std::ascii::AsciiExt': use inherent methods
> instead
> --> /<>/debian/cargo_registry/pkg-config-0.3.14/src/lib.rs:65:5
>|
> 65 | use std::ascii::AsciiExt;
>|
>|
>= note: #[warn(deprecated)] on by default
>
>Compiling cc v1.0.28
> Running `rustc --crate-name cc
> /<>/debian/cargo_registry/cc-1.0.28/src/lib.rs --color never
> --crate-type lib --emit=dep-info,link -C debuginfo=2 -C
> metadata=efe142e21115be96 -C extra-filename=-efe142e21115be96 --out-dir
> /<>/target/debug/deps -L
> dependency=/<>/target/debug/deps --cap-lints warn`
>Compiling memchr v2.1.3
> Running `rustc --crate-name build_script_build
> /<>/debian/cargo_registry/memchr-2.1.3/build.rs --color never
> --crate-type bin --emit=dep-info,link -C debuginfo=2 --cfg
> 'feature="default"' --cfg 'feature="libc"' --cfg 'feature="use_std"' -C
> metadata=1581720b2bf328f4 -C extra-filename=-1581720b2bf328f4 --out-dir
> /<>/target/debug/build/memchr-1581720b2bf328f4 -L
> dependency=/<>/target/debug/deps --cap-lints warn`
>Compiling cfg-if v0.1.6
> Running `rustc --crate-name cfg_if
> /<>/debian/ca
Bug#924833: marked as done (qgis: FTBFS: sip_corepart0.cpp:38215:19: error: 'QgsPointV2 sipQgsPolygonV2::vertexAt(const QgsVertexId&) const' marked 'override', but does not override)
Your message dated Sun, 17 Mar 2019 20:21:28 +0100 with message-id <9a52ce36-97c1-6853-ec31-ecfbf431d...@xs4all.nl> and subject line Re: Bug#924833: qgis: FTBFS: sip_corepart0.cpp:38215:19: error: 'QgsPointV2 sipQgsPolygonV2::vertexAt(const QgsVertexId&) const' marked 'override', but does not override has caused the Debian Bug report #924833, regarding qgis: FTBFS: sip_corepart0.cpp:38215:19: error: 'QgsPointV2 sipQgsPolygonV2::vertexAt(const QgsVertexId&) const' marked 'override', but does not override 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.) -- 924833: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924833 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: qgis Version: 2.18.28+dfsg-2 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20190315 qa-ftbfs Justification: FTBFS in buster on amd64 Hi, During a rebuild of all packages in buster (in a buster chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): > cd /<>/qgis-2.18.28+dfsg/debian/build/src/gui && /usr/bin/c++ > -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_NO_CAST_TO_ASCII > -DQT_NO_DEBUG -DQT_SQL_LIB -DQT_SVG_LIB -DQT_XML_LIB -Dqgis_gui_EXPORTS > -I/<>/qgis-2.18.28+dfsg/debian/build > -I/<>/qgis-2.18.28+dfsg/src/gui > -I/<>/qgis-2.18.28+dfsg/src/gui/symbology-ng > -I/<>/qgis-2.18.28+dfsg/src/gui/attributetable > -I/<>/qgis-2.18.28+dfsg/src/gui/auth > -I/<>/qgis-2.18.28+dfsg/src/gui/editorwidgets > -I/<>/qgis-2.18.28+dfsg/src/gui/editorwidgets/core > -I/<>/qgis-2.18.28+dfsg/src/gui/layertree > -I/<>/qgis-2.18.28+dfsg/src/gui/effects > -I/<>/qgis-2.18.28+dfsg/src/gui/../core > -I/<>/qgis-2.18.28+dfsg/src/gui/../core/auth > -I/<>/qgis-2.18.28+dfsg/src/gui/../core/composer > -I/<>/qgis-2.18.28+dfsg/src/gui/../core/geometry > -I/<>/qgis-2.18.28+dfsg/src/gui/../core/layertree > -I/<>/qgis-2.18.28+dfsg/src/gui/../core/raster > -I/<>/qgis-2.18.28+dfsg/src/gui/../core/symbology-ng > -I/<>/qgis-2.18.28+dfsg/src/gui/../core/effects > -I/<>/qgis-2.18.28+dfsg/debian/build/src/gui > -I/<>/qgis-2.18.28+dfsg/debian/build/src/gui/../ui -isystem > /usr/include/qt4 -isystem /usr/include/qt4/QtSvg -isystem > /usr/include/qt4/QtGui -isystem /usr/include/qt4/QtXml -isystem > /usr/include/qt4/QtSql -isystem /usr/include/qt4/QtNetwork -isystem > /usr/include/qt4/QtCore -isystem /usr/include/qt4/QtUiTools -isystem > /usr/include/QtCrypto -isystem /usr/include/qwt -isystem /usr/include/gdal > -g -O2 -fdebug-prefix-map=/<>/qgis-2.18.28+dfsg=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 -O2 -DNDEBUG -Wdate-time -D_FORTIFY_SOURCE=2 > -DSPATIALITE_VERSION_GE_4_0_0 -DSPATIALITE_VERSION_G_4_1_1 > -DSPATIALITE_HAS_INIT_EX -std=c++11 -Wall -Wextra -Wno-long-long > -Wformat-security -Wno-strict-aliasing -fPIC -fvisibility=hidden > -DCORE_EXPORT= -DPYTHON_EXPORT= -DANALYSIS_EXPORT= -DAPP_EXPORT= > -DCUSTOMWIDGETS_EXPORT= -DSERVER_EXPORT= "-DGUI_EXPORT=__attribute__ > ((visibility (\"default\")))" -o > CMakeFiles/qgis_gui.dir/symbology-ng/qgssmartgroupeditordialog.cpp.o -c > /<>/qgis-2.18.28+dfsg/src/gui/symbology-ng/qgssmartgroupeditordialog.cpp > /<>/qgis-2.18.28+dfsg/debian/build/python/core/sip_corepart0.cpp:38215:19: > error: 'QgsPointV2 sipQgsPolygonV2::vertexAt(const QgsVertexId&) const' > marked 'override', but does not override > ::QgsPolygonV2* sipQgsPolygonV2::surfaceToPolygon() const >^~~~ > /<>/qgis-2.18.28+dfsg/debian/build/python/core/sip_corepart0.cpp:66707:19: > error: 'QgsPointV2 sipQgsCurvePolygonV2::vertexAt(const QgsVertexId&) const' > marked 'override', but does not override > bool sipQgsCurvePolygonV2::insertVertex( ::QgsVertexId a0,const > ::QgsPointV2& a1) >^~~~ > /<>/qgis-2.18.28+dfsg/debian/build/python/core/sip_corepart0.cpp:87278:17: > error: 'QVariant sipQgsArrowSymbolLayer::evaluateDataDefinedProperty(const > QString&, const QgsFeature*) const' marked 'override', but does not override > } > ^ > [ 40%] Building CXX object > python/CMakeFiles/python_module_qgis__analysis.dir/analysis/sip_analysispart2.cpp.o > cd /<>/qgis-2.18.28+dfsg/debian/build/python && /usr/bin/c++ > -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_NO_CAST_TO_ASCII > -DQT_NO_DEBUG -DQT_SQL_LIB -DQT_SVG_LIB -DQT_XML_LIB -Dprotected=public > -Dpython_module_qgis__analysis_EXPORTS > -I/<>/qgis-2.18.28+dfsg/debian/build > -I/<>/qgis-2.18.28+dfsg/python/../src/core > -I/<>/q
Bug#924860: multipath-tools: FTBFS: /bin/sh: 1: Syntax error: "(" unexpected
Source: multipath-tools
Version: 0.7.9-2
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20190315 qa-ftbfs
Justification: FTBFS in buster on amd64
Hi,
During a rebuild of all packages in buster (in a buster chroot, not a
sid chroot), your package failed to build on amd64.
Relevant part (hopefully):
> make[2]: Entering directory '/<>/libmultipath'
> /bin/sh: 1: Syntax error: "(" unexpected
> Checking for dm_task_no_flush in /usr/include/libdevmapper.h ... yes
> Checking for dm_task_set_cookie in /usr/include/libdevmapper.h ... yes
> Checking for udev_monitor_set_receive_buffer_size in /usr/include/libudev.h
> ... yes
> Checking for dm_task_deferred_remove in /usr/include/libdevmapper.h ... yes
> building memory.o because of memory.c
> cc -g -O2 -fdebug-prefix-map=/<>/libmultipath=.
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
> -D_FORTIFY_SOURCE=2 -O2 -g -pipe -Wall -Wextra -Wformat=2
> -Werror=implicit-int -Werror=implicit-function-declaration
> -Werror=format-security -Wno-sign-compare -Wno-unused-parameter
> -Wno-clobbered -Werror=cast-qual -Werror=discarded-qualifiers
> -Wp,-D_FORTIFY_SOURCE=2 -fstack-protector-strong --param=ssp-buffer-size=4
> -DBIN_DIR=\"/sbin\" -DLIB_STRING=\"/lib\" -DRUN_DIR=\"run\" -MMD -MP -g -O2
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -fPIC -I../libmpathcmd -I../libmpathpersist
> -DUSE_SYSTEMD=241 (241) -DLIBDM_API_FLUSH -D_GNU_SOURCE -DLIBDM_API_COOKIE
> -DLIBUDEV_API_RECVBUF -DLIBDM_API_DEFERRED -c -o memory.o memory.c
> /bin/sh: 1: Syntax error: "(" unexpected
> make[2]: *** [../Makefile.inc:137: memory.o] Error 2
The full build log is available from:
http://aws-logs.debian.net/2019/03/15/multipath-tools_0.7.9-2_testing.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.
Bug#924855: shellia: FTBFS: tests failed
Source: shellia Version: 5.3.1 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20190315 qa-ftbfs Justification: FTBFS in buster on amd64 Hi, During a rebuild of all packages in buster (in a buster chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > rm -f shellia-tested-stamp > ./run_tests && touch shellia-tested-stamp > OK "./test.backslash" -s "bash" > OK "./test.backslash" -s "dash" > OK "./test.backslash" -s "busybox sh" > OK "./test.backslash" -s "mksh" > OK "./test.backslash" -s "posh" > OK "./test.buffer" -s "bash" > OK "./test.buffer" -s "dash" > OK "./test.buffer" -s "busybox sh" > OK "./test.buffer" -s "mksh" > OK "./test.buffer" -s "posh" > OK "./test.debug" -s "bash" > OK "./test.debug" -s "dash" > OK "./test.debug" -s "busybox sh" > OK "./test.debug" -s "mksh" > OK "./test.debug" -s "posh" > OK "./test.debug_iptables" -s "bash" > OK "./test.debug_iptables" -s "dash" > OK "./test.debug_iptables" -s "busybox sh" > OK "./test.debug_iptables" -s "mksh" > OK "./test.debug_iptables" -s "posh" > OK "./test.func" -s "bash" > OK "./test.func" -s "dash" > OK "./test.func" -s "busybox sh" > OK "./test.func" -s "mksh" > OK "./test.func" -s "posh" > OK "./test.hello_world" -s "bash" > OK "./test.hello_world" -s "dash" > OK "./test.hello_world" -s "busybox sh" > OK "./test.hello_world" -s "mksh" > OK "./test.hello_world" -s "posh" > OK "./test.hello_world_debug" -s "bash" > OK "./test.hello_world_debug" -s "dash" > OK "./test.hello_world_debug" -s "busybox sh" > OK "./test.hello_world_debug" -s "mksh" > OK "./test.hello_world_debug" -s "posh" > OK "./test.hello_world_error" -s "bash" > OK "./test.hello_world_error" -s "dash" > OK "./test.hello_world_error" -s "busybox sh" > OK "./test.hello_world_error" -s "mksh" > OK "./test.hello_world_error" -s "posh" > OK "./test.hello_world_fun" -s "bash" > OK "./test.hello_world_fun" -s "dash" > OK "./test.hello_world_fun" -s "busybox sh" > OK "./test.hello_world_fun" -s "mksh" > OK "./test.hello_world_fun" -s "posh" > OK "./test.hello_world_log" -s "bash" > OK "./test.hello_world_log" -s "dash" > OK "./test.hello_world_log" -s "busybox sh" > OK "./test.hello_world_log" -s "mksh" > OK "./test.hello_world_log" -s "posh" > OK "./test.hello_world_trace" -s "bash" > OK "./test.hello_world_trace" -s "dash" > OK "./test.hello_world_trace" -s "busybox sh" > OK "./test.hello_world_trace" -s "mksh" > OK "./test.hello_world_trace" -s "posh" > OK "./test.ia-C-error" -s "bash" > OK "./test.ia-C-error" -s "dash" > OK "./test.ia-C-error" -s "busybox sh" > OK "./test.ia-C-error" -s "mksh" > OK "./test.ia-C-error" -s "posh" > OK "./test.ia-C-expr" -s "bash" > OK "./test.ia-C-expr" -s "dash" > OK "./test.ia-C-expr" -s "busybox sh" > OK "./test.ia-C-expr" -s "mksh" > OK "./test.ia-C-expr" -s "posh" > OK "./test.ia-c-C" -s "bash" > OK "./test.ia-c-C" -s "dash" > OK "./test.ia-c-C" -s "busybox sh" > OK "./test.ia-c-C" -s "mksh" > OK "./test.ia-c-C" -s "posh" > OK "./test.ia-c-error" -s "bash" > OK "./test.ia-c-error" -s "dash" > OK "./test.ia-c-error" -s "busybox sh" > OK "./test.ia-c-error" -s "mksh" > OK "./test.ia-c-error" -s "posh" > OK "./test.ia-c-expr" -s "bash" > OK "./test.ia-c-expr" -s "dash" > OK "./test.ia-c-expr" -s "busybox sh" > OK "./test.ia-c-expr" -s "mksh" > OK "./test.ia-c-expr" -s "posh" > OK "./test.ia-c-nocheck" -s "bash" > OK "./test.ia-c-nocheck" -s "dash" > OK "./test.ia-c-nocheck" -s "busybox sh" > OK "./test.ia-c-nocheck" -s "mksh" > OK "./test.ia-c-nocheck" -s "posh" > OK "./test.ia-c-s-m" -s "bash" > OK "./test.ia-c-s-m" -s "dash" > OK "./test.ia-c-s-m" -s "busybox sh" > OK "./test.ia-c-s-m" -s "mksh" > OK "./test.ia-c-s-m" -s "posh" > OK "./test.ia-empty" -s "bash" > OK "./test.ia-empty" -s "dash" > OK "./test.ia-empty" -s "busybox sh" > OK "./test.ia-empty" -s "mksh" > OK "./test.ia-empty" -s "posh" > OK "./test.ia-expr" -s "bash" > OK "./test.ia-expr" -s "dash" > OK "./test.ia-expr" -s "busybox sh" > OK "./test.ia-expr" -s "mksh" > OK "./test.ia-expr" -s "posh" > OK "./test.ia-s" -s "bash" > OK "./test.ia-s" -s "dash" > OK "./test.ia-s" -s "busybox sh" > OK "./test.ia-s" -s "mksh" > OK "./test.ia-s" -s "posh" > OK "./test.ia_mktemp" -s "bash" > OK "./test.ia_mktemp" -s "dash" > OK "./test.ia_mktemp" -s "busybox sh" > OK "./test.multiply" -s "bash" > OK "./test.multiply" -s "dash" > ERROR "./test.multiply" -s "busybox sh" > OK "./test.multiply" -s "mksh" > OK "./test.multiply" -s "posh" > OK "./test.only_debug" -s "bash" > OK "./test.only_debug" -s "dash" > OK "./test.only_debug" -s "busybox sh" > OK "./test.only_debug" -s "mksh" > OK "./test.only_debug" -s "posh" > OK "./test.only_interactive" -s "bash" > OK "./test.only_interactive" -s "dash" > OK "./test.only_interactive" -s "busybox sh" > OK "./test.only_interactive" -s "mksh" > OK "./test.only_log" -s "bash" > OK "./test.only_log" -s "dash" > OK "./test.only_log" -s "busybox sh" > OK
Bug#924857: frobby: FTBFS: make[3]: *** [Makefile:6: refman.pdf] Error 1
Source: frobby Version: 0.9.0-5 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20190315 qa-ftbfs Justification: FTBFS in buster on amd64 Hi, During a rebuild of all packages in buster (in a buster chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): > make[3]: Entering directory '/<>/bin/develDoc/latexPdf' > rm -f *.ps *.dvi *.aux *.toc *.idx *.ind *.ilg *.log *.out *.brf *.blg *.bbl > refman.pdf > pdflatex refman > This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2019/dev/Debian) > (preloaded format=pdflatex) > restricted \write18 enabled. > entering extended mode > (./refman.tex > LaTeX2e <2018-12-01> > (/usr/share/texlive/texmf-dist/tex/latex/base/book.cls > Document Class: book 2018/09/03 v1.4i Standard LaTeX document class > (/usr/share/texlive/texmf-dist/tex/latex/base/bk10.clo)) > (/usr/share/texlive/texmf-dist/tex/latex/base/fixltx2e.sty > > Package fixltx2e Warning: fixltx2e is not required with releases after 2015 > (fixltx2e)All fixes are now in the LaTeX kernel. > (fixltx2e)See the latexrelease package for details. > > ) (/usr/share/texlive/texmf-dist/tex/latex/tools/calc.sty) (./doxygen.sty > (/usr/share/texlive/texmf-dist/tex/latex/base/alltt.sty) > (/usr/share/texlive/texmf-dist/tex/latex/tools/array.sty) > (/usr/share/texlive/texmf-dist/tex/latex/float/float.sty) > (/usr/share/texlive/texmf-dist/tex/latex/base/ifthen.sty) > (/usr/share/texlive/texmf-dist/tex/latex/tools/verbatim.sty) > (/usr/share/texlive/texmf-dist/tex/latex/xcolor/xcolor.sty > (/usr/share/texlive/texmf-dist/tex/latex/graphics-cfg/color.cfg) > (/usr/share/texlive/texmf-dist/tex/latex/graphics-def/pdftex.def) > (/usr/share/texlive/texmf-dist/tex/latex/colortbl/colortbl.sty)) > (/usr/share/texlive/texmf-dist/tex/latex/tools/longtable.sty) > (/usr/share/texlive/texmf-dist/tex/latex/tabu/tabu.sty > (/usr/share/texlive/texmf-dist/tex/latex/varwidth/varwidth.sty)) > (/usr/share/texlive/texmf-dist/tex/latex/tools/tabularx.sty) > (/usr/share/texlive/texmf-dist/tex/latex/multirow/multirow.sty)) > (/usr/share/texlive/texmf-dist/tex/latex/adjustbox/adjustbox.sty > (/usr/share/texlive/texmf-dist/tex/latex/xkeyval/xkeyval.sty > (/usr/share/texlive/texmf-dist/tex/generic/xkeyval/xkeyval.tex > (/usr/share/texlive/texmf-dist/tex/generic/xkeyval/xkvutils.tex > (/usr/share/texlive/texmf-dist/tex/generic/xkeyval/keyval.tex > (/usr/share/texlive/texmf-dist/tex/latex/adjustbox/adjcalc.sty) > (/usr/share/texlive/texmf-dist/tex/latex/adjustbox/trimclip.sty > (/usr/share/texlive/texmf-dist/tex/latex/graphics/graphicx.sty > (/usr/share/texlive/texmf-dist/tex/latex/graphics/graphics.sty > (/usr/share/texlive/texmf-dist/tex/latex/graphics/trig.sty) > (/usr/share/texlive/texmf-dist/tex/latex/graphics-cfg/graphics.cfg))) > (/usr/share/texlive/texmf-dist/tex/latex/collectbox/collectbox.sty) > (/usr/share/texlive/texmf-dist/tex/latex/adjustbox/tc-pdftex.def)) > (/usr/share/texlive/texmf-dist/tex/latex/ifoddpage/ifoddpage.sty)) > (/usr/share/texlive/texmf-dist/tex/latex/base/inputenc.sty) > (/usr/share/texlive/texmf-dist/tex/latex/base/makeidx.sty) > (/usr/share/texlive/texmf-dist/tex/latex/tools/multicol.sty) > (/usr/share/texlive/texmf-dist/tex/latex/base/textcomp.sty > (/usr/share/texlive/texmf-dist/tex/latex/base/ts1enc.def > (/usr/share/texlive/texmf-dist/tex/latex/base/ts1enc.dfu))) > (/usr/share/texlive/texmf-dist/tex/latex/wasysym/wasysym.sty) > (/usr/share/texlive/texmf-dist/tex/latex/base/fontenc.sty > (/usr/share/texlive/texmf-dist/tex/latex/base/t1enc.def)) > (/usr/share/texlive/texmf-dist/tex/latex/psnfss/helvet.sty) > (/usr/share/texlive/texmf-dist/tex/latex/psnfss/courier.sty) > (/usr/share/texlive/texmf-dist/tex/latex/amsfonts/amssymb.sty > (/usr/share/texlive/texmf-dist/tex/latex/amsfonts/amsfonts.sty)) > (/usr/share/texlive/texmf-dist/tex/latex/sectsty/sectsty.sty) > (/usr/share/texlive/texmf-dist/tex/latex/geometry/geometry.sty > (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/ifpdf.sty) > (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/ifvtex.sty) > (/usr/share/texlive/texmf-dist/tex/generic/ifxetex/ifxetex.sty)) > (/usr/share/texlive/texmf-dist/tex/latex/fancyhdr/fancyhdr.sty) > (/usr/share/texlive/texmf-dist/tex/latex/natbib/natbib.sty) > (/usr/share/texlive/texmf-dist/tex/latex/tocloft/tocloft.sty) > Writing index file refman.idx > (../../../doc/frobbyLatex.sty > > LaTeX Warning: You have requested package `../../../doc/frobbyLatex', >but the package provides `frobbyLatex'. > > (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsopn.sty > (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsgen.sty))) > (/usr/share/texlive/texmf-dist/tex/latex/hyperref/hyperref.sty > (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/hobsub-hyperref.sty > (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/hobsub-generic.sty)) > (/usr/share/texlive/texmf-dist/tex/latex/oberdiek/auxhook.sty) >
Processed: severity of 923750 is serious
Processing commands for cont...@bugs.debian.org: > severity 923750 serious Bug #923750 [src:gdcm] gdcm: FTBFS in buster/sid Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 923750: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923750 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#924858: doxygen: FTBFS: make[4]: *** [doc/CMakeFiles/doxygen_pdf.dir/build.make:62: doc/CMakeFiles/doxygen_pdf] Error 1
Source: doxygen Version: 1.8.13-10 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20190315 qa-ftbfs Justification: FTBFS in buster on amd64 Hi, During a rebuild of all packages in buster (in a buster chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): > make[4]: Entering directory '/<>/build' > [100%] Generating Doxygen Manual PDF. > cd /<>/build/latex && /usr/bin/cmake -E remove refman.tex > cd /<>/build/latex && /usr/bin/cmake -E copy > /<>/build/doc/doxygen_manual.tex . > cd /<>/build/latex && /usr/bin/cmake -E copy > /<>/build/doc/manual.sty . > cd /<>/build/latex && /usr/bin/epstopdf > /<>/doc/doxygen_logo.eps --outfile=doxygen_logo.pdf > cd /<>/build/latex && /usr/bin/pdflatex -shell-escape > doxygen_manual.tex > This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2019/dev/Debian) > (preloaded format=pdflatex) > \write18 enabled. > entering extended mode > (./doxygen_manual.tex > LaTeX2e <2018-12-01> > > make[4]: *** [doc/CMakeFiles/doxygen_pdf.dir/build.make:62: > doc/CMakeFiles/doxygen_pdf] Error 1 The full build log is available from: http://aws-logs.debian.net/2019/03/15/doxygen_1.8.13-10_testing.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.
Bug#924856: wxpython4.0: FTBFS: sip: /<>/wxpython4.0-4.0.4+dfsg/src/wacky_ints.sip:20: Invalid type for %MappedType
Source: wxpython4.0 Version: 4.0.4+dfsg-1 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20190315 qa-ftbfs Justification: FTBFS in buster on amd64 Hi, During a rebuild of all packages in buster (in a buster chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): > debian/rules build > dh build --with python2,python3 --buildsystem=pybuild >dh_update_autotools_config -O--buildsystem=pybuild >dh_auto_configure -O--buildsystem=pybuild >dh_auto_build -O--buildsystem=pybuild > I: pybuild base:217: python2.7 -u build.py dox touch etg --nodoc sip build_py > --use_syswx --gtk3 bdist_egg > Will build using: "/usr/bin/python2.7" > 2.7.16rc1 (default, Feb 18 2019, 11:05:09) > [GCC 8.2.0] > Python's architecture is 64bit > cfg.VERSION: 4.0.4 > > Running command: dox > bash ./regen.sh xml > Finished command: dox (9.990s) > Running command: touch > touch etg/*.py > Finished command: touch (0.3s) > Running command: etg > "/usr/bin/python2.7" etg/_core.py --sip --nodoc > "/usr/bin/python2.7" etg/_dataview.py --sip --nodoc > "/usr/bin/python2.7" etg/_aui.py --sip --nodoc > "/usr/bin/python2.7" etg/_msw.py --sip --nodoc > "/usr/bin/python2.7" etg/_richtext.py --sip --nodoc > "/usr/bin/python2.7" etg/_stc.py --sip --nodoc > "/usr/bin/python2.7" etg/_xml.py --sip --nodoc > "/usr/bin/python2.7" etg/_webkit.py --sip --nodoc > "/usr/bin/python2.7" etg/_adv.py --sip --nodoc > "/usr/bin/python2.7" etg/_media.py --sip --nodoc > "/usr/bin/python2.7" etg/_xrc.py --sip --nodoc > "/usr/bin/python2.7" etg/_grid.py --sip --nodoc > "/usr/bin/python2.7" etg/_propgrid.py --sip --nodoc > "/usr/bin/python2.7" etg/_html2.py --sip --nodoc > "/usr/bin/python2.7" etg/_html.py --sip --nodoc > "/usr/bin/python2.7" etg/_ribbon.py --sip --nodoc > "/usr/bin/python2.7" etg/_glcanvas.py --sip --nodoc > "/usr/bin/python2.7" etg/defs.py --sip --nodoc > "/usr/bin/python2.7" etg/debug.py --sip --nodoc > "/usr/bin/python2.7" etg/object.py --sip --nodoc > "/usr/bin/python2.7" etg/clntdatactnr.py --sip --nodoc > "/usr/bin/python2.7" etg/wxdatetime.py --sip --nodoc > "/usr/bin/python2.7" etg/stopwatch.py --sip --nodoc > "/usr/bin/python2.7" etg/windowid.py --sip --nodoc > "/usr/bin/python2.7" etg/platinfo.py --sip --nodoc > "/usr/bin/python2.7" etg/vidmode.py --sip --nodoc > "/usr/bin/python2.7" etg/display.py --sip --nodoc > "/usr/bin/python2.7" etg/intl.py --sip --nodoc > "/usr/bin/python2.7" etg/translation.py --sip --nodoc > "/usr/bin/python2.7" etg/cmndata.py --sip --nodoc > "/usr/bin/python2.7" etg/gdicmn.py --sip --nodoc > "/usr/bin/python2.7" etg/geometry.py --sip --nodoc > "/usr/bin/python2.7" etg/affinematrix2d.py --sip --nodoc > "/usr/bin/python2.7" etg/position.py --sip --nodoc > "/usr/bin/python2.7" etg/colour.py --sip --nodoc > "/usr/bin/python2.7" etg/stream.py --sip --nodoc > "/usr/bin/python2.7" etg/filesys.py --sip --nodoc > "/usr/bin/python2.7" etg/image.py --sip --nodoc > "/usr/bin/python2.7" etg/gdiobj.py --sip --nodoc > "/usr/bin/python2.7" etg/bitmap.py --sip --nodoc > "/usr/bin/python2.7" etg/icon.py --sip --nodoc > "/usr/bin/python2.7" etg/iconloc.py --sip --nodoc > "/usr/bin/python2.7" etg/iconbndl.py --sip --nodoc > "/usr/bin/python2.7" etg/font.py --sip --nodoc > "/usr/bin/python2.7" etg/fontutil.py --sip --nodoc > "/usr/bin/python2.7" etg/pen.py --sip --nodoc > "/usr/bin/python2.7" etg/brush.py --sip --nodoc > "/usr/bin/python2.7" etg/cursor.py --sip --nodoc > "/usr/bin/python2.7" etg/region.py --sip --nodoc > "/usr/bin/python2.7" etg/dc.py --sip --nodoc > "/usr/bin/python2.7" etg/dcclient.py --sip --nodoc > "/usr/bin/python2.7" etg/dcmemory.py --sip --nodoc > "/usr/bin/python2.7" etg/dcbuffer.py --sip --nodoc > "/usr/bin/python2.7" etg/dcscreen.py --sip --nodoc > "/usr/bin/python2.7" etg/dcgraph.py --sip --nodoc > "/usr/bin/python2.7" etg/dcmirror.py --sip --nodoc > "/usr/bin/python2.7" etg/dcprint.py --sip --nodoc > "/usr/bin/python2.7" etg/dcps.py --sip --nodoc > "/usr/bin/python2.7" etg/dcsvg.py --sip --nodoc > "/usr/bin/python2.7" etg/metafile.py --sip --nodoc > "/usr/bin/python2.7" etg/graphics.py --sip --nodoc > "/usr/bin/python2.7" etg/imaglist.py --sip --nodoc > "/usr/bin/python2.7" etg/overlay.py --sip --nodoc > "/usr/bin/python2.7" etg/palette.py --sip --nodoc > "/usr/bin/python2.7" etg/renderer.py --sip --nodoc > "/usr/bin/python2.7" etg/rawbmp.py --sip --nodoc > "/usr/bin/python2.7" etg/access.py --sip --nodoc > "/usr/bin/python2.7" etg/accel.py --sip --nodoc > "/usr/bin/python2.7" etg/log.py --sip --nodoc > "/usr/bin/python2.7" etg/dataobj.py --sip --nodoc > "/usr/bin/python2.7" etg/dnd.py --sip --nodoc > "/usr/bin/python2.7" etg/clipbrd.py --sip --nodoc > "/usr/bin/python2.7" etg/config.py --sip --nodoc > "/usr/bin/python2.7" etg/tracker.py --sip --nodoc > "/usr/bin/python2.7" etg/kbdstate.py --sip --nodoc > "/usr/bin/python2.7" etg/mousestate.py --sip --nodoc > "/usr/bin/python2.7" etg/tooltip.py --sip --nodoc > "/usr/bin/p
Bug#924859: libfurl-perl: FTBFS: tests failed
Source: libfurl-perl Version: 3.13-1 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20190315 qa-ftbfs Justification: FTBFS in buster on amd64 Hi, During a rebuild of all packages in buster (in a buster chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): > debian/rules build > test -x debian/rules > mkdir -p "." > cd . && perl -I. Build.PL --installdirs vendor --config ccflags="-g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -D_REENTRANT -D_GNU_SOURCE -DDEBIAN -fwrapv > -fno-strict-aliasing -pipe -I/usr/local/include -D_LARGEFILE_SOURCE > -D_FILE_OFFSET_BITS=64" --config cxxflags="-g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security" --config cppflags="-Wdate-time -D_FORTIFY_SOURCE=2 > -D_REENTRANT -D_GNU_SOURCE -DDEBIAN -fwrapv -fno-strict-aliasing -pipe > -I/usr/local/include" --config lddlflags="-Wl,-z,relro -shared > -L/usr/local/lib -fstack-protector-strong" --destdir > /<>/debian/libfurl-perl > Creating new 'Build' script for 'Furl' version '3.13' > cd . && ./Build build > cp lib/Furl/ZlibStream.pm blib/lib/Furl/ZlibStream.pm > cp lib/Furl/HTTP.pm blib/lib/Furl/HTTP.pm > cp lib/Furl/ConnectionCache.pm blib/lib/Furl/ConnectionCache.pm > cp lib/Furl/Headers.pm blib/lib/Furl/Headers.pm > cp lib/Furl/Request.pm blib/lib/Furl/Request.pm > cp lib/Furl/Response.pm blib/lib/Furl/Response.pm > cp lib/Furl.pm blib/lib/Furl.pm > touch debian/stamp-perl-build > cd . && ./Build test --verbose 1 > # Perl/v5.28.1 > # Furl/3.13 > # Net::IDN::Encode/2.5 > # IO::Socket::SSL/2.060 > # Compress::Raw::Zlib/2.076 > t/00_compile.t .. > 1..1 > ok 1 - use Furl; > ok > t/01_version.t .. > ok 1 > 1..1 > ok > t/100_low/01_simple.t ... > ok 1 > ok 2 > ok 3 - request()/1 > ok 4 > ok 5 - header > ok 6 > ok 7 > ok 8 > ok 9 - request()/2 > ok 10 > ok 11 - header > ok 12 > ok 13 > ok 14 > ok 15 - request()/3 > ok 16 > ok 17 - header > ok 18 > ok 19 > ok 20 - get()/1 > ok 21 > ok 22 - header > ok 23 > ok 24 > ok 25 - get()/2 > ok 26 > ok 27 - header > ok 28 > ok 29 > ok 30 - get()/3 > ok 31 > ok 32 - header > ok 33 > 1..33 > ok > t/100_low/03_redirect.t . > # Subtest: redirect > ok 1 > ok 2 > ok 3 > ok 4 > 1..4 > ok 1 - redirect > # Subtest: not enough redirect > ok 1 > ok 2 > ok 3 > ok 4 > ok 5 > 1..5 > ok 2 - not enough redirect > # Subtest: over max redirect > ok 1 - code ok > ok 2 - msg ok > ok 3 - content length ok > ok 4 - url ok > ok 5 - content ok > 1..5 > ok 3 - over max redirect > # Subtest: POST redirects > ok 1 - POST into 301 results in a POST > ok 2 - POST into 302 is implemented as 303 > ok 3 - POST into 303 results in a GET > ok 4 - POST into 307 results in a POST > 1..4 > ok 4 - POST redirects > 1..4 > ok > t/100_low/04_chunked.t .. > # -- TEST (packets: 1) > ok 1 - status > ok 2 - content > # -- TEST (packets: 3) > ok 3 - status > ok 4 - content > # -- TEST (packets: 1024) > ok 5 - status > ok 6 - content > # -- TEST (packets: 1) > ok 7 - status > ok 8 - content > # -- TEST (packets: 3) > ok 9 - status > ok 10 - content > # -- TEST (packets: 1024) > ok 11 - status > ok 12 - content > 1..12 > ok > t/100_low/05_slowloris.t > ok 1 > ok 2 - request()/1 > ok 3 > ok 4 > ok 5 > ok 6 > ok 7 - request()/2 > ok 8 > ok 9 > ok 10 > ok 11 > ok 12 - request()/3 > ok 13 > ok 14 > ok 15 > ok 16 - get()/1 > ok 17 > ok 18 > ok 19 > ok 20 - get()/2 > ok 21 > ok 22 > ok 23 > ok 24 - get()/3 > ok 25 > ok 26 > ok 27 > 1..27 > ok > t/100_low/06_errors.t ... > ok 1 - missuse > ok 2 - missuse > ok 3 - malformed URL: hogehoge > ok 4 - malformed URL: http://example.com:80foobar > ok 5 - malformed URL: http://example.com: > # Errorneous::Server listening > ok 6 > ok 7 - request()/1 > ok 8 > ok 9 > ok 10 - content: Unexpected EOF while reading response header at > t/100_low/06_errors.t line 66. > # > ok 11 > ok 12 - request()/2 > ok 13 > ok 14 > ok 15 - content: Unexpected EOF while reading response header at > t/100_low/06_errors.t line 66. > # > ok 16 > ok 17 - request()/3 > ok 18 > ok 19 > ok 20 - content: Unexpected EOF while reading response header at > t/100_low/06_errors.t line 66. > # > 1..20 > ok > t/100_low/07_timeout.t .. > # read_timeout > ok 1 - request()/1 > ok 2 > ok 3 > ok 4 - content: Cannot read response header: timeout at > t/100_low/07_timeout.t line 27. > # > ok 5 > ok 6 - request()/2 > ok 7 > ok 8 > ok 9 - content: Cannot read response header: timeout at > t/100_low/07_timeout.t line 27. > # > ok 10 > # write_timeout > # Try sending 1 MiB content. > # Read timeout. Retry with more POST content > # Try sending 2 MiB content. > # Read ti
Bug#924826: marked as done (python-osmapi: FTBFS: build-dependency not installable: python-tox)
Your message dated Sun, 17 Mar 2019 19:20:34 + with message-id and subject line Bug#924826: fixed in python-osmapi 1.2.2-2 has caused the Debian Bug report #924826, regarding python-osmapi: FTBFS: build-dependency not installable: python-tox 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.) -- 924826: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924826 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-osmapi Version: 1.2.2-1 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20190315 qa-ftbfs Justification: FTBFS in buster on amd64 Hi, During a rebuild of all packages in buster (in a buster chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper (>= 9), dh-python, python-all, python3-all, > python-setuptools, python3-setuptools, python-flake8, python3-flake8, > python-nose, python3-nose, python-mock, python3-mock, python-requests, > python3-requests, python-tox, python-xmltodict > Filtered Build-Depends: debhelper (>= 9), dh-python, python-all, python3-all, > python-setuptools, python3-setuptools, python-flake8, python3-flake8, > python-nose, python3-nose, python-mock, python3-mock, python-requests, > python3-requests, python-tox, python-xmltodict > dpkg-deb: building package 'sbuild-build-depends-python-osmapi-dummy' in > '/<>/resolver-h0nzmX/apt_archive/sbuild-build-depends-python-osmapi-dummy.deb'. > dpkg-scanpackages: warning: Packages in archive but missing from override > file: > dpkg-scanpackages: warning: sbuild-build-depends-core-dummy > sbuild-build-depends-python-osmapi-dummy > dpkg-scanpackages: info: Wrote 2 entries to output Packages file. > Ign:1 copy:/<>/resolver-h0nzmX/apt_archive ./ InRelease > Get:2 copy:/<>/resolver-h0nzmX/apt_archive ./ Release [963 B] > Ign:3 copy:/<>/resolver-h0nzmX/apt_archive ./ Release.gpg > Get:4 copy:/<>/resolver-h0nzmX/apt_archive ./ Sources [567 B] > Get:5 copy:/<>/resolver-h0nzmX/apt_archive ./ Packages [647 B] > Fetched 2177 B in 0s (0 B/s) > Reading package lists... > Reading package lists... > > Install python-osmapi build dependencies (apt-based resolver) > - > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > sbuild-build-depends-python-osmapi-dummy : Depends: python-tox but it is not > installable > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://aws-logs.debian.net/2019/03/15/python-osmapi_1.2.2-1_testing.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: python-osmapi Source-Version: 1.2.2-2 We believe that the bug you reported is fixed in the latest version of python-osmapi, 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 924...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bas Couwenberg (supplier of updated python-osmapi 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: Sun, 17 Mar 2019 1
Processed: Re: Bug#924833: qgis: FTBFS: sip_corepart0.cpp:38215:19: error: 'QgsPointV2 sipQgsPolygonV2::vertexAt(const QgsVertexId&) const' marked 'override', but does not override
Processing commands for cont...@bugs.debian.org: > fixed 924833 qgis/3.4.5+dfsg-1~exp1 Bug #924833 [src:qgis] qgis: FTBFS: sip_corepart0.cpp:38215:19: error: 'QgsPointV2 sipQgsPolygonV2::vertexAt(const QgsVertexId&) const' marked 'override', but does not override Marked as fixed in versions qgis/3.4.5+dfsg-1~exp1. > thanks Stopping processing here. Please contact me if you need assistance. -- 924833: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924833 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#924833: qgis: FTBFS: sip_corepart0.cpp:38215:19: error: 'QgsPointV2 sipQgsPolygonV2::vertexAt(const QgsVertexId&) const' marked 'override', but does not override
Processing control commands: > tags -1 confirmed Bug #924833 [src:qgis] qgis: FTBFS: sip_corepart0.cpp:38215:19: error: 'QgsPointV2 sipQgsPolygonV2::vertexAt(const QgsVertexId&) const' marked 'override', but does not override Added tag(s) confirmed. -- 924833: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924833 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#924833: qgis: FTBFS: sip_corepart0.cpp:38215:19: error: 'QgsPointV2 sipQgsPolygonV2::vertexAt(const QgsVertexId&) const' marked 'override', but does not override
Control: tags -1 confirmed Looks like sip4 (4.19.14+dfsg-1) broke the SIP bindings again. It's quite unfortunate that the 2.18.x LTR is EOL upstream, making them unlikely to provide a fix. I'll see what I can do to fix this. If I can't, we'll just have to release buster without QGIS and deal with lots of upset users. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#924826: python-osmapi: FTBFS: build-dependency not installable: python-tox
Control: tags -1 pending On 3/17/19 7:05 PM, Lucas Nussbaum wrote: >> sbuild-build-depends-python-osmapi-dummy : Depends: python-tox but it is >> not installable According to #922487 the transition package was removed, but this was not coordinated. The B-D has been replaced with 'tox' to fix this issue. A new upload to unstable will follow shortly. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Processed: Re: Bug#924826: python-osmapi: FTBFS: build-dependency not installable: python-tox
Processing control commands: > tags -1 pending Bug #924826 [src:python-osmapi] python-osmapi: FTBFS: build-dependency not installable: python-tox Added tag(s) pending. -- 924826: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924826 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#899007: bauble: Depends on unmaintained python-gdata
hello all, bauble as bauble is indeed dead, both the classic and the web version, which by the way never saw light. → HOWEVER → → while Debian and ubuntu still distribute the grossly outdated bauble 0.9.7, development of bauble went up to version 1.0.56, which is still a very decent option. → beyond version 1.0.56 development goes absolutely uninterrupted on, now under the name ghini.desktop. the last released version of bauble informs the user about ghini.desktop, and its new releases. → there is no plan to substitute ghini.desktop with a web application: there is a ghini.web, which serves a quite different task (integrating databases), → there might come a ghini.web version allowing limited data insertion. this is not planned at all at the moment. → other packages in the Ghini suite are two Android apps. I have been working at a python3 ghini.desktop version, and hope to release it before we reach EOL for python2. I'm stuck with some strange delays in database access, which I still need to pin down. I have not been able to follow all necessary steps to put ghini.desktop in Debian format, I'm sorry. once there's a well defined package for it, I might be able to keep it up to date, but the initial steps are far beyond my limited ability to comply with strict rules. Debian Science team? what is it? buona giornata, grazie, Mario On 17/03/2019 13:05, Giacomo Catenazzi wrote: > Hello Andreas, > > I gave the package to Mario Frasca, which then orphaned the package: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903644 > > gdata is not the only problem, there are other dependencies (which > seems to be more complex to solve). Additionally as far I know there > is no interest of upstream to continue such package, which I think it > is also reasonable: a web application is a lot better. > > For my point of view, you can put into Debian Science, but possibly we > should let it go. > > ciao > cate > > > On 17.03.19 18:29, Andreas Tille wrote: >> Hi Giacomo, >> >> the bug log states that the files using gdata have been removed >> upstream[1]. I'd volunteer to commit this package to Salsa in Debian >> Science, apply the needed patch and upload as a team upload if you don't >> mind. If I will not hear from you soon I assume you are fine with >> the move into Debian Science team. >> >> Kind regards >> >> Andreas. >> >> [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899007#15 >>
Processed: severity of 922767 is serious
Processing commands for cont...@bugs.debian.org: > severity 922767 serious Bug #922767 [libemf] libemf : FTBFS - mv: cannot stat 'refman.pdf': No such file or directory - Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 922767: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922767 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#924847: i2p: FTBFS: [javac] /<>/apps/jetty/java/src/net/i2p/jetty/I2PRequestLog.java:378: error: method write in interface Writer cannot be applied to given types;
Source: i2p Version: 0.9.38-3 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20190315 qa-ftbfs Justification: FTBFS in buster on amd64 Hi, During a rebuild of all packages in buster (in a buster chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_shlibdeps -llibjbigi-jni debian/libjbigi-jni/usr/lib/jni/*.so > make[1]: Leaving directory '/<>' >dh_installdeb -a >dh_gencontrol -a >dh_md5sums -a >dh_builddeb -a > dpkg-deb: building package 'libjbigi-jni-dbgsym' in > '../libjbigi-jni-dbgsym_0.9.38-3_amd64.deb'. > dpkg-deb: building package 'libjbigi-jni' in > '../libjbigi-jni_0.9.38-3_amd64.deb'. > dh_prep > mkdir -p /<>/installer/lib/wrapper/all > ln -sf /usr/share/java/wrapper.jar > /<>/installer/lib/wrapper/all/wrapper.jar > if [ ! -e /<>/debian/routerversion.java.bak ]; then \ > cp /<>/router/java/src/net/i2p/router/RouterVersion.java > /<>/debian/routerversion.java.bak; \ > fi > sed -e "s/\(.*EXTRA\ =\ \)[^ ]*\"\(.*\)\"/\1\"-$EXTRAPREFIX$DEBIANVERSION\"/" > < /<>/router/java/src/net/i2p/router/RouterVersion.java > > /<>/router/java/src/net/i2p/router/RouterVersion.java.tmp > mv -f /<>/router/java/src/net/i2p/router/RouterVersion.java.tmp > /<>/router/java/src/net/i2p/router/RouterVersion.java > mkdir -p /<>/apps/jetty/jettylib > ln -sf /usr/share/java/jetty9-continuation.jar > /<>/apps/jetty/jettylib/jetty-continuation.jar > ln -sf /usr/share/java/jetty9-deploy.jar > /<>/apps/jetty/jettylib/jetty-deploy.jar > ln -sf /usr/share/java/jetty9-http.jar > /<>/apps/jetty/jettylib/jetty-http.jar > ln -sf /usr/share/java/jetty9-io.jar > /<>/apps/jetty/jettylib/jetty-io.jar > ln -sf /usr/share/java/jetty9-rewrite.jar > /<>/apps/jetty/jettylib/jetty-rewrite-handler.jar > ln -sf /usr/share/java/jetty9-security.jar > /<>/apps/jetty/jettylib/jetty-security.jar > ln -sf /usr/share/java/jetty9-servlet.jar > /<>/apps/jetty/jettylib/jetty-servlet.jar > ln -sf /usr/share/java/jetty9-servlets.jar > /<>/apps/jetty/jettylib/jetty-servlets.jar > ln -sf /usr/share/java/jetty9-start.jar > /<>/apps/jetty/jettylib/jetty-start.jar > ln -sf /usr/share/java/jetty9-util.jar > /<>/apps/jetty/jettylib/jetty-util.jar > ln -sf /usr/share/java/jetty9-webapp.jar > /<>/apps/jetty/jettylib/jetty-webapp.jar > ln -sf /usr/share/java/jetty9-xml.jar > /<>/apps/jetty/jettylib/jetty-xml.jar > ln -sf /usr/share/java/jetty9-server.jar > /<>/apps/jetty/jettylib/org.mortbay.jetty.jar > ln -sf /usr/share/java/jetty9-jmx.jar > /<>/apps/jetty/jettylib/org.mortbay.jmx.jar > ln -sf /usr/share/java/servlet-api-3.1.jar > /<>/apps/jetty/jettylib/javax.servlet.jar > ln -sf /usr/share/java/jsp-api-2.3.jar > /<>/apps/jetty/jettylib/jsp-api.jar > mkdir -p /<>/apps/jetty/jettylib > ln -sf /usr/share/java/tomcat9-api.jar > /<>/apps/jetty/jettylib/tomcat-api.jar > ln -sf /usr/share/java/tomcat9-coyote.jar > /<>/apps/jetty/jettylib/tomcat-coyote.jar > ln -sf /usr/share/java/tomcat9-el-api.jar > /<>/apps/jetty/jettylib/commons-el.jar > ln -sf /usr/share/java/tomcat9-jasper.jar > /<>/apps/jetty/jettylib/jasper-runtime.jar > ln -sf /usr/share/java/tomcat9-jasper-el.jar > /<>/apps/jetty/jettylib/jasper-el.jar > ln -sf /usr/share/java/tomcat9-juli.jar > /<>/apps/jetty/jettylib/commons-logging.jar > ln -sf /usr/share/java/tomcat9-util.jar > /<>/apps/jetty/jettylib/tomcat-util.jar > ln -sf /usr/share/java/tomcat9-util-scan.jar > /<>/apps/jetty/jettylib/tomcat-util-scan.jar > ln -sf /usr/share/java/taglibs-standard-spec.jar > /<>/apps/susidns/src/lib/jstl.jar > ln -sf /usr/share/java/taglibs-standard-impl.jar > /<>/apps/susidns/src/lib/standard.jar > ln -sf /usr/share/java/taglibs-standard-jstlel.jar > /<>/apps/susidns/src/lib/jstlel.jar > ln -sf /usr/share/java/libintl.jar > /<>/core/java/build/libintl.jar > ln -sf /usr/share/java/gnu-getopt.jar > /<>/core/java/build/gnu-getopt.jar > ln -sf /usr/share/java/json-simple.jar > /<>/core/java/build/json-simple.jar > TZ=UTC JAVA_TOOL_OPTIONS=-Dfile.encoding=UTF8 ant preppkg-unix javadoc > Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF8 > Buildfile: /<>/build.xml > > checkForMtn: > > getMtnRev: > > getReleaseNumber: > [echo] Release number is 0.9.38 > > getBuildNumber: > [echo] Build number is 0-3 > > setBuildTimestamp: > > disableManifestClasspath: > > buildProperties: > [echo] Building version 0.9.38-0-3 (mtn rev unknown) > > buildCore: > > depend: > > compile: > [mkdir] Created dir: /<>/core/java/build/obj > [javac] Compiling 337 source files to /<>/core/java/build/obj > [javac] warning: [options] bootstrap class path not set in conjunction > with -source 7 > [javac] /<>/core/java/src/net/i2p/I2PAppContext.java:36: > warning: [deprecation] SimpleScheduler in net.i2p.util has been deprecated > [javac] import net.i2p.util.SimpleScheduler; > [javac]^ > [javac] /<>/core/java/src
Bug#924846: qtscript-opensource-src: FTBFS: ../3rdparty/javascriptcore/JavaScriptCore/jit/JITStubs.cpp:483:5: error: expected '(' before 'volatile'
Source: qtscript-opensource-src Version: 5.11.3+dfsg-2 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20190315 qa-ftbfs Justification: FTBFS in buster on amd64 Hi, During a rebuild of all packages in buster (in a buster chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): > g++ -c -include .pch/Qt5Script -g -O2 -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fno-strict-aliasing > -Wall -Wreturn-type -Wcast-align -Wchar-subscripts -Wformat-security > -Wreturn-type -Wno-unused-parameter -Wno-sign-compare -Wno-switch > -Wno-switch-enum -Wundef -Wmissing-noreturn -Winit-self -fno-stack-protector > -g -O2 -fdebug-prefix-map=/<>/qtscript-opensource-src-5.11.3+dfsg=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++1y > -fvisibility=hidden -fvisibility-inlines-hidden -fno-exceptions -D_REENTRANT > -fPIC -DQT_NO_FOREACH -DJSC=QTJSC -Djscyyparse=qtjscyyparse > -Djscyylex=qtjscyylex -Djscyyerror=qtjscyyerror -DWTF=QTWTF > -DQT_NO_USING_NAMESPACE -DQLALR_NO_QSCRIPTGRAMMAR_DEBUG_INFO > -DBUILDING_QT__=1 -DWTF_USE_ACCELERATED_COMPOSITING -DNDEBUG -DLOG_DISABLED=1 > -DBUILDING_QT__ -DBUILDING_JavaScriptCore -DBUILDING_WTF > -DWTF_USE_JAVASCRIPTCORE_BINDINGS=1 -DWTF_CHANGES=1 -DJS_NO_EXPORT > -DQT_NO_NARROWING_CONVERSIONS_IN_CONNECT -DQT_BUILD_SCRIPT_LIB > -DQT_BUILDING_QT -DQT_NO_CAST_TO_ASCII -DQT_ASCII_CAST_WARNINGS > -DQT_MOC_COMPAT -DQT_USE_QSTRINGBUILDER -DQT_DEPRECATED_WARNINGS > -DQT_DISABLE_DEPRECATED_BEFORE=0x05 -DQT_NO_EXCEPTIONS > -D_LARGEFILE64_SOURCE -D_LARGEFILE_SOURCE -DQT_NO_DEBUG -DQT_CORE_LIB -I. > -I../3rdparty/javascriptcore/JavaScriptCore -I../3rdparty/javascriptcore > -I../3rdparty/javascriptcore/JavaScriptCore/assembler > -I../3rdparty/javascriptcore/JavaScriptCore/bytecode > -I../3rdparty/javascriptcore/JavaScriptCore/bytecompiler > -I../3rdparty/javascriptcore/JavaScriptCore/debugger > -I../3rdparty/javascriptcore/JavaScriptCore/interpreter > -I../3rdparty/javascriptcore/JavaScriptCore/jit > -I../3rdparty/javascriptcore/JavaScriptCore/parser > -I../3rdparty/javascriptcore/JavaScriptCore/pcre > -I../3rdparty/javascriptcore/JavaScriptCore/profiler > -I../3rdparty/javascriptcore/JavaScriptCore/runtime > -I../3rdparty/javascriptcore/JavaScriptCore/wrec > -I../3rdparty/javascriptcore/JavaScriptCore/wtf > -I../3rdparty/javascriptcore/JavaScriptCore/wtf/symbian > -I../3rdparty/javascriptcore/JavaScriptCore/wtf/unicode > -I../3rdparty/javascriptcore/JavaScriptCore/yarr > -I../3rdparty/javascriptcore/JavaScriptCore/API > -I../3rdparty/javascriptcore/JavaScriptCore/ForwardingHeaders > -I../3rdparty/javascriptcore/JavaScriptCore/generated > -I/<>/qtscript-opensource-src-5.11.3+dfsg/src/3rdparty/javascriptcore/WebKit/qt/Api > -I../3rdparty/javascriptcore/JavaScriptCore/pcre > -I/<>/qtscript-opensource-src-5.11.3+dfsg/src/3rdparty/javascriptcore/JavaScriptCore/tmp > -I. -Iparser -I../../include -I../../include/QtScript > -I../../include/QtScript/5.11.3 -I../../include/QtScript/5.11.3/QtScript > -isystem /usr/include/x86_64-linux-gnu/qt5/QtCore/5.11.3 -isystem > /usr/include/x86_64-linux-gnu/qt5/QtCore/5.11.3/QtCore -isystem > /usr/include/x86_64-linux-gnu/qt5 -isystem > /usr/include/x86_64-linux-gnu/qt5/QtCore -I.moc > -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o obj/release/JITStubs.o > ../3rdparty/javascriptcore/JavaScriptCore/jit/JITStubs.cpp > In file included from > ../3rdparty/javascriptcore/JavaScriptCore/runtime/ArgList.h:28, > from > ../3rdparty/javascriptcore/JavaScriptCore/runtime/JSObject.h:26, > from > ../3rdparty/javascriptcore/JavaScriptCore/runtime/InternalFunction.h:27, > from > ../3rdparty/javascriptcore/JavaScriptCore/runtime/JSFunction.h:27, > from > ../3rdparty/javascriptcore/JavaScriptCore/runtime/Executable.h:29, > from > ../3rdparty/javascriptcore/JavaScriptCore/bytecode/EvalCodeCache.h:32, > from > ../3rdparty/javascriptcore/JavaScriptCore/bytecode/CodeBlock.h:33, > from ../3rdparty/javascriptcore/JavaScriptCore/jit/JIT.h:43, > from > ../3rdparty/javascriptcore/JavaScriptCore/jit/JITOpcodes.cpp:27: > ../3rdparty/javascriptcore/JavaScriptCore/wtf/Vector.h: In instantiation of > 'static void QTWTF::VectorMover::move(T*, const T*, T*) [with T = > QTWTF::RefPtr]': > ../3rdparty/javascriptcore/JavaScriptCore/wtf/Vector.h:266:69: required > from 'static void QTWTF::VectorTypeOperations::move(T*, const T*, T*) > [with T = QTWTF::RefPtr]' > ../3rdparty/javascriptcore/JavaScriptCore/wtf/Vector.h:810:33: required > from 'void QTWTF::Vector::reserveCapacity(size_t) [with T > = QTWTF::RefPtr; long unsigned int inlineCapacity > = 0; size_t = long unsigned int]' > ../3rdparty/
Bug#924845: nanoc: FTBFS: build-dependency not installable: ruby-fog (>= 0.13.0~)
Source: nanoc Version: 4.11.0-2 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20190315 qa-ftbfs Justification: FTBFS in buster on amd64 Hi, During a rebuild of all packages in buster (in a buster chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: asciidoc-base, asciidoctor, coderay, debhelper (>= > 10~), gem2deb, git, highlight, pry, python-pygments, rake, rsync, > ruby-addressable (>= 2.5~), ruby-adsf, ruby-builder, ruby-coffee-script, > ruby-contracts, ruby-coveralls, ruby-cri (>= 2.15~), ruby-ddmetrics, > ruby-ddmemoize, ruby-ddplugin, ruby-erubi, ruby-erubis, ruby-fog (>= > 0.13.0~), ruby-fuubar, ruby-haml, ruby-hamster, ruby-brandur-json-schema, > ruby-kramdown, ruby-listen, ruby-maruku, ruby-mime-types, ruby-minitest, > ruby-mocha, ruby-mustache, ruby-nokogiri, ruby-nokogumbo, ruby-parallel (>= > 1.12~), ruby-pygments.rb, ruby-rack, ruby-rdiscount, ruby-redcarpet, > ruby-redcloth, ruby-ref, ruby-rouge (>= 2~), ruby-rspec, ruby-rspec-its, > ruby-rubypants, ruby-sass (>= 3.2.2~), ruby-slim, ruby-slow-enumerator-tools, > ruby-timecop, ruby-tomlrb (>= 1.2~), ruby-uglifier, yard > Filtered Build-Depends: asciidoc-base, asciidoctor, coderay, debhelper (>= > 10~), gem2deb, git, highlight, pry, python-pygments, rake, rsync, > ruby-addressable (>= 2.5~), ruby-adsf, ruby-builder, ruby-coffee-script, > ruby-contracts, ruby-coveralls, ruby-cri (>= 2.15~), ruby-ddmetrics, > ruby-ddmemoize, ruby-ddplugin, ruby-erubi, ruby-erubis, ruby-fog (>= > 0.13.0~), ruby-fuubar, ruby-haml, ruby-hamster, ruby-brandur-json-schema, > ruby-kramdown, ruby-listen, ruby-maruku, ruby-mime-types, ruby-minitest, > ruby-mocha, ruby-mustache, ruby-nokogiri, ruby-nokogumbo, ruby-parallel (>= > 1.12~), ruby-pygments.rb, ruby-rack, ruby-rdiscount, ruby-redcarpet, > ruby-redcloth, ruby-ref, ruby-rouge (>= 2~), ruby-rspec, ruby-rspec-its, > ruby-rubypants, ruby-sass (>= 3.2.2~), ruby-slim, ruby-slow-enumerator-tools, > ruby-timecop, ruby-tomlrb (>= 1.2~), ruby-uglifier, yard > dpkg-deb: building package 'sbuild-build-depends-nanoc-dummy' in > '/<>/resolver-nauGEh/apt_archive/sbuild-build-depends-nanoc-dummy.deb'. > dpkg-scanpackages: warning: Packages in archive but missing from override > file: > dpkg-scanpackages: warning: sbuild-build-depends-core-dummy > sbuild-build-depends-nanoc-dummy > dpkg-scanpackages: info: Wrote 2 entries to output Packages file. > Ign:1 copy:/<>/resolver-nauGEh/apt_archive ./ InRelease > Get:2 copy:/<>/resolver-nauGEh/apt_archive ./ Release [963 B] > Ign:3 copy:/<>/resolver-nauGEh/apt_archive ./ Release.gpg > Get:4 copy:/<>/resolver-nauGEh/apt_archive ./ Sources [846 B] > Get:5 copy:/<>/resolver-nauGEh/apt_archive ./ Packages [918 B] > Fetched 2727 B in 0s (0 B/s) > Reading package lists... > Reading package lists... > > Install nanoc build dependencies (apt-based resolver) > - > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > sbuild-build-depends-nanoc-dummy : Depends: ruby-fog (>= 0.13.0~) but it is > not installable > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://aws-logs.debian.net/2019/03/15/nanoc_4.11.0-2_testing.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.
Bug#924850: netpipe: FTBFS: Errors while processing: openmpi-bin libopenmpi-dev:amd64 sbuild-build-depends-netpipe-dummy
Source: netpipe Version: 3.7.2-7.4 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20190315 qa-ftbfs Justification: FTBFS in buster on amd64 Hi, During a rebuild of all packages in buster (in a buster chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: lam4-dev (>= 7.1.1-5), libopenmpi-dev, libmpich-dev, > pvm-dev, debhelper (>= 9) > Filtered Build-Depends: lam4-dev (>= 7.1.1-5), libopenmpi-dev, libmpich-dev, > pvm-dev, debhelper (>= 9) > dpkg-deb: building package 'sbuild-build-depends-netpipe-dummy' in > '/<>/resolver-cC9WmF/apt_archive/sbuild-build-depends-netpipe-dummy.deb'. > dpkg-scanpackages: warning: Packages in archive but missing from override > file: > dpkg-scanpackages: warning: sbuild-build-depends-core-dummy > sbuild-build-depends-netpipe-dummy > dpkg-scanpackages: info: Wrote 2 entries to output Packages file. > Ign:1 copy:/<>/resolver-cC9WmF/apt_archive ./ InRelease > Get:2 copy:/<>/resolver-cC9WmF/apt_archive ./ Release [963 B] > Ign:3 copy:/<>/resolver-cC9WmF/apt_archive ./ Release.gpg > Get:4 copy:/<>/resolver-cC9WmF/apt_archive ./ Sources [585 B] > Get:5 copy:/<>/resolver-cC9WmF/apt_archive ./ Packages [600 B] > Fetched 2148 B in 0s (0 B/s) > Reading package lists... > Reading package lists... > > Install netpipe build dependencies (apt-based resolver) > --- > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > The following additional packages will be installed: > autoconf automake autopoint autotools-dev bsdmainutils debhelper > dh-autoreconf dh-strip-nondeterminism dwz file gettext gettext-base gfortran > gfortran-8 groff-base hwloc-nox ibverbs-providers intltool-debian lam4-dev > libarchive-zip-perl libbsd0 libcroco3 libedit2 libelf1 libevent-2.1-6 > libevent-core-2.1-6 libevent-pthreads-2.1-6 libfabric1 > libfile-stripnondeterminism-perl libgfortran-8-dev libgfortran5 libglib2.0-0 > libgssapi-krb5-2 libhwloc-dev libhwloc-plugins libhwloc5 libibverbs-dev > libibverbs1 libicu63 libk5crypto3 libkeyutils1 libkrb5-3 libkrb5support0 > liblam4 libltdl-dev libltdl7 libmagic-mgc libmagic1 libmpich-dev libmpich12 > libncurses-dev libncurses6 libnl-3-200 libnl-3-dev libnl-route-3-200 > libnl-route-3-dev libnuma-dev libnuma1 libopenmpi-dev libopenmpi3 > libpciaccess0 libpipeline1 libpmix2 libpsm-infinipath1 libpsm2-2 libpvm3 > librdmacm1 libreadline-dev libreadline7 libsigsegv2 libssl1.1 libtool > libuchardet0 libxml2 m4 man-db mpich ocl-icd-libopencl1 openmpi-bin > openmpi-common openssh-client po-debconf pvm pvm-dev readline-common > sensible-utils > Suggested packages: > autoconf-archive gnu-standards autoconf-doc wamerican | wordlist whois > vacation dh-make gettext-doc libasprintf-dev libgettextpo-dev > gfortran-multilib gfortran-doc gfortran-8-multilib gfortran-8-doc > libgfortran5-dbg libcoarrays-dev groff krb5-doc krb5-user > libhwloc-contrib-plugins libtool-doc ncurses-doc openmpi-doc pciutils > readline-doc gcj-jdk m4-doc apparmor less www-browser mpich-doc opencl-icd > keychain libpam-ssh monkeysphere ssh-askpass libmail-box-perl > Recommended packages: > curl | wget | lynx libarchive-cpio-perl libglib2.0-data shared-mime-info > xdg-user-dirs krb5-locales lam-runtime libgpm2 libcoarrays-openmpi-dev xauth > libmail-sendmail-perl > The following NEW packages will be installed: > autoconf automake autopoint autotools-dev bsdmainutils debhelper > dh-autoreconf dh-strip-nondeterminism dwz file gettext gettext-base gfortran > gfortran-8 groff-base hwloc-nox ibverbs-providers intltool-debian lam4-dev > libarchive-zip-perl libbsd0 libcroco3 libedit2 libelf1 libevent-2.1-6 > libevent-core-2.1-6 libevent-pthreads-2.1-6 libfabric1 > libfile-stripnondeterminism-perl libgfortran-8-dev libgfortran5 libglib2.0-0 > libgssapi-krb5-2 libhwloc-dev libhwloc-plugins libhwloc5 libibverbs-dev > libibverbs1 libicu63 libk5crypto3 libkeyutils1 libkrb5-3 libkrb5support0 > liblam4 libltdl-dev libltdl7 libmagic-mgc libmagic1 libmpich-dev libmpich12 > libncurses-dev libncurses6 libnl-3-200 libnl-3-dev libnl-route-3-200 > libnl-route-3-dev libnuma-dev libnuma1 libopenmpi-dev libopenmpi3 > libpciaccess0 libpipeline1 libpmix2 libpsm-infinipath1 libpsm2-2 libpvm3 > librdmacm1 libreadline-dev libreadline7 libsigsegv2 libssl1.1 libtool > libuchardet0 libxml2 m4 man-db mpich ocl-icd-libopencl1 openmpi-bin > openmpi-common openssh-client po-debconf pvm pvm-dev readline-common > sbuild-build-depends-netpipe-du
Bug#924848: telegram-cli: FTBFS: build-dependency not installable: libwolfssl-dev
Source: telegram-cli Version: 1.3.1+git20160323.6547c0b21-1 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20190315 qa-ftbfs Justification: FTBFS in buster on amd64 Hi, During a rebuild of all packages in buster (in a buster chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: autoconf-archive, debhelper (>= 11), libconfig-dev, > libevent-dev, libgcrypt-dev, libjansson-dev, liblua5.2-dev, libreadline-dev, > libtgl-0.0.0.20160623-dev, libwolfssl-dev, lua-lgi, lua5.2, zlib1g-dev > Filtered Build-Depends: autoconf-archive, debhelper (>= 11), libconfig-dev, > libevent-dev, libgcrypt-dev, libjansson-dev, liblua5.2-dev, libreadline-dev, > libtgl-0.0.0.20160623-dev, libwolfssl-dev, lua-lgi, lua5.2, zlib1g-dev > dpkg-deb: building package 'sbuild-build-depends-telegram-cli-dummy' in > '/<>/resolver-HiFCxw/apt_archive/sbuild-build-depends-telegram-cli-dummy.deb'. > dpkg-scanpackages: warning: Packages in archive but missing from override > file: > dpkg-scanpackages: warning: sbuild-build-depends-core-dummy > sbuild-build-depends-telegram-cli-dummy > dpkg-scanpackages: info: Wrote 2 entries to output Packages file. > Ign:1 copy:/<>/resolver-HiFCxw/apt_archive ./ InRelease > Get:2 copy:/<>/resolver-HiFCxw/apt_archive ./ Release [963 B] > Ign:3 copy:/<>/resolver-HiFCxw/apt_archive ./ Release.gpg > Get:4 copy:/<>/resolver-HiFCxw/apt_archive ./ Sources [580 B] > Get:5 copy:/<>/resolver-HiFCxw/apt_archive ./ Packages [660 B] > Fetched 2203 B in 0s (0 B/s) > Reading package lists... > Reading package lists... > > Install telegram-cli build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > sbuild-build-depends-telegram-cli-dummy : Depends: libwolfssl-dev but it is > not installable > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://aws-logs.debian.net/2019/03/15/telegram-cli_1.3.1+git20160323.6547c0b21-1_testing.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.
Bug#924840: highwayhash: FTBFS: dh_makeshlibs: failing due to earlier errors
Source: highwayhash Version: 0~git20181002.c5ee50b-3 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20190315 qa-ftbfs Justification: FTBFS in buster on amd64 Hi, During a rebuild of all packages in buster (in a buster chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<>' > g++ -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong > -Wformat -Werror=format-security -std=c++11 -Wall -O3 -fPIC -pthread > -Wl,-z,relro -Wl,-z,now -pthread -shared obj/sip_hash.o obj/sip_tree_hash.o > obj/scalar_sip_tree_hash.o obj/arch_specific.o obj/instruction_sets.o > obj/nanobenchmark.o obj/os_specific.o obj/hh_portable.o obj/hh_avx2.o > obj/hh_sse41.o obj/c_bindings.o -o lib/libhighwayhash.so.0 > -Wl,-soname,libhighwayhash.so.0 > mkdir -p /<>/debian/tmp//usr/lib/x86_64-linux-gnu/ > mkdir -p /<>/debian/tmp//usr/include//highwayhash > install -m0444 lib/libhighwayhash.a > /<>/debian/tmp//usr/lib/x86_64-linux-gnu/ > install -m0555 lib/libhighwayhash.so > /<>/debian/tmp//usr/lib/x86_64-linux-gnu/ > install -m0444 highwayhash/*.h > /<>/debian/tmp//usr/include//highwayhash/ > make[2]: Leaving directory '/<>' > mkdir -p debian/libhighwayhash0/usr/lib/x86_64-linux-gnu > rename 's/.so/.so.0/' debian/tmp/usr/lib/x86_64-linux-gnu/*.so > install -m0755 debian/tmp/usr/lib/x86_64-linux-gnu/*.so.0 \ > debian/libhighwayhash0/usr/lib/x86_64-linux-gnu/ > mkdir -p debian/libhighwayhash-dev/usr/lib/x86_64-linux-gnu > install -m0755 debian/tmp/usr/lib/x86_64-linux-gnu/*.a \ > debian/libhighwayhash-dev/usr/lib/x86_64-linux-gnu/ > set -e; cd debian/libhighwayhash-dev/usr/lib/x86_64-linux-gnu/; \ > ln -s libhighwayhash.so.0 libhighwayhash.so > make[1]: Leaving directory '/<>' >dh_install >dh_installdocs >dh_installchangelogs >dh_installman >dh_lintian >dh_perl >dh_link >dh_strip_nondeterminism >dh_compress >dh_fixperms >dh_missing >dh_strip >dh_makeshlibs > dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols > file: see diff output below > dpkg-gensymbols: warning: debian/libhighwayhash0/DEBIAN/symbols doesn't match > completely debian/libhighwayhash0.symbols > --- debian/libhighwayhash0.symbols > (libhighwayhash0_0~git20181002.c5ee50b-3_amd64) > +++ dpkg-gensymbolsg8mdHJ 2019-03-16 04:54:58.805876282 + > @@ -64,7 +64,7 @@ > > _ZNSt23mersenne_twister_engineImLm64ELm312ELm156ELm31ELm13043109905998158313ELm29ELm6148914691236517205ELm17ELm8202884508482404352ELm37ELm1873444759240704ELm43ELm6364136223846793005EEclEv@Base > 0~20180209-g14dedec > > _ZNSt24uniform_int_distributionImEclISt20discard_block_engineISt26subtract_with_carry_engineImLm48ELm5ELm12EELm389ELm11mRT_RKNS0_10param_typeE@Base > 0~20170419-g1f4a24f > > _ZNSt6vectorISt4pairIjiESaIS1_EE17_M_realloc_insertIJS1_EEEvN9__gnu_cxx17__normal_iteratorIPS1_S3_EEDpOT_@Base > 0~20180103-geeea446 > - > _ZNSt6vectorIjSaIjEE17_M_realloc_insertIJRKjEEEvN9__gnu_cxx17__normal_iteratorIPjS1_EEDpOT_@Base > 0~20180209-g14dedec > +#MISSING: 0~git20181002.c5ee50b-3# > _ZNSt6vectorIjSaIjEE17_M_realloc_insertIJRKjEEEvN9__gnu_cxx17__normal_iteratorIPjS1_EEDpOT_@Base > 0~20180209-g14dedec > _ZNSt6vectorImSaImEE17_M_default_appendEm@Base 0~20180209-g14dedec > > _ZNSt8_Rb_treeImSt4pairIKmSt6vectorIjSaIjEEESt10_Select1stIS5_ESt4lessImESaIS5_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS5_ERS1_@Base > 0~20170419-g1f4a24f > > _ZNSt8_Rb_treeImSt4pairIKmSt6vectorIjSaIjEEESt10_Select1stIS5_ESt4lessImESaIS5_EE8_M_eraseEPSt13_Rb_tree_nodeIS5_E@Base > 0~20170419-g1f4a24f > dh_makeshlibs: failing due to earlier errors > make: *** [debian/rules:22: binary] Error 2 The full build log is available from: http://aws-logs.debian.net/2019/03/15/highwayhash_0~git20181002.c5ee50b-3_testing.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.
Bug#924838: scoop: FTBFS: Could not import extension sphinx.ext.pngmath (exception: No module named pngmath)
Source: scoop Version: 0.7.1.1-2 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20190315 qa-ftbfs Justification: FTBFS in buster on amd64 Hi, During a rebuild of all packages in buster (in a buster chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_install > I: pybuild base:217: /usr/bin/python setup.py install --root > /<>/debian/python-scoop > running install > running build > running build_py > running install_lib > creating /<>/debian/python-scoop/usr > creating /<>/debian/python-scoop/usr/lib > creating /<>/debian/python-scoop/usr/lib/python2.7 > creating /<>/debian/python-scoop/usr/lib/python2.7/dist-packages > creating > /<>/debian/python-scoop/usr/lib/python2.7/dist-packages/scoop > copying > /<>/.pybuild/cpython2_2.7_scoop/build/scoop/encapsulation.pyc -> > /<>/debian/python-scoop/usr/lib/python2.7/dist-packages/scoop > copying /<>/.pybuild/cpython2_2.7_scoop/build/scoop/__init__.pyc > -> /<>/debian/python-scoop/usr/lib/python2.7/dist-packages/scoop > copying > /<>/.pybuild/cpython2_2.7_scoop/build/scoop/encapsulation.py -> > /<>/debian/python-scoop/usr/lib/python2.7/dist-packages/scoop > creating > /<>/debian/python-scoop/usr/lib/python2.7/dist-packages/scoop/_comm > copying > /<>/.pybuild/cpython2_2.7_scoop/build/scoop/_comm/scoopexceptions.pyc > -> > /<>/debian/python-scoop/usr/lib/python2.7/dist-packages/scoop/_comm > copying > /<>/.pybuild/cpython2_2.7_scoop/build/scoop/_comm/scoopzmq.py -> > /<>/debian/python-scoop/usr/lib/python2.7/dist-packages/scoop/_comm > copying > /<>/.pybuild/cpython2_2.7_scoop/build/scoop/_comm/__init__.pyc > -> > /<>/debian/python-scoop/usr/lib/python2.7/dist-packages/scoop/_comm > copying > /<>/.pybuild/cpython2_2.7_scoop/build/scoop/_comm/scoopzmq.pyc > -> > /<>/debian/python-scoop/usr/lib/python2.7/dist-packages/scoop/_comm > copying > /<>/.pybuild/cpython2_2.7_scoop/build/scoop/_comm/scoopexceptions.py > -> > /<>/debian/python-scoop/usr/lib/python2.7/dist-packages/scoop/_comm > copying > /<>/.pybuild/cpython2_2.7_scoop/build/scoop/_comm/__init__.py -> > /<>/debian/python-scoop/usr/lib/python2.7/dist-packages/scoop/_comm > copying > /<>/.pybuild/cpython2_2.7_scoop/build/scoop/_comm/scooptcp.py -> > /<>/debian/python-scoop/usr/lib/python2.7/dist-packages/scoop/_comm > copying /<>/.pybuild/cpython2_2.7_scoop/build/scoop/shared.pyc > -> /<>/debian/python-scoop/usr/lib/python2.7/dist-packages/scoop > creating > /<>/debian/python-scoop/usr/lib/python2.7/dist-packages/scoop/launch > copying > /<>/.pybuild/cpython2_2.7_scoop/build/scoop/launch/__init__.py > -> > /<>/debian/python-scoop/usr/lib/python2.7/dist-packages/scoop/launch > copying > /<>/.pybuild/cpython2_2.7_scoop/build/scoop/launch/brokerLaunch.py > -> > /<>/debian/python-scoop/usr/lib/python2.7/dist-packages/scoop/launch > copying > /<>/.pybuild/cpython2_2.7_scoop/build/scoop/launch/workerLaunch.py > -> > /<>/debian/python-scoop/usr/lib/python2.7/dist-packages/scoop/launch > copying /<>/.pybuild/cpython2_2.7_scoop/build/scoop/_control.pyc > -> /<>/debian/python-scoop/usr/lib/python2.7/dist-packages/scoop > copying /<>/.pybuild/cpython2_2.7_scoop/build/scoop/__init__.py > -> /<>/debian/python-scoop/usr/lib/python2.7/dist-packages/scoop > copying /<>/.pybuild/cpython2_2.7_scoop/build/scoop/__main__.py > -> /<>/debian/python-scoop/usr/lib/python2.7/dist-packages/scoop > copying /<>/.pybuild/cpython2_2.7_scoop/build/scoop/launcher.py > -> /<>/debian/python-scoop/usr/lib/python2.7/dist-packages/scoop > copying /<>/.pybuild/cpython2_2.7_scoop/build/scoop/utils.py -> > /<>/debian/python-scoop/usr/lib/python2.7/dist-packages/scoop > copying /<>/.pybuild/cpython2_2.7_scoop/build/scoop/fallbacks.py > -> /<>/debian/python-scoop/usr/lib/python2.7/dist-packages/scoop > copying /<>/.pybuild/cpython2_2.7_scoop/build/scoop/utils.pyc -> > /<>/debian/python-scoop/usr/lib/python2.7/dist-packages/scoop > copying /<>/.pybuild/cpython2_2.7_scoop/build/scoop/futures.pyc > -> /<>/debian/python-scoop/usr/lib/python2.7/dist-packages/scoop > copying /<>/.pybuild/cpython2_2.7_scoop/build/scoop/_types.pyc > -> /<>/debian/python-scoop/usr/lib/python2.7/dist-packages/scoop > copying /<>/.pybuild/cpython2_2.7_scoop/build/scoop/_control.py > -> /<>/debian/python-scoop/usr/lib/python2.7/dist-packages/scoop > copying /<>/.pybuild/cpython2_2.7_scoop/build/scoop/futures.py > -> /<>/debian/python-scoop/usr/lib/python2.7/dist-packages/scoop > copying /<>/.pybuild/cpython2_2.7_scoop/build/scoop/shared.py -> > /<>/debian/python-scoop/usr/lib/python2.7/dist-packages/scoop > copying /<>/.pybuild/cpython2_2.7_scoop/build/scoop/_types.py -> > /<>/debian/python-scoop/usr/lib/python2.7/dist-packages/scoop > creating > /<>/debian/python-scoop/usr/lib/python2.7/dist-packages/scoop/discovery > copying > /<>/.pybuild/cpython2_2.7_scoop/build/scoop/discovery/__init__.pyc > -> >
Bug#924841: lib3mf: FTBFS: dh_makeshlibs: failing due to earlier errors
Source: lib3mf Version: 1.8.1+ds-2 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20190315 qa-ftbfs Justification: FTBFS in buster on amd64 Hi, During a rebuild of all packages in buster (in a buster chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory > '/<>/lib3mf-1.8.1+ds/obj-x86_64-linux-gnu' > make[2]: Nothing to be done for 'preinstall'. > make[2]: Leaving directory > '/<>/lib3mf-1.8.1+ds/obj-x86_64-linux-gnu' > Install the project... > /usr/bin/cmake -P cmake_install.cmake > -- Install configuration: "None" > -- Installing: > /<>/lib3mf-1.8.1+ds/debian/tmp/usr/lib/x86_64-linux-gnu/lib3MF.so.1.8.1.0 > -- Installing: > /<>/lib3mf-1.8.1+ds/debian/tmp/usr/lib/x86_64-linux-gnu/lib3MF.so.1 > -- Installing: > /<>/lib3mf-1.8.1+ds/debian/tmp/usr/lib/x86_64-linux-gnu/lib3MF.so > -- Installing: > /<>/lib3mf-1.8.1+ds/debian/tmp/usr/include/lib3mf/Model > -- Installing: > /<>/lib3mf-1.8.1+ds/debian/tmp/usr/include/lib3mf/Model/Reader > -- Installing: > /<>/lib3mf-1.8.1+ds/debian/tmp/usr/include/lib3mf/Model/Reader/NMR_ModelReader_3MF_Native.h > -- Installing: > /<>/lib3mf-1.8.1+ds/debian/tmp/usr/include/lib3mf/Model/Reader/Slice1507 > -- Installing: > /<>/lib3mf-1.8.1+ds/debian/tmp/usr/include/lib3mf/Model/Reader/Slice1507/NMR_ModelReader_Slice1507_Polygon.h > -- Installing: > /<>/lib3mf-1.8.1+ds/debian/tmp/usr/include/lib3mf/Model/Reader/Slice1507/NMR_ModelReader_Slice1507_Vertices.h > -- Installing: > /<>/lib3mf-1.8.1+ds/debian/tmp/usr/include/lib3mf/Model/Reader/Slice1507/NMR_ModelReader_Slice1507_SliceRefModel.h > -- Installing: > /<>/lib3mf-1.8.1+ds/debian/tmp/usr/include/lib3mf/Model/Reader/Slice1507/NMR_ModelReader_Slice1507_SliceRef.h > -- Installing: > /<>/lib3mf-1.8.1+ds/debian/tmp/usr/include/lib3mf/Model/Reader/Slice1507/NMR_ModelReader_Slice1507_SliceRefResources.h > -- Installing: > /<>/lib3mf-1.8.1+ds/debian/tmp/usr/include/lib3mf/Model/Reader/Slice1507/NMR_ModelReader_Slice1507_Segment.h > -- Installing: > /<>/lib3mf-1.8.1+ds/debian/tmp/usr/include/lib3mf/Model/Reader/Slice1507/NMR_ModelReader_Slice1507_SliceStack.h > -- Installing: > /<>/lib3mf-1.8.1+ds/debian/tmp/usr/include/lib3mf/Model/Reader/Slice1507/NMR_ModelReader_Slice1507_Slice.h > -- Installing: > /<>/lib3mf-1.8.1+ds/debian/tmp/usr/include/lib3mf/Model/Reader/Slice1507/NMR_ModelReader_Slice1507_Vertex.h > -- Installing: > /<>/lib3mf-1.8.1+ds/debian/tmp/usr/include/lib3mf/Model/Reader/NMR_ModelReader_3MF.h > -- Installing: > /<>/lib3mf-1.8.1+ds/debian/tmp/usr/include/lib3mf/Model/Reader/BeamLattice1702 > -- Installing: > /<>/lib3mf-1.8.1+ds/debian/tmp/usr/include/lib3mf/Model/Reader/BeamLattice1702/NMR_ModelReaderNode_BeamLattice1702_BeamLattice.h > -- Installing: > /<>/lib3mf-1.8.1+ds/debian/tmp/usr/include/lib3mf/Model/Reader/BeamLattice1702/NMR_ModelReaderNode_BeamLattice1702_BeamSets.h > -- Installing: > /<>/lib3mf-1.8.1+ds/debian/tmp/usr/include/lib3mf/Model/Reader/BeamLattice1702/NMR_ModelReaderNode_BeamLattice1702_BeamSet.h > -- Installing: > /<>/lib3mf-1.8.1+ds/debian/tmp/usr/include/lib3mf/Model/Reader/BeamLattice1702/NMR_ModelReaderNode_BeamLattice1702_Beams.h > -- Installing: > /<>/lib3mf-1.8.1+ds/debian/tmp/usr/include/lib3mf/Model/Reader/BeamLattice1702/NMR_ModelReaderNode_BeamLattice1702_Ref.h > -- Installing: > /<>/lib3mf-1.8.1+ds/debian/tmp/usr/include/lib3mf/Model/Reader/BeamLattice1702/NMR_ModelReaderNode_BeamLattice1702_Beam.h > -- Installing: > /<>/lib3mf-1.8.1+ds/debian/tmp/usr/include/lib3mf/Model/Reader/NMR_ModelReaderNode.h > -- Installing: > /<>/lib3mf-1.8.1+ds/debian/tmp/usr/include/lib3mf/Model/Reader/NMR_ModelReader_InstructionElement.h > -- Installing: > /<>/lib3mf-1.8.1+ds/debian/tmp/usr/include/lib3mf/Model/Reader/NMR_ModelReader_STL.h > -- Installing: > /<>/lib3mf-1.8.1+ds/debian/tmp/usr/include/lib3mf/Model/Reader/NMR_ModelReader_ColorMapping.h > -- Installing: > /<>/lib3mf-1.8.1+ds/debian/tmp/usr/include/lib3mf/Model/Reader/NMR_ModelReaderWarnings.h > -- Installing: > /<>/lib3mf-1.8.1+ds/debian/tmp/usr/include/lib3mf/Model/Reader/NMR_ModelReader.h > -- Installing: > /<>/lib3mf-1.8.1+ds/debian/tmp/usr/include/lib3mf/Model/Reader/v100 > -- Installing: > /<>/lib3mf-1.8.1+ds/debian/tmp/usr/include/lib3mf/Model/Reader/v100/NMR_ModelReaderNode100_MetaData.h > -- Installing: > /<>/lib3mf-1.8.1+ds/debian/tmp/usr/include/lib3mf/Model/Reader/v100/NMR_ModelReaderNode100_Component.h > -- Installing: > /<>/lib3mf-1.8.1+ds/debian/tmp/usr/include/lib3mf/Model/Reader/v100/NMR_ModelReaderNode100_BaseMaterials.h > -- Installing: > /<>/lib3mf-1.8.1+ds/debian/tmp/usr/include/lib3mf/Model/Reader/v100/NMR_ModelReaderNode100_BaseMaterial.h > -- Installing: > /<>/lib3mf-1.8.1+ds/debian/tmp/usr/include/lib3mf/Model/Reader/v100/NMR_ModelReaderNode100_Triangle.h > -- Installing: > /<>/lib3mf-1.8.1+ds/debian/tmp/usr/include/lib3mf/Model/Reader/v100/NMR_ModelReaderNode100_Build.h >
Bug#924837: adios: FTBFS: mpicxx.h:22:4: error: #error 'Please use the same version of GCC and g++ for compiling MPICH and user MPI programs'
Source: adios Version: 1.13.1-16 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20190315 qa-ftbfs Justification: FTBFS in buster on amd64 Hi, During a rebuild of all packages in buster (in a buster chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): > x86_64-linux-gnu-g++ -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions > -Wl,-z,relro -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall > -Wstrict-prototypes -Wdate-time -D_FORTIFY_SOURCE=2 -g > -fdebug-prefix-map=/build/python2.7-UboFgi/python2.7-2.7.16~rc1=. > -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 > build/temp.linux-x86_64-2.7/adios.o -L../../debian/tmp/usr/lib > -L/usr/lib/x86_64-linux-gnu -L/usr/lib/x86_64-linux-gnu/hdf5/serial -L/sr/lib > -ladios_nompi -libverbs -lnetcdf -lhdf5_hl -lhdf5 -lz -lglib-2.0 -lz -lbz2 > -lsz -llz4 -lblosc -lm -lpthread -lrt -o > build/lib.linux-x86_64-2.7/adios/adios.so > python setup_mpi.py build > running build > running build_src > running build_py > creating build/lib.linux-x86_64-2.7/adios_mpi > copying src_mpi/__init__.py -> build/lib.linux-x86_64-2.7/adios_mpi > creating build/lib.linux-x86_64-2.7/adios_mpi/_hl > copying _hl/selections.py -> build/lib.linux-x86_64-2.7/adios_mpi/_hl > copying _hl/__init__.py -> build/lib.linux-x86_64-2.7/adios_mpi/_hl > running build_ext > MPI configuration: [mpi] from 'mpi.cfg' > MPI C compiler:/usr/bin/mpicc > MPI C++ compiler: /usr/bin/mpicxx > MPI F77 compiler: /usr/bin/mpif77 > MPI F90 compiler: /usr/bin/mpif90 > building 'adios_mpi.adios_mpi' extension > /usr/bin/mpicc -fPIC -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall > -Wstrict-prototypes -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -I/usr/lib/python2.7/dist-packages/numpy/core/include > -I../../src/public -I/usr/include > -I/usr/lib/x86_64-linux-gnu/netcdf/mpi/include -I/usr/include/hdf5/openmpi > -I/usr/include -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include > -I/usr/include -I/usr/include -I/usr/include -I/sr/include -I/usr/include > -I/sr/include -I/usr/include -I/usr/include/python2.7 -c adios_mpi.cpp -o > build/temp.linux-x86_64-2.7/adios_mpi.o -Wno-unused-function > -Wno-uninitialized > cc1plus: warning: command line option '-Wstrict-prototypes' is valid for > C/ObjC but not for C++ > In file included from > /usr/lib/python2.7/dist-packages/numpy/core/include/numpy/ndarraytypes.h:1822, > from > /usr/lib/python2.7/dist-packages/numpy/core/include/numpy/ndarrayobject.h:12, > from > /usr/lib/python2.7/dist-packages/numpy/core/include/numpy/arrayobject.h:4, > from adios_mpi.cpp:629: > /usr/lib/python2.7/dist-packages/numpy/core/include/numpy/npy_1_7_deprecated_api.h:17:2: > warning: #warning "Using deprecated NumPy API, disable it with " "#define > NPY_NO_DEPRECATED_API NPY_1_7_API_VERSION" [-Wcpp] > #warning "Using deprecated NumPy API, disable it with " \ > ^~~ > /usr/bin/mpicxx -shared -Wl,-O1 -Wl,-Bsymbolic-functions -Wl,-z,relro > -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes > -Wdate-time -D_FORTIFY_SOURCE=2 -g > -fdebug-prefix-map=/build/python2.7-UboFgi/python2.7-2.7.16~rc1=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wl,-z,relro build/temp.linux-x86_64-2.7/adios_mpi.o > -L../../debian/tmp/usr/lib -L/usr/lib/x86_64-linux-gnu > -L/usr/lib/x86_64-linux-gnu/netcdf/mpi > -L/usr/lib/x86_64-linux-gnu/hdf5/openmpi -L/sr/lib -ladios -lnetcdf -lhdf5_hl > -lhdf5 -lz -libverbs -lglib-2.0 -lz -lbz2 -lsz -llz4 -lblosc -lm -lpthread -o > build/lib.linux-x86_64-2.7/adios_mpi/adios_mpi.so > make[2]: Leaving directory '/<>/wrappers/numpy' > # MPICH > install -D -t debian/tmp/usr/lib build-mpich/src/*.a > for p in python2.7 python3.7 ; do \ > ( cd build-mpich/numpy && \ > $p ./setup_mpi.py build_ext --mpicc=mpicc.mpich --mpicxx=mpicxx.mpich ) > ; \ > done > running build_ext > MPI configuration: [mpi] from 'mpi.cfg' > MPI C compiler:/usr/bin/mpicc.mpich > MPI C++ compiler: /usr/bin/mpicxx.mpich > building 'adios_mpi.adios_mpi' extension > creating build > creating build/temp.linux-x86_64-2.7 > /usr/bin/mpicc.mpich -fPIC -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall > -Wstrict-prototypes -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -I/usr/lib/python2.7/dist-packages/numpy/core/include > -I../../src/public -I/usr/include > -I/usr/lib/
