Bug#984125: marked as done (flamp: ftbfs with GCC-11)
Your message dated Wed, 13 Oct 2021 04:48:23 + with message-id and subject line Bug#984125: fixed in flamp 2.2.07-1 has caused the Debian Bug report #984125, regarding flamp: ftbfs with GCC-11 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.) -- 984125: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984125 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:flamp Version: 2.2.05-1 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye release] 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-11/g++-11, but succeeds to build with gcc-10/g++-10. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://people.debian.org/~doko/logs/20210228/filtered/gcc11/flamp_2.2.05-1_unstable_gcc11.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 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-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] ./include/amp.h:381:17: warning: this ‘if’ clause does not guard... [-Wmisleading-indentation] 381 | if (rxnumblocks == 0 || rx_ok_blocks == 0) return empty;static char percent[6]; | ^~ ./include/amp.h:381:89: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘if’ 381 | if (rxnumblocks == 0 || rx_ok_blocks == 0) return empty;static char percent[6]; | ^~ In file included from ./include/flamp.h:39, from flamp.cxx:62: ./include/amp.h: In member function ‘const char* cAmp::rx_sz_percent()’: ./include/amp.h:381:17: warning: this ‘if’ clause does not guard... [-Wmisleading-indentation] 381 | if (rxnumblocks == 0 || rx_ok_blocks == 0) return empty;static char percent[6]; | ^~ ./include/amp.h:381:89: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘if’ 381 | if (rxnumblocks == 0 || rx_ok_blocks == 0) return empty;static char percent[6]; | ^~ gcc -DHAVE_CONFIG_H -I. -I. -I./include -I/usr/include/flxmlrpc -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/cairo -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/cairo -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 -I. -I./include -pipe -Wall -fexceptions -O2 -ffast-math -finline-functions -fomit-frame-pointer -DNDEBUG -I/usr/include/flxmlrpc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o lzma/flamp-LzmaLib.o `test -f 'lzma/LzmaLib.c' || echo './'`lzma/LzmaLib.c flamp_dialog.cxx: In function ‘void set_txt_tx_interval()’: flamp_dialog.cxx:921:15: warning: unused variable ‘t’ [-Wunused-variable] 921 | float t = cnt_tx_interval_mins->value(); | ^ g++ -DHAVE_CONFIG_H -I. -I. -I./include -I/usr/include/flxmlrpc -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/cairo -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include
Processed: tagging 994863
Processing commands for cont...@bugs.debian.org: > tags 994863 + pending Bug #994863 [python-cleo-doc] python-cleo-doc: ships /usr/share/doc-base/python-six-doc Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 994863: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994863 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#984078: vc-dev: please upload to unstable
Package: vc-dev Version: 1.4.2-1 Followup-For: Bug #984078 Dear all with gcc11 being the default in sid now, please upload vc-dev to unstable, otherwise the FTBFS for other packages continue. Thanks Norbert -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.14.11+futex+ (SMP w/8 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- no debconf information
Bug#995594: libhdf5[-openmpi]-dev: missing Depends: libcurl-dev
Drew Parsons a écrit le 04/10/2021 à 21:14 : On 2021-10-03 12:15, Gilles Filippini wrote: Drew Parsons a écrit le 02/10/2021 à 22:17 : ... Since h5pcc and h5cc invoke -lcurl, libhdf5-openmpi-dev, libhdf5-dev (and probably libhdf5-mpich-dev also) should declare Depends: libcurl-dev ... I guess this is a consequence of enabling access to HDF5 on S3. See #972537. Judging by fclib and https://ci.debian.net/data/autopkgtest/testing/amd64/f/fclib/15757105/log.gz I guess libhdf5*-dev needs libssl-dev as well Done. Thanks, _g.
Bug#996324: ruby-netcdf: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Segmentation fault at 0x0000000000000034
Source: ruby-netcdf
Version: 0.7.2-5
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.0
Hi,
We are about to enable building against ruby3.0 on unstable. During a test
rebuild, ruby-netcdf was found to fail to build in that situation.
To reproduce this locally, you need to install ruby-all-dev from experimental
on an unstable system or build chroot.
Relevant part (hopefully):
> /usr/bin/ruby3.0 /usr/bin/gem2deb-test-runner
>
> ┌──┐
> │ Run tests for ruby3.0 from debian/ruby-test-files.yaml
> │
> └──┘
>
> RUBYLIB=/<>/debian/ruby-netcdf/usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/3.0.0:/<>/debian/ruby-netcdf/usr/lib/ruby/vendor_ruby:.
>
> GEM_PATH=/<>/debian/ruby-netcdf/usr/share/rubygems-integration/3.0.0:/var/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0
> ruby3.0 -ryaml -e YAML.load_file\(\"debian/ruby-test-files.yaml\"\).each\
> \{\ \|f\|\ require\ f\ \}
> Loaded suite -e
> Started
>
> Finished in 0.028058613 seconds.
> ---
> 20 tests, 127 assertions, 0 failures, 0 errors, 0 pendings, 0 omissions, 0
> notifications
> 100% passed
> ---
> 712.79 tests/s, 4526.24 assertions/s-e: [BUG] Segmentation fault at
> 0x0034
> ruby 3.0.2p107 (2021-07-07 revision 0db68f0233) [x86_64-linux-gnu]
>
> -- Control frame information ---
> c:0001 p: s:0003 E:001f10 (none) [FINISH]
>
>
> -- Machine register context
> RIP: 0x0034 RBP: 0x5644105564a0 RSP: 0x7ffc66891258
> RAX: 0x0034 RBX: 0x564410569488 RCX: 0x0001
> RDX: 0x564410569b18 RDI: 0x0034 RSI: 0x7ffc66891278
> R8: 0x564410569780 R9: 0x0001 R10: 0x7ffc668911e0
> R11: 0x0246 R12: 0x564410568000 R13: 0x564410564a30
> R14: 0x564410569488 R15: 0x56440ff00760 EFL: 0x00010202
>
> -- C level backtrace information ---
> ERROR: Test "ruby3.0" failed.
The full build log is available at
https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-netcdf/ruby-netcdf_0.7.2-5+rebuild1633388714_amd64.build.txt
signature.asc
Description: PGP signature
Bug#996323: ruby-mono-logger: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: wrong number of arguments (given 2, expected 0..1)
Source: ruby-mono-logger Version: 1.1.0-3.1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-mono-logger was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): > ArgumentError: wrong number of arguments (given 2, expected 0..1) > /usr/lib/ruby/3.0.0/logger/log_device.rb:14:in `initialize' > /<>/test/mri_logger_test.rb:289:in `new' > /<>/test/mri_logger_test.rb:289:in `d' > /<>/test/mri_logger_test.rb:323:in `test_write' > /usr/lib/ruby/vendor_ruby/minitest/test.rb:98:in `block (3 levels) in run' > /usr/lib/ruby/vendor_ruby/minitest/test.rb:195:in `capture_exceptions' > /usr/lib/ruby/vendor_ruby/minitest/test.rb:95:in `block (2 levels) in run' > /usr/lib/ruby/vendor_ruby/minitest.rb:270:in `time_it' > /usr/lib/ruby/vendor_ruby/minitest/test.rb:94:in `block in run' > /usr/lib/ruby/vendor_ruby/minitest.rb:365:in `on_signal' > /usr/lib/ruby/vendor_ruby/minitest/test.rb:211:in `with_info_handler' > /usr/lib/ruby/vendor_ruby/minitest/test.rb:93:in `run' > /usr/lib/ruby/vendor_ruby/minitest.rb:1029:in `run_one_method' > /usr/lib/ruby/vendor_ruby/minitest.rb:339:in `run_one_method' > /usr/lib/ruby/vendor_ruby/minitest.rb:326:in `block (2 levels) in run' > /usr/lib/ruby/vendor_ruby/minitest.rb:325:in `each' > /usr/lib/ruby/vendor_ruby/minitest.rb:325:in `block in run' > /usr/lib/ruby/vendor_ruby/minitest.rb:365:in `on_signal' > /usr/lib/ruby/vendor_ruby/minitest.rb:352:in `with_info_handler' > /usr/lib/ruby/vendor_ruby/minitest.rb:324:in `run' > /usr/lib/ruby/vendor_ruby/minitest.rb:164:in `block in __run' > /usr/lib/ruby/vendor_ruby/minitest.rb:164:in `map' > /usr/lib/ruby/vendor_ruby/minitest.rb:164:in `__run' > /usr/lib/ruby/vendor_ruby/minitest.rb:141:in `run' > /usr/lib/ruby/vendor_ruby/minitest.rb:68:in `block in autorun' > > 5) Skipped: > TestLogDevice#test_shifting_size > [/<>/test/mri_logger_test.rb:354]: > shifting age doesn't work because rotation doesn't work > > 6) Skipped: > TestLogDevice#test_shifting_age > [/<>/test/mri_logger_test.rb:442]: > shifting age doesn't work because rotation doesn't work > > 20 runs, 102 assertions, 0 failures, 3 errors, 3 skips > rake aborted! > Command failed with status (1): [ruby -w -I"test" > /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/rake_test_loader.rb > "test/mri_logger_test.rb" -v] > > Tasks: TOP => default > (See full trace by running task with --trace) > ERROR: Test "ruby3.0" failed: The full build log is available at https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-mono-logger/ruby-mono-logger_1.1.0-3.1+rebuild1633387243_amd64.build.txt signature.asc Description: PGP signature
Bug#996322: ruby-mmap2: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: :85:in `require': cannot load such file -- mmap (LoadE
Source: ruby-mmap2 Version: 2.2.7-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-mmap2 was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): > :85:in > `require': cannot load such file -- mmap (LoadError) > from > :85:in > `require' > from /<>/test/test_mmap.rb:1:in `' > from > :85:in > `require' > from > :85:in > `require' > from > /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/rake_test_loader.rb:17:in > `block in ' > from > /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/rake_test_loader.rb:5:in > `select' > from > /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/rake_test_loader.rb:5:in > `' > rake aborted! > Command failed with status (1): [ruby -w -I"test" > /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/rake_test_loader.rb > "test/test_mmap.rb" -v] > > Tasks: TOP => default > (See full trace by running task with --trace) > ERROR: Test "ruby3.0" failed: The full build log is available at https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-mmap2/ruby-mmap2_2.2.7-1+rebuild1633387115_amd64.build.txt signature.asc Description: PGP signature
Bug#996321: ruby-mixlib-install: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: cannot load such file -- webrick
Source: ruby-mixlib-install Version: 3.11.7-1.1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-mixlib-install was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): > cannot load such file -- webrick > # ./spec/spec_helper.rb:5:in `' > # ./spec/unit/mixlib/install_spec.rb:18:in `' > No examples found. > > Finished in 0.8 seconds (files took 3.37 seconds to load) > 0 examples, 0 failures, 9 errors occurred outside of examples > > /usr/bin/ruby3.0 > -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 "ruby3.0" failed: Note that webrick has been removed from the standard library. It's already been packaged and is currently in NEW, but this package now needs an explicit dependency on it. The full build log is available at https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-mixlib-install/ruby-mixlib-install_3.11.7-1.1+rebuild1633386978_amd64.build.txt signature.asc Description: PGP signature
Bug#996320: ruby-minitest-excludes: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed.
Source: ruby-minitest-excludes
Version: 2.0.1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.0
Hi,
We are about to enable building against ruby3.0 on unstable. During a test
rebuild, ruby-minitest-excludes was found to fail to build in that situation.
To reproduce this locally, you need to install ruby-all-dev from experimental
on an unstable system or build chroot.
Relevant part (hopefully):
> /usr/bin/ruby3.0 /usr/bin/gem2deb-test-runner
>
> ┌──┐
> │ Checking Rubygems dependency resolution on ruby3.0
> │
> └──┘
>
> GEM_PATH=/<>/debian/ruby-minitest-excludes/usr/share/rubygems-integration/all:/var/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0
> ruby3.0 -e gem\ \"minitest-excludes\"
>
> ┌──┐
> │ Run tests for ruby3.0 from debian/ruby-test-files.yaml
> │
> └──┘
>
> RUBYLIB=.
> GEM_PATH=/<>/debian/ruby-minitest-excludes/usr/share/rubygems-integration/all:/var/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0
> ruby3.0 -ryaml -e YAML.load_file\(\"debian/ruby-test-files.yaml\"\).each\
> \{\ \|f\|\ require\ f\ \}
> Run options: --seed 1794
>
> # Running:
>
> F
>
> Finished in 0.001705s, 586.6517 runs/s, 586.6517 assertions/s.
>
> 1) Failure:
> TestMinitestExcludes#test_cls_excludes
> [/<>/test/test_minitest_excludes.rb:44]:
> Expected: ["test_test3", "test_test1"]
> Actual: ["test_test1", "test_test3"]
>
> 1 runs, 1 assertions, 1 failures, 0 errors, 0 skips
> ERROR: Test "ruby3.0" failed.
The full build log is available at
https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-minitest-excludes/ruby-minitest-excludes_2.0.1-1+rebuild1633386834_amd64.build.txt
signature.asc
Description: PGP signature
Bug#996319: ruby-mini-magick: FTBFS: ERROR: Test "ruby2.7" failed: Failure/Error: expect(described_class.new(output_path.to_s)).to be_valid
Source: ruby-mini-magick
Version: 4.10.1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.0
Hi,
We are about to enable building against ruby3.0 on unstable. During a test
rebuild, ruby-mini-magick was found to fail to build in that situation.
This does not seem related to ruby3.0, though.
Relevant part (hopefully):
> Failure/Error: expect(described_class.new(output_path.to_s)).to be_valid
>expected `# @path="/tmp/20211004-4162560-wmodba", @tempfile=nil,
> @info=# @path="/tmp/20211004-4162560-wmodba", @info={}>>.valid?` to return true, got
> false
> # ./spec/lib/mini_magick/image_spec.rb:323:in `block (5 levels) in (required)>'
>
> Finished in 25.39 seconds (files took 1.61 seconds to load)
> 283 examples, 8 failures, 5 pending
>
> Failed examples:
>
> rspec './spec/lib/mini_magick/image_spec.rb[1:1:1:3]' # With ImageMagick
> MiniMagick::Image.read reads image from tempfile
> rspec './spec/lib/mini_magick/image_spec.rb[1:1:8:5]' # With ImageMagick
> MiniMagick::Image#format works without an extension with .open
> rspec './spec/lib/mini_magick/image_spec.rb[1:1:9:1]' # With ImageMagick
> MiniMagick::Image#write writes the image
> rspec './spec/lib/mini_magick/image_spec.rb[1:1:9:4]' # With ImageMagick
> MiniMagick::Image#write accepts a Pathname
> rspec './spec/lib/mini_magick/image_spec.rb[2:1:1:3]' # With GraphicsMagick
> MiniMagick::Image.read reads image from tempfile
> rspec './spec/lib/mini_magick/image_spec.rb[2:1:8:5]' # With GraphicsMagick
> MiniMagick::Image#format works without an extension with .open
> rspec './spec/lib/mini_magick/image_spec.rb[2:1:9:1]' # With GraphicsMagick
> MiniMagick::Image#write writes the image
> rspec './spec/lib/mini_magick/image_spec.rb[2:1:9:4]' # With GraphicsMagick
> MiniMagick::Image#write accepts a Pathname
>
> /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 at
https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-mini-magick/ruby-mini-magick_4.10.1-1+rebuild1633386655_amd64.build.txt
signature.asc
Description: PGP signature
Bug#996318: ruby-messagebus-api: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: expected no Exception, got # with backtrace:
Source: ruby-messagebus-api Version: 3.0.7+git.20130130.97b34ece.REALLY.1.0.3-2.1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-messagebus-api was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): >expected no Exception, got # for URI:Module> with backtrace: > # /<>/lib/messagebus_ruby_api/messagebus.rb:130:in > `stats' > # > /<>/spec/messagebus_ruby_api/messagebus_spec.rb:320:in `block (4 > levels) in ' > # > /<>/spec/messagebus_ruby_api/messagebus_spec.rb:319:in `block (3 > levels) in ' > # /<>/spec/messagebus_ruby_api/messagebus_spec.rb:319:in > `block (3 levels) in ' > > Finished in 0.09083 seconds (files took 0.71624 seconds to load) > 22 examples, 3 failures > > Failed examples: > > rspec /<>/spec/messagebus_ruby_api/messagebus_spec.rb:223 # > MessagebusApi::Messagebus#delivery_errors request delivery errors list > rspec /<>/spec/messagebus_ruby_api/messagebus_spec.rb:238 # > MessagebusApi::Messagebus#unsubscribes request blocked emails list > rspec /<>/spec/messagebus_ruby_api/messagebus_spec.rb:312 # > MessagebusApi::Messagebus#stats stats > > /usr/bin/ruby3.0 > -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 "ruby3.0" failed: The full build log is available at https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-messagebus-api/ruby-messagebus-api_3.0.7+git.20130130.97b34ece.REALLY.1.0.3-2.1+rebuild1633386486_amd64.build.txt signature.asc Description: PGP signature
Bug#996278: marked as done (open3d: autopkgtest needs update for new version of gcc-defaults: output on stderr)
Your message dated Tue, 12 Oct 2021 22:48:53 + with message-id and subject line Bug#996278: fixed in open3d 0.9.0+ds-7 has caused the Debian Bug report #996278, regarding open3d: autopkgtest needs update for new version of gcc-defaults: output on stderr 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.) -- 996278: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996278 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: open3d Version: 0.9.0+ds-6 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:gcc-defaults [X-Debbugs-CC: debian...@lists.debian.org, gcc-defau...@packages.debian.org] Dear maintainer(s), With a recent upload of gcc-defaults the autopkgtest of open3d fails in testing on arm64, armhf and ppc64el when that autopkgtest is run with the binary packages of gcc-defaults from unstable. It passes when run with only packages from testing. In tabular form: passfail gcc-defaults from testing1.194 open3d from testing0.9.0+ds-6 all others from testingfrom testing I copied some of the output at the bottom of this report. The failure is due to output on stderr. Output to stderr is by default considered by autopkgtest as a failure of the test. If you want to have test fail on output to stderr, please fix the reason of the output. If you don't care you can add the allow-stderr restriction to have autopkgtest ignore the output. Currently this regression is blocking the migration of gcc-defaults to testing [1]. Of course, gcc-defaults shouldn't just break your autopkgtest (or even worse, your package), but it seems to me that the change in gcc-defaults was intended and your package needs to update to the new situation. If this is a real problem in your package (and not only in your autopkgtest), the right binary package(s) from gcc-defaults should really add a versioned Breaks on the unfixed version of (one of your) package(s). Note: the Breaks is nice even if the issue is only in the autopkgtest as it helps the migration software to figure out the right versions to combine in the tests. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=gcc-defaults https://ci.debian.net/data/autopkgtest/testing/arm64/o/open3d/15926028/log.gz autopkgtest [01:10:43]: test test-cpp: [--- $ cmake . -- The C compiler identification is GNU 11.2.0 -- The CXX compiler identification is GNU 11.2.0 -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working C compiler: /usr/bin/cc - skipped -- Detecting C compile features -- Detecting C compile features - done -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Check for working CXX compiler: /usr/bin/c++ - skipped -- Detecting CXX compile features -- Detecting CXX compile features - done -- Found GLEW: /usr/include (found version "2.2.0") -- Found Open3D: /usr/lib/aarch64-linux-gnu/cmake/Open3D/Open3DConfig.cmake (found version "0.9.0") -- Configuring done -- Generating done -- Build files have been written to: /tmp/tmp.HsneE5NHLQ $ make VERBOSE=ON /usr/bin/cmake -S/tmp/tmp.HsneE5NHLQ -B/tmp/tmp.HsneE5NHLQ --check-build-system CMakeFiles/Makefile.cmake 0 /usr/bin/cmake -E cmake_progress_start /tmp/tmp.HsneE5NHLQ/CMakeFiles /tmp/tmp.HsneE5NHLQ//CMakeFiles/progress.marks make -f CMakeFiles/Makefile2 all make[1]: Entering directory '/tmp/tmp.HsneE5NHLQ' make -f CMakeFiles/open3d_test.dir/build.make CMakeFiles/open3d_test.dir/depend make[2]: Entering directory '/tmp/tmp.HsneE5NHLQ' cd /tmp/tmp.HsneE5NHLQ && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /tmp/tmp.HsneE5NHLQ /tmp/tmp.HsneE5NHLQ /tmp/tmp.HsneE5NHLQ /tmp/tmp.HsneE5NHLQ /tmp/tmp.HsneE5NHLQ/CMakeFiles/open3d_test.dir/DependInfo.cmake --color= make[2]: Leaving directory '/tmp/tmp.HsneE5NHLQ' make -f CMakeFiles/open3d_test.dir/build.make CMakeFiles/open3d_test.dir/build make[2]: Entering directory '/tmp/tmp.HsneE5NHLQ' [ 50%] Building CXX object CMakeFiles/open3d_test.dir/open3d_test.cpp.o /usr/bin/c++ -DFMT_LOCALE -DFMT_SHARED -isystem /usr/include/eigen3 -MD -MT CMakeFiles/open3d_test.dir/open3d_test.cpp.o -MF CMakeFiles/open3d_test.dir/open3d_test.cpp.o.d -o CMakeFiles/open3d_test.dir/open3d_test.cpp.o -c /tmp/tmp.HsneE5NHLQ/open3d_test.cpp In file included from /usr/include/Open3D/Open3D.h:30,
Bug#996317: ruby-memory-profiler: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed.
Source: ruby-memory-profiler Version: 0.9.14-3 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-memory-profiler was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): > /usr/bin/ruby3.0 /usr/bin/gem2deb-test-runner > > ┌──┐ > │ Checking Rubygems dependency resolution on ruby3.0 > │ > └──┘ > > GEM_PATH=/<>/debian/ruby-memory-profiler/usr/share/rubygems-integration/all:/var/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0 > ruby3.0 -e gem\ \"memory_profiler\" > > ┌──┐ > │ Run tests for ruby3.0 from debian/ruby-tests.rake > │ > └──┘ > > RUBYLIB=/<>/debian/ruby-memory-profiler/usr/lib/ruby/vendor_ruby:. > > GEM_PATH=/<>/debian/ruby-memory-profiler/usr/share/rubygems-integration/all:/var/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0 > ruby3.0 -S rake -f debian/ruby-tests.rake > /usr/bin/ruby3.0 -w > /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/rake_test_loader.rb > "test/test_helper.rb" "test/test_helpers.rb" "test/test_reporter.rb" > "test/test_reporter_private_start_stop.rb" > "test/test_reporter_public_start_stop.rb" "test/test_results.rb" > "test/test_stat_hash.rb" "test/test_top_n.rb" -v > Run options: -v --seed 35593 > > # Running: > > MemoryProfiler::TestHelpers#test_rubygems_parse = 0.00 s = . > MemoryProfiler::TestHelpers#test_app_path_parse = 0.00 s = . > MemoryProfiler::TestHelpers#test_standard_parse = 0.00 s = . > MemoryProfiler::TestHelpers#test_another_standard_parse = 0.00 s = . > MemoryProfiler::TestHelpers#test_stdlib_parse = 0.00 s = . > TestResults#test_normalize_paths_true = 0.12 s = F > TestResults#test_scale_bytes_off = 0.13 s = . > TestResults#test_no_conflict_with_pretty_print = 0.00 s = . > TestResults#test_normalize_paths_default = 0.09 s = . > TestResults#test_scale_bytes_true = 0.14 s = . > TestResults#test_pretty_print_works_with_no_args = 0.00 s = . > TestResults#test_scale_bytes_default = 0.13 s = . > TestResults#test_pretty_print_works_with_io_arg = 0.00 s = . > TestResults#test_normalize_paths_false = 0.09 s = . > TestReporter#test_no_color_output = 0.08 s = . > TestReporter#test_no_strings_retained_report = 0.08 s = F > TestReporter#test_ignore_file_with_regex = 0.08 s = . > TestReporter#test_allow_files_with_string = 0.09 s = . > TestReporter#test_color_output = 0.08 s = . > TestReporter#test_basic_object = 0.08 s = . > TestReporter#test_color_output_defaults_to_true_when_run_from_tty = 0.08 s = . > TestReporter#test_ignore_file_with_string = 0.09 s = . > TestReporter#test_non_string_named_class = 0.07 s = . > TestReporter#test_reports_can_be_reused_with_different_color_options = 0.09 s > = . > TestReporter#test_class_tracing_with_value = 0.08 s = . > TestReporter#test_mono_output_defaults_to_true_when_not_run_from_tty = 0.08 s > = . > TestReporter#test_nil_reporting_class = 0.09 s = . > TestReporter#test_allow_files_with_array = 0.08 s = . > TestReporter#test_counts = 0.08 s = . > TestReporter#test_string_reporting_class = 0.09 s = . > TestReporter#test_class_tracing_with_array = 0.08 s = . > TestReporter#test_strings_report = 0.10 s = . > TestReporter#test_exception_handling = 0.11 s = . > TestReporter#test_yield_block = 0.11 s = . > TestReporter#test_anonymous_class_object = 0.08 s = . > TestTopN#test_top_n_small_n = 0.00 s = . > TestTopN#test_top_n_large_n = 0.00 s = . > TestReporterPublicStartStop#test_allow_files_with_array = 0.11 s = . > TestReporterPublicStartStop#test_allow_files_with_string = 0.11 s = . > TestReporterPublicStartStop#test_ignore_file_with_string = 0.12 s = . > TestReporterPublicStartStop#test_basic_object = 0.09 s = . > TestReporterPublicStartStop#test_color_output_defaults_to_true_when_run_from_tty > = 0.09 s = . > TestReporterPublicStartStop#test_counts = 0.12 s = . > TestReporterPublicStartStop#test_module_stop_with_no_start = 0.00 s = . > TestReporterPublicStartStop#test_no_strings_retained_report = 0.13 s = F > TestReporterPublicStartStop#test_class_tracing_with_value = 0.11 s = . >
Bug#996316: ruby-mechanize: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: /usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:311:in `to_specs': Could not find 'webrick' (~> 1.6) among 107 total gem(
Source: ruby-mechanize Version: 2.7.7-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-mechanize was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): > /usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:311:in `to_specs': Could not > find 'webrick' (~> 1.6) among 107 total gem(s) (Gem::MissingSpecError) > Checked in > 'GEM_PATH=/<>/debian/ruby-mechanize/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.0.0:/var/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0' > , execute `gem env` for more information > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1402:in `block > in activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in > `activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372:in > `activate' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `block in gem' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `synchronize' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `gem' > from -e:1:in `' > benchmark (default: 0.1.0) > bigdecimal (default: 2.0.0) > bundler (default: 2.1.4) > cgi (default: 0.1.0) > connection_pool (2.2.2) > csv (default: 3.1.2) > date (default: 3.0.0) > dbm (default: 1.1.0) > delegate (default: 0.1.0) > did_you_mean (default: 1.4.0) > domain_name (0.5.20190701) > etc (default: 1.1.0) > fcntl (default: 1.0.0) > fiddle (default: 1.0.0) > fileutils (default: 1.4.1) > forwardable (default: 1.3.1) > gdbm (default: 2.1.0) > getoptlong (default: 0.1.0) > http-cookie (1.0.3) > io-console (default: 0.5.6) > ipaddr (default: 1.2.2) > irb (default: 1.2.6) > json (default: 2.3.0) > logger (default: 1.4.2) > matrix (default: 0.2.0) > mime-types (3.3.1) > mime-types-data (3.2015.1120) > minitest (5.13.0) > mutex_m (default: 0.1.0) > net-http-digest_auth (1.4) > net-http-persistent (3.1.0) > net-pop (default: 0.1.0) > net-smtp (default: 0.1.0) > net-telnet (0.1.1) > nokogiri (1.11.7) > observer (default: 0.1.0) > open3 (default: 0.1.0) > openssl (default: 2.1.2) > ostruct (default: 0.2.0) > pkg-config (1.4.6) > power_assert (1.1.7) > prime (default: 0.1.1) > pstore (default: 0.1.0) > psych (default: 3.1.0) > racc (default: 1.4.16, 1.4.14) > rake (13.0.3) > rdoc (default: 6.2.1.1) > readline (default: 0.0.2) > readline-ext (default: 0.1.0) > reline (default: 0.1.5) > rexml (default: 3.2.3.1) > rss (default: 0.2.8) > rubygems-update (3.2.27) > rubyntlm (0.6.1) > sdbm (default: 1.0.0) > singleton (default: 0.1.0) > stringio (default: 0.1.0) > strscan (default: 1.0.3) > test-unit (3.3.9) > timeout (default: 0.1.0) > tracer (default: 0.1.0) > unf (0.1.4) > unf_ext (0.0.7.7) > uri (default: 0.10.0) > webrick (default: 1.6.1) > webrobots (0.1.2) > xmlrpc (0.3.0) > yaml (default: 0.1.0) > zlib (default: 1.1.0) > ERROR: Test "ruby3.0" failed: Note that webrick has been removed from the standard library. It's already been packaged and is currently in NEW, but this package now needs an explicit dependency on it. The full build log is available at https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-mechanize/ruby-mechanize_2.7.7-1+rebuild1633386391_amd64.build.txt signature.asc Description: PGP signature
Bug#996315: ruby-listen: FTBFS: ERROR: Test "ruby2.7" failed: Failure/Error:
Source: ruby-listen
Version: 3.2.1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.0
Hi,
We are about to enable building against ruby3.0 on unstable. During a test
rebuild, ruby-listen was found to fail to build in that situation.
This does not seem related to ruby3.0, though.
Relevant part (hopefully):
> Failure/Error:
>expect(wrapper.listen do
> mv 'dir1/file1.rb', 'dir2/file1.rb'
> mv 'dir2/file2.rb', 'dir1/file2.rb'
>end).to eq expected
>
>expected: {:added=>["dir1/file2.rb", "dir2/file1.rb"], :modified=>[],
> :removed=>["dir1/file1.rb", "dir2/file2.rb"]}
> got: {:added=>[], :modified=>[], :removed=>[]}
>
>(compared using ==)
>
>Diff:
>
>@@ -1,4 +1,4 @@
>-:added => ["dir1/file2.rb", "dir2/file1.rb"],
>+:added => [],
> :modified => [],
>-:removed => ["dir1/file1.rb", "dir2/file2.rb"],
>+:removed => [],
> # ./spec/acceptance/listen_spec.rb:181:in `block (7 levels) in (required)>'
> # ./spec/acceptance/listen_spec.rb:171:in `block (7 levels) in (required)>'
> # ./spec/acceptance/listen_spec.rb:17:in `block (4 levels) in (required)>'
> # ./spec/support/fixtures_helper.rb:20:in `fixtures'
> # ./spec/acceptance/listen_spec.rb:17:in `block (3 levels) in (required)>'
>
> Finished in 2 minutes 15.6 seconds (files took 0.57718 seconds to load)
> 318 examples, 1 failure, 1 pending
>
> Failed examples:
>
> rspec './spec/acceptance/listen_spec.rb[1:1:3:2:6:1]' # Listen with one
> listen dir force_polling option to true with default ignore options two dirs
> with files in listen dir listens to multiple file moves
>
> Randomized with seed 30022
>
> /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 --exclude-pattern
> ./spec/lib/listen/adapter/\{darwin,windows\}_spec.rb --format documentation
> failed
> ERROR: Test "ruby2.7" failed:
The full build log is available at
https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-listen/ruby-listen_3.2.1-1+rebuild1633385884_amd64.build.txt
signature.asc
Description: PGP signature
Bug#996314: ruby-liquid: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: wrong number of arguments (given 1, expected 0)
Source: ruby-liquid Version: 4.0.3-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-liquid was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): > ArgumentError: wrong number of arguments (given 1, expected 0) > > /<>/debian/ruby-liquid/usr/lib/ruby/vendor_ruby/liquid/parse_tree_visitor.rb:28:in > `block in visit' > > /<>/debian/ruby-liquid/usr/lib/ruby/vendor_ruby/liquid/parse_tree_visitor.rb:27:in > `map' > > /<>/debian/ruby-liquid/usr/lib/ruby/vendor_ruby/liquid/parse_tree_visitor.rb:27:in > `visit' > > /<>/debian/ruby-liquid/usr/lib/ruby/vendor_ruby/liquid/parse_tree_visitor.rb:31:in > `block in visit' > > /<>/debian/ruby-liquid/usr/lib/ruby/vendor_ruby/liquid/parse_tree_visitor.rb:27:in > `map' > > /<>/debian/ruby-liquid/usr/lib/ruby/vendor_ruby/liquid/parse_tree_visitor.rb:27:in > `visit' > /<>/test/integration/parse_tree_visitor_test.rb:245:in > `visit' > /<>/test/integration/parse_tree_visitor_test.rb:207:in > `test_include' > /usr/lib/ruby/vendor_ruby/minitest/test.rb:98:in `block (3 levels) in run' > /usr/lib/ruby/vendor_ruby/minitest/test.rb:195:in `capture_exceptions' > /usr/lib/ruby/vendor_ruby/minitest/test.rb:95:in `block (2 levels) in run' > /usr/lib/ruby/vendor_ruby/minitest.rb:270:in `time_it' > /usr/lib/ruby/vendor_ruby/minitest/test.rb:94:in `block in run' > /usr/lib/ruby/vendor_ruby/minitest.rb:365:in `on_signal' > /usr/lib/ruby/vendor_ruby/minitest/test.rb:211:in `with_info_handler' > /usr/lib/ruby/vendor_ruby/minitest/test.rb:93:in `run' > /usr/lib/ruby/vendor_ruby/minitest.rb:1029:in `run_one_method' > /usr/lib/ruby/vendor_ruby/minitest.rb:339:in `run_one_method' > /usr/lib/ruby/vendor_ruby/minitest.rb:326:in `block (2 levels) in run' > /usr/lib/ruby/vendor_ruby/minitest.rb:325:in `each' > /usr/lib/ruby/vendor_ruby/minitest.rb:325:in `block in run' > /usr/lib/ruby/vendor_ruby/minitest.rb:365:in `on_signal' > /usr/lib/ruby/vendor_ruby/minitest.rb:352:in `with_info_handler' > /usr/lib/ruby/vendor_ruby/minitest.rb:324:in `run' > /usr/lib/ruby/vendor_ruby/minitest.rb:164:in `block in __run' > /usr/lib/ruby/vendor_ruby/minitest.rb:164:in `map' > /usr/lib/ruby/vendor_ruby/minitest.rb:164:in `__run' > /usr/lib/ruby/vendor_ruby/minitest.rb:141:in `run' > /usr/lib/ruby/vendor_ruby/minitest.rb:68:in `block in autorun' > > 618 runs, 1426 assertions, 0 failures, 32 errors, 3 skips > rake aborted! > Command failed with status (1): [ruby -w -I"test" > /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/rake_test_loader.rb > "test/integration/assign_test.rb" "test/integration/blank_test.rb" > "test/integration/block_test.rb" "test/integration/capture_test.rb" > "test/integration/context_test.rb" "test/integration/document_test.rb" > "test/integration/drop_test.rb" "test/integration/error_handling_test.rb" > "test/integration/filter_test.rb" "test/integration/hash_ordering_test.rb" > "test/integration/output_test.rb" > "test/integration/parse_tree_visitor_test.rb" > "test/integration/parsing_quirks_test.rb" > "test/integration/render_profiling_test.rb" > "test/integration/security_test.rb" > "test/integration/standard_filter_test.rb" > "test/integration/tags/break_tag_test.rb" > "test/integration/tags/continue_tag_test.rb" > "test/integration/tags/for_tag_test.rb" > "test/integration/tags/if_else_tag_test.rb" > "test/integration/tags/include_tag_test.rb" > "test/integration/tags/increment_tag_test.rb" > "test/integration/tags/raw_tag_test.rb" > "test/integration/tags/standard_tag_test.rb" > "test/integration/tags/statements_test.rb" > "test/integration/tags/table_row_test.rb" > "test/integration/tags/unless_else_tag_test.rb" > "test/integration/template_test.rb" "test/integration/trim_mode_test.rb" > "test/integration/variable_test.rb" "test/truffle/truffle_test.rb" > "test/unit/block_unit_test.rb" "test/unit/condition_unit_test.rb" > "test/unit/context_unit_test.rb" "test/unit/file_system_unit_test.rb" > "test/unit/i18n_unit_test.rb" "test/unit/lexer_unit_test.rb" > "test/unit/parser_unit_test.rb" "test/unit/regexp_unit_test.rb" > "test/unit/strainer_unit_test.rb" "test/unit/tag_unit_test.rb" > "test/unit/tags/case_tag_unit_test.rb" "test/unit/tags/for_tag_unit_test.rb" > "test/unit/tags/if_tag_unit_test.rb" "test/unit/template_unit_test.rb" > "test/unit/tokenizer_unit_test.rb" "test/unit/variable_unit_test.rb" > "test/test_helper.rb" -v] > > Tasks: TOP => default > (See full trace by running task with --trace) > ERROR: Test "ruby3.0" failed: The full build log is available at
Bug#996313: ruby-libvirt: FTBFS with ruby3.0: common.c:27:10: fatal error: st.h: No such file or directory
Source: ruby-libvirt Version: 0.7.1-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-libvirt was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): > gcc -fdebug-prefix-map=/<>=. -I. > -I/usr/include/x86_64-linux-gnu/ruby-3.0.0 > -I/usr/include/ruby-3.0.0/ruby/backward -I/usr/include/ruby-3.0.0 -I. > -DRUBY_EXTCONF_H=\"extconf.h\" -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -g -O2 > -ffile-prefix-map=/build/ruby3.0-2KsnwC/ruby3.0-3.0.2=. > -fstack-protector-strong -Wformat -Werror=format-security -fPIC -o common.o > -c common.c > common.c:27:10: fatal error: st.h: No such file or directory >27 | #include > | ^~ > compilation terminated. > make[2]: *** [Makefile:245: common.o] Error 1 The full build log is available at https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-libvirt/ruby-libvirt_0.7.1-1+rebuild1633385464_amd64.build.txt signature.asc Description: PGP signature
Bug#996312: ruby-librarian: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: tried to create Proc object without a block
Source: ruby-librarian
Version: 0.6.4-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.0
Hi,
We are about to enable building against ruby3.0 on unstable. During a test
rebuild, ruby-librarian was found to fail to build in that situation.
To reproduce this locally, you need to install ruby-all-dev from experimental
on an unstable system or build chroot.
Relevant part (hopefully):
> ArgumentError:
> tried to create Proc object without a block
> # ./lib/librarian/dsl.rb:89:in `new'
> # ./lib/librarian/dsl.rb:89:in `block in run'
> # :90:in `tap'
> # ./lib/librarian/dsl.rb:85:in `run'
> # ./lib/librarian/dsl.rb:17:in `run'
> # ./lib/librarian/environment.rb:148:in `dsl'
> # ./spec/unit/spec_change_set_spec.rb:150:in `block (3 levels) in
> '
>
> Deprecation Warnings:
>
> Using `should` from rspec-expectations' old `:should` syntax without
> explicitly enabling the syntax is deprecated. Use the new `:expect` syntax or
> explicitly enable `:should` with `config.expect_with(:rspec) { |c| c.syntax =
> :should }` instead. Called from
> /<>/spec/unit/dependency/requirement_spec.rb:13:in `block (2
> levels) in '.
>
> Using `stub` from rspec-mocks' old `:should` syntax without explicitly
> enabling the syntax is deprecated. Use the new `:expect` syntax or explicitly
> enable `:should` instead. Called from
> /<>/spec/unit/action/clean_spec.rb:10:in `block (2 levels) in
> '.
>
>
> If you need more of the backtrace for any of these deprecations to
> identify where to make the necessary changes, you can configure
> `config.raise_errors_for_deprecations!`, and it will turn the
> deprecation warnings into errors, giving you the full backtrace.
>
> 2 deprecation warnings total
>
> Finished in 12.01 seconds (files took 1.01 seconds to load)
> 343 examples, 34 failures, 1 pending
>
> Failed examples:
>
> rspec ./spec/unit/dsl_spec.rb:12 # Librarian::Mock::Dsl a single source and a
> single dependency with a blank name should not not run with a blank name
> rspec ./spec/unit/dsl_spec.rb:24 # Librarian::Mock::Dsl a simple specfile - a
> single source, a single dependency, no transitive dependencies should run
> with a hash source
> rspec ./spec/unit/dsl_spec.rb:35 # Librarian::Mock::Dsl a simple specfile - a
> single source, a single dependency, no transitive dependencies should run
> with a shortcut source
> rspec ./spec/unit/dsl_spec.rb:46 # Librarian::Mock::Dsl a simple specfile - a
> single source, a single dependency, no transitive dependencies should run
> with a block hash source
> rspec ./spec/unit/dsl_spec.rb:58 # Librarian::Mock::Dsl a simple specfile - a
> single source, a single dependency, no transitive dependencies should run
> with a block named source
> rspec ./spec/unit/dsl_spec.rb:70 # Librarian::Mock::Dsl a simple specfile - a
> single source, a single dependency, no transitive dependencies should run
> with a default hash source
> rspec ./spec/unit/dsl_spec.rb:82 # Librarian::Mock::Dsl a simple specfile - a
> single source, a single dependency, no transitive dependencies should run
> with a default named source
> rspec ./spec/unit/dsl_spec.rb:94 # Librarian::Mock::Dsl a simple specfile - a
> single source, a single dependency, no transitive dependencies should run
> with a default shortcut source
> rspec ./spec/unit/dsl_spec.rb:106 # Librarian::Mock::Dsl a simple specfile -
> a single source, a single dependency, no transitive dependencies should run
> with a shortcut source hash definition
> rspec ./spec/unit/dsl_spec.rb:117 # Librarian::Mock::Dsl a simple specfile -
> a single source, a single dependency, no transitive dependencies should run
> with a shortcut source block definition
> rspec ./spec/unit/dsl_spec.rb:128 # Librarian::Mock::Dsl a simple specfile -
> a single source, a single dependency, no transitive dependencies should run
> with a default shortcut source hash definition
> rspec ./spec/unit/dsl_spec.rb:141 # Librarian::Mock::Dsl a simple specfile -
> a single source, a single dependency, no transitive dependencies should run
> with a default shortcut source block definition
> rspec ./spec/unit/dsl_spec.rb:158 # Librarian::Mock::Dsl validating source
> options should raise when given unrecognized optiosn options
> rspec ./spec/unit/lockfile_spec.rb:31 # Librarian::Lockfile sanity the
> resolution
> rspec ./spec/unit/lockfile_spec.rb:32 # Librarian::Lockfile sanity the
> resolution
> rspec ./spec/unit/lockfile_spec.rb:41 # Librarian::Lockfile#save just saving
> should return the lockfile text
> rspec ./spec/unit/lockfile_spec.rb:49 # Librarian::Lockfile#save saving and
> reloading should have the expected manifests
> rspec ./spec/unit/lockfile_spec.rb:58 # Librarian::Lockfile#save bouncing
> should return the same lockfile text after bouncing as before bouncing
> rspec ./spec/unit/resolver_spec.rb:36 #
Bug#996311: ruby-lapack: FTBFS: ERROR: Test "ruby2.7" failed.
Source: ruby-lapack Version: 1.8.1-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-lapack was found to fail to build in that situation. Relevant part (hopefully): > /usr/bin/ruby2.7 /usr/bin/gem2deb-test-runner > > ┌──┐ > │ Run tests for ruby2.7 from debian/ruby-tests.rake > │ > └──┘ > > RUBYLIB=/<>/debian/ruby-lapack/usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/2.7.0:/<>/debian/ruby-lapack/usr/lib/ruby/vendor_ruby:. > > GEM_PATH=/<>/debian/ruby-lapack/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"tests" > /usr/share/rubygems-integration/all/gems/rake-13.0.3/lib/rake/rake_test_loader.rb > "tests/eig/ge/test_gesdd.rb" "tests/eig/ge/test_gesvd.rb" > "tests/eig/gg/test_ggev.rb" "tests/eig/gg/test_ggsvd.rb" > "tests/eig/sb/test_sbev.rb" "tests/lapack_test.rb" > "tests/lin/gb/test_gbsv.rb" "tests/lin/gb/test_gbsvx.rb" > "tests/lin/ge/test_gels.rb" "tests/lin/ge/test_gelsd.rb" > "tests/lin/ge/test_gelss.rb" "tests/lin/ge/test_gelsy.rb" > "tests/lin/ge/test_gesv.rb" "tests/lin/ge/test_gesvx.rb" > "tests/lin/gt/test_gtsv.rb" "tests/lin/sy/test_sysv.rb" -v > /<>/tests/eig/ge/test_gesdd.rb:48: warning: assigned but unused > variable - vt > /<>/tests/eig/ge/test_gesdd.rb:48: warning: assigned but unused > variable - work > /<>/tests/eig/ge/test_gesdd.rb:62: warning: assigned but unused > variable - vt > /<>/tests/eig/ge/test_gesdd.rb:80: warning: assigned but unused > variable - s > /<>/tests/eig/ge/test_gesdd.rb:80: warning: assigned but unused > variable - u > /<>/tests/eig/ge/test_gesdd.rb:80: warning: assigned but unused > variable - vt > /<>/tests/eig/ge/test_gesdd.rb:83: warning: assigned but unused > variable - a > /<>/lib/numru/lapack.rb:21: warning: assigned but unused > variable - l > /<>/lib/numru/lapack.rb:49: warning: mismatched indentations at > 'end' with 'def' at 28 > /<>/tests/eig/ge/test_gesvd.rb:56: warning: assigned but unused > variable - work > /<>/tests/eig/ge/test_gesvd.rb:71: warning: assigned but unused > variable - u > /<>/tests/eig/ge/test_gesvd.rb:89: warning: assigned but unused > variable - s > /<>/tests/eig/ge/test_gesvd.rb:89: warning: assigned but unused > variable - u > /<>/tests/eig/ge/test_gesvd.rb:89: warning: assigned but unused > variable - vt > /<>/tests/eig/ge/test_gesvd.rb:89: warning: assigned but unused > variable - a > /<>/tests/eig/gg/test_ggev.rb:28: warning: `+' after local > variable or literal is interpreted as binary operator > /<>/tests/eig/gg/test_ggev.rb:28: warning: even though it seems > like unary operator > /<>/tests/eig/gg/test_ggev.rb:29: warning: `-' after local > variable or literal is interpreted as binary operator > /<>/tests/eig/gg/test_ggev.rb:29: warning: even though it seems > like unary operator > /<>/tests/eig/gg/test_ggev.rb:29: warning: `+' after local > variable or literal is interpreted as binary operator > /<>/tests/eig/gg/test_ggev.rb:29: warning: even though it seems > like unary operator > /<>/tests/eig/gg/test_ggev.rb:29: warning: `-' after local > variable or literal is interpreted as binary operator > /<>/tests/eig/gg/test_ggev.rb:29: warning: even though it seems > like unary operator > /<>/tests/eig/gg/test_ggev.rb:30: warning: `-' after local > variable or literal is interpreted as binary operator > /<>/tests/eig/gg/test_ggev.rb:30: warning: even though it seems > like unary operator > /<>/tests/eig/gg/test_ggev.rb:30: warning: `+' after local > variable or literal is interpreted as binary operator > /<>/tests/eig/gg/test_ggev.rb:30: warning: even though it seems > like unary operator > /<>/tests/eig/gg/test_ggev.rb:30: warning: `-' after local > variable or literal is interpreted as binary operator > /<>/tests/eig/gg/test_ggev.rb:30: warning: even though it seems > like unary operator > /<>/tests/eig/gg/test_ggev.rb:31: warning: `+' after local > variable or literal is interpreted as binary operator > /<>/tests/eig/gg/test_ggev.rb:31: warning: even though it seems > like unary operator > /<>/tests/eig/gg/test_ggev.rb:31: warning: `-' after local > variable or literal is interpreted as binary operator > /<>/tests/eig/gg/test_ggev.rb:31: warning: even though it seems > like unary operator > /<>/tests/eig/gg/test_ggev.rb:51: warning: assigned but unused > variable - vl > /<>/tests/eig/gg/test_ggev.rb:51: warning: assigned but unused > variable - work
Bug#996310: ruby-kyotocabinet: FTBFS with ruby3.0: stdalign.h:93:1: error: template with C linkage
Source: ruby-kyotocabinet
Version: 1.33-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.0
Hi,
We are about to enable building against ruby3.0 on unstable. During a test
rebuild, ruby-kyotocabinet was found to fail to build in that situation.
To reproduce this locally, you need to install ruby-all-dev from experimental
on an unstable system or build chroot.
Relevant part (hopefully):
> g++ -fdebug-prefix-map=/<>=. -I.
> -I/usr/include/x86_64-linux-gnu/ruby-3.0.0
> -I/usr/include/ruby-3.0.0/ruby/backward -I/usr/include/ruby-3.0.0 -I.
> -DHAVE_KCCOMMON_H -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -g -O2
> -ffile-prefix-map=/build/ruby3.0-2KsnwC/ruby3.0-3.0.2=.
> -fstack-protector-strong -Wformat -Werror=format-security -o kyotocabinet.o
> -c kyotocabinet.cc
> In file included from /usr/include/ruby-3.0.0/ruby/backward/2/stdalign.h:23,
> from /usr/include/ruby-3.0.0/ruby/defines.h:77,
> from /usr/include/ruby-3.0.0/ruby/ruby.h:23,
> from /usr/include/ruby-3.0.0/ruby.h:38,
> from kyotocabinet.cc:22:
> /usr/include/ruby-3.0.0/ruby/internal/stdalign.h:93:1: error: template with C
> linkage
>93 | template
> | ^~~~
> kyotocabinet.cc:20:1: note: ‘extern "C"’ linkage started here
>20 | extern "C" {
> | ^~
> make[1]: *** [Makefile:213: kyotocabinet.o] Error 1
The full build log is available at
https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-kyotocabinet/ruby-kyotocabinet_1.33-1+rebuild1633384978_amd64.build.txt
signature.asc
Description: PGP signature
Bug#996308: ruby-kitchen-salt: FTBFS: ERROR: Test "ruby2.7" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block in activate_dependencies': Could not find 'thor' (~> 0.
Source: ruby-kitchen-salt Version: 0.4.0-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-kitchen-salt was found to fail to build in that situation. This does not look related to ruby3.0, but a dependency on thor that is too strict. Relevant part (hopefully): > /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block > in activate_dependencies': Could not find 'thor' (~> 0.19) among 70 total > gem(s) (Gem::MissingSpecError) > Checked in > 'GEM_PATH=/<>/debian/ruby-kitchen-salt/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' > at: > /usr/share/rubygems-integration/all/specifications/test-kitchen-1.23.2.gemspec, > execute `gem env` for more information > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1401:in `block > in activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in > `activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372:in > `activate' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1408:in `block > in activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in > `activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372:in > `activate' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `block in gem' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `synchronize' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `gem' > from -e:1:in `' > /usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:313:in `to_specs': Could not > find 'thor' (~> 0.19) - did find: [thor-1.0.1] (Gem::MissingSpecVersionError) > Checked in > 'GEM_PATH=/<>/debian/ruby-kitchen-salt/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' > , execute `gem env` for more information > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1402:in `block > in activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in > `activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372:in > `activate' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1408:in `block > in activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in > `activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372:in > `activate' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `block in gem' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `synchronize' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `gem' > from -e:1:in `' > bcrypt_pbkdf (1.1.0) > benchmark (default: 0.1.0) > bigdecimal (default: 2.0.0) > bundler (default: 2.1.4) > cgi (default: 0.1.0) > chef-utils (16.12.3) > csv (default: 3.1.2) > date (default: 3.0.0) > dbm (default: 1.1.0) > delegate (default: 0.1.0) > did_you_mean (default: 1.4.0) > ed25519 (1.2.4) > etc (default: 1.1.0) > fcntl (default: 1.0.0) > fiddle (default: 1.0.0) > fileutils (default: 1.4.1) > forwardable (default: 1.3.1) > gdbm (default: 2.1.0) > getoptlong (default: 0.1.0) > hashie (3.5.5) > io-console (default: 0.5.6) > ipaddr (default: 1.2.2) > irb (default: 1.2.6) > json (default: 2.3.0) > logger (default: 1.4.2) > matrix (default: 0.2.0) > minitest (5.13.0) > mixlib-install (3.11.7) > mixlib-shellout (3.2.5) > mixlib-versioning (1.1.0) > mutex_m (default: 0.1.0) > net-pop (default: 0.1.0) > net-scp (3.0.0) > net-smtp (default: 0.1.0) > net-ssh (6.1.0) > net-ssh-gateway (2.0.0) > net-telnet (0.1.1) > observer (default: 0.1.0) > open3 (default: 0.1.0) > openssl (default: 2.1.2) > ostruct (default: 0.2.0) > power_assert (1.1.7) > prime (default: 0.1.1) > pstore (default: 0.1.0) > psych (default: 3.1.0) > racc (default: 1.4.16) > rake (13.0.3) > rdoc (default: 6.2.1.1) > readline (default: 0.0.2) > readline-ext (default: 0.1.0) > reline
Bug#996309: ruby-kubeclient: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: /usr/lib/ruby/vendor_ruby/recursive_open_struct.rb:84:in `alias_method': undefined method `modifiable' for class `Recursi
Source: ruby-kubeclient Version: 4.9.2-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-kubeclient was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): > /usr/lib/ruby/vendor_ruby/recursive_open_struct.rb:84:in `alias_method': > undefined method `modifiable' for class `RecursiveOpenStruct' (NameError) > Did you mean? module > from /usr/lib/ruby/vendor_ruby/recursive_open_struct.rb:84:in > `' > from /usr/lib/ruby/vendor_ruby/recursive_open_struct.rb:16:in ` (required)>' > from > :85:in > `require' > from > :85:in > `require' > from > /<>/debian/ruby-kubeclient/usr/lib/ruby/vendor_ruby/kubeclient/resource.rb:1:in > `' > from > :85:in > `require' > from > :85:in > `require' > from > /<>/debian/ruby-kubeclient/usr/lib/ruby/vendor_ruby/kubeclient.rb:13:in > `' > from > :85:in > `require' > from > :85:in > `require' > from /<>/test/test_helper.rb:6:in `' > from /<>/test/test_common.rb:2:in `require_relative' > from /<>/test/test_common.rb:2:in `' > from > :85:in > `require' > from > :85:in > `require' > from > /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/rake_test_loader.rb:17:in > `block in ' > from > /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/rake_test_loader.rb:5:in > `select' > from > /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/rake_test_loader.rb:5:in > `' > rake aborted! > Command failed with status (1): [ruby -w -I"test" > /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/rake_test_loader.rb > "test/test_common.rb" "test/test_common_url_handling.rb" > "test/test_component_status.rb" "test/test_config.rb" "test/test_endpoint.rb" > "test/test_exec_credentials.rb" "test/test_gcp_command_credentials.rb" > "test/test_google_application_default_credentials.rb" "test/test_helper.rb" > "test/test_kubeclient.rb" "test/test_limit_range.rb" > "test/test_missing_methods.rb" "test/test_namespace.rb" "test/test_node.rb" > "test/test_oidc_auth_provider.rb" "test/test_persistent_volume.rb" > "test/test_persistent_volume_claim.rb" "test/test_pod.rb" > "test/test_pod_log.rb" "test/test_process_template.rb" > "test/test_replication_controller.rb" > "test/test_resource_list_without_kind.rb" "test/test_resource_quota.rb" > "test/test_secret.rb" "test/test_security_context_constraint.rb" > "test/test_service.rb" "test/test_service_account.rb" "test/test_watch.rb" -v] > > Tasks: TOP => default > (See full trace by running task with --trace) > ERROR: Test "ruby3.0" failed: The full build log is available at https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-kubeclient/ruby-kubeclient_4.9.2-1+rebuild1633384926_amd64.build.txt signature.asc Description: PGP signature
Bug#996307: ruby-kitchen-docker: FTBFS: ERROR: Test "ruby2.7" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block in activate_dependencies': Could not find 'thor' (~>
Source: ruby-kitchen-docker Version: 2.7.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-kitchen-docker was found to fail to build in that situation. This does not seem related to ruby3.0, and looks like a missing build dependency? Relevant part (hopefully): > /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block > in activate_dependencies': Could not find 'thor' (~> 0.19) among 82 total > gem(s) (Gem::MissingSpecError) > Checked in > 'GEM_PATH=/<>/debian/ruby-kitchen-docker/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' > at: > /usr/share/rubygems-integration/all/specifications/test-kitchen-1.23.2.gemspec, > execute `gem env` for more information > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1401:in `block > in activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in > `activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372:in > `activate' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1408:in `block > in activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in > `activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372:in > `activate' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `block in gem' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `synchronize' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `gem' > from -e:1:in `' > /usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:313:in `to_specs': Could not > find 'thor' (~> 0.19) - did find: [thor-1.0.1] (Gem::MissingSpecVersionError) > Checked in > 'GEM_PATH=/<>/debian/ruby-kitchen-docker/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' > , execute `gem env` for more information > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1402:in `block > in activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in > `activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372:in > `activate' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1408:in `block > in activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in > `activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372:in > `activate' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `block in gem' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `synchronize' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `gem' > from -e:1:in `' > bcrypt_pbkdf (1.1.0) > benchmark (default: 0.1.0) > bigdecimal (default: 2.0.0) > bundler (default: 2.1.4) > cgi (default: 0.1.0) > chef-utils (16.12.3) > csv (default: 3.1.2) > date (default: 3.0.0) > dbm (default: 1.1.0) > delegate (default: 0.1.0) > did_you_mean (default: 1.4.0) > diff-lcs (1.4.4) > docile (1.1.5) > ed25519 (1.2.4) > etc (default: 1.1.0) > fcntl (default: 1.0.0) > fiddle (default: 1.0.0) > fileutils (default: 1.4.1) > forwardable (default: 1.3.1) > gdbm (default: 2.1.0) > getoptlong (default: 0.1.0) > io-console (default: 0.5.6) > ipaddr (default: 1.2.2) > irb (default: 1.2.6) > json (default: 2.3.0) > logger (default: 1.4.2) > matrix (default: 0.2.0) > minitest (5.13.0) > mixlib-install (3.11.7) > mixlib-shellout (3.2.5) > mixlib-versioning (1.1.0) > multi_json (1.14.1) > mutex_m (default: 0.1.0) > net-pop (default: 0.1.0) > net-scp (3.0.0) > net-smtp (default: 0.1.0) > net-ssh (6.1.0) > net-ssh-gateway (2.0.0) > net-telnet (0.1.1) > observer (default: 0.1.0) > open3 (default: 0.1.0) > openssl (default: 2.1.2) > ostruct (default: 0.2.0) > power_assert (1.1.7) > prime (default: 0.1.1) > pstore (default: 0.1.0) > psych (default: 3.1.0) > racc (default: 1.4.16) > rake (13.0.3) > rdoc (default: 6.2.1.1) > readline (default:
Bug#996306: ruby-jsonpath: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: RuntimeError: character '|' not supported in query.
Source: ruby-jsonpath Version: 1.0.5-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-jsonpath was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): > RuntimeError: character '|' not supported in query. > ArgumentError expected but nothing was raised. > > 89 runs, 122 assertions, 1 failures, 0 errors, 0 skips > rake aborted! > Command failed with status (1): [ruby -w -I"test" > /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/rake_test_loader.rb > "test/test_jsonpath.rb" "test/test_jsonpath_bin.rb" -v] > > Tasks: TOP => default > (See full trace by running task with --trace) > ERROR: Test "ruby3.0" failed: The full build log is available at https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-jsonpath/ruby-jsonpath_1.0.5-2+rebuild1633384673_amd64.build.txt signature.asc Description: PGP signature
Bug#996305: ruby-json: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: NoMethodError: undefined method `assert_separately'
Source: ruby-json
Version: 2.5.1+dfsg-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.0
Hi,
We are about to enable building against ruby3.0 on unstable. During a test
rebuild, ruby-json was found to fail to build in that situation.
To reproduce this locally, you need to install ruby-all-dev from experimental
on an unstable system or build chroot.
Relevant part (hopefully):
> Did you mean? assert_empty>, @method_name="test_generate">],
> @stop_tag=#, @failures=[],
> @errors=[# @test_name="test_generate(JSONInRactorTest)", @exception=# undefined method `assert_separately' for
> #
> Did you mean? assert_empty>, @method_name="test_generate">], @pendings=[],
> @omissions=[], @notifications=[],
> @channels={"Test::Unit::TestResult::FINISHED"=>{# @a_proc=# /usr/share/rubygems-integration/all/gems/test-unit-3.3.9/lib/test/unit/ui/testrunnermediator.rb:88>,
> @hash=94281040049560>=># /usr/share/rubygems-integration/all/gems/test-unit-3.3.9/lib/test/unit/ui/testrunnermediator.rb:88>},
>
> "Test::Unit::TestResult::CHANGED"=>{# @a_proc=# /usr/share/rubygems-integration/all/gems/test-unit-3.3.9/lib/test/unit/ui/testrunnermediator.rb:91>,
> @hash=94281040048400>=># /usr/share/rubygems-integration/all/gems/test-unit-3.3.9/lib/test/unit/ui/testrunnermediator.rb:91>},
>
> "Test::Unit::TestResult::PASS_ASSERTION"=>{# @a_proc=# /usr/share/rubygems-integration/all/gems/test-unit-3.3.9/lib/test/unit/ui/testrunnermediator.rb:94>,
> @hash=94281040047360>=># /usr/share/rubygems-integration/all/gems/test-unit-3.3.9/lib/test/unit/ui/testrunnermediator.rb:94>},
>
> "Test::Unit::TestResult::FAULT"=>{# @a_proc=# /usr/share/rubygems-integration/all/gems/test-unit-3.3.9/lib/test/unit/ui/testrunnermediator.rb:97>,
> @hash=94281040046320>=># /usr/share/rubygems-integration/all/gems/test-unit-3.3.9/lib/test/unit/ui/testrunnermediator.rb:97>}}>>
> Did you mean? assert_empty
> /<>/tests/ractor_test.rb:8:in `test_generate'
> 5:
> 6: class JSONInRactorTest < Test::Unit::TestCase
> 7: def test_generate
> => 8: assert_separately([], "#{<<~"begin;"}\n#{<<~'end;'}")
> 9: begin;
> 10: $VERBOSE = nil
> 11: require "json"
> ===
> : (0.042820)
> JSONParserTest:
> test_argument_encoding: .: (0.000209)
> test_backslash: .: (0.000121)
> test_construction: .: (0.78)
> test_error_message_encoding:.: (0.000158)
> test_freeze:.: (0.000218)
> test_generate_core_subclasses_with_default_to_json: .: (0.000145)
> test_generate_core_subclasses_with_new_to_json: .: (0.000242)
> test_generate_of_core_subclasses: .: (0.000123)
> test_nesting: .: (0.000632)
> test_parse_array_custom_array_derived_class:.: (0.000104)
> test_parse_array_custom_non_array_derived_class:.: (0.000105)
> test_parse_arrays: .: (0.000156)
> test_parse_big_integers:.: (0.000178)
> test_parse_bigdecimals: .: (0.000125)
> test_parse_comments:.: (0.000163)
> test_parse_complex_objects: .: (0.019595)
> test_parse_generic_object: .: (0.000173)
> test_parse_json_primitive_values: .: (0.000492)
> test_parse_more_complex_arrays: .: (0.012031)
> test_parse_numbers: .: (0.000589)
> test_parse_object: .: (0.000103)
> test_parse_object_custom_hash_derived_class:.: (0.000108)
> test_parse_object_custom_non_hash_derived_class:.: (0.000154)
> test_parse_simple_arrays: .: (0.000364)
> test_parse_simple_objects: .: (0.000253)
> test_parse_some_strings:.: (0.000102)
> test_parse_values: .: (0.000173)
> test_parser_reset: .: (0.82)
> test_parsing: .: (0.70)
> test_parsing_frozen_ascii8bit_string: .: (0.81)
> test_some_wrong_inputs: .: (0.000475)
> test_symbolize_names: .: (0.000127)
> JSONStringMatchingTest:
> test_match_date:.: (0.000540)
>
> Finished in 0.138216227 seconds.
> ---
> 103 tests, 2057 assertions, 0 failures, 1 errors, 0 pendings, 0 omissions,
Bug#996304: ruby-json-schema: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Errno::ENOENT: No such file or directory @ rb_sysopen - http://foo.bar/
Source: ruby-json-schema Version: 2.8.1-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-json-schema was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): > Errno::ENOENT: No such file or directory @ rb_sysopen - http://foo.bar/ > /<>/lib/json-schema/validator.rb:596:in `initialize' > /<>/lib/json-schema/validator.rb:596:in `open' > /<>/lib/json-schema/validator.rb:596:in `custom_open' > /<>/lib/json-schema/validator.rb:582:in `rescue in > initialize_data' > /<>/lib/json-schema/validator.rb:577:in `initialize_data' > /<>/lib/json-schema/validator.rb:55:in `initialize' > /<>/lib/json-schema/validator.rb:255:in `new' > /<>/lib/json-schema/validator.rb:255:in `validate!' > /<>/lib/json-schema/validator.rb:240:in `validate' > /<>/test/initialize_data_test.rb:80:in > `test_parse_valid_uri_string' > /usr/lib/ruby/vendor_ruby/minitest/test.rb:98:in `block (3 levels) in run' > /usr/lib/ruby/vendor_ruby/minitest/test.rb:195:in `capture_exceptions' > /usr/lib/ruby/vendor_ruby/minitest/test.rb:95:in `block (2 levels) in run' > /usr/lib/ruby/vendor_ruby/minitest.rb:270:in `time_it' > /usr/lib/ruby/vendor_ruby/minitest/test.rb:94:in `block in run' > /usr/lib/ruby/vendor_ruby/minitest.rb:365:in `on_signal' > /usr/lib/ruby/vendor_ruby/minitest/test.rb:211:in `with_info_handler' > /usr/lib/ruby/vendor_ruby/minitest/test.rb:93:in `run' > /usr/lib/ruby/vendor_ruby/minitest.rb:1029:in `run_one_method' > /usr/lib/ruby/vendor_ruby/minitest.rb:339:in `run_one_method' > /usr/lib/ruby/vendor_ruby/minitest.rb:326:in `block (2 levels) in run' > /usr/lib/ruby/vendor_ruby/minitest.rb:325:in `each' > /usr/lib/ruby/vendor_ruby/minitest.rb:325:in `block in run' > /usr/lib/ruby/vendor_ruby/minitest.rb:365:in `on_signal' > /usr/lib/ruby/vendor_ruby/minitest.rb:352:in `with_info_handler' > /usr/lib/ruby/vendor_ruby/minitest.rb:324:in `run' > /usr/lib/ruby/vendor_ruby/minitest.rb:164:in `block in __run' > /usr/lib/ruby/vendor_ruby/minitest.rb:164:in `map' > /usr/lib/ruby/vendor_ruby/minitest.rb:164:in `__run' > /usr/lib/ruby/vendor_ruby/minitest.rb:141:in `run' > /usr/lib/ruby/vendor_ruby/minitest.rb:68:in `block in autorun' > > 363 runs, 1596 assertions, 2 failures, 3 errors, 0 skips > rake aborted! > Command failed with status (1): [ruby -w -I"test" > /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/rake_test_loader.rb > "test/all_of_ref_schema_test.rb" "test/any_of_ref_schema_test.rb" > "test/bad_schema_ref_test.rb" "test/caching_test.rb" > "test/common_test_suite_test.rb" "test/custom_format_test.rb" > "test/draft1_test.rb" "test/draft2_test.rb" "test/draft3_test.rb" > "test/draft4_test.rb" "test/extended_schema_test.rb" > "test/extends_nested_test.rb" "test/files_test.rb" > "test/fragment_resolution_test.rb" > "test/fragment_validation_with_ref_test.rb" "test/full_validation_test.rb" > "test/initialize_data_test.rb" "test/list_option_test.rb" > "test/load_ref_schema_test.rb" "test/merge_missing_values_test.rb" > "test/min_items_test.rb" "test/one_of_test.rb" > "test/relative_definition_test.rb" "test/ruby_schema_test.rb" > "test/schema_reader_test.rb" "test/schema_validation_test.rb" > "test/stringify_test.rb" "test/type_attribute_test.rb" > "test/uri_parsing_test.rb" "test/uri_util_test.rb" > "test/validator_schema_reader_test.rb" "test/support/test_helper.rb" -v] > > Tasks: TOP => default > (See full trace by running task with --trace) > ERROR: Test "ruby3.0" failed: The full build log is available at https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-json-schema/ruby-json-schema_2.8.1-2+rebuild1633384561_amd64.build.txt signature.asc Description: PGP signature
Bug#996303: ruby-json-jwt: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Failure/Error:
Source: ruby-json-jwt
Version: 1.11.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.0
Hi,
We are about to enable building against ruby3.0 on unstable. During a test
rebuild, ruby-json-jwt was found to fail to build in that situation.
To reproduce this locally, you need to install ruby-all-dev from experimental
on an unstable system or build chroot.
Relevant part (hopefully):
> Failure/Error:
>jws_blank.to_json(syntax: :flattened).should == {
> protected: Base64.urlsafe_encode64(jws_blank.header.to_json,
> padding: false),
> payload: '',
> signature: Base64.urlsafe_encode64('', padding: false)
>}.to_json
>
>expected:
> "{\"protected\":\"eyJ0eXAiOiJKV1QiLCJhbGciOiJSUzI1NiJ9\",\"payload\":\"\",\"signature\":\"\"}"
> got: "{}" (using ==)
> # ./spec/json/jws_spec.rb:429:in `block (7 levels) in '
>
> Finished in 1.98 seconds (files took 2.47 seconds to load)
> 360 examples, 8 failures, 6 pending
>
> Failed examples:
>
> rspec ./spec/json/jws_spec.rb:356 # JSON::JWS#to_json when syntax option
> given when general should return General JWS JSON Serialization
> rspec ./spec/json/jws_spec.rb:366 # JSON::JWS#to_json when syntax option
> given when general with blank payload should return General JWS JSON
> Serialization
> rspec ./spec/json/jws_spec.rb:378 # JSON::JWS#to_json when syntax option
> given when general when not signed yet should not fail
> rspec ./spec/json/jws_spec.rb:388 # JSON::JWS#to_json when syntax option
> given when general when not signed yet with blank payload should not fail
> rspec ./spec/json/jws_spec.rb:402 # JSON::JWS#to_json when syntax option
> given when flattened should return Flattened JWS JSON Serialization
> rspec ./spec/json/jws_spec.rb:410 # JSON::JWS#to_json when syntax option
> given when flattened with blank payload should return Flattened JWS JSON
> Serialization
> rspec ./spec/json/jws_spec.rb:420 # JSON::JWS#to_json when syntax option
> given when flattened when not signed yet should not fail
> rspec ./spec/json/jws_spec.rb:428 # JSON::JWS#to_json when syntax option
> given when flattened when not signed yet with blank payload should not fail
>
> /usr/bin/ruby3.0
> -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 "ruby3.0" failed:
The full build log is available at
https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-json-jwt/ruby-json-jwt_1.11.0-1+rebuild1633384555_amd64.build.txt
signature.asc
Description: PGP signature
Bug#996302: ruby-joiner: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Failure/Error: require 'bundler/setup'
Source: ruby-joiner
Version: 0.5.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.0
Hi,
We are about to enable building against ruby3.0 on unstable. During a test
rebuild, ruby-joiner was found to fail to build in that situation.
To reproduce this locally, you need to install ruby-all-dev from experimental
on an unstable system or build chroot.
Relevant part (hopefully):
> Failure/Error: require 'bundler/setup'
>
> Bundler::GemNotFound:
> Could not find racc-1.4.16 in any of the sources
> #
> /usr/share/rubygems-integration/all/gems/bundler-2.2.27/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.5 seconds (files took 0.59366 seconds to load)
> 0 examples, 0 failures, 2 errors occurred outside of examples
>
> /usr/bin/ruby3.0
> -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 "ruby3.0" failed:
The full build log is available at
https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-joiner/ruby-joiner_0.5.0-2+rebuild1633384371_amd64.build.txt
signature.asc
Description: PGP signature
Bug#996301: ruby-jbuilder: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed.
Source: ruby-jbuilder Version: 2.10.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-jbuilder was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): > /usr/bin/ruby3.0 /usr/bin/gem2deb-test-runner > > ┌──┐ > │ Checking Rubygems dependency resolution on ruby3.0 > │ > └──┘ > > GEM_PATH=/<>/debian/ruby-jbuilder/usr/share/rubygems-integration/all:/var/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0 > ruby3.0 -e gem\ \"jbuilder\" > > ┌──┐ > │ Run tests for ruby3.0 from debian/ruby-tests.rake > │ > └──┘ > > RUBYLIB=/<>/debian/ruby-jbuilder/usr/lib/ruby/vendor_ruby:. > GEM_PATH=/<>/debian/ruby-jbuilder/usr/share/rubygems-integration/all:/var/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0 > ruby3.0 -S rake -f debian/ruby-tests.rake > /usr/bin/ruby3.0 -w -I"test" > /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/rake_test_loader.rb > "test/jbuilder_dependency_tracker_test.rb" "test/jbuilder_generator_test.rb" > "test/jbuilder_template_test.rb" "test/jbuilder_test.rb" > "test/scaffold_api_controller_generator_test.rb" > "test/scaffold_controller_generator_test.rb" -v > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/core_ext/hash/except.rb:12: > warning: method redefined; discarding old except > /usr/lib/ruby/vendor_ruby/tzinfo/ruby_core_support.rb:163: warning: > Object#taint is deprecated and will be removed in Ruby 3.2 > /usr/lib/ruby/vendor_ruby/tzinfo/ruby_core_support.rb:163: warning: > Object#tainted? is deprecated and will be removed in Ruby 3.2 > Run options: -v --seed 5207 > > # Running: > > JbuilderGeneratorTest#test_index_content = 0.02 s = . > JbuilderGeneratorTest#test_timestamps_are_not_generated_in_partial_with_--no-timestamps > = 0.02 s = . > JbuilderGeneratorTest#test_views_are_generated = 0.00 s = . > ScaffoldApiControllerGeneratorTest#test_controller_content = 0.33 s = . > ScaffoldApiControllerGeneratorTest#test_dont_use_require_and_permit_if_there_are_no_attributes > = 0.18 s = . > JbuilderTemplateTest#test_basic_template = 0.54 s = . > JbuilderTemplateTest#test_empty_array_of_partials_from_nil_collection = 0.00 > s = . > JbuilderTemplateTest#test_array_of_partials_under_key = 0.02 s = . > JbuilderTemplateTest#test_nil_partial_collection_by_name = 0.00 s = . > JbuilderTemplateTest#test_partial_collection_by_name_with_string_local = 0.00 > s = . > JbuilderTemplateTest#test_partial_by_name_with_nested_locals = 0.00 s = . > JbuilderTemplateTest#test_partial_collection_by_options = 0.00 s = . > JbuilderTemplateTest#test_partial_for_Active_Model = 0.01 s = . > JbuilderTemplateTest#test_array_root_caching = 0.00 s = . > JbuilderTemplateTest#test_conditional_object_fragment_caching = 0.00 s = . > JbuilderTemplateTest#test_failing_to_cache_root_after_JSON_structures_have_been_defined > = 0.00 s = . > JbuilderTemplateTest#test_object_fragment_caching = 0.01 s = . > JbuilderTemplateTest#test_partial_by_name_with_top-level_locals = 0.00 s = . > JbuilderTemplateTest#test_partial_collection_by_name_with_symbol_local = 0.00 > s = . > JbuilderTemplateTest#test_nil_partial_collection_by_options = 0.00 s = . > JbuilderTemplateTest#test_object_fragment_caching_with_expiry = 0.01 s = . > JbuilderTemplateTest#test_partial_by_options_containing_nested_locals = 0.00 > s = . > JbuilderTemplateTest#test_partial_by_options_containing_top-level_locals = > 0.00 s = . > JbuilderTemplateTest#test_empty_array_of_partials_under_key_from_nil_collection > = 0.00 s = . > JbuilderTemplateTest#test_cache_instrumentation = 0.00 s = . > JbuilderTemplateTest#test_object_root_caching = 0.00 s = . > JbuilderTemplateTest#test_array_of_partials = 0.01 s = . > JbuilderTemplateTest#test_camelized_keys = 0.00 s = . > JbuilderTemplateTest#test_empty_fragment_caching = 0.00 s = . > JbuilderTemplateTest#test_array_fragment_caching = 0.00 s = . > JbuilderDependencyTrackerTest#test_detects_partial_in_indirect_collection_calls > = 0.00 s = . >
Bug#996300: ruby-jaeger-client: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError:
Source: ruby-jaeger-client Version: 1.1.0-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-jaeger-client was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): > ArgumentError: > wrong number of arguments (given 1, expected 0; required keywords: > span_id, trace_id, flags) > # ./lib/jaeger/span_context.rb:25:in `initialize' > # ./spec/spec_helper.rb:16:in `new' > # ./spec/spec_helper.rb:16:in `build_span_context' > # ./spec/jaeger/span_spec.rb:50:in `block (3 levels) in (required)>' > # ./spec/jaeger/span_spec.rb:51:in `block (3 levels) in (required)>' > # ./spec/jaeger/span_spec.rb:61:in `block (4 levels) in (required)>' > > Finished in 0.37196 seconds (files took 1.6 seconds to load) > 177 examples, 42 failures > > Failed examples: > > rspec ./spec/jaeger/injectors/b3_rack_codec_spec.rb:9 # > Jaeger::Injectors::B3RackCodec sets trace information > rspec ./spec/jaeger/injectors/trace_context_rack_codec_spec.rb:14 # > Jaeger::Injectors::TraceContextRackCodec sets traceparent > rspec ./spec/jaeger/injectors/trace_context_rack_codec_spec.rb:27 # > Jaeger::Injectors::TraceContextRackCodec sets traceparent with largest trace > id and span id > rspec ./spec/jaeger/rate_limiter_spec.rb:11 # > Jaeger::RateLimiter#check_credit returns false if item cost is higher than > balance > rspec ./spec/jaeger/rate_limiter_spec.rb:16 # > Jaeger::RateLimiter#check_credit returns true until there is credit left > rspec ./spec/jaeger/rate_limiter_spec.rb:23 # > Jaeger::RateLimiter#check_credit returns true when there is enough credit > rspec ./spec/jaeger/rate_limiter_spec.rb:51 # Jaeger::RateLimiter#update when > balance was full before the update keeps the new balance full > rspec ./spec/jaeger/rate_limiter_spec.rb:61 # Jaeger::RateLimiter#update when > balance was half full before the update marks the new balance half full > rspec ./spec/jaeger/reporters/composite_reporter_spec.rb:9 # > Jaeger::Reporters::CompositeReporter#report forwards span to all reporters > rspec ./spec/jaeger/reporters/in_memory_reporter_spec.rb:7 # > Jaeger::Reporters::InMemoryReporter#report adds span to in memory spans list > rspec ./spec/jaeger/reporters/in_memory_reporter_spec.rb:19 # > Jaeger::Reporters::InMemoryReporter#clear clears spans from the reporter > rspec ./spec/jaeger/reporters/logging_reporter_spec.rb:8 # > Jaeger::Reporters::LoggingReporter#report logs out span information > rspec ./spec/jaeger/samplers/guaranteed_throughput_probabilistic_spec.rb:31 # > Jaeger::Samplers::GuaranteedThroughputProbabilistic when rate is set to 0 > when lower bound return false returns false for every trace > rspec ./spec/jaeger/samplers/guaranteed_throughput_probabilistic_spec.rb:35 # > Jaeger::Samplers::GuaranteedThroughputProbabilistic when rate is set to 0 > when lower bound return false returns tags with param 0 > rspec ./spec/jaeger/samplers/guaranteed_throughput_probabilistic_spec.rb:49 # > Jaeger::Samplers::GuaranteedThroughputProbabilistic when rate is set to 0 > when lower bound sampler returns true returns true > rspec ./spec/jaeger/samplers/guaranteed_throughput_probabilistic_spec.rb:53 # > Jaeger::Samplers::GuaranteedThroughputProbabilistic when rate is set to 0 > when lower bound sampler returns true returns tags with lower bound param > rspec ./spec/jaeger/samplers/guaranteed_throughput_probabilistic_spec.rb:70 # > Jaeger::Samplers::GuaranteedThroughputProbabilistic when rate is set to 1 > returns true for every trace > rspec ./spec/jaeger/samplers/guaranteed_throughput_probabilistic_spec.rb:74 # > Jaeger::Samplers::GuaranteedThroughputProbabilistic when rate is set to 1 > returns tags with param 1 > rspec ./spec/jaeger/samplers/guaranteed_throughput_probabilistic_spec.rb:81 # > Jaeger::Samplers::GuaranteedThroughputProbabilistic when rate is set to 1 > calls lower bound sampler > rspec ./spec/jaeger/samplers/per_operation_spec.rb:24 # > Jaeger::Samplers::PerOperation when operation strategy is defined when > operation rate is set to 0 uses lower bound sampler > rspec ./spec/jaeger/samplers/per_operation_spec.rb:37 # > Jaeger::Samplers::PerOperation when operation strategy is defined when > operation rate is set to 0 returns tags with lower bound param > rspec ./spec/jaeger/samplers/per_operation_spec.rb:57 # > Jaeger::Samplers::PerOperation when operation strategy is defined when > operation rate is set to 1 uses operation probabilistic sampler > rspec ./spec/jaeger/samplers/per_operation_spec.rb:73 # > Jaeger::Samplers::PerOperation when operation strategy is defined when > operation rate is set to 1 returns tags with lower bound param > rspec
Bug#996299: ruby-invisible-captcha: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Failure/Error: require 'bundler/setup' # Set up gems listed in the Gemfile.
Source: ruby-invisible-captcha Version: 1.1.0-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-invisible-captcha was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): > Failure/Error: require 'bundler/setup' # Set up gems listed in the Gemfile. > > Bundler::GemNotFound: > Could not find racc-1.4.16 in any of the sources > # > /usr/share/rubygems-integration/all/gems/bundler-2.2.27/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:5:in `' > No examples found. > No examples found. > > > Finished in 0.5 seconds (files took 0.23192 seconds to load) > 0 examples, 0 failures, 1 error occurred outside of examples > > Finished in 0.5 seconds (files took 0.23192 seconds to load) > 0 examples, 0 failures, 1 error occurred outside of examples > > > /usr/bin/ruby3.0 > -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 "ruby3.0" failed: The full build log is available at https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-invisible-captcha/ruby-invisible-captcha_1.1.0-2+rebuild1633383610_amd64.build.txt signature.asc Description: PGP signature
Bug#996298: ruby-influxdb: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Failure/Error: specify { expect(conf.proxy_port).to eq(8080) }
Source: ruby-influxdb
Version: 0.8.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.0
Hi,
We are about to enable building against ruby3.0 on unstable. During a test
rebuild, ruby-influxdb was found to fail to build in that situation.
To reproduce this locally, you need to install ruby-all-dev from experimental
on an unstable system or build chroot.
Relevant part (hopefully):
> Failure/Error: specify { expect(conf.proxy_port).to eq(8080) }
>
> expected: 8080
> got: nil
>
> (compared using ==)
> # ./spec/influxdb/config_spec.rb:225:in `block (3 levels) in (required)>'
>
> Finished in 0.63051 seconds (files took 1.34 seconds to load)
> 190 examples, 71 failures
>
> Failed examples:
>
> rspec ./spec/influxdb/cases/query_batch_spec.rb:98 #
> InfluxDB::Client#batch.execute with multiple queries when there is no data
> for a query should return responses for all statements
> rspec ./spec/influxdb/cases/query_batch_spec.rb:143 #
> InfluxDB::Client#batch.execute with a group by tag query should return a
> single result
> rspec ./spec/influxdb/cases/query_cluster_spec.rb:29 #
> InfluxDB::Client#create_cluster_admin with existing admin user should GET to
> create a new cluster admin
> rspec ./spec/influxdb/cases/query_cluster_spec.rb:43 #
> InfluxDB::Client#create_cluster_admin with no admin user should GET to create
> a new cluster admin
> rspec ./spec/influxdb/cases/query_cluster_spec.rb:63 #
> InfluxDB::Client#list_cluster_admins should GET a list of cluster admins
> rspec ./spec/influxdb/cases/query_cluster_spec.rb:78 #
> InfluxDB::Client#revoke_cluster_admin_privileges should GET to revoke cluster
> admin privileges from a user
> rspec ./spec/influxdb/cases/query_core_spec.rb:29 # InfluxDB::Client#query
> should handle responses with no values
> rspec ./spec/influxdb/cases/query_series_spec.rb:31 # InfluxDB::Client GET
> #list_series returns a list of all series names
> rspec ./spec/influxdb/cases/query_series_spec.rb:46 # InfluxDB::Client GET
> empty #list_series returns a empty list
> rspec ./spec/influxdb/cases/query_series_spec.rb:61 #
> InfluxDB::Client#delete_series without a where clause should GET to remove a
> database
> rspec ./spec/influxdb/cases/query_series_spec.rb:75 #
> InfluxDB::Client#delete_series with a where clause should GET to remove a
> database
> rspec ./spec/influxdb/cases/query_with_params_spec.rb:31 #
> InfluxDB::Client#query with parameters should handle responses with no values
> rspec ./spec/influxdb/cases/querying_issue_7000_spec.rb:54 #
> InfluxDB::Client#query with series with different tags (multi-line) should
> return array with 2 elements grouped by tags
> rspec ./spec/influxdb/cases/querying_issue_7000_spec.rb:110 #
> InfluxDB::Client#query with multiple series with different tags should return
> array with 4 elements grouped by name and tags
> rspec ./spec/influxdb/cases/querying_spec.rb:41 # InfluxDB::Client#query with
> single series with multiple points should return array with single hash
> containing multiple values
> rspec ./spec/influxdb/cases/querying_spec.rb:69 # InfluxDB::Client#query with
> series with different tags should return array with 2 elements grouped by tags
> rspec ./spec/influxdb/cases/querying_spec.rb:110 # InfluxDB::Client#query
> with multiple series with different tags should return array with 4 elements
> grouped by name and tags
> rspec ./spec/influxdb/cases/querying_spec.rb:135 # InfluxDB::Client#query
> with multiple series for explicit value only should return array with 2
> elements grouped by name only and no tags
> rspec ./spec/influxdb/cases/querying_spec.rb:164 # InfluxDB::Client#query
> with a block should accept a block and yield name, tags and points
> rspec ./spec/influxdb/cases/querying_spec.rb:199 # InfluxDB::Client#query
> with epoch set to seconds should return results with integer timestamp
> rspec ./spec/influxdb/cases/querying_spec.rb:222 # InfluxDB::Client#query
> with chunk_size set to 100 should set 'chunked' and 'chunk_size' parameters
> rspec ./spec/influxdb/cases/querying_spec.rb:243 # InfluxDB::Client#query
> with database should return array with single hash containing multiple values
> rspec ./spec/influxdb/cases/querying_spec.rb:275 # InfluxDB::Client multiple
> select queries with single series with multiple points should return array
> with single hash containing multiple values
> rspec ./spec/influxdb/cases/querying_spec.rb:319 # InfluxDB::Client multiple
> select queries with series with different tags should return array with 2
> elements grouped by tags
> rspec ./spec/influxdb/cases/querying_spec.rb:364 # InfluxDB::Client multiple
> select queries with a block should accept a block and yield name, tags and
> points
> rspec ./spec/influxdb/cases/retry_requests_spec.rb:43 # InfluxDB::Client
> retrying requests raises when stopped
> rspec
Bug#996297: ruby-ice-nine: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Failure/Error: expect(subject.end).to be_frozen
Source: ruby-ice-nine Version: 0.11.2-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-ice-nine was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): > Failure/Error: expect(subject.end).to be_frozen > expected `"z".frozen?` to return true, got false > Shared Example Group: "IceNine.deep_freeze" called from > ./spec/integration/ice_nine/class_methods/deep_freeze_bang_spec.rb:20 > # ./spec/shared/ice_nine_deep_freeze.rb:134:in `block (3 levels) in > ' > > Top 10 slowest examples (0.02481 seconds, 24.6% of total time): > IceNine.deep_freeze it should behave like IceNine.deep_freeze with a Range > freezes the object > 0.01391 seconds ./spec/shared/ice_nine_deep_freeze.rb:125 > IceNine::Freezer::Hash.deep_freeze with a Hash object having a default > value freezes the default value > 0.00449 seconds > ./spec/unit/ice_nine/freezer/hash/class_methods/deep_freeze_spec.rb:30 > IceNine.deep_freeze it should behave like IceNine.deep_freeze with a > Integer does not freeze the object > 0.00196 seconds ./spec/shared/ice_nine_deep_freeze.rb:257 > IceNine::Freezer::Range.deep_freeze with a Range with a circular reference > in the first element behaves like IceNine::Freezer::Range.deep_freeze freeze > the first element > 0.00172 seconds ./spec/shared/range_deep_freeze.rb:6 > IceNine.deep_freeze it should behave like IceNine.deep_freeze with a > Integer returns the object > 0.00073 seconds ./spec/shared/ice_nine_deep_freeze.rb:253 > IceNine.deep_freeze with a shallowly frozen value does a deep freeze > 0.0007 seconds > ./spec/integration/ice_nine/class_methods/deep_freeze_spec.rb:15 > IceNine::Freezer::Struct.deep_freeze with a Struct behaves like > IceNine::Freezer::Array.deep_freeze behaves like > IceNine::Freezer::Object.deep_freeze freezes instance variables > 0.00035 seconds ./spec/shared/object_deep_freeze.rb:16 > IceNine.deep_freeze! it should behave like IceNine.deep_freeze with a Hash > with a circular reference freezes the object > 0.00033 seconds ./spec/shared/ice_nine_deep_freeze.rb:104 > IceNine.deep_freeze! it should behave like IceNine.deep_freeze with a > Struct with a circular reference freezes the object > 0.00032 seconds ./spec/shared/ice_nine_deep_freeze.rb:201 > IceNine.deep_freeze! it should behave like IceNine.deep_freeze with a Range > freeze the last object in the Range > 0.0003 seconds ./spec/shared/ice_nine_deep_freeze.rb:133 > > Top 10 slowest example groups: > IceNine::Freezer::Array.deep_freeze > 0.00062 seconds average (0.00497 seconds / 8 examples) > ./spec/unit/ice_nine/freezer/array/class_methods/deep_freeze_spec.rb:6 > IceNine.deep_freeze > 0.00058 seconds average (0.03281 seconds / 57 examples) > ./spec/integration/ice_nine/class_methods/deep_freeze_spec.rb:7 > IceNine::Freezer::Range.deep_freeze > 0.00046 seconds average (0.0069 seconds / 15 examples) > ./spec/unit/ice_nine/freezer/range/class_methods/deep_freeze_spec.rb:6 > IceNine::Freezer::Hash.deep_freeze > 0.00045 seconds average (0.01272 seconds / 28 examples) > ./spec/unit/ice_nine/freezer/hash/class_methods/deep_freeze_spec.rb:6 > IceNine::Freezer::Struct.deep_freeze > 0.0004 seconds average (0.0016 seconds / 4 examples) > ./spec/unit/ice_nine/freezer/struct/class_methods/deep_freeze_spec.rb:6 > IceNine::RecursionGuard::Frozen#guard > 0.0004 seconds average (0.0008 seconds / 2 examples) > ./spec/unit/ice_nine/recursion_guard/frozen/guard_spec.rb:6 > IceNine::Freezer.[] > 0.00036 seconds average (0.00289 seconds / 8 examples) > ./spec/unit/ice_nine/freezer/class_methods/element_reader_spec.rb:9 > IceNine::Freezer::Object.deep_freeze > 0.00036 seconds average (0.00325 seconds / 9 examples) > ./spec/unit/ice_nine/freezer/object/class_methods/deep_freeze_spec.rb:6 > IceNine::Freezer::NilClass.deep_freeze > 0.00035 seconds average (0.00104 seconds / 3 examples) > ./spec/unit/ice_nine/freezer/nil_class/class_methods/deep_freeze_spec.rb:8 > IceNine::RecursionGuard::ObjectSet#guard > 0.00032 seconds average (0.00065 seconds / 2 examples) > ./spec/unit/ice_nine/recursion_guard/object_set/guard_spec.rb:6 > > Finished in 0.10075 seconds (files took 0.21702 seconds to load) > 244 examples, 13 failures > > Failed examples: > > rspec > './spec/unit/ice_nine/freezer/range/class_methods/deep_freeze_spec.rb[1:1:2:1:1:3]' > # IceNine::Freezer::Range.deep_freeze with a Range with a circular reference > in the first element behaves like IceNine::Freezer::Range.deep_freeze behaves > like IceNine::Freezer::Object.deep_freeze freezes instance variables > rspec >
Processed: bug 994257 is forwarded to https://github.com/django-ldapdb/django-ldapdb/pull/202
Processing commands for cont...@bugs.debian.org: > forwarded 994257 https://github.com/django-ldapdb/django-ldapdb/pull/202 Bug #994257 [src:python-django, src:django-ldapdb] python-django breaks django-ldapdb autopkgtest: 'Field' object has no attribute 'attname' Set Bug forwarded-to-address to 'https://github.com/django-ldapdb/django-ldapdb/pull/202'. > thanks Stopping processing here. Please contact me if you need assistance. -- 994257: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994257 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996296: ruby-ice-cube: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError:
Source: ruby-ice-cube Version: 0.16.3-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-ice-cube was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): >ArgumentError: > wrong number of arguments (given 2, expected 0..1) ># > /usr/share/rubygems-integration/all/gems/i18n-1.8.10/lib/i18n.rb:196:in > `translate' ># ./lib/ice_cube/i18n.rb:9:in `t' ># ./lib/ice_cube/validations/weekly_interval.rb:42:in `build_s' ># ./lib/ice_cube/validated_rule.rb:74:in `block (2 levels) in to_s' ># ./lib/ice_cube/validated_rule.rb:73:in `each' ># ./lib/ice_cube/validated_rule.rb:73:in `block in to_s' ># ./lib/ice_cube/validated_rule.rb:72:in `each_value' ># ./lib/ice_cube/validated_rule.rb:72:in `to_s' ># ./lib/ice_cube/schedule.rb:317:in `block in to_s' ># ./lib/ice_cube/schedule.rb:317:in `map' ># ./lib/ice_cube/schedule.rb:317:in `to_s' ># ./spec/examples/to_s_ja_spec.rb:205:in `block (2 levels) in (required)>' ># ./spec/spec_helper.rb:68:in `block (3 levels) in ' ># ./spec/spec_helper.rb:67:in `block (2 levels) in ' ># ./spec/spec_helper.rb:56:in `block (2 levels) in ' > > Finished in 1.54 seconds (files took 0.57364 seconds to load) > 1074 examples, 177 failures, 2 pending > > Failed examples: > > rspec ./spec/examples/from_ical_spec.rb:68 # IceCube::Rule from_ical should > be able to parse a rule with an until date > rspec ./spec/examples/from_ical_spec.rb:138 # IceCube::Schedule from_ical > daily frequency matches simple daily > rspec ./spec/examples/from_ical_spec.rb:148 # IceCube::Schedule from_ical > daily frequency handles counts > rspec ./spec/examples/from_ical_spec.rb:158 # IceCube::Schedule from_ical > daily frequency handles intervals > rspec ./spec/examples/from_ical_spec.rb:168 # IceCube::Schedule from_ical > daily frequency handles intervals and counts > rspec ./spec/examples/from_ical_spec.rb:178 # IceCube::Schedule from_ical > daily frequency handles until dates > rspec ./spec/examples/from_ical_spec.rb:191 # IceCube::Schedule from_ical > weekly frequency matches simple weekly > rspec ./spec/examples/from_ical_spec.rb:201 # IceCube::Schedule from_ical > weekly frequency handles weekdays > rspec ./spec/examples/from_ical_spec.rb:211 # IceCube::Schedule from_ical > weekly frequency handles intervals > rspec ./spec/examples/from_ical_spec.rb:221 # IceCube::Schedule from_ical > weekly frequency handles intervals and counts > rspec ./spec/examples/from_ical_spec.rb:231 # IceCube::Schedule from_ical > weekly frequency handles intervals and counts on given weekdays > rspec ./spec/examples/from_ical_spec.rb:243 # IceCube::Schedule from_ical > monthly frequency matches simple monthly > rspec ./spec/examples/from_ical_spec.rb:253 # IceCube::Schedule from_ical > monthly frequency handles intervals > rspec ./spec/examples/from_ical_spec.rb:263 # IceCube::Schedule from_ical > monthly frequency handles intervals and counts > rspec ./spec/examples/from_ical_spec.rb:273 # IceCube::Schedule from_ical > monthly frequency handles intervals and counts on specific days > rspec ./spec/examples/from_ical_spec.rb:285 # IceCube::Schedule from_ical > yearly frequency matches simple yearly > rspec ./spec/examples/from_ical_spec.rb:295 # IceCube::Schedule from_ical > yearly frequency handles intervals > rspec ./spec/examples/from_ical_spec.rb:305 # IceCube::Schedule from_ical > yearly frequency handles a specific day > rspec ./spec/examples/from_ical_spec.rb:315 # IceCube::Schedule from_ical > yearly frequency handles specific days > rspec ./spec/examples/from_ical_spec.rb:325 # IceCube::Schedule from_ical > yearly frequency handles counts > rspec ./spec/examples/from_ical_spec.rb:335 # IceCube::Schedule from_ical > yearly frequency handles specific months > rspec ./spec/examples/from_ical_spec.rb:345 # IceCube::Schedule from_ical > yearly frequency handles specific months and counts > rspec ./spec/examples/from_ical_spec.rb:357 # IceCube::Schedule from_ical > exceptions handles single EXDATE lines, single RDATE lines > rspec ./spec/examples/to_ical_spec.rb:97 # IceCube to_ical should be able to > serialize a base schedule to ical in local time > rspec ./spec/examples/to_ical_spec.rb:103 # IceCube to_ical should be able to > serialize a base schedule to ical in UTC time > rspec ./spec/examples/to_ical_spec.rb:108 # IceCube to_ical should be able to > serialize a schedule with one rrule > rspec ./spec/examples/to_ical_spec.rb:118 # IceCube to_ical should be able to > serialize a schedule with multiple rrules > rspec ./spec/examples/to_ical_spec.rb:129 # IceCube to_ical
Bug#996295: ruby-i18n-inflector-rails: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError:
Source: ruby-i18n-inflector-rails Version: 1.0.7-4.1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-i18n-inflector-rails was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): > ArgumentError: > wrong number of arguments (given 2, expected 1) > # > /usr/share/rubygems-integration/all/gems/actionpack-6.0.3.7/lib/abstract_controller/translation.rb:13:in > `translate' > # ./lib/i18n-inflector-rails/inflector.rb:322:in `translate' > # ./spec/inflector_spec.rb:215:in `t_male' > # ./spec/inflector_spec.rb:327:in `block (4 levels) in ' > > Finished in 2.06 seconds (files took 3.09 seconds to load) > 33 examples, 11 failures > > Failed examples: > > rspec ./spec/inflector_spec.rb:272 # ApplicationController controller > instance methods #translate should translate using inflection patterns and > pick up the right value > rspec ./spec/inflector_spec.rb:278 # ApplicationController controller > instance methods #translate should make use of a block passed to inflection > method > rspec ./spec/inflector_spec.rb:282 # ApplicationController controller > instance methods #translate should make use of inherited inflection method > assignments > rspec ./spec/inflector_spec.rb:286 # ApplicationController controller > instance methods #translate should make use of overriden inflection method > assignments > rspec ./spec/inflector_spec.rb:290 # ApplicationController controller > instance methods #translate should prioritize strict kinds when both > inflection options are passed > rspec ./spec/inflector_spec.rb:295 # ApplicationController controller > instance methods #translate should use regular kind option when strict kind > option is missing > rspec ./spec/inflector_spec.rb:300 # ApplicationController controller > instance methods #translate should make use of disabled inflection method > assignments > rspec ./spec/inflector_spec.rb:308 # ApplicationController controller > instance methods #translate should not raise when method does not exists and > verify_methods is enabled > rspec ./spec/inflector_spec.rb:314 # ApplicationController controller > instance methods #translate should translate with the :inflector_lazy_methods > switch turned off > rspec ./spec/inflector_spec.rb:318 # ApplicationController controller > instance methods #translate should omit pattern interpolation when locale is > not inflected > rspec ./spec/inflector_spec.rb:326 # ApplicationController controller > instance methods #t should call translate > > /usr/bin/ruby3.0 > -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 "ruby3.0" failed: The full build log is available at https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-i18n-inflector-rails/ruby-i18n-inflector-rails_1.0.7-4.1+rebuild1633383189_amd64.build.txt signature.asc Description: PGP signature
Bug#996294: ruby-httpclient: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed.
Source: ruby-httpclient Version: 2.8.3-3 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-httpclient was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): > /usr/bin/ruby3.0 /usr/bin/gem2deb-test-runner > > ┌──┐ > │ Checking Rubygems dependency resolution on ruby3.0 > │ > └──┘ > > GEM_PATH=/<>/debian/ruby-httpclient/usr/share/rubygems-integration/all:/var/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0 > ruby3.0 -e gem\ \"httpclient\" > > ┌──┐ > │ Run tests for ruby3.0 from debian/ruby-tests.rake > │ > └──┘ > > RUBYLIB=/<>/debian/ruby-httpclient/usr/lib/ruby/vendor_ruby:. > GEM_PATH=/<>/debian/ruby-httpclient/usr/share/rubygems-integration/all:/var/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0 > ruby3.0 -S rake -f debian/ruby-tests.rake > /usr/bin/ruby3.0 -w -I"test" > /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/rake_test_loader.rb > "test/test_auth.rb" "test/test_cookie.rb" "test/test_hexdump.rb" > "test/test_http-access2.rb" "test/test_httpclient.rb" > "test/test_include_client.rb" "test/test_jsonclient.rb" > "test/test_webagent-cookie.rb" -v > /<>/debian/ruby-httpclient/usr/lib/ruby/vendor_ruby/httpclient/ssl_config.rb:370: > warning: assigned but unused variable - pathlen > /<>/debian/ruby-httpclient/usr/lib/ruby/vendor_ruby/httpclient/ssl_config.rb:51: > warning: method redefined; discarding old initialize > /<>/debian/ruby-httpclient/usr/lib/ruby/vendor_ruby/httpclient/ssl_config.rb:58: > warning: method redefined; discarding old add_cert > /<>/debian/ruby-httpclient/usr/lib/ruby/vendor_ruby/httpclient/ssl_config.rb:58: > warning: method redefined; discarding old add_file > /<>/debian/ruby-httpclient/usr/lib/ruby/vendor_ruby/httpclient/ssl_config.rb:58: > warning: method redefined; discarding old add_path > > File does not exist: webrick > > rake aborted! > Command failed with status (1): [ruby -w -I"test" > /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/rake_test_loader.rb > "test/test_auth.rb" "test/test_cookie.rb" "test/test_hexdump.rb" > "test/test_http-access2.rb" "test/test_httpclient.rb" > "test/test_include_client.rb" "test/test_jsonclient.rb" > "test/test_webagent-cookie.rb" -v] > > Tasks: TOP => default > (See full trace by running task with --trace) > ERROR: Test "ruby3.0" failed. Note that webrick has been removed from the standard library. It's already been packaged and is currently in NEW, but this package now needs an explicit dependency on it. The full build log is available at https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-httpclient/ruby-httpclient_2.8.3-3+rebuild1633383080_amd64.build.txt signature.asc Description: PGP signature
Bug#996293: ruby-httparty: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError:
Source: ruby-httparty Version: 0.18.1-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-httparty was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): > ArgumentError: >wrong number of arguments (given 2, expected 1) > # ./lib/httparty/request/body.rb:6:in `initialize' > # ./spec/httparty/request/body_spec.rb:10:in `new' > # ./spec/httparty/request/body_spec.rb:10:in `block (3 levels) in (required)>' > # ./spec/httparty/request/body_spec.rb:15:in `block (4 levels) in (required)>' > > Top 10 slowest examples (1.21 seconds, 28.9% of total time): > HTTParty#get should be able parse response type xml automatically > 0.21851 seconds ./spec/httparty_spec.rb:906 > HTTParty::Request SSL certificate verification should work when no trusted > CA list is specified, when the verify option is set to false > 0.16157 seconds ./spec/httparty/ssl_spec.rb:19 > HTTParty::Request SSL certificate verification should provide the > certificate used by the server via peer_cert > 0.15752 seconds ./spec/httparty/ssl_spec.rb:74 > HTTParty::Request SSL certificate verification should work when no trusted > CA list is specified, even with a bogus hostname, when the verify option is > set to true > 0.15627 seconds ./spec/httparty/ssl_spec.rb:29 > HTTParty::Request SSL certificate verification should work when using > ssl_ca_file with a certificate authority > 0.14463 seconds ./spec/httparty/ssl_spec.rb:37 > HTTParty::Request SSL certificate verification should work when using > ssl_ca_file with a self-signed CA > 0.14422 seconds ./spec/httparty/ssl_spec.rb:33 > HTTParty::Request SSL certificate verification should fail when using > ssl_ca_file and the server uses an unrecognized certificate authority > 0.06358 seconds ./spec/httparty/ssl_spec.rb:50 > HTTParty::Request SSL certificate verification should fail when using > ssl_ca_path and the server uses an unrecognized certificate authority > 0.06255 seconds ./spec/httparty/ssl_spec.rb:56 > HTTParty::Request SSL certificate verification should fail when using > ssl_ca_file and the server uses a bogus hostname > 0.05454 seconds ./spec/httparty/ssl_spec.rb:62 > HTTParty::Request SSL certificate verification should fail when no trusted > CA list is specified, with a bogus hostname, by default > 0.04319 seconds ./spec/httparty/ssl_spec.rb:23 > > Top 10 slowest example groups: > HTTParty::Request > 0.08922 seconds average (1.07 seconds / 12 examples) > ./spec/httparty/ssl_spec.rb:3 > HTTParty::Logger::LogstashFormatter > 0.0175 seconds average (0.0175 seconds / 1 example) > ./spec/httparty/logger/logstash_formatter_spec.rb:3 > HTTParty::Request > 0.00609 seconds average (1.57 seconds / 258 examples) > ./spec/httparty/request_spec.rb:3 > HTTParty::ConnectionAdapter > 0.00583 seconds average (0.40809 seconds / 70 examples) > ./spec/httparty/connection_adapter_spec.rb:3 > HTTParty > 0.00515 seconds average (0.60239 seconds / 117 examples) > ./spec/httparty_spec.rb:3 > HTTParty::Logger::CurlFormatter > 0.00417 seconds average (0.05416 seconds / 13 examples) > ./spec/httparty/logger/curl_formatter_spec.rb:3 > HTTParty::HeadersProcessor > 0.00373 seconds average (0.01866 seconds / 5 examples) > ./spec/httparty/headers_processor_spec.rb:3 > Net::HTTPHeader::DigestAuthenticator > 0.0036 seconds average (0.11892 seconds / 33 examples) > ./spec/httparty/net_digest_auth_spec.rb:3 > HTTParty::Request::Body > 0.00245 seconds average (0.02204 seconds / 9 examples) > ./spec/httparty/request/body_spec.rb:6 > HTTParty::Response > 0.00242 seconds average (0.22293 seconds / 92 examples) > ./spec/httparty/response_spec.rb:3 > > Finished in 4.18 seconds (files took 2.99 seconds to load) > 673 examples, 5 failures, 1 pending > > Failed examples: > > rspec ./spec/httparty/request/body_spec.rb:22 # HTTParty::Request::Body#call > when params is hash > rspec ./spec/httparty/request/body_spec.rb:65 # HTTParty::Request::Body#call > when params is hash when params has file > rspec ./spec/httparty/request/body_spec.rb:106 # HTTParty::Request::Body#call > when params is hash when params has file file object responds to > original_filename > rspec ./spec/httparty/request/body_spec.rb:94 # HTTParty::Request::Body#call > when params is hash when params has file when passing multipart as an option > rspec ./spec/httparty/request/body_spec.rb:15 # HTTParty::Request::Body#call > when params is string > > Randomized with seed 45873 > > Coverage report generated for RSpec to /<>/coverage. 995 / 1033 > LOC (96.32%) covered. > Stopped
Bug#996292: ruby-http: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: cannot load such file -- webrick
Source: ruby-http
Version: 4.4.1-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.0
Hi,
We are about to enable building against ruby3.0 on unstable. During a test
rebuild, ruby-http was found to fail to build in that situation.
To reproduce this locally, you need to install ruby-all-dev from experimental
on an unstable system or build chroot.
Relevant part (hopefully):
> cannot load such file -- webrick
> #
> :85:in
> `require'
> #
> :85:in
> `require'
> # ./spec/support/dummy_server.rb:3:in `'
> #
> :85:in
> `require'
> #
> :85:in
> `require'
> # ./spec/lib/http_spec.rb:6:in `'
> #
> /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/configuration.rb:2103:in
> `load'
> #
> /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/configuration.rb:2103:in
> `load_file_handling_errors'
> #
> /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/configuration.rb:1606:in
> `block in load_spec_files'
> #
> /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/configuration.rb:1604:in
> `each'
> #
> /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/configuration.rb:1604:in
> `load_spec_files'
> #
> /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/runner.rb:102:in
> `setup'
> #
> /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/runner.rb:86:in
> `run'
> #
> /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/runner.rb:71:in
> `run'
> #
> /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/runner.rb:45:in
> `invoke'
> # /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/exe/rspec:4:in
> `'
> Run options: include {:focus=>true}
>
> All examples were filtered out; ignoring {:focus=>true}
>
> Top 0 slowest examples (0 seconds, 0.0% of total time):
>
> Finished in 0.8 seconds (files took 0.7255 seconds to load)
> 0 examples, 0 failures, 2 errors occurred outside of examples
>
> Coverage report generated for RSpec to /<>/coverage. 652 / 1361
> LOC (47.91%) covered.
> [33m[Coveralls] Outside the CI environment, not sending data.[0m
> Stopped processing SimpleCov as a previous error not related to SimpleCov has
> been detected
> /usr/bin/ruby3.0
> -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 "ruby3.0" failed:
Note that webrick has been removed from the standard library. It's
already been packaged and is currently in NEW, but this package now
needs an explicit dependency on it.
The full build log is available at
https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-http/ruby-http_4.4.1-4+rebuild1633382951_amd64.build.txt
signature.asc
Description: PGP signature
Bug#996291: ruby-hdfeos5: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: :85:in `require': /<>/debian/ruby-hdfeo
Source: ruby-hdfeos5 Version: 1.2-10 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-hdfeos5 was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): > :85:in > `require': > /<>/debian/ruby-hdfeos5/usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/3.0.0/numru/hdfeos5raw.so: > undefined symbol: rb_secure - > /<>/debian/ruby-hdfeos5/usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/3.0.0/numru/hdfeos5raw.so > (LoadError) > from > :85:in > `require' > from > /<>/debian/ruby-hdfeos5/usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/3.0.0/numru/hdfeos5.rb:3:in > `' > from > :85:in > `require' > from > :85:in > `require' > from /<>/test/test_gd.rb:2:in `' > from > :85:in > `require' > from > :85:in > `require' > from -e:1:in `block in ' > from -e:1:in `each' > from -e:1:in `' > ERROR: Test "ruby3.0" failed: The full build log is available at https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-hdfeos5/ruby-hdfeos5_1.2-10+rebuild1633382527_amd64.build.txt signature.asc Description: PGP signature
Bug#959927: marked as done (birdtray: Uninstallable on Debian Buster)
Your message dated Tue, 12 Oct 2021 23:38:31 +0200 with message-id and subject line gone from Buster has caused the Debian Bug report #959927, regarding birdtray: Uninstallable on Debian Buster to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 959927: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959927 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: birdtray Version: 1.5-1 Severity: important Dear Maintainer, * What led up to the situation? Attempting to install birdtray. The current version of thunderbird in buster has Breaks: birdtray (<< 1.7.0+ds-1~) which is preventing birdtray from installing. Can birdtray please be updated to allow it to be installed on Debian buster. -- System Information: Debian Release: 10.0 Architecture: amd64 (x86_64) Kernel: Linux 5.4.0-0.bpo.4-amd64 (SMP w/8 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) LSM: AppArmor: enabled Versions of packages birdtray depends on: ii libc6 2.28-10 ii libgcc1 1:8.3.0-6 ii libgl11.1.0-1 ii libqt5core5a 5.11.3+dfsg1-1+deb10u3 ii libqt5gui55.11.3+dfsg1-1+deb10u3 ii libqt5widgets55.11.3+dfsg1-1+deb10u3 ii libqt5x11extras5 5.11.3-2 ii libsqlite3-0 3.27.2-3 ii libstdc++68.3.0-6 ii libx11-6 2:1.6.7-1 ii thunderbird 1:68.7.0-1~deb10u1 birdtray recommends no packages. birdtray suggests no packages. --- End Message --- --- Begin Message --- Not the nicest thing to do, but I've had birdtray removed from Buster instead. Thus, this is an ex-bug. Meow! -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Polexit is brewing? Let's skip that smelly Polsha and reactivate ⢿⡄⠘⠷⠚⠋⠀ the Free City of Danzig and/or reapply to the Hansa. ⠈⠳⣄--- End Message ---
Bug#984009: marked as done (cheesecutter: ftbfs with GCC-11)
Your message dated Tue, 12 Oct 2021 21:33:42 + with message-id and subject line Bug#984009: fixed in cheesecutter 2.9+git20211011-1 has caused the Debian Bug report #984009, regarding cheesecutter: ftbfs with GCC-11 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.) -- 984009: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984009 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:cheesecutter Version: 2.9+git20191210-2 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye release] 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-11/g++-11, but succeeds to build with gcc-10/g++-10. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://people.debian.org/~doko/logs/20210228/filtered/gcc11/cheesecutter_2.9+git20191210-2_unstable_gcc11.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 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-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] LOGNAME=user42 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games SCHROOT_ALIAS_NAME=unstable SCHROOT_CHROOT_NAME=sid-amd64-sbuild SCHROOT_COMMAND=env SCHROOT_GID=1001 SCHROOT_GROUP=user42 SCHROOT_SESSION_ID=sid-amd64-sbuild-4ce1bd09-ae7e-4b24-ab9c-7341d373cc36 SCHROOT_UID=1001 SCHROOT_USER=user42 SHELL=/bin/sh USER=user42 dpkg-buildpackage - Command: dpkg-buildpackage -us -uc -b -rfakeroot dpkg-buildpackage: info: source package cheesecutter dpkg-buildpackage: info: source version 2.9+git20191210-2 dpkg-buildpackage: info: source distribution unstable dpkg-buildpackage: info: source changed by Gürkan Myczko dpkg-source --before-build . dpkg-buildpackage: info: host architecture amd64 fakeroot debian/rules clean dh clean dh_auto_clean make -j4 clean make[1]: Entering directory '/<>' Makefile:29: warning: ignoring prerequisites on suffix rule definition Makefile:26: warning: ignoring prerequisites on suffix rule definition rm -f *.o *~ resid/*.o resid-fp/*.o ccutter ct2util \ src/c64/player.bin src/derelict/util/compat.o src/derelict/util/sharedlib.o src/derelict/util/exception.o src/derelict/util/loader.o src/derelict/util/wintypes.o src/derelict/util/xtypes.o src/derelict/sdl/sdl.o src/derelict/sdl/net.o src/derelict/sdl/ttf.o src/derelict/sdl/mixer.o src/derelict/sdl/image.o src/derelict/sdl/sdlfuncs.o src/derelict/sdl/sdltypes.o src/derelict/sdl/macinit/CoreFoundation.o src/derelict/sdl/macinit/DerelictSDLMacLoader.o src/derelict/sdl/macinit/ID.o src/derelict/sdl/macinit/MacTypes.o src/derelict/sdl/macinit/NSApplication.o src/derelict/sdl/macinit/NSArray.o src/derelict/sdl/macinit/NSAutoreleasePool.o src/derelict/sdl/macinit/NSDictionary.o src/derelict/sdl/macinit/NSEnumerator.o src/derelict/sdl/macinit/NSEvent.o src/derelict/sdl/macinit/NSGeometry.o src/derelict/sdl/macinit/NSMenu.o src/derelict/sdl/macinit/NSMenuItem.o src/derelict/sdl/macinit/NSNotification.o src/derelict/sdl/macinit/NSObject.o src/derelict/sdl/macinit/NSProcessInfo.o src/derelict /sdl/macinit/NSString.o src/derelict/sdl/macinit/NSZone.o src/derelict/sdl/macinit/runtime.o src/derelict/sdl/macinit/SDLMain.o src/derelict/sdl/macinit/selectors.o src/derelict/sdl/macinit/string.o src/audio/audio.o src/audio/player.o src/audio/timer.o src/audio/callback.o src/ct/purge.o src/ct/base.o src/ct/dump.o src/com/fb.o src/com/cpu.o src/com/kbd.o src/com/session.o src/com/util.o src/main.o src/ui/tables.o src/ui/dialogs.o src/ui/ui.o src/ui/input.o
Bug#994561: marked as done (cheesecutter ftbfs with gdc-11)
Your message dated Tue, 12 Oct 2021 21:33:42 + with message-id and subject line Bug#994561: fixed in cheesecutter 2.9+git20211011-1 has caused the Debian Bug report #994561, regarding cheesecutter ftbfs with gdc-11 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.) -- 994561: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994561 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: src:cheesecutter Version: 2.9+git20191210-2 Severity: important Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [...] debian/rules override_dh_auto_build make[1]: Entering directory '/<>/cheesecutter-2.9+git20191210' /usr/bin/make make[2]: Entering directory '/<>/cheesecutter-2.9+git20191210' Makefile:29: warning: ignoring prerequisites on suffix rule definition Makefile:26: warning: ignoring prerequisites on suffix rule definition acme -f cbm --outfile src/c64/player.bin src/c64/player_v4.acme Warning - File src/c64/player_v4.acme, line 1687 (Zone ): Found old "!for" syntax. Warning - File src/c64/player_v4.acme, line 1693 (Zone ): Found old "!for" syntax. Warning - File src/c64/player_v4.acme, line 1699 (Zone ): Found old "!for" syntax. Warning - File src/c64/player_v4.acme, line 1707 (Zone ): Found old "!for" syntax. Warning - File src/c64/player_v4.acme, line 1721 (Zone ): Found old "!for" syntax. gdc -O2 -g -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -I./src -J./src/c64 -J./src/font -c -o src/ct2util.o src/ct2util.d gdc -O2 -g -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -I./src -J./src/c64 -J./src/font -c -o src/ct/base.o src/ct/base.d src/ct/base.d:385:41: warning: function ct.base.Track.dup is deprecated [-Wdeprecated] 385 | list[i+1] = list[i].dup; | ^ src/ct/base.d:397:39: warning: function ct.base.Track.dup is deprecated [-Wdeprecated] 397 | list[i] = list[i+1].dup; | ^ gdc -O2 -g -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -I./src -J./src/c64 -J./src/font -c -o src/com/cpu.o src/com/cpu.d gdc -O2 -g -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -I./src -J./src/c64 -J./src/font -c -o src/com/util.o src/com/util.d src/com/util.d:142:17: error: undefined identifier ‘munch’ 142 | munch(strvalue, "\r\n\t"); | ^ make[2]: *** [Makefile:75: src/com/util.o] Error 1 make[2]: Leaving directory '/<>/cheesecutter-2.9+git20191210' make[1]: *** [debian/rules:16: override_dh_auto_build] Error 2 make[1]: Leaving directory '/<>/cheesecutter-2.9+git20191210' make: *** [debian/rules:13: build] Error 2 --- End Message --- --- Begin Message --- Source: cheesecutter Source-Version: 2.9+git20211011-1 Done: Gürkan Myczko We believe that the bug you reported is fixed in the latest version of cheesecutter, 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 994...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gürkan Myczko (supplier of updated cheesecutter package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 11 Oct 2021 08:56:15 +0200 Source: cheesecutter Architecture: source Version: 2.9+git20211011-1 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Gürkan Myczko Closes: 984009 994561 Changes: cheesecutter (2.9+git20211011-1) unstable; urgency=medium . * New upstream version. (Closes: #984009, #994561) * Bump standards version to 4.6.0. * d/upstream/metadata: added. * d/control: added Rules-Requires-Root. * d/copyright: - update copyright years. - added Upstream-Contact. - pdate file patterns. Checksums-Sha1: a4f9db151190500f30f30709e38c21a6354110e2 2058 cheesecutter_2.9+git20211011-1.dsc 2a513da39fe441f91991188a74c4f716ac00280e 407879 cheesecutter_2.9+git20211011.orig.tar.gz 5e29d141314bafe2bc040d6c97e3c8218c4a3cd0 5160 cheesecutter_2.9+git20211011-1.debian.tar.xz c762013fb8b767390e2c8db2ef5b945eaa132bfa 9437
Processed: tagging 995779, tagging 995780, tagging 995781, tagging 995783
Processing commands for cont...@bugs.debian.org: > tags 995779 + sid bookworm Bug #995779 [mailman3] autopkgtest fails with sqlalchemy 1.4.23+ds1 Added tag(s) bookworm and sid. > tags 995780 + sid bookworm Bug #995780 [src:python-agate-sql] python-agate-sql autopkgtest fails with SQLAlchemy 1.4.23+ds1-2 Added tag(s) sid and bookworm. > tags 995781 + sid bookworm Bug #995781 [src:python-sqlsoup] python-sqlsoup autopkgtest fails with SQLAlchemy 1.4.23+ds1-2 Added tag(s) sid and bookworm. > tags 995783 + sid bookworm Bug #995783 [src:python-marshmallow-sqlalchemy] python-marshmallow-sqlalchemy autopkgtest fails with SQLAlchemy 1.4.23+ds1-2 Added tag(s) sid and bookworm. > thanks Stopping processing here. Please contact me if you need assistance. -- 995779: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995779 995780: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995780 995781: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995781 995783: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995783 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 995437, tagging 995480, tagging 995597, tagging 995600, tagging 995603, tagging 995623 ...
Processing commands for cont...@bugs.debian.org:
> tags 995437 + sid bookworm
Bug #995437 {Done: Laszlo Boszormenyi (GCS) } [src:vips] vips:
FTBFS
Added tag(s) sid and bookworm.
> tags 995480 + sid bookworm
Bug #995480 [src:ytree] FTBFS: error: format not a string literal and no format
arguments
Added tag(s) sid and bookworm.
> tags 995597 + sid bookworm
Bug #995597 {Done: Stephen Kitt } [src:bsdgames] FTBFS:
error: format not a string literal and no format arguments
Added tag(s) bookworm and sid.
> tags 995600 + sid bookworm
Bug #995600 [src:omega-rpg] FTBFS: error: format not a string literal and no
format arguments
Added tag(s) bookworm and sid.
> tags 995603 + sid bookworm
Bug #995603 [src:why3] FTBFS: pdflatex fails with no message
Added tag(s) sid and bookworm.
> tags 995623 + sid bookworm
Bug #995623 [src:refind] refind FTBFS: error: conflicting types for
‘EFI_DEVICE_PATH_UTILITIES_PROTOCOL’
Added tag(s) bookworm and sid.
> tags 995625 + sid bookworm
Bug #995625 [src:httping] httping FTBFS: error: format not a string literal and
no format arguments [-Werror=format-security]
Added tag(s) sid and bookworm.
> tags 995815 + sid bookworm
Bug #995815 {Done: Antonio Terceiro }
[src:ruby-eventmachine] ruby-eventmachine FTBFS on IPV6-only buildds
Added tag(s) bookworm and sid.
> tags 995846 + sid bookworm
Bug #995846 [pgloader] FTBFS: Fatal TYPE-ERROR and tests incompatible with PG14
Added tag(s) bookworm and sid.
> tags 995979 + sid bookworm
Bug #995979 [src:pamix] pamix FTBFS: error: format not a string literal and no
format arguments [-Werror=format-security]
Added tag(s) bookworm and sid.
> tags 995983 + sid bookworm
Bug #995983 {Done: Roland Rosenfeld } [lbdb] FTBFS: required
file 'config.rpath' not found
Added tag(s) sid and bookworm.
> tags 995999 + sid bookworm
Bug #995999 [prometheus] FTBFS: FAIL:
TestChunkDiskMapper_WriteChunk_Chunk_IterateChunks
Added tag(s) bookworm and sid.
> tags 996170 + sid bookworm
Bug #996170 [src:linux] linux: FTBFS if bpftool detects clang-bpf-co-re
Added tag(s) bookworm and sid.
> tags 996241 + sid bookworm
Bug #996241 [glm] glm: FTBFS with GCC-11 (test-core_func_integer)
Added tag(s) bookworm and sid.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
995437: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995437
995480: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995480
995597: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995597
995600: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995600
995603: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995603
995623: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995623
995625: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995625
995815: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995815
995846: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995846
995979: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995979
995983: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995983
995999: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995999
996170: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996170
996241: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996241
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#984257: marked as done (nted: ftbfs with GCC-11)
Your message dated Tue, 12 Oct 2021 21:05:47 +
with message-id
and subject line Bug#984257: fixed in nted 1.10.18-13
has caused the Debian Bug report #984257,
regarding nted: ftbfs with GCC-11
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.)
--
984257: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984257
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:nted
Version: 1.10.18-12
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-11
[This bug is not targeted to the upcoming bullseye release]
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-11/g++-11, but succeeds to build with gcc-10/g++-10. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.
The full build log can be found at:
http://people.debian.org/~doko/logs/20210228/filtered/gcc11/nted_1.10.18-12_unstable_gcc11.log
The last lines of the build log are at the end of this report.
To build with GCC 11, either set CC=gcc-11 CXX=g++-11 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-11/porting_to.html
GCC 11 defaults to the GNU++17 standard. If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.
[...]
from /usr/include/glib-2.0/gio/gio.h:26,
from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:30,
from /usr/include/gtk-2.0/gdk/gdk.h:32,
from /usr/include/gtk-2.0/gtk/gtk.h:32,
from resource.h:27,
from staff.h:26,
from staff.cpp:23:
/usr/include/glib-2.0/glib/gtypes.h:545:26: note: declared here
545 | typedef struct _GTimeVal GTimeVal
GLIB_DEPRECATED_TYPE_IN_2_62_FOR(GDateTime);
| ^~~~
In file included from /usr/include/gtk-2.0/gtk/gtktoolitem.h:31,
from /usr/include/gtk-2.0/gtk/gtktoolbutton.h:30,
from /usr/include/gtk-2.0/gtk/gtkmenutoolbutton.h:30,
from /usr/include/gtk-2.0/gtk/gtk.h:126,
from voice.h:27,
from voice.cpp:23:
/usr/include/gtk-2.0/gtk/gtktooltips.h:73:12: warning: ‘GTimeVal’ is
deprecated: Use 'GDateTime' instead [-Wdeprecated-declarations]
73 | GTimeVal last_popdown;
|^~~~
In file included from /usr/include/glib-2.0/glib/galloca.h:32,
from /usr/include/glib-2.0/glib.h:30,
from /usr/include/glib-2.0/gobject/gbinding.h:28,
from /usr/include/glib-2.0/glib-object.h:22,
from /usr/include/glib-2.0/gio/gioenums.h:28,
from /usr/include/glib-2.0/gio/giotypes.h:28,
from /usr/include/glib-2.0/gio/gio.h:26,
from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:30,
from /usr/include/gtk-2.0/gdk/gdk.h:32,
from /usr/include/gtk-2.0/gtk/gtk.h:32,
from voice.h:27,
from voice.cpp:23:
/usr/include/glib-2.0/glib/gtypes.h:545:26: note: declared here
545 | typedef struct _GTimeVal GTimeVal
GLIB_DEPRECATED_TYPE_IN_2_62_FOR(GDateTime);
| ^~~~
voice.cpp: In member function ‘bool NedVoice::tryConvertToTuplet(int, int,
NedChordOrRest*)’:
voice.cpp:1366:66: error: ordered comparison of pointer with integer zero
(‘GList*’ {aka ‘_GList*’} and ‘int’)
1366 | if ((min_pos_ptr = g_list_find(m_chord_or_rests, templ)) < 0) {
| ~^~~
make[3]: *** [Makefile:656: voice.o] Error 1
make[3]: *** Waiting for unfinished jobs
mainwindow.cpp: In static member function ‘static void
NedMainWindow::save_score(GtkWidget*, void*)’:
mainwindow.cpp:2885:28: warning: ‘%s’ directive writing up to 4095 bytes into a
region
Bug#970880: [Pkg-freeipa-devel] Bug#970880: Bug#970880: Bug#970880: Bug#970880: Bug#970880: freeipa-server: FreeIPA server installation fails with Certificate issuance failed (CA_REJECTED)
On Tue, Oct 12, 2021 at 2:17 PM Timo Aaltonen wrote: > > On 12.10.2021 20.48, Spencer Olson wrote: > > On Tue, Oct 12, 2021 at 9:53 AM Spencer Olson wrote: > >> > >> On Sun, Oct 10, 2021 at 12:58 PM Timo Aaltonen wrote: > >>> > > > Maybe the CI will finish before I can get back to my testing. > >>> > >>> And it did, this error is fixed now :) > >>> > >>> But it fails later on, so there's some work still to catch up with the > >>> current distro, but at least this particular annoyance is resolved, so > >>> many thanks for figuring it out! I was sure the reason was something > >>> silly and related to the SSL stack (or maybe ciphers) but was blind to > >>> see it. > >> > >> I borrowed the .deb packages from the build artifacts and tested more. > >> You probably already have this fixed but, > >>* /var/lib/gssproxy directory has to be created so that gssproxy can > >> be started. > > gssproxy 0.8.2-2 or newer has it. I have tried to keep my Debian Sid instance updated. It has gssproxy 0.8.4-1 installed. Installing gssproxy 0.8.4-1 did not result in /var/lib/gssproxy being created. Just for kicks, I tried removing then reinstalling to see if anything different would happen--it didn't and the directory still does not exist simply due to installation. > > Well, at this point my focus is on getting a working baseline on Debian sid. Unless you request any specific help, I will keep testing as you submit changes or new CI tests.
Bug#984099: marked as done (libebml: ftbfs with GCC-11)
Your message dated Tue, 12 Oct 2021 20:49:06 + with message-id and subject line Bug#984099: fixed in libebml 1.4.2-2 has caused the Debian Bug report #984099, regarding libebml: ftbfs with GCC-11 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.) -- 984099: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984099 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:libebml Version: 1.4.2-1 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye release] 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-11/g++-11, but succeeds to build with gcc-10/g++-10. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://people.debian.org/~doko/logs/20210228/filtered/gcc11/libebml_1.4.2-1_unstable_gcc11.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 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-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] make[2]: Entering directory '/<>/obj-x86_64-linux-gnu' make -f CMakeFiles/ebml.dir/build.make CMakeFiles/ebml.dir/depend make[3]: Entering directory '/<>/obj-x86_64-linux-gnu' cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /<> /<> /<>/obj-x86_64-linux-gnu /<>/obj-x86_64-linux-gnu /<>/obj-x86_64-linux-gnu/CMakeFiles/ebml.dir/DependInfo.cmake --color= Dependee "/<>/obj-x86_64-linux-gnu/CMakeFiles/ebml.dir/DependInfo.cmake" is newer than depender "/<>/obj-x86_64-linux-gnu/CMakeFiles/ebml.dir/depend.internal". Dependee "/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeDirectoryInformation.cmake" is newer than depender "/<>/obj-x86_64-linux-gnu/CMakeFiles/ebml.dir/depend.internal". Scanning dependencies of target ebml make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu' make -f CMakeFiles/ebml.dir/build.make CMakeFiles/ebml.dir/build make[3]: Entering directory '/<>/obj-x86_64-linux-gnu' [ 4%] Building CXX object CMakeFiles/ebml.dir/src/EbmlContexts.cpp.o /usr/bin/c++ -Debml_EXPORTS -I/<>/obj-x86_64-linux-gnu -I/<> -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -fvisibility=hidden -fvisibility-inlines-hidden -std=gnu++11 -o CMakeFiles/ebml.dir/src/EbmlContexts.cpp.o -c /<>/src/EbmlContexts.cpp [ 12%] Building CXX object CMakeFiles/ebml.dir/src/EbmlBinary.cpp.o [ 12%] Building CXX object CMakeFiles/ebml.dir/src/Debug.cpp.o /usr/bin/c++ -Debml_EXPORTS -I/<>/obj-x86_64-linux-gnu -I/<> -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -fvisibility=hidden -fvisibility-inlines-hidden -std=gnu++11 -o CMakeFiles/ebml.dir/src/Debug.cpp.o -c /<>/src/Debug.cpp /usr/bin/c++ -Debml_EXPORTS -I/<>/obj-x86_64-linux-gnu -I/<> -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -fvisibility=hidden -fvisibility-inlines-hidden -std=gnu++11 -o CMakeFiles/ebml.dir/src/EbmlBinary.cpp.o -c /<>/src/EbmlBinary.cpp [ 16%] Building CXX object CMakeFiles/ebml.dir/src/EbmlCrc32.cpp.o /usr/bin/c++ -Debml_EXPORTS -I/<>/obj-x86_64-linux-gnu -I/<> -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -fvisibility=hidden -fvisibility-inlines-hidden -std=gnu++11 -o CMakeFiles/ebml.dir/src/EbmlCrc32.cpp.o -c /<>/src/EbmlCrc32.cpp [ 20%] Building CXX object CMakeFiles/ebml.dir/src/EbmlDate.cpp.o /usr/bin/c++ -Debml_EXPORTS
Bug#984024: marked as done (connectome-workbench: ftbfs with GCC-11)
Your message dated Tue, 12 Oct 2021 20:48:37 + with message-id and subject line Bug#984024: fixed in connectome-workbench 1.5.0-2 has caused the Debian Bug report #984024, regarding connectome-workbench: ftbfs with GCC-11 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.) -- 984024: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984024 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:connectome-workbench Version: 1.5.0-1 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye release] 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-11/g++-11, but succeeds to build with gcc-10/g++-10. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://people.debian.org/~doko/logs/20210228/filtered/gcc11/connectome-workbench_1.5.0-1_unstable_gcc11.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 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-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] [ 11%] Building CXX object Annotations/CMakeFiles/Annotations.dir/AnnotationTypeEnum.cxx.o cd /<>/obj-x86_64-linux-gnu/Annotations && /usr/bin/c++ -DCARET_DOTFCN -DCARET_OS_LINUX -DHAVE_FREETYPE -DQT_CORE_LIB -DQT_NO_DEBUG -DWORKBENCH_HAVE_HELP_HTML -I/<>/src/kloewe/dot/src -I/usr/include/x86_64-linux-gnu/qt5/QtXml -I/<>/src/Common -I/<>/src/Graphics -I/<>/src/Scenes -I/<>/src/Nifti -isystem /usr/include/x86_64-linux-gnu/qt5 -isystem /usr/include/x86_64-linux-gnu/qt5/QtCore -isystem /usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -fopenmp -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -DNDEBUG -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -W -Wall -Werror=return-type -Werror=switch -Wunused-parameter -Wno-narrowing -Wno-unused-local-typedefs -fPIC -std=gnu++11 -o CMakeFiles/Annotations.dir/AnnotationTypeEnum.cxx.o -c /<>/src/Annotations/AnnotationTypeEnum.cxx [ 11%] Building CXX object FilesBase/CMakeFiles/FilesBase.dir/VolumeMappableInterface.cxx.o cd /<>/obj-x86_64-linux-gnu/FilesBase && /usr/bin/c++ -DCARET_DOTFCN -DCARET_OS_LINUX -DHAVE_FREETYPE -DQT_CORE_LIB -DQT_NO_DEBUG -DWORKBENCH_HAVE_HELP_HTML -I/<>/src/kloewe/dot/src -I/<>/src/Annotations -I/<>/src/FilesBase -I/<>/src/Common -I/<>/src/Palette -I/<>/src/Xml -isystem /usr/include/x86_64-linux-gnu/qt5 -isystem /usr/include/x86_64-linux-gnu/qt5/QtCore -isystem /usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -fopenmp -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -DNDEBUG -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -W -Wall -Werror=return-type -Werror=switch -Wunused-parameter -Wno-narrowing -Wno-unused-local-typedefs -fPIC -std=gnu++11 -o CMakeFiles/FilesBase.dir/VolumeMappableInterface.cxx.o -c /<>/src/FilesBase/VolumeMappableInterface.cxx [ 11%] Building CXX object Annotations/CMakeFiles/Annotations.dir/EventAnnotationAddToRemoveFromFile.cxx.o cd /<>/obj-x86_64-linux-gnu/Annotations && /usr/bin/c++ -DCARET_DOTFCN -DCARET_OS_LINUX -DHAVE_FREETYPE -DQT_CORE_LIB -DQT_NO_DEBUG -DWORKBENCH_HAVE_HELP_HTML -I/<>/src/kloewe/dot/src -I/usr/include/x86_64-linux-gnu/qt5/QtXml -I/<>/src/Common -I/<>/src/Graphics -I/<>/src/Scenes -I/<>/src/Nifti -isystem /usr/include/x86_64-linux-gnu/qt5 -isystem /usr/include/x86_64-linux-gnu/qt5/QtCore -isystem /usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -fopenmp -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -DNDEBUG -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -W -Wall
Bug#984361: marked as done (tcm: ftbfs with GCC-11)
Your message dated Tue, 12 Oct 2021 20:27:53 + with message-id and subject line Bug#984361: fixed in tcm 2.20+TSQD-7 has caused the Debian Bug report #984361, regarding tcm: ftbfs with GCC-11 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.) -- 984361: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984361 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:tcm Version: 2.20+TSQD-6 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye release] 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-11/g++-11, but succeeds to build with gcc-10/g++-10. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://people.debian.org/~doko/logs/20210228/filtered/gcc11/tcm_2.20+TSQD-6_unstable_gcc11.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 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-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] from modejunction.h:25, from modejunction.c:22: /<>/src/gl/llist.h: In member function ‘int List::next()’: /<>/src/gl/llist.h:106:17: warning: this ‘if’ clause does not guard... [-Wmisleading-indentation] 106 | if (current) current=current->next; return (current != 0); } | ^~ /<>/src/gl/llist.h:106:53: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘if’ 106 | if (current) current=current->next; return (current != 0); } | ^~ /<>/src/gl/llist.h: In member function ‘int List::prev()’: /<>/src/gl/llist.h:110:17: warning: this ‘if’ clause does not guard... [-Wmisleading-indentation] 110 | if (current) current=current->prev; return (current != 0); } | ^~ /<>/src/gl/llist.h:110:53: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘if’ 110 | if (current) current=current->prev; return (current != 0); } | ^~ /usr/bin/g++ -Wall -g -fcommon -O2 -DCONFIG_INSTALL=\"/etc/tcm/\" -DTCM_INSTALL_DIR=\"/usr\" -DTCM_INSTALL_LIB=\"/usr/lib/\" -DTCM_INSTALL_SHARE=\"/usr/share/doc/tcm-doc/\" -DCONFIG_FILE=\"tcm.conf\" -DHELP_DIR=\"/usr/share/doc/tcm-doc/help/\" -DCOLOR_FILE=\"colorrgb.txt\" -DBANNER_FILE=\"banner.ps\" -I. -I/<>/src/bitmaps -I/<>/src/gl -I/<>/src/ui -I/<>/src/ed -I/<>/src/dg -I/<>/src/tb -I/usr/X11R6/LessTif/Motif1.2/include -I/usr/X11R6/include -I/usr/X11R6/include/X11 -I../dv -DLINUX -c cbactor.c In file included from /<>/src/dg/thing.h:25, from /<>/src/dg/subject.h:25, from /<>/src/dg/node.h:25, from cbactor.h:26, from cbactor.c:23: /<>/src/gl/llist.h: In member function ‘int List::next()’: /<>/src/gl/llist.h:106:17: warning: this ‘if’ clause does not guard... [-Wmisleading-indentation] 106 | if (current) current=current->next; return (current != 0); } | ^~ /<>/src/gl/llist.h:106:53: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘if’ 106 | if (current) current=current->next; return (current != 0); } | ^~ /<>/src/gl/llist.h: In member function ‘int List::prev()’: /<>/src/gl/llist.h:110:17: warning: this ‘if’ clause does not guard...
Bug#995737: marked as done (pytest breaks pytest-doctestplus autopkgtest: pytest.PytestAssertRewriteWarning: Module already imported so cannot be rewritten: pytest_doctestplus)
Your message dated Tue, 12 Oct 2021 20:22:47 +
with message-id
and subject line Bug#995737: fixed in pytest-doctestplus 0.11.0-2
has caused the Debian Bug report #995737,
regarding pytest breaks pytest-doctestplus autopkgtest:
pytest.PytestAssertRewriteWarning: Module already imported so cannot be
rewritten: pytest_doctestplus
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.)
--
995737: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995737
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pytest, pytest-doctestplus
Control: found -1 pytest/6.2.5-1
Control: found -1 pytest-doctestplus/0.11.0-1
Severity: serious
Tags: sid bookworm
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update
Dear maintainer(s),
With a recent upload of pytest the autopkgtest of pytest-doctestplus
fails in testing when that autopkgtest is run with the binary packages
of pytest from unstable. It passes when run with only packages from
testing. In tabular form:
passfail
pytest from testing6.2.5-1
pytest-doctestplus from testing0.11.0-1
all others from testingfrom testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration of pytest to testing
[1]. Due to the nature of this issue, I filed this bug report against
both packages. Can you please investigate the situation and reassign the
bug to the right package?
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=pytest
https://ci.debian.net/data/autopkgtest/testing/amd64/p/pytest-doctestplus/15768646/log.gz
=== FAILURES
===
_ test_ignore_warnings_module
__
testdir =
def test_ignore_warnings_module(testdir):
# First check that we get a warning if we don't add the
IGNORE_WARNINGS
# directive
p = testdir.makepyfile(
"""
def myfunc():
'''
>>> import warnings
>>> warnings.warn('A warning occurred', UserWarning)
'''
pass
""")
> reprec = testdir.inline_run(p, "--doctest-plus", "-W error")
/tmp/autopkgtest-lxc.37ycsxwg/downtmp/build.mpq/src/tests/test_doctestplus.py:414:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _
/usr/lib/python3/dist-packages/_pytest/pytester.py:1615: in inline_run
return self._pytester.inline_run(
/usr/lib/python3/dist-packages/_pytest/pytester.py:1072: in inline_run
ret = main([str(x) for x in args], plugins=plugins)
/usr/lib/python3/dist-packages/_pytest/config/__init__.py:143: in main
config = _prepareconfig(args, plugins)
/usr/lib/python3/dist-packages/_pytest/config/__init__.py:318: in
_prepareconfig
config = pluginmanager.hook.pytest_cmdline_parse(
/usr/lib/python3/dist-packages/pluggy/hooks.py:286: in __call__
return self._hookexec(self, self.get_hookimpls(), kwargs)
/usr/lib/python3/dist-packages/pluggy/manager.py:92: in _hookexec
return self._inner_hookexec(hook, methods, kwargs)
/usr/lib/python3/dist-packages/pluggy/manager.py:83: in
self._inner_hookexec = lambda hook, methods, kwargs: hook.multicall(
/usr/lib/python3/dist-packages/_pytest/helpconfig.py:100: in
pytest_cmdline_parse
config: Config = outcome.get_result()
/usr/lib/python3/dist-packages/_pytest/config/__init__.py:1003: in
pytest_cmdline_parse
self.parse(args)
/usr/lib/python3/dist-packages/_pytest/config/__init__.py:1283: in parse
self._preparse(args, addopts=addopts)
/usr/lib/python3/dist-packages/_pytest/config/__init__.py:1167: in _preparse
self._consider_importhook(args)
/usr/lib/python3/dist-packages/_pytest/config/__init__.py:1114: in
_consider_importhook
self._mark_plugins_for_rewrite(hook)
/usr/lib/python3/dist-packages/_pytest/config/__init__.py:1135: in
_mark_plugins_for_rewrite
hook.mark_rewrite(name)
/usr/lib/python3/dist-packages/_pytest/assertion/rewrite.py:259: in
mark_rewrite
self._warn_already_imported(name)
/usr/lib/python3/dist-packages/_pytest/assertion/rewrite.py:266: in
_warn_already_imported
self.config.issue_config_time_warning(
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _
self = <_pytest.config.Config object at
Processed: Bug#984099 marked as pending in libebml
Processing control commands: > tag -1 pending Bug #984099 [src:libebml] libebml: ftbfs with GCC-11 Added tag(s) pending. -- 984099: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984099 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#984099: marked as pending in libebml
Control: tag -1 pending Hello, Bug #984099 in libebml 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/multimedia-team/libebml/-/commit/045247a442f9d3f00eb1f372ad6e274d3ea65ba3 Apply upstream patch to fix build with GCC 11 Closes: #984099 (this message was generated automatically) -- Greetings https://bugs.debian.org/984099
Bug#993184: Please switch upstream
Dear maintainer, I suggest to switch upstream to https://github.com/fer-moreira/floating-dock which is a fork of https://github.com/micheleg/dash-to-dock/. Floating-dock works perfectly fine for me in my bookworm installation. Cheers, Sven -- GPG Fingerprint 3DF5 E8AA 43FC 9FDF D086 F195 ADF5 0EDA F8AD D585 signature.asc Description: This is a digitally signed message part
Processed: simde: autopkgtest needs update for new version of gcc-defaults: x86/sse2/native/c(pp|) failed
Processing control commands: > affects -1 src:gcc-defaults Bug #996281 [src:simde] simde: autopkgtest needs update for new version of gcc-defaults: x86/sse2/native/c(pp|) failed Added indication that 996281 affects src:gcc-defaults -- 996281: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996281 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996281: simde: autopkgtest needs update for new version of gcc-defaults: x86/sse2/native/c(pp|) failed
Source: simde Version: 0.7.2-4 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:gcc-defaults [X-Debbugs-CC: debian...@lists.debian.org, gcc-defau...@packages.debian.org] Dear maintainer(s), With a recent upload of gcc-defaults the autopkgtest of simde fails in testing when that autopkgtest is run with the binary packages of gcc-defaults from unstable. It passes when run with only packages from testing. In tabular form: passfail gcc-defaults from testing1.194 simde from testing0.7.2-4 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of gcc-defaults to testing [1]. If this is a real problem in your package (and not only in your autopkgtest), the right binary package(s) from gcc-defaults should really add a versioned Breaks on the unfixed version of (one of your) package(s). Note: the Breaks is nice even if the issue is only in the autopkgtest as it helps the migration software to figure out the right versions to combine in the tests. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=gcc-defaults https://ci.debian.net/data/autopkgtest/testing/amd64/s/simde/15914134/log.gz 289/874 x86/sse2/native/c ERROR 0.59s exit status 1 >>> MALLOC_PERTURB_=93 /tmp/autopkgtest-lxc.vneo8tix/downtmp/autopkgtest_tmp/build-gcc/test/x86/sse2-native-c ― ✀ ― stderr: ../test/x86/sse2.c:4432: assertion failed: r[0] == simde_x_mm_loadu_epi16(test_vec[i].r)[0] (0 == -11138) ../test/x86/sse2.c:4465: assertion failed: r[0] == simde_x_mm_loadu_epi32(test_vec[i].r)[0] (0 == 418822831) (test program exited with status code 1) ―― 290/874 x86/sse2/native/cppERROR 0.59s exit status 1 >>> MALLOC_PERTURB_=239 /tmp/autopkgtest-lxc.vneo8tix/downtmp/autopkgtest_tmp/build-gcc/test/x86/sse2-native-cpp ― ✀ ― stderr: test/x86/sse2.cpp:4432: assertion failed: r[0] == simde_x_mm_loadu_epi16(test_vec[i].r)[0] (0 == -11138) test/x86/sse2.cpp:4465: assertion failed: r[0] == simde_x_mm_loadu_epi32(test_vec[i].r)[0] (0 == 418822831) (test program exited with status code 1) ―― OpenPGP_signature Description: OpenPGP digital signature
Bug#970880: [Pkg-freeipa-devel] Bug#970880: Bug#970880: Bug#970880: Bug#970880: Bug#970880: freeipa-server: FreeIPA server installation fails with Certificate issuance failed (CA_REJECTED)
On 12.10.2021 20.48, Spencer Olson wrote:
On Tue, Oct 12, 2021 at 9:53 AM Spencer Olson wrote:
On Sun, Oct 10, 2021 at 12:58 PM Timo Aaltonen wrote:
Maybe the CI will finish before I can get back to my testing.
And it did, this error is fixed now :)
But it fails later on, so there's some work still to catch up with the
current distro, but at least this particular annoyance is resolved, so
many thanks for figuring it out! I was sure the reason was something
silly and related to the SSL stack (or maybe ciphers) but was blind to
see it.
I borrowed the .deb packages from the build artifacts and tested more.
You probably already have this fixed but,
* /var/lib/gssproxy directory has to be created so that gssproxy can
be started.
gssproxy 0.8.2-2 or newer has it.
I manually created the path and ran the script again. It passes the
gssproxy error that the CI got stuck on, but it failed at creating the
client with this error:
DEBUG The ipa-client-install command failed, exception: KerberosError:
No valid Negotiate header in server response
2021-10-11T09:32:49Z ERROR No valid Negotiate header in server response
I've found a few posts online with errors similar to this in 2019 (one
"solution" supposedly posted on RedHat's site that I don't have access
to). But, I haven't figured this one out yet. Perhaps you already
know how to fix this one.
So, I am now wondering if the latest issue I am seeing (where iti
complains about the Negotiate problem) might be due to the bind9
configuration/installation not being quite correct.
I have two VMs, one for CentOS Stream.
For the CentOS stream VM:
- just uses a DHCP address because I was lazy in the setup and didn't
take the time to change this
- ipa-server-install finished successfully
- there is a named-pkcs11 program installed and corresponding
processing running
- the named-pkcs11 program is certainly linked to a few libraries
that the normal named program is not linked to
- the nameserver resolves things as expected: the host of the server
("sid" in my test case) and certainly also ipa-ca.domain resolve just
fine
- bind9-dyndb-ldap *is* installed
- doing "fuser /usr/lib64/bind/ldap.so" does show the process ID of
named-pkcs11
For the Debian sid install:
- Uses netplan to specify a static IP. This is the same VM i've been
using for all my tests, though I have been using and unwinding
snapshots a lot from test to test.
- ipa-server-install fails at the point that the ipa-client-install runs
- named-pkcs11 does *not* exist as an installed program
- `named` process is running and does respond to queries, but it does
not resolve anything useful
- browsing through the LDAP entries for DNS, I can see entries for
the ipa server, but named does not resolve these
- bind9-dyndb-ldap *is* installed.
- doing "fuser /usr/lib64/bind/ldap.so" does show the process ID of
named-pkcs11
So, clearly, there is a difference between the install on CentOS and
Debian Sid with the latest updates. I might add that my working old
ubuntu machine does indeed have the named-pkcs11 process. I am
wondering if this is a problem that was never resolved since the
updates to the new bind9 that plagued getting freeipa to work for
debian originally. Perhaps this was never fully finished because we
never had freeipa to actually test the changes in the bind9 package.
Well, at this point my focus is on getting a working baseline on Debian sid.
named-pkcs11 isn't used anymore with the current versions.
--
t
Processed: seqan3: autopkgtest needs update for new version of gcc-defaults
Processing control commands: > affects -1 src:gcc-defaults Bug #996280 [src:seqan3] seqan3: autopkgtest needs update for new version of gcc-defaults Added indication that 996280 affects src:gcc-defaults -- 996280: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996280 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996280: seqan3: autopkgtest needs update for new version of gcc-defaults
Source: seqan3
Version: 3.0.2+ds-9
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:gcc-defaults
[X-Debbugs-CC: debian...@lists.debian.org, gcc-defau...@packages.debian.org]
Dear maintainer(s),
With a recent upload of gcc-defaults the autopkgtest of seqan3 fails in
testing when that autopkgtest is run with the binary packages of
gcc-defaults from unstable. It passes when run with only packages from
testing. In tabular form:
passfail
gcc-defaults from testing1.194
seqan3 from testing3.0.2+ds-9
all others from testingfrom testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration of gcc-defaults to
testing [1].
If this is a real problem in your package (and not only in your
autopkgtest), the right binary package(s) from gcc-defaults should
really add a versioned Breaks on the unfixed version of (one of your)
package(s). Note: the Breaks is nice even if the issue is only in the
autopkgtest as it helps the migration software to figure out the right
versions to combine in the tests.
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=gcc-defaults
https://ci.debian.net/data/autopkgtest/testing/amd64/s/seqan3/15914132/log.gz
/tmp/autopkgtest-lxc.yel9kndg/downtmp/autopkgtest_tmp/unit/alignment/pairwise/pairwise_alignment_single_test_template.hpp:101:48:
required from ‘void
gtest_suite_pairwise_alignment_test_::alignment::TestBody()
[with gtest_TypeParam_ = pairwise_alignment_fixture<(&
seqan3::test::alignment::fixture::global::affine::banded::dna4_single_diagonal)>]’
/tmp/autopkgtest-lxc.yel9kndg/downtmp/autopkgtest_tmp/unit/alignment/pairwise/pairwise_alignment_single_test_template.hpp:89:1:
required from here
/usr/include/seqan3/alignment/pairwise/edit_distance_unbanded.hpp:946:19: error:
‘struct
seqan3::detail::edit_distance_unbanded&,
std::vector&,
seqan3::configuration >, seqan3::align_cfg::output_score,
seqan3::align_cfg::output_end_position,
seqan3::align_cfg::output_begin_position,
seqan3::align_cfg::output_alignment,
seqan3::detail::debug_mode >,
seqan3::align_cfg::detail::result_type >, seqan3::gap_decorator > >,
seqan3::detail::two_dimensional_matrix,
std::allocator >,
seqan3::detail::matrix_major_order::column>,
seqan3::detail::two_dimensional_matrix,
std::allocator >,
seqan3::detail::matrix_major_order::column> > > > >,
seqan3::detail::default_edit_distance_trait_type&,
std::vector&,
seqan3::configuration >, seqan3::align_cfg::output_score,
seqan3::align_cfg::output_end_position,
seqan3::align_cfg::output_begin_position,
seqan3::align_cfg::output_alignment,
seqan3::detail::debug_mode >,
seqan3::align_cfg::detail::result_type >, seqan3::gap_decorator > >,
seqan3::detail::two_dimensional_matrix,
std::allocator >,
seqan3::detail::matrix_major_order::column>,
seqan3::detail::two_dimensional_matrix,
std::allocator >,
seqan3::detail::matrix_major_order::column> > > > >,
std::integral_constant, long unsigned int>
>::compute_state’ has no member named ‘db’; did you mean ‘b’?
946 | state.db =
proxy_reference{this->db[current_block]};
| ~~^~
| b
/usr/include/seqan3/alignment/pairwise/edit_distance_unbanded.hpp:952:19: error:
‘struct
seqan3::detail::edit_distance_unbanded&,
std::vector&,
seqan3::configuration >, seqan3::align_cfg::output_score,
seqan3::align_cfg::output_end_position,
seqan3::align_cfg::output_begin_position,
seqan3::align_cfg::output_alignment,
seqan3::detail::debug_mode >,
seqan3::align_cfg::detail::result_type >, seqan3::gap_decorator > >,
seqan3::detail::two_dimensional_matrix,
std::allocator >,
seqan3::detail::matrix_major_order::column>,
seqan3::detail::two_dimensional_matrix,
std::allocator >,
seqan3::detail::matrix_major_order::column> > > > >,
seqan3::detail::default_edit_distance_trait_type&,
std::vector&,
seqan3::configuration >, seqan3::align_cfg::output_score,
seqan3::align_cfg::output_end_position,
seqan3::align_cfg::output_begin_position,
seqan3::align_cfg::output_alignment,
seqan3::detail::debug_mode >,
seqan3::align_cfg::detail::result_type >, seqan3::gap_decorator > >,
seqan3::detail::two_dimensional_matrix,
std::allocator >,
seqan3::detail::matrix_major_order::column>,
seqan3::detail::two_dimensional_matrix,
std::allocator >,
seqan3::detail::matrix_major_order::column> > > > >,
std::integral_constant, long unsigned int>
>::compute_state’ has no member named ‘db’; did you mean ‘b’?
952 | state.db = ~(state.b ^ state.d0);
| ~~^~
| b
make[2]: ***
[alignment/pairwise/CMakeFiles/global_affine_banded_test.dir/build.make:79:
Bug#996279: xmds2: autopkgtest needs update for new version of gcc-defaults: 5 tests fail to build
Source: xmds2
Version: 3.0.0+dfsg-5
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:gcc-defaults
[X-Debbugs-CC: debian...@lists.debian.org, gcc-defau...@packages.debian.org]
Dear maintainer(s),
With a recent upload of gcc-defaults the autopkgtest of xmds2 fails in
testing on the releases where it's not blocked when that autopkgtest is
run with the binary packages of gcc-defaults from unstable. It passes
when run with only packages from testing. In tabular form:
passfail
gcc-defaults from testing1.194
xmds2 from testing3.0.0+dfsg-5
all others from testingfrom testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration of gcc-defaults to
testing [1].
If this is a real problem in your package (and not only in your
autopkgtest), the right binary package(s) from gcc-defaults should
really add a versioned Breaks on the unfixed version of (one of your)
package(s). Note: the Breaks is nice even if the issue is only in the
autopkgtest as it helps the migration software to figure out the right
versions to combine in the tests.
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=gcc-defaults
https://ci.debian.net/data/autopkgtest/testing/amd64/x/xmds2/15914167/log.gz
==
FAIL: test_fibre_integer_dimensions_mpi
(__main__.main..ScriptTestCase)
mpi/fibre_integer_dimensions_mpi.xmds
--
Traceback (most recent call last):
File
"/tmp/autopkgtest-lxc.ekv9ekvw/downtmp/build.mTv/src/./run_tests.py",
line 328, in newfunc
return func(*(args + fargs), **newkeywords)
File
"/tmp/autopkgtest-lxc.ekv9ekvw/downtmp/build.mTv/src/./run_tests.py",
line 106, in scriptTestingFunction
self.assertTrue(returnCode == 0, ("Failed to compile." % locals()) +
message)
AssertionError: False is not true : Failed to compile.
stdout:
b'xmds2 version 3.0.0 "Release the Kraken" (Debian package
3.0.0+dfsg-5)\nCopyright 2000-2019 Graham Dennis, Joseph Hope, Mattias
Johnsson\nand the xmds team\nGenerating source
code...\n... done\nCompiling simulation...\n\n\nFATAL ERROR: Failed to
compile. Check warnings and errors. The most important will be first.\n'
stderr:
b'In file included from
/usr/lib/python3/dist-packages/xpdeint/includes/solirte/randpool.h:19,\n
from
/usr/lib/python3/dist-packages/xpdeint/includes/solirte/prng.h:13,\n
from
fibre_integer_dimensions_mpi.cc:96:\n/usr/lib/python3/dist-packages/xpdeint/includes/solirte/u128simd.h:
In function \xe2\x80\x98uint128_t SIMDOps::AndNot(const uint128_t&,
const
uint128_t&)\xe2\x80\x99:\n/usr/lib/python3/dist-packages/xpdeint/includes/solirte/u128simd.h:402:32:
warning: narrowing conversion of
\xe2\x80\x98SIMDOps::AndNot(((uint64_t)((int64_t)LHS.uint128_t::VecData[0])),
((uint64_t)((int64_t)RHS.uint128_t::VecData[0])))\xe2\x80\x99 from
\xe2\x80\x98uint64_t\xe2\x80\x99 {aka \xe2\x80\x98long unsigned
int\xe2\x80\x99} to \xe2\x80\x98int64_t\xe2\x80\x99 {aka
\xe2\x80\x98long int\xe2\x80\x99} [-Wnarrowing]\n 402 | uint128_t
RetVal = {{AndNot(LHS.VecData[0], RHS.VecData[0]),
AndNot(LHS.VecData[1], RHS.VecData[1])}};\n |
~~^~~~\n/usr/lib/python3/dist-packages/xpdeint/includes/solirte/u128simd.h:402:72:
warning: narrowing conversion of
\xe2\x80\x98SIMDOps::AndNot(((uint64_t)((int64_t)LHS.uint128_t::VecData[1])),
((uint64_t)((int64_t)RHS.uint128_t::VecData[1])))\xe2\x80\x99 from
\xe2\x80\x98uint64_t\xe2\x80\x99 {aka \xe2\x80\x98long unsigned
int\xe2\x80\x99} to \xe2\x80\x98int64_t\xe2\x80\x99 {aka
\xe2\x80\x98long int\xe2\x80\x99} [-Wnarrowing]\n 402 | uint128_t
RetVal = {{AndNot(LHS.VecData[0], RHS.VecData[0]),
AndNot(LHS.VecData[1], RHS.VecData[1])}};\n |
~~^~~~\n/usr/lib/python3/dist-packages/xpdeint/includes/solirte/u128simd.h:
In function \xe2\x80\x98uint128_t SIMDOps::Parity(const
uint128_t&)\xe2\x80\x99:\n/usr/lib/python3/dist-packages/xpdeint/includes/solirte/u128simd.h:468:26:
warning: narrowing conversion of \xe2\x80\x98x\xe2\x80\x99 from
\xe2\x80\x98uint64_t\xe2\x80\x99 {aka \xe2\x80\x98long unsigned
int\xe2\x80\x99} to \xe2\x80\x98int64_t\xe2\x80\x99 {aka
\xe2\x80\x98long int\xe2\x80\x99} [-Wnarrowing]\n 468 | uint128_t
RetVal = {{x, x}};\n |
^\n/usr/lib/python3/dist-packages/xpdeint/includes/solirte/u128simd.h:468:29:
warning: narrowing conversion of \xe2\x80\x98x\xe2\x80\x99 from
\xe2\x80\x98uint64_t\xe2\x80\x99 {aka \xe2\x80\x98long unsigned
int\xe2\x80\x99} to \xe2\x80\x98int64_t\xe2\x80\x99 {aka
\xe2\x80\x98long int\xe2\x80\x99} [-Wnarrowing]\n
Processed: xmds2: autopkgtest needs update for new version of gcc-defaults: 5 tests fail to build
Processing control commands: > affects -1 src:gcc-defaults Bug #996279 [src:xmds2] xmds2: autopkgtest needs update for new version of gcc-defaults: 5 tests fail to build Added indication that 996279 affects src:gcc-defaults -- 996279: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996279 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996028: [debian-mysql] Bug#996028: InnoDB: corrupted TRX_NO after upgrading to 10.3.31
On Sunday 10 October 2021 23:58:12 Otto Kekäläinen wrote: > > The problem is in the ibdata1 file (about 450MB). Deleted other database > > directories and it still crashes, deleted ibdata1 and it runs. > > > > How to bisect mariadb from git? Tried: > > $ git bisect good mariadb-10.3.29 > > $ git bisect bad mariadb-10.3.31 > > the build process showed version 10.2 so I aborted it. > > > > Checked out mariadb-10.3.30 but dpkg-buildpackage failed with: > > dh_install: mariadb-plugin-cassandra missing files: > > etc/mysql/conf.d/cassandra.cnf > > Some dependency was missing and Cassandra was not built. Note that the > upstream repository is not identical to the one in Debian regarding > the contents of debian/ directory. MariaDB builds without a cache take > 30 mins each and there are all kinds of things going on. Doing bisect > (fully correctly) on MariaDB is hard even for experienced developers. > Your time is probably better spent doing some other kind of debugging. > > I recommend that you file a bug about this upstream, and try to attach > relevant info from the error log, maybe a strace output etc. Upstream > devs will guide you on what to debug next. > > One thing you could also try is to start the server with 10.3.29 and > ensure that you have a clean shutdown (SET GLOBAL > innodb_fast_shutdown=0; SHUTDOWN) and only after that start with the > new 10.3.31 binary. With fast shutdown disabled, mysqld (10.3.29) seems to be stuck in an infinite loop. 100% CPU usage, no I/O for an hour until I killed it. Even dropping all the databases did not help - killed it after it has been running for 5 minutes. Deleted ibdata1 (and ib_logfile0, ib_logfile1), then shutdown ended immediately. Seems that the file structure is corrupted somehow - probably because of a previous bug. One table is also affected by the "ERROR 1118 (42000): Row size too large (> 8126)" bug. When complete SQL dump is restored with a new ibdata1, everything works (upgrade to 10.3.31 and also clean shutdown). -- Ondrej Zary
Processed: Re: Bug#995362: zint breaks zbar autopkgtest: unable to open file `/tmp/magick-VxkNk3KeW43pSnBYixIpsF9xU8qRmIzE': No such file or directory @ error/constitute.c/ReadImage/614
Processing control commands: > severity -1 important Bug #995362 [zbar-tools] zint breaks zbar autopkgtest: unable to open file `/tmp/magick-VxkNk3KeW43pSnBYixIpsF9xU8qRmIzE': No such file or directory @ error/constitute.c/ReadImage/614 Severity set to 'important' from 'serious' -- 995362: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995362 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#995362: zint breaks zbar autopkgtest: unable to open file `/tmp/magick-VxkNk3KeW43pSnBYixIpsF9xU8qRmIzE': No such file or directory @ error/constitute.c/ReadImage/614
Control: severity -1 important On Thu, 30 Sep 2021 23:32:21 + John Scott wrote: > On Thu, 2021-09-30 at 09:18 -0400, John Scott wrote: > > Outside a minimal chroot, on my desktop system, zbarimg seems to > > process SVGs just fine. So this may be a case of a Recommends > > (somewhere) not being installed wreaking havok, but in my opinion > > zbarimg should still not behave this way when a Recommends is > > missing. > > I've found the culprit: if libmagickcore-6.q16-6-extra is not > installed, then this cryptic error occurs. I've reported this issue > (the lack of a helpful error message) at > https://github.com/mchehab/zbar/issues/202 . > > I'll leave it to the maintainer to decide what they'd like to do: > either hardcode a dependency on libmagickcore-6.q16-6-extra, or switch > zint's output format to PNG (I personally would prefer the latter). I have set the bug forwarding address to https://github.com/mchehab/zbar/issues/202 . Besides, the new zbar/0.23.92-4 upload has switched zint's output format to PNG. Downgrading severity to important since this issue is not RC-buggy now. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Processed: open3d: autopkgtest needs update for new version of gcc-defaults: output on stderr
Processing control commands: > affects -1 src:gcc-defaults Bug #996278 [src:open3d] open3d: autopkgtest needs update for new version of gcc-defaults: output on stderr Added indication that 996278 affects src:gcc-defaults -- 996278: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996278 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996278: open3d: autopkgtest needs update for new version of gcc-defaults: output on stderr
Source: open3d
Version: 0.9.0+ds-6
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:gcc-defaults
[X-Debbugs-CC: debian...@lists.debian.org, gcc-defau...@packages.debian.org]
Dear maintainer(s),
With a recent upload of gcc-defaults the autopkgtest of open3d fails in
testing on arm64, armhf and ppc64el when that autopkgtest is run with
the binary packages of gcc-defaults from unstable. It passes when run
with only packages from testing. In tabular form:
passfail
gcc-defaults from testing1.194
open3d from testing0.9.0+ds-6
all others from testingfrom testing
I copied some of the output at the bottom of this report. The failure is
due to output on stderr. Output to stderr is by default considered by
autopkgtest as a failure of the test. If you want to have test fail on
output to stderr, please fix the reason of the output. If you don't care
you can add the allow-stderr restriction to have autopkgtest ignore the
output.
Currently this regression is blocking the migration of gcc-defaults to
testing [1]. Of course, gcc-defaults shouldn't just break your
autopkgtest (or even worse, your package), but it seems to me that the
change in gcc-defaults was intended and your package needs to update to
the new situation.
If this is a real problem in your package (and not only in your
autopkgtest), the right binary package(s) from gcc-defaults should
really add a versioned Breaks on the unfixed version of (one of your)
package(s). Note: the Breaks is nice even if the issue is only in the
autopkgtest as it helps the migration software to figure out the right
versions to combine in the tests.
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=gcc-defaults
https://ci.debian.net/data/autopkgtest/testing/arm64/o/open3d/15926028/log.gz
autopkgtest [01:10:43]: test test-cpp: [---
$ cmake .
-- The C compiler identification is GNU 11.2.0
-- The CXX compiler identification is GNU 11.2.0
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Found GLEW: /usr/include (found version "2.2.0")
-- Found Open3D:
/usr/lib/aarch64-linux-gnu/cmake/Open3D/Open3DConfig.cmake (found
version "0.9.0")
-- Configuring done
-- Generating done
-- Build files have been written to: /tmp/tmp.HsneE5NHLQ
$ make VERBOSE=ON
/usr/bin/cmake -S/tmp/tmp.HsneE5NHLQ -B/tmp/tmp.HsneE5NHLQ
--check-build-system CMakeFiles/Makefile.cmake 0
/usr/bin/cmake -E cmake_progress_start /tmp/tmp.HsneE5NHLQ/CMakeFiles
/tmp/tmp.HsneE5NHLQ//CMakeFiles/progress.marks
make -f CMakeFiles/Makefile2 all
make[1]: Entering directory '/tmp/tmp.HsneE5NHLQ'
make -f CMakeFiles/open3d_test.dir/build.make
CMakeFiles/open3d_test.dir/depend
make[2]: Entering directory '/tmp/tmp.HsneE5NHLQ'
cd /tmp/tmp.HsneE5NHLQ && /usr/bin/cmake -E cmake_depends "Unix
Makefiles" /tmp/tmp.HsneE5NHLQ /tmp/tmp.HsneE5NHLQ /tmp/tmp.HsneE5NHLQ
/tmp/tmp.HsneE5NHLQ
/tmp/tmp.HsneE5NHLQ/CMakeFiles/open3d_test.dir/DependInfo.cmake --color=
make[2]: Leaving directory '/tmp/tmp.HsneE5NHLQ'
make -f CMakeFiles/open3d_test.dir/build.make
CMakeFiles/open3d_test.dir/build
make[2]: Entering directory '/tmp/tmp.HsneE5NHLQ'
[ 50%] Building CXX object CMakeFiles/open3d_test.dir/open3d_test.cpp.o
/usr/bin/c++ -DFMT_LOCALE -DFMT_SHARED -isystem /usr/include/eigen3 -MD
-MT CMakeFiles/open3d_test.dir/open3d_test.cpp.o -MF
CMakeFiles/open3d_test.dir/open3d_test.cpp.o.d -o
CMakeFiles/open3d_test.dir/open3d_test.cpp.o -c
/tmp/tmp.HsneE5NHLQ/open3d_test.cpp
In file included from /usr/include/Open3D/Open3D.h:30,
from /tmp/tmp.HsneE5NHLQ/open3d_test.cpp:1:
/usr/include/Open3D/Camera/PinholeCameraIntrinsic.h: In member function
‘std::pair
open3d::camera::PinholeCameraIntrinsic::GetFocalLength() const’:
/usr/include/Open3D/Camera/PinholeCameraIntrinsic.h:93:54: note:
parameter passing for argument of type ‘std::pair’ when
C++17 is enabled changed to match C++14 in GCC 10.1
93 | std::pair GetFocalLength() const {
| ^
[100%] Linking CXX executable open3d_test
/usr/bin/cmake -E cmake_link_script CMakeFiles/open3d_test.dir/link.txt
--verbose=ON
/usr/bin/c++ CMakeFiles/open3d_test.dir/open3d_test.cpp.o -o open3d_test
/usr/lib/aarch64-linux-gnu/libOpen3D.so.0d
make[2]: Leaving directory '/tmp/tmp.HsneE5NHLQ'
[100%] Built target open3d_test
make[1]: Leaving directory
Processed: deal.ii: autopkgtest needs update for new version of gcc-defaults: An error occurred in line <1048> of file <./source/fe/mapping_q_generic.cc> in function
Processing control commands: > affects -1 src:gcc-defaults Bug #996277 [src:deal.ii] deal.ii: autopkgtest needs update for new version of gcc-defaults: An error occurred in line <1048> of file <./source/fe/mapping_q_generic.cc> in function Added indication that 996277 affects src:gcc-defaults -- 996277: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996277 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996277: deal.ii: autopkgtest needs update for new version of gcc-defaults: An error occurred in line <1048> of file <./source/fe/mapping_q_generic.cc> in function
Source: deal.ii
Version: 9.3.0-1
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:gcc-defaults
[X-Debbugs-CC: debian...@lists.debian.org, gcc-defau...@packages.debian.org]
Dear maintainer(s),
With a recent upload of gcc-defaults the autopkgtest of deal.ii fails in
testing on amd64 and ppc64el when that autopkgtest is run with the
binary packages of gcc-defaults from unstable. It passes when run with
only packages from testing. In tabular form:
passfail
gcc-defaults from testing1.194
deal.iifrom testing9.3.0-1
all others from testingfrom testing
I copied some of the output on amd64 at the bottom of this report;
ppc64el fails in a different way.
Currently this regression is blocking the migration of gcc-defaults to
testing [1]. Of course, gcc-defaults shouldn't just break your
autopkgtest (or even worse, your package), but it seems to me that the
change in gcc-defaults was intended and your package needs to update to
the new situation.
If this is a real problem in your package (and not only in your
autopkgtest), the right binary package(s) from gcc-defaults should
really add a versioned Breaks on the unfixed version of (one of your)
package(s). Note: the Breaks is nice even if the issue is only in the
autopkgtest as it helps the migration software to figure out the right
versions to combine in the tests.
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=gcc-defaults
https://ci.debian.net/data/autopkgtest/testing/amd64/d/deal.ii/15913694/log.gz
-- Build files have been written to:
/tmp/autopkgtest-lxc.hp8op3fo/downtmp/autopkgtest_tmp/examples/step-50
make
[ 50%] Building CXX object CMakeFiles/step-50.dir/step-50.cc.o
In file included from
/usr/include/boost/smart_ptr/detail/sp_thread_sleep.hpp:22,
from /usr/include/boost/smart_ptr/detail/yield_k.hpp:23,
from
/usr/include/boost/smart_ptr/detail/spinlock_gcc_atomic.hpp:14,
from /usr/include/boost/smart_ptr/detail/spinlock.hpp:42,
from
/usr/include/boost/smart_ptr/detail/spinlock_pool.hpp:25,
from /usr/include/boost/smart_ptr/shared_ptr.hpp:29,
from
/usr/include/boost/archive/detail/helper_collection.hpp:27,
from
/usr/include/boost/archive/detail/basic_iarchive.hpp:28,
from
/usr/include/boost/archive/detail/common_iarchive.hpp:21,
from
/usr/include/boost/archive/basic_binary_iarchive.hpp:30,
from
/usr/include/boost/archive/binary_iarchive_impl.hpp:21,
from /usr/include/boost/archive/binary_iarchive.hpp:20,
from /usr/include/deal.II/base/utilities.h:45,
from /usr/include/deal.II/base/tensor.h:26,
from /usr/include/deal.II/base/point.h:23,
from /usr/include/deal.II/base/geometry_info.h:24,
from /usr/include/deal.II/base/data_out_base.h:22,
from
/tmp/autopkgtest-lxc.hp8op3fo/downtmp/autopkgtest_tmp/examples/step-50/step-50.cc:29:
/usr/include/boost/detail/no_exceptions_support.hpp:17:1: note: ‘#pragma
message: This header is deprecated. Use
instead.’
17 | BOOST_HEADER_DEPRECATED("")
| ^~~
[100%] Linking CXX executable step-50
[100%] Built target step-50
./step-50 gmg_mb_2d.prm
Cycle 0:
Number of active cells: 12 (2 global levels)
Partition efficiency: 1
Number of degrees of freedom: 65 (by level: 21, 65)
An error occurred in line <1048> of file
<./source/fe/mapping_q_generic.cc> in function
dealii::CellSimilarity::Similarity dealii::MappingQGeneric::fill_fe_values(const typename dealii::Triangulation::cell_iterator&, dealii::CellSimilarity::Similarity, const
dealii::Quadrature&, const typename dealii::Mapping::InternalDataBase&,
dealii::internal::FEValuesImplementation::MappingRelatedData&) const [with int dim = 2; int spacedim = 2; typename
dealii::Triangulation::cell_iterator =
dealii::TriaIterator >; typename
dealii::Mapping::InternalDataBase = dealii::Mapping<2,
2>::InternalDataBase]
The violated condition was:
det > 1e-12 * Utilities::fixed_power( cell->diameter() /
std::sqrt(double(dim)))
Additional information:
The image of the mapping applied to cell with center [-1 -0.125] is
distorted. The cell geometry or the mapping are invalid, giving a
non-positive volume fraction of -0.221825 in quadrature point 0.
Stacktrace:
---
#0 /lib/x86_64-linux-gnu/libdeal.ii.g.so.9.3.0:
dealii::MappingQGeneric<2,
2>::fill_fe_values(dealii::TriaIterator >
const&, dealii::CellSimilarity::Similarity, dealii::Quadrature<2>
const&,
Bug#996188: marked as done (RuntimeError: populate() isn't reentrant)
Your message dated Tue, 12 Oct 2021 20:51:11 +0200
with message-id <024a686c-cf8b-6b27-de85-0a907ac5a...@debian.org>
and subject line Re: Bug#996188: RuntimeError: populate() isn't reentrant
has caused the Debian Bug report #996188,
regarding RuntimeError: populate() isn't reentrant
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.)
--
996188: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996188
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: graphite-web
Version: 1.1.8-1
Severity: grave
Dear Maintainer,
Installed graphite-web on a fresh bullseye machine and migrated the apache
virtualhost configuration from a running buster machine.
Attempting to load the page results in the error listed in the subject.
Full traceback:
[Mon Oct 11 23:04:53.039528 2021] [wsgi:error] [pid 12645:tid 140670772766464]
[remote 2603:6080:a201:f403:c2d6:3266:d138:be92:40254] mod_wsgi (pid=12645):
Failed to exec Python script file '/usr/share/graphite-web/graphite.wsgi'.
[Mon Oct 11 23:04:53.039710 2021] [wsgi:error] [pid 12645:tid 140670772766464]
[remote 2603:6080:a201:f403:c2d6:3266:d138:be92:40254] mod_wsgi (pid=12645):
Exception occurred processing WSGI script
'/usr/share/graphite-web/graphite.wsgi'.
[Mon Oct 11 23:04:53.040057 2021] [wsgi:error] [pid 12645:tid 140670772766464]
[remote 2603:6080:a201:f403:c2d6:3266:d138:be92:40254] Traceback (most recent
call last):
[Mon Oct 11 23:04:53.040169 2021] [wsgi:error] [pid 12645:tid 140670772766464]
[remote 2603:6080:a201:f403:c2d6:3266:d138:be92:40254] File
"/usr/share/graphite-web/graphite.wsgi", line 15, in
[Mon Oct 11 23:04:53.040190 2021] [wsgi:error] [pid 12645:tid 140670772766464]
[remote 2603:6080:a201:f403:c2d6:3266:d138:be92:40254] application =
get_wsgi_application()
[Mon Oct 11 23:04:53.040217 2021] [wsgi:error] [pid 12645:tid 140670772766464]
[remote 2603:6080:a201:f403:c2d6:3266:d138:be92:40254] File
"/usr/lib/python3/dist-packages/django/core/wsgi.py", line 12, in
get_wsgi_application
[Mon Oct 11 23:04:53.040232 2021] [wsgi:error] [pid 12645:tid 140670772766464]
[remote 2603:6080:a201:f403:c2d6:3266:d138:be92:40254]
django.setup(set_prefix=False)
[Mon Oct 11 23:04:53.040257 2021] [wsgi:error] [pid 12645:tid 140670772766464]
[remote 2603:6080:a201:f403:c2d6:3266:d138:be92:40254] File
"/usr/lib/python3/dist-packages/django/__init__.py", line 24, in setup
[Mon Oct 11 23:04:53.040271 2021] [wsgi:error] [pid 12645:tid 140670772766464]
[remote 2603:6080:a201:f403:c2d6:3266:d138:be92:40254]
apps.populate(settings.INSTALLED_APPS)
[Mon Oct 11 23:04:53.040295 2021] [wsgi:error] [pid 12645:tid 140670772766464]
[remote 2603:6080:a201:f403:c2d6:3266:d138:be92:40254] File
"/usr/lib/python3/dist-packages/django/apps/registry.py", line 83, in populate
[Mon Oct 11 23:04:53.040309 2021] [wsgi:error] [pid 12645:tid 140670772766464]
[remote 2603:6080:a201:f403:c2d6:3266:d138:be92:40254] raise
RuntimeError("populate() isn't reentrant")
[Mon Oct 11 23:04:53.040389 2021] [wsgi:error] [pid 12645:tid 140670772766464]
[remote 2603:6080:a201:f403:c2d6:3266:d138:be92:40254] RuntimeError: populate()
isn't reentrant
-- System Information:
Debian Release: 11.1
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-8-amd64 (SMP w/1 CPU thread)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to en_US.UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages graphite-web depends on:
ii adduser 3.118
ii python3 3.9.2-3
ii python3-cairo 1.16.2-4+b2
ii python3-cairocffi 1.2.0-1
ii python3-django 2:2.2.24-1
ii python3-django-tagging 1:0.4.5-3
ii python3-pyparsing 2.4.7-1
ii python3-simplejson 3.17.2-1
ii python3-six 1.16.0-2
ii python3-tz 2021.1-1
ii python3-urllib3 1.26.5-1~exp1
ii python3-whisper 1.1.4-2.1
graphite-web recommends no packages.
Versions of packages graphite-web suggests:
pn graphite-carbon
ii libapache2-mod-wsgi-py3 4.7.1-3+b1
pn python3-ldap
pn python3-memcache
pn python3-mysqldb
-- no debconf information
--- End Message ---
--- Begin Message ---
On 10/12/21 1:11 AM, Kevin Otte wrote:
> Package: graphite-web
> Version: 1.1.8-1
> Severity: grave
>
> Dear Maintainer,
>
> Installed graphite-web on a
Bug#995928: acorn: doc directory shipped by both binaries
Hi release team, concerning this bug, I'd like to hear advice from you on how you'd best like to see this fixed in stable. The current bug causes trouble for reproducible builds operations (basically, it throws away all build involving node-acorn in bullseye). See the last paragraph on my thoughts about the potential solutions; I'm happy to implement what you think would be best. On Fri, Oct 08, 2021 at 12:07:36PM +0200, Mattia Rizzolo wrote: > Source: acorn > Version: 8.0.5+ds+~cs19.19.27-3 > Severity: serious > Control: fixed -1 8.5.0+ds+~cs23.9.6-2 > > This happens in bullseye: > > root@warren:/# apt install node-acorn > ... > The following NEW packages will be installed: > libbrotli1 libc-ares2 libicu67 libnghttp2-14 libnode72 libuv1 node-acorn > node-debbundle-acorn node-xtend nodejs > ... > root@warren:/# apt install --reinstall node-debbundle-acorn > ... > (Reading database ... 12963 files and directories currently installed.) > Preparing to unpack .../node-debbundle-acorn_8.0.5+ds+~cs19.19.27-3_all.deb > ... > Unpacking node-debbundle-acorn (8.0.5+ds+~cs19.19.27-3) over > (8.0.5+ds+~cs19.19.27-3) ... > (Noting disappearance of node-acorn, which has been completely replaced.) > Setting up node-debbundle-acorn (8.0.5+ds+~cs19.19.27-3) ... > The following package disappeared from your system as > all files have been overwritten by other packages: > node-acorn > Note: This is done automatically and on purpose by dpkg. > > > This is due to node-acorn shipping /usr/share/doc/node-acorn (type: > symlink) which is *also* shipping by node-debbundle-acorn (type: > directory). > dpkg seems to always overwrite the symlink anyway, but it doesn't detect > that it's gone until later when reinstalling it. > > > To be honest, I'm not sure what was the wanted situation, but I *think* > the symlink is just wrong. Looking at the content of the > /usr/share/doc/node-acorn/ directory as present in node-debbundle-acorn, > I think that is the appropriate content. So, probably, the best fix is > to just get rid of the symlink from node-acorn, however that would leave > the package totally empty, which dpkg is not totally thrilled about. > So more likely at least the 2 symlinks of copyright and > changelog.Debian.gz in /usr/share/doc/node-acorn could be moved from > node-debbundle-acorn to node-acorn, so effectively shipping the > directory from both packages. > > > > This is fixed in 8.5.0+ds+~cs23.9.6-2 by moving everything to node-acorn > and turning node-debbundle-acorn into a pure transitional package. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. More about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature
Processed: found 994300 in 0.7.0-2
Processing commands for cont...@bugs.debian.org:
> found 994300 0.7.0-2
Bug #994300 {Done: Picca Frédéric-Emmanuel } [src:gpyfft]
gpyfft: Removal of the python3-*-dbg packages in sid/bookworm
Marked as found in versions gpyfft/0.7.0-2.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
994300: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994300
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: severity of 993622 is serious
Processing commands for cont...@bugs.debian.org:
> severity 993622 serious
Bug #993622 {Done: Timo Röhling } [python3-open3d]
python3-open3d: Missing dependency on python3-numpy
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
993622: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993622
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#970880: [Pkg-freeipa-devel] Bug#970880: Bug#970880: Bug#970880: Bug#970880: freeipa-server: FreeIPA server installation fails with Certificate issuance failed (CA_REJECTED)
On Tue, Oct 12, 2021 at 9:53 AM Spencer Olson wrote:
>
> On Sun, Oct 10, 2021 at 12:58 PM Timo Aaltonen wrote:
> >
> > >
> > >
> > > Maybe the CI will finish before I can get back to my testing.
> >
> > And it did, this error is fixed now :)
> >
> > But it fails later on, so there's some work still to catch up with the
> > current distro, but at least this particular annoyance is resolved, so
> > many thanks for figuring it out! I was sure the reason was something
> > silly and related to the SSL stack (or maybe ciphers) but was blind to
> > see it.
>
> I borrowed the .deb packages from the build artifacts and tested more.
> You probably already have this fixed but,
> * /var/lib/gssproxy directory has to be created so that gssproxy can
> be started.
>
> I manually created the path and ran the script again. It passes the
> gssproxy error that the CI got stuck on, but it failed at creating the
> client with this error:
>
> DEBUG The ipa-client-install command failed, exception: KerberosError:
> No valid Negotiate header in server response
> 2021-10-11T09:32:49Z ERROR No valid Negotiate header in server response
>
> I've found a few posts online with errors similar to this in 2019 (one
> "solution" supposedly posted on RedHat's site that I don't have access
> to). But, I haven't figured this one out yet. Perhaps you already
> know how to fix this one.
So, I am now wondering if the latest issue I am seeing (where iti
complains about the Negotiate problem) might be due to the bind9
configuration/installation not being quite correct.
I have two VMs, one for CentOS Stream.
For the CentOS stream VM:
- just uses a DHCP address because I was lazy in the setup and didn't
take the time to change this
- ipa-server-install finished successfully
- there is a named-pkcs11 program installed and corresponding
processing running
- the named-pkcs11 program is certainly linked to a few libraries
that the normal named program is not linked to
- the nameserver resolves things as expected: the host of the server
("sid" in my test case) and certainly also ipa-ca.domain resolve just
fine
- bind9-dyndb-ldap *is* installed
- doing "fuser /usr/lib64/bind/ldap.so" does show the process ID of
named-pkcs11
For the Debian sid install:
- Uses netplan to specify a static IP. This is the same VM i've been
using for all my tests, though I have been using and unwinding
snapshots a lot from test to test.
- ipa-server-install fails at the point that the ipa-client-install runs
- named-pkcs11 does *not* exist as an installed program
- `named` process is running and does respond to queries, but it does
not resolve anything useful
- browsing through the LDAP entries for DNS, I can see entries for
the ipa server, but named does not resolve these
- bind9-dyndb-ldap *is* installed.
- doing "fuser /usr/lib64/bind/ldap.so" does show the process ID of
named-pkcs11
So, clearly, there is a difference between the install on CentOS and
Debian Sid with the latest updates. I might add that my working old
ubuntu machine does indeed have the named-pkcs11 process. I am
wondering if this is a problem that was never resolved since the
updates to the new bind9 that plagued getting freeipa to work for
debian originally. Perhaps this was never fully finished because we
never had freeipa to actually test the changes in the bind9 package.
Bug#995815: marked as done (ruby-eventmachine FTBFS on IPV6-only buildds)
Your message dated Tue, 12 Oct 2021 17:34:40 +
with message-id
and subject line Bug#995815: fixed in ruby-eventmachine
1.3~pre20201020-b50c135-4
has caused the Debian Bug report #995815,
regarding ruby-eventmachine FTBFS on IPV6-only buildds
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.)
--
995815: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995815
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-eventmachine
Version: 1.3~pre20190820-g10fb0c4-3
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/logs.php?pkg=ruby-eventmachine=amd64
...
TestResolver:
test_garbage: F
===
Failure: test_garbage(TestResolver)
/<>/tests/test_resolver.rb:58:in `test_garbage'
55: end
56:
57: def test_garbage
=> 58: assert_raises( ArgumentError ) {
59: EM.run {
60: EM::DNS::Resolver.resolve 123
61: }
expected but was
)
...
Finished in 8.026344954 seconds.
---
274 tests, 3490 assertions, 2 failures, 24 errors, 0 pendings, 10 omissions, 0
notifications
90.1515% passed
---
34.14 tests/s, 434.82 assertions/s
rake aborted!
Command failed with status (1): [ruby -w -I"tests"
/usr/share/rubygems-integration/all/gems/rake-13.0.3/lib/rake/rake_test_loader.rb
"tests/jruby/test_jeventmachine.rb" "tests/test_attach.rb"
"tests/test_basic.rb" "tests/test_channel.rb" "tests/test_completion.rb"
"tests/test_connection_count.rb" "tests/test_connection_write.rb"
"tests/test_defer.rb" "tests/test_deferrable.rb" "tests/test_epoll.rb"
"tests/test_error_handler.rb" "tests/test_exc.rb" "tests/test_file_watch.rb"
"tests/test_fork.rb" "tests/test_futures.rb" "tests/test_handler_check.rb"
"tests/test_hc.rb" "tests/test_httpclient.rb" "tests/test_httpclient2.rb"
"tests/test_inactivity_timeout.rb" "tests/test_io_streamer.rb"
"tests/test_ipv4.rb" "tests/test_ipv6.rb" "tests/test_iterator.rb"
"tests/test_kb.rb" "tests/test_keepalive.rb" "tests/test_line_protocol.rb"
"tests/test_ltp.rb" "tests/test_ltp2.rb" "tests/test_many_fds.rb"
"tests/test_next_tick.rb" "tests/test_object_protocol.rb" "tests/test_pause.rb"
"tests/test_pending_connect_timeout.rb" "tests/test_pool.rb"
"tests/test_process_watch.rb" "tests/test_processes.rb"
"tests/test_proxy_connection.rb" "tests/test_pure.rb" "tests/test_queue.rb"
"tests/test_resolver.rb" "tests/test_running.rb" "tests/test_sasl.rb"
"tests/test_send_file.rb" "tests/test_servers.rb"
"tests/test_shutdown_hooks.rb" "tests/test_smtpclient.rb"
"tests/test_smtpserver.rb" "tests/test_sock_opt.rb" "tests/test_spawn.rb"
"tests/test_ssl_args.rb" "tests/test_ssl_dhparam.rb"
"tests/test_ssl_ecdh_curve.rb" "tests/test_ssl_extensions.rb"
"tests/test_ssl_methods.rb" "tests/test_ssl_protocols.rb"
"tests/test_ssl_verify.rb" "tests/test_stomp.rb" "tests/test_system.rb"
"tests/test_threaded_resource.rb" "tests/test_tick_loop.rb"
"tests/test_timers.rb" "tests/test_ud.rb" "tests/test_unbind_reason.rb" -v]
/usr/share/rubygems-integration/all/gems/rake-13.0.3/exe/rake:27:in `'
Tasks: TOP => default
(See full trace by running task with --trace)
ERROR: Test "ruby2.7" failed. Exiting.
dh_auto_install: error: dh_ruby --install
/<>/ruby-eventmachine-1.3\~pre20201020-b50c135/debian/ruby-eventmachine
returned exit code 1
make[1]: *** [debian/rules:13: override_dh_auto_install] Error 25
--- End Message ---
--- Begin Message ---
Source: ruby-eventmachine
Source-Version: 1.3~pre20201020-b50c135-4
Done: Antonio Terceiro
We believe that the bug you reported is fixed in the latest version of
ruby-eventmachine, 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 995...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Antonio Terceiro (supplier of updated ruby-eventmachine
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: Tue, 12 Oct 2021 14:13:34 -0300
Source:
Bug#996263: ctop: Should this package be removed?
Package: ctop Severity: serious Version: 1.0.0-2.1 X-Debbugs-CC: czc...@debian.org Dear Debian ctop package maintainer, As discussed in https://bugs.debian.org/922061 , the current ctop software in Debian is unmaintained, incompatible with Debian 11 and later, and has a dead upstream. I believe this package should be removed from Debian to avoid confusion. I may submit a package removal request within 1 month if there's no other opinions. Also please let me know if we should choose other solutions. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#995815: marked as pending in ruby-eventmachine
Control: tag -1 pending Hello, Bug #995815 in ruby-eventmachine 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-eventmachine/-/commit/2816263a3f9f559f3d434161c7da3340b797a940 debian/ruby-tests.rake: skip tests when no ipv4 is available Closes: #995815 (this message was generated automatically) -- Greetings https://bugs.debian.org/995815
Processed: Bug#995815 marked as pending in ruby-eventmachine
Processing control commands: > tag -1 pending Bug #995815 [src:ruby-eventmachine] ruby-eventmachine FTBFS on IPV6-only buildds Added tag(s) pending. -- 995815: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995815 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996258: marked as done (FTBFS: test failure in t/06-replicated.t)
Your message dated Tue, 12 Oct 2021 17:03:39 +
with message-id
and subject line Bug#996258: fixed in libdbicx-sugar-perl 0.0200-2
has caused the Debian Bug report #996258,
regarding FTBFS: test failure in t/06-replicated.t
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.)
--
996258: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996258
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libdbicx-sugar-perl
Version: 0.0200-1
Severity: serious
Tags: ftbfs bookworm sid
Justification: fails to build from source
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
As noticed on ci.debian.net, the package's testsuite fails, and does
so also during build in a sid chroot:
DBIx::Class::Schema::catch {...} (): Unable to load storage class
DBIx::Class::Storage::DBI::Replicated: {UNKNOWN}: The following modules are
required for Replication Clone (see DBIx::Class::Optional::Dependencies for
details)
BEGIN failed--compilation aborted at
/usr/share/perl5/DBIx/Class/Storage/DBI/Replicated.pm line 7.
Compilation failed in require at /usr/share/perl5/Class/C3/Componentised.pm
line 146. at /usr/share/perl5/Class/C3/Componentised.pm line 151 at
/build/libdbicx-sugar-perl-0.0200/blib/lib/DBICx/Sugar.pm line 118
# Looks like your test exited with 2 just after 3.
t/06-replicated.t
1..8
ok 1
ok 2
ok 3 - no (unexpected) warnings (via END block)
Dubious, test returned 2 (wstat 512, 0x200)
Failed 5/8 subtests
Test Summary Report
- ---
t/06-replicated.t (Wstat: 512 Tests: 3 Failed: 0)
Non-zero exit status: 2
Parse errors: Bad plan. You planned 8 tests but ran 3.
Files=6, Tests=22, 2 wallclock secs ( 0.03 usr 0.01 sys + 1.54 cusr 0.13
csys = 1.71 CPU)
Result: FAIL
Failed 1/6 test programs. 0/22 subtests failed.
make[1]: *** [Makefile:871: test_dynamic] Error 2
Not sure which reverse build dependency changed. No upstream bug
report available yet.
Maybe libdbix-class-perl/0.082842-1?
Oh yes, tracker agrees:
https://tracker.debian.org/pkg/libdbix-class-perl
And the fix is simple: libclone-perl is needed
Cheers,
gregor, preparing an upload
-BEGIN PGP SIGNATURE-
iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmFltn5fFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgZAXRAAkT33c5pHaHSuocCYhnr0KEMyd7p2UkLvDrdD38FenzfQtF1C0jYesQ3r
64C1GSo38YwqsNC+z9TM87fPHQIP52airNnmHS7EAEWg+WCIfzTK24T5adWGAnpJ
I/tmHOZNgFE81taiJGEWVll3uF2st49D3p90dwnyb/AoW4u+f3X6snHxeHvBiqRY
U1d9sTVaVwMrABlYTaRuVagWra5xYQbuPaQGlO5KhPQ3KIWJFL9YY7FNC5MYwIzT
c4FyBhGBSgUkCxV5GwV17dlRRkinZrRXR2DToQH31779ryT20CKbHKrbhjKVQTuC
yXISxhX/0YQiaYV7nUPR8p0W9M7AN3D9oL7c+MJek8p+hLF1N0WsT2Z912veXZrh
2zmiylnaC3ZHawWy667YfdAGFrL5wkBw9GdVzAtq9ONGUAlIvz9GOxsfNOMCtilY
TJFdyWsELWAs19JT3C1kKWfnGQ5jr8TaXX4+rhtSl9VyRlNvXy9RAh/0LfDSxhXW
JYwJv45jCuvdd5Xma5lFjNhTD9ncUHqHw0rguT4criFv0nXtsf0IwJ1/kinEo+fW
FDo7+4TqUL74NThKGiuDIp9x1sAxhZv2Bvu1A6RbxoFK0/YXZbbx15yN0flGX2DC
0L5lr+9gyt+daheIQIZnnFzOx3SU2lo3AUAG7a4PzYoPOiyX6nY=
=DpEX
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: libdbicx-sugar-perl
Source-Version: 0.0200-2
Done: gregor herrmann
We believe that the bug you reported is fixed in the latest version of
libdbicx-sugar-perl, 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 996...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
gregor herrmann (supplier of updated libdbicx-sugar-perl
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 12 Oct 2021 18:45:18 +0200
Source: libdbicx-sugar-perl
Architecture: source
Version: 0.0200-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group
Changed-By: gregor herrmann
Closes: 996258
Changes:
libdbicx-sugar-perl (0.0200-2) unstable; urgency=medium
.
* Team upload.
.
[ Debian Janitor ]
* Bump debhelper dependency to >= 9, since that's what is used in
debian/compat.
* Bump debhelper from old 9 to 12.
* Set debhelper-compat version in Build-Depends.
* Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
Bug#984092: marked as done (libbpp-seq-omics: ftbfs with GCC-11)
Your message dated Tue, 12 Oct 2021 17:03:35 + with message-id and subject line Bug#984092: fixed in libbpp-seq-omics 2.4.1-7 has caused the Debian Bug report #984092, regarding libbpp-seq-omics: ftbfs with GCC-11 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.) -- 984092: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984092 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:libbpp-seq-omics Version: 2.4.1-5 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye release] 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-11/g++-11, but succeeds to build with gcc-10/g++-10. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://people.debian.org/~doko/logs/20210228/filtered/gcc11/libbpp-seq-omics_2.4.1-5_unstable_gcc11.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 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-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] +++ dpkg-gensymbolsTekV7w 2021-03-01 21:02:24.325500245 + @@ -38,6 +38,7 @@ _ZN3bpp12EdSymbolList25beforeSequenceSubstitutedERKNS_27SymbolListSubstitutionEventE@Base 2.4.1 _ZN3bpp12EdSymbolList7shuffleEv@Base 2.4.1 _ZN3bpp12EdSymbolListixEm@Base 2.4.1 + _ZN3bpp12SequenceMaskC1ERKSt6vectorIbSaIbEEb@Base 2.4.1-5 _ZN3bpp12SequenceMaskD0Ev@Base 2.4.1 _ZN3bpp13AlphabetStateD0Ev@Base 2.4.1 _ZN3bpp13AlphabetStateD1Ev@Base 2.4.1 @@ -126,8 +127,8 @@ _ZN3bpp19OutOfRangeExceptionD2Ev@Base 2.4.1 _ZN3bpp19VectorSiteContainerD0Ev@Base 2.4.1 _ZN3bpp19VectorSiteContainerD1Ev@Base 2.4.1 - _ZN3bpp20AbstractCoreSequence11setCommentsERKSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS7_EE@Base 2.4.1 - _ZN3bpp20AbstractCoreSequence7setNameERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base 2.4.1 +#MISSING: 2.4.1-5# _ZN3bpp20AbstractCoreSequence11setCommentsERKSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS7_EE@Base 2.4.1 +#MISSING: 2.4.1-5# _ZN3bpp20AbstractCoreSequence7setNameERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base 2.4.1 _ZN3bpp20BasicSequenceFeature12getAttributeERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base 2.4.1 _ZN3bpp20BasicSequenceFeature12setAttributeERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES8_@Base 2.4.1 _ZN3bpp20BasicSequenceFeature13setSequenceIdERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base 2.4.1 @@ -516,13 +517,17 @@ _ZNSt15_Sp_counted_ptrIDnLN9__gnu_cxx12_Lock_policyE2EE10_M_disposeEv@Base 2.4.1 _ZNSt16_Sp_counted_baseILN9__gnu_cxx12_Lock_policyE2EE10_M_destroyEv@Base 2.4.1 _ZNSt3mapINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEPN3bpp10BppNumberIESt4lessIS5_ESaISt4pairIKS5_S8_EEEixERSC_@Base 2.4.1 + _ZNSt3mapINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES5_St4lessIS5_ESaISt4pairIKS5_S5_EEEixEOS5_@Base 2.4.1-5 + _ZNSt3mapINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEjSt4lessIS5_ESaISt4pairIKS5_jEEEixERS9_@Base 2.4.1-5 _ZNSt5dequeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EED1Ev@Base 2.4.1 _ZNSt5dequeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EED2Ev@Base 2.4.1 _ZNSt5dequeIPN3bpp8MafBlockESaIS2_EE16_M_push_back_auxIJRKS2_EEEvDpOT_@Base 2.4.1 _ZNSt5dequeISt6vectorIbSaIbEESaIS2_EE16_M_push_back_auxIJRKS2_EEEvDpOT_@Base 2.4.1 _ZNSt5dequeISt6vectorIiSaIiEESaIS2_EE16_M_push_back_auxIJRKS2_EEEvDpOT_@Base 2.4.1 - _ZNSt5dequeIjSaIjEE16_M_push_back_auxIJjEEEvDpOT_@Base 2.4.1 -
Bug#995021: osmnx: autopkgtest regression on armhf: Restriction not respected
Hi, On 12-10-2021 10:12, Jerome BENOIT wrote: > Hello Paul, it seems that the Restriction needs-internet is not respected. All our hosts have unlimited internet access, so the restriction is currently not "meaning" anything on ci.d.n infrastructure. Hosts that have no unlimited internet access should properly call autopkgtest to skip those tests, but that doesn't apply for us. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#996160: closing 996160
close 996160 1.3~pre20201020-b50c135-3 thanks
Processed: closing 996160
Processing commands for cont...@bugs.debian.org: > close 996160 1.3~pre20201020-b50c135-3 Bug #996160 [src:ruby-eventmachine] ruby-eventmachine: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed. Marked as fixed in versions ruby-eventmachine/1.3~pre20201020-b50c135-3. Bug #996160 [src:ruby-eventmachine] ruby-eventmachine: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed. Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 996160: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996160 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#996258 marked as pending in libdbicx-sugar-perl
Processing control commands: > tag -1 pending Bug #996258 [src:libdbicx-sugar-perl] FTBFS: test failure in t/06-replicated.t Added tag(s) pending. -- 996258: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996258 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996258: marked as pending in libdbicx-sugar-perl
Control: tag -1 pending Hello, Bug #996258 in libdbicx-sugar-perl 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/perl-team/modules/packages/libdbicx-sugar-perl/-/commit/0f0ee41c31bd4c6c528e4ca8fd4359c671e247f1 Add test dependency on libclone-perl. Closes: #996258 (this message was generated automatically) -- Greetings https://bugs.debian.org/996258
Processed: bug 996258 is forwarded to https://github.com/ironcamel/DBICx-Sugar/issues/6
Processing commands for cont...@bugs.debian.org: > forwarded 996258 https://github.com/ironcamel/DBICx-Sugar/issues/6 Bug #996258 [src:libdbicx-sugar-perl] FTBFS: test failure in t/06-replicated.t Set Bug forwarded-to-address to 'https://github.com/ironcamel/DBICx-Sugar/issues/6'. > thanks Stopping processing here. Please contact me if you need assistance. -- 996258: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996258 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996258: FTBFS: test failure in t/06-replicated.t
Source: libdbicx-sugar-perl
Version: 0.0200-1
Severity: serious
Tags: ftbfs bookworm sid
Justification: fails to build from source
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
As noticed on ci.debian.net, the package's testsuite fails, and does
so also during build in a sid chroot:
DBIx::Class::Schema::catch {...} (): Unable to load storage class
DBIx::Class::Storage::DBI::Replicated: {UNKNOWN}: The following modules are
required for Replication Clone (see DBIx::Class::Optional::Dependencies for
details)
BEGIN failed--compilation aborted at
/usr/share/perl5/DBIx/Class/Storage/DBI/Replicated.pm line 7.
Compilation failed in require at /usr/share/perl5/Class/C3/Componentised.pm
line 146. at /usr/share/perl5/Class/C3/Componentised.pm line 151 at
/build/libdbicx-sugar-perl-0.0200/blib/lib/DBICx/Sugar.pm line 118
# Looks like your test exited with 2 just after 3.
t/06-replicated.t
1..8
ok 1
ok 2
ok 3 - no (unexpected) warnings (via END block)
Dubious, test returned 2 (wstat 512, 0x200)
Failed 5/8 subtests
Test Summary Report
- ---
t/06-replicated.t (Wstat: 512 Tests: 3 Failed: 0)
Non-zero exit status: 2
Parse errors: Bad plan. You planned 8 tests but ran 3.
Files=6, Tests=22, 2 wallclock secs ( 0.03 usr 0.01 sys + 1.54 cusr 0.13
csys = 1.71 CPU)
Result: FAIL
Failed 1/6 test programs. 0/22 subtests failed.
make[1]: *** [Makefile:871: test_dynamic] Error 2
Not sure which reverse build dependency changed. No upstream bug
report available yet.
Maybe libdbix-class-perl/0.082842-1?
Oh yes, tracker agrees:
https://tracker.debian.org/pkg/libdbix-class-perl
And the fix is simple: libclone-perl is needed
Cheers,
gregor, preparing an upload
-BEGIN PGP SIGNATURE-
iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmFltn5fFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgZAXRAAkT33c5pHaHSuocCYhnr0KEMyd7p2UkLvDrdD38FenzfQtF1C0jYesQ3r
64C1GSo38YwqsNC+z9TM87fPHQIP52airNnmHS7EAEWg+WCIfzTK24T5adWGAnpJ
I/tmHOZNgFE81taiJGEWVll3uF2st49D3p90dwnyb/AoW4u+f3X6snHxeHvBiqRY
U1d9sTVaVwMrABlYTaRuVagWra5xYQbuPaQGlO5KhPQ3KIWJFL9YY7FNC5MYwIzT
c4FyBhGBSgUkCxV5GwV17dlRRkinZrRXR2DToQH31779ryT20CKbHKrbhjKVQTuC
yXISxhX/0YQiaYV7nUPR8p0W9M7AN3D9oL7c+MJek8p+hLF1N0WsT2Z912veXZrh
2zmiylnaC3ZHawWy667YfdAGFrL5wkBw9GdVzAtq9ONGUAlIvz9GOxsfNOMCtilY
TJFdyWsELWAs19JT3C1kKWfnGQ5jr8TaXX4+rhtSl9VyRlNvXy9RAh/0LfDSxhXW
JYwJv45jCuvdd5Xma5lFjNhTD9ncUHqHw0rguT4criFv0nXtsf0IwJ1/kinEo+fW
FDo7+4TqUL74NThKGiuDIp9x1sAxhZv2Bvu1A6RbxoFK0/YXZbbx15yN0flGX2DC
0L5lr+9gyt+daheIQIZnnFzOx3SU2lo3AUAG7a4PzYoPOiyX6nY=
=DpEX
-END PGP SIGNATURE-
Bug#970880: [Pkg-freeipa-devel] Bug#970880: Bug#970880: Bug#970880: Bug#970880: freeipa-server: FreeIPA server installation fails with Certificate issuance failed (CA_REJECTED)
On Sun, Oct 10, 2021 at 12:58 PM Timo Aaltonen wrote: > > > > > > > Maybe the CI will finish before I can get back to my testing. > > And it did, this error is fixed now :) > > But it fails later on, so there's some work still to catch up with the > current distro, but at least this particular annoyance is resolved, so > many thanks for figuring it out! I was sure the reason was something > silly and related to the SSL stack (or maybe ciphers) but was blind to > see it. I borrowed the .deb packages from the build artifacts and tested more. You probably already have this fixed but, * /var/lib/gssproxy directory has to be created so that gssproxy can be started. I manually created the path and ran the script again. It passes the gssproxy error that the CI got stuck on, but it failed at creating the client with this error: DEBUG The ipa-client-install command failed, exception: KerberosError: No valid Negotiate header in server response 2021-10-11T09:32:49Z ERROR No valid Negotiate header in server response I've found a few posts online with errors similar to this in 2019 (one "solution" supposedly posted on RedHat's site that I don't have access to). But, I haven't figured this one out yet. Perhaps you already know how to fix this one. -Spencer
Bug#984264: marked as done (oasis3: ftbfs with GCC-11)
Your message dated Tue, 12 Oct 2021 15:34:28 + with message-id and subject line Bug#984264: fixed in oasis3 3.mct+dfsg.121022-16 has caused the Debian Bug report #984264, regarding oasis3: ftbfs with GCC-11 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.) -- 984264: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984264 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:oasis3 Version: 3.mct+dfsg.121022-15 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye release] 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-11/g++-11, but succeeds to build with gcc-10/g++-10. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://people.debian.org/~doko/logs/20210228/filtered/gcc11/oasis3_3.mct+dfsg.121022-15_unstable_gcc11.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 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-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] .. 954 |call MPI_BCAST(arr,lsize,MPI_REAL8,lpebcast,comm,ierr) | 2 Error: Type mismatch between actual argument at (1) and actual argument at (2) (LOGICAL(4)/REAL(8)). /<>//lib/psmile/src/mod_oasis_mpi.F90:548:18: 548 |call MPI_BCAST(vec,lsize,MPI_INTEGER,lpebcast,comm,ierr) | 1 .. 954 |call MPI_BCAST(arr,lsize,MPI_REAL8,lpebcast,comm,ierr) | 2 Error: Type mismatch between actual argument at (1) and actual argument at (2) (INTEGER(4)/REAL(8)). /<>//lib/psmile/src/mod_oasis_mpi.F90:430:17: 430 |call MPI_RECV(lvec,lsize,MPI_REAL8,pid,tag,comm,status,ierr) | 1 .. 508 |call MPI_RECV(array,lsize,MPI_REAL8,pid,tag,comm,status,ierr) | 2 Error: Rank mismatch between actual argument at (1) and actual argument at (2) (rank-1 and scalar) /<>//lib/psmile/src/mod_oasis_mpi.F90:391:17: 391 |call MPI_RECV(lvec,lsize,MPI_INTEGER,pid,tag,comm,status,ierr) | 1 .. 508 |call MPI_RECV(array,lsize,MPI_REAL8,pid,tag,comm,status,ierr) | 2 Error: Type mismatch between actual argument at (1) and actual argument at (2) (INTEGER(4)/REAL(8)). /<>//lib/psmile/src/mod_oasis_mpi.F90:352:17: 352 |call MPI_RECV(lvec,lsize,MPI_INTEGER,pid,tag,comm,status,ierr) | 1 .. 508 |call MPI_RECV(array,lsize,MPI_REAL8,pid,tag,comm,status,ierr) | 2 Error: Type mismatch between actual argument at (1) and actual argument at (2) (INTEGER(4)/REAL(8)). /<>//lib/psmile/src/mod_oasis_mpi.F90:237:17: 237 |call MPI_SEND(lvec,lsize,MPI_REAL8,pid,tag,comm,ierr) | 1 .. 313 |call MPI_SEND(array,lsize,MPI_REAL8,pid,tag,comm,ierr) | 2 Error: Rank mismatch between actual argument at (1) and actual argument at (2) (rank-1 and scalar) /<>//lib/psmile/src/mod_oasis_mpi.F90:199:17: 199 |call MPI_SEND(lvec,lsize,MPI_INTEGER,pid,tag,comm,ierr) | 1 .. 313 |call MPI_SEND(array,lsize,MPI_REAL8,pid,tag,comm,ierr) | 2 Error: Type mismatch between actual argument at (1) and actual argument at (2) (INTEGER(4)/REAL(8)). /<>//lib/psmile/src/mod_oasis_mpi.F90:161:17: 161 |call MPI_SEND(lvec,lsize,MPI_INTEGER,pid,tag,comm,ierr) | 1 .. 313 |call MPI_SEND(array,lsize,MPI_REAL8,pid,tag,comm,ierr) | 2 Error: Type mismatch between actual
Bug#984416: marked as done (xmltooling: ftbfs with GCC-11)
Your message dated Tue, 12 Oct 2021 15:19:04 + with message-id and subject line Bug#984222: fixed in log4shib 2.0.0-3 has caused the Debian Bug report #984222, regarding xmltooling: ftbfs with GCC-11 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.) -- 984222: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984222 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:xmltooling Version: 3.2.0-2 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye release] 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-11/g++-11, but succeeds to build with gcc-10/g++-10. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://people.debian.org/~doko/logs/20210228/filtered/gcc11/xmltooling_3.2.0-2_unstable_gcc11.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 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-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] from ../xmltooling/AbstractXMLObject.h:30, from AbstractSimpleElement.h:30, from AbstractSimpleElement.cpp:28: /usr/include/log4shib/Category.hh:115:9: error: ISO C++17 does not allow dynamic exception specifications 115 | throw(std::invalid_argument); | ^ /usr/include/log4shib/Category.hh:149:9: error: ISO C++17 does not allow dynamic exception specifications 149 | throw(std::invalid_argument); | ^ In file included from /usr/include/log4shib/Appender.hh:21, from /usr/include/log4shib/Category.hh:14, from ../xmltooling/logging.h:34, from ../xmltooling/AbstractXMLObject.h:30, from AbstractComplexElement.h:30, from AbstractComplexElement.cpp:28: /usr/include/log4shib/Priority.hh:106:9: error: ISO C++17 does not allow dynamic exception specifications 106 | throw(std::invalid_argument); | ^ In file included from /usr/include/log4shib/Appender.hh:21, from /usr/include/log4shib/Category.hh:14, from ../xmltooling/logging.h:34, from ../xmltooling/AbstractXMLObject.h:30, from AbstractAttributeExtensibleXMLObject.h:30, from AbstractAttributeExtensibleXMLObject.cpp:28: /usr/include/log4shib/Priority.hh:106:9: error: ISO C++17 does not allow dynamic exception specifications 106 | throw(std::invalid_argument); | ^ In file included from ../xmltooling/logging.h:34, from ../xmltooling/AbstractXMLObject.h:30, from AbstractComplexElement.h:30, from AbstractComplexElement.cpp:28: /usr/include/log4shib/Category.hh:115:9: error: ISO C++17 does not allow dynamic exception specifications 115 | throw(std::invalid_argument); | ^ /usr/include/log4shib/Category.hh:149:9: error: ISO C++17 does not allow dynamic exception specifications 149 | throw(std::invalid_argument); | ^ In file included from ../xmltooling/logging.h:34, from ../xmltooling/AbstractXMLObject.h:30, from AbstractAttributeExtensibleXMLObject.h:30, from AbstractAttributeExtensibleXMLObject.cpp:28: /usr/include/log4shib/Category.hh:115:9: error: ISO C++17 does not allow dynamic exception specifications 115 | throw(std::invalid_argument); | ^ /usr/include/log4shib/Category.hh:149:9: error: ISO
Bug#984329: marked as done (shibboleth-resolver: ftbfs with GCC-11)
Your message dated Tue, 12 Oct 2021 15:19:04 + with message-id and subject line Bug#984222: fixed in log4shib 2.0.0-3 has caused the Debian Bug report #984222, regarding shibboleth-resolver: ftbfs with GCC-11 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.) -- 984222: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984222 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:shibboleth-resolver Version: 3.1.0-3 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye release] 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-11/g++-11, but succeeds to build with gcc-10/g++-10. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://people.debian.org/~doko/logs/20210228/filtered/gcc11/shibboleth-resolver_3.1.0-3_unstable_gcc11.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 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-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] | ^ /usr/include/log4shib/Category.hh:149:9: error: ISO C++17 does not allow dynamic exception specifications 149 | throw(std::invalid_argument); | ^ In file included from /usr/include/log4shib/Appender.hh:21, from /usr/include/log4shib/Category.hh:14, from /usr/include/xmltooling/logging.h:34, from shibresolver/internal.h:42, from shibresolver/resolver.cpp:22: /usr/include/log4shib/Priority.hh:106:9: error: ISO C++17 does not allow dynamic exception specifications 106 | throw(std::invalid_argument); | ^ In file included from /usr/include/xmltooling/logging.h:34, from shibresolver/internal.h:42, from shibresolver/resolver.cpp:22: /usr/include/log4shib/Category.hh:115:9: error: ISO C++17 does not allow dynamic exception specifications 115 | throw(std::invalid_argument); | ^ /usr/include/log4shib/Category.hh:149:9: error: ISO C++17 does not allow dynamic exception specifications 149 | throw(std::invalid_argument); | ^ shibresolver/resolver.cpp:115:12: warning: ‘template class std::auto_ptr’ is deprecated: use 'std::unique_ptr' instead [-Wdeprecated-declarations] 115 | static auto_ptr g_lock(Mutex::create()); |^~~~ In file included from /usr/include/c++/11/memory:76, from shibresolver/internal.h:41, from shibresolver/resolver.cpp:22: /usr/include/c++/11/bits/unique_ptr.h:57:28: note: declared here 57 | template class auto_ptr; |^~~~ make[3]: *** [Makefile:600: shibresolver/libshibresolver_lite_la-resolver.lo] Error 1 make[3]: *** Waiting for unfinished jobs shibresolver/resolver.cpp:115:12: warning: ‘template class std::auto_ptr’ is deprecated: use 'std::unique_ptr' instead [-Wdeprecated-declarations] 115 | static auto_ptr g_lock(Mutex::create()); |^~~~ In file included from /usr/include/c++/11/memory:76, from /usr/include/boost/smart_ptr/scoped_ptr.hpp:22, from /usr/include/boost/scoped_ptr.hpp:13, from /usr/include/shibsp/TransactionLog.h:40, from /usr/include/shibsp/SPConfig.h:34, from shibresolver/resolver.h:28, from shibresolver/internal.h:39, from shibresolver/resolver.cpp:22: /usr/include/c++/11/bits/unique_ptr.h:57:28: note:
Bug#984327: marked as done (shibboleth-sp: ftbfs with GCC-11)
Your message dated Tue, 12 Oct 2021 15:19:04 + with message-id and subject line Bug#984222: fixed in log4shib 2.0.0-3 has caused the Debian Bug report #984222, regarding shibboleth-sp: ftbfs with GCC-11 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.) -- 984222: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984222 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:shibboleth-sp Version: 3.2.0+dfsg1-2 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye release] 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-11/g++-11, but succeeds to build with gcc-10/g++-10. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://people.debian.org/~doko/logs/20210228/filtered/gcc11/shibboleth-sp_3.2.0+dfsg1-2_unstable_gcc11.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 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-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] 149 | throw(std::invalid_argument); | ^ In file included from /usr/include/log4shib/Appender.hh:21, from /usr/include/log4shib/Category.hh:14, from /usr/include/xmltooling/logging.h:34, from ../shibsp/TransactionLog.h:33, from SPConfig.h:34, from internal.h:50, from AbstractSPRequest.cpp:27: /usr/include/log4shib/Priority.hh:106:9: error: ISO C++17 does not allow dynamic exception specifications 106 | throw(std::invalid_argument); | ^ In file included from /usr/include/xmltooling/logging.h:34, from ../shibsp/TransactionLog.h:33, from SPConfig.h:34, from internal.h:50, from AbstractSPRequest.cpp:27: /usr/include/log4shib/Category.hh:115:9: error: ISO C++17 does not allow dynamic exception specifications 115 | throw(std::invalid_argument); | ^ /usr/include/log4shib/Category.hh:149:9: error: ISO C++17 does not allow dynamic exception specifications 149 | throw(std::invalid_argument); | ^ In file included from /usr/include/log4shib/Appender.hh:21, from /usr/include/log4shib/Category.hh:14, from /usr/include/xmltooling/logging.h:34, from ../shibsp/TransactionLog.h:33, from SPConfig.h:34, from internal.h:50, from ServiceProvider.cpp:27: /usr/include/log4shib/Priority.hh:106:9: error: ISO C++17 does not allow dynamic exception specifications 106 | throw(std::invalid_argument); | ^ In file included from /usr/include/xmltooling/logging.h:34, from ../shibsp/TransactionLog.h:33, from SPConfig.h:34, from internal.h:50, from ServiceProvider.cpp:27: /usr/include/log4shib/Category.hh:115:9: error: ISO C++17 does not allow dynamic exception specifications 115 | throw(std::invalid_argument); | ^ /usr/include/log4shib/Category.hh:149:9: error: ISO C++17 does not allow dynamic exception specifications 149 | throw(std::invalid_argument); | ^ Application.cpp: In member function ‘virtual void shibsp::Application::limitRedirect(const xmltooling::GenericRequest&, const char*) const’: Application.cpp:174:55: warning: unused parameter ‘request’ [-Wunused-parameter] 174 | void Application::limitRedirect(const
Bug#984241: marked as done (moonshot-gss-eap: ftbfs with GCC-11)
Your message dated Tue, 12 Oct 2021 15:19:04 + with message-id and subject line Bug#984222: fixed in log4shib 2.0.0-3 has caused the Debian Bug report #984222, regarding moonshot-gss-eap: ftbfs with GCC-11 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.) -- 984222: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984222 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:moonshot-gss-eap Version: 1.0.1-6 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye release] 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-11/g++-11, but succeeds to build with gcc-10/g++-10. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://people.debian.org/~doko/logs/20210228/filtered/gcc11/moonshot-gss-eap_1.0.1-6_unstable_gcc11.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 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-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -DBUILD_GSSEAP_LIB -DSYSCONFDIR=\"/etc\" -DDATAROOTDIR=\"/usr/share\" -Wdate-time -D_FORTIFY_SOURCE=2 -Werror -Wall -Wunused-parameter -isystem /usr/include/mit-krb5 -I/usr/include -DGSSEAP_ENABLE_ACCEPTOR -I./../libeap/src -I./../libeap/src/common -I./../libeap/src/eap_common -I./../libeap/src/utils -DEAP_TLS -DEAP_PEAP -DEAP_TTLS -DEAP_MD5 -DEAP_MSCHAPv2 -DEAP_GTC -DEAP_OTP -DEAP_LEAP -DEAP_PSK -DEAP_PAX -DEAP_SAKE -DEAP_GPSK -DEAP_GPSK_SHA256 -DEAP_SERVER_IDENTITY -DEAP_SERVER_TLS -DEAP_SERVER_PEAP -DEAP_SERVER_TTLS -DEAP_SERVER_MD5 -DEAP_SERVER_MSCHAPV2 -DEAP_SERVER_GTC -DEAP_SERVER_PSK -DEAP_SERVER_PAX -DEAP_SERVER_SAKE -DEAP_SERVER_GPSK -DEAP_SERVER_GPSK_SHA256 -DIEEE8021X_EAPOL -I/usr/include -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wno-error=deprecated -Wno-error=deprecated-declarations -c -o mech_eap_la-verify_mic.lo `test -f 'verify_m ic.c' || echo './'`verify_mic.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -DBUILD_GSSEAP_LIB -DSYSCONFDIR=\"/etc\" -DDATAROOTDIR=\"/usr/share\" -Wdate-time -D_FORTIFY_SOURCE=2 -Werror -Wall -Wunused-parameter -isystem /usr/include/mit-krb5 -I/usr/include -DGSSEAP_ENABLE_ACCEPTOR -I./../libeap/src -I./../libeap/src/common -I./../libeap/src/eap_common -I./../libeap/src/utils -DEAP_TLS -DEAP_PEAP -DEAP_TTLS -DEAP_MD5 -DEAP_MSCHAPv2 -DEAP_GTC -DEAP_OTP -DEAP_LEAP -DEAP_PSK -DEAP_PAX -DEAP_SAKE -DEAP_GPSK -DEAP_GPSK_SHA256 -DEAP_SERVER_IDENTITY -DEAP_SERVER_TLS -DEAP_SERVER_PEAP -DEAP_SERVER_TTLS -DEAP_SERVER_MD5 -DEAP_SERVER_MSCHAPV2 -DEAP_SERVER_GTC -DEAP_SERVER_PSK -DEAP_SERVER_PAX -DEAP_SERVER_SAKE -DEAP_SERVER_GPSK -DEAP_SERVER_GPSK_SHA256 -DIEEE8021X_EAPOL -I/usr/include -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wno-error=deprecated -Wno-error=deprecated-declarations -c verify_mic.c -fPIC -DPIC -o .libs/mech_eap_la-verify_mic.o /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -DBUILD_GSSEAP_LIB -DSYSCONFDIR=\"/etc\" -DDATAROOTDIR=\"/usr/share\" -Wdate-time -D_FORTIFY_SOURCE=2 -Werror -Wall -Wunused-parameter -isystem /usr/include/mit-krb5 -I/usr/include -DGSSEAP_ENABLE_ACCEPTOR -I./../libeap/src -I./../libeap/src/common -I./../libeap/src/eap_common -I./../libeap/src/utils -DEAP_TLS -DEAP_PEAP -DEAP_TTLS -DEAP_MD5 -DEAP_MSCHAPv2 -DEAP_GTC -DEAP_OTP -DEAP_LEAP -DEAP_PSK -DEAP_PAX -DEAP_SAKE -DEAP_GPSK -DEAP_GPSK_SHA256 -DEAP_SERVER_IDENTITY
Bug#984277: marked as done (opensaml: ftbfs with GCC-11)
Your message dated Tue, 12 Oct 2021 15:19:04 + with message-id and subject line Bug#984222: fixed in log4shib 2.0.0-3 has caused the Debian Bug report #984222, regarding opensaml: ftbfs with GCC-11 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.) -- 984222: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984222 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:opensaml Version: 3.2.0-2 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye release] 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-11/g++-11, but succeeds to build with gcc-10/g++-10. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://people.debian.org/~doko/logs/20210228/filtered/gcc11/opensaml_3.2.0-2_unstable_gcc11.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 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-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] from /usr/include/xmltooling/logging.h:34, from SAMLConfig.cpp:57: /usr/include/log4shib/Priority.hh:106:9: error: ISO C++17 does not allow dynamic exception specifications 106 | throw(std::invalid_argument); | ^ In file included from /usr/include/xmltooling/logging.h:34, from SAMLConfig.cpp:57: /usr/include/log4shib/Category.hh:115:9: error: ISO C++17 does not allow dynamic exception specifications 115 | throw(std::invalid_argument); | ^ /usr/include/log4shib/Category.hh:149:9: error: ISO C++17 does not allow dynamic exception specifications 149 | throw(std::invalid_argument); | ^ make[3]: *** [Makefile:1320: binding/impl/libsaml_la-ClientCertAuthRule.lo] Error 1 make[3]: *** Waiting for unfinished jobs make[3]: *** [Makefile:1313: binding/impl/libsaml_la-ArtifactMap.lo] Error 1 SAMLConfig.cpp: In function ‘void opensaml::annotateException(xmltooling::XMLToolingException*, const opensaml::saml2md::RoleDescriptor*, const opensaml::Status*, bool)’: SAMLConfig.cpp:357:90: warning: ‘this’ pointer is null [-Wnonnull] 357 | auto_ptr_char id(dynamic_cast(role->getParent())->getEntityID()); | ^ In file included from base.h:31, from internal.h:45, from SAMLConfig.cpp:27: saml2/metadata/Metadata.h:398:13: note: in a call to non-static member function ‘virtual const XMLCh* opensaml::saml2md::EntityDescriptor::getEntityID() const’ 398 | DECL_STRING_ATTRIB(EntityID,ENTITYID); | ^~ In file included from /usr/include/log4shib/Appender.hh:21, from /usr/include/log4shib/Category.hh:14, from /usr/include/xmltooling/logging.h:34, from /usr/include/xmltooling/AbstractXMLObject.h:30, from /usr/include/xmltooling/AbstractAttributeExtensibleXMLObject.h:30, from /usr/include/xmltooling/impl/AnyElement.h:31, from binding/impl/MessageDecoder.cpp:34: /usr/include/log4shib/Priority.hh:106:9: error: ISO C++17 does not allow dynamic exception specifications 106 | throw(std::invalid_argument); | ^ In file included from /usr/include/xmltooling/logging.h:34, from /usr/include/xmltooling/AbstractXMLObject.h:30, from /usr/include/xmltooling/AbstractAttributeExtensibleXMLObject.h:30,
Bug#984222: marked as done (log4shib: ftbfs with GCC-11)
Your message dated Tue, 12 Oct 2021 15:19:04 + with message-id and subject line Bug#984222: fixed in log4shib 2.0.0-3 has caused the Debian Bug report #984222, regarding log4shib: ftbfs with GCC-11 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.) -- 984222: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984222 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:log4shib Version: 2.0.0-2 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye release] 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-11/g++-11, but succeeds to build with gcc-10/g++-10. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://people.debian.org/~doko/logs/20210228/filtered/gcc11/log4shib_2.0.0-2_unstable_gcc11.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 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-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] make[5]: Entering directory '/<>/doc/html' make[5]: Nothing to be done for 'html'. make[5]: Leaving directory '/<>/doc/html' make[5]: Entering directory '/<>/doc' make[5]: Nothing to be done for 'html-am'. make[5]: Leaving directory '/<>/doc' /usr/bin/doxygen warning: Tag 'PERL_PATH' at line 56 of file 'Doxyfile' has become obsolete. To avoid this warning please remove this line from your configuration file or upgrade it using "doxygen -u" make[4]: Leaving directory '/<>/doc' make[3]: Leaving directory '/<>/doc' make[2]: Leaving directory '/<>' make[1]: Leaving directory '/<>' dh_auto_build -Nliblog4shib-doc make -j4 make[1]: Entering directory '/<>' Making all in src make[2]: Entering directory '/<>/src' /bin/bash ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I../include -I../include -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -Wall -W -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o Appender.lo Appender.cpp /bin/bash ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I../include -I../include -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -Wall -W -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o AppenderSkeleton.lo AppenderSkeleton.cpp /bin/bash ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I../include -I../include -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -Wall -W -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o LayoutAppender.lo LayoutAppender.cpp /bin/bash ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I../include -I../include -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -Wall -W -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o FileAppender.lo FileAppender.cpp libtool: compile: g++ -DHAVE_CONFIG_H -I. -I../include -I../include -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -Wall -W -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c LayoutAppender.cpp -fPIC -DPIC -o .libs/LayoutAppender.o libtool: compile: g++ -DHAVE_CONFIG_H -I. -I../include -I../include -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -Wall -W -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c Appender.cpp -fPIC -DPIC -o .libs/Appender.o libtool: compile: g++ -DHAVE_CONFIG_H -I. -I../include -I../include -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -Wall -W -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
Processed: bug 994736 is forwarded to https://github.com/leto/math--gsl/issues/243
Processing commands for cont...@bugs.debian.org: > forwarded 994736 https://github.com/leto/math--gsl/issues/243 Bug #994736 [src:libmath-gsl-perl] libmath-gsl-perl: FTBFS on several architectures: undefined symbol: gsl_matrix_char_norm1 Set Bug forwarded-to-address to 'https://github.com/leto/math--gsl/issues/243'. > thanks Stopping processing here. Please contact me if you need assistance. -- 994736: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994736 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996251: marked as done (libdbd-pg-perl: FTBFS with postgresql 14: test failures)
Your message dated Tue, 12 Oct 2021 15:04:55 + with message-id and subject line Bug#996251: fixed in libdbd-pg-perl 3.15.0-2 has caused the Debian Bug report #996251, regarding libdbd-pg-perl: FTBFS with postgresql 14: 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.) -- 996251: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996251 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libdbd-pg-perl Version: 3.14.2-1 Severity: serious Tags: ftbfs upstream fixed-upstream Justification: fails to build from source (but built successfully in the past) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 As seen on ci.debian.net, libdbd-pg-perl's test suite fails against PostgreSQL 14: # Failed test 'Correct stats output for dbd_pg_test1' # at t/03dbmethod.t line 1211. # Structures begin differing at: # $got->[3][10] = '-1' # $expected->[3][10] = '0' # Failed test 'Correct stats output for dbd_pg_test2' # at t/03dbmethod.t line 1216. # Structures begin differing at: # $got->[6][10] = '-1' # $expected->[6][10] = '0' # Failed test 'Correct stats output for dbd_pg_test3' # at t/03dbmethod.t line 1223. # Structures begin differing at: # $got->[6][10] = '-1' # $expected->[6][10] = '0' # Failed test 'Correct stats output for dbd_pg_test1' # at t/03dbmethod.t line 1240. # Structures begin differing at: # $got->[3][10] = '-1' # $expected->[3][10] = '0' # Failed test 'Correct stats output for dbd_pg_test3' # at t/03dbmethod.t line 1245. # Structures begin differing at: # $got->[6][10] = '-1' # $expected->[6][10] = '0' # Failed test 'Correct stats output for dbd_pg_test3' # at t/03dbmethod.t line 1251. # Structures begin differing at: # $got->[6][10] = '-1' # $expected->[6][10] = '0' # Looks like you failed 6 tests of 646. t/03dbmethod.t . Luckily 3.15.0-1, already in experimantal, fixes the issue. Cheers, gregor, preparing an upload to unstable. -BEGIN PGP SIGNATURE- iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmFlnq1fFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ qgZbXg//blgFyv4YGT43OqaGt0zmgurVNN2H0zXm9F0X3zij3RYoKvutFOxb4qjz NnceAXMQxkZpq5R/bEqBWvDpA/Zd+Sx2xSOoxtUsF1DfxFrKMUnZhYcN/VO67EHz RmMtTdaDzLzVt6URM7Sj92wmIRRKC//yb+5kZRrHNgR0aqftUDpf5ZSbUbkBSaze Z4IL5ugJX9lK12ioY3UUAISBsHYRVDz2Ba8idQi8+2sLFEL08htYtls5Qm9z3d9q /JRo7KTDi7AKeyCd9ikk9e9XOvPfXWEPwd8vPqRAmKST4GTPFGHk+nglscZyYep0 evk6TYQOL+5TWtHiAl96faCpmEFrgC7XBz8c+/tA2mflfarSmh+jx2p0mjdDKf08 Vk4geaTqbXokkOZMAOpTBtSydlDtMBjRi+x5+ALqGk7IIqayLje+80G0k99f2Ne6 5OPBRtbe1uc4T1yxg/pLMR76/jvNuN8zxJJ0pkdSV1aP/Qdj4Lj4ocAbeYGxgMaO SxUuCf2NafQT/esoO9VfOPX4i7vQXD3W0YLmCnslTgaYswbhfq9tjA4y5qpj04/3 8O8ZWVTbF5kClxNVsnNYWrJj1l1gL60w+PjoEhIaitk8EjwQ39kFD+eUf81h3ucj SBudTmVVl1oiEuQsTB5DHeAYBm/lcl5tyq7Eg00c3NyWfHDJC/A= =Y+QW -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Source: libdbd-pg-perl Source-Version: 3.15.0-2 Done: gregor herrmann We believe that the bug you reported is fixed in the latest version of libdbd-pg-perl, 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 996...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. gregor herrmann (supplier of updated libdbd-pg-perl package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 12 Oct 2021 16:48:08 +0200 Source: libdbd-pg-perl Architecture: source Version: 3.15.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Perl Group Changed-By: gregor herrmann Closes: 996251 Changes: libdbd-pg-perl (3.15.0-2) unstable; urgency=medium . [ Debian Janitor ] * Update standards version to 4.5.1, no changes needed. * Apply multi-arch hints. + libdbd-pg-perl: Add Multi-Arch: same. . [ gregor herrmann ] * Update debian/upstream/metadata. * Update years of packaging copyright. * Declare compliance with Debian Policy 4.6.0. * Upload to unstable. Fixes "FTBFS with postgresql 14: test failures"
Bug#984336: marked as done (skycat: ftbfs with GCC-11)
Your message dated Tue, 12 Oct 2021 15:05:51 + with message-id and subject line Bug#984336: fixed in skycat 3.1.2+starlink1~b+dfsg-6 has caused the Debian Bug report #984336, regarding skycat: ftbfs with GCC-11 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.) -- 984336: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984336 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:skycat Version: 3.1.2+starlink1~b+dfsg-5 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye release] 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-11/g++-11, but succeeds to build with gcc-10/g++-10. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://people.debian.org/~doko/logs/20210228/filtered/gcc11/skycat_3.1.2+starlink1~b+dfsg-5_unstable_gcc11.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 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-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] 79 | return ""; |^~ make[2]: *** [Makefile:328: BiasData.o] Error 1 make[2]: Leaving directory '/<>/rtd' + exit 1 + cd cat + make all make[2]: Entering directory '/<>/cat' g++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -funsigned-char -DPACKAGE_NAME=\"cat\" -DPACKAGE_TARNAME=\"cat\" -DPACKAGE_VERSION=\"4.1.0\" -DPACKAGE_STRING=\"cat\ 4.1.0\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_LIMITS_H=1 -DHAVE_SYS_PARAM_H=1 -DUSE_COMPAT_CONST=1 -DUSE_THREAD_ALLOC=1 -D_REENTRANT=1 -D_THREAD_SAFE=1 -DTCL_THREADS=1 -D_LARGEFILE64_SOURCE=1 -DTCL_WIDE_INT_IS_LONG=1 -DUSE_TCL_STUBS=1 -DUSE_TK_STUBS=1 -I./generic -I./bitmaps -I./../astrotcl/generic -I./../astrotcl/cfitsio -I./../astrotcl/libwcs -I./../tclutil/generic -I"/usr/include/tcl8.6" -I"/usr/include/tcl8.6" -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefi x-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -funsigned-char -O2 -fPIC -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c `echo ./generic/AstroCatalog.C` -o AstroCatalog.o g++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -funsigned-char -DPACKAGE_NAME=\"cat\" -DPACKAGE_TARNAME=\"cat\" -DPACKAGE_VERSION=\"4.1.0\" -DPACKAGE_STRING=\"cat\ 4.1.0\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_LIMITS_H=1 -DHAVE_SYS_PARAM_H=1 -DUSE_COMPAT_CONST=1 -DUSE_THREAD_ALLOC=1 -D_REENTRANT=1 -D_THREAD_SAFE=1 -DTCL_THREADS=1 -D_LARGEFILE64_SOURCE=1 -DTCL_WIDE_INT_IS_LONG=1 -DUSE_TCL_STUBS=1 -DUSE_TK_STUBS=1 -I./generic -I./bitmaps -I./../astrotcl/generic -I./../astrotcl/cfitsio -I./../astrotcl/libwcs -I./../tclutil/generic -I"/usr/include/tcl8.6" -I"/usr/include/tcl8.6" -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefi x-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -funsigned-char -O2 -fPIC -g -O2 -ffile-prefix-map=/<>=.
Processed: tagging 996251
Processing commands for cont...@bugs.debian.org: > tags 996251 + bookworm sid Bug #996251 [src:libdbd-pg-perl] libdbd-pg-perl: FTBFS with postgresql 14: test failures Added tag(s) bookworm and sid. > thanks Stopping processing here. Please contact me if you need assistance. -- 996251: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996251 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: fixed 996251 in 3.15.0-1
Processing commands for cont...@bugs.debian.org: > fixed 996251 3.15.0-1 Bug #996251 [src:libdbd-pg-perl] libdbd-pg-perl: FTBFS with postgresql 14: test failures Marked as fixed in versions libdbd-pg-perl/3.15.0-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 996251: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996251 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: notfound 994370 in 1.2.2-2
Processing commands for cont...@bugs.debian.org:
> notfound 994370 1.2.2-2
Bug #994370 {Done: Gordon Ball }
[src:python-setproctitle] python-setproctitle: Removal of the python3-*-dbg
packages in sid/bookworm
No longer marked as found in versions python-setproctitle/1.2.2-2.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
994370: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994370
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
