Bug#919419: marked as done (yatex: hangs while installing along xemacs21)
Your message dated Sun, 24 Feb 2019 07:35:13 + with message-id and subject line Bug#919419: fixed in yatex 1.81-2 has caused the Debian Bug report #919419, regarding yatex: hangs while installing along xemacs21 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.) -- 919419: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919419 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: yatex Version: 1.81-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. If yatex is installed in a piuparts chroot that has already xemacs21 installed, the installation will hand infinitely (until it is killed by a timeout). All processes are idle, there does not seem to be a busy loop involved: root 9236 32750 0 18:28 pts/000:00:00 /usr/bin/dpkg --force-unsafe-io --status-fd 19 --configure --pending root 11033 9236 0 18:28 pts/000:00:00 /bin/sh /var/lib/dpkg/info/yatex.postinst configure root 11035 11033 0 18:28 pts/000:00:00 /usr/bin/perl -w /usr/lib/emacsen-common/emacs-package-install --postinst yatex root 11057 11035 0 18:28 pts/000:00:00 [emacs-package-i] root 11148 11035 0 18:28 pts/000:00:00 /bin/bash -e /usr/lib/emacsen-common/packages/install/yatex xemacs21 root 11151 11148 0 18:28 pts/000:00:00 /bin/bash -e /usr/lib/emacsen-common/packages/install/yatex xemacs21 root 11152 11151 0 18:28 pts/000:00:00 xemacs21 -batch -no-site-file -no-init-file -l ./lp.el -e bcf-and-exit comment.el yatex.el yatexadd.el yatexgen.el yatexenv.el yatexlib.el yatexprc.el yatexmth.el yatexhks.el yatexhlp.el yatexm-o.el yatexsec.el yatexhie.el yahtml.el yatexpkg.el root 11153 11151 0 18:28 pts/000:00:00 gzip -9qf It has been in this state for 30 minutes now ... cheers, Andreas --- End Message --- --- Begin Message --- Source: yatex Source-Version: 1.81-2 We believe that the bug you reported is fixed in the latest version of yatex, 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 919...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. KURASHIKI Satoru (supplier of updated yatex 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: Thu, 14 Feb 2019 00:58:18 +0900 Source: yatex Binary: yatex Architecture: source all Version: 1.81-2 Distribution: unstable Urgency: medium Maintainer: KURASHIKI Satoru Changed-By: KURASHIKI Satoru Description: yatex - Yet Another TeX mode for Emacs Closes: 919419 Changes: yatex (1.81-2) unstable; urgency=medium . * Skip old/unsupported emacs flavors for un/installation. (Closes: #919419) (patch from Tatsuya Kinoshita.) Checksums-Sha1: 335d9d14b9f803908c2a16da4b413960a1fe4fd7 1878 yatex_1.81-2.dsc 4a0511e87d50f8243f700f104eb28136ffa51178 23588 yatex_1.81-2.debian.tar.xz bce0a171b86bce4f382b36082cf76288b253c1c9 306036 yatex_1.81-2_all.deb 5fcaf012ffb9d20024a8f8e4e364d4466097f542 7603 yatex_1.81-2_amd64.buildinfo Checksums-Sha256: 54fd82f107c13a0c54e49f0d1cbe08ea65bdc20b333ca486a7401af39f9dc33a 1878 yatex_1.81-2.dsc b479d1fdf2666d23c8ba03fdea0875231f901071837c2a07b9d077f0877b3c70 23588 yatex_1.81-2.debian.tar.xz 57a82c02d30fbebba0dcd85e675b9d557c90a48fe8ec7e60af78770fe6689669 306036 yatex_1.81-2_all.deb 96468061bd163eaaf904c2864eeb6d15065af45ccd226778221aaf1796adff58 7603 yatex_1.81-2_amd64.buildinfo Files: fadb0112bd2eb8ed816087c65150b158 1878 tex optional yatex_1.81-2.dsc e10b64e4b47d82f63fc8ce3b90eca28f 23588 tex optional yatex_1.81-2.debian.tar.xz e7b9540bb31e2dac6e0598681c4c5887 306036 tex optional yatex_1.81-2_all.deb 2168bf71c25ba42ad9df28a05bf08b59 7603 tex optional yatex_1.81-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEwRyljAF1wkDVjDDI0n3eEUCi8RMFAlxyNUEACgkQ0n3eEUCi 8RP/0A//b5T7JDoNf0OXlrQWuG3cXXZxlgi9fNjyDAag4hgUyLbiYk5ZuIcvAR4U Jnm9zDoitlMjJ9Zh02HMbnEoMEMIh1/nX3VSN/he6vFZpksUoc76hVVg9wF2ulWl LKchorq9p93ZAgSfYPDkI7fSnpZYEYtMtm4v7fSwcXUYhYe9Kl1Y08HZlqSBi4z7 BYI
Bug#917685: marked as done (ruby-rack: FTBFS: ERROR: Test "ruby2.5" failed.)
Your message dated Sun, 24 Feb 2019 15:45:50 +0900 with message-id <8736odr8f5.wl-uwab...@gfd-dennou.org> and subject line has caused the Debian Bug report #917685, regarding ruby-rack: FTBFS: ERROR: Test "ruby2.5" failed. 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.) -- 917685: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917685 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-rack Version: 1.6.4-6 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20181229 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/ruby2.5 /usr/bin/gem2deb-test-runner > > ┌──┐ > │ Checking Rubygems dependency resolution on ruby2.5 > │ > └──┘ > > GEM_PATH=debian/ruby-rack/usr/share/rubygems-integration/all:/var/lib/gems/2.5.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all > ruby2.5 -e gem\ \"rack\" > > ┌──┐ > │ Run tests for ruby2.5 from debian/ruby-tests.rake > │ > └──┘ > > RUBYLIB=/<>/debian/ruby-rack/usr/lib/ruby/vendor_ruby:. > GEM_PATH=debian/ruby-rack/usr/share/rubygems-integration/all:/var/lib/gems/2.5.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all > ruby2.5 -S rake -f debian/ruby-tests.rake > /usr/bin/ruby2.5 /usr/bin/bacon -I./test -w -a > /usr/lib/ruby/vendor_ruby/bacon.rb:221: warning: shadowing outer local > variable - args > /<>/test/spec_response.rb:138: warning: assigned but unused > variable - body > /<>/test/spec_response.rb:151: warning: assigned but unused > variable - status > /<>/test/spec_response.rb:151: warning: assigned but unused > variable - header > /<>/test/spec_deflater.rb:331: warning: shadowing outer local > variable - body > Rack::Response > - should have sensible default values > - can be written to [ERROR: NameError] > - can set and read headers > - can override the initial Content-Type with a different case [ERROR: > NameError] > - can set cookies > - can set cookies with the same name for multiple domains > - formats the Cookie expiration date accordingly to RFC 6265 > - can set secure cookies > - can set http only cookies > - can set http only cookies with :http_only > - can set prefers :httponly for http only cookie setting when :httponly and > :http_only provided > - can delete cookies > - can delete cookies with the same name from multiple domains > - can delete cookies with the same name with different paths > - can do redirects > - has a useful constructor [ERROR: NameError] > - has a constructor that can take a block [ERROR: NameError] > - doesn't return invalid responses [ERROR: NameError] > - knows if it's empty [ERROR: NameError] > - should provide access to the HTTP status > - should provide access to the HTTP headers [ERROR: NameError] > - does not add or change Content-Length when #finish()ing > - updates Content-Length when body appended to using #write [ERROR: > NameError] > - calls close on #body > - calls close on #body when 204, 205, or 304 [ERROR: NameError] > - wraps the body from #to_ary to prevent infinite loops > > Rack::Deflater > - should be able to deflate bodies that respond to each > - should flush deflated chunks to the client as they become ready > - should be able to deflate String bodies > - should be able to gzip bodies that respond to each > - should flush gzipped chunks to the client as they become ready > - should be able to fallback to no deflation > - should be able to skip when there is no response entity body > - should handle the lack of an acceptable encoding > - should handle gzip response with Last-Modified header > - should do nothing when no-transform Cache-Control directive present > - should do nothing when Content-Encoding already present > - should deflate when Content-Encoding is identity > - should deflate if content-type matches :include > - should deflate if content-type is included it :include > - should not deflate if content-type is not set but given in :include > - should not
Processed: severity of 903121 is important
Processing commands for cont...@bugs.debian.org: > severity 903121 important Bug #903121 [xserver-xorg-video-nvidia] xserver-xorg-video-nvidia: blank screen, CPU fan goes to max and the systems freezes Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 903121: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903121 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#921030: Fails to import the ansible module since its migration to Python 3
I'm working on this: https://salsa.debian.org/debian/ansible-lint I think i'm close to an upload now, there's only some problems with .js sources. Anyone please feel free to help. -- Samuel Henrique
Processed: Re: Bug#923001: error message on start
Processing control commands: > severity -1 serious Bug #923001 [chromium-ublock-origin] chromium: failed to load extension message on start Severity set to 'serious' from 'minor' -- 923001: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923001 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#921637: marked as done (ronn 0.8.0-1 breaks man pages with numbered lists)
Your message dated Sun, 24 Feb 2019 00:34:14 + with message-id and subject line Bug#921637: fixed in ruby-ronn 0.8.0-2 has caused the Debian Bug report #921637, regarding ronn 0.8.0-1 breaks man pages with numbered lists 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.) -- 921637: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921637 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: git-lfs Version: 2.6.1-3 Severity: serious -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 When rebuild git-lfs, it FTBFS: warn: unrecognized inline tag: ["p"] html: man/git-lfs-untrack.1.html+man roff: man/git-lfs-update.1 html: man/git-lfs-update.1.html +man roff: man/git-lfs.1 /usr/lib/ruby/vendor_ruby/ronn/roff.rb:165:in `block_filter': undefined method `position' for # (NoMethodError) from /usr/lib/ruby/vendor_ruby/ronn/roff.rb:88:in `block in block_filter' from /usr/lib/ruby/vendor_ruby/nokogiri/xml/node_set.rb:204:in `block in each' from /usr/lib/ruby/vendor_ruby/nokogiri/xml/node_set.rb:203:in `upto' from /usr/lib/ruby/vendor_ruby/nokogiri/xml/node_set.rb:203:in `each' from /usr/lib/ruby/vendor_ruby/ronn/roff.rb:88:in `block_filter' from /usr/lib/ruby/vendor_ruby/ronn/roff.rb:160:in `block_filter' from /usr/lib/ruby/vendor_ruby/ronn/roff.rb:88:in `block in block_filter' from /usr/lib/ruby/vendor_ruby/nokogiri/xml/node_set.rb:204:in `block in each' from /usr/lib/ruby/vendor_ruby/nokogiri/xml/node_set.rb:203:in `upto' from /usr/lib/ruby/vendor_ruby/nokogiri/xml/node_set.rb:203:in `each' from /usr/lib/ruby/vendor_ruby/ronn/roff.rb:88:in `block_filter' from /usr/lib/ruby/vendor_ruby/ronn/roff.rb:91:in `block_filter' from /usr/lib/ruby/vendor_ruby/ronn/roff.rb:18:in `initialize' from /usr/lib/ruby/vendor_ruby/ronn/document.rb:245:in `new' from /usr/lib/ruby/vendor_ruby/ronn/document.rb:245:in `to_roff' from /usr/lib/ruby/vendor_ruby/ronn/document.rb:240:in `convert' from /usr/bin/ronn:209:in `block (2 levels) in ' from /usr/bin/ronn:199:in `each' from /usr/bin/ronn:199:in `block in ' from /usr/bin/ronn:184:in `each' from /usr/bin/ronn:184:in `' make[1]: *** [debian/rules:28: override_dh_auto_build] Error 1 I see ruby-ronn 0.8.0-1 was accepted on 2019-02-07, this may be the reason. Please reassign to ruby-ronn if you think it's the bug in ruby-ronn instead. - -- Shengjing Zhu -BEGIN PGP SIGNATURE- iQFEBAEBCgAuFiEE85F2DZP0aJKsSKyHONAPABi+PjUFAlxcR7IQHHpoc2pAZGVi aWFuLm9yZwAKCRA40A8AGL4+NTqRB/0TMPE3oaR0kUXa78k6HUizl9f5+Npxawn9 OU1fFYEbY4yh4wZcXigqitBavnF3KvYpOWb4KbrKb04FYK3KOSWW/eXVKnQraSQc YL57l2p2zEQVydKBt/9ADBskd13fxNLOVki/asiRN0MoHuiHw6vzZaWbCKyPlght LE3CxXMuKLhAuUG+0BSliKRxNDHidcALEqKvmzmajgNccMeDvDSqO8ePy33YDvW2 3x8QDpm8emgy5+V1DCRRQbchKhbsrYQp+ali6/UPV4aEV8Um7QBCVTytr0819kDr U2v+t8MCnBQiZ9a+znhvBfjRFi4cW6S0Gx+6hXKI6HvftepwV9zt =RKLP -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Source: ruby-ronn Source-Version: 0.8.0-2 We believe that the bug you reported is fixed in the latest version of ruby-ronn, 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 921...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stephen Gelman (supplier of updated ruby-ronn 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: Sat, 23 Feb 2019 17:43:39 -0600 Source: ruby-ronn Architecture: source Version: 0.8.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers Changed-By: Stephen Gelman Closes: 921637 Changes: ruby-ronn (0.8.0-2) unstable; urgency=medium . * Team upload. * Fix issue with ordered lists (Closes: #921637) * Fix url hyphenation issue Checksums-Sha1: 5db220d0f685aa1d894a610f8627102376342210 2179 ruby-ronn_0.8.0-2.dsc 1a76efdb362f99aae7b77586b226251a94643afc 7512 ruby-ronn_0.8.0-2.debian.tar.xz 0e1af7274c3f8955b038bf18c1cf460cbd7790f4 9005 ruby-ronn_0.8.0-2_amd
Bug#922420: got an unexpected keyword argument 'bg'
Control: tags -1 + moreinfo On 17-Feb-2019, Ben Finney wrote: > So maybe, though upstream has not described any change to this effect, > the bug has been fixed? Can you try again with version “1.4-1”, now in > Debian? This would need to be tested before deciding whether this bug is fixed in the new version. -- \ “Don't you try to outweird me, I get stranger things than you | `\ free with my breakfast cereal.” —Zaphod Beeblebrox, _The | _o__)Restaurant At The End Of The Universe_, Douglas Adams | Ben Finney signature.asc Description: PGP signature
Processed: Re: Bug#922420: got an unexpected keyword argument 'bg'
Processing control commands: > tags -1 + moreinfo Bug #922420 [gandi-cli] got an unexpected keyword argument 'bg' Added tag(s) moreinfo. -- 922420: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922420 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#911533: gandi-cli: missing dependencies
Processing control commands:
> clone -1 -2
Bug #911533 [gandi-cli] gandi-cli: missing dependencies for python3 setuptools
and ipy
Bug 911533 cloned as bug 923084
> retitle -1 gandi-cli: Python dependencies not declared
Bug #911533 [gandi-cli] gandi-cli: missing dependencies for python3 setuptools
and ipy
Changed Bug title to 'gandi-cli: Python dependencies not declared' from
'gandi-cli: missing dependencies for python3 setuptools and ipy'.
> summary -1 ‘dh_python3’ is failing to expand ${python3:Depends} for the
> binary package.
Summary recorded from message bug 911533 message
> outlook -1 0
Outlook recorded from message bug 911533 message 24
> fixed -1 gandi-cli/1.4-1
Bug #911533 [gandi-cli] gandi-cli: Python dependencies not declared
Marked as fixed in versions gandi-cli/1.4-1.
> close -1
Bug #911533 [gandi-cli] gandi-cli: Python dependencies not declared
Marked Bug as done
> retitle -2 gandi-cli: Show ‘dh_python3’ where to find install requirements
Bug #923084 [gandi-cli] gandi-cli: missing dependencies for python3 setuptools
and ipy
Changed Bug title to 'gandi-cli: Show ‘dh_python3’ where to find install
requirements' from 'gandi-cli: missing dependencies for python3 setuptools and
ipy'.
--
911533: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911533
923084: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923084
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Bug#911533: gandi-cli: missing dependencies
Processing control commands:
> clone -1 -2
Bug #911533 {Done: Ben Finney } [gandi-cli] gandi-cli:
Python dependencies not declared
Bug 911533 cloned as bug 923085
> retitle -1 gandi-cli: Python dependencies not declared
Bug #911533 {Done: Ben Finney } [gandi-cli] gandi-cli:
Python dependencies not declared
Ignoring request to change the title of bug#911533 to the same title
> summary -1 ‘dh_python3’ is failing to expand ${python3:Depends} for the
> binary package.
Ignoring request to change the summary of bug 911533 to the same value
> outlook -1 0
Ignoring request to change the outlook of bug 911533 to the same value
> fixed -1 gandi-cli/1.4-1
Bug #911533 {Done: Ben Finney } [gandi-cli] gandi-cli:
Python dependencies not declared
Marked as fixed in versions gandi-cli/1.4-1; no longer marked as fixed in
versions gandi-cli/1.4-1.
> close -1
Bug #911533 {Done: Ben Finney } [gandi-cli] gandi-cli:
Python dependencies not declared
Bug 911533 is already marked as done; not doing anything.
> retitle -2 gandi-cli: Show ‘dh_python3’ where to find install requirements
Bug #923085 {Done: Ben Finney } [gandi-cli] gandi-cli:
Python dependencies not declared
Changed Bug title to 'gandi-cli: Show ‘dh_python3’ where to find install
requirements' from 'gandi-cli: Python dependencies not declared'.
--
911533: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911533
923085: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923085
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#911533: gandi-cli: missing dependencies
Control: clone -1 -2
Control: retitle -1 gandi-cli: Python dependencies not declared
Control: summary -1 ‘dh_python3’ is failing to expand ${python3:Depends} for
the binary package.
Control: outlook -1 0
Control: fixed -1 gandi-cli/1.4-1
Control: close -1
Control: retitle -2 gandi-cli: Show ‘dh_python3’ where to find install
requirements
The workaround is to explicitly declare the package dependencies,
because ‘dh_python3’ fails to do so.
A better solution is to have ‘dh_python3’ correctly find the package
install requirements list, as built by Setuptools.
On 13-Nov-2018, Michele Orrù wrote:
> one can see that at least the packages python3-ipy, python3-click,
> and python3-yaml are missing.
With release “1.4-1” the declared dependencies are:
Depends: python3-setuptools, python3-yaml, python3-click, python3-requests,
python3-ipy, python3
https://tracker.debian.org/media/packages/g/gandi-cli/control-1.4-1>
This addresses the problem reported originally in this bug report.
--
\ “I don't like country music, but I don't mean to denigrate |
`\ those who do. And for the people who like country music, |
_o__)denigrate means ‘put down’.” —Bob Newhart |
Ben Finney
signature.asc
Description: PGP signature
Bug#897882: marked as done (validns: ftbfs with GCC-8)
Your message dated Sat, 23 Feb 2019 23:49:18 + with message-id and subject line Bug#897882: fixed in validns 0.8+git20160720-3.1 has caused the Debian Bug report #897882, regarding validns: ftbfs with GCC-8 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.) -- 897882: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897882 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:validns Version: 0.8+git20160720-3 Severity: normal Tags: sid buster User: debian-...@lists.debian.org Usertags: ftbfs-gcc-8 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-8/g++-8, but succeeds to build with gcc-7/g++-7. The severity of this report will be raised before the buster release. The full build log can be found at: http://aws-logs.debian.net/2018/05/01/gcc8/validns_0.8+git20160720-3_unstable_gcc8.log.gz The last lines of the build log are at the end of this report. To build with GCC 8, either set CC=gcc-8 CXX=g++-8 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-8/porting_to.html [...] cc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>/validns-0.8+git20160720=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -Werror -pthread -fno-strict-aliasing -O2 -g -c -o soa.o soa.c -I/usr/local/include -I/opt/local/include -I/usr/local/ssl/include cc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>/validns-0.8+git20160720=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -Werror -pthread -fno-strict-aliasing -O2 -g -c -o a.o a.c -I/usr/local/include -I/opt/local/include -I/usr/local/ssl/include cc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>/validns-0.8+git20160720=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -Werror -pthread -fno-strict-aliasing -O2 -g -c -o cname.o cname.c -I/usr/local/include -I/opt/local/include -I/usr/local/ssl/include cc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>/validns-0.8+git20160720=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -Werror -pthread -fno-strict-aliasing -O2 -g -c -o mx.o mx.c -I/usr/local/include -I/opt/local/include -I/usr/local/ssl/include cc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>/validns-0.8+git20160720=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -Werror -pthread -fno-strict-aliasing -O2 -g -c -o ns.o ns.c -I/usr/local/include -I/opt/local/include -I/usr/local/ssl/include cc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>/validns-0.8+git20160720=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -Werror -pthread -fno-strict-aliasing -O2 -g -c -o rrsig.o rrsig.c -I/usr/local/include -I/opt/local/include -I/usr/local/ssl/include cc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>/validns-0.8+git20160720=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -Werror -pthread -fno-strict-aliasing -O2 -g -c -o nsec.o nsec.c -I/usr/local/include -I/opt/local/include -I/usr/local/ssl/include cc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>/validns-0.8+git20160720=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -Werror -pthread -fno-strict-aliasing -O2 -g -c -o dnskey.o dnskey.c -I/usr/local/include -I/opt/local/include -I/usr/local/ssl/include cc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>/validns-0.8+git20160720=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -Werror -pthread -fno-strict-aliasing -O2 -g -c -o txt.o txt.c -I/usr/local/include -I/opt/local/include -I/usr/local/ssl/include cc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>/validns-0.8+git20160720=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -Werror -pthread -fno-strict-aliasing -O2 -g -c -o .o .c -I/usr/local/include -I/opt/local/include -I/usr/local/ssl/include cc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-
Bug#859784: marked as done (validns: Please migrate to openssl1.1 in Buster)
Your message dated Sat, 23 Feb 2019 23:49:18 + with message-id and subject line Bug#859784: fixed in validns 0.8+git20160720-3.1 has caused the Debian Bug report #859784, regarding validns: Please migrate to openssl1.1 in Buster 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.) -- 859784: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859784 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: validns Version: 0.8+git20160720-2 Severity: important Tags: sid buster User: pkg-openssl-de...@lists.alioth.debian.org Usertags: openssl-1.1-trans Please migrate to libssl-dev in the Buster cycle. The bug report about the FTBFS is #828591. The log of the FTBFS can be found at https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/validns_0.8-2_amd64-20160529-1548 Sebastian --- End Message --- --- Begin Message --- Source: validns Source-Version: 0.8+git20160720-3.1 We believe that the bug you reported is fixed in the latest version of validns, 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 859...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastian Andrzej Siewior (supplier of updated validns 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: Fri, 22 Feb 2019 23:52:58 +0100 Source: validns Architecture: source Version: 0.8+git20160720-3.1 Distribution: unstable Urgency: medium Maintainer: Casper Gielen Changed-By: Sebastian Andrzej Siewior Closes: 859784 897882 Changes: validns (0.8+git20160720-3.1) unstable; urgency=medium . * Non-maintainer upload. * Avoid a warning regarding string truncation (Closes: #897882). * Get it compiled against OpenSSL 1.1+ (Closes: #859784). * Use priority optional instead of extra. Checksums-Sha1: 404710449d79f23633923a853a10f168bfcffa0b 1898 validns_0.8+git20160720-3.1.dsc 6e254095e72b780d511e4d176f5cdce329d4db04 8184 validns_0.8+git20160720-3.1.debian.tar.xz 75038ac4f702d7da71b7f5c2145ce0d2cbc6f0f2 5030 validns_0.8+git20160720-3.1_source.buildinfo Checksums-Sha256: 64966d8603ad12ecfaff6c497e767b7f56e3e107117b356d61c384129cbdbde0 1898 validns_0.8+git20160720-3.1.dsc 372fe2e2d1f8b3f377ee9c75f1a2392bbb5d272ab51e127f46796f2875816f84 8184 validns_0.8+git20160720-3.1.debian.tar.xz 8b094e51c6cb6dc090f36b3b941fce3cda5d1c715289ed260bb371d189fde505 5030 validns_0.8+git20160720-3.1_source.buildinfo Files: 0867d97b3ac3a428e1fb0848f55b88a6 1898 net optional validns_0.8+git20160720-3.1.dsc 77e79e3b47a7886bdf437c05adc19baf 8184 net optional validns_0.8+git20160720-3.1.debian.tar.xz 4353de9de3802c187c633ce8f4ed80c8 5030 net optional validns_0.8+git20160720-3.1_source.buildinfo -BEGIN PGP SIGNATURE- iQHMBAEBCgA2FiEEV4kucFIzBRM39v3RBWQfF1cS+lsFAlxwhjcYHHNlYmFzdGlh bkBicmVha3BvaW50LmNjAAoJEAVkHxdXEvpbGMIL/jRQ3ch+9MqiCWOTCt4qa/60 kRAqKBPSwS/phTdqRv9gQ0a5/2jNXH8yzZgEtJ7CTNJ1A3jqUpve/3R6OFpA8y62 H/DznR5Nk5Hy+65ZhLwkGD0CfmyFbczjXxcuwd9H6EdX+JhELqymdrTyjCJqFHW5 nVkvkk5Jz1xEuqW2b86UPvK8pWt9bqVYG5dE/wFrpvig4mHttUaMJUJyOTF6C0Cs GZGxkROf3XZSqF811fiNim2EynIOdLCwU1MjI5twM8jvLhKXeqA9hzbfstH77rSy DiJZG9VRvQ9D5zdatCe80T0xQr2fl9mWhGML/dh3pqERsNMLV83HuN5AQUFA4Su7 8AtPb6Viux+mRYEnUahtbcLAi3ugl8i0aADvTuu5Sa1xRtlQSapRhimYciOpMzle m+hTMRFWE0Kp2p4fD0WRCaBmQzo2DskFj/vz1DTtgwMLRVorNo6H6u2cqr98b1tu mMi7knhtE07VATP5XneYR29QMeG/ZyQ6vQJC9QgC9w== =2Mqz -END PGP SIGNATURE End Message ---
Bug#900299: leiningen-clojure: depends on openjdk-8
On Tue, Jan 22, 2019 at 05:39:46PM -0800, Phil Hagelberg wrote: > > It looks like it's been fixed in newer versions of Clojure, but we > haven't bumped that in Leiningen yet. Note that this has been fixed upstream in the 2.9.0 release. I've been trying to upgrade Leiningen in Debian to this new release but the jar is not working properly with the current build strategy; it's slow and can't seem to find clojure.main on any JVM. I've had no luck trying to pin down where the bug is and the complexity of the build is not helping. So this weekend I am going to look into changing the build to more closely match upstream, now that we've bootstrapped a working Leiningen into the archive. This would involve building Leiningen with a previous version of itself, as upstream does. (In Debian, we currently build the leiningen-core jar using Maven and then attempt to build the entire Leiningen codebase with that.) - e signature.asc Description: PGP signature
Bug#921761: sssd: FTBFS (failing tests)
Fedora project seems to know how to fix this, but I cannot get my head wrapped around how the hell you find out how they did it… https://bugzilla.redhat.com/show_bug.cgi?id=1645912 -nik signature.asc Description: PGP signature
Bug#912183: marked as done (python-cookies FTBFS with python 3.7 as supported version)
Your message dated Sat, 23 Feb 2019 23:35:15 +
with message-id
and subject line Bug#912183: fixed in python-cookies 2.2.1-2
has caused the Debian Bug report #912183,
regarding python-cookies FTBFS with python 3.7 as supported version
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.)
--
912183: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912183
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-cookies
Version: 2.2.1-1
Severity: serious
Tags: ftbfs buster sid
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-cookies.html
...
= test session starts ==
platform linux -- Python 3.7.1, pytest-3.6.4, py-1.6.0, pluggy-0.6.0
rootdir: /build/1st/python-cookies-2.2.1, inifile:
collected 67 items
test_cookies.py [ 83%]
..F [100%]
=== FAILURES ===
__ test_encoding_assumptions ___
check_unicode = False
def test_encoding_assumptions(check_unicode=False):
"Document and test assumptions underlying URL encoding scheme"
# Use the RFC 6265 based character class to build a regexp matcher that
# will tell us whether or not a character is okay to put in cookie
values.
cookie_value_re = re.compile("[%s]" % Definitions.COOKIE_OCTET)
# Figure out which characters are okay. (unichr doesn't exist in Python
3,
# in Python 2 it shouldn't be an issue)
cookie_value_safe1 = set(chr(i) for i in range(0, 256) \
if cookie_value_re.match(chr(i)))
cookie_value_safe2 = set(unichr(i) for i in range(0, 256) \
if cookie_value_re.match(unichr(i)))
# These two are NOT the same on Python3
assert cookie_value_safe1 == cookie_value_safe2
# Now which of these are quoted by urllib.quote?
# caveat: Python 2.6 crashes if chr(127) is passed to quote and safe="",
# so explicitly set it to b"" to avoid the issue
safe_but_quoted = set(c for c in cookie_value_safe1
if quote(c, safe=b"") != c)
# Produce a set of characters to give to urllib.quote for the safe parm.
dont_quote = "".join(sorted(safe_but_quoted))
# Make sure it works (and that it works because of what we passed)
for c in dont_quote:
assert quote(c, safe="") != c
assert quote(c, safe=dont_quote) == c
# Make sure that the result of using dont_quote as the safe characters
for
# urllib.quote produces stuff which is safe as a cookie value, but not
# different unless it has to be.
for i in range(0, 255):
original = chr(i)
quoted = quote(original, safe=dont_quote)
# If it is a valid value for a cookie, that quoting should leave it
# alone.
if cookie_value_re.match(original):
assert original == quoted
# If it isn't a valid value, then the quoted value should be valid.
else:
assert cookie_value_re.match(quoted)
> assert set(dont_quote) == set("!#$%&'()*+/:<=>?@[]^`{|}~")
E assert {'!', '#', '$...'&', "'", ...} == {'!', '#', '$'...'&', "'", ...}
E Extra items in the right set:
E '~'
E Use -v to get the full diff
test_cookies.py:2228: AssertionError
= 1 failed, 66 passed in 1.07 seconds ==
E: pybuild pybuild:338: test: plugin distutils failed with: exit code=1: cd
/build/1st/python-cookies-2.2.1/.pybuild/cpython3_3.7_cookies/build; python3.7
-m pytest
dh_auto_test: pybuild --test -i python{version} -p "3.7 3.6" returned exit code
13
make: *** [debian/rules:8: build] Error 25
--- End Message ---
--- Begin Message ---
Source: python-cookies
Source-Version: 2.2.1-2
We believe that the bug you reported is fixed in the latest version of
python-cookies, 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 912...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Federico Ceratto (supplier of u
Bug#921761: sssd: FTBFS (failing tests)
The error returned in line 193 of test_copy_ccache.c is "Matching credential not found". signature.asc Description: PGP signature
Processed: tagging 921637
Processing commands for cont...@bugs.debian.org: > tags 921637 + confirmed pending Bug #921637 [ronn] ronn 0.8.0-1 breaks man pages with numbered lists Added tag(s) confirmed and pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 921637: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921637 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#922805: marked as done (strophejs: FTBFS (ERROR: module path does not exist: /usr/lib/nodejs/node-almond/almond.js))
Your message dated Sat, 23 Feb 2019 22:35:16 + with message-id and subject line Bug#922805: fixed in strophejs 1.2.14+dfsg-4 has caused the Debian Bug report #922805, regarding strophejs: FTBFS (ERROR: module path does not exist: /usr/lib/nodejs/node-almond/almond.js) 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.) -- 922805: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922805 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:strophejs Version: 1.2.14+dfsg-3 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep dh build-indep dh_update_autotools_config -i dh_auto_configure -i debian/rules override_dh_auto_build make[1]: Entering directory '/<>/strophejs-1.2.14+dfsg' node /usr/lib/nodejs/requirejs/r.js -o build.js name=/usr/lib/nodejs/node-almond/almond.js insertRequire=strophe-polyfill include=strophe-polyfill out=strophe.min.js Error: Error: ERROR: module path does not exist: /usr/lib/nodejs/node-almond/almond.js for module named: /usr/lib/nodejs/node-almond/almond.js. Path is relative to: /<>/strophejs-1.2.14+dfsg at /usr/lib/nodejs/requirejs/r.js:28446:35 make[1]: *** [debian/rules:17: override_dh_auto_build] Error 1 make[1]: Leaving directory '/<>/strophejs-1.2.14+dfsg' make: *** [debian/rules:14: build-indep] Error 2 dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit status 2 The build was made in my autobuilder with "dpkg-buildpackage -A" and it also fails here: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/strophejs.html If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks. --- End Message --- --- Begin Message --- Source: strophejs Source-Version: 1.2.14+dfsg-4 We believe that the bug you reported is fixed in the latest version of strophejs, 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 922...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dominik George (supplier of updated strophejs 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: Sat, 23 Feb 2019 23:17:03 +0100 Source: strophejs Binary: libjs-strophe Architecture: source all Version: 1.2.14+dfsg-4 Distribution: unstable Urgency: high Maintainer: Debian XMPP Maintainers Changed-By: Dominik George Description: libjs-strophe - Library for writing XMPP clients Closes: 922805 Changes: strophejs (1.2.14+dfsg-4) unstable; urgency=high . * Team upload. * Fix path to almond.js. (Closes: #922805) Checksums-Sha1: 287b4b46f90ce8e0fa12f7f90ba9198d268d76d6 2071 strophejs_1.2.14+dfsg-4.dsc 276dd12fd5812798cc46cc4b01f6b7b0966d7f00 4192 strophejs_1.2.14+dfsg-4.debian.tar.xz 4087e9d1d8f9b0538ec395a15810e9880005ccd5 73144 libjs-strophe_1.2.14+dfsg-4_all.deb 7ea4fab97fa6bd37c6864547a6c5f920fcecb3ae 7240 strophejs_1.2.14+dfsg-4_amd64.buildinfo Checksums-Sha256: e1aaab0bb0df8a6c4aceb0f086613dbe2754985013eeeba3002723552988c163 2071 strophejs_1.2.14+dfsg-4.dsc d1ec2b8bbc5fdeecedc3c7a591fe7307a1d5034808ea879a35c1b6e05ace43c7 4192 strophejs_1.2.14+dfsg-4.debian.tar.xz b3a4e14feebb346b3b19dea8e6076b30e6b515b70ca4053a75da68ccd2cab7e3 73144 libjs-strophe_1.2.14+dfsg-4_all.deb ff2673da007bfbc53222e2f2f120874be3761978674e564a1cb4fcd8d10045d8 7240 strophejs_1.2.14+dfsg-4_amd64.buildinfo Files: 340e5e511ac1559752da9f94f2011a42 2071 web optional strophejs_1.2.14+dfsg-4.dsc 548ab093c2518bc0bfb3da4ade08aa24 4192 web optional strophejs_1.2.14+dfsg-4.debian.tar.xz 32f21920e987744882c7df040ea201c7 73144 web optional libjs-strophe_1.2.14+dfsg-4_all.deb 77e09926edd89628bb1178ee363bd174 7240 web optional strophejs_1.2.14+dfsg-4_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJlBAEBCgBPFiEEPJ1UpHV1wCb7F/0mt5o8FqDE8pYFAlxxx4ExGmh0dHBzOi8v d3d3LmRvbWluaWstZ2VvcmdlLmRlL2dwZy1wb2xpY3kudHh0LmFzYwAKCRC3mjwW
Bug#921637: [DRE-maint] Bug#921637: FTBFS: /usr/lib/ruby/vendor_ruby/ronn/roff.rb:165:in `block_filter': undefined method
Control: tags + confirmed pending On 19-02-23 20:24:15, brian m. carlson wrote: > It would be great if we could get this patch into buster. [...] Upload, including the patch, upcoming in the next days. Cheers, Georg signature.asc Description: Digital signature
Bug#919516: marked as done (ruby2.5 ftbfs in testing/unstable: certificate verify failed (certificate has expired))
Your message dated Sat, 23 Feb 2019 21:34:57 + with message-id and subject line Bug#919516: fixed in ruby2.5 2.5.3-4 has caused the Debian Bug report #919516, regarding ruby2.5 ftbfs in testing/unstable: certificate verify failed (certificate has expired) 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.) -- 919516: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919516 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:ruby2.5 Version: 2.5.3-3 Severity: serious Tags: sid buster [...] 13) Error: TestNetHTTPS#test_get: OpenSSL::SSL::SSLError: SSL_connect returned=1 errno=0 state=error: certificate verify failed (certificate has expired) /home/packages/tmp/ruby2.5-2.5.3/lib/net/protocol.rb:44:in `connect_nonblock' /home/packages/tmp/ruby2.5-2.5.3/lib/net/protocol.rb:44:in `ssl_socket_connect' /home/packages/tmp/ruby2.5-2.5.3/lib/net/http.rb:981:in `connect' /home/packages/tmp/ruby2.5-2.5.3/lib/net/http.rb:920:in `do_start' /home/packages/tmp/ruby2.5-2.5.3/lib/net/http.rb:909:in `start' /home/packages/tmp/ruby2.5-2.5.3/lib/net/http.rb:1455:in `request' /home/packages/tmp/ruby2.5-2.5.3/lib/net/http.rb:1365:in `request_get' /home/packages/tmp/ruby2.5-2.5.3/test/net/http/test_https.rb:44:in `test_get' 14) Error: TestNetHTTPS#test_post: OpenSSL::SSL::SSLError: SSL_connect returned=1 errno=0 state=error: certificate verify failed (certificate has expired) /home/packages/tmp/ruby2.5-2.5.3/lib/net/protocol.rb:44:in `connect_nonblock' /home/packages/tmp/ruby2.5-2.5.3/lib/net/protocol.rb:44:in `ssl_socket_connect' /home/packages/tmp/ruby2.5-2.5.3/lib/net/http.rb:981:in `connect' /home/packages/tmp/ruby2.5-2.5.3/lib/net/http.rb:920:in `do_start' /home/packages/tmp/ruby2.5-2.5.3/lib/net/http.rb:909:in `start' /home/packages/tmp/ruby2.5-2.5.3/lib/net/http.rb:1455:in `request' /home/packages/tmp/ruby2.5-2.5.3/lib/net/http.rb:1409:in `request_post' /home/packages/tmp/ruby2.5-2.5.3/test/net/http/test_https.rb:58:in `test_post' Finished tests in 289.841475s, 59.8914 tests/s, 7810.6041 assertions/s. 17359 tests, 2263837 assertions, 5 failures, 9 errors, 19 skips ruby -v: ruby 2.5.3p105 (2018-10-18 revision 65156) [x86_64-linux-gnu] make[2]: *** [uncommon.mk:698: yes-test-almost] Error 14 make[2]: Leaving directory '/home/packages/tmp/ruby2.5-2.5.3' make[1]: *** [debian/rules:81: override_dh_auto_test-arch] Error 2 make[1]: Leaving directory '/home/packages/tmp/ruby2.5-2.5.3' make: *** [debian/rules:59: build] Error 2 --- End Message --- --- Begin Message --- Source: ruby2.5 Source-Version: 2.5.3-4 We believe that the bug you reported is fixed in the latest version of ruby2.5, 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 919...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Antonio Terceiro (supplier of updated ruby2.5 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: Sat, 23 Feb 2019 17:51:21 -0300 Source: ruby2.5 Architecture: source Version: 2.5.3-4 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Team Changed-By: Antonio Terceiro Closes: 919516 Changes: ruby2.5 (2.5.3-4) unstable; urgency=medium . * 0012-test-update-test-certificate.patch: update test certificate so SSL-related tests pass (Closes: 919516) Checksums-Sha1: fc48180908eac9931b87224c448586bb1b6edc6a 2421 ruby2.5_2.5.3-4.dsc 98ba8b0fc37ff10fc60384c82d4291ea0bc34b43 123764 ruby2.5_2.5.3-4.debian.tar.xz bcaf1d343f33c7e53b6c602e40f8c1b6084c1002 7027 ruby2.5_2.5.3-4_source.buildinfo Checksums-Sha256: df81473d35d5d409794059652fdb17b5f68c0a1164c303d18d7687f8a03529cb 2421 ruby2.5_2.5.3-4.dsc a7ab2d1af3bf4a7ec4a447c717a0ccc88d4b904e2ec61dfa4ab0819487141aa4 123764 ruby2.5_2.5.3-4.debian.tar.xz 1590c63d80f51593983158f3cb6f6e9373695e56a9de313d5f640576baf4943b 7027 ruby2.5_2.5.3-4_source.buildinfo Files: 30a50c8fd97f013e9f8ac91e42b4e669 2421 ruby optional ruby2.5_2.5.3-4.dsc 3a251965a58ec60517f7689114192da7 123764 ruby optional ruby2.5_2.5.3-4.debian.tar.xz 300baec610cf5aa00d0931c70d2a8b0c 7027 ruby optional ruby2.5_2.5.3-4_sourc
Bug#923008: marked as done (CVE-2018-16886)
Your message dated Sat, 23 Feb 2019 21:34:12 +
with message-id
and subject line Bug#923008: fixed in etcd 3.2.26+dfsg-1
has caused the Debian Bug report #923008,
regarding CVE-2018-16886
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.)
--
923008: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923008
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: etcd
Severity: grave
Tags: security
Please see http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-16886 and
https://security-tracker.debian.org/tracker/CVE-2018-16886
Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Source: etcd
Source-Version: 3.2.26+dfsg-1
We believe that the bug you reported is fixed in the latest version of
etcd, 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.
Shengjing Zhu (supplier of updated etcd 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, 24 Feb 2019 02:26:48 +0800
Source: etcd
Architecture: source
Version: 3.2.26+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team
Changed-By: Shengjing Zhu
Closes: 923008
Changes:
etcd (3.2.26+dfsg-1) unstable; urgency=medium
.
* Team upload.
.
[ Arnaud Rebillout ]
* {Build-,}Depends on golang-github-xiang90-probing-dev (>= 0.0.1~)
* Build-Depends on golang-any (>= 2:1.10~)
.
[ Shengjing Zhu ]
* New upstream release v3.2.26
+ Address CVE-2018-16886 (Closes: #923008)
Disable CommonName authentication for gRPC-gateway
gRPC-gateway proxy requests to etcd server use the etcd
client server TLS certificate. If that certificate contains
CommonName we do not want to use that for authentication as
it could lead to permission escalation.
* Remove pgpsigurlmangle in debian/watch.
Upstream didn't sign the source tarball since v3.2.26
* Update pkg-go team address to team+pkg...@tracker.debian.org
* Update debhelper and compat to 11
* Update etcd server default env from upstream docs
* Remove etcd-dump-db, etcd-dump-logs in etcd-client package
upstream didn't provide these tools in v3.2.26 tarball
* Add golang-go.uber-zap-dev to {Build-,}Depends
* Remove socket files created during test phase
Checksums-Sha1:
bb25ff5bd7d7282b6f08ebf05b97f1cc74f6def3 3322 etcd_3.2.26+dfsg-1.dsc
34361315751680213f0f81eaedc3fecc5ce0f952 1003372 etcd_3.2.26+dfsg.orig.tar.xz
0a6a907c1db12db006ea201218cee9f2c7de9951 22136 etcd_3.2.26+dfsg-1.debian.tar.xz
bbf08337c151ff9d304df91ea8b334f005582903 12104
etcd_3.2.26+dfsg-1_amd64.buildinfo
Checksums-Sha256:
8060d0d75c45114608c6fe32ac52100616199a1bd817c99c6a09ef383553219a 3322
etcd_3.2.26+dfsg-1.dsc
b372c18626b884ce810cc1086a9eec7019967776e03d6b91151064398a4bb2fa 1003372
etcd_3.2.26+dfsg.orig.tar.xz
8edb9215addc981c7061d433cc6a2c19d76e95765da8ce7488b81d5335642175 22136
etcd_3.2.26+dfsg-1.debian.tar.xz
cc689ed3d823bdc29e5f5d9e7259792b8fa5d77f0e7836fd8ab4234458917a36 12104
etcd_3.2.26+dfsg-1_amd64.buildinfo
Files:
f22ac2e27a38055263d1280d411bdb20 3322 net optional etcd_3.2.26+dfsg-1.dsc
c0b93d28d7551fabc825b1678c95e2bd 1003372 net optional
etcd_3.2.26+dfsg.orig.tar.xz
b32fb415fae778820b3db4ce17472a11 22136 net optional
etcd_3.2.26+dfsg-1.debian.tar.xz
429ee8547a397da7a6e940ae9f458581 12104 net optional
etcd_3.2.26+dfsg-1_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQFEBAEBCgAuFiEE85F2DZP0aJKsSKyHONAPABi+PjUFAlxxpgEQHHpoc2pAZGVi
aWFuLm9yZwAKCRA40A8AGL4+NWl+B/9FwSWXNYmxlNjxacO0olaAHXjhvIPwbWYX
8XGO9F5SPlCUPuVSV8S25lwwtAot4/b/fR354KdLS14ptltykO4n2Y10y09Y26rT
hepByVoFiCp5jdpzNdzaC+cLzDfPYZq+W9EqWs9NmRFLk6jD7embRram1GH2gvDj
MxO3vzkU6dXpXT++I70EkIIxe88j1UDKCfWeNxVnaf6ZHtlNCV2+zY++ocwxzSr0
19k/wFD8E8xk0cpipd/KhFGs5lYk/V6VZUBVXWdxja0c+7hltwdnc7SkpgTEbzSj
XV4kr9ksh1JqYQvNBrPE0cprYqBbURqW2zLT0bbLfsAoR6ubfB59
=G+5f
-END PGP SIGNATURE End Message ---
Bug#922261: marked as done (python-sunlight: FTBFS (Could not import extension sphinx.ext.pngmath))
Your message dated Sat, 23 Feb 2019 20:57:30 + with message-id and subject line Bug#922261: fixed in python-sunlight 1.1.5-2 has caused the Debian Bug report #922261, regarding python-sunlight: FTBFS (Could not import extension sphinx.ext.pngmath) 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.) -- 922261: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922261 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-sunlight Version: 1.1.5-1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep dh build-indep --with python2,python3,sphinxdoc dh: Compatibility levels before 9 are deprecated (level 8 in use) dh_update_autotools_config -i dh_auto_configure -i dh_auto_configure: Compatibility levels before 9 are deprecated (level 8 in use) dh_auto_configure: Please use the third-party "pybuild" build system instead of python-distutils dh_auto_configure: This feature will be removed in compat 12. debian/rules override_dh_auto_build make[1]: Entering directory '/<>' set -xe; \ for py in python2.7 python3.7; do \ $py setup.py build; \ done + python2.7 setup.py build running build running build_py creating build creating build/lib.linux-x86_64-2.7 creating build/lib.linux-x86_64-2.7/sunlight copying sunlight/config.py -> build/lib.linux-x86_64-2.7/sunlight copying sunlight/__init__.py -> build/lib.linux-x86_64-2.7/sunlight copying sunlight/errors.py -> build/lib.linux-x86_64-2.7/sunlight copying sunlight/service.py -> build/lib.linux-x86_64-2.7/sunlight creating build/lib.linux-x86_64-2.7/sunlight/services copying sunlight/services/capitolwords.py -> build/lib.linux-x86_64-2.7/sunlight/services copying sunlight/services/__init__.py -> build/lib.linux-x86_64-2.7/sunlight/services copying sunlight/services/influenceexplorer.py -> build/lib.linux-x86_64-2.7/sunlight/services copying sunlight/services/openstates.py -> build/lib.linux-x86_64-2.7/sunlight/services copying sunlight/services/congress.py -> build/lib.linux-x86_64-2.7/sunlight/services + python3.7 setup.py build running build running build_py creating build/lib creating build/lib/sunlight copying sunlight/config.py -> build/lib/sunlight copying sunlight/__init__.py -> build/lib/sunlight copying sunlight/errors.py -> build/lib/sunlight copying sunlight/service.py -> build/lib/sunlight creating build/lib/sunlight/services copying sunlight/services/capitolwords.py -> build/lib/sunlight/services copying sunlight/services/__init__.py -> build/lib/sunlight/services copying sunlight/services/influenceexplorer.py -> build/lib/sunlight/services copying sunlight/services/openstates.py -> build/lib/sunlight/services copying sunlight/services/congress.py -> build/lib/sunlight/services make -C docs html make[2]: Entering directory '/<>/docs' sphinx-build -b html -d build/doctrees source build/html Running Sphinx v1.8.3 Extension error: Could not import extension sphinx.ext.pngmath (exception: No module named pngmath) make[2]: *** [Makefile:40: html] Error 2 make[2]: Leaving directory '/<>/docs' make[1]: *** [debian/rules:21: override_dh_auto_build] Error 2 make[1]: Leaving directory '/<>' make: *** [debian/rules:13: build-indep] Error 2 dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit status 2 (The above is just how the build ends and not necessarily the most relevant part) The build was made in my autobuilder with "dpkg-buildpackage -A" and it also fails here: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-sunlight.html where you can get a full build log if you need it. If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks. --- End Message --- --- Begin Message --- Source: python-sunlight Source-Version: 1.1.5-2 We believe that the bug you reported is fixed in the latest version of python-sunlight, 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 922...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dominik George (supplier o
Bug#887988: marked as done (mblaze: File conflict at /usr/bin/msort, /usr/bin/mprev)
Your message dated Sat, 23 Feb 2019 20:50:45 + with message-id and subject line Bug#887988: fixed in mblaze 0.5-1 has caused the Debian Bug report #887988, regarding mblaze: File conflict at /usr/bin/msort, /usr/bin/mprev 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.) -- 887988: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887988 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: mblaze,msort Version: mblaze/0.2-1 msort/8.53-2.1+b2 Severity: serious Hi, when installing mblaze on a system where msort is already installed, it fails to install with a file conflict as follows: Unpacking mblaze (0.2-1) ... dpkg: error processing archive /var/cache/apt/archives/mblaze_0.2-1_amd64.deb (--unpack): trying to overwrite '/usr/bin/msort', which is also in package msort 8.53-2.1+b2 Errors were encountered while processing: /var/cache/apt/archives/mblaze_0.2-1_amd64.deb (Please note that dpkg aborts on the first file conflict and there's a chance that e.g. man pages also have a file conflict.) -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (990, 'unstable'), (600, 'testing'), (500, 'unstable-debug'), (500, 'buildd-unstable'), (110, 'experimental'), (1, 'experimental-debug'), (1, 'buildd-experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.14.0-3-amd64 (SMP w/8 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Source: mblaze Source-Version: 0.5-1 We believe that the bug you reported is fixed in the latest version of mblaze, 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 887...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nicolas Braud-Santoni (supplier of updated mblaze package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 12 Feb 2019 11:44:33 +0100 Source: mblaze Architecture: source Version: 0.5-1 Distribution: unstable Urgency: medium Maintainer: Nicolas Braud-Santoni Changed-By: Nicolas Braud-Santoni Closes: 887988 907537 921891 Changes: mblaze (0.5-1) unstable; urgency=medium . * New upstream release (2019-02-09) + Closes: 921891 + GNUmakefile: correct reference to SOURCE_DATE_EPOCH, patch by Chris Lamb Closes: #907537 . * Rename mless and msort to mblaze-less and mblaze-sort Closes: #887988 correctly, avoids conflicts on mpdtoys & msort . * Switch to debhelper 12. The compatibility level is now controlled by a Build-Depends. . * Declare compliance with policy v4.2.1. No change required. . * debian/rules + Make dh_missing fail the build + Symlink docs from mblaze-* to mblaze Checksums-Sha1: da85ebefd4cb6b2b1efbd1434ed935e133631da6 1794 mblaze_0.5-1.dsc 2ba0f5b7e4717005256cd96e66af90b037a37b74 74968 mblaze_0.5.orig.tar.xz 58026487adaaf7f65fb1c9579614ab70ae26 8348 mblaze_0.5-1.debian.tar.xz 8e8d150a69442a8bf4b5e07b354cd783157bcab1 5472 mblaze_0.5-1_amd64.buildinfo Checksums-Sha256: 1f229e0ceff321d3eb372b080668a4d455c57600a1558b70a0a2df9de1f52d6e 1794 mblaze_0.5-1.dsc 506b20ed79c759b1bcf9303e6f84eab250ff03e5a130b24950797e7593910333 74968 mblaze_0.5.orig.tar.xz 89e4ba07f0e5e87426c9045e3192cb47784084f91b5dd19188dad07d5ee5424d 8348 mblaze_0.5-1.debian.tar.xz c642eee4b00627198b229b23655b261d2652984b38b78f6975a051fbd9c6e66f 5472 mblaze_0.5-1_amd64.buildinfo Files: ce160254eba74e69f2694250ed80ba07 1794 utils optional mblaze_0.5-1.dsc 3e5dd9ad8e8decc083aaedacf43af6f4 74968 utils optional mblaze_0.5.orig.tar.xz 8e7a4b11c3a3b75efb44614cc26bf73f 8348 utils optional mblaze_0.5-1.debian.tar.xz d78e760e33b027c6e9b60cfa32949c2f 5472 utils optional mblaze_0.5-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEU7EqA8ZVHYoLJhPE5vmO4pLV7MsFAlxxo3kACgkQ5vmO4pLV 7MuIHQ/+OpCfnlaPiJtQm4M2ZBXIQG1VpRUwzE9YrlNws/j3mIbw+GGTAHDIxVFS r3ELWY7kd+63AQJDSDA34Dby2YqxMfm8BmfYi4PWjfKSONi1Lo24i3c+cnkxR3MZ nzCN9ileNwiGt+BXWsj7BQKHmHUDM5THvmkWgbcXf79eg+XifkM3oMtp9QCCszUX +SJICRcFee8Idkpn
Bug#915208: marked as done (easybind FTBFS: error: package javafx.beans does not exist)
Your message dated Sat, 23 Feb 2019 20:43:41 +
with message-id
and subject line Bug#915208: fixed in easybind 1.0.3-2
has caused the Debian Bug report #915208,
regarding easybind FTBFS: error: package javafx.beans does not exist
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.)
--
915208: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915208
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: easybind
Version: 1.0.3-1
Severity: serious
Tags: ftbfs buster sid
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/easybind.html
...
Compiling with JDK Java compiler API.
/build/1st/easybind-1.0.3/src/main/java/org/fxmisc/easybind/select/SelectObjectBinding.java:3:
error: package javafx.beans does not exist
import javafx.beans.InvalidationListener;
^
/build/1st/easybind-1.0.3/src/main/java/org/fxmisc/easybind/select/SelectObjectBinding.java:4:
error: package javafx.beans.binding does not exist
import javafx.beans.binding.ObjectBinding;
^
/build/1st/easybind-1.0.3/src/main/java/org/fxmisc/easybind/select/SelectObjectBinding.java:5:
error: package javafx.beans.value does not exist
import javafx.beans.value.ObservableValue;
^
/build/1st/easybind-1.0.3/src/main/java/org/fxmisc/easybind/select/SelectObjectBinding.java:9:
error: cannot find symbol
class SelectObjectBinding extends ObjectBinding implements
MonadicBinding {
^
symbol: class ObjectBinding
/build/1st/easybind-1.0.3/src/main/java/org/fxmisc/easybind/monadic/MonadicBinding.java:3:
error: package javafx.beans.binding does not exist
import javafx.beans.binding.Binding;
^
/build/1st/easybind-1.0.3/src/main/java/org/fxmisc/easybind/monadic/MonadicBinding.java:6:
error: cannot find symbol
extends Binding, MonadicObservableValue {}
^
symbol: class Binding
/build/1st/easybind-1.0.3/src/main/java/org/fxmisc/easybind/monadic/MonadicObservableValue.java:9:
error: package javafx.beans does not exist
import javafx.beans.InvalidationListener;
^
/build/1st/easybind-1.0.3/src/main/java/org/fxmisc/easybind/monadic/MonadicObservableValue.java:10:
error: package javafx.beans.property does not exist
import javafx.beans.property.Property;
^
/build/1st/easybind-1.0.3/src/main/java/org/fxmisc/easybind/monadic/MonadicObservableValue.java:11:
error: package javafx.beans.value does not exist
import javafx.beans.value.ChangeListener;
^
/build/1st/easybind-1.0.3/src/main/java/org/fxmisc/easybind/monadic/MonadicObservableValue.java:12:
error: package javafx.beans.value does not exist
import javafx.beans.value.ObservableObjectValue;
^
/build/1st/easybind-1.0.3/src/main/java/org/fxmisc/easybind/monadic/MonadicObservableValue.java:13:
error: package javafx.beans.value does not exist
import javafx.beans.value.ObservableValue;
^
/build/1st/easybind-1.0.3/src/main/java/org/fxmisc/easybind/monadic/MonadicObservableValue.java:22:
error: cannot find symbol
public interface MonadicObservableValue extends ObservableObjectValue {
^
symbol: class ObservableObjectValue
/build/1st/easybind-1.0.3/src/main/java/org/fxmisc/easybind/select/SelectObjectBinding.java:10:
error: cannot find symbol
private final ObservableValue root;
^
symbol: class ObservableValue
location: class SelectObjectBinding
where T,U are type-variables:
T extends Object declared in class SelectObjectBinding
U extends Object declared in class SelectObjectBinding
...
--- End Message ---
--- Begin Message ---
Source: easybind
Source-Version: 1.0.3-2
We believe that the bug you reported is fixed in the latest version of
easybind, 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 915...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
tony mancill (supplier of updated easybind 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: Sat, 23 F
Bug#921637: [pkg-go] Bug#921637: FTBFS: /usr/lib/ruby/vendor_ruby/ronn/roff.rb:165:in `block_filter': undefined method
On Sat, Feb 16, 2019 at 09:55:16PM -0500, Andrew Janke wrote: > I've confirmed this is the https://github.com/apjanke/ronn-ng/issues/24 bug > in ronn-ng. > > It looks liike an easy fix and I have pushed a ronn-ng 0.8.1.beta.1 > gem/release with the fix. Are you able to test against a prerelease gem? > > I've tested locally and it fixed the problem for git-lfs man generation. > I've also added an ordered-list example to Ronn-NG's internal test suite. It would be great if we could get this patch into buster. I realize that a new version may not be possible, but applying a patch to fix an FTBFS might be. As an upstream Git LFS maintainer, I'm already seeing people trying to build git-lfs packages on buster and (in Ubuntu) disco and failing to do so because of this bug. It will be difficult for us to build our own packages on buster if this isn't fixed. -- brian m. carlson: Houston, Texas, US OpenPGP: https://keybase.io/bk2204 signature.asc Description: PGP signature
Bug#918827: I'll apply the patch and NMU
Hi, since this package is about to be removed I'll apply the patch and NMU soon. Kind regards Andreas. -- http://fam-tille.de
Bug#902618: why: needs porting to why3 version 1.0.0
The current version of why in debian, 2.40, as well as the newest available upstream version 2.41, need a version of why3 that is older than the version of why3 that we have in unstable or in testing (see the table in [1]). As a consequence I think that why should not be distributed with buster. [1] http://krakatoa.lri.fr/
Processed: severity of 902618 is serious
Processing commands for cont...@bugs.debian.org: > severity 902618 serious Bug #902618 [src:why] why: needs porting to why3 version 1.0.0 Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 902618: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902618 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: user debian-rele...@lists.debian.org, usertagging 922805, tagging 922805
Processing commands for cont...@bugs.debian.org: > user debian-rele...@lists.debian.org Setting user to debian-rele...@lists.debian.org (was c.schoen...@t-online.de). > usertags 922805 + bsp-2019-02-de-bonn There were no usertags set. Usertags are now: bsp-2019-02-de-bonn. > tags 922805 + patch Bug #922805 [src:strophejs] strophejs: FTBFS (ERROR: module path does not exist: /usr/lib/nodejs/node-almond/almond.js) Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 922805: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922805 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#923013: [Pkg-xen-devel] Bug#923013: xen: FTBFS when built with dpkg-buildpackage -A
Hi Santiago, First of all, apologies because the tone in my previous message yesterday may sound a bit hostile. I was tired and happy that we had a productive day yesterday, getting ~30 bts closed and an upload with a lot of fixes done, I just did my own rebuild for stretch-backports, and then the report that it ftbfs came in, and I was too quick with thinking "no way, I just built it!". :) Thanks for your report. On 2/23/19 7:04 AM, Santiago Vila wrote: > On Sat, Feb 23, 2019 at 01:15:49AM +0100, Hans van Kranenburg wrote: > >> Can you please help me by formulating a clear problem / question and if >> possible some expected things that you would like to have as a result? > > Sure. This is a packaging bug in debian/rules. Packages must build for the > end user with plain "dpkg-buildpackage" but also in the official > autobuilders by doing "dpkg-buildpackage -A" (to generate arch-all > packages) or "dpkg-buildpackage -B" (to generate arch-indep packages). I can indeed reproduce the error by doing dpkg-buildpackage -A: >8 dh_missing --fail-missing dh_missing: etc/bash_completion.d/xl.sh exists in debian/tmp but is not installed to anywhere >8 This file is installed into the xen-utils-common package as /usr/share/bash-completion/completions/xl. From debian/xen-utils-common.install: >8 #! /usr/bin/dh-exec --with=install [...] etc/bash_completion.d/xl.sh => usr/share/bash-completion/completions/xl >8 > Either of those failing is a FTBFS bug, hence the serious severity. > > To reproduce the problem, please try building the package with > "dpkg-buildpackage -A", which is exactly what the arch:all > autobuilder would do if the package was uploaded in source-only form. > > The hint of splitting dh_foo into dh_foo-arch and dh_foo-indep usually > works for packages that use dh and have this bug, i.e. for packages > which build ok when built with plain "dpkg-buildpackage" but not with > "dpkg-buildpackage -A" or "dpkg-buildpackage -B". All of this seems to be related to the dh-exec usage for putting files in the xen-utils-common package with a different name. This is the first time this package is using dh-exec. If I change the following, dpkg-buildpackage -A completes: >8 diff --git a/debian/xen-utils-common.install b/debian/xen-utils-common.install index 60642c9a9c..e83dc0740b 100755 --- a/debian/xen-utils-common.install +++ b/debian/xen-utils-common.install @@ -2,7 +2,7 @@ etc/xen/scripts etc/xen/xl* -etc/bash_completion.d/xl.sh => usr/share/bash-completion/completions/xl +etc/bash_completion.d/xl.sh usr/share/bash-completion/completions etc/default/xendomains etc/default/xencommons => /etc/default/xen >8 Interestingly, 'etc/default/xencommons => /etc/default/xen' does not result in a similar error? I also found this one, which seems to be related: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831786 Do you have an idea / suggestion how we can deal with this? Hans
Bug#887988: conflicts are not appropriate
Control: reopen -1 Control: found -1 0.3.1-1 Conflicts are no appropriate tool to handle conflicts files. Please fix that properly. Bastian -- Change is the essential process of all existence. -- Spock, "Let That Be Your Last Battlefield", stardate 5730.2
Processed: conflicts are not appropriate
Processing control commands:
> reopen -1
Bug #887988 {Done: Nicolas Braud-Santoni } [mblaze]
mblaze: File conflict at /usr/bin/msort, /usr/bin/mprev
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions mblaze/0.3.1-1.
> found -1 0.3.1-1
Bug #887988 [mblaze] mblaze: File conflict at /usr/bin/msort, /usr/bin/mprev
Marked as found in versions mblaze/0.3.1-1.
--
887988: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887988
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#922261: python-sunlight: FTBFS (Could not import extension sphinx.ext.pngmath)
Hi, On Wed, Feb 13, 2019 at 08:16:36PM +, Santiago Vila wrote: ... > make[2]: Entering directory '/<>/docs' > sphinx-build -b html -d build/doctrees source build/html > Running Sphinx v1.8.3 > > Extension error: > Could not import extension sphinx.ext.pngmath (exception: No module named > pngmath) > make[2]: *** [Makefile:40: html] Error 2 > make[2]: Leaving directory '/<>/docs' > make[1]: *** [debian/rules:21: override_dh_auto_build] Error 2 > make[1]: Leaving directory '/<>' > make: *** [debian/rules:13: build-indep] Error 2 > dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit > status 2 > the fix is rather trivial. The file docs/source/conf.py neededs to be modified as sphinx.ext.pngmath is now been dropped in favour of sphinx.ext.imgmath. Please see attached patch for applying on top the packagig branch. Regards Carsten >From 376ce69f5f4748fd077b13e84243078f86a172b4 Mon Sep 17 00:00:00 2001 From: Carsten Schoenert Date: Sat, 23 Feb 2019 20:08:41 +0100 Subject: [PATCH] adding a patch queue to fix FTBFS added patch: 0001-Fix-FTBFS-with-sphinx-1.8.patch --- .../0001-Fix-FTBFS-with-sphinx-1.8.patch | 23 +++ debian/patches/series | 1 + 2 files changed, 24 insertions(+) create mode 100644 debian/patches/0001-Fix-FTBFS-with-sphinx-1.8.patch create mode 100644 debian/patches/series diff --git a/debian/patches/0001-Fix-FTBFS-with-sphinx-1.8.patch b/debian/patches/0001-Fix-FTBFS-with-sphinx-1.8.patch new file mode 100644 index 000..4c3787e --- /dev/null +++ b/debian/patches/0001-Fix-FTBFS-with-sphinx-1.8.patch @@ -0,0 +1,23 @@ +From: Carsten Schoenert +Date: Sat, 23 Feb 2019 19:50:52 +0100 +Subject: Fix-FTBFS-with-sphinx-1.8 + +sphinx.ext.pngmath has been removed in favor of sphinx.ext.imgmath. +replace the former with the latter in docs/source/conf.py. +--- + docs/source/conf.py | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/docs/source/conf.py b/docs/source/conf.py +index 8ec8ee0..c0c7dd5 100644 +--- a/docs/source/conf.py b/docs/source/conf.py +@@ -17,7 +17,7 @@ version = sunlight.__version__ + # Add any Sphinx extension module names here, as strings. They can be extensions + # coming with Sphinx (named 'sphinx.ext.*') or your custom ones. + extensions = ['sphinx.ext.autodoc', 'sphinx.ext.intersphinx', +-'sphinx.ext.todo', 'sphinx.ext.coverage', 'sphinx.ext.pngmath', ++'sphinx.ext.todo', 'sphinx.ext.coverage', 'sphinx.ext.imgmath', + 'sphinx.ext.ifconfig', 'sphinx.ext.viewcode'] + + # Add any paths that contain templates here, relative to this directory. diff --git a/debian/patches/series b/debian/patches/series new file mode 100644 index 000..4ef579c --- /dev/null +++ b/debian/patches/series @@ -0,0 +1 @@ +0001-Fix-FTBFS-with-sphinx-1.8.patch -- 2.20.1
Processed: unarchiving 887988
Processing commands for cont...@bugs.debian.org:
> unarchive 887988
Bug #887988 {Done: Nicolas Braud-Santoni } [mblaze]
mblaze: File conflict at /usr/bin/msort, /usr/bin/mprev
Unarchived Bug 887988
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
887988: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887988
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#920584: fixed in plastex 1.0.0-1
Hi Stuart, CCing the old bug report to have some public record of our conversation. On Sat, Feb 23, 2019 at 10:49:24AM +1100, Stuart Prescott wrote: > Please reread > > https://release.debian.org/buster/freeze_policy.html > > Particularly the bit about "small targeted fixes". I admit I was aware that I was violating that part. I was hunting for packages with testing removal warning and stumbled upon de-facto orphaned plastex. Version 1.0.0 which is also quite aged seemed like a candidate where this upgrade does not harm. Its a real pity that I was wrong with my estimation and I agree that I should not have done this. > On Friday, 22 February 2019 13:20:03 AEDT Andreas Tille wrote: > > Source: plastex > > Source-Version: 1.0.0-1 > [...] > > We're in the freeze, why are you uploading new upstream releases without > looking very carefully at the changes they bring and checking that they do > not > break rdeps? pyxplot now FTBFS with this version of plastex :( After we now agreed that I did a mistake which I regret what do you think is the best option to fix it. I see: 1. Revert the version bump by adding an epoch. 2. Adapt pyxplot to new version 3. Go with the docs that do not need plastex which seems to be fragile anyway and since it is not ported to Python3 will be droped with Buster+1 anyway. Looking at popcon[1] the usage of the docs is not impressive and its available online as well 4. Any other suggestion? Please decide what would be your prefered choice and I'll help implementing it. Sorry for the trouble Andreas. [1] https://qa.debian.org/popcon-graph.php?packages=pyxplot+pyxplot-doc&show_vote=on&want_legend=on&want_ticks=on&from_date=&to_date=&hlght_date=&date_fmt=%25Y-%25m&beenhere=1 -- http://fam-tille.de
Processed: tagging 922261
Processing commands for cont...@bugs.debian.org: > tags 922261 + pending Bug #922261 [src:python-sunlight] python-sunlight: FTBFS (Could not import extension sphinx.ext.pngmath) Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 922261: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922261 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: fix ftbfs bug metadata
Processing commands for cont...@bugs.debian.org: > # reassign to source package > reassign 922692 src:galax 1.1-15 Bug #922692 [galax] galax: FTBFS - ERROR: unable to find camomileLibrary.cmi in /usr/lib/ocaml/camomile Bug reassigned from package 'galax' to 'src:galax'. No longer marked as found in versions galax/1.1-15. Ignoring request to alter fixed versions of bug #922692 to the same values previously set Bug #922692 [src:galax] galax: FTBFS - ERROR: unable to find camomileLibrary.cmi in /usr/lib/ocaml/camomile Marked as found in versions galax/1.1-15. > # wrongly reassigned from source to non-existent binary > reassign 921732 src:hg-git 0.8.12-1 Bug #921732 [hg-git] hg-git: incompatible with mercurial 4.9 Bug reassigned from package 'hg-git' to 'src:hg-git'. No longer marked as found in versions 0.8.12-1. Ignoring request to alter fixed versions of bug #921732 to the same values previously set Bug #921732 [src:hg-git] hg-git: incompatible with mercurial 4.9 Marked as found in versions hg-git/0.8.12-1. > # reassign to source package > reassign 920442 src:libcaca 0.99.beta19-2 Bug #920442 [libcaca] libcaca FTBFS in unstable Bug reassigned from package 'libcaca' to 'src:libcaca'. No longer marked as found in versions 0.99.beta19-2. Ignoring request to alter fixed versions of bug #920442 to the same values previously set Bug #920442 [src:libcaca] libcaca FTBFS in unstable Marked as found in versions libcaca/0.99.beta19-2. > # wrongly reassigned from source to binary and cleared found version > reassign 867515 src:mdp 3.5-1 Bug #867515 [python3-mdp] mdp FTBFS with python 3.6 as supported version Bug reassigned from package 'python3-mdp' to 'src:mdp'. Ignoring request to alter found versions of bug #867515 to the same values previously set Ignoring request to alter fixed versions of bug #867515 to the same values previously set Bug #867515 [src:mdp] mdp FTBFS with python 3.6 as supported version Marked as found in versions mdp/3.5-1. > # wrongly assigned to non-existent binary package > reassign 843320 src:janest-core-extended 113.00.00-2 Bug #843320 [janest-core-extended] FTBFS: libsexplib-camlp4-dev is no longer available Bug reassigned from package 'janest-core-extended' to 'src:janest-core-extended'. No longer marked as found in versions 113.00.00-2. Ignoring request to alter fixed versions of bug #843320 to the same values previously set Bug #843320 [src:janest-core-extended] FTBFS: libsexplib-camlp4-dev is no longer available Marked as found in versions janest-core-extended/113.00.00-2. > thanks Stopping processing here. Please contact me if you need assistance. -- 843320: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843320 867515: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867515 920442: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920442 921732: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921732 922692: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922692 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#920027: marked as done (python3-persistent: ships headers in /usr/include/python3.7/)
Your message dated Sat, 23 Feb 2019 18:35:36 + with message-id and subject line Bug#920027: fixed in python-persistent 4.2.2-2 has caused the Debian Bug report #920027, regarding python3-persistent: ships headers in /usr/include/python3.7/ 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.) -- 920027: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920027 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-persistent Version: 4.2.2-1 Severity: serious Hi, your package ships the header file(s): /usr/include/python3.7/persistent/cPersistence.h /usr/include/python3.7/persistent/ring.h but /usr/include/python3.7 is a symlink to python3.7m in libpython3.7-dev. This may result in silent file overwrites or depending on the unpacking order /usr/include/python3.7 being a directory in some cases, separating the headers into two independent trees. These header files must be shipped in /usr/include/python3.7m/ instead. Please talk to the python maintainers to find a proper solution for handling the packaging of python header files in a future-proof way. Cheers, Andreas --- End Message --- --- Begin Message --- Source: python-persistent Source-Version: 4.2.2-2 We believe that the bug you reported is fixed in the latest version of python-persistent, 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 920...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dominik George (supplier of updated python-persistent 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: Sat, 23 Feb 2019 19:12:16 +0100 Source: python-persistent Binary: python-persistent python-persistent-dbgsym python-persistent-doc python3-persistent python3-persistent-dbgsym Architecture: source amd64 all Version: 4.2.2-2 Distribution: unstable Urgency: high Maintainer: Debian Python Modules Team Changed-By: Dominik George Description: python-persistent - Automatic persistence for Python objects python-persistent-doc - Automatic persistence for Python objects - documentation python3-persistent - Automatic persistence for Python objects Closes: 920027 Changes: python-persistent (4.2.2-2) unstable; urgency=high . * Team upload. . [ Ondřej Nový ] * d/control: Set Vcs-* to salsa.debian.org * d/control: Remove ancient X-Python-Version field * d/control: Remove ancient X-Python3-Version field . [ Dominik George ] * Move header files to correct location. (Closes: #920027) Checksums-Sha1: 3bfe6073d53f586880bd13006aa954d33abe50fb 2445 python-persistent_4.2.2-2.dsc 470663c516ece76a758e8c61dffacc36d6bc9a38 4384 python-persistent_4.2.2-2.debian.tar.xz 9e12e25f4c5ff7a1a66428f49c7f3e2652784a3a 68600 python-persistent-dbgsym_4.2.2-2_amd64.deb e94a75b3e00bcbfee0abb7d6235f9ff809e265ae 52024 python-persistent-doc_4.2.2-2_all.deb f143b080ec14d2c3026cf18e29008bfecc36a743 9285 python-persistent_4.2.2-2_amd64.buildinfo f70f7a8c0015a21f2926bb145d961270f9a0d064 47880 python-persistent_4.2.2-2_amd64.deb a3cfd76881a06e3a91282519f18e332ba7cf9497 80556 python3-persistent-dbgsym_4.2.2-2_amd64.deb 289b9182acf342b548000731576c8c46e7c28925 48036 python3-persistent_4.2.2-2_amd64.deb Checksums-Sha256: a3275acc59ba116082dc76b3e3b2405e19e66374cb82f333ddd31b702f744961 2445 python-persistent_4.2.2-2.dsc 6b5b1c666a5af0049a3f0d237c962c550eb407b6c1f713800ead6c4dcd22ee98 4384 python-persistent_4.2.2-2.debian.tar.xz 08a606fedd4c355c25b4019bd6f78eff29bf25061b91321a7e3a7931120d9a60 68600 python-persistent-dbgsym_4.2.2-2_amd64.deb c3977f6677e966bfa36d2e9e0d5db6182d018dd18fcd04a0f77de4c090765b26 52024 python-persistent-doc_4.2.2-2_all.deb 9ad12d9ea4043cf72574e3cf182b080eb245c25c5b14520c946b8976ee6b3d88 9285 python-persistent_4.2.2-2_amd64.buildinfo 47c67668c4e9d312d82336c124ab31b82cba6a78297b66d2fd31f80d8fb43d01 47880 python-persistent_4.2.2-2_amd64.deb 25ebee4e94dca8979a77bc12c7a542c9fc0da3fc17316e8ebc5f9e96a67a64cc 80556 python3-persistent-dbgsym_4.2.2-2_amd64.deb 70e397509e7d8a06e0044680999d58767936f8358a79dab6baa5e56714be915a 48036 python3-persistent_4.2.2-2_amd64.deb Files: 54b44e095dc48079c6b3c67e58c15bff 244
Bug#920029: python3-zope.proxy: ships header in /usr/include/python3.7/
Control: tag -1 + pending NMU to DELAYED/2. -nik signature.asc Description: PGP signature
Processed: Re: python3-zope.proxy: ships header in /usr/include/python3.7/
Processing control commands: > tag -1 + pending Bug #920029 [python3-zope.proxy] python3-zope.proxy: ships header in /usr/include/python3.7/ Added tag(s) pending. -- 920029: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920029 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 923053
Processing commands for cont...@bugs.debian.org: > tags 923053 + pending Bug #923053 [python3-stem] python3-stem: Version in stretch-backport isn't installable Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 923053: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923053 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 920027
Processing commands for cont...@bugs.debian.org: > tags 920027 + pending Bug #920027 [python3-persistent] python3-persistent: ships headers in /usr/include/python3.7/ Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 920027: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920027 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#916702: Merge request
Control: tag -1 + pending On Mon, Jan 21, 2019 at 01:28:46PM -0500, Dave Steele wrote: > Upstream upgrade available as a merge request. > > https://salsa.debian.org/debian/python-freezegun/merge_requests I checked that. The new upstream release does not change too much. I chose to merge, test, and upload to DELAYED/2. Maintainer, please consider moving the package to the Debian Python Modules Team. -nik signature.asc Description: PGP signature
Processed: Re: Merge request
Processing control commands: > tag -1 + pending Bug #916702 [src:freezegun] freezegun FTBFS: test failures Added tag(s) pending. -- 916702: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916702 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#923053: python3-stem: Version in stretch-backport isn't installable
Package: python3-stem Version: 1.7.0-1~bpo9+1 Severity: serious Justification: Non installable Control: block 905212 by -1 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi, The version of python3-stem in stretch-backports isn't installable due to its dependency on python3-distutils, which only exists starting with buster: > (stretch-backports-amd64-sbuild)# apt install --dry-run python3-stem > Reading package lists... Done > Building dependency tree > Reading state information... Done > 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: > python3-stem : Depends: python3-distutils but it is not installable > E: Unable to correct problems, you have held broken packages. > > (stretch-backports-amd64-sbuild)# apt-cache policy python3-stem > python3-distutils > python3-stem: > Installed: (none) > Candidate: 1.7.0-1~bpo9+1 > Version table: > 1.7.0-1~bpo9+1 990 > 990 http://localhost:3142/debian stretch-backports/main amd64 Packages > 1.5.3-1 500 > 500 http://localhost:3142/debian stretch/main amd64 Packages > python3-distutils: > Installed: (none) > Candidate: (none) > Version table: > > $ rmadison python3-distutils > python3-distutils | 3.7.2-3 | testing| all > python3-distutils | 3.7.2-3 | unstable | all Best, nicoo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEEU7EqA8ZVHYoLJhPE5vmO4pLV7MsFAlxxiy0RHG5pY29vQGRl Ymlhbi5vcmcACgkQ5vmO4pLV7Mt7hw//Z5579LzG2Ud5Hd32hGiqO1mc9Xo4eyFm ALuXAofejUmM7lgnSx32EfNYXPuYUg4gRXHTqKbvjSqpVrP9Jsy1z/Uzflw1VP/T cURzp9KdlFQvyarb/TXiYKUyX08YzF6ncAZVggqlbHTW78nzs1+tXfHtD6rIZKVQ 5IG+H+OCVS17x2hZh+rQeQgC9ILC4+Av/Uhzt8BCpoq0e2Pecg7ntIBJLYXF4Qxf VuyF+KQFkFsvCBBgctc8hkhDNLjUehPyeVlh0JA1WjEpVKPv6WxH59pNtnR65tt7 K1jU8+dJ5WHmM73lfP/Xt4ZHmoNiZiBWmGWD/yTE4FIFCwN5ifvdDwxsyd2VKc6Q m1wR2/k+KrrVvvhZ4u5rp3p0CrMN1kH0RgSKXGtAFZxxDe44yZ9qXbaB3g6WYUkP Z3L87fl/nwFr3Ui2PEi1IGR5GkiPxH+HMRmsKBjoU6ZycSafIbacsIOQGeNZylm9 MTkRfa3FcUyMyV7zQDiV6CFYXVJ74a73LhBu2lFn3iU8c2ytYtEbVlSdTLEqzLyv rwTwVKH/uTvLoF8+Y22gI/P7+FwWFqs4+QqxfCqzBQseXD/yD/WYgAG2qvR4rAWn 0UQ0eU2s2QSVf0Zil/x/1/9Dc+xWPAG8C/yrm0Ahjfs/tKEbl8ByDDiYyg27iiRo rE2fPMrUXbQ= =7ewQ -END PGP SIGNATURE-
Processed: python3-stem: Version in stretch-backport isn't installable
Processing control commands: > block 905212 by -1 Bug #905212 [nyx] nyx: please provide a backport to stretch 905212 was not blocked by any bugs. 905212 was not blocking any bugs. Added blocking bug(s) of 905212: 923053 -- 905212: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905212 923053: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923053 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#921031: marked as done (Dpkg::Source::Package missing use of ::Format)
Your message dated Sat, 23 Feb 2019 17:49:13 +
with message-id
and subject line Bug#921031: fixed in dpkg 1.19.5
has caused the Debian Bug report #921031,
regarding Dpkg::Source::Package missing use of ::Format
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.)
--
921031: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921031
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libdpkg-perl
Version: 1.19.4
User: debian...@lists.debian.org
Usertags: breaks regression
Hi. I finally investigated the dgit autopkgtest regression.
The error message is:
Can't locate object method "new" via package "Dpkg::Source::Format" (perhaps
you forgot to load "Dpkg::Source::Format"?) at
/usr/share/perl5/Dpkg/Source/Package.pm line 214.
I had mistakenly grokked that as indicating that it was my code which
depended on Dpkg::Source::Format but failed to load it. However, that
isn't the case.
See transcripts below, where a minimal test program for
Dpkg::Source::Package fails with this error, but only with recent
dpkg.
I haven't dug into the dpkg history to see what change caused this. I
guess it will be obvious to you. I think you may just be missing a
`require'.
I thought you would like information report as a bug report. I
haven't made it `serious' since that doesn't seem necessary as it is
blocking the dpkg testing migration already.
Regards,
Ian.
$ dpkg-query -f'${Version}\n' -W libdpkg-perl
1.19.4
$ cat t.pl
#!/usr/bin/perl -w
use strict;
use Dpkg::Source::Package;
my $dp = new Dpkg::Source::Package filename => $ARGV[0];
print "ok\n";
$ ./t.pl ../bpd/dgit_8.3.dsc
Can't locate object method "new" via package "Dpkg::Source::Format" (perhaps
you forgot to load "Dpkg::Source::Format"?) at
/usr/share/perl5/Dpkg/Source/Package.pm line 214.
$
Whereas with stretch:
$ dpkg-query -f'${Version}\n' -W libdpkg-perl
1.18.25
$ ./t.pl ../bpd/dgit_8.3.dsc
ok
$
--
Ian JacksonThese opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.
--- End Message ---
--- Begin Message ---
Source: dpkg
Source-Version: 1.19.5
We believe that the bug you reported is fixed in the latest version of
dpkg, 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 921...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Guillem Jover (supplier of updated dpkg 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: Sat, 23 Feb 2019 18:00:54 +0100
Source: dpkg
Architecture: source
Version: 1.19.5
Distribution: unstable
Urgency: medium
Maintainer: Dpkg Developers
Changed-By: Guillem Jover
Closes: 666147 883700 920880 920905 920972 920974 921031 921557 921942 921943
922039 922212 922407 922410 922799
Changes:
dpkg (1.19.5) unstable; urgency=medium
.
[ Guillem Jover ]
* start-stop-daemon: Make sure that we get a meaningful errno on
parse_unsigned(), so that the error messages always make sense.
* start-stop-daemon: Add new fatalv() and fatale() functions and use the
latter for system errors, so that we are explicit on whether we want to
use errno for error reporting or not.
* start-stop-daemon: Always refuse to parse a world-writable pidfile,
except when that is /dev/null.
* dpkg: Print the current set of enabled force options on --force-help.
* dpkg: Parse and set new DPKG_FORCE environment variable for subprocesses.
Closes: #666147
* dpkg-statoverride: Add support for --force-* options.
* dpkg-statoverride: Switch from --force option to new --force-
options. Deprecate --force option which will be considered an alias for
--force-all for now.
* dpkg, dpkg-statoverride: Add new option --refuse-security-mac to control
SELinux. See #811037.
* dpkg: Clarify error on unknown system user/group in statoverride database.
Closes: #920880
* dpkg-buildpackage: Clarify the warning/error on short OpenPGP key IDs.
Closes: #922039
* dpkg-maintscript-helper: Restrict find for dir-to-symlink move to
-maxdepth 1. Thanks to Ralf Treinen . Closes: #922799
* dpkg-genbu
Bug#922693: marked as done (dgit: autopkgtests regressed since the upload of dpkg 1.19.3)
Your message dated Sat, 23 Feb 2019 17:49:13 + with message-id and subject line Bug#921031: fixed in dpkg 1.19.5 has caused the Debian Bug report #921031, regarding dgit: autopkgtests regressed since the upload of dpkg 1.19.3 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.) -- 921031: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921031 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: dgit Version: 8.3 Severity: normal Subject says it all, I think. Since dpkg 1.19.3, autopkgtests for dgit have gone consistently red: https://ci.debian.net/packages/d/dgit/unstable/amd64/ ... Adam -- System Information: Debian Release: buster/sid APT prefers disco APT policy: (500, 'disco') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-13-lowlatency (SMP w/4 CPU cores; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.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 dgit depends on: ii apt 1.8.0~rc3ubuntu1 ii ca-certificates 20190110 ii coreutils 8.30-1ubuntu1 ii curl7.63.0-1ubuntu1 ii devscripts 2.19.2 ii dpkg-dev1.19.2ubuntu2 ii dput1.0.2ubuntu2 ii git [git-core] 1:2.20.1-2ubuntu1 ii git-buildpackage0.9.13 pn libdigest-sha-perl ii libdpkg-perl1.19.2ubuntu2 ii libjson-perl4.01000-1 ii liblist-moreutils-perl 0.416-1build4 ii liblocale-gettext-perl 1.07-3build3 ii libtext-glob-perl 0.10-1 ii libtext-iconv-perl 1.7-5build7 ii libwww-perl 6.36-1 ii perl5.28.1-4 Versions of packages dgit recommends: ii openssh-client [ssh-client] 1:7.9p1-6 Versions of packages dgit suggests: ii sbuild 0.77.1-2ubuntu2 --- End Message --- --- Begin Message --- Source: dpkg Source-Version: 1.19.5 We believe that the bug you reported is fixed in the latest version of dpkg, 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 921...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Guillem Jover (supplier of updated dpkg 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: Sat, 23 Feb 2019 18:00:54 +0100 Source: dpkg Architecture: source Version: 1.19.5 Distribution: unstable Urgency: medium Maintainer: Dpkg Developers Changed-By: Guillem Jover Closes: 666147 883700 920880 920905 920972 920974 921031 921557 921942 921943 922039 922212 922407 922410 922799 Changes: dpkg (1.19.5) unstable; urgency=medium . [ Guillem Jover ] * start-stop-daemon: Make sure that we get a meaningful errno on parse_unsigned(), so that the error messages always make sense. * start-stop-daemon: Add new fatalv() and fatale() functions and use the latter for system errors, so that we are explicit on whether we want to use errno for error reporting or not. * start-stop-daemon: Always refuse to parse a world-writable pidfile, except when that is /dev/null. * dpkg: Print the current set of enabled force options on --force-help. * dpkg: Parse and set new DPKG_FORCE environment variable for subprocesses. Closes: #666147 * dpkg-statoverride: Add support for --force-* options. * dpkg-statoverride: Switch from --force option to new --force- options. Deprecate --force option which will be considered an alias for --force-all for now. * dpkg, dpkg-statoverride: Add new option --refuse-security-mac to control SELinux. See #811037. * dpkg: Clarify error on unknown system user/group in statoverride database. Closes: #920880 * dpkg-buildpackage: Clarify the warning/error on short OpenPGP key IDs. Closes: #922039 * dpkg-maintscript-helper: Restrict find for dir-to-symlink move to -maxdepth 1. Thanks to Ralf Treinen . Closes: #922799 * dpkg-genbuildinfo: Add support for a new Build-Tainted-By field in .buildinfo files. Suggested by Alexander E. Pat
Bug#914632: uw-imap: CVE-2018-19518
Hi Magnus, >I reckon. I just haven't been able to make gbp use my long PGP key id... any progress with that? Otherwise I’d be willing to NMU your patch. Greetings from the BSP, //mirabilos -- 21:12⎜ sogar bei opensolaris haben die von der community so ziemlich jeden mist eingebaut │ man sollte unices nich so machen das desktopuser zuviel intresse kriegen │ das macht die code base kaputt 21:13⎜ linux war früher auch mal besser :D
Bug#922404: Uploaded and pushed
Hi, I uploaded freeipmi as per the patch in the BTS, plus I pushed the changes to Git. I also fixed Piority from extra to optional, as per the Debian policy. Cheers, Thomas Goirand (zigo)
Bug#921189: marked as done (postsrsd FTBFS on 64bit big endian: AllTests (Failed))
Your message dated Sat, 23 Feb 2019 17:38:32 +
with message-id
and subject line Bug#921189: fixed in postsrsd 1.5-2
has caused the Debian Bug report #921189,
regarding postsrsd FTBFS on 64bit big endian: AllTests (Failed)
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.)
--
921189: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921189
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: postsrsd
Version: 1.5-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/package.php?p=postsrsd
...
dh_auto_test -a -O--buildsystem=cmake
cd obj-s390x-linux-gnu && make -j2 test ARGS\+=-j2
make[1]: Entering directory '/<>/obj-s390x-linux-gnu'
Running tests...
/usr/bin/ctest --force-new-ctest-process -j2
Test project /<>/obj-s390x-linux-gnu
Start 1: AllTests
1/1 Test #1: AllTests .***Failed0.00 sec
srs_forward("n@w", "example.com") = 0
srs_reverse("SRS0=Nl1u=P7=w=n...@example.com") = 0
srs_reverse("SRS0=Nl1u=P7=w=o...@example.com") = 0
0% tests passed, 1 tests failed out of 1
Total Test time (real) = 0.00 sec
The following tests FAILED:
1 - AllTests (Failed)
Errors while running CTest
make[1]: *** [Makefile:99: test] Error 8
--- End Message ---
--- Begin Message ---
Source: postsrsd
Source-Version: 1.5-2
We believe that the bug you reported is fixed in the latest version of
postsrsd, 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 921...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Oxan van Leeuwen (supplier of updated postsrsd 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: Sat, 23 Feb 2019 14:27:44 +0100
Source: postsrsd
Architecture: source
Version: 1.5-2
Distribution: unstable
Urgency: medium
Maintainer: Oxan van Leeuwen
Changed-By: Oxan van Leeuwen
Closes: 921189
Changes:
postsrsd (1.5-2) unstable; urgency=medium
.
* Increase hashlength for unit tests (cherry-picked from upstream db9ed58)
* Fix SHA-1 implementation on big endian architectures (cherry-picked from
upstream 0b8f8be, Closes: #921189)
Checksums-Sha1:
ee2fda8b34556cee18901d109b7c63d65da755a6 1874 postsrsd_1.5-2.dsc
99e728b0a5f2553bce799cd13c7aaefdd21de239 11488 postsrsd_1.5-2.debian.tar.xz
7157632faf4a81efd9a22f05af61a973e4c120c1 6660 postsrsd_1.5-2_amd64.buildinfo
Checksums-Sha256:
33242d3e6739550ffabaeb0aa56d3f791b2e7c867990b6c8f766d3c8b3a136fe 1874
postsrsd_1.5-2.dsc
7e3bbc6e0e37862ba4323f3bf860917050506b9058c426caebb352cac2f745d0 11488
postsrsd_1.5-2.debian.tar.xz
8144994141d355ec451f39951cbf715a45077f4abf2a9d0c6f6daf82b6cad096 6660
postsrsd_1.5-2_amd64.buildinfo
Files:
7039fdd7a80363cc350be04e65825f0e 1874 mail optional postsrsd_1.5-2.dsc
7911efc17d94774e0cab04a277341315 11488 mail optional
postsrsd_1.5-2.debian.tar.xz
b634d016aeee8aec3d67d4830b466aa2 6660 mail optional
postsrsd_1.5-2_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQJGBAEBCgAwFiEEzmRl4OZ9N8ZVV+eKAK40x+rZ6zgFAlxxgZ8SHHRvbWFzekBi
dWNoZXJ0LnBsAAoJEACuNMfq2es4XDcP/24+YJyCa/Iw27pZhmz6ir7Kh79RhHxX
tr7n6x4+52j2h56aXMp3LOOnpQB7S97K7YndRqbP3Ysybttdks6ttmuh9Cho0kgF
T42x10PXSi1JsC1ag7senoE7ipf8Los8BGMJavLtP69T2c8iyuox2r0BBJ+5YlNr
aVmN5qRChL6gqTD3ROqoZ+xQH3utJLIKoDALGaOgcfcr4B5Mrr1iumjeuxKoK6lT
FnFvmGdrvbe5i1UenHxVu4Xgc6RgE/VEGbXoH/7WDLeb4jMJ86bEcHX6LmbDw5RB
yIfc2f84pJshwBC8c5qQG1IZVes1fk8dneGYO3e1LYELzaCvcCfttErjJAWwllsq
JpJClgxx9J+qGKnSjuSGWsuS0/jDpFhlnse8hPnjtvlZsshuxihtbWKlkllrXqp/
piysMWuTf5dTDj3WxFbt9xmkxD9OWQYyECHAf2pwkP75hOH2BuxVGXLsEmRm2jj1
KNGiEU7TNSeedyLGC8ItjpsWA/pfvXB80bTtCxhRvwyiddi49mywIesH3JaPfr6a
wrZl/NU5s4Y18Ed1usFgbTRzI77629j992Bbj1OwL9YCk7W2HoyPN8/x4DsCIazB
XuldqEen8mAHFuoLxv8JKXL9JyZR/Vks2F9zLZkUMHzP7xiq6seb9pUWT1M+oT/Y
6+xeXxxQKrxT
=CLkW
-END PGP SIGNATURE End Message ---
Processed: Bug#921031 in package dpkg marked as pending
Processing control commands: > tag 921031 pending Bug #921031 [libdpkg-perl] Dpkg::Source::Package missing use of ::Format Bug #922693 [libdpkg-perl] dgit: autopkgtests regressed since the upload of dpkg 1.19.3 Added tag(s) pending. Added tag(s) pending. -- 921031: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921031 922693: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922693 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#921031: in package dpkg marked as pending
Control: tag 921031 pending Hi! Bug #921031 in package dpkg reported by you has been fixed in the dpkg/dpkg.git Git repository. You can see the changelog below, and you can check the diff of the fix at: https://git.dpkg.org/cgit/dpkg/dpkg.git/diff/?id=41628ced3 --- commit 41628ced3ebbdb2ed2219b5320b6301aee7d65be Author: Guillem Jover Date: Fri Feb 1 03:41:25 2019 +0100 Dpkg::Source::Package: Add a missing use Dpkg::Source::Format Closes: #921031 Fixes: commit d1d35a56e401181b6d15baf474a7db21d3372a65 Diagnosed-by: Ian Jackson diff --git a/debian/changelog b/debian/changelog index 16ea0cf74..90edb01b0 100644 --- a/debian/changelog +++ b/debian/changelog @@ -29,6 +29,9 @@ dpkg (1.19.5) UNRELEASED; urgency=medium - Dpkg::Vendor::Debian: Add support for merged-usr-via-symlinks tainted tag. Suggested by Alexander E. Patrakov . - Dpkg::Vendor::Debian: Add support for usr-local-has-* tainted tags. +- Dpkg::Source::Package: Add a missing use Dpkg::Source::Format. + Diagnosed by Ian Jackson . + Closes: #921031 * Documentation: - start-stop-daemon(1): Document behavior of --pidfile security checks. Closes: #921557
Processed: fix wrong close version.
Processing commands for cont...@bugs.debian.org:
> notfixed 921745 0.11.1-2
Bug #921745 {Done: Yaroslav Halchenko } [src:datalad]
src:datalad: Build-depends/Recommends uninstallable packages
The source 'datalad' and version '0.11.1-2' do not appear to match any binary
packages
No longer marked as fixed in versions 0.11.1-2.
> close 921745 0.11.2-2
Bug #921745 {Done: Yaroslav Halchenko } [src:datalad]
src:datalad: Build-depends/Recommends uninstallable packages
Marked as fixed in versions datalad/0.11.2-2.
Bug #921745 {Done: Yaroslav Halchenko } [src:datalad]
src:datalad: Build-depends/Recommends uninstallable packages
Bug 921745 is already marked as done; not doing anything.
> thanks.
Stopping processing here.
Please contact me if you need assistance.
--
921745: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921745
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#922957: marked as done (python-igraph's tests fail with Python 3.7 on Windows10 (version python-igraph/0.7.1.post6-6))
Your message dated Sat, 23 Feb 2019 22:08:32 +0500
with message-id <20190223170832.ga4...@belkar.wrar.name>
and subject line Re: Bug#922957: python-igraph's tests fail with Python 3.7 on
Windows10 (version python-igraph/0.7.1.post6-6)
has caused the Debian Bug report #922957,
regarding python-igraph's tests fail with Python 3.7 on Windows10 (version
python-igraph/0.7.1.post6-6)
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.)
--
922957: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922957
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-igraph
Version: 0.7.1.post6-6
Severity: serious
python-igraph's tests fail with Python 3.7, RC severity for the upcoming Python
3.7 transition.
..E.E..E...
==
ERROR: testFormula (igraph.test.generators.GeneratorTests)
--
Traceback (most recent call last):
File
"C:\Users\Nczjam\AppData\Local\Programs\Python\Python37\lib\site-packages\igraph\test\generators.py",
line 72, in testFormula
g = Graph.Formula(formula)
File
"C:\Users\Nczjam\AppData\Local\Programs\Python\Python37\lib\site-packages\igraph\formula.py",
line 209, in construct_graph_from_formula
for start_names, end_names, arrowheads in generate_edges(part):
File
"C:\Users\Nczjam\AppData\Local\Programs\Python\Python37\lib\site-packages\igraph\formula.py",
line 90, in generate_edges
raise SyntaxError(msg)
File "", line None
SyntaxError: invalid token found in edge specification: A
==
ERROR: testPickle (igraph.test.foreign.ForeignTests)
--
Traceback (most recent call last):
File
"C:\Users\Nczjam\AppData\Local\Programs\Python\Python37\lib\site-packages\igraph\test\foreign.py",
line 207, in testPickle
g = Graph.Read_Pickle(pickle)
File
"C:\Users\Nczjam\AppData\Local\Programs\Python\Python37\lib\site-packages\igraph\__init__.py",
line 1829, in Read_Pickle
fp = open(fname, "rb")
UnicodeDecodeError: 'utf-8' codec can't decode byte 0x80 in position 0: invalid
start byte
==
ERROR: testCohesiveBlocks2 (igraph.test.decomposition.CohesiveBlocksTests)
--
Traceback (most recent call last):
File
"C:\Users\Nczjam\AppData\Local\Programs\Python\Python37\lib\site-packages\igraph\test\decomposition.py",
line 329, in testCohesiveBlocks2
g = Graph.Formula("1-2:3:4:5:6, 2-3:4:5:7, 3-4:6:7, 4-5:6:7, "
File
"C:\Users\Nczjam\AppData\Local\Programs\Python\Python37\lib\site-packages\igraph\formula.py",
line 209, in construct_graph_from_formula
for start_names, end_names, arrowheads in generate_edges(part):
File
"C:\Users\Nczjam\AppData\Local\Programs\Python\Python37\lib\site-packages\igraph\formula.py",
line 90, in generate_edges
raise SyntaxError(msg)
File "", line None
SyntaxError: invalid token found in edge specification: 1-2:3:4:5:6
--
Ran 307 tests in 2.798s
FAILED (errors=3)
--- End Message ---
--- Begin Message ---
On Fri, Feb 22, 2019 at 10:53:41AM +0100, ensieh.davoodi...@uzh.ch wrote:
> Package: src:python-igraph
> Version: 0.7.1.post6-6
> Severity: serious
>
> python-igraph's tests fail with Python 3.7
They don't in sid. Please only report bugs that actually happen in Debian.
--
WBR, wRAR
signature.asc
Description: PGP signature
--- End Message ---
Bug#923011: nuxwdog: FTBFS (/usr/include/keyutils.h:204:48: error: expected ',' or '...' before 'private')
On Fri, Feb 22, 2019 at 10:53:47PM +, Santiago Vila wrote: > In file included from src/com/redhat/nuxwdog/wdpwd.cpp:37: > /usr/include/keyutils.h:204:48: error: expected ',' or '...' before 'private' > extern long keyctl_dh_compute_kdf(key_serial_t private, key_serial_t prime, > ^~~ https://bugzilla.redhat.com/show_bug.cgi?id=1629878 https://lkml.org/lkml/2018/8/28/1051 (linked from there) -- WBR, wRAR signature.asc Description: PGP signature
Bug#893287: marked as done (libjogl2-java FTBFS with openjdk-9)
Your message dated Sat, 23 Feb 2019 16:04:22 + with message-id and subject line Bug#893287: fixed in libjogl2-java 2.3.2+dfsg-8 has caused the Debian Bug report #893287, regarding libjogl2-java FTBFS with openjdk-9 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.) -- 893287: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893287 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libjogl2-java Version: 2.3.2+dfsg-5 Severity: serious Tags: buster sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libjogl2-java.html ... BUILD FAILED /build/1st/libjogl2-java-2.3.2+dfsg/make/build.xml:71: The following error occurred while executing this line: /build/1st/libjogl2-java-2.3.2+dfsg/make/build-nativewindow.xml:798: The following error occurred while executing this line: /build/1st/libjogl2-java-2.3.2+dfsg/make/build-nativewindow.xml:738: /usr/lib/jvm/jre/lib/amd64 does not exist. at org.apache.tools.ant.types.AbstractFileSet.getDirectoryScanner(AbstractFileSet.java:505) at net.sf.antcontrib.cpptasks.types.LibrarySet.visitLibraries(LibrarySet.java:310) at net.sf.antcontrib.cpptasks.LinkerDef.visitSystemLibraries(LinkerDef.java:469) at net.sf.antcontrib.cpptasks.CCTask.collectExplicitObjectFiles(CCTask.java:520) at net.sf.antcontrib.cpptasks.CCTask.execute(CCTask.java:613) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:293) at jdk.internal.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:564) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106) at org.apache.tools.ant.Task.perform(Task.java:348) at org.apache.tools.ant.taskdefs.Sequential.execute(Sequential.java:67) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:564) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106) at org.apache.tools.ant.Task.perform(Task.java:348) at net.sf.antcontrib.logic.OutOfDate.execute(OutOfDate.java:457) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:293) at jdk.internal.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:564) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106) at org.apache.tools.ant.Task.perform(Task.java:348) at org.apache.tools.ant.taskdefs.Sequential.execute(Sequential.java:67) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:293) at jdk.internal.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:564) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106) at org.apache.tools.ant.Task.perform(Task.java:348) at org.apache.tools.ant.taskdefs.MacroInstance.execute(MacroInstance.java:402) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:293) at jdk.internal.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:564) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106) at org.apache.tools.ant.Task.perform(Task.java:348) at org.apache.tools.ant.Target.execute(Target.java:437) at org.apache.tools.ant.Target.performTasks(Target.java:458) at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1405) at org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:36) at org.apache.tools.ant.Project.executeTargets(Pro
Processed: tg.controllers.decoratedcontroller requires newer python-crank
Processing control commands: > block 922263 by -1 Bug #922263 [src:turbogears2-doc] turbogears2-doc: FTBFS (ImportError: cannot import name flatten_arguments) 922263 was not blocked by any bugs. 922263 was not blocking any bugs. Added blocking bug(s) of 922263: 923049 -- 922263: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922263 923049: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923049 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#893287: Bug #893287 in libjogl2-java marked as pending
Control: tag -1 pending Hello, Bug #893287 in libjogl2-java 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/libjogl2-java/commit/112b53cf6a8d9d06ffe655c0c147ccdee941db68 java11.patch: Fix FTBFS with Java 11. Closes: #893287 (this message was generated automatically) -- Greetings https://bugs.debian.org/893287
Bug#921898: marked as done (pilkit: FTBFS (AssertionError: '.apng' != '.png'))
Your message dated Sat, 23 Feb 2019 15:49:56 +
with message-id
and subject line Bug#921898: fixed in pilkit 2.0-2
has caused the Debian Bug report #921898,
regarding pilkit: FTBFS (AssertionError: '.apng' != '.png')
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.)
--
921898: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921898
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:pilkit
Version: 2.0-1
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-indep
dh build-indep --with python2,python3 --buildsystem=pybuild
dh_update_autotools_config -i -O--buildsystem=pybuild
dh_auto_configure -i -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
debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
cp debian/reference.png tests/assets/reference.png
dh_auto_build
I: pybuild base:217: /usr/bin/python setup.py build
running build
[... snipped ...]
tests.test_processors.test_smartcrop ... ok
tests.test_processors.test_resizetofill ... ok
tests.test_processors.test_resizetofit ... ok
Regression test for matthewwithanm/pilkit#1 ... ok
tests.test_processors.test_resizetofit_mat ... ok
Test that the ColorOverlay processor ... ok
Test that the Resize processor antialiases. ... ok
Test that the upscale argument works as expected. ... ok
tests.test_processors.test_should_raise_exception_if_anchor_is_passed_and_crop_is_set_to_false
... ok
tests.test_processors.test_should_set_crop_to_true_if_anchor_is_passed_without_crop
... ok
tests.test_processors.test_should_raise_exception_when_crop_is_passed_without_height_and_width
... ok
tests.test_processors.test_make_gifs_opaque ... ok
tests.test_processors.test_should_call_resizetofill_when_crop_and_ancho_is_passed
... ok
tests.test_processors.test_should_call_resizetofit_when_crop_is_not_passed ...
ok
tests.test_processors.test_should_call_smartresize_when_crop_not_passed ... ok
tests.test_processors.test_should_repass_upscale_option_false ... ok
tests.test_processors.test_should_repass_upscale_option_true ... ok
tests.test_utils.test_extension_to_format ... ok
tests.test_utils.test_format_to_extension_no_init ... FAIL
tests.test_utils.test_unknown_format ... ok
tests.test_utils.test_unknown_extension ... ok
Ensure default extensions are honored. ... ok
tests.test_utils.test_filewrapper ... ok
Test that ``save_image`` accepts filename strings (not just file objects). ...
ok
Make sure formats are normalized by ``prepare_image()``. ... ok
Make sure the ``quiet`` util doesn't error if devnull is unwriteable. ... ok
==
FAIL: tests.test_utils.test_format_to_extension_no_init
--
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
File
"/<>/.pybuild/cpython2_2.7_pilkit/build/tests/test_utils.py", line
19, in test_format_to_extension_no_init
eq_(format_to_extension('PNG'), '.png')
AssertionError: '.apng' != '.png'
--
Ran 26 tests in 0.205s
FAILED (failures=1)
E: pybuild pybuild:338: test: plugin distutils failed with: exit code=1: cd
/<>/.pybuild/cpython2_2.7_pilkit/build; python2.7 -m nose -v tests
dh_auto_test: pybuild --test --test-nose -i python{version} -p 2.7 returned
exit code 13
make: *** [debian/rules:9: build-indep] Error 25
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit
status 2
(The above is just how the build ends and not necessarily the most relevant
part)
The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/pilkit.html
where you can get a full build log if you need it.
If this is really a bug in one of the build-depends, please use reassign and
affects,
so that this is still visible in the BTS web page for this package.
Thanks.
--- End Message ---
--- Begin Message ---
Source: pilkit
Source-Version: 2.0-2
We believe that the bug you reported is fixed in the latest version of
pilkit, which is due to be installed in the Debian FTP archive.
Processed: Bug #893287 in libjogl2-java marked as pending
Processing control commands: > tag -1 pending Bug #893287 [src:libjogl2-java] libjogl2-java FTBFS with openjdk-9 Added tag(s) pending. -- 893287: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893287 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#921759: marked as done (sdaps: FTBFS (Error running "pdflatex" to compile the LaTeX file))
Your message dated Sat, 23 Feb 2019 15:34:36 +
with message-id
and subject line Bug#921759: fixed in sdaps 1.2.1-2
has caused the Debian Bug report #921759,
regarding sdaps: FTBFS (Error running "pdflatex" to compile the LaTeX file)
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.)
--
921759: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921759
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:sdaps
Version: 1.2.1-1
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-arch
dh build-arch --with python2 --buildsystem=pybuild
dh_update_autotools_config -a -O--buildsystem=pybuild
dh_autoreconf -a -O--buildsystem=pybuild
dh_auto_configure -a -O--buildsystem=pybuild
I: pybuild base:217: python2.7 setup.py config
running config
dh_auto_build -a -O--buildsystem=pybuild
I: pybuild base:217: /usr/bin/python setup.py build
running build
running build_py
creating /<>/.pybuild/cpython2_2.7_sdaps/build/sdaps
copying sdaps/defs.py ->
/<>/.pybuild/cpython2_2.7_sdaps/build/sdaps
copying sdaps/paths.py ->
/<>/.pybuild/cpython2_2.7_sdaps/build/sdaps
[... snipped ...]
(/usr/share/texlive/texmf-dist/fonts/source/jknappen/ec/exromp.mf
Ok [38] [63] [190])
(/usr/share/texlive/texmf-dist/fonts/source/jknappen/ec/exrulett.mf
Ok [65] [66] [67] [68] [69] [70] [71] [72] [73] [74] [75] [76] [77] [78]
[79] [80] [81] [82] [83] [84] [85] [86] [87] [88] [89] [90])
(/usr/share/texlive/texmf-dist/fonts/source/jknappen/ec/exrllett.mf
Ok [97] [98] [99] [100] [101] [102] [103] [104] [105] [106] [107] [108]
[109] [110] [111] [112] [113] [114] [115] [116] [117] [118] [119] [120]
[121] [122])
(/usr/share/texlive/texmf-dist/fonts/source/jknappen/ec/exrdigit.mf
Ok [48] [49] [50] [51] [52] [53] [54] [55] [56] [57])
(/usr/share/texlive/texmf-dist/fonts/source/jknappen/ec/exrligtb.mf
Ok) ) ) )
(some charht values had to be adjusted by as much as 0.08084pt)
Font metrics written on ecrm1440.tfm.
Output written on ecrm1440.600gf (256 characters, 71064 bytes).
Transcript written on ecrm1440.log.
mktexpk: /tmp/texfonts/pk/ljfour/jknappen/ec/ecrm1440.600pk: successfully
generated.
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
Running pdflatex now twice to generate the report.
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
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
Error: An error occured in the setup routine. The survey directory still
exists. You can for example check the questionnaire.log file for LaTeX compile
errors.
Running pdflatex now twice to generate the questionnaire.
Error running "pdflatex" to compile the LaTeX file.
Traceback (most recent call last):
File "../sdaps.py", line 23, in
sys.exit(sdaps.main(local_run = True))
File "/<>/sdaps/__init__.py", line 64, in main
return cmdline['_func'](cmdline)
File "/<>/sdaps/cmdline/setuptex.py", line 47, in setup_tex
return setuptex.setup(survey, cmdline['questionnaire.tex'],
cmdline['additional_questions'], cmdline['add'])
File "/<>/sdaps/setuptex/__init__.py", line 100, in setup
raise AssertionError('PDF file not generated')
AssertionError: PDF file not generated
make[1]: *** [debian/rules:11: override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:7: build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit
status 2
(The above is just how the build ends and not necessarily the most relevant
part)
The build was made in my autobuilder with "dpkg-buildpackage -B"
and it also fails here:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/sdaps.html
where you can get a full build log if you need it.
If this is really a bug in one of the build-depends, please use reassign and
affects,
so that this is still visible in the BTS web page for this package.
Thanks.
--- End Message ---
--- Begin Message ---
Source: sdaps
Source-Version: 1.2.1-2
We believe that the bug you reported is fixed in the latest version of
sdaps, which is due to be installed in the Debian FTP archive
Processed (with 1 error): Re: Bug#921898: pilkit: FTBFS (AssertionError: '.apng' != '.png')
Processing control commands: > tags -1 + upstr4eam fixed-upstream patch pending Unknown tag/s: upstr4eam. Recognized are: patch wontfix moreinfo unreproducible help security upstream pending confirmed ipv6 lfs d-i l10n newcomer a11y ftbfs fixed-upstream fixed fixed-in-experimental sid experimental potato woody sarge sarge-ignore etch etch-ignore lenny lenny-ignore squeeze squeeze-ignore wheezy wheezy-ignore jessie jessie-ignore stretch stretch-ignore buster buster-ignore bullseye bullseye-ignore. Bug #921898 [src:pilkit] pilkit: FTBFS (AssertionError: '.apng' != '.png') Added tag(s) pending, patch, and fixed-upstream. -- 921898: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921898 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#921898: pilkit: FTBFS (AssertionError: '.apng' != '.png')
Control: tags -1 + upstr4eam fixed-upstream patch pending
On Sat, Feb 09, 2019 at 11:49:51PM +, Santiago Vila wrote:
> ==
> FAIL: tests.test_utils.test_format_to_extension_no_init
> --
> Traceback (most recent call last):
> File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest
> self.test(*self.arg)
> File
> "/<>/.pybuild/cpython2_2.7_pilkit/build/tests/test_utils.py",
> line 19, in test_format_to_extension_no_init
> eq_(format_to_extension('PNG'), '.png')
> AssertionError: '.apng' != '.png'
This seems to be fixed by
https://github.com/matthewwithanm/pilkit/commit/c3702a84ae603f4d06dec8827be66c43644a9683
--
WBR, wRAR
signature.asc
Description: PGP signature
Bug#922257: pyfr: FTBFS (dh_installman: Could not determine section for ./build/man/_static)
Control: tags -1 + patch On Wed, Feb 13, 2019 at 08:16:28PM +, Santiago Vila wrote: >dh_installman -i -O--buildsystem=pybuild > dh_installman: Could not determine section for ./build/man/_static This is caused by "build/man/*" in debian/pyfr.manpages. I think it's safe to assume that replacing that with "build/man/pyfr.1" should help. -- WBR, wRAR signature.asc Description: PGP signature
Processed: Re: Bug#922257: pyfr: FTBFS (dh_installman: Could not determine section for ./build/man/_static)
Processing control commands: > tags -1 + patch Bug #922257 [src:pyfr] pyfr: FTBFS (dh_installman: Could not determine section for ./build/man/_static) Added tag(s) patch. -- 922257: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922257 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: retitle 922179 to shim-signed depends on packages not in repos
Processing commands for cont...@bugs.debian.org: > retitle 922179 shim-signed depends on packages not in repos Bug #922179 [shim-signed] shim-signed depends on packages not repos Changed Bug title to 'shim-signed depends on packages not in repos' from 'shim-signed depends on packages not repos'. > thanks Stopping processing here. Please contact me if you need assistance. -- 922179: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922179 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#921787: kombu: FTBFS (failing tests)
Processing control commands: > tags -1 + upstream fixed-upstream patch Bug #921787 [src:kombu] kombu: FTBFS (failing tests) Added tag(s) patch, upstream, and fixed-upstream. -- 921787: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921787 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#921787: kombu: FTBFS (failing tests)
Control: tags -1 + upstream fixed-upstream patch This seems to be fixed by https://github.com/celery/kombu/pull/978/files -- WBR, wRAR signature.asc Description: PGP signature
Bug#923042: node-handlebars: Prototype Pollution allowing an attacker to execute arbitrary code
Quoting Jonas Smedegaard (2019-02-23 15:15:25) > All releases of handlebars older than 4.0.13 should be affected. Possibly only 4.x versions are affected - according to this: https://github.com/wycats/handlebars.js/issues/1495 - 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#914632: uw-imap: CVE-2018-19518
Hi, On Sun, Jan 13, 2019 at 06:24:36PM +0100, Magnus Holmgren wrote: > söndag 13 januari 2019 kl. 08:31:28 CET skrev Salvatore Bonaccorso: > > On Fri, Dec 28, 2018 at 10:22:53AM +0100, Moritz Mühlenhoff wrote: > > > On Wed, Dec 26, 2018 at 05:20:40PM +0100, Magnus Holmgren wrote: > > > > I'm wondering if anyone would complain if I'd disable RSH (SSH) > > > > connections > > > > altogether. > > > > > > Full ack, that seems like the most sensible fix. > > > > Any news on this approach, or did you spot any problem with that way? > > Here's my plan. Removing the RSHPATH define should disable the insecure code, > I reckon. I just haven't been able to make gbp use my long PGP key id... Any news on this? Regards, Salvatore
Bug#923042: node-handlebars: Prototype Pollution allowing an attacker to execute arbitrary code
Source: node-handlebars Version: 3:4.0.10-5 Severity: grave Tags: security upstream -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 At https://snyk.io/vuln/SNYK-JS-HANDLEBARS-173692 this is reported: > Affected versions of this package are vulnerable to Prototype Pollution. > Templates may alter an Objects' prototype, thus allowing an attacker to > execute arbitrary code on the server. All releases of handlebars older than 4.0.13 should be affected. - Jonas -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAlxxVXoACgkQLHwxRsGg ASGoEA/+NGvVunzYs3SvvZRC8SaGuV8s3I9BolYz9w5/HA2jks61I0QPKL+NioOC Ky9+4X0nIQcsotu3eOJe3q7abbRrSdILO00RmvFsoHlHeSBYqQB+FoAG439QyNmb vzPaJ0cU2h+WujuCZxRI2kl0xcUzchHq2iEqJW2aueEuxhdOAPCrykzDWo6bL8FU mknTpLeukJ7Ownj7H3XbT8z2pFZ1Pv2sq4UsMEcu6FljGec9qWm1Ohn0qq9WQYrP a2zhQpF77QhDDUEBVP/HeQTx4In8RetM4Iim3XH93KG5j1VY8R+2pVbynbMWbk6c C6h1vm6hezmtiuJtw6p5oy5Kda1/waxFaIUfCHIF9DhdTV2ZY74MapdC2e8HAD9g iKq9Eq2P+OYMBkGRbcAvOcUQgpX4dJWihelv1DJQJWYbYCJaG+hTUd+S0cHakfLa +IdiZ3h4dVUmIuWKV1fmUhUBWnr7mHTPLe4tiIQqqD3T51zIUO1xMu953L0xprH2 UdESnJG4ySryK06SKaljtfXRz3WlsPrPGTJu2LYN9Y6xEugu+dm3heqdxnv8Ek4A P2rrPWlULbUI9Rk8lkcFiNLNeS7zzHflcp2qY02CLN8zSGkaBIVf/RKnhSO624pA lV0BTfNiEk2tGAYV8vN/TOcZQb1gQRdT0qoFgU63bQaVvDS7gig= =JfmR -END PGP SIGNATURE-
Bug#859224: netkit-ftp-ssl: Please migrate to openssl1.1 in Buster
On 2019-02-23 12:47:40 [+0100], Christoph Biedl wrote: > Sebastian Andrzej Siewior wrote... > > > Do you still plan to address this or should a RM be filled? The window > > for Buster has been closed imho. > > Yes, and yes :( > > Patches are more or less done but I haven't got the tuits for the last > checks unfortunatly. Unless I'm done within the next 48h, I'll give up > on these. Ah okay. The SSL part should be good. So it is just the Makefile bits that are missing. > Christoph, at the Bonn BSP Have fun. I planned to say hello but probably don't make it… Sebastian
Bug#922404: freeipmi install fails
Hi, just upload to unstable or move the upload, all fine by me. The git should be writeable by you as it is in the Debian group in salsa, please push your changes if possible. Thanks a lot, Bernd Am 23. Februar 2019 14:15:22 MEZ schrieb Dominik George : >Hi, > >> Installation fails because ipmidetectd has an empty default >> configuration. Fix simply avoids to enable and start the daemon that >> will need to be configured by hand. > >Building the package, lintian reported that the real culprit here is >that RUN= variables in /etc/default should not be used anymore. I thus >completed the patch by avoiding this in both optional services. See >attached. I will upload to DELAYED/5. > >-nik -- Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.
Bug#922404: freeipmi install fails
Hi, > Installation fails because ipmidetectd has an empty default > configuration. Fix simply avoids to enable and start the daemon that > will need to be configured by hand. Building the package, lintian reported that the real culprit here is that RUN= variables in /etc/default should not be used anymore. I thus completed the patch by avoiding this in both optional services. See attached. I will upload to DELAYED/5. -nik diff -Nru freeipmi-1.6.3/debian/changelog freeipmi-1.6.3/debian/changelog --- freeipmi-1.6.3/debian/changelog 2019-02-02 15:50:10.0 +0100 +++ freeipmi-1.6.3/debian/changelog 2019-02-23 14:06:54.0 +0100 @@ -1,3 +1,15 @@ +freeipmi (1.6.3-1.1) unstable; urgency=high + + * Non-maintainer upload. + + [ Antonio Galea ] + * Do not start ipmidetectd daemon until configured. Closes: #922404 + + [ Dominik George ] + * Use init system to handle defaults instead of RUN= (cf. lintian error). + + -- Dominik George Sat, 23 Feb 2019 14:06:54 +0100 + freeipmi (1.6.3-1) unstable; urgency=medium * [3f1f5ea] Updating symbols file diff -Nru freeipmi-1.6.3/debian/freeipmi-ipmidetect.ipmidetectd.default freeipmi-1.6.3/debian/freeipmi-ipmidetect.ipmidetectd.default --- freeipmi-1.6.3/debian/freeipmi-ipmidetect.ipmidetectd.default 2019-02-02 15:50:10.0 +0100 +++ freeipmi-1.6.3/debian/freeipmi-ipmidetect.ipmidetectd.default 1970-01-01 01:00:00.0 +0100 @@ -1,5 +0,0 @@ -# -# Set to 'yes' after you have configured ipmidetectd. -# See ipmidetectd.conf(5) manpage for more information. -# -RUN=no diff -Nru freeipmi-1.6.3/debian/patches/deb_bmc-watchdog_noRUN freeipmi-1.6.3/debian/patches/deb_bmc-watchdog_noRUN --- freeipmi-1.6.3/debian/patches/deb_bmc-watchdog_noRUN2019-02-02 15:50:10.0 +0100 +++ freeipmi-1.6.3/debian/patches/deb_bmc-watchdog_noRUN1970-01-01 01:00:00.0 +0100 @@ -1,12 +0,0 @@ -From: Yaroslav Halchenko -Subject: to be able to condition use of watchdog in the configuration -Vendor: Debian - a/etc/bmc-watchdog.sysconfig -+++ b/etc/bmc-watchdog.sysconfig -@@ -41,4 +41,5 @@ - # - # For the remaining options, consult man bmc-watchdog - # -+RUN=no - OPTIONS="-d -u 4 -p 0 -a 1 -F -P -L -S -O -i 900 -e 60" diff -Nru freeipmi-1.6.3/debian/patches/series freeipmi-1.6.3/debian/patches/series --- freeipmi-1.6.3/debian/patches/series2019-02-02 15:50:10.0 +0100 +++ freeipmi-1.6.3/debian/patches/series1970-01-01 01:00:00.0 +0100 @@ -1 +0,0 @@ -deb_bmc-watchdog_noRUN diff -Nru freeipmi-1.6.3/debian/rules freeipmi-1.6.3/debian/rules --- freeipmi-1.6.3/debian/rules 2019-02-02 15:50:10.0 +0100 +++ freeipmi-1.6.3/debian/rules 2019-02-23 14:03:32.0 +0100 @@ -39,9 +39,9 @@ : # Use Debian specific init files with "matching" names dh_installinit -pfreeipmi-bmc-watchdog \ ---name=bmc-watchdog +--name=bmc-watchdog --no-enable --no-start dh_installinit -pfreeipmi-ipmidetect \ ---name=ipmidetectd +--name=ipmidetectd --no-enable --no-start dh_installinit -pfreeipmi-ipmiseld \ --name=ipmiseld signature.asc Description: PGP signature
Processed: tagging 922404
Processing commands for cont...@bugs.debian.org: > tags 922404 + pending Bug #922404 [freeipmi] freeipmi install fails Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 922404: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922404 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#922513: capstone: Block from entering testing
Hi, On Sun, Feb 17, 2019 at 01:10:18PM +0100, Hilko Bengen wrote: > I recently uploaded the capstone4 as a separate source package, assuming > that this would not have consequences in testing. As I was told on > #debian-release, that is not the case because the capstone4 package > takes over python-capstone, python3-capstone, capstone-tool and a > subsequent capstone migration to testing would cause removal of those > binary packages from testing. > > This bug is intended to prevent such a migration. The change should really be reverted and 3.0.5 should be re-uploaded to unstable (obviously using a version number that is higher than what's there now). Not only is this an uncoordinated transition long after the transition freeze, it will also block new uploads of qemu (which will be needed because of security issues). Thanks, Ivo
Bug#776246: Processed: severity of 776246 is grave
Control: tags -1 buster-ignore Hi, On Tue, Feb 19, 2019 at 10:18:19PM +0100, Moritz Mühlenhoff wrote: > On Wed, Feb 20, 2019 at 02:12:55AM +0500, Andrey Rahmatullin wrote: > > On Tue, Feb 19, 2019 at 10:00:34PM +0100, Moritz Mühlenhoff wrote: > > > If a transition (even though it's marginal in size) isn't an option at > > > this > > > point > > That's not for me to decide. Should we ask the RT? > > Sounds like a plan, can you please ping them? This looks like something that will have to wait till after the release. Thanks, Ivo
Processed: Re: Processed: severity of 776246 is grave
Processing control commands: > tags -1 buster-ignore Bug #776246 [librsync1] MD4 collision/preimage attacks (CVE-2014-8242) Added tag(s) buster-ignore. -- 776246: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776246 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 922404
Processing commands for cont...@bugs.debian.org: > tags 922404 + patch Bug #922404 [freeipmi] freeipmi install fails Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 922404: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922404 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#922404: freeipmi install fails
Control: tag-1 + patch Installation fails because ipmidetectd has an empty default configuration. Fix simply avoids to enable and start the daemon that will need to be configured by hand. Antonio bug922404.debdiff Description: Binary data
Bug#919373: kannel: FTBFS with mariadb-10.3: gwlib/utils.c:602:14:
control: reassign -1 libmariadb-dev-compat control: affects -1 kannel control: retitle -1 libmariadb-dev-compat: lacks MYSQL_SERVER_VERSION causing FTBFS Quoting Jonas Smedegaard (2019-02-18 20:54:04) > Quoting Faustin Lammler (2019-01-17 22:17:07) > > Control: forwarded -1 https://redmine.kannel.org/issues/795 > > > > Hi, > > This seems to be a bug (see > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919395#36): > > > > > error: 'MYSQL_SERVER_VERSION' undeclared > > > > > > this looks like a bug. MYSQL_SERVER_VERSION is documented here: > > > https://dev.mysql.com/doc/refman/5.5/en/c-api-server-client-versions.html > > Thanks, Andreas and Faustin. > > In case others get confused same as me: This seems to be a but not in > kannel but in mariadb, in that it fails to implement the MySQL spec. ...and therefore reassigning to libmariadb-dev-compat. - 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
Processed: Re: Bug#919373: kannel: FTBFS with mariadb-10.3: gwlib/utils.c:602:14:
Processing control commands: > reassign -1 libmariadb-dev-compat Bug #919373 [src:kannel] kannel: FTBFS with mariadb-10.3: gwlib/utils.c:602:14: error: 'MYSQL_SERVER_VERSION' undeclared Bug reassigned from package 'src:kannel' to 'libmariadb-dev-compat'. No longer marked as found in versions kannel/1.4.5-2. Ignoring request to alter fixed versions of bug #919373 to the same values previously set > affects -1 kannel Bug #919373 [libmariadb-dev-compat] kannel: FTBFS with mariadb-10.3: gwlib/utils.c:602:14: error: 'MYSQL_SERVER_VERSION' undeclared Added indication that 919373 affects kannel > retitle -1 libmariadb-dev-compat: lacks MYSQL_SERVER_VERSION causing FTBFS Bug #919373 [libmariadb-dev-compat] kannel: FTBFS with mariadb-10.3: gwlib/utils.c:602:14: error: 'MYSQL_SERVER_VERSION' undeclared Changed Bug title to 'libmariadb-dev-compat: lacks MYSQL_SERVER_VERSION causing FTBFS' from 'kannel: FTBFS with mariadb-10.3: gwlib/utils.c:602:14: error: 'MYSQL_SERVER_VERSION' undeclared'. -- 919373: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919373 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#920030: marked as done (python3-pygame: ships headers in /usr/include/python3.7/)
Your message dated Sat, 23 Feb 2019 12:04:56 + with message-id and subject line Bug#920030: fixed in pygame 1.9.4.post1+dfsg-3 has caused the Debian Bug report #920030, regarding python3-pygame: ships headers in /usr/include/python3.7/ 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.) -- 920030: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920030 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-pygame Version: 1.9.4.post1+dfsg-2 Severity: serious Hi, your package ships the header file(s): /usr/include/python3.7/pygame/_camera.h /usr/include/python3.7/pygame/_pygame.h /usr/include/python3.7/pygame/_surface.h /usr/include/python3.7/pygame/bitmask.h /usr/include/python3.7/pygame/camera.h /usr/include/python3.7/pygame/fastevents.h /usr/include/python3.7/pygame/font.h /usr/include/python3.7/pygame/freetype.h /usr/include/python3.7/pygame/mask.h /usr/include/python3.7/pygame/mixer.h /usr/include/python3.7/pygame/pgarrinter.h /usr/include/python3.7/pygame/pgbufferproxy.h /usr/include/python3.7/pygame/pgcompat.h /usr/include/python3.7/pygame/pgopengl.h /usr/include/python3.7/pygame/pygame.h /usr/include/python3.7/pygame/scrap.h /usr/include/python3.7/pygame/surface.h but /usr/include/python3.7 is a symlink to python3.7m in libpython3.7-dev. This may result in silent file overwrites or depending on the unpacking order /usr/include/python3.7 being a directory in some cases, separating the headers into two independent trees. These header files must be shipped in /usr/include/python3.7m/ instead. Please talk to the python maintainers to find a proper solution for handling the packaging of python header files in a future-proof way. Cheers, Andreas --- End Message --- --- Begin Message --- Source: pygame Source-Version: 1.9.4.post1+dfsg-3 We believe that the bug you reported is fixed in the latest version of pygame, 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 920...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dominik George (supplier of updated pygame 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: Sat, 23 Feb 2019 12:10:31 +0100 Source: pygame Binary: python-pygame python-pygame-dbgsym python-pygame-doc python3-pygame python3-pygame-dbgsym Architecture: source amd64 all Version: 1.9.4.post1+dfsg-3 Distribution: unstable Urgency: high Maintainer: Debian Python Modules Team Changed-By: Dominik George Description: python-pygame - SDL bindings for games development (Python 2) python-pygame-doc - SDL bindings for games development in Python (documentation) python3-pygame - SDL bindings for games development (Python 3) Closes: 920030 Changes: pygame (1.9.4.post1+dfsg-3) unstable; urgency=high . * Move header files to correct location. (Closes: #920030) Checksums-Sha1: 4c72c32ee0e9074b70feb2b72e0df53674a0d885 2843 pygame_1.9.4.post1+dfsg-3.dsc fbdd9ab27c6d63aad35052fa494332d0bb4779ba 22084 pygame_1.9.4.post1+dfsg-3.debian.tar.xz 9ca1bdcf784f67767207c6db0ecf98e373dfb95c 15704 pygame_1.9.4.post1+dfsg-3_amd64.buildinfo c32113ca191eb3ca67055e0ab2abba791bd34a91 1304892 python-pygame-dbgsym_1.9.4.post1+dfsg-3_amd64.deb 2364778697917199c7a91c9c397b335502d410ab 1580780 python-pygame-doc_1.9.4.post1+dfsg-3_all.deb 291c6bae1dcb62bef7fb382d6d6de74d0fb61ae3 593620 python-pygame_1.9.4.post1+dfsg-3_amd64.deb 8313d118aaa3d5af7023c1a0d4868759423b447b 1440416 python3-pygame-dbgsym_1.9.4.post1+dfsg-3_amd64.deb a0549b8be5f59cec8369351176b2a686cb7915a2 595564 python3-pygame_1.9.4.post1+dfsg-3_amd64.deb Checksums-Sha256: 08444d3fc743cd62c7880552b580c4f38751a1dcecb8d6e742982c5bc0a6e588 2843 pygame_1.9.4.post1+dfsg-3.dsc d442ad63b2951b425e138c036cf38a4be655db509601add71a546236d0156667 22084 pygame_1.9.4.post1+dfsg-3.debian.tar.xz ce1ed09c5aed4bd64184a7851af4f09291ef7cefd23ccf63fe106aaad5ae5f11 15704 pygame_1.9.4.post1+dfsg-3_amd64.buildinfo f0f535073388900e5144d6d28e09dbb926dead34c97bf3ec6760f3d07158776c 1304892 python-pygame-dbgsym_1.9.4.post1+dfsg-3_amd64.deb de145d2d12f8a8287864be5f6cde06fc94031edab125a835f5cd7bb934e6f65f 1580780 python-py
Bug#859224: netkit-ftp-ssl: Please migrate to openssl1.1 in Buster
Sebastian Andrzej Siewior wrote... > Do you still plan to address this or should a RM be filled? The window > for Buster has been closed imho. Yes, and yes :( Patches are more or less done but I haven't got the tuits for the last checks unfortunatly. Unless I'm done within the next 48h, I'll give up on these. Christoph, at the Bonn BSP signature.asc Description: PGP signature
Bug#859553: marked as done (pidentd: Please migrate to openssl1.1 in buster)
Your message dated Sat, 23 Feb 2019 11:35:17 + with message-id and subject line Bug#922997: Removed package(s) from unstable has caused the Debian Bug report #859553, regarding pidentd: Please migrate to openssl1.1 in buster 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.) -- 859553: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859553 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pidentd Version: 3.0.19.ds1-7 Severity: important Control: block 827061 by -1 Hi, OpenSSL 1.1.0 is about to released. During a rebuild of all packages using OpenSSL this package fail to build. A log of that build can be found at: https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/pidentd_3.0.19.ds1-7_amd64-20160529-1508 On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of the reasons why it might fail. There are also updated man pages at https://www.openssl.org/docs/manmaster/ that should contain useful information. There is a libssl-dev package available in experimental that contains a recent snapshot, I suggest you try building against that to see if everything works. If you have problems making things work, feel free to contact us. Kurt --- End Message --- --- Begin Message --- Version: 3.0.19.ds1-8+rm Dear submitter, as the package pidentd has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/922997 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#918403: marked as done (ruby-rack-pjax FTBFS with ruby-rack 2.0.6-2)
Your message dated Sat, 23 Feb 2019 11:31:39 +
with message-id
and subject line Bug#922837: Removed package(s) from unstable
has caused the Debian Bug report #918403,
regarding ruby-rack-pjax FTBFS with ruby-rack 2.0.6-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.)
--
918403: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918403
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-rack-pjax
Version: 0.7.0-2
Severity: serious
Tags: ftbfs buster sid
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ruby-rack-pjax.html
...
┌──┐
│ Run tests for ruby2.5 from debian/ruby-tests.rake│
└──┘
RUBYLIB=/build/1st/ruby-rack-pjax-0.7.0/debian/ruby-rack-pjax/usr/lib/ruby/vendor_ruby:.
GEM_PATH=debian/ruby-rack-pjax/usr/share/rubygems-integration/all:/var/lib/gems/2.5.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all
ruby2.5 -S rake -f debian/ruby-tests.rake
/usr/bin/ruby2.5 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb
FFF
Failures:
1) Rack::Pjax a pjaxified app, upon receiving a pjax-request should return
the title-tag in the body
Failure/Error: {'Content-Type' => 'text/plain', 'Content-Length' =>
Rack::Utils.bytesize(body).to_s},
NoMethodError:
undefined method `bytesize' for Rack::Utils:Module
# ./spec/rack/pjax_spec.rb:14:in `block in generate_app'
# ./lib/rack/pjax.rb:12:in `call'
# ./spec/rack/pjax_spec.rb:28:in `block (3 levels) in '
2) Rack::Pjax a pjaxified app, upon receiving a pjax-request should return
the inner-html of the pjax-container in the body
Failure/Error: {'Content-Type' => 'text/plain', 'Content-Length' =>
Rack::Utils.bytesize(body).to_s},
NoMethodError:
undefined method `bytesize' for Rack::Utils:Module
# ./spec/rack/pjax_spec.rb:14:in `block in generate_app'
# ./lib/rack/pjax.rb:12:in `call'
# ./spec/rack/pjax_spec.rb:35:in `block (3 levels) in '
3) Rack::Pjax a pjaxified app, upon receiving a pjax-request should return
the inner-html of the custom pjax-container in the body
Failure/Error: {'Content-Type' => 'text/plain', 'Content-Length' =>
Rack::Utils.bytesize(body).to_s},
NoMethodError:
undefined method `bytesize' for Rack::Utils:Module
# ./spec/rack/pjax_spec.rb:14:in `block in generate_app'
# ./lib/rack/pjax.rb:12:in `call'
# ./spec/rack/pjax_spec.rb:42:in `block (3 levels) in '
4) Rack::Pjax a pjaxified app, upon receiving a pjax-request should handle
self closing tags with HTML5 elements
Failure/Error: {'Content-Type' => 'text/plain', 'Content-Length' =>
Rack::Utils.bytesize(body).to_s},
NoMethodError:
undefined method `bytesize' for Rack::Utils:Module
# ./spec/rack/pjax_spec.rb:14:in `block in generate_app'
# ./lib/rack/pjax.rb:12:in `call'
# ./spec/rack/pjax_spec.rb:49:in `block (3 levels) in '
5) Rack::Pjax a pjaxified app, upon receiving a pjax-request should handle
nesting of elements inside anchor tags
Failure/Error: {'Content-Type' => 'text/plain', 'Content-Length' =>
Rack::Utils.bytesize(body).to_s},
NoMethodError:
undefined method `bytesize' for Rack::Utils:Module
# ./spec/rack/pjax_spec.rb:14:in `block in generate_app'
# ./lib/rack/pjax.rb:12:in `call'
# ./spec/rack/pjax_spec.rb:57:in `block (3 levels) in '
6) Rack::Pjax a pjaxified app, upon receiving a pjax-request should handle
html5 br tags correctly
Failure/Error: {'Content-Type' => 'text/plain', 'Content-Length' =>
Rack::Utils.bytesize(body).to_s},
NoMethodError:
undefined method `bytesize' for Rack::Utils:Module
# ./spec/rack/pjax_spec.rb:14:in `block in generate_app'
# ./lib/rack/pjax.rb:12:in `call'
# ./spec/rack/pjax_spec.rb:65:in `block (3 levels) in '
7) Rack::Pjax a pjaxified app, upon receiving a pjax-request should return
the correct Content Length
Failure/Error: {'Content-Type' => 'text/plain', 'Content-Length' =>
Rack::Utils.bytesize(body).to_s},
NoMethodError:
undefined method `bytesize' for Rack::Utils:Module
# ./spec/rack/pjax_spec.rb:14:in `block in generate_app'
# ./lib/rack/pjax.rb:12:in `call'
# ./spec/rack/pjax_spec.rb:71:in `block (3 levels) in '
8) Rack::Pjax a pjaxified app, upon receiving a pjax-request should retu
Bug#918260: marked as done (ruby-protected-attributes: Depends: ruby-activemodel (< 2:5.0) but 2:5.2.0+dfsg-2 is to be installed)
Your message dated Sat, 23 Feb 2019 11:32:37 + with message-id and subject line Bug#922868: Removed package(s) from unstable has caused the Debian Bug report #918260, regarding ruby-protected-attributes: Depends: ruby-activemodel (< 2:5.0) but 2:5.2.0+dfsg-2 is to be installed 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.) -- 918260: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918260 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-protected-attributes Version: 1.1.4-2 Severity: serious The following packages have unmet dependencies: ruby-protected-attributes : Depends: ruby-activemodel (< 2:5.0) but 2:5.2.0+dfsg-2 is to be installed --- End Message --- --- Begin Message --- Version: 1.1.4-2+rm Dear submitter, as the package ruby-protected-attributes has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/922868 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#912142: marked as done (ruby-capybara-screenshot FTBFS: test failure)
Your message dated Sat, 23 Feb 2019 11:32:05 +
with message-id
and subject line Bug#922843: Removed package(s) from unstable
has caused the Debian Bug report #912142,
regarding ruby-capybara-screenshot FTBFS: test failure
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.)
--
912142: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912142
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-capybara-screenshot
Version: 1.0.14-1
Severity: serious
Tags: ftbfs
Some recent change in unstable makes ruby-capybara-screenshot FTBFS:
https://tests.reproducible-builds.org/debian/history/ruby-capybara-screenshot.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ruby-capybara-screenshot.html
...
Failures:
1) Capybara::Screenshot::RSpec used with RSpec saves a screenshot on failure
Failure/Error: expect(expand_path('tmp/screenshot.html')).to_not
have_file_content('This is the root page')
expected "This is the root page" not to have file content: "This is the
root page"
# ./spec/rspec/rspec_spec.rb:54:in `block (3 levels) in '
Finished in 18.08 seconds (files took 0.92333 seconds to load)
83 examples, 1 failure
Failed examples:
rspec ./spec/rspec/rspec_spec.rb:44 # Capybara::Screenshot::RSpec used with
RSpec saves a screenshot on failure
/usr/bin/ruby2.5 /usr/bin/rspec ./spec/cucumber/cucumber_spec.rb
./spec/rspec/rspec_spec.rb ./spec/unit/base_reporter_spec.rb
./spec/unit/capybara-screenshot_rspec_spec.rb
./spec/unit/capybara-screenshot_spec.rb ./spec/unit/capybara_spec.rb
./spec/unit/pruner_spec.rb
./spec/unit/rspec_reporters/html_embed_reporter_spec.rb
./spec/unit/rspec_reporters/html_link_reporter_spec.rb
./spec/unit/rspec_reporters/text_reporter_spec.rb
./spec/unit/rspec_reporters/textmate_link_reporter_spec.rb
./spec/unit/saver_spec.rb --format documentation failed
ERROR: Test "ruby2.5" failed. Exiting.
dh_auto_install: dh_ruby --install
/build/1st/ruby-capybara-screenshot-1.0.14/debian/ruby-capybara-screenshot
returned exit code 1
make: *** [debian/rules:6: binary] Error 1
--- End Message ---
--- Begin Message ---
Version: 1.0.14-1+rm
Dear submitter,
as the package ruby-capybara-screenshot has just been removed from the Debian
archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/922843
The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.
Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#900178: marked as done (ruby-rails-admin: CVE-2017-12098)
Your message dated Sat, 23 Feb 2019 11:31:10 + with message-id and subject line Bug#922836: Removed package(s) from unstable has caused the Debian Bug report #900178, regarding ruby-rails-admin: CVE-2017-12098 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.) -- 900178: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900178 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-rails-admin Version: 0.8.1+dfsg-3 Severity: grave Tags: patch security upstream Justification: user security hole Forwarded: https://github.com/sferik/rails_admin/issues/2985 Hi, The following vulnerability was published for ruby-rails-admin. CVE-2017-12098[0]: | An exploitable cross site scripting (XSS) vulnerability exists in the | add filter functionality of the rails_admin rails gem version 1.2.0. A | specially crafted URL can cause an XSS flaw resulting in an attacker | being able to execute arbitrary javascript on the victim's browser. An | attacker can phish an authenticated user to trigger this | vulnerability. 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-2017-12098 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-12098 [1] https://github.com/sferik/rails_admin/issues/2985 [2] https://github.com/sferik/rails_admin/commit/44f09ed72b5e0e917a5d61bd89c48d97c494b41c Regards, Salvatore --- End Message --- --- Begin Message --- Version: 0.8.1+dfsg-3+rm Dear submitter, as the package ruby-rails-admin has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/922836 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#903855: marked as done (CVE-2016-10522)
Your message dated Sat, 23 Feb 2019 11:31:10 + with message-id and subject line Bug#922836: Removed package(s) from unstable has caused the Debian Bug report #903855, regarding CVE-2016-10522 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.) -- 903855: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903855 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ruby-rails-admin Severity: grave Tags: security http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-10522 --- End Message --- --- Begin Message --- Version: 0.8.1+dfsg-3+rm Dear submitter, as the package ruby-rails-admin has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/922836 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#891716: marked as done (ruby-rails-admin FTBFS: Could not find 'kaminari' (~> 0.14) - did find: [kaminari-1.0.1])
Your message dated Sat, 23 Feb 2019 11:31:10 + with message-id and subject line Bug#922836: Removed package(s) from unstable has caused the Debian Bug report #891716, regarding ruby-rails-admin FTBFS: Could not find 'kaminari' (~> 0.14) - did find: [kaminari-1.0.1] 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.) -- 891716: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891716 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-rails-admin Version: 0.8.1+dfsg-3 Severity: serious Tags: buster sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ruby-rails-admin.html ... ┌──┐ │ Checking Rubygems dependency resolution on ruby2.3 │ └──┘ GEM_PATH=debian/ruby-rails-admin/usr/share/rubygems-integration/all:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all ruby2.3 -e gem\ \"rails_admin\" /usr/lib/ruby/2.3.0/rubygems/dependency.rb:319:in `to_specs': Could not find 'kaminari' (~> 0.14) - did find: [kaminari-1.0.1] (Gem::LoadError) --- End Message --- --- Begin Message --- Version: 0.8.1+dfsg-3+rm Dear submitter, as the package ruby-rails-admin has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/922836 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#918164: Broken with Thunderbird 60
Hello Matthias, On Thu, Jan 03, 2019 at 11:21:19PM +0100, Moritz Muehlenhoff wrote: > The plugin is broken with Thunderbird 60 in stretch and sid, after > installation > it's disabled and only prints "Timeline is incompatible with Thunderbird > 60.4". > > TB 60 was uploaded to stretch over two months ago (and three months ago to > sid), > given that noone filed a bug so far, it makes me wonder whether this package > is > used at all... currently the package xul-ext-timeline is useless as it isn't usable in any release of Debian any more. Upstream seems to have given up the development not only this extension for Thunderbird. https://addons.thunderbird.net/en-us/thunderbird/user/teester/ The last supported Thunderbird version is mainly on all of the provided extension staying at 31.*. We should remove this package completely from the Debian archives. Regards Carsten
Processed: Re: Bug#913467: nvidia-graphics-drivers: CVE‑2018‑6260: access to application data processed on the GPU through a side channel exposed by the GPU performance counters
Processing control commands: > severity -1 important Bug #913467 [src:nvidia-graphics-drivers] nvidia-graphics-drivers: CVE‑2018‑6260: access to application data processed on the GPU through a side channel exposed by the GPU performance counters Severity set to 'important' from 'serious' -- 913467: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913467 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#913467: nvidia-graphics-drivers: CVE‑2018‑6260: access to application data processed on the GPU through a side channel exposed by the GPU performance counters
Control: severity -1 important Hello, Andreas Beckmann, le mer. 20 févr. 2019 12:41:10 +0100, a ecrit: > On 2019-02-19 17:42, Moritz Muehlenhoff wrote: > >> Unfortunately we have no idea - NVIDIA's security tracker was never > >> updated after the initial mention of the CVE: > >> > >> https://nvidia.custhelp.com/app/answers/detail/a_id/4738 > > > > Ack, we can revisit once more information is available. > > There was an upstream changelog entries that appeared for the 340.xx > series in the 410.93 release: > > - Added a new kernel module parameter, > NVreg_RestrictProfilingToAdminUsers, > to allow restricting the use of GPU performance counters to system > administrators only. > > but that was not announced afaik. That change should be in sid (410.xx) > and experimental (415.xx) (but there haven't been 340/390 releases > since). But the entry is again missing from the 418.xx beta upstream > changelog, which could either indicate a missing upstream merge or a > revert ... At least in the meanwhile users have a way to avoid the issue, so downgrading the bug severity. (personally, I believe users shouldn't ever trust these GPUs for security, and it's not a question of software) Samuel
Bug#896189: marked as done (update-alternatives: error: /var/lib/dpkg/alternatives/mpi corrupt: slave link same as main link /usr/bin/mpicc)
Your message dated Sat, 23 Feb 2019 10:44:19 + with message-id and subject line Bug#896189: fixed in mpich 3.3-2 has caused the Debian Bug report #896189, regarding update-alternatives: error: /var/lib/dpkg/alternatives/mpi corrupt: slave link same as main link /usr/bin/mpicc 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.) -- 896189: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896189 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: openmpi-bin Version: 3.0.1-6 Severity: serious Control: affects -1 src:netpipe https://buildd.debian.org/status/package.php?p=netpipe&suite=sid ... Setting up libncurses5:i386 (6.1-1) ... Setting up readline-common (7.0-3) ... Setting up libevent-2.1-6:i386 (2.1.8-stable-4) ... Setting up libevent-core-2.1-6:i386 (2.1.8-stable-4) ... Setting up libarchive-zip-perl (1.60-1) ... Setting up libgfortran4:i386 (7.3.0-16) ... Setting up libtimedate-perl (2.3000-2) ... Setting up libsigsegv2:i386 (2.12-2) ... Setting up libreadline7:i386 (7.0-3) ... Setting up libnuma1:i386 (2.0.11-2.1) ... Setting up groff-base (1.22.3-10) ... Setting up libglib2.0-0:i386 (2.56.1-2) ... No schema files found: doing nothing. Setting up libtinfo-dev:i386 (6.1-1) ... Setting up gettext-base (0.19.8.1-6) ... Setting up libpipeline1:i386 (1.5.0-1) ... Setting up m4 (1.4.18-1) ... Setting up libicu57:i386 (57.1-9) ... Setting up libbsd0:i386 (0.8.7-1) ... Setting up libxml2:i386 (2.9.4+dfsg1-6.1) ... Setting up libmagic-mgc (1:5.32-2) ... Setting up libmagic1:i386 (1:5.32-2) ... Setting up libcroco3:i386 (0.6.12-2) ... Setting up libpsm-infinipath1 (3.3+20.604758e7-5) ... update-alternatives: using /usr/lib/libpsm1/libpsm_infinipath.so.1.16 to provide /usr/lib/i386-linux-gnu/libpsm_infinipath.so.1 (libpsm_infinipath.so.1) in auto mode Setting up libssl1.0.2:i386 (1.0.2o-1) ... Setting up libevent-pthreads-2.1-6:i386 (2.1.8-stable-4) ... Setting up openmpi-common (3.0.1-6) ... Processing triggers for libc-bin (2.27-3) ... Setting up autotools-dev (20180224.1) ... Setting up libltdl7:i386 (2.4.6-2.1) ... Setting up libpvm3:i386 (3.4.6-1+b3) ... Setting up libgfortran-7-dev:i386 (7.3.0-16) ... Setting up libreadline-dev:i386 (7.0-3) ... Setting up libpciaccess0:i386 (0.14-1) ... Setting up gfortran-7 (7.3.0-16) ... Setting up libnuma-dev:i386 (2.0.11-2.1) ... Setting up ocl-icd-libopencl1:i386 (2.2.12-1) ... Setting up libkeyutils1:i386 (1.5.9-9.2) ... Setting up bsdmainutils (11.1.2) ... update-alternatives: using /usr/bin/bsd-write to provide /usr/bin/write (write) in auto mode update-alternatives: using /usr/bin/bsd-from to provide /usr/bin/from (from) in auto mode Setting up libnl-3-200:i386 (3.2.27-2) ... Setting up autopoint (0.19.8.1-6) ... Setting up libfile-stripnondeterminism-perl (0.041-1) ... Setting up libedit2:i386 (3.1-20170329-1) ... Setting up gfortran (4:7.3.0-3) ... update-alternatives: using /usr/bin/gfortran to provide /usr/bin/f95 (f95) in auto mode update-alternatives: using /usr/bin/gfortran to provide /usr/bin/f77 (f77) in auto mode Setting up libmpich12:i386 (3.3~b2-3) ... Setting up libltdl-dev:i386 (2.4.6-2.1) ... Setting up gettext (0.19.8.1-6) ... Setting up libnl-route-3-200:i386 (3.2.27-2) ... Setting up autoconf (2.69-11) ... Setting up file (1:5.32-2) ... Setting up libhwloc5:i386 (1.11.10-1) ... Setting up libkrb5support0:i386 (1.16-2) ... Setting up liblam4 (7.1.4-3.1) ... Setting up libhwloc-plugins (1.11.10-1) ... Setting up intltool-debian (0.35.0+20060710.4) ... Setting up lam4-dev (7.1.4-3.1) ... update-alternatives: using /usr/include/lam to provide /usr/include/mpi (mpi) in auto mode update-alternatives: using /usr/share/man/man3/MPI_Comm_set_name_lam4-dev.3.gz to provide /usr/share/man/man3/MPI_Comm_set_name.3.gz (MPI_Comm_set_name.3.gz) in auto mode Setting up automake (1:1.15.1-3.1) ... update-alternatives: using /usr/bin/automake-1.15 to provide /usr/bin/automake (automake) in auto mode Setting up man-db (2.8.3-2) ... Not building database; man-db/auto-update is not 'true'. Setting up libtool (2.4.6-2.1) ... Setting up hwloc-nox (1.11.10-1) ... Setting up libibverbs1:i386 (17.1-1) ... Setting up mpich (3.3~b2-3) ... update-alternatives: renaming mpi link from /usr/include/mpi to /usr/bin/mpicc update-alternatives: using /usr/bin/mpicc.mpich to provide /usr/bin/mpicc (mpi) in auto mode update-alternatives: using /usr/bin/mpirun.mpich to provide /usr/bin/mpirun (mpirun) in auto mode Setting up libk5crypto3:i386 (1.16-2) ... Setting up po-debconf (1.0.20) ... Setting up libhwloc-dev:i386 (1.11.10-1) ... Setting up l
Bug#896644: marked as done (openmpi-bin: postinst script fails)
Your message dated Sat, 23 Feb 2019 10:44:19 + with message-id and subject line Bug#896189: fixed in mpich 3.3-2 has caused the Debian Bug report #896189, regarding openmpi-bin: postinst script fails 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.) -- 896189: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896189 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: openmpi-bin Severity: serious Version: 3.0.1-7 Dear maintainer, With the latest openmpi, I would get the following result when running "apt dist-upgrade": % LANG=C sudo apt install -f Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded. 2 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Setting up openmpi-bin (3.0.1-7) ... dpkg: error processing package openmpi-bin (--configure): installed openmpi-bin package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of libopenmpi-dev:amd64: libopenmpi-dev:amd64 depends on openmpi-bin (>= 3.0.0-1); however: Package openmpi-bin is not configured yet. dpkg: error processing package libopenmpi-dev:amd64 (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: openmpi-bin libopenmpi-dev:amd64 E: Sub-process /usr/bin/dpkg returned an error code (1) -- Regards, Boyuan Yang --- End Message --- --- Begin Message --- Source: mpich Source-Version: 3.3-2 We believe that the bug you reported is fixed in the latest version of mpich, 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 896...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alastair McKinstry (supplier of updated mpich 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: Fri, 22 Feb 2019 16:45:42 + Source: mpich Binary: libmpich-dev libmpich12 libmpich12-dbgsym mpich mpich-dbgsym mpich-doc Architecture: source amd64 all Version: 3.3-2 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Alastair McKinstry Description: libmpich-dev - Development files for MPICH libmpich12 - Shared libraries for MPICH mpich - Implementation of the MPI Message Passing Interface standard mpich-doc - Documentation for MPICH Closes: 896189 Changes: mpich (3.3-2) unstable; urgency=medium . * Use dh_fortran_mod to install Fortran mod files in $fmoddir/mpich. * B-D on gfortran | fortran-compiler * Use f95, f77 aliases for Fortran compiler in d/rules * Standards-Version: 4.3.0 * Update alternatives handling. Closes: #896189 Checksums-Sha1: 886759f87e69857bebe7a740053a58d6a00e55bf 2502 mpich_3.3-2.dsc 4cd370415e93e5a68f905159ff1246a90283f62f 338536 mpich_3.3-2.debian.tar.xz 33154c962839d27ecd6c5d97f1856a07d270e894 1426728 libmpich-dev_3.3-2_amd64.deb 305e5d579de4d1ba4f2f47d8f2a502d19673aa37 11884104 libmpich12-dbgsym_3.3-2_amd64.deb 18ae064fb5079090dfca9dc26ab1d1d5d24d2a11 1167756 libmpich12_3.3-2_amd64.deb 8d832cb8f480517367db441194a9502a7b8d77f8 2784624 mpich-dbgsym_3.3-2_amd64.deb c5795fc961a34152232e3bdc3b304c634652656e 692768 mpich-doc_3.3-2_all.deb 9a3d3bf548a5597380873d1a1aebb62ab317efa9 11219 mpich_3.3-2_amd64.buildinfo 30740909c4b4ff779ae4d0b25a921455ad7c2c07 410376 mpich_3.3-2_amd64.deb Checksums-Sha256: c03d435261278944180e4b6241210358bfe416b3f8f61802182ab2c6392280e8 2502 mpich_3.3-2.dsc 1664d594872d1c73d5ec8653b4ffbd542d2d634fdd9651ecdb5af325b1c602bc 338536 mpich_3.3-2.debian.tar.xz 7fea824d8ddd49fe633af3679d1c9e6f1ada042709675905ece45a6d645545f5 1426728 libmpich-dev_3.3-2_amd64.deb 90de2559a3cf74df0e81d27d636aa867593607906bcb4cffcc693322db66099c 11884104 libmpich12-dbgsym_3.3-2_amd64.deb 6b9e534ceed441c6b601750cfd936c7e491b2512859b7bc64e610e8d72908490 1167756 libmpich12_3.3-2_amd64.deb 13c408353b4c34c94296dfac8669d083b55187cfdefb3889e1b5796f85377fe9 2784624 mpich-dbgsym_3.3-2_amd64.deb 1cfee1c2d39c35b03c55b0d4b24a13550e6336b6ed626d9b257f0481d76dbd95 692768 mpich-doc_3.3-2_all.deb a4fe031948aa2748d025
Processed: severity of 909218 is important
Processing commands for cont...@bugs.debian.org: > severity 909218 important Bug #909218 [nvidia-graphics-drivers] nvidia-xconfig: Files section missing ModulePath entries break GLX upon installing libgl1-nvidia-glx (required by Steam) Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 909218: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909218 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 905309 is important
Processing commands for cont...@bugs.debian.org: > severity 905309 important Bug #905309 [nvidia-driver] nvidia-modeset: WARNING: GPU:0: Lost display notification (0:0x); continuing Severity set to 'important' from 'critical' > thanks Stopping processing here. Please contact me if you need assistance. -- 905309: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905309 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
