Bug#973085: pyrandom2: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.9 3.8" returned exit code 13
Fedora have decided to disable the failing part of that test.[1] Python docs for the tested function now state "Changed in version 3.9: This method now accepts zero for k."[2] [1] https://src.fedoraproject.org/rpms/python-random2/blob/master/f/python-random2.spec#_39 [2] https://docs.python.org/3/library/random.html#random.getrandbits
Bug#973906: gevent-websocket's autopkg tests fail
Package: src:gevent-websocket Version: 0.10.1-3 Severity: serious Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: python3.9 gevent-websocket's autopkg tests fail: [...] autopkgtest [12:02:51]: test command1: python3 -c "import geventwebsocket" autopkgtest [12:02:51]: test command1: [--- :219: RuntimeWarning: greenlet.greenlet size changed, may indicate binary incompatibility. Expected 144 from C header, got 152 from PyObject :219: RuntimeWarning: greenlet.greenlet size changed, may indicate binary incompatibility. Expected 144 from C header, got 152 from PyObject :219: RuntimeWarning: greenlet.greenlet size changed, may indicate binary incompatibility. Expected 144 from C header, got 152 from PyObject :219: RuntimeWarning: greenlet.greenlet size changed, may indicate binary incompatibility. Expected 144 from C header, got 152 from PyObject :219: RuntimeWarning: greenlet.greenlet size changed, may indicate binary incompatibility. Expected 144 from C header, got 152 from PyObject :219: RuntimeWarning: greenlet.greenlet size changed, may indicate binary incompatibility. Expected 144 from C header, got 152 from PyObject autopkgtest [12:02:51]: test command1: ---] command1 FAIL stderr: :219: RuntimeWarning: greenlet.greenlet size changed, may indicate binary incompatibility. Expected 144 from C header, got 152 from PyObject autopkgtest [12:02:52]: test command1: - - - - - - - - - - results - - - - - - - - - - autopkgtest [12:02:52]: test command1: - - - - - - - - - - stderr - - - - - - - - - - :219: RuntimeWarning: greenlet.greenlet size changed, may indicate binary incompatibility. Expected 144 from C header, got 152 from PyObject :219: RuntimeWarning: greenlet.greenlet size changed, may indicate binary incompatibility. Expected 144 from C header, got 152 from PyObject :219: RuntimeWarning: greenlet.greenlet size changed, may indicate binary incompatibility. Expected 144 from C header, got 152 from PyObject :219: RuntimeWarning: greenlet.greenlet size changed, may indicate binary incompatibility. Expected 144 from C header, got 152 from PyObject :219: RuntimeWarning: greenlet.greenlet size changed, may indicate binary incompatibility. Expected 144 from C header, got 152 from PyObject :219: RuntimeWarning: greenlet.greenlet size changed, may indicate binary incompatibility. Expected 144 from C header, got 152 from PyObject autopkgtest [12:02:52]: summary command1 FAIL stderr: :219: RuntimeWarning: greenlet.greenlet size changed, may indicate binary incompatibility. Expected 144 from C header, got 152 from PyObject
Bug#973905: python-typing-inspect's autopkg test fails
Package: src:python-typing-inspect Version: 0.6.0-1 Severity: serious Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: python3.9 python-typing-inspect's autopkg test fails: autopkgtest [14:48:01]: test unittests: [--- === python3.9 === /tmp/autopkgtest-lxc.bhraj9yn/downtmp/build.0gO/src/debian/tests/unittests: 11: python3.9: not found autopkgtest [14:48:01]: test unittests: ---] autopkgtest [14:48:01]: test unittests: - - - - - - - - - - results - - - - - - - - - - unittestsFAIL non-zero exit status 127 autopkgtest [14:48:01]: summary unittestsFAIL non-zero exit status 127
Bug#973159: marked as done (ruby-joiner: FTBFS: ERROR: Test "ruby2.7" failed: Failure/Error: require 'bundler/setup')
Your message dated Sat, 07 Nov 2020 01:42:00 +0100
with message-id <8b824ea3f34ca0a3e3d4a9897bf082cd78d277ec.ca...@debian.org>
and subject line FTBFS fixed by closing #972702
has caused the Debian Bug report #973159,
regarding ruby-joiner: FTBFS: ERROR: Test "ruby2.7" failed: Failure/Error:
require 'bundler/setup'
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.)
--
973159: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973159
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-joiner
Version: 0.5.0-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> Failure/Error: require 'bundler/setup'
>
> Bundler::GemNotFound:
> Could not find gem 'sqlite3 (~> 1.4)' in any of the gem sources listed in
> your Gemfile.
> #
> /usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler.rb:149:in
> `setup'
> # ./spec/spec_helper.rb:2:in `'
> # ./spec/acceptance/paths_spec.rb:1:in `'
> No examples found.
>
>
> Finished in 0.4 seconds (files took 0.17979 seconds to load)
> 0 examples, 0 failures, 2 errors occurred outside of examples
>
> /usr/bin/ruby2.7
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib
> /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/exe/rspec
> --pattern spec/\*\*\{,/\*/\*\*\}/\*_spec.rb failed
> ERROR: Test "ruby2.7" failed:
The full build log is available from:
http://qa-logs.debian.net/2020/10/27/ruby-joiner_0.5.0-2_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
This FTBFS has been fixed by the recent binNMUs after closing #972702
(dependency resolution issue with updated ruby-bundler).
Regards, Daniel
--
Regards,
Daniel Leidert | https://www.wgdd.de/
GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D
GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78
If you like my work consider sponsoring me via
https://www.patreon.com/join/dleidert
signature.asc
Description: This is a digitally signed message part
--- End Message ---
Bug#973155: marked as done (ruby-puma-worker-killer: FTBFS: ERROR: Test "ruby2.7" failed.)
Your message dated Sat, 07 Nov 2020 01:42:00 +0100 with message-id <8b824ea3f34ca0a3e3d4a9897bf082cd78d277ec.ca...@debian.org> and subject line FTBFS fixed by closing #972702 has caused the Debian Bug report #973155, regarding ruby-puma-worker-killer: FTBFS: ERROR: Test "ruby2.7" 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.) -- 973155: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973155 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-puma-worker-killer Version: 0.1.1-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201027 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/ruby2.7 /usr/bin/gem2deb-test-runner > > ┌──┐ > │ Checking Rubygems dependency resolution on ruby2.7 > │ > └──┘ > > GEM_PATH=/<>/debian/ruby-puma-worker-killer/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/2.7.0:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0 > ruby2.7 -e gem\ \"puma_worker_killer\" > > ┌──┐ > │ Run tests for ruby2.7 from debian/ruby-tests.rake > │ > └──┘ > > RUBYLIB=. > GEM_PATH=/<>/debian/ruby-puma-worker-killer/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/2.7.0:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0 > ruby2.7 -S rake -f debian/ruby-tests.rake > /usr/bin/ruby2.7 -w -I"test" > "/usr/share/rubygems-integration/all/gems/rake-13.0.1/lib/rake/rake_test_loader.rb" > "test/puma_worker_killer_test.rb" "test/test_helper.rb" -v > Loaded suite > /usr/share/rubygems-integration/all/gems/rake-13.0.1/lib/rake/rake_test_loader > Started > PumaWorkerKillerTest: > test_kills_large_app: > /usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/resolver.rb:59:in > `rescue in start': Bundler could not find compatible versions for gem > "puma": (Bundler::VersionConflict) > In Gemfile: > puma_worker_killer was resolved to 0.1.1, which depends on > puma (>= 2.7, < 5) > > Could not find gem 'puma (>= 2.7, < 5)', which is required by gem > 'puma_worker_killer', in any of the sources. > from > /usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/resolver.rb:45:in > `start' > from > /usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/resolver.rb:22:in > `resolve' > from > /usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/definition.rb:264:in > `resolve' > from > /usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/definition.rb:175:in > `specs' > from > /usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/definition.rb:243:in > `specs_for' > from > /usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/definition.rb:231:in > `requested_specs' > from > /usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/runtime.rb:91:in > `block in definition_method' > from > /usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/runtime.rb:20:in > `setup' > from > /usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler.rb:149:in > `setup' > from > /usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/setup.rb:20:in > `block in ' > from > /usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/ui/shell.rb:136:in > `with_level' > from > /usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/ui/shell.rb:88:in > `silence' > from > /usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/setup.rb:20:in > `' > fro
Bug#973156: marked as done (sketch: FTBFS: Error: /undefined in .setopacityalpha)
Your message dated Sat, 07 Nov 2020 03:03:44 +
with message-id
and subject line Bug#973156: fixed in sketch 1:0.3.7-12
has caused the Debian Bug report #973156,
regarding sketch: FTBFS: Error: /undefined in .setopacityalpha
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.)
--
973156: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973156
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sketch
Version: 1:0.3.7-11
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[2]: Entering directory '/<>'
> gcc -O1 -g -Wall -Wall -g -O2 -Wdate-time -D_FORTIFY_SOURCE=2 -c -o bsp.o
> bsp.c
> gcc -O1 -g -Wall -Wall -g -O2 -Wdate-time -D_FORTIFY_SOURCE=2 -c -o
> cmdline.o cmdline.c
> gcc -O1 -g -Wall -Wall -g -O2 -Wdate-time -D_FORTIFY_SOURCE=2 -c -o emit.o
> emit.c
> gcc -O1 -g -Wall -Wall -g -O2 -Wdate-time -D_FORTIFY_SOURCE=2 -c -o error.o
> error.c
> gcc -O1 -g -Wall -Wall -g -O2 -Wdate-time -D_FORTIFY_SOURCE=2 -c -o expr.o
> expr.c
> expr.c: In function ‘to_integer’:
> expr.c:374:12: warning: variable ‘frac_part’ set but not used
> [-Wunused-but-set-variable]
> 374 | double frac_part, int_part;
> |^
> gcc -O1 -g -Wall -Wall -g -O2 -Wdate-time -D_FORTIFY_SOURCE=2 -c -o
> geometry.o geometry.c
> gcc -O1 -g -Wall -Wall -g -O2 -Wdate-time -D_FORTIFY_SOURCE=2 -c -o geomio.o
> geomio.c
> gcc -O1 -g -Wall -Wall -g -O2 -Wdate-time -D_FORTIFY_SOURCE=2 -c -o global.o
> global.c
> gcc -O1 -g -Wall -Wall -g -O2 -Wdate-time -D_FORTIFY_SOURCE=2 -c -o
> langver.o langver.c
> bison --defines --debug --report=all --yacc sketch.y
> gcc -O1 -g -Wall -Wall -g -O2 -Wdate-time -D_FORTIFY_SOURCE=2 -c -o main.o
> main.c
> gcc -O1 -g -Wall -Wall -g -O2 -Wdate-time -D_FORTIFY_SOURCE=2 -c -o
> memutil.o memutil.c
> gcc -O1 -g -Wall -Wall -g -O2 -Wdate-time -D_FORTIFY_SOURCE=2 -c -o opts.o
> opts.c
> gcc -O1 -g -Wall -Wall -g -O2 -Wdate-time -D_FORTIFY_SOURCE=2 -c -o scene.o
> scene.c
> geometry.c: In function ‘boxes_3d_intersect_p’:
> geometry.c:628:15: warning: array subscript 2 is above array bounds of
> ‘POINT_2D’ {aka ‘double[2]’} [-Warray-bounds]
> 628 | if (a->max[Z] < b->min[Z]) // a behind b
> | ~~^~~
> In file included from geometry.c:25:
> geometry.h:222:19: note: while referencing ‘max’
> 222 | POINT_2D min, max;
> | ^~~
> geometry.c:630:27: warning: array subscript 2 is above array bounds of
> ‘POINT_2D’ {aka ‘double[2]’} [-Warray-bounds]
> 630 | if (a->min[Z] > b->max[Z]) // a in front of b
> | ~~^~~
> In file included from geometry.c:25:
> geometry.h:222:19: note: while referencing ‘max’
> 222 | POINT_2D min, max;
> | ^~~
> gcc -O1 -g -Wall -Wall -g -O2 -Wdate-time -D_FORTIFY_SOURCE=2 -c -o symbol.o
> symbol.c
> gcc -O1 -g -Wall -Wall -g -O2 -Wdate-time -D_FORTIFY_SOURCE=2 -c -o y.tab.o
> y.tab.c
> gcc -O1 -g -Wall -Wall -g -O2 -Wdate-time -D_FORTIFY_SOURCE=2 -c -o lex.yy.o
> lex.yy.c
> gcc -O1 -g -Wall -o sketch bsp.o cmdline.o emit.o error.o expr.o geometry.o
> geomio.o global.o langver.o lex.yy.o main.o memutil.o opts.o scene.o symbol.o
> y.tab.o -lm
> make[2]: Leaving directory '/<>'
> cd Doc && perl make.pl linux examples
> ../sketch -D ex000 manexamples.sk > ex000.tex
> summary: no errors
> remark, node=1721 probe=98.8 swap=18 split=3 (in=6 out=9) ols=439/22
> remark, scene bb=(-1.804,-.797)(1.718,5.511)
> remark, writing 1724 objects
> latex example 'ex000-tmp.tex':
> This is pdfTeX, Version 3.14159265-2.6-1.40.21 (TeX Live 2020/Debian)
> (preloaded format=latex)
> restricted \write18 enabled.
> entering extended mode
> (./ex000-tmp.tex
> LaTeX2e <2020-02-02> patch level 5
> L3 programming layer <2020-09-24>
> (/usr/share/texlive/texmf-dist/tex/latex/base/article.cls
> Document Class: article 2019/12/20 v1.4l Standard LaTeX document class
> (/usr/share/texlive/texmf-dist/tex/latex/base/size10.clo))
> (/usr/share/texlive/texmf-dist/tex/latex/pstricks/pst-all.sty
> (/usr/share/texlive/texmf-dist/tex/latex/pstricks/pstricks.sty
> (/usr/share/texlive/texmf-dist/tex/generic/iftex/iftex.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/xcolor/xcolor.sty
> (/usr/share/texlive/texmf-dist/tex/latex/graphics-cfg/color.cfg)
> (/usr/share/texlive/texmf-dist/tex/latex/graphics-def/dvips.def))
> (/usr/share/texlive/texmf-dist/tex/generic/xkeyva
Bug#973142: marked as done (ruby-arbre: FTBFS: ERROR: Test "ruby2.7" failed: LoadError:)
Your message dated Sat, 07 Nov 2020 01:42:00 +0100 with message-id <8b824ea3f34ca0a3e3d4a9897bf082cd78d277ec.ca...@debian.org> and subject line FTBFS fixed by closing #972702 has caused the Debian Bug report #973142, regarding ruby-arbre: FTBFS: ERROR: Test "ruby2.7" failed: LoadError: 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.) -- 973142: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973142 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-arbre Version: 1.2.1-4 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201027 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > LoadError: > cannot load such file -- combustion > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.4/lib/active_support/dependencies.rb:324:in > `block in require' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.4/lib/active_support/dependencies.rb:291:in > `load_dependency' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.4/lib/active_support/dependencies.rb:324:in > `require' > # ./spec/rails/rails_spec_helper.rb:1:in `' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.4/lib/active_support/dependencies.rb:324:in > `block in require' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.4/lib/active_support/dependencies.rb:291:in > `load_dependency' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.4/lib/active_support/dependencies.rb:324:in > `require' > # ./spec/rails/integration/rendering_spec.rb:1:in `' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.4/lib/active_support/dependencies.rb:318:in > `load' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.4/lib/active_support/dependencies.rb:318:in > `block in load' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.4/lib/active_support/dependencies.rb:291:in > `load_dependency' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.4/lib/active_support/dependencies.rb:318:in > `load' > # -- > # --- Caused by: --- > # LoadError: > # cannot load such file -- combustion > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.4/lib/active_support/dependencies.rb:324:in > `block in require' > No examples found. > > Finished in 0.5 seconds (files took 0.57863 seconds to load) > 0 examples, 0 failures, 12 errors occurred outside of examples > > /usr/bin/ruby2.7 > -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/exe/rspec > --pattern ./spec/\*\*/\*_spec.rb --format documentation failed > ERROR: Test "ruby2.7" failed: The full build log is available from: http://qa-logs.debian.net/2020/10/27/ruby-arbre_1.2.1-4_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- This FTBFS has been fixed by the recent binNMUs after closing #972702 (dependency resolution issue with updated ruby-bundler). Regards, Daniel -- Regards, Daniel Leidert | https://www.wgdd.de/ GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78 If you like my work consider sponsoring me via https://www.patreon.com/join/dleidert signature.asc Description: This is a digitally signed message part --- End Message ---
Bug#973139: marked as done (ruby-bootsnap: FTBFS: ERROR: Test "ruby2.7" failed.)
Your message dated Sat, 07 Nov 2020 01:42:00 +0100 with message-id <8b824ea3f34ca0a3e3d4a9897bf082cd78d277ec.ca...@debian.org> and subject line FTBFS fixed by closing #972702 has caused the Debian Bug report #973139, regarding ruby-bootsnap: FTBFS: ERROR: Test "ruby2.7" 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.) -- 973139: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973139 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-bootsnap Version: 1.4.6-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201027 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/ruby2.7 /usr/bin/gem2deb-test-runner > > ┌──┐ > │ Checking Rubygems dependency resolution on ruby2.7 > │ > └──┘ > > GEM_PATH=/<>/debian/ruby-bootsnap/usr/share/rubygems-integration/2.7.0:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0 > ruby2.7 -e gem\ \"bootsnap\" > > ┌──┐ > │ Run tests for ruby2.7 from debian/ruby-tests.rake > │ > └──┘ > > RUBYLIB=/<>/debian/ruby-bootsnap/usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/2.7.0:/<>/debian/ruby-bootsnap/usr/lib/ruby/vendor_ruby:. > > GEM_PATH=/<>/debian/ruby-bootsnap/usr/share/rubygems-integration/2.7.0:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0 > ruby2.7 -S rake -f debian/ruby-tests.rake > /usr/bin/ruby2.7 -w -I"test" > "/usr/share/rubygems-integration/all/gems/rake-13.0.1/lib/rake/rake_test_loader.rb" > "test/bundler_test.rb" "test/compile_cache_handler_errors_test.rb" > "test/compile_cache_key_format_test.rb" "test/compile_cache_test.rb" > "test/helper_test.rb" "test/load_path_cache/cache_test.rb" > "test/load_path_cache/change_observer_test.rb" > "test/load_path_cache/loaded_features_index_test.rb" > "test/load_path_cache/path_scanner_test.rb" > "test/load_path_cache/path_test.rb" > "test/load_path_cache/realpath_cache_test.rb" > "test/load_path_cache/store_test.rb" -v > /usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/resolver.rb:59:in > `rescue in start': Bundler could not find compatible versions for gem > "msgpack": (Bundler::VersionConflict) > In Gemfile: > bootsnap was resolved to 1.4.6, which depends on > msgpack (~> 1.0) > > Could not find gem 'msgpack (~> 1.0)', which is required by gem 'bootsnap', > in any of the sources. > from > /usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/resolver.rb:45:in > `start' > from > /usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/resolver.rb:22:in > `resolve' > from > /usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/definition.rb:264:in > `resolve' > from > /usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/definition.rb:175:in > `specs' > from > /usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/definition.rb:243:in > `specs_for' > from > /usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/definition.rb:231:in > `requested_specs' > from > /usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/runtime.rb:91:in > `block in definition_method' > from > /usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/runtime.rb:20:in > `setup' > from > /usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler.rb:149:in > `setup' > from > /usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/setup.rb:20:in > `block in ' > from > /usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/ui/shell.rb:136:in > `with_level' > from > /usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/ui/shell.
Bug#973140: marked as done (ruby-invisible-captcha: FTBFS: ERROR: Test "ruby2.7" failed: Failure/Error: require 'bundler/setup' # Set up gems listed in the Gemfile.)
Your message dated Sat, 07 Nov 2020 01:42:00 +0100 with message-id <8b824ea3f34ca0a3e3d4a9897bf082cd78d277ec.ca...@debian.org> and subject line FTBFS fixed by closing #972702 has caused the Debian Bug report #973140, regarding ruby-invisible-captcha: FTBFS: ERROR: Test "ruby2.7" failed: Failure/Error: require 'bundler/setup' # Set up gems listed in the Gemfile. 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.) -- 973140: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973140 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-invisible-captcha Version: 0.12.2-4 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201027 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > Failure/Error: require 'bundler/setup' # Set up gems listed in the Gemfile. > > Bundler::VersionConflict: > Bundler could not find compatible versions for gem "nio4r": > In rails_6.0.gemfile: > rails (~> 6.0.0) was resolved to 6.0.3.4, which depends on > actioncable (= 6.0.3.4) was resolved to 6.0.3.4, which depends on > nio4r (~> 2.0) > > Could not find gem 'nio4r (~> 2.0)', which is required by gem 'actioncable > (= 6.0.3.4)', in any of the sources. > # > /usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler.rb:149:in > `setup' > # ./spec/dummy/config/boot.rb:3:in `' > # ./spec/dummy/config/application.rb:1:in `' > # ./spec/dummy/config/environment.rb:2:in `require_relative' > # ./spec/dummy/config/environment.rb:2:in `' > # ./spec/spec_helper.rb:3:in `' > # -- > # --- Caused by: --- > # Bundler::Molinillo::VersionConflict: > # Unable to satisfy the following requirements: > # > # - `nio4r (~> 2.0)` required by `actioncable (6.0.3.4) (ruby)` > # > /usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler.rb:149:in > `setup' > No examples found. > No examples found. > > > Finished in 0.4 seconds (files took 0.21098 seconds to load) > 0 examples, 0 failures, 1 error occurred outside of examples > > Finished in 0.4 seconds (files took 0.21098 seconds to load) > 0 examples, 0 failures, 1 error occurred outside of examples > > > /usr/bin/ruby2.7 > -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/exe/rspec > --pattern ./spec/\*\*/\*_spec.rb --format documentation failed > ERROR: Test "ruby2.7" failed: The full build log is available from: http://qa-logs.debian.net/2020/10/27/ruby-invisible-captcha_0.12.2-4_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- This FTBFS has been fixed by the recent binNMUs after closing #972702 (dependency resolution issue with updated ruby-bundler). Regards, Daniel -- Regards, Daniel Leidert | https://www.wgdd.de/ GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78 If you like my work consider sponsoring me via https://www.patreon.com/join/dleidert signature.asc Description: This is a digitally signed message part --- End Message ---
Bug#973146: marked as done (ruby-voight-kampff: FTBFS: ERROR: Test "ruby2.7" failed: LoadError:)
Your message dated Sat, 07 Nov 2020 01:42:00 +0100 with message-id <8b824ea3f34ca0a3e3d4a9897bf082cd78d277ec.ca...@debian.org> and subject line FTBFS fixed by closing #972702 has caused the Debian Bug report #973146, regarding ruby-voight-kampff: FTBFS: ERROR: Test "ruby2.7" failed: LoadError: 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.) -- 973146: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973146 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-voight-kampff Version: 1.1.3-4 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201027 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > LoadError: > cannot load such file -- combustion > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.4/lib/active_support/dependencies.rb:324:in > `block in require' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.4/lib/active_support/dependencies.rb:291:in > `load_dependency' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.4/lib/active_support/dependencies.rb:324:in > `require' > # ./spec/spec_helper.rb:1:in `' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.4/lib/active_support/dependencies.rb:324:in > `block in require' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.4/lib/active_support/dependencies.rb:291:in > `load_dependency' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.4/lib/active_support/dependencies.rb:324:in > `require' > # ./spec/lib/voight_kampff_spec.rb:1:in `' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.4/lib/active_support/dependencies.rb:318:in > `load' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.4/lib/active_support/dependencies.rb:318:in > `block in load' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.4/lib/active_support/dependencies.rb:291:in > `load_dependency' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.4/lib/active_support/dependencies.rb:318:in > `load' > # -- > # --- Caused by: --- > # LoadError: > # cannot load such file -- combustion > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.4/lib/active_support/dependencies.rb:324:in > `block in require' > No examples found. > > Finished in 0.4 seconds (files took 0.4 seconds to load) > 0 examples, 0 failures, 4 errors occurred outside of examples > > /usr/bin/ruby2.7 > -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/exe/rspec > --pattern ./spec/\*\*/\*_spec.rb --format documentation failed > ERROR: Test "ruby2.7" failed: The full build log is available from: http://qa-logs.debian.net/2020/10/27/ruby-voight-kampff_1.1.3-4_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- This FTBFS has been fixed by the recent binNMUs after closing #972702 (dependency resolution issue with updated ruby-bundler). Regards, Daniel -- Regards, Daniel Leidert | https://www.wgdd.de/ GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78 If you like my work consider sponsoring me via https://www.patreon.com/join/dleidert signature.asc Description: This is a digitally signed message part --- End Message ---
Bug#973133: marked as done (ruby-jquery-ui-rails: FTBFS: Command failed with status (127): [git submodule update --init...])
Your message dated Sat, 07 Nov 2020 01:49:05 + with message-id and subject line Bug#973133: fixed in ruby-jquery-ui-rails 6.0.1+dfsg-6 has caused the Debian Bug report #973133, regarding ruby-jquery-ui-rails: FTBFS: Command failed with status (127): [git submodule update --init...] 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.) -- 973133: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973133 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-jquery-ui-rails Version: 6.0.1+dfsg-5 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201027 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_build > dh_ruby --build >dh_ruby --build > ln -s /usr/lib/nodejs/jquery-ui . > rake > rm -rf app > git submodule update --init > rake aborted! > Command failed with status (127): [git submodule update --init...] > /<>/Rakefile:70:in `block in ' > /usr/share/rubygems-integration/all/gems/rake-13.0.1/exe/rake:27:in ` (required)>' > Tasks: TOP => default => assets => javascripts => submodule > (See full trace by running task with --trace) > make[1]: *** [debian/rules:20: override_dh_auto_build] Error 1 The full build log is available from: http://qa-logs.debian.net/2020/10/27/ruby-jquery-ui-rails_6.0.1+dfsg-5_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: ruby-jquery-ui-rails Source-Version: 6.0.1+dfsg-6 Done: Daniel Leidert We believe that the bug you reported is fixed in the latest version of ruby-jquery-ui-rails, 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 973...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Daniel Leidert (supplier of updated ruby-jquery-ui-rails 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, 07 Nov 2020 02:11:38 +0100 Source: ruby-jquery-ui-rails Architecture: source Version: 6.0.1+dfsg-6 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Team Changed-By: Daniel Leidert Closes: 973133 Changes: ruby-jquery-ui-rails (6.0.1+dfsg-6) unstable; urgency=medium . * Team upload. * d/rules (override_dh_auto_build): Fix the link creation after node-jquery-ui changed from /Usr/lib to /usr/share (closes: #973133). Checksums-Sha1: fdf8214453088aa9469be7c1364ee5a906ddce7c 2225 ruby-jquery-ui-rails_6.0.1+dfsg-6.dsc f1c5054fe4fc5d18264bd8648ef3db283e1652c5 5032 ruby-jquery-ui-rails_6.0.1+dfsg-6.debian.tar.xz 11a23487e58df6b5b45f20fe9fda9db5aab86ede 9162 ruby-jquery-ui-rails_6.0.1+dfsg-6_amd64.buildinfo Checksums-Sha256: 9e2c6481129afa3bceff4ca5cb27a4d21784c26c097d11a6d6d98153d0cd591d 2225 ruby-jquery-ui-rails_6.0.1+dfsg-6.dsc 9008a110c08b35e5d95f71924e9c6378304f09a3b2000abc4d2f572ae6a7bde7 5032 ruby-jquery-ui-rails_6.0.1+dfsg-6.debian.tar.xz 7bbfd660785b5767388c537c74b1d4edab1a621403537bb1115d28abcca5b627 9162 ruby-jquery-ui-rails_6.0.1+dfsg-6_amd64.buildinfo Files: 1151e7ae35a89c3f8dc3a10bcca72338 2225 ruby optional ruby-jquery-ui-rails_6.0.1+dfsg-6.dsc 2fade0b5efbbcb77537542d8bee29c65 5032 ruby optional ruby-jquery-ui-rails_6.0.1+dfsg-6.debian.tar.xz 2e5ef41078b2d0c80eee1ebf0b7a02dd 9162 ruby optional ruby-jquery-ui-rails_6.0.1+dfsg-6_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAl+l+HsACgkQS80FZ8KW 0F3t6xAAgv0pbfRAfJQlv1+qT9XZAXm0jgynLQMuOxoGTf5jAt8RBr9gaNj2uZEU jwSt9e8f6r15fx4fEIIXhDgpYvir2cq3H//D4Fp7A+lHCpwuEOJbjX264Me7jo/p ji5aKYxawCMrmaE7IMSB4E8HLo7Tu1hxbZnQ8o/tMnRzbCCaQ17YOX+ra2J9Z8sh QZh7tJdrG9CKe1QfUlVypFz+2VYBmWG11D6PQWZnKrIBg3PmhRFTKt5zhvwNbqxP zM0LpegrpdtXGwc5yZJ7Avtru9aHjCpqIUNrLD/U9JoDM/8roPcQnRscwmrSkL25 L5a5BLPow5b0XF/DQ/m3lS1RW
Bug#973133: marked as pending in ruby-jquery-ui-rails
Control: tag -1 pending Hello, Bug #973133 in ruby-jquery-ui-rails reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/ruby-team/ruby-jquery-ui-rails/-/commit/885eddaa8c0a41d980a4bb06665a3555b4996f2b Fix the link creation to jquery-ui and fix the FTBFS * d/rules (override_dh_auto_build): Fix the link creation after node-jquery-ui changed from /Usr/lib to /usr/share (closes: #973133). (this message was generated automatically) -- Greetings https://bugs.debian.org/973133
Processed: Bug#973133 marked as pending in ruby-jquery-ui-rails
Processing control commands: > tag -1 pending Bug #973133 [src:ruby-jquery-ui-rails] ruby-jquery-ui-rails: FTBFS: Command failed with status (127): [git submodule update --init...] Added tag(s) pending. -- 973133: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973133 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#973110: marked as done (ruby-ahoy-email: FTBFS: ERROR: Test "ruby2.7" failed.)
Your message dated Sat, 07 Nov 2020 01:42:00 +0100 with message-id <8b824ea3f34ca0a3e3d4a9897bf082cd78d277ec.ca...@debian.org> and subject line FTBFS fixed by closing #972702 has caused the Debian Bug report #973110, regarding ruby-ahoy-email: FTBFS: ERROR: Test "ruby2.7" 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.) -- 973110: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973110 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-ahoy-email Version: 1.1.0-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201027 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/ruby2.7 /usr/bin/gem2deb-test-runner > > ┌──┐ > │ Checking Rubygems dependency resolution on ruby2.7 > │ > └──┘ > > GEM_PATH=/<>/debian/ruby-ahoy-email/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/2.7.0:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0 > ruby2.7 -e gem\ \"ahoy_email\" > > ┌──┐ > │ Run tests for ruby2.7 from debian/ruby-tests.rake > │ > └──┘ > > RUBYLIB=/<>/debian/ruby-ahoy-email/usr/lib/ruby/vendor_ruby:. > GEM_PATH=/<>/debian/ruby-ahoy-email/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/2.7.0:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0 > ruby2.7 -S rake -f debian/ruby-tests.rake > /usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/resolver.rb:313:in > `block in verify_gemfile_dependencies_are_found!': Could not find gem > 'sqlite3' in any of the gem sources listed in your Gemfile. > (Bundler::GemNotFound) > from > /usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/resolver.rb:281:in > `each' > from > /usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/resolver.rb:281:in > `verify_gemfile_dependencies_are_found!' > from > /usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/resolver.rb:49:in > `start' > from > /usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/resolver.rb:22:in > `resolve' > from > /usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/definition.rb:264:in > `resolve' > from > /usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/definition.rb:175:in > `specs' > from > /usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/definition.rb:243:in > `specs_for' > from > /usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/definition.rb:231:in > `requested_specs' > from > /usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/runtime.rb:91:in > `block in definition_method' > from > /usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/runtime.rb:20:in > `setup' > from > /usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler.rb:149:in > `setup' > from > /usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/setup.rb:20:in > `block in ' > from > /usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/ui/shell.rb:136:in > `with_level' > from > /usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/ui/shell.rb:88:in > `silence' > from > /usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/setup.rb:20:in > `' > from > /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:83:in `require' > from > /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:83:in `require' > from /<>/test/test_helper.rb:1:in `' > from /<>/test/click_test.rb:1:in `require_r
Bug#973127: marked as done (ruby-combustion: FTBFS: ERROR: Test "ruby2.7" failed: Failure/Error: require "bundler/setup")
Your message dated Sat, 07 Nov 2020 01:42:00 +0100 with message-id <8b824ea3f34ca0a3e3d4a9897bf082cd78d277ec.ca...@debian.org> and subject line FTBFS fixed by closing #972702 has caused the Debian Bug report #973127, regarding ruby-combustion: FTBFS: ERROR: Test "ruby2.7" failed: Failure/Error: require "bundler/setup" 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.) -- 973127: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973127 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-combustion Version: 1.3.0-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201027 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > Failure/Error: require "bundler/setup" > > Bundler::GemNotFound: > Could not find gem 'mysql2' in any of the gem sources listed in your > Gemfile. > # > /usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler.rb:149:in > `setup' > # ./spec/spec_helper.rb:3:in `' > No examples found. > > > Finished in 0.2 seconds (files took 0.18247 seconds to load) > [31m0 examples, 0 failures, 1 error occurred outside of examples[0m > > /usr/bin/ruby2.7 > -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/exe/rspec > --pattern ./spec/\*_spec.rb failed > ERROR: Test "ruby2.7" failed: The full build log is available from: http://qa-logs.debian.net/2020/10/27/ruby-combustion_1.3.0-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- This FTBFS has been fixed by the recent binNMUs after closing #972702 (dependency resolution issue with updated ruby-bundler). Regards, Daniel -- Regards, Daniel Leidert | https://www.wgdd.de/ GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78 If you like my work consider sponsoring me via https://www.patreon.com/join/dleidert signature.asc Description: This is a digitally signed message part --- End Message ---
Bug#973108: marked as done (ruby-sassc-rails: FTBFS: ERROR: Test "ruby2.7" failed.)
Your message dated Sat, 07 Nov 2020 01:42:00 +0100 with message-id <8b824ea3f34ca0a3e3d4a9897bf082cd78d277ec.ca...@debian.org> and subject line FTBFS fixed by closing #972702 has caused the Debian Bug report #973108, regarding ruby-sassc-rails: FTBFS: ERROR: Test "ruby2.7" 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.) -- 973108: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973108 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-sassc-rails Version: 2.1.2-5 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201027 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/ruby2.7 /usr/bin/gem2deb-test-runner > > ┌──┐ > │ Checking Rubygems dependency resolution on ruby2.7 > │ > └──┘ > > GEM_PATH=/<>/debian/ruby-sassc-rails/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0 > ruby2.7 -e gem\ \"sassc-rails\" > > ┌──┐ > │ Run tests for ruby2.7 from debian/ruby-tests.rake > │ > └──┘ > > RUBYLIB=/<>/debian/ruby-sassc-rails/usr/lib/ruby/vendor_ruby:. > GEM_PATH=/<>/debian/ruby-sassc-rails/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0 > ruby2.7 -S rake -f debian/ruby-tests.rake > /usr/bin/ruby2.7 -w -I"test" > "/usr/share/rubygems-integration/all/gems/rake-13.0.1/lib/rake/rake_test_loader.rb" > "test/sassc_rails_test.rb" "test/test_helper.rb" -v > /<>/test/sassc_rails_test.rb:125: warning: ambiguous first > argument; put parentheses or a space even after `/' operator > /<>/test/sassc_rails_test.rb:126: warning: ambiguous first > argument; put parentheses or a space even after `/' operator > /<>/test/sassc_rails_test.rb:127: warning: ambiguous first > argument; put parentheses or a space even after `/' operator > /<>/test/sassc_rails_test.rb:128: warning: ambiguous first > argument; put parentheses or a space even after `/' operator > /<>/test/sassc_rails_test.rb:129: warning: ambiguous first > argument; put parentheses or a space even after `/' operator > /<>/test/sassc_rails_test.rb:130: warning: ambiguous first > argument; put parentheses or a space even after `/' operator > /<>/test/sassc_rails_test.rb:131: warning: ambiguous first > argument; put parentheses or a space even after `/' operator > /<>/test/sassc_rails_test.rb:132: warning: ambiguous first > argument; put parentheses or a space even after `/' operator > /<>/test/sassc_rails_test.rb:133: warning: ambiguous first > argument; put parentheses or a space even after `/' operator > /<>/test/sassc_rails_test.rb:134: warning: ambiguous first > argument; put parentheses or a space even after `/' operator > /<>/test/sassc_rails_test.rb:135: warning: ambiguous first > argument; put parentheses or a space even after `/' operator > /<>/test/sassc_rails_test.rb:136: warning: ambiguous first > argument; put parentheses or a space even after `/' operator > /<>/test/sassc_rails_test.rb:137: warning: ambiguous first > argument; put parentheses or a space even after `/' operator > /<>/test/sassc_rails_test.rb:138: warning: ambiguous first > argument; put parentheses or a space even after `/' operator > /<>/test/sassc_rails_test.rb:139: warning: ambiguous first > argument; put parentheses or a space even after `/' operator > /<>/test/sassc_rails_test.rb:140: warning: ambiguous first > argument; put parentheses or a space even after `/' operator > /<>/test/sassc_rails_test.rb:144: warning: ambiguous first > argument; put parentheses or a space even after `/' operator > /<>/test/sassc_rails_test.rb:145: warning: ambiguous first > argument; put parentheses or a space even after `/' operator > /<>/test/sassc_rails_test.rb:147: warning: ambiguous first > argument; put parenthe
Bug#973107: marked as done (ruby-premailer-rails: FTBFS: ERROR: Test "ruby2.7" failed: LoadError:)
Your message dated Sat, 07 Nov 2020 01:42:00 +0100 with message-id <8b824ea3f34ca0a3e3d4a9897bf082cd78d277ec.ca...@debian.org> and subject line FTBFS fixed by closing #972702 has caused the Debian Bug report #973107, regarding ruby-premailer-rails: FTBFS: ERROR: Test "ruby2.7" failed: LoadError: 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.) -- 973107: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973107 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-premailer-rails Version: 1.10.3-3 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201027 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > LoadError: > cannot load such file -- rails > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.4/lib/active_support/dependencies.rb:324:in > `block in require' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.4/lib/active_support/dependencies.rb:291:in > `load_dependency' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.4/lib/active_support/dependencies.rb:324:in > `require' > # ./spec/spec_helper.rb:1:in `' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.4/lib/active_support/dependencies.rb:324:in > `block in require' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.4/lib/active_support/dependencies.rb:291:in > `load_dependency' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.4/lib/active_support/dependencies.rb:324:in > `require' > # ./spec/unit/premailer_rails_spec.rb:1:in `' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.4/lib/active_support/dependencies.rb:318:in > `load' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.4/lib/active_support/dependencies.rb:318:in > `block in load' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.4/lib/active_support/dependencies.rb:291:in > `load_dependency' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.4/lib/active_support/dependencies.rb:318:in > `load' > # -- > # --- Caused by: --- > # LoadError: > # cannot load such file -- rails > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.4/lib/active_support/dependencies.rb:324:in > `block in require' > No examples found. > > Finished in 0.5 seconds (files took 0.65618 seconds to load) > 0 examples, 0 failures, 8 errors occurred outside of examples > > Coverage report generated for RSpec to /<>/coverage. 12 / 245 > LOC (4.9%) covered. > SimpleCov failed with exit 1 > /usr/bin/ruby2.7 > -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/exe/rspec > --pattern ./spec/\*\*/\*_spec.rb --format documentation failed > ERROR: Test "ruby2.7" failed: The full build log is available from: http://qa-logs.debian.net/2020/10/27/ruby-premailer-rails_1.10.3-3_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- This FTBFS has been fixed by the recent binNMUs after closing #972702 (dependency resolution issue with updated ruby-bundler). Regards, Daniel -- Regards, Daniel Leidert | https://www.wgdd.de/ GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78 If you like my work consider sponsoring me via https://www.patreon.com/join/dleidert signature.asc Description: This is a digitally signed message part --- End Message ---
Bug#973064: marked as done (ruby-rails-controller-testing: FTBFS: ERROR: Test "ruby2.7" failed.)
Your message dated Sat, 07 Nov 2020 01:42:00 +0100 with message-id <8b824ea3f34ca0a3e3d4a9897bf082cd78d277ec.ca...@debian.org> and subject line FTBFS fixed by closing #972702 has caused the Debian Bug report #973064, regarding ruby-rails-controller-testing: FTBFS: ERROR: Test "ruby2.7" 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.) -- 973064: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973064 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-rails-controller-testing Version: 1.0.5-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201027 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/ruby2.7 /usr/bin/gem2deb-test-runner > > ┌──┐ > │ Checking Rubygems dependency resolution on ruby2.7 > │ > └──┘ > > GEM_PATH=/<>/debian/ruby-rails-controller-testing/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0 > ruby2.7 -e gem\ \"rails-controller-testing\" > > ┌──┐ > │ Run tests for ruby2.7 from debian/ruby-tests.rake > │ > └──┘ > > RUBYLIB=. > GEM_PATH=/<>/debian/ruby-rails-controller-testing/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0 > ruby2.7 -S rake -f debian/ruby-tests.rake > /usr/bin/ruby2.7 -w -I"test" > "/usr/share/rubygems-integration/all/gems/rake-13.0.1/lib/rake/rake_test_loader.rb" > "test/controllers/assigns_test.rb" > "test/controllers/template_assertions_test.rb" > "test/helpers/template_assertions_test.rb" > "test/integration/template_assertions_test.rb" "test/test_helper.rb" -v > /usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/resolver.rb:313:in > `block in verify_gemfile_dependencies_are_found!': Could not find gem > 'sqlite3' in any of the gem sources listed in your Gemfile. > (Bundler::GemNotFound) > from > /usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/resolver.rb:281:in > `each' > from > /usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/resolver.rb:281:in > `verify_gemfile_dependencies_are_found!' > from > /usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/resolver.rb:49:in > `start' > from > /usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/resolver.rb:22:in > `resolve' > from > /usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/definition.rb:264:in > `resolve' > from > /usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/definition.rb:175:in > `specs' > from > /usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/definition.rb:243:in > `specs_for' > from > /usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/definition.rb:231:in > `requested_specs' > from > /usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/runtime.rb:91:in > `block in definition_method' > from > /usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/runtime.rb:20:in > `setup' > from > /usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler.rb:149:in > `setup' > from > /usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/setup.rb:20:in > `block in ' > from > /usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/ui/shell.rb:136:in > `with_level' > from > /usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/ui/shell.rb:88:in > `silence' > from > /usr/share/rubygems-integration/all/gems/bundler-2.2.0.rc.1/lib/bundler/setup.rb:20:in > `' > from > /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:83:in
Processed: closing 851048
Processing commands for cont...@bugs.debian.org: > close 851048 0.12.0-1 Bug #851048 [src:dipy] dipy: FTBFS: x86_64-linux-gnu-gcc: error: /arch:SSE2: No such file or directory Marked as fixed in versions dipy/0.12.0-1. Bug #851048 [src:dipy] dipy: FTBFS: x86_64-linux-gnu-gcc: error: /arch:SSE2: No such file or directory Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 851048: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851048 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#957503: marked as done (lpe: ftbfs with GCC-10)
Your message dated Fri, 06 Nov 2020 22:49:23 + with message-id and subject line Bug#957503: fixed in lpe 1.2.8-2.1 has caused the Debian Bug report #957503, regarding lpe: ftbfs with GCC-10 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.) -- 957503: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957503 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:lpe Version: 1.2.8-2 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 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-10/g++-10, but succeeds to build with gcc-9/g++-9. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc10-20200225/lpe_1.2.8-2_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 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-10/porting_to.html [...] ../../src/input.c: In function ‘stream_manip’: ../../src/input.c:1675:5: warning: ignoring return value of ‘pipe’ declared with attribute ‘warn_unused_result’ [-Wunused-result] 1675 | pipe (pipes[0]); | ^~~ ../../src/input.c:1676:5: warning: ignoring return value of ‘pipe’ declared with attribute ‘warn_unused_result’ [-Wunused-result] 1676 | pipe (pipes[1]); | ^~~ gcc -DHAVE_CONFIG_H -I. -I../../src -I.. -DLOCALEDIR=\"/usr/share/locale\" -DPLUGINDIR=\"/usr/lib/x86_64-linux-gnu/lpe\" -Wdate-time -D_FORTIFY_SOURCE=2 -DDATADIR=\"/usr/share/lpe\" -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o lpe.o ../../src/lpe.c gcc -DHAVE_CONFIG_H -I. -I../../src -I.. -DLOCALEDIR=\"/usr/share/locale\" -DPLUGINDIR=\"/usr/lib/x86_64-linux-gnu/lpe\" -Wdate-time -D_FORTIFY_SOURCE=2 -DDATADIR=\"/usr/share/lpe\" -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o lpecomm.o ../../src/lpecomm.c gcc -DHAVE_CONFIG_H -I. -I../../src -I.. -DLOCALEDIR=\"/usr/share/locale\" -DPLUGINDIR=\"/usr/lib/x86_64-linux-gnu/lpe\" -Wdate-time -D_FORTIFY_SOURCE=2 -DDATADIR=\"/usr/share/lpe\" -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o minibuf.o ../../src/minibuf.c In file included from /usr/include/string.h:495, from ../../src/minibuf.c:13: In function ‘strncpy’, inlined from ‘mbuf_mode_compl’ at ../../src/minibuf.c:279:2, inlined from ‘mbuf_key_tab’ at ../../src/minibuf.c:417:2, inlined from ‘mbuf_process_input’ at ../../src/minibuf.c:673:6, inlined from ‘mbuf_ask’ at ../../src/minibuf.c:724:13: /usr/include/x86_64-linux-gnu/bits/string_fortified.h:106:10: warning: ‘__builtin___strncpy_chk’ specified bound depends on the length of the source argument [-Wstringop-overflow=] 106 | return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest)); | ^~ ../../src/minibuf.c: In function ‘mbuf_ask’: ../../src/minibuf.c:277:12: note: length computed here 277 | if ((ml = strlen (am[found])) > 99) |^~ In file included from /usr/include/string.h:495, from ../../src/minibuf.c:13: In function ‘strncpy’, inlined from ‘mbuf_file_compl’ at ../../src/minibuf.c:389:2, inlined from ‘mbuf_key_tab’ at ../../src/minibuf.c:412:2, inlined from ‘mbuf_process_input’ at ../../src/minibuf.c:673:6, inlined from ‘mbuf_ask’ at ../../src/minibuf.c:724:13: /usr/include/x86_64-linux-gnu/bits/string_fortified.h:106:10: warning: ‘__builtin___strncpy_chk’ specified bound depends on the length of the source argument [-Wstringop-overflow=] 106 | return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest)); | ^~
Bug#964195: guacamole-client: CVE-2020-9497 and CVE-2020-9498
Control: tags -1 patch
Hi,
I'm attaching my patch for Stretch to this bug report. Since the
versions in Stretch and unstable are identical, it should work there
too. However I don't intend to NMU guacamole-server because I believe a
new upstream version should be packaged instead.
Regards,
Markus
diff -Nru
guacamole-server-0.9.9/debian/patches/CVE-2020-9497-and-CVE-2020-9498.patch
guacamole-server-0.9.9/debian/patches/CVE-2020-9497-and-CVE-2020-9498.patch
--- guacamole-server-0.9.9/debian/patches/CVE-2020-9497-and-CVE-2020-9498.patch
1970-01-01 01:00:00.0 +0100
+++ guacamole-server-0.9.9/debian/patches/CVE-2020-9497-and-CVE-2020-9498.patch
2020-11-06 22:44:56.0 +0100
@@ -0,0 +1,355 @@
+From: Markus Koschany
+Date: Tue, 3 Nov 2020 13:45:20 +0100
+Subject: CVE-2020-9497 and CVE-2020-9498
+
+Bug-Debian: https://bugs.debian.org/964195
+Origin:
https://github.com/apache/guacamole-server/commit/a0e11dc81727528224d28466903454e1cb0266bb
+---
+ src/protocols/rdp/guac_rdpdr/rdpdr_fs_messages.c | 40 ++
+ .../rdp/guac_rdpdr/rdpdr_fs_messages_file_info.c | 12 +++
+ src/protocols/rdp/guac_rdpdr/rdpdr_messages.c | 18 ++
+ src/protocols/rdp/guac_rdpdr/rdpdr_printer.c | 7
+ src/protocols/rdp/guac_rdpdr/rdpdr_service.c | 3 ++
+ src/protocols/rdp/guac_rdpsnd/rdpsnd_messages.c| 29
+ src/protocols/rdp/guac_rdpsnd/rdpsnd_service.c | 5 +++
+ 7 files changed, 114 insertions(+)
+
+diff --git a/src/protocols/rdp/guac_rdpdr/rdpdr_fs_messages.c
b/src/protocols/rdp/guac_rdpdr/rdpdr_fs_messages.c
+index bfd8ead..10d41bb 100644
+--- a/src/protocols/rdp/guac_rdpdr/rdpdr_fs_messages.c
b/src/protocols/rdp/guac_rdpdr/rdpdr_fs_messages.c
+@@ -58,6 +58,10 @@ void guac_rdpdr_fs_process_create(guac_rdpdr_device* device,
+ int create_disposition, create_options, path_length;
+ char path[GUAC_RDP_FS_MAX_PATH];
+
++/* Check remaining stream data prior to reading. */
++if (Stream_GetRemainingLength(input_stream) < 32)
++return;
++
+ /* Read "create" information */
+ Stream_Read_UINT32(input_stream, desired_access);
+ Stream_Seek_UINT64(input_stream); /* allocation size */
+@@ -67,6 +71,11 @@ void guac_rdpdr_fs_process_create(guac_rdpdr_device* device,
+ Stream_Read_UINT32(input_stream, create_options);
+ Stream_Read_UINT32(input_stream, path_length);
+
++/* Check to make sure the stream contains path_length bytes. */
++if(Stream_GetRemainingLength(input_stream) < path_length) {
++return;
++}
++
+ /* Convert path to UTF-8 */
+ guac_rdp_utf16_to_utf8(Stream_Pointer(input_stream), path_length/2 - 1,
+ path, sizeof(path));
+@@ -133,6 +142,10 @@ void guac_rdpdr_fs_process_read(guac_rdpdr_device* device,
+
+ wStream* output_stream;
+
++/* Check remaining bytes before reading stream. */
++if (Stream_GetRemainingLength(input_stream) < 12)
++return;
++
+ /* Read packet */
+ Stream_Read_UINT32(input_stream, length);
+ Stream_Read_UINT64(input_stream, offset);
+@@ -181,6 +194,10 @@ void guac_rdpdr_fs_process_write(guac_rdpdr_device*
device,
+
+ wStream* output_stream;
+
++/* Check remaining length. */
++if (Stream_GetRemainingLength(input_stream) < 32)
++return;
++
+ /* Read packet */
+ Stream_Read_UINT32(input_stream, length);
+ Stream_Read_UINT64(input_stream, offset);
+@@ -190,6 +207,11 @@ void guac_rdpdr_fs_process_write(guac_rdpdr_device*
device,
+ "%s: [file_id=%i] length=%i, offset=%" PRIu64,
+ __func__, file_id, length, (uint64_t) offset);
+
++/* Check to make sure stream contains at least length bytes */
++if (Stream_GetRemainingLength(input_stream) < length) {
++return;
++}
++
+ /* Attempt write */
+ bytes_written = guac_rdp_fs_write((guac_rdp_fs*) device->data, file_id,
+ offset, Stream_Pointer(input_stream), length);
+@@ -252,6 +274,10 @@ void guac_rdpdr_fs_process_volume_info(guac_rdpdr_device*
device, wStream* input
+
+ int fs_information_class;
+
++/* Check remaining length */
++if (Stream_GetRemainingLength(input_stream) < 4)
++return;
++
+ Stream_Read_UINT32(input_stream, fs_information_class);
+
+ /* Dispatch to appropriate class-specific handler */
+@@ -294,6 +320,10 @@ void guac_rdpdr_fs_process_file_info(guac_rdpdr_device*
device, wStream* input_s
+
+ int fs_information_class;
+
++/* Check remaining length */
++if (Stream_GetRemainingLength(input_stream) < 4)
++return;
++
+ Stream_Read_UINT32(input_stream, fs_information_class);
+
+ /* Dispatch to appropriate class-specific handler */
+@@ -341,6 +371,10 @@ void
guac_rdpdr_fs_process_set_file_info(guac_rdpdr_device* device,
+ int fs_information_class;
+ int length;
+
++/* Check remaining length */
++if (Stream_GetRemainingLength(input_stream) < 32)
+
Processed: Re: Bug#964195: guacamole-client: CVE-2020-9497 and CVE-2020-9498
Processing control commands: > tags -1 patch Bug #964195 [src:guacamole-server] CVE-2020-9497 CVE-2020-9498 Added tag(s) patch. -- 964195: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964195 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 973889
Processing commands for cont...@bugs.debian.org: > tags 973889 + fixed-upstream Bug #973889 [src:raptor2] raptor2: CVE-2017-18926 Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 973889: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973889 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: raptor2: diff for NMU version 2.0.14-1.1
Processing control commands: > tags 973889 + patch Bug #973889 [src:raptor2] raptor2: CVE-2017-18926 Added tag(s) patch. > tags 973889 + pending Bug #973889 [src:raptor2] raptor2: CVE-2017-18926 Added tag(s) pending. -- 973889: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973889 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#973889: raptor2: diff for NMU version 2.0.14-1.1
Control: tags 973889 + patch
Control: tags 973889 + pending
Dear maintainer,
I've prepared an NMU for raptor2 (versioned as 2.0.14-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
Regards,
Salvatore
diff -Nru raptor2-2.0.14/debian/changelog raptor2-2.0.14/debian/changelog
--- raptor2-2.0.14/debian/changelog 2014-05-05 20:15:34.0 +0200
+++ raptor2-2.0.14/debian/changelog 2020-11-06 22:08:54.0 +0100
@@ -1,3 +1,11 @@
+raptor2 (2.0.14-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Calcualte max nspace declarations correctly for XML writer
+(CVE-2017-18926) (Closes: #973889)
+
+ -- Salvatore Bonaccorso Fri, 06 Nov 2020 22:08:54 +0100
+
raptor2 (2.0.14-1) unstable; urgency=medium
* New upstream release
diff -Nru raptor2-2.0.14/debian/patches/Calcualte-max-nspace-declarations-correctly-for-XML-.patch raptor2-2.0.14/debian/patches/Calcualte-max-nspace-declarations-correctly-for-XML-.patch
--- raptor2-2.0.14/debian/patches/Calcualte-max-nspace-declarations-correctly-for-XML-.patch 1970-01-01 01:00:00.0 +0100
+++ raptor2-2.0.14/debian/patches/Calcualte-max-nspace-declarations-correctly-for-XML-.patch 2020-11-06 22:08:54.0 +0100
@@ -0,0 +1,45 @@
+From: Dave Beckett
+Date: Sun, 16 Apr 2017 23:15:12 +0100
+Subject: Calcualte max nspace declarations correctly for XML writer
+Origin: https://github.com/dajobe/raptor/commit/590681e546cd9aa18d57dc2ea1858cb734a3863f
+Bug-Debian: https://bugs.debian.org/973889
+Bug-Debian-Security: https://security-tracker.debian.org/tracker/CVE-2017-18926
+
+(raptor_xml_writer_start_element_common): Calculate max including for
+each attribute a potential name and value.
+
+Fixes Issues #617 http://bugs.librdf.org/mantis/view.php?id=617
+and #618 http://bugs.librdf.org/mantis/view.php?id=618
+---
+ src/raptor_xml_writer.c | 7 ---
+ 1 file changed, 4 insertions(+), 3 deletions(-)
+
+diff --git a/src/raptor_xml_writer.c b/src/raptor_xml_writer.c
+index 693b946863e6..0d3a36a5a21c 100644
+--- a/src/raptor_xml_writer.c
b/src/raptor_xml_writer.c
+@@ -181,9 +181,10 @@ raptor_xml_writer_start_element_common(raptor_xml_writer* xml_writer,
+ size_t nspace_declarations_count = 0;
+ unsigned int i;
+
+- /* max is 1 per element and 1 for each attribute + size of declared */
+ if(nstack) {
+-int nspace_max_count = element->attribute_count+1;
++int nspace_max_count = element->attribute_count * 2; /* attr and value */
++if(element->name->nspace)
++ nspace_max_count++;
+ if(element->declared_nspaces)
+ nspace_max_count += raptor_sequence_size(element->declared_nspaces);
+ if(element->xml_language)
+@@ -237,7 +238,7 @@ raptor_xml_writer_start_element_common(raptor_xml_writer* xml_writer,
+ }
+ }
+
+- /* Add the attribute + value */
++ /* Add the attribute's value */
+ nspace_declarations[nspace_declarations_count].declaration=
+ raptor_qname_format_as_xml(element->attributes[i],
+&nspace_declarations[nspace_declarations_count].length);
+--
+2.29.1
+
diff -Nru raptor2-2.0.14/debian/patches/series raptor2-2.0.14/debian/patches/series
--- raptor2-2.0.14/debian/patches/series 1970-01-01 01:00:00.0 +0100
+++ raptor2-2.0.14/debian/patches/series 2020-11-06 22:08:54.0 +0100
@@ -0,0 +1 @@
+Calcualte-max-nspace-declarations-correctly-for-XML-.patch
signature.asc
Description: PGP signature
Bug#973889: raptor2: CVE-2017-18926
Source: raptor2 Version: 2.0.14-1 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for raptor2. CVE-2017-18926[0]: | raptor_xml_writer_start_element_common in raptor_xml_writer.c in | Raptor RDF Syntax Library 2.0.15 miscalculates the maximum nspace | declarations for the XML writer, leading to heap-based buffer | overflows (sometimes seen in raptor_qname_format_as_xml). 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-18926 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-18926 [1] https://github.com/LibreOffice/core/blob/master/external/redland/raptor/0001-Calcualte-max-nspace-declarations-correctly-for-XML-.patch.1 [2] https://www.openwall.com/lists/oss-security/2017/06/07/1 Regards, Salvatore
Bug#971704: gnome-shell-pomodoro: diff for NMU version 0.18.0-0.1
Thanks for doing that. I unfortunately haven't taken any time for opensource since the beginning of this COVID madness. Feel free to push it now. It's totally fine with me. Thanks Joseph
Bug#973767: dolfin FTBFS: The MPI_Comm_rank() function was called before MPI_INIT was invoked.
Source: dolfin Followup-For: Bug #973767 Yeah, I'm more certain SLEPc is the problem. In the new release they abolishing SLEPc.pc, renaming it slepc.pc. Since pkg-config is case-sensitive, the unexpected change is causing problems. Notice how the reported error is only with dolfin64. Because the proper SLEPc is not detected, the 64-bit build is mixing up 32-bit and 64-bit builds of PETSc and SLEPc. Resolution in progress.
Bug#972490: marked as done (rubygems_3.2.0~rc.1-2_all-buildd.changes REJECTED)
Your message dated Fri, 06 Nov 2020 17:33:31 + with message-id and subject line Bug#972490: fixed in rubygems 3.2.0~rc.1-3 has caused the Debian Bug report #972490, regarding rubygems_3.2.0~rc.1-2_all-buildd.changes REJECTED 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.) -- 972490: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972490 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rubygems Version: 3.2.0~rc.1-2 Severity: serious - Forwarded message from Debian FTP Masters - From: Debian FTP Masters To: all Build Daemon Date: Mon, 19 Oct 2020 03:49:20 + Subject: rubygems_3.2.0~rc.1-2_all-buildd.changes REJECTED Message-Id: Version check failed: Your upload included the binary package ruby-bundler, version 2.2.0~rc.1, for all, however unstable already has version 2.2.0~rc.1. Uploads to unstable must have a higher version than present in unstable. Mapping sid to unstable. === Please feel free to respond to this email if you don't understand why your files were rejected, or if you upload new files which address our concerns. - End forwarded message - --- End Message --- --- Begin Message --- Source: rubygems Source-Version: 3.2.0~rc.1-3 Done: Lucas Kanashiro We believe that the bug you reported is fixed in the latest version of rubygems, 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 972...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Lucas Kanashiro (supplier of updated rubygems 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, 05 Nov 2020 16:09:55 -0300 Source: rubygems Architecture: source Version: 3.2.0~rc.1-3 Distribution: sid Urgency: medium Maintainer: Debian Ruby Team Changed-By: Lucas Kanashiro Closes: 972490 Changes: rubygems (3.2.0~rc.1-3) unstable; urgency=medium . * d/p/0001-Replace-bundled-libraries-with-system-versions.patch: make bundler use libraries from the system. * Add b-d on ruby-molinillo and ruby-thor. * Add patches to make bundler better handle temporary directories: - d/p/0002-Don-t-use-insecure-temporary-directory-as-home-direc.patch - d/p/0003-Remove-temporary-home-directories.patch * Add debian revision to bundler version string (Closes: #972490) Checksums-Sha1: 1cbc5e4264345652631d32cbaf4476a09f86071d 2308 rubygems_3.2.0~rc.1-3.dsc 5d6c37ca29c298db988a54d9add6688de6ffbd6e 7084 rubygems_3.2.0~rc.1-3.debian.tar.xz dcc4c2eed7b8e4e309c9576dbdc2aab07f90a3a3 9459 rubygems_3.2.0~rc.1-3_amd64.buildinfo Checksums-Sha256: 1b8c2dcfeb8809bd82315b0d635934a6b6307a03abc45c45839a7ffaf8d36c23 2308 rubygems_3.2.0~rc.1-3.dsc 1c0413b80dd256e2e266c2948a17a5d60a54328a55983f1e18bc5d0fa217fcef 7084 rubygems_3.2.0~rc.1-3.debian.tar.xz 0df9aa07e760d60284619314c1011ba9cb33bfaefb2d35955b13cbe0ac70d135 9459 rubygems_3.2.0~rc.1-3_amd64.buildinfo Files: 811863be2408fc1f6369463beb028e88 2308 ruby optional rubygems_3.2.0~rc.1-3.dsc 9f8ef4edb029e7355576dbcd68ff92a8 7084 ruby optional rubygems_3.2.0~rc.1-3.debian.tar.xz 492156b5c7ae73d59f2cdf4f16d0c2cb 9459 ruby optional rubygems_3.2.0~rc.1-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJJBAEBCAAzFiEEjtbD+LrJ23/BMKhw+COicpiDyXwFAl+lgnUVHGthbmFzaGly b0BkZWJpYW4ub3JnAAoJEPgjonKYg8l8XZgP/A4rhUeSTnsr9rxegtmvbO3ttI+q duOgHVfA2DlXNkpjpyxrsFFQAYDc4BD5+DyJ+BlnDzPTInhltWN78T/Y962ZFD1y 8mxMP0+rSARajley+uc4fHI8flomkZ9Dyp6EoPRg9rxSRSyvn1/kryDGvHrhsWkv lB3/+7bdk2zQtIlF3Q6UWicKkG4nTo3R3Q8LvTCPH5TV0Ob4I++J88kOuNDaaUBb v+t17QeceE0UnDqBAJEsEAkZYrDM9W7ispgZnZVKy8qPeMgkk+lXVTLk+mceOY3O QteuMxujP5zKp2VzZiRlPsHIRNWHb4iPCmXlGpRj8VxMNKR1sgBfs+i/KOAi49KL NOo/3mmG5lUruKCiu7uem8MNE3uJpwgBqPB77u2MmySSHVj4xZuSxCZnI7aIu7rV tcNsLRaIEIIgEw8wD/G/3M3ckaob0y5eRKMtU1xy83Hb4JkpA8+ZEPHmczn+/Zqd wJNt7xuc1QxNuWch3zRjo7pSIo+IeO+Fg5Pfmxdz+fayk1tIYwXe5q9S9EbYl9GR YN3KZLbcb4T60G7UGpg/5gOvJULAwXBKmyI6RlS3K6MVEiIXQ/g3CfTec8HLMNOb oHOj/5WYRpuuN9X9R/LRSK1UL4qwwn4H04TNvd9L0lTaDqox7ux7T32rh1rP9GUv v0auREtm3YWyuKH5 =tKpX -END PGP SIGNATURE End Message ---
Bug#949736: marked as done (enigmail: uninstallable in stretch (since thunderbird was upgraded to version 68 due to security upgrade))
Your message dated Fri, 6 Nov 2020 16:35:18 +0100 with message-id and subject line enigmail has been removed from stretch has caused the Debian Bug report #949736, regarding enigmail: uninstallable in stretch (since thunderbird was upgraded to version 68 due to security upgrade) 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.) -- 949736: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949736 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: enigmail Version: 2:2.0.8-5~deb9u1 Justification: renders package unusable Severity: grave Tags: stretch Dear Maintainer, Current version of Thunderbird in Debian stretch is 68, which is incompatible with the enigmail currently packaged in stretch. The issue was fixed in Debian buster and Debian jessie by upgrading the version of enigmail, but this has not been done in stretch yet. Then, * for new installs, enigmail cannot be installed, * the computers that were already running stretch need to choose between upgrading Thunderbird to get the security updates (and then enigmail will be uninstalled), or keeping the old version of Thunderbird with a working enigmail (but having unpatched security vulnerabilities). There will be a release point for stretch soon and it would be great if it carries a new version of enigmail solving this issue for stretch. Thanks! -- Laura Arjona https://wiki.debian.org/LauraArjona -- System Information: Debian Release: 9.11 APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-11-amd64 (SMP w/1 CPU core) Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE=es_ES.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages enigmail depends on: ii gnupg 2.1.18-8~deb9u4 ii gnupg-agent2.1.18-8~deb9u4 ii icedove1:68.4.1-1~deb9u1 ii thunderbird [icedove] 1:68.4.1-1~deb9u1 Versions of packages enigmail recommends: ii pinentry-gnome3 [pinentry-x11] 1.0.0-2 enigmail suggests no packages. -- Laura Arjona Reina https://wiki.debian.org/LauraArjona --- End Message --- --- Begin Message --- As of https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965128 - enigmail has been removed from stretch, making this bug obsolete. --- End Message ---
Bug#973291: marked as done (ros-rospack ftbfs with new googletest)
Your message dated Fri, 06 Nov 2020 15:33:36 + with message-id and subject line Bug#973095: fixed in cmake-extras 1.5-7 has caused the Debian Bug report #973095, regarding ros-rospack ftbfs with new googletest 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.) -- 973095: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973095 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:ros-rospack Version: 2.6.2-2 Severity: serious Tags: sid bullseye ftbfs ros-rospack ftbfs with new googletest, seen in a test rebuild: https://people.debian.org/~ginggs/python3.9-default/ros-rospack_2.6.2-2+build1_amd64-2020-10-27T13:12:37Z.build [...] make[5]: Entering directory '/<>/build' [ 93%] Building CXX object test/CMakeFiles/rospack-utest.dir/test/utest.cpp.o cd /<>/build/test && /usr/bin/c++ -DBOOST_ALL_NO_LIB -DBOOST_FILESYSTEM_DYN_LINK -DBOOST_PROGRAM_OPTIONS_DYN_LINK -DBOOST_SYSTEM_DYN_LINK -DGTEST_VERSION_MAJOR=1 -DGTEST_VERSION_MINOR=8 -DGTEST_VERSION_PATCH=0 -DGTEST_VERSION_UNKNOWN -DROSPACK_API_BACKCOMPAT_V1 -DROS_BUILD_SHARED_LIBS=1 -I/<>/include -I/usr/include/python3.9 -I/<>/src -I/usr/src/googletest/googlemock/include -I/usr/src/googletest/googletest/include -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -o CMakeFiles/rospack-utest.dir/test/utest.cpp.o -c /<>/test/test/utest.cpp make[5]: *** No rule to make target 'gmock/libgmock.a', needed by 'devel/lib/rospack/rospack-utest'. Stop. make[5]: Leaving directory '/<>/build' make[4]: *** [CMakeFiles/Makefile2:438: test/CMakeFiles/rospack-utest.dir/all] Error 2 make[4]: Leaving directory '/<>/build' make[3]: *** [CMakeFiles/Makefile2:254: CMakeFiles/run_tests.dir/rule] Error 2 make[3]: Leaving directory '/<>/build' make[2]: *** [Makefile:249: run_tests] Error 2 make[2]: Leaving directory '/<>/build' make[1]: *** [debian/rules:7: override_dh_auto_test] Error 2 --- End Message --- --- Begin Message --- Source: cmake-extras Source-Version: 1.5-7 Done: Mike Gabriel We believe that the bug you reported is fixed in the latest version of cmake-extras, 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 973...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mike Gabriel (supplier of updated cmake-extras 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, 06 Nov 2020 16:22:28 +0100 Source: cmake-extras Architecture: source Version: 1.5-7 Distribution: unstable Urgency: medium Maintainer: Mike Gabriel Changed-By: Mike Gabriel Closes: 973095 Changes: cmake-extras (1.5-7) unstable; urgency=medium . * debian/patches: + Add Forwarded: URL to 1007_fix-FTCBFS-of-googlemock-projects.patch. * debian/control: + Add D (cmake-extras): pkg-config. (Closes: #973095). Checksums-Sha1: 18083b0a5b1577e2ab71d4f3677eed1721a16f53 2418 cmake-extras_1.5-7.dsc ff79b07977c7909846a5c19f7a2fd2aa53cd859e 11600 cmake-extras_1.5-7.debian.tar.xz 98b90df170a6385cbec3b131444a06c33232b44c 7421 cmake-extras_1.5-7_source.buildinfo Checksums-Sha256: a4b96bfc6d914901ee2b306eb5bbc682344e40fc9d970209e37f9bfe5e2b8722 2418 cmake-extras_1.5-7.dsc d71dbe68b8e78f7526e15cc4ac7da3538bff0a963f9f7521e45287691629f4b8 11600 cmake-extras_1.5-7.debian.tar.xz 6fecc5c0da764bf5b2138119603e950251d83d2c2643b1f1f778a7eedd5c5b2b 7421 cmake-extras_1.5-7_source.buildinfo Files: d376bec14fa583c71a8236a128e8c5c5 2418 devel optional cmake-extras_1.5-7.dsc d6b230c00254b726a27cbb8119176f59 11600 devel optional cmake-extras_1.5-7.debian.tar.xz bb8adb64e23334e338f140fdc34f7e85 7421 devel optional cmake-extras_1.5-7_source.buildinfo -BEGIN PGP SIGNATURE- iQJJBAEBCAAzFiEEm/uu6GwKpf+/IgeCmvRrMCV3GzEFAl+lakIVHHN1bndlYXZl ckBkZWJpYW4ub3JnAAoJEJr0azAldxsxdhMP/3ARA7gdcE5wg5xdChVij9GsKWi5 cLUeeWNZmdG73r/5/lzCEzTByviTkR/Ld+NXH/oLcDdg1fF99A52F249iEc3N56k 9Qu9dMJu+COY9zyaRzioxNa8iZAKK7zCV5Gpj6t2P2NKMmRp+i6a6vxZxjyuGBPh pmQlWLew9LqqKQNuUfGAF17EFpWzragsxgDRV+5dYQlg4ulFRcpBbdLuW6IY9+3r uhtXAZqz4BZMyH6H3TA/4ssCnKM0S6VAi3OIGAge5FtWSbUBynohcNBkyjEwcVJu cVKUDgGlnVUFvcagy2v/OJjG7nmGR9SkRWNEEIkWEjMNGjbgIW6MjvJKbPU8p5df
Bug#973290: marked as done (ros-ros ftbfs in unstable with python3.9)
Your message dated Fri, 06 Nov 2020 15:33:36 + with message-id and subject line Bug#973095: fixed in cmake-extras 1.5-7 has caused the Debian Bug report #973095, regarding ros-ros ftbfs in unstable with python3.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.) -- 973095: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973095 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:ros-ros Version: 1.15.7-1 Severity: serious Tags: sid bullseye ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.9 to reproduce, you can use the repositories found at: deb [trusted=yes] http://people.debian.org/~doko/tmp/python3.9 ./ deb [trusted=yes] http://people.debian.org/~ginggs/python3.9-repo ./ https://people.debian.org/~ginggs/python3.9-default/ros-ros_1.15.7-1+build1_amd64-2020-10-27T13:10:57Z.build [...] make -f core/roslib/CMakeFiles/roslib.dir/build.make core/roslib/CMakeFiles/roslib.dir/build make[3]: Entering directory '/<>/obj-x86_64-linux-gnu' make[3]: Entering directory '/<>/obj-x86_64-linux-gnu' make[3]: *** No rule to make target '/usr/lib/x86_64-linux-gnu/libpython3.8.so', needed by 'devel/lib/x86_64-linux-gnu/libroslib.so.1.15.7'. Stop. make[3]: *** Waiting for unfinished jobs the cmake output looks like it's using just python3, but apparently that gets translated to the wrong python3 version. --- End Message --- --- Begin Message --- Source: cmake-extras Source-Version: 1.5-7 Done: Mike Gabriel We believe that the bug you reported is fixed in the latest version of cmake-extras, 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 973...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mike Gabriel (supplier of updated cmake-extras 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, 06 Nov 2020 16:22:28 +0100 Source: cmake-extras Architecture: source Version: 1.5-7 Distribution: unstable Urgency: medium Maintainer: Mike Gabriel Changed-By: Mike Gabriel Closes: 973095 Changes: cmake-extras (1.5-7) unstable; urgency=medium . * debian/patches: + Add Forwarded: URL to 1007_fix-FTCBFS-of-googlemock-projects.patch. * debian/control: + Add D (cmake-extras): pkg-config. (Closes: #973095). Checksums-Sha1: 18083b0a5b1577e2ab71d4f3677eed1721a16f53 2418 cmake-extras_1.5-7.dsc ff79b07977c7909846a5c19f7a2fd2aa53cd859e 11600 cmake-extras_1.5-7.debian.tar.xz 98b90df170a6385cbec3b131444a06c33232b44c 7421 cmake-extras_1.5-7_source.buildinfo Checksums-Sha256: a4b96bfc6d914901ee2b306eb5bbc682344e40fc9d970209e37f9bfe5e2b8722 2418 cmake-extras_1.5-7.dsc d71dbe68b8e78f7526e15cc4ac7da3538bff0a963f9f7521e45287691629f4b8 11600 cmake-extras_1.5-7.debian.tar.xz 6fecc5c0da764bf5b2138119603e950251d83d2c2643b1f1f778a7eedd5c5b2b 7421 cmake-extras_1.5-7_source.buildinfo Files: d376bec14fa583c71a8236a128e8c5c5 2418 devel optional cmake-extras_1.5-7.dsc d6b230c00254b726a27cbb8119176f59 11600 devel optional cmake-extras_1.5-7.debian.tar.xz bb8adb64e23334e338f140fdc34f7e85 7421 devel optional cmake-extras_1.5-7_source.buildinfo -BEGIN PGP SIGNATURE- iQJJBAEBCAAzFiEEm/uu6GwKpf+/IgeCmvRrMCV3GzEFAl+lakIVHHN1bndlYXZl ckBkZWJpYW4ub3JnAAoJEJr0azAldxsxdhMP/3ARA7gdcE5wg5xdChVij9GsKWi5 cLUeeWNZmdG73r/5/lzCEzTByviTkR/Ld+NXH/oLcDdg1fF99A52F249iEc3N56k 9Qu9dMJu+COY9zyaRzioxNa8iZAKK7zCV5Gpj6t2P2NKMmRp+i6a6vxZxjyuGBPh pmQlWLew9LqqKQNuUfGAF17EFpWzragsxgDRV+5dYQlg4ulFRcpBbdLuW6IY9+3r uhtXAZqz4BZMyH6H3TA/4ssCnKM0S6VAi3OIGAge5FtWSbUBynohcNBkyjEwcVJu cVKUDgGlnVUFvcagy2v/OJjG7nmGR9SkRWNEEIkWEjMNGjbgIW6MjvJKbPU8p5df dsr+krRPzSbFCdBydeOOdmRhJZqiEBqqPnVBEGdMt5/Fn9jvSG1kS9ISxU5Ao6/B y6QHYZ1lGlGByyknCVPBaK95c/MyLmWQlW163AlPmWV01rKJGCfjb2ZwBq2kF6WO 6ZCEgd2pMBvLlJgAVa49DPqDbJ2m7RLNhiTPZSE6N0JZ+94s8mx6mwQhln+zL71n hxydZWczAuelJzU5LxJn4kGPHigf32yuPbJAmkYMu2/vAgwREKG3MdlytCGZZvB0 PiCYoN+bjsSuMf+FJHkHHuzjM3mbMHHTK1ixkREEq9USHI9Jw3O5HHi7m0Wx8gSK SuABiS1FeVJZNU4h =FlPF -END PGP SIGNATURE End Message ---
Bug#973095: marked as done (ros-angles: FTBFS: make[5]: *** No rule to make target 'gmock/libgmock.a', needed by 'devel/lib/angles/utest'. Stop.)
Your message dated Fri, 06 Nov 2020 15:33:36 + with message-id and subject line Bug#973095: fixed in cmake-extras 1.5-7 has caused the Debian Bug report #973095, regarding ros-angles: FTBFS: make[5]: *** No rule to make target 'gmock/libgmock.a', needed by 'devel/lib/angles/utest'. Stop. 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.) -- 973095: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973095 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ros-angles Version: 1.9.13-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201027 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[5]: Entering directory '/<>/build' > [ 90%] Building CXX object test/CMakeFiles/utest.dir/utest.cpp.o > cd /<>/build/test && /usr/bin/c++ -DGTEST_VERSION_MAJOR=1 > -DGTEST_VERSION_MINOR=8 -DGTEST_VERSION_PATCH=0 -DGTEST_VERSION_UNKNOWN > -DROS_BUILD_SHARED_LIBS=1 -I/<>/angles/include > -I/usr/src/googletest/googlemock/include > -I/usr/src/googletest/googletest/include -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -o > CMakeFiles/utest.dir/utest.cpp.o -c /<>/angles/test/utest.cpp > make[5]: *** No rule to make target 'gmock/libgmock.a', needed by > 'devel/lib/angles/utest'. Stop. > make[5]: Leaving directory '/<>/build' > make[4]: *** [CMakeFiles/Makefile2:324: test/CMakeFiles/utest.dir/all] Error 2 The full build log is available from: http://qa-logs.debian.net/2020/10/27/ros-angles_1.9.13-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: cmake-extras Source-Version: 1.5-7 Done: Mike Gabriel We believe that the bug you reported is fixed in the latest version of cmake-extras, 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 973...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mike Gabriel (supplier of updated cmake-extras 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, 06 Nov 2020 16:22:28 +0100 Source: cmake-extras Architecture: source Version: 1.5-7 Distribution: unstable Urgency: medium Maintainer: Mike Gabriel Changed-By: Mike Gabriel Closes: 973095 Changes: cmake-extras (1.5-7) unstable; urgency=medium . * debian/patches: + Add Forwarded: URL to 1007_fix-FTCBFS-of-googlemock-projects.patch. * debian/control: + Add D (cmake-extras): pkg-config. (Closes: #973095). Checksums-Sha1: 18083b0a5b1577e2ab71d4f3677eed1721a16f53 2418 cmake-extras_1.5-7.dsc ff79b07977c7909846a5c19f7a2fd2aa53cd859e 11600 cmake-extras_1.5-7.debian.tar.xz 98b90df170a6385cbec3b131444a06c33232b44c 7421 cmake-extras_1.5-7_source.buildinfo Checksums-Sha256: a4b96bfc6d914901ee2b306eb5bbc682344e40fc9d970209e37f9bfe5e2b8722 2418 cmake-extras_1.5-7.dsc d71dbe68b8e78f7526e15cc4ac7da3538bff0a963f9f7521e45287691629f4b8 11600 cmake-extras_1.5-7.debian.tar.xz 6fecc5c0da764bf5b2138119603e950251d83d2c2643b1f1f778a7eedd5c5b2b 7421 cmake-extras_1.5-7_source.buildinfo Files: d376bec14fa583c71a8236a128e8c5c5 2418 devel optional cmake-extras_1.5-7.dsc d6b230c00254b726a27cbb8119176f59 11600 devel optional cmake-extras_1.5-7.debian.tar.xz bb8adb64e23334e338f140fdc34f7e85 7421 devel optional cmake-extras_1.5-7_source.buildinfo -BEGIN PGP SIGNATURE- iQJJBAEBCAAzFiEEm/uu6GwKpf+/IgeCmvRrMCV3GzEFAl+lakIVHHN1bndlYXZl ckBkZWJpYW4ub3JnAAoJEJr0azAldxsxdhMP/3ARA7gdcE5wg5xdChVij9GsKWi5 cLUeeWNZmdG73r/5/lzCEzTByviTkR/Ld+NXH/oLcDdg1fF99A52F249iEc3N56k 9Qu9dMJu+COY9zyaRzioxNa8iZAKK7zCV5Gpj6t2P2NKMmRp+i6a6vxZxjyuGBPh pmQlWLew9LqqKQNuUfGAF17EFpWzragsxgDRV+5dYQlg4ulFRcpBbdLuW6IY9+3r uhtXAZqz4BZMyH6H3TA/4ssCnKM0S6VAi3OIGAge5FtWSbUBynohcN
Processed: Bug#973095 marked as pending in cmake-extras
Processing control commands: > tag -1 pending Bug #973095 [cmake-extras] ros-angles: FTBFS: make[5]: *** No rule to make target 'gmock/libgmock.a', needed by 'devel/lib/angles/utest'. Stop. Bug #973290 [cmake-extras] ros-ros ftbfs in unstable with python3.9 Bug #973291 [cmake-extras] ros-rospack ftbfs with new googletest Added tag(s) pending. Added tag(s) pending. Added tag(s) pending. -- 973095: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973095 973290: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973290 973291: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973291 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#973095: marked as pending in cmake-extras
Control: tag -1 pending Hello, Bug #973095 in cmake-extras 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/debian-ayatana-team/cmake-extras/-/commit/18f58363a054821365c88077579cf2d6d96a2f7b debian/control: Add D (cmake-extras): pkg-config. (Closes: #973095). (this message was generated automatically) -- Greetings https://bugs.debian.org/973095
Bug#971171: marked as done (libvirt-dbus: FTBFS: dh_auto_test: error: cd debian/build && LC_ALL=C.UTF-8 MESON_TESTTHREADS=4 ninja test returned exit code 1)
Your message dated Fri, 06 Nov 2020 14:49:51 + with message-id and subject line Bug#971171: fixed in libvirt-dbus 1.4.0-2 has caused the Debian Bug report #971171, regarding libvirt-dbus: FTBFS: dh_auto_test: error: cd debian/build && LC_ALL=C.UTF-8 MESON_TESTTHREADS=4 ninja test returned exit code 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.) -- 971171: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971171 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libvirt-dbus Version: 1.4.0-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200926 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_configure -- \ > -Dsystem_user=libvirtdbus > cd debian/build && LC_ALL=C.UTF-8 meson ../.. --wrap-mode=nodownload > --buildtype=plain --prefix=/usr --sysconfdir=/etc --localstatedir=/var > --libdir=lib/x86_64-linux-gnu -Dsystem_user=libvirtdbus > The Meson build system > Version: 0.55.3 > Source dir: /<> > Build dir: /<>/debian/build > Build type: native build > Project name: libvirt-dbus > Project version: 1.4.0 > Using 'CFLAGS' from environment with value: '-g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security' > Using 'LDFLAGS' from environment with value: '-Wl,-z,relro -Wl,-z,now' > Using 'CPPFLAGS' from environment with value: '-Wdate-time > -D_FORTIFY_SOURCE=2' > Using 'CFLAGS' from environment with value: '-g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security' > Using 'LDFLAGS' from environment with value: '-Wl,-z,relro -Wl,-z,now' > Using 'CPPFLAGS' from environment with value: '-Wdate-time > -D_FORTIFY_SOURCE=2' > C compiler for the host machine: cc (gcc 10.2.0 "cc (Debian 10.2.0-9) 10.2.0") > C linker for the host machine: cc ld.bfd 2.35.1 > Host machine cpu family: x86_64 > Host machine cpu: x86_64 > Found pkg-config: /usr/bin/pkg-config (0.29.2) > Run-time dependency gio-unix-2.0 found: YES 2.66.0 > Run-time dependency glib-2.0 found: YES 2.66.0 > Run-time dependency libvirt found: YES 6.6.0 > Run-time dependency libvirt-glib-1.0 found: YES 3.0.0 > Compiler for C supports arguments -W: YES > Compiler for C supports arguments -Waddress: YES > Compiler for C supports arguments -Waggressive-loop-optimizations: YES > Compiler for C supports arguments -Wall: YES > Compiler for C supports arguments -Warray-bounds=2: YES > Compiler for C supports arguments -Wattributes: YES > Compiler for C supports arguments -Wbad-function-cast: YES > Compiler for C supports arguments -Wbool-compare: YES > Compiler for C supports arguments -Wbuiltin-macro-redefined: YES > Compiler for C supports arguments -Wcast-align: YES > Compiler for C supports arguments -Wchar-subscripts: YES > Compiler for C supports arguments -Wclobbered: YES > Compiler for C supports arguments -Wcomment: YES > Compiler for C supports arguments -Wcomments: YES > Compiler for C supports arguments -Wcoverage-mismatch: YES > Compiler for C supports arguments -Wcpp: YES > Compiler for C supports arguments -Wdate-time: YES > Compiler for C supports arguments -Wdeprecated-declarations: YES > Compiler for C supports arguments -Wdesignated-init: YES > Compiler for C supports arguments -Wdiscarded-array-qualifiers: YES > Compiler for C supports arguments -Wdiscarded-qualifiers: YES > Compiler for C supports arguments -Wdiv-by-zero: YES > Compiler for C supports arguments -Wdouble-promotion: YES > Compiler for C supports arguments -Wduplicated-cond: YES > Compiler for C supports arguments -Wempty-body: YES > Compiler for C supports arguments -Wendif-labels: YES > Compiler for C supports arguments -Wextra: YES > Compiler for C supports arguments -Wformat: YES > Compiler for C supports arguments -Wformat-contains-nul: YES > Compiler for C supports arguments -Wformat-extra-args: YES > Compiler for C supports arguments -Wformat-nonliteral: YES > Compiler for C supports arguments -Wformat-security: YES > Compiler for C supports arguments -Wformat-y2k: YES > Compiler for C supports arguments -Wformat-zero-length: YES > Compiler for C supports arguments -Wframe-address: YES > Compiler for C supports arguments -Wframe-larger-than=1024: YES > Compiler for C supports arguments -Wfree-nonheap-object: YES > Compiler for C supports arguments -Whsa: YES > Compiler for C supports arguments -Wignored-attributes: YES > Compiler for C su
Bug#973883: [apt-cacher-ng] bad exit code (=0) instead (<>0) if Check permissions of /var/log/apt-cacher-ng
Package: apt-cacher-ng
Version: 3.2.1-1
Severity: grave
Dear maintainers,
It seems there is one bad exit code issue (=0) when trying to start
démon if internal check is bad. (/etc/init.d/apt-cacher-ng start)
ansible@srv-apt-cache-400:~$ dpkg -l |grep apt-cache
ii apt-cacher-ng 3.2.1-1 amd64
caching proxy server for software repositories
ansible@srv-apt-cache-400:~$ uname -a
Linux srv-apt-cache-400 4.19.0-12-amd64 #1 SMP Debian 4.19.152-1
(2020-10-18) x86_64 GNU/Linux
ansible@srv-apt-cache-400:~$ cat /etc/debian_version
10.6
ansible@srv-apt-cache-400:~$ pstree -anp
init,1
|-sshd,682
| |-sshd,717
| | `-sshd,719
| `-sshd,11014
| `-sshd,11016
| `-bash,11017
| `-pstree,11964 -anp
|-getty,696 38400 tty2
|-getty,697 38400 tty3
|-getty,698 38400 tty4
|-monit,7389 -c /etc/monit/monitrc
| |-{monit},7390
| |-{monit},7913
| `-(bash,11655)
|-syslog-ng,9901
| `-syslog-ng,9902 -p /var/run/syslog-ng.pid --no-caps
`-cron,17286
ansible@srv-apt-cache-400:~$ sudo /etc/init.d/apt-cacher-ng start
[] Starting apt-cacher-ng: apt-cacher-ngProblem creating log files.
Check permissions of the log directory, //var/log/apt-cacher-ng
failed!
ansible@srv-apt-cache-400:~$ echo $?
0
ansible@srv-apt-cache-400:~$
And, of course, this is true, because ...
ansible@srv-apt-cache-400:~$ sudo ls -altr /var/log/apt-cacher-ng
total 2
drwx-- 2 root root 1024 Nov 6 14:34 .
drwxr-xr-x 8 root root 1024 Nov 6 14:52 ..
Thanks in advance to correct this issue. In my use case, because i am
using Ansible to make deployment, it is then not possible to detect this
bug (because exit code = 0) in one automatic way
Best regards
Bug#922589: marked as done (FTBFS against opencv 4.0.1 (exp))
Your message dated Fri, 06 Nov 2020 14:50:33 + with message-id and subject line Bug#922589: fixed in opencfu 3.9.0-4 has caused the Debian Bug report #922589, regarding FTBFS against opencv 4.0.1 (exp) 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.) -- 922589: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922589 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: opencfu Version: 3.9.0-3 Severity: important pkg-config file has been marked deprecated by upstream. opencfu_3.9.0-3_ppc64el-2019-02-15T11:23:33Z.build.zst Description: Binary data --- End Message --- --- Begin Message --- Source: opencfu Source-Version: 3.9.0-4 Done: Andreas Tille We believe that the bug you reported is fixed in the latest version of opencfu, 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. Andreas Tille (supplier of updated opencfu 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, 06 Nov 2020 15:04:06 +0100 Source: opencfu Architecture: source Version: 3.9.0-4 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andreas Tille Closes: 922589 Changes: opencfu (3.9.0-4) unstable; urgency=medium . [ Andreas Tille ] * Standards-Version: 4.5.0 (routine-update) * debhelper-compat 12 (routine-update) * Secure URI in copyright format (routine-update) * Trim trailing whitespace. * Set upstream metadata fields: Repository. * Point watch file to Github * Detect opencv4.pc . [ Alex Dewar ] * Fix build on OpenCV v4+ Closes: #922589 Checksums-Sha1: dd89c552ddc6273f34a17ea040b1cf918ef2f232 1994 opencfu_3.9.0-4.dsc 73ee5dd041159614c8cb626d88abc4318a542bed 25340 opencfu_3.9.0-4.debian.tar.xz 803326f2519315618851644863c87ab1af1bd43a 20206 opencfu_3.9.0-4_amd64.buildinfo Checksums-Sha256: 26bc0af902d8d48e36e46f3813af3b956f9a358e98487e3278db123f6ce8358d 1994 opencfu_3.9.0-4.dsc e98cbdb75fc940b0fdaf72e99b4c1bc303189b394ad3afca4e7ffc0ea0635c17 25340 opencfu_3.9.0-4.debian.tar.xz 1e2a6230c630a6172e61bed6c5efa9ed238304da145692f1fb227d6b3d66361d 20206 opencfu_3.9.0-4_amd64.buildinfo Files: 648a1e7355d1dc9d29aebf90a14e1bc5 1994 misc optional opencfu_3.9.0-4.dsc adf381aad8d65b3257881085d722a2aa 25340 misc optional opencfu_3.9.0-4.debian.tar.xz 5549002e5786d119486ce3a9f1c9c156 20206 misc optional opencfu_3.9.0-4_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl+lWXcRHHRpbGxlQGRl Ymlhbi5vcmcACgkQV4oElNHGRtFUJw//W6T0lDLaFoBkT+JH2m/RmwKXrUF9lhp3 hXLGNoKRRsO9JehhjO81FpqTXshEfeRcmsxZPN56TgoqIA7ohd7N8AbjtniB7Bgg EZZzqevnGM5THss13ZU1mmfFcMK/xNhcXpEajiNUscOQhBen2ALO3VlYf9YjdEwa wNLbHYBU8IAmUnZU2BRPtI4SKIIRHyBUozUSjI5nLiTCLC2BRXI/DG4v43nhDLfv 0gM7jxClgTkkJPg/rZUWdgJ1AQcQJkD3Wgo1yjPkDDG++xuVZzmnn0lHX8lLQJZa 5fzCMfxskD2rrzJllMyZrsBNsVOSJ+JFIZQCO1PKZ+SRDJRuIxY+eZNhF52urBRS YYCph1IFIQnXkFn/KtZcECLGMv7WjtW2WHOI6d5wmXVBIdc2EguMZyMjvMrtI2AQ 05TPfA7oypWDXq4jGqfwvk0hl6pgSixYfhqOEFqdGlBUxs5ttcd1jXKMzxP560Zv uI2pl9YPj67GVRyaGp08nRHxo/jpmA4oCF4pmgkP6AT4rjiNMtlTAdYQZy6ORPwr e1d798h41a/k/YvjplF/YD8P8K7z6WOGLwZyFivBk4IrgpL+XWqxE/tpL1bVvTpS XwDEuQMkyOUp3DncZNXKFJ496ppie1a/ATuPjM49XRJPz9Jtu1IcM49C7LULgOW3 2ERje29sPR0= =K5YC -END PGP SIGNATURE End Message ---
Processed: Still fine in unstable
Processing control commands: > severity -1 important Bug #972769 [src:libsigrokdecode] libsigrokdecode ftbfs with python3.9 Severity set to 'important' from 'serious' > tag -1 pending Bug #972769 [src:libsigrokdecode] libsigrokdecode ftbfs with python3.9 Added tag(s) pending. -- 972769: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972769 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#972769: Still fine in unstable
Control: severity -1 important Control: tag -1 pending This is still building fine with the python3-defaults in unstable so doesn't warrant the serious severity. Upstream has a minor fix to enable Python3.9 which I will pull in. J. -- /-\ | 101 things you can't have too much |@/ Debian GNU/Linux Developer | of : 18 - Roleplaying. \- |
Bug#973858: chromium: Outdated version, more than 100 open security issues
Package: chromium Version: 84.0.4147.105-1 Severity: grave Tags: security Justification: user security hole X-Debbugs-Cc: Debian Security Team Versions in Debian, even that in experimental have 100+ open unfixed CVE listed in the tracker. https://security-tracker.debian.org/tracker/source-package/chromium Many of those are just a few days old. This is related to bug#973848 but underlines the security side importance. Thanks.
Bug#969372: uwsgi-emperor: SysV init script does nothing
Hi there I encounter the exact same behaviour with: /etc/debian_version: bullseye/sid dpkg -l | grep uwsgi: ii uwsgi-core2.0.19.1-3+b1 amd64 fast, self-healing application container server (core) ii uwsgi-emperor 2.0.19.1-3+b1 amd64 fast, self-healing application container server (emperor scripts) ii uwsgi-plugin-python3 2.0.19.1-3+b1 amd64 WSGI plugin for uWSGI (Python 3) changes in /etc/uwsgi-emperor/emperor.ini: + emperor-on-demand-directory = /var/uwsgi Sam Quoting Vlastimil Zima (2020-11-06 15:36:47) > Package: uwsgi-emperor > Version: 2.0.19.1-3+b1 > Followup-For: Bug #969372 > > Hi Thomas, > > indeed, I have a number of vassals configured, actually I use emperor > for web development for several years now. > > At first, I noticed that the emperor haven't start after reboot. > I have tried to start it with systemd, but with no success. Systemd > only reports the process as "started" but it's not running > (`ps -ef | grep uwsgi`). > > > Here's a relevant output of terminal commands: > > $ sudo service uwsgi-emperor start > $ sudo service uwsgi-emperor status > ● uwsgi-emperor.service - LSB: Start/stop uWSGI server instance(s) > Loaded: loaded (/etc/init.d/uwsgi-emperor; generated) > Active: active (exited) since Fri 2020-11-06 09:23:17 CET; 1s ago >Docs: man:systemd-sysv-generator(8) > Process: 889151 ExecStart=/etc/init.d/uwsgi-emperor start (code=exited, > status=0/SUCCESS) > > Nov 06 09:23:17 queeg-500 systemd[1]: Starting LSB: Start/stop uWSGI server > instance(s)... > Nov 06 09:23:17 queeg-500 systemd[1]: Started LSB: Start/stop uWSGI server > instance(s). > $ ps -ef | grep uwsgi > vzima 889177 887414 0 09:23 pts/500:00:00 grep uwsgi > > > Despite this, I can start the emperor manually using command composed on > /etc/init.d/uwsgi-emperor: > > $ sudo /usr/bin/uwsgi --ini /etc/uwsgi-emperor/emperor.ini --die-on-term > --pidfile /run/uwsgi-emperor.pid --daemonize /var/log/uwsgi/emperor.log > > I also encounter the PID file bug > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934731, > so I need to delete PID file manually. > > Regards, > > Vlastimil Zíma > > -- System Information: > Debian Release: bullseye/sid > APT prefers testing > APT policy: (500, 'testing'), (90, 'unstable') > Architecture: amd64 (x86_64) > > Kernel: Linux 5.8.0-2-amd64 (SMP w/8 CPU threads) > Kernel taint flags: TAINT_FIRMWARE_WORKAROUND > Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8), > LANGUAGE=en_US:en > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > Versions of packages uwsgi-emperor depends on: > ii uwsgi-core 2.0.19.1-3+b1 > > uwsgi-emperor recommends no packages. > > uwsgi-emperor suggests no packages. > > -- Configuration Files: > /etc/uwsgi-emperor/emperor.ini changed: > [uwsgi] > master = true > workers = 2 > no-orphans = true > log-date = true > uid = www-data > gid = www-data > emperor = /etc/uwsgi-emperor/vassals > emperor-tyrant = true > cap = setgid,setuid > > > -- no debconf information signature.asc Description: signature
Processed: closing 871564
Processing commands for cont...@bugs.debian.org: > close 871564 Bug #871564 [src:manpages-fr] manpages-fr outdated Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 871564: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871564 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#871564: closing 871564
close 871564 thanks This is probably fixed by the switch to a new upstream
Bug#973232: marked as done (minexpert2: FTBFS: ProgramWindow.cpp:2318:58: error: no matching function for call to ‘pappso::ColorMapPlotConfig::ColorMapPlotConfig(pappso::DataKind&, pappso::DataKind, s
Your message dated Fri, 06 Nov 2020 11:03:33 + with message-id and subject line Bug#973232: fixed in minexpert2 7.3.0-1 has caused the Debian Bug report #973232, regarding minexpert2: FTBFS: ProgramWindow.cpp:2318:58: error: no matching function for call to ‘pappso::ColorMapPlotConfig::ColorMapPlotConfig(pappso::DataKind&, pappso::DataKind, std::size_t, std::size_t, double, double, double, double)’ 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.) -- 973232: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973232 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: minexpert2 Version: 7.2.0-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201027 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > cd /<>/debian/build/src && /usr/bin/c++ > -DQCUSTOMPLOT_USE_LIBRARY -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NO_DEBUG > -DQT_NO_DEBUG_OUTPUT -DQT_PRINTSUPPORT_LIB -DQT_SVG_LIB -DQT_WIDGETS_LIB > -DQT_XML_LIB -I/<>/debian/build/src -I/<>/src > -I/<>/debian/build/src/minexpert2_autogen/include > -I/<>/debian/build -I/<> -isystem > /usr/include/x86_64-linux-gnu/qt5 -isystem > /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem > /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem > /usr/include/x86_64-linux-gnu/qt5/QtCore -isystem > /usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -isystem > /usr/include/x86_64-linux-gnu/qt5/QtXml -isystem > /usr/include/x86_64-linux-gnu/qt5/QtSvg -isystem > /usr/include/x86_64-linux-gnu/qt5/QtPrintSupport -isystem > /usr/include/IsoSpec++ -isystem /usr/include/pappsomspp -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -fopenmp -O3 -DNDEBUG -Wno-unknown-pragmas -Wall > -pedantic -Wextra -fPIC -std=gnu++17 -o > CMakeFiles/minexpert2.dir/gui/ProgramWindow.cpp.o -c > /<>/src/gui/ProgramWindow.cpp > /<>/src/gui/ProgramWindow.cpp: In member function ‘void > msxps::minexpert::ProgramWindow::finishedIntegratingQualifiedMassSpectrumVectorToDtRtMz(msxps::minexpert::QualifiedMassSpectrumVectorMassDataIntegrator*)’: > /<>/src/gui/ProgramWindow.cpp:2318:58: error: no matching > function for call to > ‘pappso::ColorMapPlotConfig::ColorMapPlotConfig(pappso::DataKind&, > pappso::DataKind, std::size_t, std::size_t, double, double, double, double)’ > 2318 | qualified_mass_spectra_integrator->getColorMapMaxMz()); > | ^ > In file included from /<>/src/gui/BaseColorMapPlotWnd.hpp:44, > from > /<>/src/gui/DriftSpecMassSpecColorMapWnd.hpp:46, > from /<>/src/gui/ProgramWindow.hpp:71, > from /<>/src/gui/ProgramWindow.cpp:63: > /usr/include/pappsomspp/widget/plotwidget/colormapplotconfig.h:42:3: note: > candidate: ‘pappso::ColorMapPlotConfig::ColorMapPlotConfig(pappso::DataKind, > pappso::DataKind, pappso::AxisScale, pappso::AxisScale, pappso::AxisScale, > std::size_t, std::size_t, double, double, double, double)’ >42 | ColorMapPlotConfig(DataKind x_axis_data_kind, > | ^~ > /usr/include/pappsomspp/widget/plotwidget/colormapplotconfig.h:42:3: note: > candidate expects 11 arguments, 8 provided > /usr/include/pappsomspp/widget/plotwidget/colormapplotconfig.h:40:3: note: > candidate: ‘pappso::ColorMapPlotConfig::ColorMapPlotConfig()’ >40 | ColorMapPlotConfig(); > | ^~ > /usr/include/pappsomspp/widget/plotwidget/colormapplotconfig.h:40:3: note: > candidate expects 0 arguments, 8 provided > /usr/include/pappsomspp/widget/plotwidget/colormapplotconfig.h:22:23: note: > candidate: ‘constexpr pappso::ColorMapPlotConfig::ColorMapPlotConfig(const > pappso::ColorMapPlotConfig&)’ >22 | struct PMSPP_LIB_DECL ColorMapPlotConfig > | ^~ > /usr/include/pappsomspp/widget/plotwidget/colormapplotconfig.h:22:23: note: > candidate expects 1 argument, 8 provided > /usr/include/pappsomspp/widget/plotwidget/colormapplotconfig.h:22:23: note: > candidate: ‘constexpr > pappso::ColorMapPlotConfig::ColorMapPlotConfig(pappso::ColorMapPlotConfig&&)’ > /usr/include/pappsomspp/widget/plotwidget/colormapplotconfig.h:22:23: note: > candidate expects 1 argument, 8 provided > /<>/src/gui/ProgramWindow.cpp: In member function ‘void > msxps::minexpert::ProgramWindow::finishedIntegratingQualifiedMassSpectrumVectorToRtDt(msxps::minexpert::QualifiedMassSpectrumVectorMassDataIntegrator*)’: > /<>/src/gui
Bug#972140: marked as done (libsass-python tries to download code from the net for the build)
Your message dated Fri, 06 Nov 2020 10:48:28 +
with message-id
and subject line Bug#972140: fixed in libsass-python 0.20.1-2
has caused the Debian Bug report #972140,
regarding libsass-python tries to download code from the net for the build
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.)
--
972140: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972140
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libsass-python
Version: 0.20.1-1
Severity: serious
Tags: sid bullseye
libsass-python tries to download code from the net for the build, apparently
some sphinx build dependencies are missing.
[...]
# build doc once
pybuild -s custom --build -p 3.8 \
--build-args="env PYTHONPATH={build_dir} python3 -m sphinx -N -bman
docs/
build/man"
I: pybuild base:217: env PYTHONPATH=/<>/.pybuild/cpython3_3.8/build
python3 -m sphinx -N -bman docs/ build/man
Running Sphinx v3.2.1
making output directory... done
WARNING: html_static_path entry '_static' does not exist
loading intersphinx inventory from https://docs.python.org/objects.inv...
loading intersphinx inventory from
https://setuptools.readthedocs.io/en/latest/objects.inv...
WARNING: failed to reach any of the inventories with the following issues:
intersphinx inventory 'https://setuptools.readthedocs.io/en/latest/objects.inv'
not fetchable due to :
HTTPSConnectionPool(host='setuptools.readthedocs.io', port=443): Max retries
exceeded with url: /en/latest/objects.inv (Caused by ProxyError('Cannot connect
to proxy.', NewConnectionError(': Failed to establish a new connection: [Errno 111] Connection
refused')))
loading intersphinx inventory from http://flask.pocoo.org/docs/objects.inv...
WARNING: failed to reach any of the inventories with the following issues:
intersphinx inventory 'https://docs.python.org/objects.inv' not fetchable due to
:
HTTPSConnectionPool(host='docs.python.org', port=443): Max retries exceeded with
url: /objects.inv (Caused by ProxyError('Cannot connect to proxy.',
NewConnectionError(': Failed to establish a new connection: [Errno 111] Connection
refused')))
WARNING: failed to reach any of the inventories with the following issues:
intersphinx inventory 'http://flask.pocoo.org/docs/objects.inv' not fetchable
due to :
HTTPConnectionPool(host='127.0.0.1', port=9): Max retries exceeded with url:
http://flask.pocoo.org/docs/objects.inv (Caused by ProxyError('Cannot connect to
proxy.', NewConnectionError(': Failed to establish a new connection: [Errno 111] Connection
refused')))
building [mo]: targets for 0 po files that are out of date
--- End Message ---
--- Begin Message ---
Source: libsass-python
Source-Version: 0.20.1-2
Done: =?utf-8?b?RnLDqWTDqXJpYyBCb25uYXJk?=
We believe that the bug you reported is fixed in the latest version of
libsass-python, 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 972...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Frédéric Bonnard (supplier of updated libsass-python
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, 06 Nov 2020 11:23:10 +0100
Source: libsass-python
Architecture: source
Version: 0.20.1-2
Distribution: sid
Urgency: medium
Maintainer: Frédéric Bonnard
Changed-By: Frédéric Bonnard
Closes: 971527 972140
Changes:
libsass-python (0.20.1-2) unstable; urgency=medium
.
* Avoid code download during doc build (Closes: #972140)
* Make the build reproducible (Closes: #971527)
Checksums-Sha1:
4cdb9d9159a3ba265885dc5bb6cc9f4dc3bd56ee 2182 libsass-python_0.20.1-2.dsc
60d8a05701fd3a6b729bfdfe535c45473a138346 5296
libsass-python_0.20.1-2.debian.tar.xz
5e445e81e693e8f14912943d465a2600d4e44080 8832
libsass-python_0.20.1-2_ppc64el.buildinfo
Checksums-Sha256:
864383f54eec949f57532ee08c6471a97071cce1b999077bb96c9681a1e58a70 2182
libsass-python_0.20.1-2.dsc
82729df305143712c4dd8d30b76460c7c324b4996f18996288dc12034e25bbde 5296
libsass-python_0.20.1-2.debian.tar.xz
8a47cd86319514c9dff67599f4bee04c518601826445bdb8e9c52671665e2790 8832
libsass-python_0.20.1-2_ppc64el.buildinfo
Files:
84a6d4486ec3fad5370f801cf564ce7d 2182 python optional
libsass-python_0.20.1
Bug#950929: marked as done (python-biom-format: FTBFS with pandas 1.0: test failures)
Your message dated Fri, 06 Nov 2020 10:49:57 + with message-id and subject line Bug#950929: fixed in python-biom-format 2.1.9-1 has caused the Debian Bug report #950929, regarding python-biom-format: FTBFS with pandas 1.0: test failures 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.) -- 950929: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950929 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-biom-format Version: 2.1.8+dfsg-1 Control: block 950430 by -1 With pandas 1.0 from experimental: == ERROR: test_to_dataframe (biom.tests.test_table.TableTests) -- Traceback (most recent call last): File "/build/python-biom-format-2.1.8+dfsg/.pybuild/cpython3_3.8_biom-format/build/biom/tests/test_table.py", line 1476, in test_to_dataframe exp = pd.SparseDataFrame(np.array([[0.0, 1.0, 2.0], [3.0, 4.0, 5.0]]), TypeError: SparseDataFrame() takes no arguments == ERROR: test_to_dataframe_is_sparse (biom.tests.test_table.TableTests) -- Traceback (most recent call last): File "/build/python-biom-format-2.1.8+dfsg/.pybuild/cpython3_3.8_biom-format/build/biom/tests/test_table.py", line 1484, in test_to_dataframe_is_sparse df = example_table.to_dataframe() File "/build/python-biom-format-2.1.8+dfsg/.pybuild/cpython3_3.8_biom-format/build/biom/table.py", line 4053, in to_dataframe return constructor(mat, index=index, columns=columns) TypeError: SparseDataFrame() takes no arguments -- Ran 343 tests in 5.493s --- End Message --- --- Begin Message --- Source: python-biom-format Source-Version: 2.1.9-1 Done: cru...@debian.org (Michael R. Crusoe) We believe that the bug you reported is fixed in the latest version of python-biom-format, 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 950...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael R. Crusoe (supplier of updated python-biom-format 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, 06 Nov 2020 11:23:23 +0100 Source: python-biom-format Architecture: source Version: 2.1.9-1 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Michael R. Crusoe Closes: 950929 Changes: python-biom-format (2.1.9-1) unstable; urgency=medium . * Team Upload. . [ Andreas Tille ] * New upstream version Closes: #950929 * Build-Depends: python3-pytest . [ Michael R. Crusoe ] * Build-Depends: python3-pytest-cov Checksums-Sha1: fbd0c40577c86253a8ddbb464d5fbc6e7d58134b 2564 python-biom-format_2.1.9-1.dsc 7abf39de22fe35b8a4bfdd830d27ed7aa42ae8f7 8531448 python-biom-format_2.1.9.orig.tar.xz 1cf17c863e06ffa45b32f602921fa7183eb472a6 10412 python-biom-format_2.1.9-1.debian.tar.xz ebeba3fdd2fe9ee919cb6328cadbc9a5b9bafd2c 10037 python-biom-format_2.1.9-1_source.buildinfo Checksums-Sha256: 787f8d1d43c4464335188b0290127c2e9dc119bc475a6391ec568380d2af52f3 2564 python-biom-format_2.1.9-1.dsc 5668128de885ece5702c4965f9878ecf4d510c43d8290654d063733cfd58173c 8531448 python-biom-format_2.1.9.orig.tar.xz ed10111203a55cb0c13e0f844b11e6bb13c692dd6747b8f9b8437411d224a4aa 10412 python-biom-format_2.1.9-1.debian.tar.xz abb92624e3302f24b4e7f15db59bebddfad0a9cc5316290bddf3b1d45df85293 10037 python-biom-format_2.1.9-1_source.buildinfo Files: a5bc209e2375d002078f422f0f04e0d3 2564 python optional python-biom-format_2.1.9-1.dsc 4036809972030fd184bca4557a3ad2bf 8531448 python optional python-biom-format_2.1.9.orig.tar.xz 5d17f92b52a028556232b0289a1c984b 10412 python optional python-biom-format_2.1.9-1.debian.tar.xz e1ad1e96725cd46e7d5f9a3ab674abfa 10037 python optional python-biom-format_2.1.9-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEck1gkzcRPHEFUNdHPCZ2P2xn5uIFAl+lJFQACgkQPCZ2P2xn 5uLt6g//Q3fKsiDH29aoHaSW7FifsR+
Bug#973794: marked as done (pybind11's autopkg tests fail)
Your message dated Fri, 06 Nov 2020 10:49:49 + with message-id and subject line Bug#973794: fixed in pybind11 2.6.0-2 has caused the Debian Bug report #973794, regarding pybind11's autopkg tests fail 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.) -- 973794: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973794 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:pybind11 Version: 2.6.0-1 Severity: serious Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: python3.9 command4 still fails: [...] [100%] Built target pybind11_tests Failed to import pybind11_tests from pytest: ModuleNotFoundError: No module named 'pybind11_tests' autopkgtest [17:15:08]: test command4: --- End Message --- --- Begin Message --- Source: pybind11 Source-Version: 2.6.0-2 Done: Drew Parsons We believe that the bug you reported is fixed in the latest version of pybind11, 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 973...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Drew Parsons (supplier of updated pybind11 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, 06 Nov 2020 18:09:24 +0800 Source: pybind11 Architecture: source Version: 2.6.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Drew Parsons Closes: 973794 Changes: pybind11 (2.6.0-2) unstable; urgency=medium . * Team upload. * update debian patch test_cmake_pyversion.patch to process PYVERSION to find python before using PYTHON_VERSION. Otherwise test_async is skipped. Closes: #973794. * use help2man to generate a manpage for pybind11-config Checksums-Sha1: 999de44c8e5d8601bebea6650c3a0691e7093ec9 2602 pybind11_2.6.0-2.dsc ccad385f9989ce767400fe987f8ea9648683b222 66688 pybind11_2.6.0-2.debian.tar.xz Checksums-Sha256: 9746f8c94a51c0de369475e89fd544cd39b8923ca08c15c3cfbc2fde75c408a6 2602 pybind11_2.6.0-2.dsc 76e81e3e7642bc0e82f135cef73dc38e29b189954e5f3acbf29e10a810e310ce 66688 pybind11_2.6.0-2.debian.tar.xz Files: 3609e480d639d7388b38ab7ec6ac0692 2602 libs optional pybind11_2.6.0-2.dsc 1866998c5d2969b94f3d301301dc87cf 66688 libs optional pybind11_2.6.0-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEI8mpPlhYGekSbQo2Vz7x5L1aAfoFAl+lJp8ACgkQVz7x5L1a Afr7hBAAh0lBGlbZy4ThL2dyirIyunJ1uz3z26huW+z3OIJt2e0v2psajC926Mn1 AF8M/f7uaZ6qmBF4bjeO51Ftt/7hr9zfGC/sqOs4/dE91UYBeIUJ0su94sfyi+Te u/z6p4LTfD15U5HX5Ye/8/57Cvdv+JmMDmpHYL2GZafK5S756ZrB5tvn9m70o8VC jzt5muxmz1WIFoDNv7P6HA9n3NzFybb7j6iwpMViiq12VhACHqQE49sjfxn1dDby 4ylyoCRLYYDct6EMRDMW1xPjIQnDe2JjYDnVhwBCvh4Rd5FDnB2NO9AxqudI458b 0TDI5n44DIt3ukjCj1K9ulz63NwRvx+5Kf2punBzAysw4zD9OKijVRlJisKm+1WD /qoVSmnk1RAbYjxBOgQRhf+0rXsl4R1ZgAaCB17oyDcIM81ueEjIeEISdWy82bN3 otO11lR+xT83A7dmvy43TfGlmPY0cA+DaGJohDzZlS2xkrzSECojCeDn4G2dGJPk LgwsBUIz/lBwn9KhnL27HbboFV4hiWpRbqN1u9BlZXPvz89MEfod+XA+fULUV6zO YNfHjoZSnhWnxyttCVkgXwEQiH6XfAi6PTOoWE8FgotFdlE4lG/1Mdp1Ejf9MIwh M5XT6dxw5Q0swNF8wBBmgGx31Zqg5Qt0lhz+BckTf3FMk3Pf2nU= =9NaT -END PGP SIGNATURE End Message ---
Bug#973804: marked as done (bcbio: FTBFS undeclared build-dependency on git)
Your message dated Fri, 06 Nov 2020 10:33:22 +
with message-id
and subject line Bug#973804: fixed in bcbio 1.2.4-2
has caused the Debian Bug report #973804,
regarding bcbio: FTBFS undeclared build-dependency on git
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.)
--
973804: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973804
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bcbio
Version: 1.2.4-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source
https://buildd.debian.org/status/fetch.php?pkg=bcbio&arch=all&ver=1.2.4-1&stamp=1603386246&raw=0
debian/rules clean
dh clean --with python3,sphinxdoc --buildsystem=pybuild
debian/rules override_dh_auto_clean
make[1]: Entering directory '/<>'
dh_auto_clean
install -d /<>/debian/.debhelper/generated/_source/home
pybuild --clean --test-pytest -i python{version} -p "3.9 3.8"
I: pybuild base:217: python3.9 setup.py clean
Traceback (most recent call last):
File "/<>/setup.py", line 14, in
git_run = subprocess.run(['git', 'rev-parse', '--short', 'HEAD'],
stdout=subprocess.PIPE)
File "/usr/lib/python3.9/subprocess.py", line 501, in run
with Popen(*popenargs, **kwargs) as process:
File "/usr/lib/python3.9/subprocess.py", line 947, in __init__
self._execute_child(args, executable, preexec_fn, close_fds,
File "/usr/lib/python3.9/subprocess.py", line 1819, in _execute_child
raise child_exception_type(errno_num, err_msg, err_filename)
FileNotFoundError: [Errno 2] No such file or directory: 'git'
E: pybuild pybuild:352: clean: plugin distutils failed with: exit code=1:
python3.9 setup.py clean
dh_auto_clean: error: pybuild --clean --test-pytest -i python{version} -p "3.9
3.8" returned exit code 13
make[1]: *** [debian/rules:44: override_dh_auto_clean] Error 25
make[1]: Leaving directory '/<>'
make: *** [debian/rules:10: clean] Error 2
Andreas
--- End Message ---
--- Begin Message ---
Source: bcbio
Source-Version: 1.2.4-2
Done: Andreas Tille
We believe that the bug you reported is fixed in the latest version of
bcbio, 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 973...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Tille (supplier of updated bcbio 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, 06 Nov 2020 11:16:33 +0100
Source: bcbio
Architecture: source
Version: 1.2.4-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team
Changed-By: Andreas Tille
Closes: 973804
Changes:
bcbio (1.2.4-2) unstable; urgency=medium
.
* Team upload.
* Avoid calling Git - use Debian version to specify the code version
Closes: #973804
Checksums-Sha1:
849bd20307aec4567ce36df8e5f52381c31b453a 2930 bcbio_1.2.4-2.dsc
5ed93a8ea321ffeb3bbf4c5ba7cffa4c9cb56cdd 12268 bcbio_1.2.4-2.debian.tar.xz
6ca0a49da267aa17a44dd3e32d313741b5dc3f26 14959 bcbio_1.2.4-2_amd64.buildinfo
Checksums-Sha256:
afa9bcb3d48ba162876b932bcb4114e6d39c4d693863989079265f0d5e149243 2930
bcbio_1.2.4-2.dsc
dc3673807dd9e5d14551aa11eac0fb1f43cdbed42743ccc1767342a2a67845e5 12268
bcbio_1.2.4-2.debian.tar.xz
92c7d1b398fe275963f7d5c64f9d165b6204a4331404e6a3f5b1a31b23858ede 14959
bcbio_1.2.4-2_amd64.buildinfo
Files:
7ed20f6e6e8b252886f9d8e4aea9a4f3 2930 contrib/science optional
bcbio_1.2.4-2.dsc
f276cfc9730d438df82297a8cc038604 12268 contrib/science optional
bcbio_1.2.4-2.debian.tar.xz
3feae8bd2e412c59b418ea6302450366 14959 contrib/science optional
bcbio_1.2.4-2_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl+lJBcRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtHDrw/5AQkyCig0OX8FFGJt/WRvyFD7I7pvw3gd
haEdENTbyLFzObwpAQYftJOvdpYaDhsKsOPnv280kn0+XYZGgIoB3k5/asixxiym
EEado3KmYXp8HH/Dq5blC2rVf08LGLyE4jPtEjAa3R2Q/Om941QHaCAn20EgfoGL
emYuKEoRww0vGyiChpzjI2tjZYQoZBD7dyyObQTSI7EcYPN80ifPBEVRbMbZcn29
A42e21WBs+v3GnkmMUtMVb4QhCwI4UclPQF8O3in4NVIGrlS6wZ/XkTe5McE4EBV
xOG2pqKQOn+1o/MshLqGLHT4sSsMILZHxO5AcosoeJf0VmJ2Slf4E0gsygdi/na5
5JYlZVzHyoACaaQ4q0l/V3D+0/B9Oo0IDR/KGPGp+ZCkpSoB/TgOQ7sQfFx2SAam
yX6JJrfc+FGjjjCOU/FDc5lN0BZsX7FzFqyfSlWO7GtJPFXOk2gCE1QG
Bug#973871: gnustep-icons: invalid maintainer address
Source: gnustep-icons Version: 1.0-8 Severity: serious X-Debbugs-Cc: Gürkan Myczko , ba...@debian.org The maintainer address is invalid, see bounce message below. Three other packages also have the same invalid address: chess.app, fontmanager.app and price.app. Ansgar On Wed, 2020-11-04 at 18:16 +, Mail Delivery System wrote: > This message was created automatically by mail delivery software. > > A message that you sent could not be delivered to one or more of its > recipients. This is a permanent error. The following address(es) failed: > > pkg-gnustep-maintain...@lists.debian.org > host bendel.debian.org [2001:41b8:202:deb:216:36ff:fe40:4002] > SMTP error from remote mail server after RCPT > TO:: > 550 5.1.1 : > Recipient address rejected: User unknown in virtual alias table
Bug#973868: satpy: autopkgtest failure with pyproj 3.0.0
Source: satpy Version: 0.23.0-1 Severity: serious Tags: ftbfs Justification: makes the package in question unusable or mostly so Dear Maintainer, The autopkgtest of your package fail with pyproj 3.0.0: === python3.9 === satpy (unittest.loader._FailedTest) ... ERROR == ERROR: satpy (unittest.loader._FailedTest) -- ImportError: Failed to import test module: satpy Traceback (most recent call last): File "pyresample/ewa/_ll2cr.pyx", line 27, in pyresample.ewa._ll2cr ModuleNotFoundError: No module named 'pyproj._proj' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3.9/unittest/loader.py", line 154, in loadTestsFromName module = __import__(module_name) File "/usr/lib/python3/dist-packages/satpy/__init__.py", line 33, in from satpy.readers import (find_files_and_readers, # noqa File "/usr/lib/python3/dist-packages/satpy/readers/__init__.py", line 34, in from .yaml_reader import (AbstractYAMLReader, File "/usr/lib/python3/dist-packages/satpy/readers/yaml_reader.py", line 41, in from satpy.resample import get_area_def File "/usr/lib/python3/dist-packages/satpy/resample.py", line 144, in from pyresample.ewa import fornav, ll2cr File "/usr/lib/python3/dist-packages/pyresample/ewa/__init__.py", line 72, in from pyresample.ewa import _ll2cr, _fornav File "pyresample/ewa/_ll2cr.pyx", line 30, in init pyresample.ewa._ll2cr ModuleNotFoundError: No module named 'pyproj._proj' -- Ran 1 test in 0.000s FAILED (errors=1) https://ci.debian.net/data/autopkgtest/unstable/amd64/s/satpy/7973931/log.gz Kind Regards, Bas
Bug#973867: pyresample: autopkgtest failure with pyproj 3.0.0
Source: pyresample Version: 1.16.0+ds-2 Severity: serious Tags: ftbfs Justification: makes the package in question unusable or mostly so Dear Maintainer, The autopkgtest of your package fail with python-pyproj 3.0.0, the log shows many issues like this: E ModuleNotFoundError: No module named 'pyproj._proj' https://ci.debian.net/data/autopkgtest/unstable/amd64/p/pyresample/7973930/log.gz Kind Regards, Bas
Bug#973846: marked as done (manpages: file conflict with manpages-dev=5.08-1)
Your message dated Fri, 06 Nov 2020 09:34:11 + with message-id and subject line Bug#973846: fixed in manpages 5.09-2 has caused the Debian Bug report #973846, regarding manpages: file conflict with manpages-dev=5.08-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.) -- 973846: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973846 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: manpages Version: 5.09-1 Severity: grave Justification: renders package unupgradeable Hi! I'm afraid that the package fails to upgrade: Unpacking manpages (5.09-1) over (5.08-1) ... dpkg: error processing archive /tmp/apt-dpkg-install-Vi3YLk/00-manpages_5.09-1_all.deb (--unpack): trying to overwrite '/usr/share/man/man3/queue.3.gz', which is also in package manpages-dev 5.08-1 Obviously, you need Replaces: manpages-dev (<< 5.09) Meow! -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-rc2-00014-g46c809d3dfda (SMP w/64 CPU threads) Kernel taint flags: TAINT_WARN Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages manpages-dev depends on: ii manpages 5.08-1 manpages-dev recommends no packages. Versions of packages manpages-dev suggests: ii man-db [man-browser] 2.9.3-2 -- no debconf information --- End Message --- --- Begin Message --- Source: manpages Source-Version: 5.09-2 Done: to...@debian.org (Dr. Tobias Quathamer) We believe that the bug you reported is fixed in the latest version of manpages, 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 973...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dr. Tobias Quathamer (supplier of updated manpages 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, 06 Nov 2020 10:08:51 +0100 Source: manpages Architecture: source Version: 5.09-2 Distribution: unstable Urgency: medium Maintainer: Dr. Tobias Quathamer Changed-By: Dr. Tobias Quathamer Closes: 973846 Changes: manpages (5.09-2) unstable; urgency=medium . * Resolve file conflict with manpages-dev=5.08-1. Thanks to Adam Borowski (Closes: #973846) Checksums-Sha1: 3b907b66fdcf5ef6d6583ce5a98965276afac2a9 1882 manpages_5.09-2.dsc 010877dd739e3dcd656af9bcba354b95e0fdcb1c 77176 manpages_5.09-2.debian.tar.xz 4bad83e4a226b9518f9fcfcdfce6371d4c2b9903 5964 manpages_5.09-2_amd64.buildinfo Checksums-Sha256: ae1a09516365ad05b7de5bf571c06146d23d779d720ac207936a86ad211b741a 1882 manpages_5.09-2.dsc 35aa862f4ba978877c9d5f171ef315d205540f2813b38f2c779a08d15cf1d475 77176 manpages_5.09-2.debian.tar.xz d8becda9173da9c2e697058778c3d97bec3665d8e0155a276c7759440ebb40ff 5964 manpages_5.09-2_amd64.buildinfo Files: ca8dd301fe4bbf0728d1fdb792111c12 1882 doc standard manpages_5.09-2.dsc 688342d699118041643189bc6743d702 77176 doc standard manpages_5.09-2.debian.tar.xz c8563cae69a172368622f5c5932311cd 5964 doc standard manpages_5.09-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEE0cuPObxd7STF0seMEwLx8Dbr6xkFAl+lE8QACgkQEwLx8Dbr 6xl38Q//XiMu7ybg3TJQ83ALUY9G4PYcah2ai9nyyB4roinL+gRfaEehic73V6O7 yquaNLFH39uttZ0eqTP38tsXOjjeD0+tNZMkV/zpwCsanFMawcWomLYVAWRw+Kz3 G1z1YJdoATqOMXJHNNu5RWapDuFl6QeOigsMHRf9evBvkf2pJkQ6SnGlFm5ile7/ pDNFSZz3kaiM9anBAbxmSe/xdT1sFYRFgawg/fnOfoDu418viieef0HLF6MA8v34 jpPL3TCuLwCdtTW5Av/mo8QHFZh7X9gDmd4SZDMyaTDSorAVSEZDoUIcOH+DMTC8 Nqas32TCx6dwnFsOiaIOZ5D8le2r6v/osBEg6qW9XNwMLisLHp9P0egxwOhk/lgM Zf5KaRrevjLJ0BziMS7lbERVxW1lXh8T/YtwqMP0AMcH7OVn74/zQEoh6psBDYqK mlbyw1Af6jAD8GJeycmCZ00S6G2Ui1bLqqoDweZdkc+VKbst/H1ronxUpoDdDC5H zHmdBPRIhG76yO6tiEUEf8rnfskIrqQHQFzZaYFJazYdvCVLu7MmsfIXJ59B6++X 6yUqXNlVj/gTB2l2ie5hLhGkBcj7BiFNbZrkeyAZufZY1bddYeW6h9SKsVTepmpv kY82S8nGtsquQJOxz3WfU6nQiMB8pB9qk4rrMiMPM/STJz5iD4I= =AyIv -END PGP SIGNATURE End Message ---
Processed: found 961534 in 0.8.3-1
Processing commands for cont...@bugs.debian.org: > # Issue also present in Buster > found 961534 0.8.3-1 Bug #961534 [s-tui] s-tui: Missing package relation with stress/stress-ng (Suggests or Recommends) Marked as found in versions s-tui/0.8.3-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 961534: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961534 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#973714: Depends on argyll which is going away
On 06 nov. 2020 09:02, Moritz Muehlenhoff wrote: [...] > 966416 was a RoM (Request of maintainer), if the current maintainer wants to > get argyll removed, then you should adopt it instead or make a QA upload, but > you can't simply do an NMU and override the maintainer's request. > > Reopening until Jörg has had a chance to comment. [I forgot to put a Cc to the bug report.] I'm sorry I din't see the RoM and I don't want to adopt argyll again : , | argyll (1.5.1-5) unstable; urgency=low | | * Package orphaned. I don't intent to support the work of an agressive | upstream author more longer and realy good luck for the next maintainer. | | -- Christian Marillat Mon, 19 Aug 2013 14:18:29 +0200 ` Jörg why a RoM ? Why to not simply orphan this package ? Others people are still using it. Chirstian
Processed: Re: Bug#961534: Please "Recommend: stress-ng/stress"
Processing control commands: > severity -1 serious Bug #961534 [s-tui] Please "Recommend: stress-ng/stress" Severity set to 'serious' from 'wishlist' > found -1 1.0.2-1 Bug #961534 [s-tui] Please "Recommend: stress-ng/stress" Marked as found in versions s-tui/1.0.2-1. > retitle -1 s-tui: Missing package relation with stress/stress-ng (Suggests or > Recommends) Bug #961534 [s-tui] Please "Recommend: stress-ng/stress" Changed Bug title to 's-tui: Missing package relation with stress/stress-ng (Suggests or Recommends)' from 'Please "Recommend: stress-ng/stress"'. -- 961534: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961534 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#958607: marked as done (pppconfig: Build-Depends on deprecated dh-systemd which is going away)
Your message dated Fri, 06 Nov 2020 08:49:24 + with message-id and subject line Bug#958607: fixed in pppconfig 2.3.25 has caused the Debian Bug report #958607, regarding pppconfig: Build-Depends on deprecated dh-systemd which is going away 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.) -- 958607: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958607 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pppconfig Severity: normal User: pkg-systemd-maintain...@lists.alioth.debian.org Usertags: dh-systemd-removal Hi, your package pppconfig declares a build dependency on dh-systemd. dh-systemd was merged into debhelper in version 9.20160709 [1] and since stretch, dh-systemd is an empty transitional package. For bullseye we intend to drop this empty transitional package. Once we drop dh-systemd, this bug report will become RC. Please update your package accordingly. The change should be as simple as replacing the build dependency on dh-systemd with a build dependency on debhelper (>= 9.20160709). Regards, Michael [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822670 --- End Message --- --- Begin Message --- Source: pppconfig Source-Version: 2.3.25 Done: Ryan Finnie We believe that the bug you reported is fixed in the latest version of pppconfig, 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 958...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ryan Finnie (supplier of updated pppconfig package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 05 Nov 2020 14:59:44 -0800 Source: pppconfig Architecture: source Version: 2.3.25 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Ryan Finnie Closes: 958607 Changes: pppconfig (2.3.25) unstable; urgency=medium . * QA upload. * Remove dh-systemd Build-Depends, move to debhelper 10. (Closes: #958607) * Remove pppconfig.lintian-overrides, contained removed override init.d-script-missing-dependency-on-remote_fs throwing lintian E. Checksums-Sha1: 73571481be5072327b21af246a27764c645da63e 1457 pppconfig_2.3.25.dsc d04f6c6f129c457b20996582de1ae7792c338e24 392316 pppconfig_2.3.25.tar.gz Checksums-Sha256: d47b549ee5307710a1f8c59e54a618316812fd16fc5b046d9da2f93895e188ef 1457 pppconfig_2.3.25.dsc a49b0abf88f9c48a03fe2754a4343b26889f2dee49ba0de4ef2dcfbbc4a97341 392316 pppconfig_2.3.25.tar.gz Files: e1bd8a02938a67058fc84a61714eecfe 1457 admin optional pppconfig_2.3.25.dsc ba3d626b336cb810e3097e1626b38d38 392316 admin optional pppconfig_2.3.25.tar.gz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAl+lCMwACgkQiNJCh6LY mLH99xAAxNmjq0XKB/zUPRYaKcyW+ugCcZaifbYeonPMBGSfE8vdwbdXOTNVNwfE Re97HSOSmWBBcSsQaRBrB/1pgBAoIMp9iA54aiy9ptrKAez2wwok4weKHHX8l7AN k3xbiRMCPSo+jXyR8xbsH5ovU/H6n5+d+2lsoDJ+Zlbk6SyaWOOr3gR6W4GmnJ5C f9seQumGHanrP6lXRt425viZax6P75wziF7pXGO2j6A7L8tK/W9+gUzVMw6nQZ66 bm8f6NXGdc3rYvqQ54iSNA5HQR4b/UAvWyQ0LGCi44aiCpY0yRPVcHVI/kZowtm/ 9cYH/z59G1RyUNaZOen2ChedY7oRqwNYLwEqKNwmWZKSGcoYBWfhHwxmV8aRXvYC tAZm1wxFJ4V7PpX/yccIwJpWKcT2XeewzlBf/3Zxa7q7rw4937WsZaMxal+2L01R uVGAEOqf+oF9MZDwY9FQ70Z9yD8sJN4WP5B5hTdLFF1mBOGRjYHIRYh7ZAXdXFbI fGM6RQ95SLAKDiBTnE/ZxpDq3XuA9EDaXzQkt6mXDKtbfBxQqH+SKWLAgNOTx7Zl 4Z4WAySB8omN3PIHb6MBtzDaHtA68DQsy3uEjr4KLHnM879sCbGxe515j1uWJcNu K2DL0KW/02lwAkvJp5V3XG3R+dlI6zlkjTpwOGikWoHhXW3ER/g= =dF6l -END PGP SIGNATURE End Message ---
Bug#969372: uwsgi-emperor: SysV init script does nothing
Package: uwsgi-emperor Version: 2.0.19.1-3+b1 Followup-For: Bug #969372 Hi Thomas, indeed, I have a number of vassals configured, actually I use emperor for web development for several years now. At first, I noticed that the emperor haven't start after reboot. I have tried to start it with systemd, but with no success. Systemd only reports the process as "started" but it's not running (`ps -ef | grep uwsgi`). Here's a relevant output of terminal commands: $ sudo service uwsgi-emperor start $ sudo service uwsgi-emperor status ● uwsgi-emperor.service - LSB: Start/stop uWSGI server instance(s) Loaded: loaded (/etc/init.d/uwsgi-emperor; generated) Active: active (exited) since Fri 2020-11-06 09:23:17 CET; 1s ago Docs: man:systemd-sysv-generator(8) Process: 889151 ExecStart=/etc/init.d/uwsgi-emperor start (code=exited, status=0/SUCCESS) Nov 06 09:23:17 queeg-500 systemd[1]: Starting LSB: Start/stop uWSGI server instance(s)... Nov 06 09:23:17 queeg-500 systemd[1]: Started LSB: Start/stop uWSGI server instance(s). $ ps -ef | grep uwsgi vzima 889177 887414 0 09:23 pts/500:00:00 grep uwsgi Despite this, I can start the emperor manually using command composed on /etc/init.d/uwsgi-emperor: $ sudo /usr/bin/uwsgi --ini /etc/uwsgi-emperor/emperor.ini --die-on-term --pidfile /run/uwsgi-emperor.pid --daemonize /var/log/uwsgi/emperor.log I also encounter the PID file bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934731, so I need to delete PID file manually. Regards, Vlastimil Zíma -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing'), (90, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.8.0-2-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages uwsgi-emperor depends on: ii uwsgi-core 2.0.19.1-3+b1 uwsgi-emperor recommends no packages. uwsgi-emperor suggests no packages. -- Configuration Files: /etc/uwsgi-emperor/emperor.ini changed: [uwsgi] master = true workers = 2 no-orphans = true log-date = true uid = www-data gid = www-data emperor = /etc/uwsgi-emperor/vassals emperor-tyrant = true cap = setgid,setuid -- no debconf information
Bug#971171: MP up
To help integrating these I have opened https://salsa.debian.org/libvirt-team/libvirt-dbus/-/merge_requests/4 -- Christian Ehrhardt Staff Engineer, Ubuntu Server Canonical Ltd
Bug#973472: fetchmail: Fails to connect using SSL
On Mon, 2 Nov 2020 10:34:35 +0100 Timo van Roermund wrote: > On Sun, 01 Nov 2020 14:25:03 -0800 Bill Wohler wrote: > > > Thanks for explaining the situation. Sounds like just some bad luck. > > Even so, it would still be good if a mechanism could be created that > > would prevent this from happening in the future. > > Yes, some mechanism to prevent this would be good. I only noticed this > issue after approximately two days and therefore received some e-mails > (too) late. > > > I appreciate your sending the link to the prior package. It made it much > > easier to go back, and now my mail is flowing again.. I've also held the > > package until I see an OpenSSL update. > > I took a different approach and upgraded the openssl and libssl1.1 > packages to version 1.1.1h-1 (from unstable). I did so because I am not > affected by any of the regressions listed at the oppenssl package > tracker (https://tracker.debian.org/pkg/openssl). With this approach, I > don't need to take any further manual actions later on (to unhold the > package). for those stumbling on this via searching, the workaround mentioned above is: create priority for testing: /etc/apt/apt.conf.d/default-release with APT::Default-Release "testing"; add into sources (with your favourite mirror): deb http://ftp.debian.sk/debian/ unstable main contrib non-free apt update and reinstall apt -t unstable install libssl1.1:amd64 -- Michal Páleník
