Processed: buster-pu, bullseye-pu
Processing commands for cont...@bugs.debian.org: > tags 1000341 -moreinfo Bug #1000341 [release.debian.org] buster-pu: package mariadb-10.3 10.3.32-0+deb10u1 Removed tag(s) moreinfo. > tags 1000340 -moreinfo Bug #1000340 [src:bibtexconv] bibtexconv: autopkgtest failure: "Tests" field is empty Ignoring request to alter tags of bug #1000340 to the same tags previously set > End of message, stopping processing here. Please contact me if you need assistance. -- 1000340: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000340 1000341: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000341 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996378: marked as done (ruby-rspec-retry: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Failure/Error:)
Your message dated Sat, 27 Nov 2021 05:03:41 +
with message-id
and subject line Bug#996378: fixed in ruby-rspec-retry 0.6.2-2
has caused the Debian Bug report #996378,
regarding ruby-rspec-retry: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed:
Failure/Error:
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.)
--
996378: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996378
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-rspec-retry
Version: 0.6.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-rspec-retry 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(example_group.class_variable_get(:@@results)).to eq({
> 'without retry option' => [true, 1],
> 'with retry option' => [false, 3]
>})
>
> NameError:
>uninitialized class variable @@results in
> RSpec::ExampleGroups::Anonymous
> # ./spec/lib/rspec/retry_spec.rb:359:in `class_variable_get'
> # ./spec/lib/rspec/retry_spec.rb:359:in `block (3 levels) in (required)>'
> # ./spec/spec_helper.rb:13:in `block (3 levels) in '
> # ./spec/spec_helper.rb:11:in `block (2 levels) in '
> # ./lib/rspec/retry.rb:124:in `block in run'
> # ./lib/rspec/retry.rb:110:in `loop'
> # ./lib/rspec/retry.rb:110:in `run'
> # ./lib/rspec_ext/rspec_ext.rb:12:in `run_with_retry'
> # ./lib/rspec/retry.rb:37:in `block (2 levels) in setup'
>
> Finished in 0.259 seconds (files took 0.35161 seconds to load)
> 29 examples, 3 failures, 5 pending, 1 error occurred outside of examples
>
> Failed examples:
>
> rspec ./spec/lib/rspec/retry_spec.rb:70 # RSpec::Retry with retry option with
> :retry => 0 should still run once
> rspec ./spec/lib/rspec/retry_spec.rb:74 # RSpec::Retry with retry option with
> :retry => 0 should run have run once
> rspec ./spec/lib/rspec/retry_spec.rb:357 # RSpec::Retry
> Example::Procsy#attempts should be exposed
>
> /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-rspec-retry/ruby-rspec-retry_0.6.2-1+rebuild1633394189_amd64.build.txt
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ruby-rspec-retry
Source-Version: 0.6.2-2
Done: Daniel Leidert
We believe that the bug you reported is fixed in the latest version of
ruby-rspec-retry, 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.
Daniel Leidert (supplier of updated ruby-rspec-retry
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 27 Nov 2021 05:39:26 +0100
Source: ruby-rspec-retry
Architecture: source
Version: 0.6.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team
Changed-By: Daniel Leidert
Closes: 996378
Changes:
ruby-rspec-retry (0.6.2-2) unstable; urgency=medium
.
* Team upload.
.
[ Debian Janitor ]
* Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
Repository-Browse.
.
[ Daniel Leidert ]
* d/control: Add Testsuite and Rules-Requires-Root fields.
(Build-Depends): Bump debhelper to version 13.
(Standards-Version): Bump to 4.6.0.
(Depends): Remove interpreters and use ${ruby:Depends}.
* d/copyright: Add Upstream-Contact field.
(Copyright): Add team.
* d/rules: Use gem installation layout and install upstream changelog.
* d/watch: Bump to version 4.
* d/patches/0002-Workaround-class-variabl
Bug#996378: marked as pending in ruby-rspec-retry
Control: tag -1 pending Hello, Bug #996378 in ruby-rspec-retry 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-rspec-retry/-/commit/91eba55133161295ec87ba1739456cc95ff84c7f Add patch to workaround class variables in tests with Ruby 3.0 * d/patches/0002-Workaround-class-variable-issues.patch: Add patch. - Work around the usage of class variables in tests (closes: #996378). * d/patches/series: Enable new patch. (this message was generated automatically) -- Greetings https://bugs.debian.org/996378
Processed: Bug#996378 marked as pending in ruby-rspec-retry
Processing control commands: > tag -1 pending Bug #996378 [src:ruby-rspec-retry] ruby-rspec-retry: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Failure/Error: Added tag(s) pending. -- 996378: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996378 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996527: marked as done (sup-mail: FTBFS: ERROR: Test "ruby2.7" failed: NameError: uninitialized constant ActiveSupport)
Your message dated Sat, 27 Nov 2021 03:34:36 + with message-id and subject line Bug#996527: fixed in sup-mail 1.0-4 has caused the Debian Bug report #996527, regarding sup-mail: FTBFS: ERROR: Test "ruby2.7" failed: NameError: uninitialized constant ActiveSupport 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.) -- 996527: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996527 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sup-mail Version: 1.0-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, sup-mail was found to fail to build in that situation. This seems unrelated to ruby3.0, since the ruby2.7 tests already fail. Relevant part (hopefully): > /usr/bin/ruby2.7 /usr/bin/gem2deb-test-runner > > ┌──┐ > │ Run tests for ruby2.7 from debian/ruby-tests.rb > │ > └──┘ > > RUBYLIB=/<>/debian/sup-mail/usr/lib/ruby/vendor_ruby:. > GEM_PATH=/<>/debian/sup-mail/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/2.7.0:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0 > ruby2.7 debian/ruby-tests.rb > tput: No value for $TERM and no -T specified > tput: No value for $TERM and no -T specified > Some YAML tests are skipped on Ruby 2.1.0 and newer. > Run options: --seed 8439 > > # Running: > > [2021-10-05 02:07:09 +] WARNING: URI.escape is obsolete > [2021-10-05 02:07:09 +] WARNING: found invalid date in potential mbox > split line, not splitting: "From sea to shining sea\n" > [2021-10-05 02:07:09 +] WARNING: found invalid date in potential mbox > split line, not splitting: "From b...@bob.com I get only spam.\n" > ..[2021-10-05 02:07:09 +] WARNING: URI.escape is obsolete > .[2021-10-05 02:07:09 +] WARNING: DEPRECATED: Use assert_nil if expecting > nil from /<>/test/test_header_parsing.rb:72. This will fail in > Minitest 6. > E/usr/bin/which: this version of `which' is deprecated; use `command -v' > in scripts instead. > [2021-10-05 02:07:09 +] WARNING: No crypto set up, crypto will not be > tested. Reason: ["Environment variable 'GPG_AGENT_INFO' not set, is gpg-agent > running?", "If gpg-agent is running, try $ export `cat ~/.gpg-agent-info`"] > ./usr/bin/which: this version of `which' is deprecated; use `command -v' in > scripts instead. > [2021-10-05 02:07:09 +] WARNING: No crypto set up, crypto will not be > tested. Reason: ["Environment variable 'GPG_AGENT_INFO' not set, is gpg-agent > running?", "If gpg-agent is running, try $ export `cat ~/.gpg-agent-info`"] > ./usr/bin/which: this version of `which' is deprecated; use `command -v' in > scripts instead. > [2021-10-05 02:07:09 +] WARNING: No crypto set up, crypto will not be > tested. Reason: ["Environment variable 'GPG_AGENT_INFO' not set, is gpg-agent > running?", "If gpg-agent is running, try $ export `cat ~/.gpg-agent-info`"] > ./usr/bin/which: this version of `which' is deprecated; use `command -v' in > scripts instead. > [2021-10-05 02:07:09 +] WARNING: No crypto set up, crypto will not be > tested. Reason: ["Environment variable 'GPG_AGENT_INFO' not set, is gpg-agent > running?", "If gpg-agent is running, try $ export `cat ~/.gpg-agent-info`"] > ./usr/bin/which: this version of `which' is deprecated; use `command -v' in > scripts instead. > [2021-10-05 02:07:09 +] WARNING: No crypto set up, crypto will not be > tested. Reason: ["Environment variable 'GPG_AGENT_INFO' not set, is gpg-agent > running?", "If gpg-agent is running, try $ export `cat ~/.gpg-agent-info`"] > ./usr/bin/which: this version of `which' is deprecated; use `command -v' in > scripts instead. > [2021-10-05 02:07:09 +] WARNING: No crypto set up, crypto will not be > tested. Reason: ["Environment variable 'GPG_AGENT_INFO' not set, is gpg-agent > running?", "If gpg-agent is running, try $ export `cat ~/.gpg-agent-info`"] > .[2021-10-05 02:07:09 +] WARNING: problem reading message > sup-faked-df001467cbd7d1c987812838111e7731 > [2021-10-05 02:07:09 +] WARNING: Message is in sup-test://test_messag
Bug#1000360: marked as done (segyio: FTBFS with Python 3.10)
Your message dated Sat, 27 Nov 2021 03:34:30 + with message-id and subject line Bug#1000360: fixed in segyio 1.8.3-1.1 has caused the Debian Bug report #1000360, regarding segyio: FTBFS with Python 3.10 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1000360: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000360 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: segyio Version: 1.8.3-1 Severity: serious Tags: upstream patch Justification: FTBFS FTBFS with Python 3.10: Tests fail with: E AttributeError: module 'collections' has no attribute 'Mapping' See: https://buildd.debian.org/status/fetch.php?pkg=segyio&arch=amd64&ver=1.8.3-1%2Bb5&stamp=1637491602&raw=0 Looks like upstream fixed this issue years ago, updating to a new upstream version would probably be good. But, in the meantime, we can probably patch it. SR --- End Message --- --- Begin Message --- Source: segyio Source-Version: 1.8.3-1.1 Done: Stefano Rivera We believe that the bug you reported is fixed in the latest version of segyio, 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 1000...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stefano Rivera (supplier of updated segyio package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 21 Nov 2021 22:51:13 -0400 Source: segyio Architecture: source Version: 1.8.3-1.1 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Stefano Rivera Closes: 1000360 Changes: segyio (1.8.3-1.1) unstable; urgency=medium . * Non-maintainer upload. * Python 3.10 support. (Closes: #1000360) - Patch: Import from collections.abc. - Patch: PY_SSIZE_T_CLEAN. Checksums-Sha1: f90c4c2abd77e93d2caf159ae07a1bd8ef582c19 1698 segyio_1.8.3-1.1.dsc cf04320db9be92e76889c2208ddfc2da2c610717 7624 segyio_1.8.3-1.1.debian.tar.xz 554fbaef3278e25fc2ffb8cca93efe543de445e6 6482 segyio_1.8.3-1.1_source.buildinfo Checksums-Sha256: e031d24866041fcabbd3a77edfddb93f31d77493fcb7440f0ba5463550cdcc24 1698 segyio_1.8.3-1.1.dsc 90988f1b415b205887033e773a5ed9efe9a4dbe15436e8890159cffcd77b4ddb 7624 segyio_1.8.3-1.1.debian.tar.xz fd39565676aed86c2959f0f32a9d791836f823e1e84bb474c385edc71636067b 6482 segyio_1.8.3-1.1_source.buildinfo Files: b34248ccc2d19709a4d5c17f7dd7be2b 1698 science optional segyio_1.8.3-1.1.dsc 55ec80b020c65e7c5dbbeedf6197f30b 7624 science optional segyio_1.8.3-1.1.debian.tar.xz 362d88212b16c6c8be820eae5e50872b 6482 science optional segyio_1.8.3-1.1_source.buildinfo -BEGIN PGP SIGNATURE- iIoEARYKADIWIQTumtb5BSD6EfafSCRHew2wJjpU2AUCYZsGKRQcc3RlZmFub3JA ZGViaWFuLm9yZwAKCRBHew2wJjpU2F+YAQDA4Th0CnxOUdox2HADqEXlCxnDE42S rEKQgJLZVT3f4wEAwRg/loiAoJEFk+6JCNAJMZLj5uCUemp0yMfPb+HoRAk= =KAFI -END PGP SIGNATURE End Message ---
Bug#996379: marked as done (ruby-rspec: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Failure/Error: DEFAULT_FAILURE_NOTIFIER = lambda { |failure, _opts| raise failure })
Your message dated Sat, 27 Nov 2021 04:29:12 +0100
with message-id <5bff162e3757627ba99b19e9d595ecf8e6fe4583.ca...@debian.org>
and subject line Fixed with the latest upload of ruby-rspec/3.10.0c1e1m2s3-1
has caused the Debian Bug report #996379,
regarding ruby-rspec: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed:
Failure/Error: DEFAULT_FAILURE_NOTIFIER = lambda { |failure, _opts| raise
failure }
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
996379: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996379
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-rspec
Version: 3.9.0c2e2m1s3-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-rspec 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: DEFAULT_FAILURE_NOTIFIER = lambda { |failure, _opts|
> raise failure }
>expected /Warnings were generated:/ but nothing was raised
> # ./spec/rspec/support/spec/stderr_splitter_spec.rb:92:in `block (2
> levels) in '
> # ./spec/rspec/support/spec/stderr_splitter_spec.rb:19:in `block (2
> levels) in '
>
> Finished in 1.08 seconds (files took 0.2783 seconds to load)
> 538 examples, 1 failure, 1 pending
>
> Failed examples:
>
> rspec ./spec/rspec/support/spec/stderr_splitter_spec.rb:90 #
> RSpec::Support::StdErrSplitter will fail an example which generates a warning
>
> Randomized with seed 13098
>
> cd -
> Failed: rspec-support
> ERROR: Test "ruby3.0" failed:
The full build log is available at
https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-rspec/ruby-rspec_3.9.0c2e2m1s3-2+rebuild1633393939_amd64.build.txt
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ruby-rspec
Source-Version: 3.10.0c1e1m2s3-1
Done: Antonio Terceiro
I cannot reproduce this build failure with the latest upload of ruby-rspec. I
therefor assume it has been closed by Antonio's upload.
Regards, Daniel
--
Regards,
Daniel Leidert | https://www.wgdd.de/
GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D
GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78
https://www.fiverr.com/dleidert
https://www.patreon.com/join/dleidert
signature.asc
Description: This is a digitally signed message part
--- End Message ---
Bug#996527: marked as pending in sup-mail
Control: tag -1 pending Hello, Bug #996527 in sup-mail 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/sup-mail/-/commit/9a12bf6ed2976e5dacf68f1adc7d7eb0992472d3 Add patch for Ruby 3.0 compatibility * d/patches/0005-avoid-URI.encode-and-URI.decode.patch: Add patch. - Replace methods not available in Ruby 3.0 (closes: #996527). * d/patches/series: Enable new patch. (this message was generated automatically) -- Greetings https://bugs.debian.org/996527
Processed: Bug#996527 marked as pending in sup-mail
Processing control commands: > tag -1 pending Bug #996527 [src:sup-mail] sup-mail: FTBFS: ERROR: Test "ruby2.7" failed: NameError: uninitialized constant ActiveSupport Added tag(s) pending. -- 996527: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996527 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000680: python3-aiohttp: fails to import, "TypeError: function() argument 'code' must be code, not str"
Package: python3-aiohttp Version: 3.7.4-2+b1 Severity: grave X-Debbugs-Cc: mo...@debian.org Control: affects -1 uvloop Hello, simply importing aiohttp results in an error: root@zion:/# python3.9 -c "import aiohttp" Traceback (most recent call last): File "", line 1, in File "/usr/lib/python3/dist-packages/aiohttp/__init__.py", line 6, in from .client import ( File "/usr/lib/python3/dist-packages/aiohttp/client.py", line 35, in from . import hdrs, http, payload File "/usr/lib/python3/dist-packages/aiohttp/http.py", line 7, in from .http_parser import ( File "/usr/lib/python3/dist-packages/aiohttp/http_parser.py", line 15, in from .helpers import NO_EXTENSIONS, BaseTimerContext File "/usr/lib/python3/dist-packages/aiohttp/helpers.py", line 667, in class CeilTimeout(async_timeout.timeout): TypeError: function() argument 'code' must be code, not str root@zion:/# python3.10 -c "import aiohttp" Traceback (most recent call last): File "", line 1, in File "/usr/lib/python3/dist-packages/aiohttp/__init__.py", line 6, in from .client import ( File "/usr/lib/python3/dist-packages/aiohttp/client.py", line 35, in from . import hdrs, http, payload File "/usr/lib/python3/dist-packages/aiohttp/http.py", line 7, in from .http_parser import ( File "/usr/lib/python3/dist-packages/aiohttp/http_parser.py", line 15, in from .helpers import NO_EXTENSIONS, BaseTimerContext File "/usr/lib/python3/dist-packages/aiohttp/helpers.py", line 667, in class CeilTimeout(async_timeout.timeout): TypeError: function() argument 'code' must be code, not str this is from an up-to-date, clean chroot. This is already affecting uvloop, likely all other aiohttop rdeps are affected too. Regards, Sandro -- System Information: Debian Release: 11.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.14.0-4-amd64 (SMP w/8 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3-aiohttp depends on: ii libc6 2.32-4 ii python33.9.8-1 ii python3-async-timeout 3.0.1-1.1 ii python3-attr 20.3.0-1 ii python3-chardet4.0.0-1 ii python3-multidict 5.1.0-1 ii python3-typing-extensions 3.10.0.2-1 ii python3-yarl 1.6.3-2 Versions of packages python3-aiohttp recommends: ii libjs-jquery 3.5.1+dfsg+~3.5.5-7 python3-aiohttp suggests no packages. -- no debconf information
Processed: python3-aiohttp: fails to import, "TypeError: function() argument 'code' must be code, not str"
Processing control commands: > affects -1 uvloop Bug #1000680 [python3-aiohttp] python3-aiohttp: fails to import, "TypeError: function() argument 'code' must be code, not str" Added indication that 1000680 affects uvloop -- 1000680: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000680 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000679: marked as done (ruby-rr: NameError: uninitialized constant ActiveSupport)
Your message dated Sat, 27 Nov 2021 03:04:39 + with message-id and subject line Bug#1000679: fixed in ruby-rr 3.0.8-1 has caused the Debian Bug report #1000679, regarding ruby-rr: NameError: uninitialized constant ActiveSupport 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.) -- 1000679: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000679 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sup-mail Version: 1.0-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, sup-mail was found to fail to build in that situation. This seems unrelated to ruby3.0, since the ruby2.7 tests already fail. Relevant part (hopefully): > /usr/bin/ruby2.7 /usr/bin/gem2deb-test-runner > > ┌──┐ > │ Run tests for ruby2.7 from debian/ruby-tests.rb > │ > └──┘ > > RUBYLIB=/<>/debian/sup-mail/usr/lib/ruby/vendor_ruby:. > GEM_PATH=/<>/debian/sup-mail/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/2.7.0:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0 > ruby2.7 debian/ruby-tests.rb > tput: No value for $TERM and no -T specified > tput: No value for $TERM and no -T specified > Some YAML tests are skipped on Ruby 2.1.0 and newer. > Run options: --seed 8439 > > # Running: > > [2021-10-05 02:07:09 +] WARNING: URI.escape is obsolete > [2021-10-05 02:07:09 +] WARNING: found invalid date in potential mbox > split line, not splitting: "From sea to shining sea\n" > [2021-10-05 02:07:09 +] WARNING: found invalid date in potential mbox > split line, not splitting: "From b...@bob.com I get only spam.\n" > ..[2021-10-05 02:07:09 +] WARNING: URI.escape is obsolete > .[2021-10-05 02:07:09 +] WARNING: DEPRECATED: Use assert_nil if expecting > nil from /<>/test/test_header_parsing.rb:72. This will fail in > Minitest 6. > E/usr/bin/which: this version of `which' is deprecated; use `command -v' > in scripts instead. > [2021-10-05 02:07:09 +] WARNING: No crypto set up, crypto will not be > tested. Reason: ["Environment variable 'GPG_AGENT_INFO' not set, is gpg-agent > running?", "If gpg-agent is running, try $ export `cat ~/.gpg-agent-info`"] > ./usr/bin/which: this version of `which' is deprecated; use `command -v' in > scripts instead. > [2021-10-05 02:07:09 +] WARNING: No crypto set up, crypto will not be > tested. Reason: ["Environment variable 'GPG_AGENT_INFO' not set, is gpg-agent > running?", "If gpg-agent is running, try $ export `cat ~/.gpg-agent-info`"] > ./usr/bin/which: this version of `which' is deprecated; use `command -v' in > scripts instead. > [2021-10-05 02:07:09 +] WARNING: No crypto set up, crypto will not be > tested. Reason: ["Environment variable 'GPG_AGENT_INFO' not set, is gpg-agent > running?", "If gpg-agent is running, try $ export `cat ~/.gpg-agent-info`"] > ./usr/bin/which: this version of `which' is deprecated; use `command -v' in > scripts instead. > [2021-10-05 02:07:09 +] WARNING: No crypto set up, crypto will not be > tested. Reason: ["Environment variable 'GPG_AGENT_INFO' not set, is gpg-agent > running?", "If gpg-agent is running, try $ export `cat ~/.gpg-agent-info`"] > ./usr/bin/which: this version of `which' is deprecated; use `command -v' in > scripts instead. > [2021-10-05 02:07:09 +] WARNING: No crypto set up, crypto will not be > tested. Reason: ["Environment variable 'GPG_AGENT_INFO' not set, is gpg-agent > running?", "If gpg-agent is running, try $ export `cat ~/.gpg-agent-info`"] > ./usr/bin/which: this version of `which' is deprecated; use `command -v' in > scripts instead. > [2021-10-05 02:07:09 +] WARNING: No crypto set up, crypto will not be > tested. Reason: ["Environment variable 'GPG_AGENT_INFO' not set, is gpg-agent > running?", "If gpg-agent is running, try $ export `cat ~/.gpg-agent-info`"] > .[2021-10-05 02:07:09 +] WARNING: problem reading message > sup-faked-df001467cbd7d1c987812838111e7731 > [2021-10-05 02:07:09 +] WARNING: Message is in sup-test://test_messages > at 0 > ..[2021-10-05 02:07:0
Processed: Bug#1000679 marked as pending in ruby-rr
Processing control commands: > tag -1 pending Bug #1000679 [ruby-rr] ruby-rr: NameError: uninitialized constant ActiveSupport Added tag(s) pending. -- 1000679: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000679 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000679: marked as pending in ruby-rr
Control: tag -1 pending Hello, Bug #1000679 in ruby-rr 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-rr/-/commit/12e9e609ee3e27d8b87b6432b3e72060a9cdbcea ruby-rr (3.0.8-1) UNRELEASED * New upstream release. - Fixes Minitest and ActiveSupport integration (closes: #1000679). (this message was generated automatically) -- Greetings https://bugs.debian.org/1000679
Processed: cloning 996527, reassign -1 to ruby-rr ..., tagging -1 ..., block 996527 with -1
Processing commands for cont...@bugs.debian.org: > clone 996527 -1 Bug #996527 [src:sup-mail] sup-mail: FTBFS: ERROR: Test "ruby2.7" failed: NameError: uninitialized constant ActiveSupport Bug 996527 cloned as bug 1000679 > reassign -1 ruby-rr 3.0.7-1 Bug #1000679 [src:sup-mail] sup-mail: FTBFS: ERROR: Test "ruby2.7" failed: NameError: uninitialized constant ActiveSupport Bug reassigned from package 'src:sup-mail' to 'ruby-rr'. No longer marked as found in versions sup-mail/1.0-3. Ignoring request to alter fixed versions of bug #1000679 to the same values previously set Bug #1000679 [ruby-rr] sup-mail: FTBFS: ERROR: Test "ruby2.7" failed: NameError: uninitialized constant ActiveSupport Marked as found in versions ruby-rr/3.0.7-1. > retitle -1 ruby-rr: NameError: uninitialized constant ActiveSupport Bug #1000679 [ruby-rr] sup-mail: FTBFS: ERROR: Test "ruby2.7" failed: NameError: uninitialized constant ActiveSupport Changed Bug title to 'ruby-rr: NameError: uninitialized constant ActiveSupport' from 'sup-mail: FTBFS: ERROR: Test "ruby2.7" failed: NameError: uninitialized constant ActiveSupport'. > tags -1 + fixed-upstream Bug #1000679 [ruby-rr] ruby-rr: NameError: uninitialized constant ActiveSupport Added tag(s) fixed-upstream. > forwarded -1 https://github.com/rr/rr/issues/88 Bug #1000679 [ruby-rr] ruby-rr: NameError: uninitialized constant ActiveSupport Set Bug forwarded-to-address to 'https://github.com/rr/rr/issues/88'. > block 996527 with -1 Bug #996527 [src:sup-mail] sup-mail: FTBFS: ERROR: Test "ruby2.7" failed: NameError: uninitialized constant ActiveSupport 996527 was not blocked by any bugs. 996527 was not blocking any bugs. Added blocking bug(s) of 996527: 1000679 > thanks Stopping processing here. Please contact me if you need assistance. -- 1000679: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000679 996527: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996527 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996308: marked as done (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 fi
Your message dated Sat, 27 Nov 2021 02:53:30 +0100 with message-id <4e48a243a735f622cd20ac3a783ee01b7b696799.ca...@debian.org> and subject line Both issues fixed with the upload of test-kitchen/1.23.2-6 has caused the Debian Bug report #996308, regarding 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.19) among 70 total gem(s) (Gem::MissingSpecError) 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.) -- 996308: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996308 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- 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
Bug#996307: marked as done (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
Your message dated Sat, 27 Nov 2021 02:53:30 +0100 with message-id <4e48a243a735f622cd20ac3a783ee01b7b696799.ca...@debian.org> and subject line Both issues fixed with the upload of test-kitchen/1.23.2-6 has caused the Debian Bug report #996307, regarding 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' (~> 0.19) among 82 total gem(s) (Gem::MissingSpecError) 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.) -- 996307: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996307 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- 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)
Bug#996528: marked as done (test-kitchen: FTBFS: ERROR: Test "ruby2.7" failed: Could not find 'thor' (~> 0.19) among 87 total gem(s) (Gem::MissingSpecError))
Your message dated Sat, 27 Nov 2021 01:48:45 + with message-id and subject line Bug#996528: fixed in test-kitchen 1.23.2-6 has caused the Debian Bug report #996528, regarding test-kitchen: FTBFS: ERROR: Test "ruby2.7" failed: Could not find 'thor' (~> 0.19) among 87 total gem(s) (Gem::MissingSpecError) 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.) -- 996528: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996528 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: test-kitchen Version: 1.23.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, test-kitchen 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/specification.rb:1404:in `rescue in block > in activate_dependencies': Could not find 'thor' (~> 0.19) among 87 total > gem(s) (Gem::MissingSpecError) > Checked in > 'GEM_PATH=/<>/debian/test-kitchen/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: > /<>/debian/test-kitchen/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/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/test-kitchen/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/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 `' > aruba (1.0.4) > bcrypt_pbkdf (1.1.0) > benchmark (default: 0.1.0) > bigdecimal (default: 2.0.0) > builder (3.2.4) > bundler (default: 2.1.4) > cgi (default: 0.1.0) > chef-utils (16.12.3) > childprocess (4.1.0) > coderay (1.1.3) > contracts (0.16.0) > csv (default: 3.1.2) > cucumber (2.4.0) > cucumber-core (1.5.0) > cucumber-wire (0.0.1) > 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) > ed25519 (1.2.4) > etc (default: 1.1.0) > fakefs (1.2.0) > fcntl (default: 1.0.0) > ffi (1.12.2) > 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) > gherkin (4.0.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) > metaclass (0.0.4) > method_source (1.0.0) > minitest (5.13.0) > mixlib-install (3.11.7) > mixlib-shellout (3.2.5) > mixlib-versioning (1.1.0) > mocha (1.7.0) > multi_json (1.14.1) > multi_test (0.1.2) > mut
Bug#967018: marked as done (test-kitchen: FTBFS: ERROR: Test "ruby2.7" failed: cannot load such file -- aruba/in_process (LoadError))
Your message dated Sat, 27 Nov 2021 01:48:45 + with message-id and subject line Bug#967018: fixed in test-kitchen 1.23.2-6 has caused the Debian Bug report #967018, regarding test-kitchen: FTBFS: ERROR: Test "ruby2.7" failed: cannot load such file -- aruba/in_process (LoadError) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 967018: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967018 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: test-kitchen Version: 1.23.2-5 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200802 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > cannot load such file -- aruba/in_process (LoadError) > /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in `require' > /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in `require' > /<>/features/support/env.rb:6:in `' > /usr/lib/ruby/vendor_ruby/cucumber/rb_support/rb_language.rb:96:in `load' > /usr/lib/ruby/vendor_ruby/cucumber/rb_support/rb_language.rb:96:in > `load_code_file' > /usr/lib/ruby/vendor_ruby/cucumber/runtime/support_code.rb:142:in `load_file' > /usr/lib/ruby/vendor_ruby/cucumber/runtime/support_code.rb:84:in `block in > load_files!' > /usr/lib/ruby/vendor_ruby/cucumber/runtime/support_code.rb:83:in `each' > /usr/lib/ruby/vendor_ruby/cucumber/runtime/support_code.rb:83:in `load_files!' > /usr/lib/ruby/vendor_ruby/cucumber/runtime.rb:253:in `load_step_definitions' > /usr/lib/ruby/vendor_ruby/cucumber/runtime.rb:61:in `run!' > /usr/lib/ruby/vendor_ruby/cucumber/cli/main.rb:32:in `execute!' > /usr/bin/cucumber:7:in `' > ERROR: Test "ruby2.7" failed: The full build log is available from: http://qa-logs.debian.net/2020/08/02/test-kitchen_1.23.2-5_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: test-kitchen Source-Version: 1.23.2-6 Done: Daniel Leidert We believe that the bug you reported is fixed in the latest version of test-kitchen, 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 967...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Daniel Leidert (supplier of updated test-kitchen package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 27 Nov 2021 02:25:32 +0100 Source: test-kitchen Architecture: source Version: 1.23.2-6 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Team Changed-By: Daniel Leidert Closes: 967018 996528 Changes: test-kitchen (1.23.2-6) unstable; urgency=medium . * Team upload. . [ Debian Janitor ] * Set upstream metadata fields: Bug-Submit. . [ Daniel Leidert ] * d/rules: Avoid a nasty error when rebuilding after a build failure. * d/patches/0019-Relax-dependency-on-thor.patch: Add patch. - Allow thor 1.x (closes: #996528) * d/patches/0020-Fix-Aruba-depreaction.patch: Add patch. - Replace deprecated aruba requires (closes: #967018). * d/patches/0021-Fix-Ruby-3.0-TypeError.patch: Add patch. - Fix a Ruby 3.0 TypeError. * d/patches/series: Add new patch. Checksums-Sha1: 5029f6870f1c9e9d65fc637462232244f8d1141b 2313 test-kitchen_1.23.2-6.dsc b19c847d6cefdca8f987d6da1dc568bc24d9cbc7 11656 test-kitchen_1.23.2-6.debian.tar.xz a58ae32122fc0e4684fdc499e5c4f9c46f2c8061 10309 test-kitchen_1.23.2-6_amd64.buildinfo Checksums-Sha256: cc74441cf1a3593e46368423204ef64e6cd95a11c31703c3fbd9f53f55a76832 2313 test-kitchen_1.23.2-6.dsc 54c613416cb268aad27094894411949cda22b3434a4655b303c765fd0972bdf2 11656 test-kitchen_1.23.2-6.debian.tar.xz 8c5b3104a637aa48827cbcfbef69ca24fbfd5eea811579adb4c822be61c3eb02 10309 test-kitchen_1.23.2-6_amd64.buildinfo Files: 57a05ffbc4e09757eeeb2b774bb23322 2313 misc optional test-kitche
Bug#996528: marked as pending in test-kitchen
Control: tag -1 pending Hello, Bug #996528 in test-kitchen 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/test-kitchen/-/commit/b078c418725c243a02c0e9ef9acbbcf810e91d9b Add patch to relax dependency on thor * d/patches/0019-Relax-dependency-on-thor.patch: Add patch. - Allow thor 1.x (closes: #996528) * d/patches/series: Add new patch. (this message was generated automatically) -- Greetings https://bugs.debian.org/996528
Processed: Bug#996528 marked as pending in test-kitchen
Processing control commands: > tag -1 pending Bug #996528 [src:test-kitchen] test-kitchen: FTBFS: ERROR: Test "ruby2.7" failed: Could not find 'thor' (~> 0.19) among 87 total gem(s) (Gem::MissingSpecError) Added tag(s) pending. -- 996528: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996528 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#967018 marked as pending in test-kitchen
Processing control commands: > tag -1 pending Bug #967018 [src:test-kitchen] test-kitchen: FTBFS: ERROR: Test "ruby2.7" failed: cannot load such file -- aruba/in_process (LoadError) Added tag(s) pending. -- 967018: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967018 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#967018: marked as pending in test-kitchen
Control: tag -1 pending Hello, Bug #967018 in test-kitchen 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/test-kitchen/-/commit/f95bcf341f8bb4e0edc481978c238146ff804ce7 Add patch to replace deprecated aruba requires * d/patches/0020-Fix-Aruba-depreaction.patch: Add patch. - Replace deprecated aruba requires (closes: #967018). * d/patches/series: Add new patch. (this message was generated automatically) -- Greetings https://bugs.debian.org/967018
Bug#994366: marked as done (python-pyxattr: Removal of the python3-*-dbg packages in sid/bookworm)
Your message dated Sat, 27 Nov 2021 00:49:44 + with message-id and subject line Bug#994366: fixed in python-pyxattr 0.7.2-2 has caused the Debian Bug report #994366, regarding python-pyxattr: Removal of the python3-*-dbg packages in sid/bookworm 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.) -- 994366: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994366 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-pyxattr Version: 0.7.2-1 Severity: serious Tags: sid bookworm User: debian-pyt...@lists.debian.org Usertags: pydbg-removal Python 3.8 upstream now has a common ABI for normal and debug extension builds, so we can drop the python3-*-dbg packages. Details at https://lists.debian.org/debian-python/2021/09/msg4.html Stop building the python3-*-dbg package, but be careful that all the reverse dependencies are also removed. Please check for dependencies, build dependencies AND autopkg tests. If help is needed, please ask on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: python-pyxattr Source-Version: 0.7.2-2 Done: Iustin Pop We believe that the bug you reported is fixed in the latest version of python-pyxattr, 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. Iustin Pop (supplier of updated python-pyxattr package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 27 Nov 2021 01:13:39 +0100 Source: python-pyxattr Architecture: source Version: 0.7.2-2 Distribution: unstable Urgency: medium Maintainer: Iustin Pop Changed-By: Iustin Pop Closes: 994366 Changes: python-pyxattr (0.7.2-2) unstable; urgency=medium . [ Debian Janitor ] * Remove constraints unnecessary since buster: + python-pyxattr-doc: Drop versioned constraint on python-pyxattr in Replaces. + python-pyxattr-doc: Drop versioned constraint on python-pyxattr in Breaks. . [ Iustin Pop ] * Remove debug package; no reverse deps, so straightforward (Closes: #994366). * Bump standards version (no changes needed). * Fix double-building (pbuild) by adding an ignore for egg-info/PKG-INFO files. Checksums-Sha1: ed1e9ca403e30a54691779e544e43cdddf4eed07 2402 python-pyxattr_0.7.2-2.dsc 82158f33f97741afb76377eec93a681f46a3bedb 8836 python-pyxattr_0.7.2-2.debian.tar.xz f236a3101ab8a18df6df96a5306394343bfb2a4c 8917 python-pyxattr_0.7.2-2_source.buildinfo Checksums-Sha256: 42f06545fc962fbec6ff74e089a284d098c4b1153d103ceb42d195b57252229c 2402 python-pyxattr_0.7.2-2.dsc 8bce08fa90dd8e8b42c2418e5291c34990bdba549b79361b6b3157a51c66ecbe 8836 python-pyxattr_0.7.2-2.debian.tar.xz 5ba0bb53d871132ca0ec1ad598ae6ac2a98a9beae2af5463de4c826e7643036b 8917 python-pyxattr_0.7.2-2_source.buildinfo Files: 63acf9ee0ba4fe97ec629d27ebae9586 2402 python optional python-pyxattr_0.7.2-2.dsc 83b5cfc6736c1021acdc68427c18f0c4 8836 python optional python-pyxattr_0.7.2-2.debian.tar.xz 86a7153897bbd79c0297fe1a6f3bf703 8917 python optional python-pyxattr_0.7.2-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEy5TjqjsXVdYeuxml9m4+QZ+E9N4FAmGhehwSHGl1c3RpbkBk ZWJpYW4ub3JnAAoJEPZuPkGfhPTeVd8P/Ryow6BpIzM8mc3cwVWFeKQTY7ZQSvee qGLi6RtGgxOh/kuC2b96BMOPZ14pqKtJxkN325P7xLJeDP6LIPXwVr0YLnyvx/yZ B0NOPqWog9qtivVJQFTYEbpc2GrMAAicbxRWfBc99FmgUnChS3NqyyK5s62PZqkw gMdmG/uT140AwOZdpisFSVjuEuXst36HoMfDGUea9ieT2lVtq2qoGZLx7pwy+aTo spf2vENIg34qmX4T7WCK+39N3sbJOdCm/Epg3EXP0Y3S6N9R4fLaffZnmZvs3W+H r7JQevhd9TIUgWGiryNIi0rLhuOjHtfPcfhyuREbBDLQW/LU8vGY+4H6gBDvY0cq I0xvMdy7Eg+BYvke6O4XMkeK1XYWNKzrxzlQw2U4dtuo8+vM4bWY92NS15XxJeAG T0vWzlISE3fZLYCmxGgGrb0dKUQo0TsG6+5x2Rnk49ozd3Ne0+xW5jTF2q9UkfVv YSqWpTB0c6Kv4bwkWaJdrrlr5cFeQn0ZrYh7ayjbFPXcRbWZA7+K9egs4ljdmmio WE9xgmjCpnoPyG3RJyK6K5Tz9Gc2NtqyTLekqTo3xMQLp2Op4Xxy1rIzCIcUQo5g fkqg3HCUckFuMC5WOA6ZwTNFmE+7uWtnIOKvJGl2XcstFD63hmLw2pauCAbmfLPG Jz0j29NdMXGD =lp07 -END PGP SIGNATURE End Message ---
Processed: severity of 994359 is important
Processing commands for cont...@bugs.debian.org: > severity 994359 important Bug #994359 [src:python-llfuse] python-llfuse: Removal of the python3-*-dbg packages in sid/bookworm Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 994359: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994359 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: block 996308 with 996528
Processing commands for cont...@bugs.debian.org: > block 996308 with 996528 Bug #996308 [src:ruby-kitchen-salt] 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.19) among 70 total gem(s) (Gem::MissingSpecError) 996308 was not blocked by any bugs. 996308 was not blocking any bugs. Added blocking bug(s) of 996308: 996528 > thanks Stopping processing here. Please contact me if you need assistance. -- 996308: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996308 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000673: [Pkg-javascript-devel] Bug#1000673: reportbug: npm package depends on too many packages, including X11
Control: severity -1 important Hi Mikel, Quoting Mikel Pérez (2021-11-26 23:57:36) > Severity: serious > Justification: Policy 2.2.1 Justification cannot be § 2.2.1 which is about what can go into Debian or instead can only be part of the "contrib" or "non-free": the npm package comply with all requirements in § 2.2.1 to be in "main" and all of its dependencies and recommendations are permitted in "main" as well. This issue seems instead to be related to Policy § 7.2 - the rules about declaring package dependencies, recommendations, and suggestions: https://www.debian.org/doc/debian-policy/ch-relationships.html#binary-dependencies-depends-recommends-suggests-enhances-pre-depends I consider the severity inflated of this issue inflated: Severity "serious" means the issue to so severe that it is better to completely remove npm from Debian if the issue is not resolved. That's certainly not the case here, so I've taken the liberty to lower severity to "important" - even though I am not the maintainer of npm. > I was installing npm on my headless raspberry pi when I noticed it > pulls unnecessary libx11 packages and xserver-utils. Since they're not > listed on the package dependencies, I assume one of the dependencies > is that which includes it. Still, I find it doubtful that anything > that depends on X is actually needed to run npm. > > I believe the dependency list needs to be revised. > I tried with the debian docker image too so it is not a raspbian bug. npm depends on node-opener, which depends on xdg-utils, which recommends xserver-utils, which depends on libx11. Seems sensible to me that npm wants the ability to open things in a web browser and thus via node-opener uses XDG calls for that. Since the X11 libraries and tools are only recommended, you have the option to suppress installing it - e.g. with this command: apt install npm libx11-data- Personally I consider this a non-issue: I would prefer if npm would consider it an exotic thing to rely on graphical tools, but by its dependency on node-opener the authors of npm clearly consider integration with graphical tools a part of its user experience, and we should appreciate that it is _possible_ to suppress that. Only if npm gracefully handles node-opener being unavailable does it (maybe) make sense to relax to only suggesting node-opener. I leave it to npm package maintainers how to proceed further here... - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Processed: block 996307 with 996528
Processing commands for cont...@bugs.debian.org: > block 996307 with 996528 Bug #996307 [src:ruby-kitchen-docker] 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' (~> 0.19) among 82 total gem(s) (Gem::MissingSpecError) 996307 was not blocked by any bugs. 996307 was not blocking any bugs. Added blocking bug(s) of 996307: 996528 > thanks Stopping processing here. Please contact me if you need assistance. -- 996307: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996307 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: [Pkg-javascript-devel] Bug#1000673: reportbug: npm package depends on too many packages, including X11
Processing control commands: > severity -1 important Bug #1000673 [npm] reportbug: npm package depends on too many packages, including X11 Severity set to 'important' from 'serious' -- 1000673: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000673 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 996116
Processing commands for cont...@bugs.debian.org: > # > https://salsa.debian.org/ruby-team/forks/r10k/-/commit/8b869037d4fa83de1d5ab67b34ce6ac70718fd30 > tags 996116 + pending Bug #996116 [src:r10k] r10k: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 996116: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996116 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000467: marked as done (rpm, autopkgtest failure on armhf)
Your message dated Fri, 26 Nov 2021 23:35:43 +
with message-id
and subject line Bug#968487: fixed in rpm 4.17.0+dfsg1-2
has caused the Debian Bug report #968487,
regarding rpm, autopkgtest failure on armhf
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.)
--
968487: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968487
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: rpm
Version: 4.17.0+dfsg1-1
Severity: serious
The new version of rpm added an autopkgtest, but unfortunately it's failing on
armhf
and blocking the migration to testing (and hence blocking the fixes for two
other rc bugs).
autopkgtest [04:40:50]: test rpmbuild: env PYTHONPATH="$(pwd)/debian/tests/src"
python3 -B -u -m rpmtest -b /usr/bin -d debian/tests/data
autopkgtest [04:40:50]: test rpmbuild: [---
Using /tmp/tmpma2atafk as a temporary directory
Querying `rpm` for the target architecture
Unexpected `rpm --eval` output: '%{_arch}'
autopkgtest [04:40:51]: test rpmbuild: ---]
autopkgtest [04:40:51]: test rpmbuild: - - - - - - - - - - results - - - - - -
- - - -
rpmbuild FAIL non-zero exit status 1
autopkgtest [04:40:51]: summary
rpmbuild FAIL non-zero exit status 1
--- End Message ---
--- Begin Message ---
Source: rpm
Source-Version: 4.17.0+dfsg1-2
Done: Peter Pentchev
We believe that the bug you reported is fixed in the latest version of
rpm, 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 968...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Peter Pentchev (supplier of updated rpm package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 27 Nov 2021 00:58:55 +0200
Source: rpm
Architecture: source
Version: 4.17.0+dfsg1-2
Distribution: unstable
Urgency: medium
Maintainer: RPM packaging team
Changed-By: Peter Pentchev
Closes: 968487 990329 1000575
Changes:
rpm (4.17.0+dfsg1-2) unstable; urgency=medium
.
* Team upload.
* Add pandoc as a build dependency to fix a "FTBFS twice in a row" bug.
* Sort the list of build dependencies alphabetically.
* Add an epoch to the debugedit dependency. Closes: #1000575
* Add the gnueabihf patch to fix the armhf build. Closes: #968487
* Make the brp-python-bytecompile script executable.
* Fix the filename in a Facebook copyright notice.
* Fix the pythondistdeps.py interpreter name.
* Drop the no-op debian/dirs file.
* Also hardcode the /bin/mkdir path in `mkdir -p`. Closes: #990329
* Activate all the build hardening flags.
* Add the triplet-suffix patch as an attempt to catch earlier any
future breakage with new, unrecognized GNU target triplets.
* Refresh the line numbers in two patches.
* Add the cppcheck patch to fix two minor issues.
Checksums-Sha1:
81f486940d8773b347946989c32b1822c6abd858 3069 rpm_4.17.0+dfsg1-2.dsc
a447c22e2fd624f884a339282f7496293115dd9f 46888 rpm_4.17.0+dfsg1-2.debian.tar.xz
Checksums-Sha256:
1b7e0aea172ab482fef68548c5576738aee20029324ea2b04f3d0eda4a8546c9 3069
rpm_4.17.0+dfsg1-2.dsc
5997a7930ce546a9cc23ae3dd8f64bf88d22a442a024fe0895227ccd41af0f4c 46888
rpm_4.17.0+dfsg1-2.debian.tar.xz
Files:
cef761a6fda04e3bb931163d584cd440 3069 admin optional rpm_4.17.0+dfsg1-2.dsc
a25074ab85e89ac7ea1e88354550d88a 46888 admin optional
rpm_4.17.0+dfsg1-2.debian.tar.xz
-BEGIN PGP SIGNATURE-
iQJEBAEBCgAuFiEELuenpRf8EkzxFcNUZR7vsCUn3xMFAmGhaJkQHHJvYW1AZGVi
aWFuLm9yZwAKCRBlHu+wJSffE35PD/955nR0uU7oZ2+TD2AwfW21TbCohSpH8emd
AFrk1abqifOe3jorzo6gq9ouKhwH6xnL6+23INwBOTQ7dg74vma3j8cwGB/NNFIn
xnPWWYpNAE4cSPRuLwAMekHwlx17hyb5MYtG/iTSxi9qdc4twIBSKsZs6N6ZGNwe
fpIu06qyTbIn2XLY5gjAgIOI5ez0WXlIjS2kGv1FzUtn000lKXHurqa2b4AA9/7V
XD+zhkVPjzzNrOnSRkDcDqNZr8yS5EZDXxMLd0DWk9ciOYmgP9sqzrVazTm4rdJp
tCARZ5tBeWLhZkv2kIJzjgCrnusRK7TCdLC8veyaUsHpwOSZFPLcWXdnPYCU41EJ
rD4yer7Caa6xnJI6As/BSAhw53RrDNGfaA+MH6xXN8tK0kvkgWkQtsPdo8gyLRjs
1zLNqhx+6zOYZjfkstopl4MHTd2ofjq2hS1avlQOvJi0wx34YlTAdfPiCMqkQJs+
JK7KJtocH/hL83ZOVn2wouKg6jeqfS04jXxnD5q/oB/mHw6a4kxPzaa9J3xiTFg9
wOTqjUYwJ2GUEO3bQLyD75x5qXXzbzc+L9iRGVsP1iFiMfGQhxYvU81RSSm/1aQc
2CMlotRDD6evohWUDcyzA3M8o5KWWO
Bug#996137: marked as done (ruby-binding-of-caller: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: :85:in `require': cannot l
Your message dated Fri, 26 Nov 2021 23:35:51 +
with message-id
and subject line Bug#996137: fixed in ruby-binding-of-caller 1.0.0-1
has caused the Debian Bug report #996137,
regarding ruby-binding-of-caller: FTBFS with ruby3.0: ERROR: Test "ruby3.0"
failed:
:85:in
`require': cannot load such file -- binding_of_caller.so (LoadError)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
996137: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996137
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-binding-of-caller
Version: 0.7.2+debian1-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-binding-of-caller 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 -- binding_of_caller.so (LoadError)
> Did you mean? binding_of_caller
>binding_of_caller/mri2
> from
> :85:in
> `require'
> from /<>/lib/binding_of_caller.rb:11:in `'
> from
> :85:in
> `require'
> from
> :85:in
> `require'
> from /<>/test/test_binding_of_caller.rb:3:in ` (required)>'
> from /usr/bin/bacon:116:in `load'
> from /usr/bin/bacon:116:in `block in '
> from /usr/bin/bacon:115:in `each'
> from /usr/bin/bacon:115:in `'
> 0 specifications (0 requirements), 0 failures, 0 errors
> ERROR: Test "ruby3.0" failed:
The full build log is available at
https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-binding-of-caller/ruby-binding-of-caller_0.7.2+debian1-3+rebuild1633375675_amd64.build.txt
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ruby-binding-of-caller
Source-Version: 1.0.0-1
Done: Daniel Leidert
We believe that the bug you reported is fixed in the latest version of
ruby-binding-of-caller, 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.
Daniel Leidert (supplier of updated
ruby-binding-of-caller package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 27 Nov 2021 00:07:27 +0100
Source: ruby-binding-of-caller
Architecture: source
Version: 1.0.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team
Changed-By: Daniel Leidert
Closes: 996137
Changes:
ruby-binding-of-caller (1.0.0-1) unstable; urgency=medium
.
* Team upload.
* New upstream release (closes: #996137).
.
[ Debian Janitor ]
* Use secure copyright file specification URI.
* Use secure URI in debian/watch.
* Use secure URI in Homepage field.
* Set debhelper-compat version in Build-Depends.
* Set upstream metadata fields: Bug-Database, Bug-Submit.
* Update Vcs-* headers from URL redirect.
* Use canonical URL in Vcs-Git.
* Update watch file format version to 4.
* Remove constraints unnecessary since buster:
+ Build-Depends: Drop versioned constraint on ruby-debug-inspector.
+ ruby-binding-of-caller: Drop versioned constraint on ruby-debug-inspector
in Depends.
.
[ Daniel Leidert ]
* d/control: Add Rules-Requires-Root field.
(Standards-Version): Bump to 4.6.0.
(Build-Depends): Raise debhelper to version 13 and remove ruby-bacon.
(Depends): Remove interpreters and use ${ruby:Depends}.
* d/copyright: Add Upstream-Contact field and remove Files-Excluded.
(Source): Update URL.
(Copyright): Add team.
* d/ruby-binding-of-caller.examples: Install examples.
* d/ruby-tests.rake: Add and run tests.
* d/ruby-tests.rb: Remove old test file.
* d/rules: Use gem installation layout and remove obsolete targets.
* d/watch: Update and use github sources for tests.
* d/patches/add-clean-target.patch: Drop obsolete patch.
* d/patches/no-extensions.patch: Ditto.
* d/patches/Remove-git-from-gemspec.patch: Add patch.
- Remove
Bug#968487: marked as done (rpm returns wrong %{_target})
Your message dated Fri, 26 Nov 2021 23:35:43 +
with message-id
and subject line Bug#968487: fixed in rpm 4.17.0+dfsg1-2
has caused the Debian Bug report #968487,
regarding rpm returns wrong %{_target}
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.)
--
968487: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968487
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: rpm
Version: 4.14.2.1+dfsg1-1
Severity: important
Dear Maintainer,
On my 32-bit ARM system (armhf architecture), the value for the
%{_target} macro returned `rpm` or `rpmbuild` does not match the
directory names in `/usr/lib/rpm/platform`. Subsequently, rpm-package
builds fail as the macros
defined in `/usr/lib/rpm/platform/%{_target}` are not included, e.g.
%{_arch} is not defined in that case.
In particular, `rpm -E '%{_target}'` returns `armv7hnl-linux`, however
the respective directory is called `armv7hnl-linux-gnueabihf`.
Workaround: Creating a sym-link (`ln -s armv7hnl-linux-gnueabihf
armv7hnl-linux`) resolves the issue as the correct macros are
included, but is obviously not a proper solution.
It seems this issue is not present for other architectures (e.g.
x86_64) as the values returned by `rpm` and the directory names in
`/usr/lib/rpm/platform` match there.
-Armin
-- System Information:
Debian Release: 10.5
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: armhf (armv7l)
Kernel: Linux 5.4.43-mvebu (SMP w/2 CPU cores)
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=en_US.UTF-8
(charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages rpm depends on:
ii debugedit 4.14.2.1+dfsg1-1
ii libc6 2.28-10
ii libelf1 0.176-1.1
ii libpopt0 1.16-12
ii librpm8 4.14.2.1+dfsg1-1
ii librpmbuild8 4.14.2.1+dfsg1-1
ii librpmio8 4.14.2.1+dfsg1-1
ii librpmsign8 4.14.2.1+dfsg1-1
ii perl 5.28.1-6+deb10u1
ii rpm-common4.14.2.1+dfsg1-1
ii rpm2cpio 4.14.2.1+dfsg1-1
rpm recommends no packages.
Versions of packages rpm suggests:
ii alien 8.95
pn elfutils
ii python2.7.16-1
pn rpm-i18n
pn rpm2html
pn rpmlint
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: rpm
Source-Version: 4.17.0+dfsg1-2
Done: Peter Pentchev
We believe that the bug you reported is fixed in the latest version of
rpm, 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 968...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Peter Pentchev (supplier of updated rpm package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 27 Nov 2021 00:58:55 +0200
Source: rpm
Architecture: source
Version: 4.17.0+dfsg1-2
Distribution: unstable
Urgency: medium
Maintainer: RPM packaging team
Changed-By: Peter Pentchev
Closes: 968487 990329 1000575
Changes:
rpm (4.17.0+dfsg1-2) unstable; urgency=medium
.
* Team upload.
* Add pandoc as a build dependency to fix a "FTBFS twice in a row" bug.
* Sort the list of build dependencies alphabetically.
* Add an epoch to the debugedit dependency. Closes: #1000575
* Add the gnueabihf patch to fix the armhf build. Closes: #968487
* Make the brp-python-bytecompile script executable.
* Fix the filename in a Facebook copyright notice.
* Fix the pythondistdeps.py interpreter name.
* Drop the no-op debian/dirs file.
* Also hardcode the /bin/mkdir path in `mkdir -p`. Closes: #990329
* Activate all the build hardening flags.
* Add the triplet-suffix patch as an attempt to catch earlier any
future breakage with new, unrecognized GNU target triplets.
* Refresh the line numbers in two patches.
* Add the cppcheck patch to fix two minor issues.
Checksums-Sha1:
81f486940d8773b347946989c32b1822c6abd858 3069 rpm_4.17.0+dfsg1-2.dsc
a447c22e2fd624f884a339282f7496293115dd9f 46888 rpm_4.17.0+dfsg1-2.debian.tar.xz
Checksums-Sha256:
1b7e0aea172ab482fef68548c5576738aee20029324ea2b04f3d0eda4a854
Bug#1000388: marked as done (FTBFS on s390x due to whitespace damage)
Your message dated Fri, 26 Nov 2021 23:18:45 + with message-id and subject line Bug#1000388: fixed in parlatype 3.0-2 has caused the Debian Bug report #1000388, regarding FTBFS on s390x due to whitespace damage 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.) -- 1000388: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000388 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: parlatype Version: 3.0-1 Build is currently broken like here [1] dpkg-buildpackage: info: host architecture s390x debian/rules clean debian/rules:19: *** missing separator. Stop. It is odd that this is only happening on s390x, but it is in fact whitespace damage. The rules do not start all lines with tabs, some are mixed space/tabs and that causes this. I'll open an MP with the (trivial) fix once I have a bug reference. [1]: https://buildd.debian.org/status/fetch.php?pkg=parlatype&arch=s390x&ver=3.0-1&stamp=1637515334&raw=0 -- Christian Ehrhardt Staff Engineer, Ubuntu Server Canonical Ltd --- End Message --- --- Begin Message --- Source: parlatype Source-Version: 3.0-2 Done: Gabor Karsay We believe that the bug you reported is fixed in the latest version of parlatype, 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 1000...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gabor Karsay (supplier of updated parlatype 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, 22 Nov 2021 22:34:16 +0100 Source: parlatype Architecture: source Version: 3.0-2 Distribution: unstable Urgency: medium Maintainer: Gabor Karsay Changed-By: Gabor Karsay Closes: 1000388 Changes: parlatype (3.0-2) unstable; urgency=medium . [ Christian Ehrhardt ] * d/rules: fix whitespace damage that breaks s390x builds (Closes: #1000388) Checksums-Sha1: f888ea73afd85f3d3c04db228f99fed48178ede5 2925 parlatype_3.0-2.dsc 0222156282c7ee892241fe1a0a6b08fb54db8937 21088 parlatype_3.0-2.debian.tar.xz b8bed41664b65a6f6db0a644ff81e56234f3af40 17435 parlatype_3.0-2_source.buildinfo Checksums-Sha256: 40dc28f7d7f03abdc902b5a91c128e544e4a85d6c872bb2e9bd778fbd7442f4f 2925 parlatype_3.0-2.dsc 2cc0a4c8a08d3bc01bbde93b14f12eab5d05b68fa4ffdb27d72cb7bb59cb8033 21088 parlatype_3.0-2.debian.tar.xz ba1d7b6fd8ecf2fd63ff38c65e15a4f286e3213d091dd5a38b64aa02b4a3a7f5 17435 parlatype_3.0-2_source.buildinfo Files: f014b2a804d26359a565ba8155fcc5a3 2925 sound optional parlatype_3.0-2.dsc 0f801eea170852b2c3a36d8a3dfa78d5 21088 sound optional parlatype_3.0-2.debian.tar.xz c6182aed499eef95c28274e440548016 17435 sound optional parlatype_3.0-2_source.buildinfo -BEGIN PGP SIGNATURE- iQGzBAEBCgAdFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmGhZ04ACgkQH1x6i0VW QxRjNQv/Ug92H7VKiSbHWMB01TbgcBp2nG4nmWs7drh1s3f1BWwIv2hq9pg6FQm8 S2OMcblsgmIXy+ap03s1VCZYaNm34ojIaiEbAJ10nozJKcyNm11zA5Wx+xnKWyFX U9Pox1JcVoOnlJSNQI10Jk9if4GDTFsbR4ks3UYyYXpLhd2rk2uWsY3lVGXldINa 5OaKZlyewrhLHDubokpFcxj3vUG0l4Y2nvdB6lqTlTBYZeI/EJBgzKrzWl9YRJjQ IZJpBukuD4o+S0cx2S0l/X4NDdGaK6jhnOscA7xWJ0TjGFVXhKiHQRRYCQhr25Sd MpGkkZpw5rB2+AOTlRw+kRoiIHCWNCmwr3SZ+XO0X359BRpo3stJL0KbU4wRPapB jy8C0upDhUTLI1BYuGZFwXwUPycRmm0oyMQwLuBzG21WhHHpHWRYCpsvtLzlY/Ou xRHBkuTjRmGbJDHDt5eIMpZ8+FRKp67/6wyqfrZqGuVFbGs020rvC5zpm7TsUQsn s/OVlCe8 =1wIt -END PGP SIGNATURE End Message ---
Processed: Bug#996137 marked as pending in ruby-binding-of-caller
Processing control commands: > tag -1 pending Bug #996137 [src:ruby-binding-of-caller] ruby-binding-of-caller: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: :85:in `require': cannot load such file -- binding_of_caller.so (LoadError) Added tag(s) pending. -- 996137: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996137 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996137: marked as pending in ruby-binding-of-caller
Control: tag -1 pending Hello, Bug #996137 in ruby-binding-of-caller 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-binding-of-caller/-/commit/52666f29526bdafe719174b5aeb47e076ec4135e ruby-binding-of-caller (1.0.0-1) UNRELEASED * New upstream release (closes: #996137) (this message was generated automatically) -- Greetings https://bugs.debian.org/996137
Bug#1000673: reportbug: npm package depends on too many packages, including X11
Package: npm Severity: serious Justification: Policy 2.2.1 X-Debbugs-Cc: i...@mikelpr.com Dear Maintainer, I was installing npm on my headless raspberry pi when I noticed it pulls unnecessary libx11 packages and xserver-utils. Since they're not listed on the package dependencies, I assume one of the dependencies is that which includes it. Still, I find it doubtful that anything that depends on X is actually needed to run npm. I believe the dependency list needs to be revised. I tried with the debian docker image too so it is not a raspbian bug. -- 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.14.18-300.fc35.x86_64 (SMP w/16 CPU threads) Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: unable to detect Versions of packages npm depends on: ii ca-certificates 20210119 pn node-abbrev pn node-agent-base pn node-ajv pn node-ansi pn node-ansi-regex pn node-ansi-styles pn node-ansistyles pn node-aproba pn node-archy pn node-are-we-there-yet pn node-asap pn node-asn1 pn node-assert-plus pn node-asynckit pn node-aws-sign2 pn node-aws4 pn node-balanced-match pn node-bcrypt-pbkdf pn node-brace-expansion pn node-builtins pn node-cacache pn node-caseless pn node-chalk pn node-chownr pn node-clone pn node-color-convert pn node-color-name pn node-colors pn node-columnify pn node-combined-stream pn node-concat-map pn node-console-control-strings pn node-core-util-is pn node-dashdash pn node-debug pn node-defaults pn node-delayed-stream pn node-delegates pn node-depd pn node-ecc-jsbn pn node-encoding pn node-err-code pn node-extend pn node-extsprintf pn node-fast-deep-equal pn node-forever-agent pn node-form-data pn node-fs.realpath pn node-function-bind pn node-gauge pn node-getpass pn node-glob pn node-graceful-fs pn node-gyp pn node-har-schema pn node-har-validator pn node-has-flag pn node-http-signature pn node-https-proxy-agent pn node-iconv-lite pn node-imurmurhash pn node-indent-string pn node-inflight pn node-inherits pn node-ini pn node-ip pn node-ip-regex pn node-is-typedarray pn node-isarray pn node-isexe pn node-isstream pn node-jsbn pn node-json-parse-better-errors pn node-json-schema pn node-json-schema-traverse pn node-json-stable-stringify pn node-json-stringify-safe pn node-jsonparse pn node-jsonstream pn node-jsprim pn node-leven pn node-lockfile pn node-mime pn node-mime-types pn node-minimatch pn node-mkdirp pn node-ms pn node-mute-stream pn node-nopt pn node-normalize-package-data pn node-npm-bundled pn node-npm-package-arg pn node-npmlog pn node-number-is-nan pn node-oauth-sign pn node-object-assign pn node-opener pn node-p-map pn node-path-is-absolute pn node-performance-now pn node-process-nextick-args pn node-promise-retry pn node-promzard pn node-psl pn node-puka pn node-punycode pn node-qs pn node-read
Bug#1000197: marked as done (assimp: binary-any FTBFS)
Your message dated Fri, 26 Nov 2021 22:19:16 + with message-id and subject line Bug#1000197: fixed in assimp 5.1.1~ds0-2 has caused the Debian Bug report #1000197, regarding assimp: binary-any FTBFS 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.) -- 1000197: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000197 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: assimp Version: 5.0.1~ds0-4 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=assimp&ver=5.0.1~ds0-4 ... dh clean --buildsystem=cmake dh_auto_clean -O--buildsystem=cmake debian/rules execute_after_dh_auto_clean-arch make[1]: Entering directory '/<>' rm -rf doc/tmp/ make[1]: Leaving directory '/<>' debian/rules execute_after_dh_auto_clean-indep make[1]: Entering directory '/<>' dh_auto_clean --indep --buildsystem=pybuild -- \ -d port/PyAssimp/ dh_auto_clean: error: unable to load build system class 'pybuild': Can't locate Debian/Debhelper/Buildsystem/pybuild.pm in @INC (you may need to install the Debian::Debhelper::Buildsystem::pybuild module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.32.1 /usr/local/share/perl/5.32.1 /usr/lib/x86_64-linux-gnu/perl5/5.32 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.32 /usr/share/perl/5.32 /usr/local/lib/site_perl) at (eval 6) line 1. BEGIN failed--compilation aborted at (eval 6) line 1. make[1]: *** [debian/rules:73: execute_after_dh_auto_clean-indep] Error 25 --- End Message --- --- Begin Message --- Source: assimp Source-Version: 5.1.1~ds0-2 Done: IOhannes m zmölnig (Debian/GNU) We believe that the bug you reported is fixed in the latest version of assimp, 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 1000...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. IOhannes m zmölnig (Debian/GNU) (supplier of updated assimp package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 26 Nov 2021 22:21:47 +0100 Source: assimp Architecture: source Version: 5.1.1~ds0-2 Distribution: unstable Urgency: medium Maintainer: IOhannes m zmölnig (Debian/GNU) Changed-By: IOhannes m zmölnig (Debian/GNU) Closes: 1000197 Changes: assimp (5.1.1~ds0-2) unstable; urgency=medium . * Allow failures of 'dh_auto_clean-indep' (Closes: #1000197) Checksums-Sha1: 4e05059afefd72a06800718dcade4707bd3ee093 2587 assimp_5.1.1~ds0-2.dsc 71d79f2c8cb7cf3c00070b8c697bba1b36514c53 32756 assimp_5.1.1~ds0-2.debian.tar.xz Checksums-Sha256: 89eeae998dd0580e7a51c477cc89762f8e91068c9d896061ba3b081c999c4b12 2587 assimp_5.1.1~ds0-2.dsc 5052af544ee330670926661af6d9c26397e78190c893553b956fa3610a4a4c5d 32756 assimp_5.1.1~ds0-2.debian.tar.xz Files: 185ea2e1c938b73f82e785b8b1f80308 2587 graphics optional assimp_5.1.1~ds0-2.dsc ae9516c52ece0035581133ee06f9163e 32756 graphics optional assimp_5.1.1~ds0-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQJKBAEBCAA0FiEEdAXnRVdICXNIABVttlAZxH96NvgFAmGhVc0WHGZvcnVtQHVt bGFldXRlLm11ci5hdAAKCRC2UBnEf3o2+FkxD/4gmcEIiJO89GC6dG4YmXRjpPMK Kh4uqJlCcXeDY3YAyPmcqK0gtAwKyTGqTXjAvwBJzzZWnytCPa2UJDW1cKwmkSoA tggLyGvsCn7N6I62LK5zfs3zb036VUpAQ9unyErdn47tj+fMf25GICCCOLXsgZuK 1fqWw7eadPGkZDQRz2yk7UJEP8qBNC6LlhHJr4v26rZhscpXWgtYPdmyDVVT+5nW af9TE5RW4vjnyQS+rIimH4aV7t0e/cTD33qYVhZky4ITnTtW7i39xU6OxVPa+gto tfA8zqn912pgK4P0IkmGe7mYiG3zEYjZwiDyODvuzjfFzWtd5cFtl2e4yq1bNzwW rET+JaAhpZtyx8b4Ry3H96iH9ssYaGPTlREnCRT3CoVUsPGVb/SoLszrY5b4MCgH QcwmrSPQhXs4LDEtGWQp4BIn3Rn7nhbojzR9lu7P4ozHAdLDg+KfVZqA1ezH/4l+ Oe+lqz6q6M1u1tiU9+BdXi1GpT10m8+DCaiSti1ScVaBA6CU3OLLDDlAvUmY43AD yZgr86M7VOIW6f/furXuRt4mKO0uAEkHcK8mdCxzuV2nZbc3Gl8s267oH/KIn2A0 kaOX2kJEabUfRn3JO0JYsAR4RdKapb+y5GKFzs5ShE2ndamSZCiuvs4yeTMTp+dQ IiTVrQbuSPi9trgarA== =Utts -END PGP SIGNATURE End Message ---
Bug#1000617: marked as done (python3-nbclient_0.5.6-1: trying to overwrite '/usr/bin/jupyter-run', which is also in package jupyter-client 7.0.6-2)
Your message dated Fri, 26 Nov 2021 21:19:36 + with message-id and subject line Bug#1000617: fixed in nbclient 0.5.6-2 has caused the Debian Bug report #1000617, regarding python3-nbclient_0.5.6-1: trying to overwrite '/usr/bin/jupyter-run', which is also in package jupyter-client 7.0.6-2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1000617: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000617 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-nbclient Version: 0.5.5-1 Severity: serious -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer, it looks like python3-nbclient / jupyter-client don't play well together: Unpacking python3-nbclient (0.5.6-1) over (0.5.5-1) ... dpkg: error processing archive /tmp/apt-dpkg-install-dawlPe/41-python3-nbclient_0.5.6-1_all.deb (--unpack): trying to overwrite '/usr/bin/jupyter-run', which is also in package jupyter-client 7.0.6-2 Roman - -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'unstable-debug'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.15.0-1-amd64 (SMP w/32 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3-nbclient depends on: ii python3 3.9.8-1 ii python3-jupyter-client 7.0.6-2 ii python3-nbformat5.1.3-1 ii python3-nest-asyncio1.5.1-1 ii python3-traitlets 5.1.1-1 python3-nbclient recommends no packages. python3-nbclient suggests no packages. - -- debconf-show failed -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEjkF6151RK40WXe2HCDw+u0oWieAFAmGgAWAACgkQCDw+u0oW ieBqgg/8DM/IiyThgtywLCfOU8oGu3WGFCFDQcT7q7X+TkNSB+q3aeZ/rH5+5V19 fwlS2LnNKG/yqvDz2BSUq5+NZZJXp1wEqlpDhpgb3eSMjimBN/AjudtQbATqFtXW EhWIRCH3qlig3Bs/q170DbdAT7D6ql4iDdM3hFVN7W4UpjcxmJL1y1k9lQpYG54G 5F25gUI5yrBJTVmt+24ApZChNEj6L1ZKnF7g5155V6PhMnyjygigzift2RfbUGfB fJerTPjEhPYdwIYq/fLIrVC9cmfVT4EYzxqUIFEK0wlUZNTBYbhb6HO+J9EXtbrB BrN8/6wptBlyP4R4dmCCplqt2UzduLRkVvgSjMNyzTcZIhco5vs8bQzplKOjA9ui vuKCmtjgcuNyCvvCi6p2LTaimne74gUNdPic99THb2XqplfvwPMN/+cvoONCh4r9 AUiv//q/OCJP3bC9bZg0cmwm69td5SUI4FtnkDF344hJLETio8nXhfaIIgi59io5 2hCQQhxIxOMxIQ1/iOpGGq+VrZlIHi8TaqiwItB6vxPrMEMy6P59zk18lamxpIsd 9d/QE6K36+3yYxNscPucpLAMPEQxtIQ68IFQM7M7betVNHPVErDVgn/9CNFR8rNc gwgBvsEyG+0LLjtWD8yLA8L4H8OLgxW27ldGo1OHQOwOMw7oyoI= =BbOc -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Source: nbclient Source-Version: 0.5.6-2 Done: Julien Puydt We believe that the bug you reported is fixed in the latest version of nbclient, 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 1000...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Julien Puydt (supplier of updated nbclient package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 26 Nov 2021 21:58:25 +0100 Source: nbclient Architecture: source Version: 0.5.6-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Julien Puydt Closes: 1000617 Changes: nbclient (0.5.6-2) unstable; urgency=medium . * Add patch to drop the jupyter-run script (Closes: #1000617). Checksums-Sha1: 123cc12cedbae86c723c2b8b2e9d4c3afd01cb23 2489 nbclient_0.5.6-2.dsc d98c47216a3af0cbb95cead36f05e4be2abbac99 4948 nbclient_0.5.6-2.debian.tar.xz c71d81002805c313590b54ca5ab1d9aaa4e228c7 9664 nbclient_0.5.6-2_source.buildinfo Checksums-Sha256: 3b344d03b50ebf3c8f0b00383ff537e7fc59ccf62830d29a271a0d4e2021154a 2489 nbclient_0.5.6-2.dsc e415639aafafe75d2b1750aed3723643df6afe394ef33e8286526885012b6eec 4948 nbclient_0.5.6-2.debian.tar.xz f7fc8b3af967431fc5d4d03e09619e8344c911fab21f94f9709205dbf7530e07 9664 nbclient_0.5.6-2_source.buildinfo Files: cf5a0e0a322ae0d3cf9558636b57ea68 2489 python optional nbclient_0.5.6-2.dsc 36b8c2ce3560226151e2e3636d7691ed 4948 python optional nbclient_0.5.6-2.debian.tar.xz 4b6f033ef7d4365750080a9aaa47d483 9664 python optional nbclient_0.5.6-2_source.bu
Bug#1000230: marked as done (screenruler fails to start)
Your message dated Fri, 26 Nov 2021 19:08:02 + with message-id and subject line Bug#1000230: fixed in screenruler 0.960+bzr41+deb10-5 has caused the Debian Bug report #1000230, regarding screenruler fails to start 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.) -- 1000230: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000230 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: screenruler Version: 0.960+bzr41+deb10-4 I use Gnome on Wayland. Reproduce: 1) Open uxterm, bash being my shell. 2) Type in screenruler and press [Enter]. 3) Observe: $ screenruler Loading libraries... Gtk-Message: 00:03:09.619: Failed to load module "canberra-gtk-module" /usr/bin/screenruler:61:in `block in ': 'Gdk::Pixbuf' has been deprecated. Use 'GdkPixbuf::Pixbuf'. /usr/lib/ruby/vendor_ruby/gdk_pixbuf2/deprecated.rb:48:in `new': GdkPixbuf::Pixbuf.new(path) is deprecated. Use GdkPixbuf::Pixbuf.new(:file => path) instead. /usr/lib/ruby/vendor_ruby/gdk_pixbuf2/deprecated.rb:48:in `new': GdkPixbuf::Pixbuf.new(path) is deprecated. Use GdkPixbuf::Pixbuf.new(:file => path) instead. /usr/lib/ruby/vendor_ruby/gdk_pixbuf2/deprecated.rb:48:in `new': GdkPixbuf::Pixbuf.new(path) is deprecated. Use GdkPixbuf::Pixbuf.new(:file => path) instead. Creating windows... Gtk-WARNING **: Unknown property: GtkWindow.has-resize-grip from /usr/share/screenruler/utils/glade_window.rb:29:in `initialize' from /usr/share/screenruler/ruler_window.rb:51:in `initialize' from /usr/bin/screenruler:76:in `new' from /usr/bin/screenruler:76:in `' Reading settings... Presenting ruler... Shutting down... $ sudo aptitude show gnome|grep Version Version: 1:3.38+3 I would be happy if I could kindly ask that my bug report finds attention. --- End Message --- --- Begin Message --- Source: screenruler Source-Version: 0.960+bzr41+deb10-5 Done: Georges Khaznadar We believe that the bug you reported is fixed in the latest version of screenruler, 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 1000...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Georges Khaznadar (supplier of updated screenruler package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 26 Nov 2021 19:41:58 +0100 Source: screenruler Architecture: source Version: 0.960+bzr41+deb10-5 Distribution: unstable Urgency: medium Maintainer: Georges Khaznadar Changed-By: Georges Khaznadar Closes: 1000230 Changes: screenruler (0.960+bzr41+deb10-5) unstable; urgency=medium . * added a dependency on ibcanberra-gtk3-module. Closes: #1000230 Checksums-Sha1: 4d141ff0f2ff063abc612eb6ef71a94403d465a1 2042 screenruler_0.960+bzr41+deb10-5.dsc f952577962859fa4c284bebc6334e122576882dd 5996 screenruler_0.960+bzr41+deb10-5.debian.tar.xz f59e921b01792af74f7e6f5257928171d1f7d6f5 6005 screenruler_0.960+bzr41+deb10-5_source.buildinfo Checksums-Sha256: b03a1d2186ed5410def71337722d71b3e587a909bfb72a25732272bc9747d5e7 2042 screenruler_0.960+bzr41+deb10-5.dsc c6c6507ead1ae4a8845ad7d14ea67b88aacfc3a7d7416ffbeff186ba20e35720 5996 screenruler_0.960+bzr41+deb10-5.debian.tar.xz f78a6f638d66caac420284ff9679fe8679fe4c86dac5843a8ee1c4b71c8fa102 6005 screenruler_0.960+bzr41+deb10-5_source.buildinfo Files: db134c03ae01d1ebf8263925097245e1 2042 gnome optional screenruler_0.960+bzr41+deb10-5.dsc aa8ffa14f248307a56be34c1b4be86dd 5996 gnome optional screenruler_0.960+bzr41+deb10-5.debian.tar.xz 239d4cfe121f18402e26a8e86508da57 6005 gnome optional screenruler_0.960+bzr41+deb10-5_source.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCAAyFiEEM0CzZP9nFT+3zK6FHCgWkHE2rjkFAmGhKpEUHGdlb3JnZXNr QGRlYmlhbi5vcmcACgkQHCgWkHE2rjnK/w/+K5pd1397hb/FeKDiVj3IUp6G67Ou lAUOOCkBuzrWqBYs0mFonka5hapw7ncpEo3aaHexuqw06mE04Yyx+CYbnvRNDOde uTDVvbiCTD1qahEoKc+w8rnSs0plK/y3xJu8VtMkpuxKOrRsnwNQy0GrLg6n/0Vu QuW9qJFk61BumkKGU8G52/MXJ3oODUyMUlJEk6Akv41lc+ZL89+sB0fIUJ5tx2OJ MHoabFYlwuDMGRBRpU2wy7WbudQ/P/ybmOmaakZ0Lg1Q5u1t07XQYYXMIB56VuwA ez9pGKQOzQsyJZXnP8YRiiJdxGsc49SwXSv79JU2g9GFFOG1DE33CrtELhNL42Xy yGOgnFGd+eWbvuJSpBwfyPlKu7wLjjtdEXCBvO+HmP8/Ltt9MMDvn3VyDKeWxPqO i+kZohIi3pl9cczUmP3e9K2DB8uUcgHJSJ0WC8xzO4v36S+FLY5uCStst
Bug#1000215:
I filed this upstream bug https://github.com/gluster/glusterfs/issues/2979 and am using this patch in Ubuntu: diff --git a/debian/rules b/debian/rules index 0e28ea8e..7bfab4c1 100755 --- a/debian/rules +++ b/debian/rules @@ -4,6 +4,12 @@ include /usr/share/dpkg/pkg-info.mk export DEB_BUILD_MAINT_OPTIONS = hardening=+all +# Fix build on these arches (LP: #1951408) (#1000215) +ifneq (,$(filter $(DEB_HOST_ARCH), armel armhf mipsel)) +DEB_CFLAGS_MAINT_APPEND = -DUATOMIC_NO_LINK_ERROR +export DEB_CFLAGS_MAINT_APPEND +endif + DEB_CONFIGURE_EXTRA_FLAGS := \ --disable-linux-io_uring --enable-firewalld --libexecdir=/usr/lib/$(DEB_HOST_MULTIARCH) We don´t built armel or mipsel in Ubuntu, but I included them in the hopes of being able to keep this package a sync.
Bug#973153: caml-crush: FTBFS: ocamlopt: OCaml has been configured with -force-safe-string: -unsafe-string is not available.
I believe this is resolved in 1.0.12-1 published in unstable but I forgot to add the *Closes* reference to the Changelog. On Fri, Aug 20, 2021 at 10:51 AM Simon Chopin wrote: > Source: caml-crush > Followup-For: Bug #973153 > > There's a PR upstream to deal with this: > > https://github.com/caml-pkcs11/caml-crush/pull/46 > > -- System Information: > Debian Release: 11.0 > APT prefers impish > APT policy: (500, 'impish'), (50, 'impish-proposed') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 5.13.0-14-generic (SMP w/8 CPU threads) > Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE > Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE > not set > Shell: /bin/sh linked to /usr/bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled >
Bug#984299: marked as done (psocksxx: ftbfs with GCC-11)
Your message dated Fri, 26 Nov 2021 17:33:54 + with message-id and subject line Bug#984299: fixed in psocksxx 1.1.1-2 has caused the Debian Bug report #984299, regarding psocksxx: 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.) -- 984299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984299 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:psocksxx Version: 1.1.1-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/psocksxx_1.1.1-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. [...] | ^ sockstreambuf.h:149:37: error: ISO C++17 does not allow dynamic exception specifications 149 | virtual int flush() throw( socktimeoutexception ); | ^ sockstreambuf.h:165:86: error: ISO C++17 does not allow dynamic exception specifications 165 | void connect( const sockaddr * dest_addr, unsigned int timeout = 0 ) throw( sockexception, socktimeoutexception ); | ^ sockstreambuf.h:181:79: error: ISO C++17 does not allow dynamic exception specifications 181 | void connect( const sockaddr * dest_addr, timeval * timeout ) throw( sockexception, socktimeoutexception ); | ^ sockstreambuf.h:195:82: error: ISO C++17 does not allow dynamic exception specifications 195 | void bind( const sockaddr * bind_addr, bool reuse_addr = false ) throw( sockexception ); | ^ sockstreambuf.h:209:56: error: ISO C++17 does not allow dynamic exception specifications 209 | void listen( int backlog = SOMAXCONN ) throw( sockexception ); |^ sockstreambuf.h:223:35: error: ISO C++17 does not allow dynamic exception specifications 223 | socket_t accept() throw( sockexception ); | ^ sockstreambuf.h:298:53: error: ISO C++17 does not allow dynamic exception specifications 298 | virtual int overflow( int c = eof ) throw( socktimeoutexception ); | ^ sockstreambuf.h:314:41: error: ISO C++17 does not allow dynamic exception specifications 314 | virtual int underflow() throw( socktimeoutexception ); | ^ sockstreambuf.h:328:94: error: ISO C++17 does not allow dynamic exception specifications 328 | bool ready( timeval * timeout, bool chk_read = true, bool chk_write = true ) throw( sockexception ); | ^ sockstreambuf.cpp:89:105: error: ISO C++17 does not allow dynam
Bug#996363: marked as done (ruby-rbpdf: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Error: test: Image get image file test(RbpdfHttpTest): NoMethodError: undefined method `shutdown' for nil:NilC
Your message dated Fri, 26 Nov 2021 16:49:55 + with message-id and subject line Bug#996363: fixed in ruby-rbpdf 1.20.1-2 has caused the Debian Bug report #996363, regarding ruby-rbpdf: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Error: test: Image get image file test(RbpdfHttpTest): NoMethodError: undefined method `shutdown' for nil:NilClass 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.) -- 996363: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996363 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-rbpdf Version: 1.20.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-rbpdf 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): > Error: test: Image get image file test(RbpdfHttpTest): NoMethodError: > undefined method `shutdown' for nil:NilClass > /<>/test/rbpdf_http_test.rb:73:in `teardown' > === > : (0.076125) > RbpdfPageTest: > test: Basic Page content test: .: (0.016013) > test: circle content: .: (0.002147) > test: viewerpreferences test: .: (0.009738) > test: write English and Persian Sunday content test:.: (0.040401) > test: write Persian Sunday content test:.: (0.018405) > test: write content RTL test: .: (0.014958) > test: write content back slash test:.: (0.010998) > test: write content test: .: (0.002775) > RbpdfTest: > test: Bidi: .: (0.003737) > test: Bidi English and Persian test:.: (0.016793) > test: Bidi Japanese test: .: (0.002068) > test: Bidi Persian Monday forcertl test:.: (0.026487) > test: Bidi Persian Monday test: .: (0.002678) > test: Bidi Persian Sunday forcertl test:.: (0.002213) > test: Bidi Persian Sunday test: .: (0.020082) > test: Bidi Persian and English test:.: (0.002842) > test: Bidi arabic test: .: (0.002191) > test: Bidi ascii colon test:.: (0.015445) > test: Bidi ascii numeric space test:.: (0.002643) > test: Bidi ascii space test:.: (0.002923) > test: Bidi date test: .: (0.018149) > test: Bidi subset font test:.: (0.001524) > test: Cell link with Close and output PDF document test:.: (0.024133) > test: Dom Basic test[Simple Text]: .: (0.010209) > test: Dom Basic test[Back Slash Text]: .: (0.001992) > test: Dom Basic test[Simple Tag]: .: (0.010288) > test: Dom Basic test[pre Tag]: .: (0.011303) > test: Dom Basic test[pre code Tag]: .: (0.002410) > test: Dom Basic test[pre code span Tag]:.: (0.010691) > test: Dom Basic test[Error Tag (doble colse tag)]: .: (0.001804) > test: Dom Basic test[Attribute]:.: (0.010585) > test: Dom Basic test[Table border]: .: (0.002507) > test: Dom Basic test[Table td Width]: .: (0.014737) > test: Dom Basic test[Dom open angled bracket "<"]: .: (0.014486) > test: Dom Basic test[Dom self close tag]: .: (0.017457) > test: Dom HTMLTagHandler Basic test:.: (0.015236) > test: Dom HTMLTagHandler DIR test[LTR]: .: (0.016512) > test: Dom HTMLTagHandler DIR test[RTL]: .: (0.016407) > test: Dom HTMLTagHandler img y position with height attribute test: E, > [2021-10-05T00:14:46.580331 #990090] ERROR -- : pdf: Image: error: RBPDF > error: Image file is not found. : /public/ng.png > .: (0.004269) > test: Dom HTMLTagHandler img y position without height attribute test:E, > [2021-10-05T00:14:46.601847 #990090] ERROR -- : pdf: Image: error: RBPDF > error: Image file is not found. : /public/ng.png > .: (0.021489) > test: Dom pre tag test: .: (0.054893) > test: Dom self
Processed: Bug#996363 marked as pending in ruby-rbpdf
Processing control commands: > tag -1 pending Bug #996363 [src:ruby-rbpdf] ruby-rbpdf: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Error: test: Image get image file test(RbpdfHttpTest): NoMethodError: undefined method `shutdown' for nil:NilClass Added tag(s) pending. -- 996363: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996363 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996363: marked as pending in ruby-rbpdf
Control: tag -1 pending
Hello,
Bug #996363 in ruby-rbpdf 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-rbpdf/-/commit/637ee7bff7b2ec4aff2e5d76ff43a7e476947126
Update packaging files
* d/control: Add Rules-Requires-Root field.
(Build-Depends): Add ruby-webrick (closes: #996363).
(Standards-Version): Bump to 4.6.0.
(Depends): Remove interpreters and use ${ruby:Depends}.
* d/copyright: Add Upstream-Contact field.
(Copyright): Add team.
* d/rules: Install upstream changelog.
* d/watch: Update file.
* d/upstream/metadata: Add missing fields.
(this message was generated automatically)
--
Greetings
https://bugs.debian.org/996363
Bug#996298: marked as done (ruby-influxdb: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Failure/Error: specify { expect(conf.proxy_port).to eq(8080) })
Your message dated Fri, 26 Nov 2021 16:21:39 +
with message-id
and subject line Bug#996298: fixed in ruby-influxdb 0.8.1-1
has caused the Debian Bug report #996298,
regarding ruby-influxdb: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed:
Failure/Error: specify { expect(conf.proxy_port).to eq(8080) }
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.)
--
996298: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996298
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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 1
Bug#999626: No need to conflict with xemacs21 here
On Thu, 25 Nov 2021 16:48:50 + Debian FTP Masters
wrote:
> We believe that the bug you reported is fixed in the latest version of
> maxima, which is due to be installed in the Debian FTP archive.
...
> maxima (5.45.1-6) unstable; urgency=medium
> .
>* maxima-emacs conflicts with xemacs21
>* reverse earlier patch attempts
>* Bug fix: "fails to install with xemacs21", thanks to Andreas Beckmann
> (Closes: #999626).
Hi, Camm,
I think that there is no need to make maxima-emacs conflict with
xemacs21, should just not be compiled for it. It is legitimate to have
xemacs21 installed for whatever reason, but use FSF Emacs for maxima
stuff.
While we are with this, I have noticed that maxima-emacs is not
bytecompiled for FSF Emacs because the emacsen-common files are
ancient and do not match current emacs handling.
Please consider attached patch, it has been minimally tested to make
maxima-emacs bytecompile for emacs but not for xemacs. It leaves the
door open to other flavors different from emacs, although I would not
expecl them (there seems to be no further xemacs deveñopment)
When bytecompiling for emacs some apparently harmless warnings are shown.
---
Install maxima-emacs for emacs
install/maxima: Handling install for emacsen flavor emacs
In toplevel form:
imaxima.el:583:1:Warning: Unused lexical argument ‘process’
imaxima.el:696:1:Warning: Unused lexical variable ‘text-prop’
imaxima.el:696:1:Warning: Unused lexical variable ‘pos’
imaxima.el:696:1:Warning: Unused lexical variable ‘label’
imaxima.el:696:1:Warning: Unused lexical variable ‘pos2’
imaxima.el:862:1:Warning: Unused lexical variable ‘imaxima-error-3’
imaxima.el:862:1:Warning: Unused lexical variable ‘imaxima-error-2’
imaxima.el:1416:1:Warning: Unused lexical variable ‘err’
imaxima.el:1416:1:Warning: Unused lexical variable ‘err’
imaxima.el:1472:1:Warning: Unused lexical variable ‘err’
imaxima.el:1472:1:Warning: Unused lexical variable ‘err’
Install maxima-emacs for xemacs21
install/maxima: Skipping byte-compilation for xemacs21
---
Regards,
--
Agustin
From 18b14e632eb26cd469754a9a41b03f0e6e66832e Mon Sep 17 00:00:00 2001
From: Agustin Martin
Date: Fri, 26 Nov 2021 16:17:23 +0100
Subject: [PATCH] Fix byte compilation with emacs and disable it for xemacs.
---
debian/control | 7 +++
debian/maxima-emacs.emacsen-install | 30 ++---
debian/maxima-emacs.emacsen-remove | 18 +++--
3 files changed, 38 insertions(+), 17 deletions(-)
diff --git a/debian/control b/debian/control
index dd74c39..eb58671 100644
--- a/debian/control
+++ b/debian/control
@@ -85,15 +85,14 @@ Description: Computer algebra system -- x interface
quite reliable, and has good garbage collection, and no memory leaks.
It comes with hundreds of self tests.
.
- This package contains an X Windows interface using the tcl/tk
- libraries.
+ This package contains an X Windows interface using the tcl/tk
+ libraries.
Package: maxima-emacs
Depends: maxima (>= ${binary:Version}), emacs-gtk | emacsen, emacsen-common (>= 1.4.14), texlive-base-bin, ${misc:Depends}, texlive-latex-recommended, maxima-doc (>= ${source:Version})
Recommends: mime-support, postscript-viewer, pdf-viewer
Architecture: all
Replaces: maxima (<< ${binary:Version})
-Conflicts: xemacs21, xemacs
Description: Computer algebra system -- emacs interface
Maxima is a fully symbolic computation program. It is full featured
doing symbolic manipulation of polynomials, matrices, rational
@@ -122,5 +121,5 @@ Description: Computer algebra system -- extra code
quite reliable, and has good garbage collection, and no memory leaks.
It comes with hundreds of self tests.
.
- This package contains a set of contributed routines and add-on
+ This package contains a set of contributed routines and add-on
packages.
diff --git a/debian/maxima-emacs.emacsen-install b/debian/maxima-emacs.emacsen-install
index 6bddd2f..04501a3 100644
--- a/debian/maxima-emacs.emacsen-install
+++ b/debian/maxima-emacs.emacsen-install
@@ -8,9 +8,24 @@
FLAVOR=$1
PACKAGE=maxima
-if [ ${FLAVOR} = emacs ]; then exit 0; fi
-
-echo install/${PACKAGE}: Handling install for emacsen flavor ${FLAVOR}
+case ${FLAVOR} in
+xemacs*)
+ # xemacs is not supported by current maxima-emacs
+ echo "install/${PACKAGE}: Skipping byte-compilation for ${FLAVOR}"
+exit 0
+;;
+emacs19|emacs20|emacs21|emacs22|emacs-snapshot*)
+# Do not byte-compile anything for above emacsen flavours
+ echo "install/${PACKAGE}: Skipping byte-compilation for ${FLAVOR}"
+exit 0
+ ;;
+emacs*)
+ echo install/${PACKAGE}: Handling install for emacsen flavor ${FLAVOR}
+ ;;
+*)
+echo install/${PACKAGE}: Ignoring emacsen flavour [${FLAVOR}]
+exit 0
+esac
SITEFLAG="-no-site-file"
FLAGS="${SITEFLAG} -q -batch -l path.el -f batch-byte-compile"
@@ -18,7 +33,7 @@ FLAGS="${SITEFLAG} -q -batch -l path.el -f batch-byte-compile"
ELDIR=/usr/
Bug#1000661: Missing b-dep on libbase64-ocaml-dev
Package: haxe Version: 1:4.1.5-1 Severity: grave I was checking whether a recent dune would break any package, and my test failed because Base64 was an unbound module -- it's a missing build-dep on libbase64-ocaml-dev, so it should be pretty straightforward to fix. Cheers, J.Puydt
Bug#1000558: Compatibility with Symfony 5
Le Wed, Nov 24, 2021 at 07:03:39PM -0400, David Prévot a écrit : > Package: php-cboden-ratchet […] > Since symfony 5 has finally been uploaded to unstable, packages now > can’t depend on php-symfony-* (<< 5) anymore. Upgrading to a new > upstream version should do the trick (Symfony 5 has been released two > years ago). Actually, the upstream package already declares proper versioned dependencies, so “rm -r debian/patches” should be the only needed step. I notice upstream provide a testsuite, it’s unfortunate that the build system doesn’t use it, nor autopkgtest, it makes it way harder for everyone to notice possible regressions (on top of Symfony 5, PHP 8.1 is on its way for example). Regards David signature.asc Description: PGP signature
Bug#1000307: marked as done (FTBFS: autopkgtest fails sue to missing socket.io module)
Your message dated Fri, 26 Nov 2021 15:07:15 + with message-id and subject line Bug#1000307: fixed in node-http-proxy 1.18.1-6 has caused the Debian Bug report #1000307, regarding FTBFS: autopkgtest fails sue to missing socket.io module 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.) -- 1000307: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000307 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: node-http-proxy Severity: serious Tags: ftbfs socket.io module is missing in autopkgtest dependencies and unavailable in Debian --- End Message --- --- Begin Message --- Source: node-http-proxy Source-Version: 1.18.1-6 Done: Roland Mas We believe that the bug you reported is fixed in the latest version of node-http-proxy, 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 1000...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Roland Mas (supplier of updated node-http-proxy 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: Wed, 24 Nov 2021 18:30:22 +0100 Source: node-http-proxy Architecture: source Version: 1.18.1-6 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Roland Mas Closes: 1000307 Changes: node-http-proxy (1.18.1-6) unstable; urgency=medium . * Document fixing of bug in previous upload. . node-http-proxy (1.18.1-5) unstable; urgency=medium . * Disable autopkgtests for now (they depend on node-socket.io, which is not available yet) (Closes: #1000307). Checksums-Sha1: ee4698253253fe86f66906c55afb76d971cec657 2351 node-http-proxy_1.18.1-6.dsc 1e9f60f7554e5740781417f73885c699d27bd5ff 2824 node-http-proxy_1.18.1-6.debian.tar.xz 42ca143532ac99e79925f4a65dae7bb73b655bbe 11705 node-http-proxy_1.18.1-6_amd64.buildinfo Checksums-Sha256: c022e18fecb81fbc20b5444777ffb6235d6016a29dbf6044c69fdeefa80007cb 2351 node-http-proxy_1.18.1-6.dsc 5459000db80fb433f41257f97e099d2116304a9b99a2ee55f512f02d068acb02 2824 node-http-proxy_1.18.1-6.debian.tar.xz 3728d6aaaf10bb0392ee1763baf6003b7ef9d93d8b3f67f178791c60e6b90101 11705 node-http-proxy_1.18.1-6_amd64.buildinfo Files: 2206cda6e2c1311b51d2470d84939b00 2351 javascript optional node-http-proxy_1.18.1-6.dsc 4188bc0ff37d26342d4f928de5defff1 2824 javascript optional node-http-proxy_1.18.1-6.debian.tar.xz f2b973da6968535b55b1275fbc5b1807 11705 javascript optional node-http-proxy_1.18.1-6_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEtBU2D1kett1zr/uD0w3s0lmTIvwFAmGg8x4ACgkQ0w3s0lmT IvzD3g//eTAVxxVe/KYi9briU4LQJC7NJVx7N45E//+63bBYWQN98xWUmhZPZlME iFlSdRGuwR4nC3t8W3wHyXYAaW4+FwZpi6YjWcmdAStUbmYoQGlSVDPT3R7rsh6U XPVVZvMKCzG94UN8bN6DSdRNgvwcNuXrzGcaRBNanAmpwqLP8vrY4qkJqt0WvSm9 nsxalicBp3R2zMwHHZa4gmslqwlPKKXHqEbByVq/FNnZSF1/CBp8br5qZ79qYcjI pHhbEUf8yXyR9NDNsOcGokn6HHVZkQAqPWFB4sXOyCD6YWTDFVZbHZGn3LHTBwKm dBysTGxuKDSOt1NivYB6Ex7G3NqCC6g87+yWg3SluDp7qPDpWNENcjFJlInPBFNt qc6YHF5PfxDvo1aKeuIyWFKnAftuOJaUKXj/UFr/Z9HGlcBYqTGnpTTn8ir8zsND d4wo+YIL9yD/hEbmoZLAKM9jvBSRGXwnyPvUzHBeOOGYHXrC6Ym2cDgTmeVfNS6E mj6GQc2RU1Y8863tu9Tst12I00CB5u+eu2mmJBPy2pml0fqRM1iR575TDnMVQVrd zCYu8h9YZtUQb+4zpUSVedBofhdbfCDONGGz3qkSCWSW2VmT9EwHmKuRxu9UoTYO +gGJKtQY3ZLFF0lV9fs33Ib0Em72OfFUsHOSz+5p3IM6u7TmdfI= =4Pvw -END PGP SIGNATURE End Message ---
Bug#1000465: marked as done (libodbc1: Missing dependency and dangling symlink)
Your message dated Fri, 26 Nov 2021 14:44:09 + with message-id and subject line Bug#1000465: fixed in unixodbc 2.3.9-3 has caused the Debian Bug report #1000465, regarding libodbc1: Missing dependency and dangling symlink 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.) -- 1000465: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000465 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libodbc1 Version: 2.3.9-2 Severity: serious Hi! Nice cleanup with the odbc packaging! Unfortunately the new transitional package looks a bit broken. It contains a dangling symlink: $ ls -la /usr/lib/x86_64-linux-gnu/libodbccr.so.1 ls: cannot access '/usr/lib/x86_64-linux-gnu/libodbccr.so.1': No such file or directory Which whould point to libodbccr.so.2. But then the package is also missing a dependency on libodbccr2. Thanks, Guillem --- End Message --- --- Begin Message --- Source: unixodbc Source-Version: 2.3.9-3 Done: Hugh McMaster We believe that the bug you reported is fixed in the latest version of unixodbc, 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 1000...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Hugh McMaster (supplier of updated unixodbc package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 26 Nov 2021 22:59:37 +1100 Source: unixodbc Architecture: source Version: 2.3.9-3 Distribution: unstable Urgency: medium Maintainer: Hugh McMaster Changed-By: Hugh McMaster Closes: 1000465 Changes: unixodbc (2.3.9-3) unstable; urgency=medium . * debian/control: libodbc1 also depends on libodbccr2 (Closes: #1000465). * debian/not-installed: Add upstream-generated odbcinst.ini file. * unixodbc-common: - Do not install odbcinst.ini as a conffile. - Add maintscripts to manage the odbcinst.ini file. Checksums-Sha1: c6e16ab9246fa79526adbf24821282d4094ee244 2330 unixodbc_2.3.9-3.dsc e848e43e160639b05b05196f6bc855ab44a0556a 19184 unixodbc_2.3.9-3.debian.tar.xz 5dde87521062d5da32cb3a80bde456f677f68924 9418 unixodbc_2.3.9-3_amd64.buildinfo Checksums-Sha256: a1ec9090c3f9b683dff4d606193170c5b843a0a97ae588e0cda25c8cd48c3175 2330 unixodbc_2.3.9-3.dsc 1aa049c1eac71bd673d778000536ad48c20a659782dfe7a0eb690e98ee70f104 19184 unixodbc_2.3.9-3.debian.tar.xz bda69ab12d66a3edcb3855e943b79f4bec4ad1f251f37c82c86265f3e7187c1f 9418 unixodbc_2.3.9-3_amd64.buildinfo Files: cad9a22363e2ae8b9adb7d99eb623b71 2330 libs optional unixodbc_2.3.9-3.dsc a9f28f7ab1e3399a18e40febadc78214 19184 libs optional unixodbc_2.3.9-3.debian.tar.xz 392ab310388077f6fdae574d99a96ca4 9418 libs optional unixodbc_2.3.9-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEi3hoeGwz5cZMTQpICBa54Yx2K60FAmGg5G4ACgkQCBa54Yx2 K63A5A/+JkpTVWz0tKXvBxcuuv4juy6RTiJew45KoRYzNKi7/OeyaBUOEx/PYnOk N8jXaWPVQoW6QwbF9HKvaufKUHagR+e4p6KvEGJsObV89Ciwv79rZe8wlScGcaq1 9mjtAxhU/+Z4P8xGGDejmvoxOmvBZLeyH2wmIBXE8YAzw57eU9mesNYfMq66qif2 c0OZFEh+L5eHAxiEhtlyVPXCv2FJhg6ITkexVweQnnXz61OshRu8Mc10YgnNynuB p4IL6Y4YJnOSjKbizxrRFEuo5aGS0Kn8mGZUkCG4l7ThYae6PE9s4cab5vsaqmhr RJX30iKuJm20dwes5WZFPOTCcpvldgS806aoSJkJI3cw0pSHUDLUMEPsfoOCey/f QMY8CaAJ5yVHICq6sR7s4m+L60jPNRQfLWCm51o9XMZncanstpbqGJ8jYwEsuqqF ciA8S55XORg0ucenrlJ8c8YqtKe3as8GIPhbrnuq73UM0UGDtzQYJd56lSE4WuHb kQEfNznv+NN+RzX98kmmucEWbTWuerdEY6wQsm8YvGybNxReOh6OUnmGxqTHKwIs mO1rGgUsYShZqIeQMlCz90KhA+mxXBJOxfxFagRxlqP5X/5HZI9I5spVYsHlCySi RUISBnwEeFqny+YSdFgClReD0ceclUXzszZKLrbJoTk2CJiDRvc= =B+Ew -END PGP SIGNATURE End Message ---
Processed: closing 996403
Processing commands for cont...@bugs.debian.org: > close 996403 Bug #996403 [src:ruby-rails-controller-testing] ruby-rails-controller-testing: FTBFS: ERROR: Test "ruby3.0" failed. Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 996403: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996403 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: merge RPM armhf bugs
Processing commands for cont...@bugs.debian.org:
> package rpm
Limiting to bugs with field 'package' containing at least one of 'rpm'
Limit currently set to 'package':'rpm'
> severity 968487 serious
Bug #968487 [rpm] rpm returns wrong %{_target}
Severity set to 'serious' from 'important'
> merge 968487 1000467
Bug #968487 [rpm] rpm returns wrong %{_target}
Bug #968487 [rpm] rpm returns wrong %{_target}
Marked as found in versions rpm/4.17.0+dfsg1-1.
Bug #1000467 [rpm] rpm, autopkgtest failure on armhf
Marked as found in versions rpm/4.14.2.1+dfsg1-1.
Merged 968487 1000467
> tag 968487 + confirmed pending
Bug #968487 [rpm] rpm returns wrong %{_target}
Bug #1000467 [rpm] rpm, autopkgtest failure on armhf
Added tag(s) pending and confirmed.
Added tag(s) pending and confirmed.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1000467: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000467
968487: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968487
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#999907: libglobalarrays-dev,libga-dev: both ship /usr/lib/x86_64-linux-gnu/libga.a
X-Debbugs-CC: mba...@debian.org debichem-de...@lists.alioth.debian.org Hi, My personal preference would be implementing mutual conflict. Michael: Please let me know whether this works for you. I can make an NMU to implement mutual conflic for src:ga if you find it necessary. -- Thanks, Boyuan Yang On Thu, 18 Nov 2021 11:20:50 +0100 Andreas Beckmann wrote: > Package: libglobalarrays-dev,libga-dev > Severity: serious > Tags: sid bookworm > User: trei...@debian.org > Usertags: edos-file-overwrite > Control: found -1 5.7.2-2 > Control: found -1 1:2.4.7-5 > > Hi, > > automatic installation tests of packages that share a file and at the > same time do not conflict by their package dependency relationships has > detected the following problem: > > Preparing to unpack .../libga-dev_1%3a2.4.7-5_amd64.deb ... > Unpacking libga-dev:amd64 (1:2.4.7-5) ... > dpkg: error processing archive /var/cache/apt/archives/libga- dev_1%3a2.4.7-5_amd64.deb (--unpack): > trying to overwrite '/usr/lib/x86_64-linux-gnu/libga.a', which is also in package libglobalarrays-dev 5.7.2-2 > dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) > Errors were encountered while processing: > /var/cache/apt/archives/libga-dev_1%3a2.4.7-5_amd64.deb > > This is a serious bug as it makes installation fail, and violates > sections 7.6.1 and 10.1 of the policy. An optimal solution would > consist in only one of the packages installing that file, and renaming > or removing the file in the other package. Depending on the > circumstances you might also consider Replace relations or file > diversions. If the conflicting situation cannot be resolved then, as a > last resort, the two packages have to declare a mutual > Conflict. Please take into account that Replaces, Conflicts and > diversions should only be used when packages provide different > implementations for the same functionality. > > Here is a list of files that are known to be shared by both packages > (according to the Contents file for sid/amd64, which may be > slightly out of sync): > > /usr/lib/x86_64-linux-gnu/libga.a > > This bug is assigned to both packages. If you, the maintainers of > the two packages in question, have agreed on which of the packages will > resolve the problem please reassign the bug to that package. You may > also register in the BTS that the other package is affected by the bug. > > > libglobalarrays-dev does have one reverse build-dependency: nwchem. > libga-dev does have none. > > PS: for more information about the detection of file overwrite errors > of this kind see https://qa.debian.org/dose/file-overwrites.html signature.asc Description: This is a digitally signed message part
Processed: ruby-jaeger-client FTBFS on IPV6-only buildds
Processing control commands:
> block 998006 by -1
Bug #998006 {Done: Paul Gevers } [src:ruby-jaeger-client]
src:ruby-jaeger-client: fails to migrate to testing for too long: unresolved RC
bug
998006 was blocked by: 996300
998006 was not blocking any bugs.
Added blocking bug(s) of 998006: 1000649
--
1000649: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000649
998006: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998006
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1000649: ruby-jaeger-client FTBFS on IPV6-only buildds
Source: ruby-jaeger-client Version: 1.2.0-1 Severity: serious Tags: ftbfs Control: block 998006 by -1 https://buildd.debian.org/status/logs.php?pkg=ruby-jaeger-client&arch=all ... Failures: 1) Jaeger::Encoders::ThriftEncoder without custom tags has ip Failure/Error: expect(ip_tag.vStr).to be_a(String) NoMethodError: undefined method `vStr' for nil:NilClass # ./spec/jaeger/encoders/thrift_encoder_spec.rb:40:in `block (3 levels) in ' Finished in 0.30993 seconds (files took 0.58969 seconds to load) 187 examples, 1 failure ... Same problem in reproducible builds: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ruby-jaeger-client.html
Processed: block 998006 with 996300
Processing commands for cont...@bugs.debian.org:
> block 998006 with 996300
Bug #998006 {Done: Paul Gevers } [src:ruby-jaeger-client]
src:ruby-jaeger-client: fails to migrate to testing for too long: unresolved RC
bug
998006 was not blocked by any bugs.
998006 was not blocking any bugs.
Added blocking bug(s) of 998006: 996300
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
998006: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998006
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#981680 closed by Debian FTP Masters (reply to Mathias Gibbens ) (Bug#981680: fixed in golang-github-canonical-go-dqlite 1.10.
Processing control commands:
> reopen -1
Bug #981680 {Done: Mathias Gibbens }
[src:golang-github-canonical-go-dqlite] golang-github-canonical-go-dqlite
FTBFS: test failures
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions
golang-github-canonical-go-dqlite/1.10.1-1.
--
981680: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981680
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#981680: closed by Debian FTP Masters (reply to Mathias Gibbens ) (Bug#981680: fixed in golang-github-canonical-go-dqlite 1.10.1-1)
Control: reopen -1 On Fri, Nov 26, 2021 at 12:21:09PM +, Debian Bug Tracking System wrote: >... > golang-github-canonical-go-dqlite (1.10.1-1) unstable; urgency=medium >... >* Add patches to fix tests (Closes: #981680) >... Unfortunately this does not seem to be sufficient: https://buildd.debian.org/status/logs.php?pkg=golang-github-canonical-go-dqlite&ver=1.10.1-1 cu Adrian
Bug#994365: marked as done (python-pylibacl: Removal of the python3-*-dbg packages in sid/bookworm)
Your message dated Fri, 26 Nov 2021 12:34:04 + with message-id and subject line Bug#994365: fixed in python-pylibacl 0.6.0-2 has caused the Debian Bug report #994365, regarding python-pylibacl: Removal of the python3-*-dbg packages in sid/bookworm 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.) -- 994365: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994365 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-pylibacl Version: 0.6.0-1 Severity: serious Tags: sid bookworm User: debian-pyt...@lists.debian.org Usertags: pydbg-removal Python 3.8 upstream now has a common ABI for normal and debug extension builds, so we can drop the python3-*-dbg packages. Details at https://lists.debian.org/debian-python/2021/09/msg4.html Stop building the python3-*-dbg package, but be careful that all the reverse dependencies are also removed. Please check for dependencies, build dependencies AND autopkg tests. If help is needed, please ask on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: python-pylibacl Source-Version: 0.6.0-2 Done: Iustin Pop We believe that the bug you reported is fixed in the latest version of python-pylibacl, 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. Iustin Pop (supplier of updated python-pylibacl package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 26 Nov 2021 13:13:53 +0100 Source: python-pylibacl Architecture: source Version: 0.6.0-2 Distribution: unstable Urgency: medium Maintainer: Iustin Pop Changed-By: Iustin Pop Closes: 994365 Changes: python-pylibacl (0.6.0-2) unstable; urgency=medium . [ Debian Janitor ] * Remove constraints unnecessary since buster: + python-pylibacl-doc: Drop versioned constraint on python-pylibacl in Replaces. + python-pylibacl-doc: Drop versioned constraint on python-pylibacl in Breaks. . [ Iustin Pop ] * Drop the debug package; no reverse dependencies, so this is straightforward (Closes: #994365). * Bump standards version (no changes). Checksums-Sha1: 6a042410efa0c42e74ebcce7a133de87f82c8cca 2409 python-pylibacl_0.6.0-2.dsc b02a622e71de03ea59ca9d7d86e7aa55e39a5211 8928 python-pylibacl_0.6.0-2.debian.tar.xz f3f664bae7c9a36857c508d082a942042a80d402 8905 python-pylibacl_0.6.0-2_source.buildinfo Checksums-Sha256: 7adf6f8842c2e01995dc817ea5f1cbb32572ae64e4385af00d1abe8108280d5e 2409 python-pylibacl_0.6.0-2.dsc 3bace19eaee1ee4763d2cf9170e2ad56964ecd53ee0166db6a6d3734b7e59765 8928 python-pylibacl_0.6.0-2.debian.tar.xz d5ca98c5bfdad0e1b38abdf2967cd1b471a6c39f79220ca06ab40e9c4dd224c1 8905 python-pylibacl_0.6.0-2_source.buildinfo Files: 6a82967e4c9d41be4c28470dc2debadb 2409 python optional python-pylibacl_0.6.0-2.dsc 72d540c00763a2886b52e8df9bbf97ce 8928 python optional python-pylibacl_0.6.0-2.debian.tar.xz 8d3f95dc889f6e939597a92074995f4f 8905 python optional python-pylibacl_0.6.0-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEy5TjqjsXVdYeuxml9m4+QZ+E9N4FAmGg0UESHGl1c3RpbkBk ZWJpYW4ub3JnAAoJEPZuPkGfhPTeclsP/ApQfIKwhuxmpQHjx3ikds15cJmm7NDF GpGnBTcLujzElvmzqp5WDqExLM9sA+s8BVUXrDFHvkZRZifXZmADsYPkMIva1BUv 0ABfGZCUjef3OUVhNfceBH3QHbKTj9FsDADrXD4f6ky9VfrQypsiUFwwfRX4oYbx KpgvTkopBOe8Jr14i+j2+tB6Ta1xAKNX4fGGq3PbVc7gKoV8ZWPND2MhojzVfWu6 UZpOubZS908HWGtAktWt8GSDZwBT1OhUansTmCpjBjpgNBwkM14b8JdUADaCKIkr 2zXCVE/Xl76h6tQj80GzmouYHhdWYF0pNt18Jmzm5Q6ZPKBT8+j+ENZBAgcvwp5m u01an/rdwsBAl2pyoZ/ffHWi888eWjN12Vw2BbCHyPlfriPx7xzaVXS+q93Go170 RZJrWhlsGK7dZQ4VCKAseNGTIgT25lqR2n9MES6nqHc3njS8bpaoHGS0jRHXv1e/ k7UbxnA7acVaZ2gAZUpERPRp/vnLJ4obNmlUjQGXYMmaWLhH710ipGzIxHn5VFnW lMEdRY9E7fVtBUCuQPrGzH9g1G1hRdp7UUCgIw06ImxnrOPx0s4exNwgU9ESwEKF 8fGmFZS5e2TockVypyjkPjGfxM3aZ8jQk1NEOVRgObV1Ka4JHmRSWTmaph3yC/pq fgC2ekVGyMHQ =UkhQ -END PGP SIGNATURE End Message ---
Bug#981680: marked as done (golang-github-canonical-go-dqlite FTBFS: test failures)
Your message dated Fri, 26 Nov 2021 12:18:43 + with message-id and subject line Bug#981680: fixed in golang-github-canonical-go-dqlite 1.10.1-1 has caused the Debian Bug report #981680, regarding golang-github-canonical-go-dqlite FTBFS: 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.) -- 981680: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981680 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: golang-github-canonical-go-dqlite Version: 1.8.0-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=golang-github-canonical-go-dqlite https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-github-canonical-go-dqlite.html ... --- FAIL: TestRolesAdjustment_ReplaceVoterHonorWeight (9.69s) ... --- FAIL: TestRolesAdjustment_ReplaceStandBy (11.18s) ... --- FAIL: TestRolesAdjustment_ReplaceStandByHonorFailureDomains (15.04s) ... --- FAIL: TestMembership (1.08s) ... --- FAIL: TestConnector_DialTimeout (0.20s) ... --- FAIL: TestConnector_ContextCanceled (0.20s) ... --- End Message --- --- Begin Message --- Source: golang-github-canonical-go-dqlite Source-Version: 1.10.1-1 Done: Mathias Gibbens We believe that the bug you reported is fixed in the latest version of golang-github-canonical-go-dqlite, 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 981...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mathias Gibbens (supplier of updated golang-github-canonical-go-dqlite package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 26 Nov 2021 12:51:47 +0100 Source: golang-github-canonical-go-dqlite Architecture: source Version: 1.10.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Go Packaging Team Changed-By: Mathias Gibbens Closes: 981680 Changes: golang-github-canonical-go-dqlite (1.10.1-1) unstable; urgency=medium . * New upstream release * d/control: - Add myself to Uploaders - Declare compliance with Debian Policy 4.6.0 (no change) - Update Section to golang - Update Build-Depends and Depends * Update d/rules to set CGO_LDFLAGS_ALLOW * Add patches to fix tests (Closes: #981680) Checksums-Sha1: c48c90f4a007903dbcd1c84afef49feada76b255 2745 golang-github-canonical-go-dqlite_1.10.1-1.dsc 08548b49d6e8a17d9b284616682f4a1684cb8716 104180 golang-github-canonical-go-dqlite_1.10.1.orig.tar.gz 6dc101cfeb49fa43db333182fcff020474f52e8e 4496 golang-github-canonical-go-dqlite_1.10.1-1.debian.tar.xz 0be5b3f18122e951bd3544c6b3010b17453a50b0 9067 golang-github-canonical-go-dqlite_1.10.1-1_amd64.buildinfo Checksums-Sha256: 1ef9ebdc772eac1b829689c86643cc13e797f55dbaf1e622f8a178971d3c8d1d 2745 golang-github-canonical-go-dqlite_1.10.1-1.dsc c41b726eceac5d01d5f5836c3506c1b367385ec0523851ebef1a35d9287e4b01 104180 golang-github-canonical-go-dqlite_1.10.1.orig.tar.gz 7533cb219dd47f74adcda7e8e37f2fe4ecd947c88138fd8de1fd76ef4395c69a 4496 golang-github-canonical-go-dqlite_1.10.1-1.debian.tar.xz 132b057a6f80c29c3b5da70b2f5119d4039326d0395c9ac545b3f64971e03a5b 9067 golang-github-canonical-go-dqlite_1.10.1-1_amd64.buildinfo Files: 4462c8ba1d10c557374bb6999073a93c 2745 golang optional golang-github-canonical-go-dqlite_1.10.1-1.dsc 255abb58b1ce5e66a7495e336c80a345 104180 golang optional golang-github-canonical-go-dqlite_1.10.1.orig.tar.gz ceec4f12a6eed171e92ae4051060c7ca 4496 golang optional golang-github-canonical-go-dqlite_1.10.1-1.debian.tar.xz d0bee9622b8517db192260f49a52800b 9067 golang optional golang-github-canonical-go-dqlite_1.10.1-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCgAuFiEECYc16JDXWgmzZBaOGg64LwcfXv4FAmGgy2cQHGFsb2lzQG1p Y2FyZC5sdQAKCRAaDrgvBx9e/pcoD/9EscWKI2DfZ40Oq54wwoykfQK8OI2pyeIW VJGRRINgyCeRkpbdkWnTapYjUWmEI2GBDjgToW9yv2KxABNbxptyI9NOYWzEiwp3 dQ/4uMJNU14o/6j7SWTSq4CuORggthtTZFw5kbe4dOxMyvzU8tIbcRmPlNF3mf43 YtfUeL6kw+18VEeqT/s2UOGAwYmj2fEFP+50kMXHoQ7hLl8tCwv3U1Lo1AqjQxrb /MQLlSbKCX2KSQlERZxNi6egbS2Gb/k9avTrOP2KyVesCu2/pMVJL6y0jKNU6dDp yDBodNqDOM6JZFrGGEZhALj1PjXA7mzPNvOPryYYjW2FRhX8VVtfO9gurGb2oChW 8TdrrbkMZKfR+Z/eaf/v+0eGcssC0Mkj8rJyeR4rG7WPqPc6tgEVWbeW+jHlm2
Bug#996806: [Pkg-mailman-hackers] Bug#996806: mailmain3: Expected test results for arc_validate tests need updating
Le 26 novembre 2021 12:42:23 GMT+01:00, Jordi Mallach a écrit : >Hi Pierre-Elliott! > >El dj. 25 de 11 de 2021 a les 22:19 +0100, en/na Pierre-Elliott Bécue >va escriure: >> > I might try to work on a fix in the following days, most probably >> > including an update to the latest version, which includes other >> > fixes I >> > need. >> >> I'm waiting for some stuck dependencies issues to solve to batch a >> full >> update of mailman3. > >Sounds great! Do you have a list of missing deps? > >-- >Jordi Mallach >Debian Project > Mistune 2.0.0rc1 which hyperkitty depends on but which car't be included until it is a full release instead of a rc. -- Pierre-Elliott Bécue From my phone
Bug#996806: [Pkg-mailman-hackers] Bug#996806: mailmain3: Expected test results for arc_validate tests need updating
Hi Pierre-Elliott! El dj. 25 de 11 de 2021 a les 22:19 +0100, en/na Pierre-Elliott Bécue va escriure: > > I might try to work on a fix in the following days, most probably > > including an update to the latest version, which includes other > > fixes I > > need. > > I'm waiting for some stuck dependencies issues to solve to batch a > full > update of mailman3. Sounds great! Do you have a list of missing deps? -- Jordi Mallach Debian Project
Bug#855837: marked as done (golang-petname: should this be in bullseye)
Your message dated Fri, 26 Nov 2021 11:18:54 + with message-id and subject line Bug#855837: fixed in golang-petname 2.11~git20191129.8e5a1ed-1 has caused the Debian Bug report #855837, regarding golang-petname: should this be in bullseye 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.) -- 855837: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855837 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: golang-petname Severity: serious I uploaded this as a dependency of LXD which unfortunately we did not finish packaging in time for the Stretch freeze. As such, unless someone else is prepared to help support it, and/or users of this package come out of the woodwork, I do not think we should include this library in Stretch. -- Jonathan Dowland signature.asc Description: Digital signature --- End Message --- --- Begin Message --- Source: golang-petname Source-Version: 2.11~git20191129.8e5a1ed-1 Done: Mathias Gibbens We believe that the bug you reported is fixed in the latest version of golang-petname, 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 855...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mathias Gibbens (supplier of updated golang-petname package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 26 Nov 2021 11:58:17 +0100 Source: golang-petname Architecture: source Version: 2.11~git20191129.8e5a1ed-1 Distribution: unstable Urgency: medium Maintainer: Debian Go Packaging Team Changed-By: Mathias Gibbens Closes: 855837 Changes: golang-petname (2.11~git20191129.8e5a1ed-1) unstable; urgency=medium . [ Mathias Gibbens ] * New upstream snapshot * Adopt this package, as LXD is coming to Debian (Closes: #855837) * d/control - Update Go Team's email address in Maintainer field - Add myself to Uploaders - Update Section to golang - Add Testsuite: autopkgtest-pkg-go - Update Build-Depends and Depends - Bump Standards-Version (no changes needed) - Add Rules-Requires-Root: no * Cleanup d/copyright * Add d/gbp.conf * Update d/golang-github-dustinkirkland-golang-petname-dev.install * Delete d/lintian-overrides * Refresh d/rules * Update d/upstream/metadata * Add d/watch . [ Alexandre Viau ] * Point Vcs-* urls to salsa.debian.org. . [ Jonathan Dowland ] * Remove myself from Uploaders. . [ Debian Janitor ] * Use secure copyright file specification URI * Bump debhelper from deprecated 9 to 12 * Set debhelper-compat version in Build-Depends * Change priority extra to priority optional * Set upstream metadata fields: Repository, Repository-Browse * Apply multi-arch hints Checksums-Sha1: 0e03739afa54a1251a93d3572de4cb3fb4baf5bc 2402 golang-petname_2.11~git20191129.8e5a1ed-1.dsc a81c84692502a6dd3b1c7db933ec7dd8e4d52f06 13976 golang-petname_2.11~git20191129.8e5a1ed.orig.tar.xz 687a21931a898e90fc514634695eb78f275ae1c5 5540 golang-petname_2.11~git20191129.8e5a1ed-1.debian.tar.xz cf9cc7704c0100fc78e414d53c3f46b197f638c6 6814 golang-petname_2.11~git20191129.8e5a1ed-1_amd64.buildinfo Checksums-Sha256: 5799c5497ca7f90b048c7503ae142b58c70c9ac2f07038bf31a0793f67e9d7de 2402 golang-petname_2.11~git20191129.8e5a1ed-1.dsc d05156cc02138f0b0e1a10c1250dce355bfc943b7eb5bce24b6fcafd2d150702 13976 golang-petname_2.11~git20191129.8e5a1ed.orig.tar.xz 8a01ddb55916a749352e5178bf642f34593247b122044138583b0fd87e1c7235 5540 golang-petname_2.11~git20191129.8e5a1ed-1.debian.tar.xz 2768f36f6256992f25eeb324795569aa35a66b4c054f0f8b72462c438d46e9f5 6814 golang-petname_2.11~git20191129.8e5a1ed-1_amd64.buildinfo Files: 962ed4a72e14e1272feef38aa01719d1 2402 golang optional golang-petname_2.11~git20191129.8e5a1ed-1.dsc a9ed09dd2e7a9489cc02a66c26293bff 13976 golang optional golang-petname_2.11~git20191129.8e5a1ed.orig.tar.xz 087a5fe45b54cc85c19ce9f2083f4f2d 5540 golang optional golang-petname_2.11~git20191129.8e5a1ed-1.debian.tar.xz e06a77df7c1c9146982c0a0ef0b59e3b 6814 golang optional golang-petname_2.11~git20191129.8e5a1ed-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCgAuFiEECYc16JDX
Bug#995625: httping FTBFS: error: format not a string literal and no format arguments [-Werror=format-security]
It's on https://github.com/folkertvanheusden/HTTPing > Would it be possible to either have the URL of the upstream VCS or a > proper patch file for 4ea9d5b78540c972e3fe1bf44db9f7b3f87c0ad0? > I couldn't find any mention of a VCS on the homepage, only tarballs.
Bug#995625: httping FTBFS: error: format not a string literal and no format arguments [-Werror=format-security]
Hi, Would it be possible to either have the URL of the upstream VCS or a proper patch file for 4ea9d5b78540c972e3fe1bf44db9f7b3f87c0ad0? I couldn't find any mention of a VCS on the homepage, only tarballs. Thanks in advance, Cheers -- Simon Chopin Foundations Team Ubuntu MOTU simon.cho...@canonical.comscho...@ubuntu.com
Processed: tagging 1000635
Processing commands for cont...@bugs.debian.org: > tags 1000635 + ftbfs Bug #1000635 [node-monocle] node-monocle is incompatible with current node-readdirp Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1000635: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000635 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000637: php-facedetect FTBFS: Package not converted to dh-php >= 4
Source: php-facedetect Version: 1.1.0-19-g135c72a-2 Severity: serious Tags: ftbfs bookworm sid https://buildd.debian.org/status/logs.php?pkg=php-facedetect&ver=1.1.0-19-g135c72a-2%2Bb1 ... dh_clean /usr/share/dh-php/gen-control Package not converted to dh-php >= 4 make[1]: *** [/usr/share/dh-php/pkg-pecl.mk:72: override_dh_clean] Error 1
Bug#999764: marked as done (gcc-12: file conflicts with gcc-11 due to missing Breaks+Replaces or renaming)
Your message dated Fri, 26 Nov 2021 09:33:41 + with message-id and subject line Bug#999764: fixed in gcc-12 12-20211126-1 has caused the Debian Bug report #999764, regarding gcc-12: file conflicts with gcc-11 due to missing Breaks+Replaces or renaming 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.) -- 999764: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999764 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gcc-12 Version: 12-2023-1 Severity: serious To avoid repeating this bug on every new major upstrema release, I'd suggest to add Conflicts+Replaces+Provides: some-new-virtual-package to all intentionally not co-installable packages in addition to the Breaks+Replaces that is needed now. File conflicts with src:gcc-11: gcc-12-locales: usr/share/locale/be/LC_MESSAGES/cpplib-11.mo usr/share/locale/be/LC_MESSAGES/gcc-11.mo usr/share/locale/ca/LC_MESSAGES/cpplib-11.mo usr/share/locale/da/LC_MESSAGES/cpplib-11.mo usr/share/locale/da/LC_MESSAGES/gcc-11.mo usr/share/locale/de/LC_MESSAGES/cpplib-11.mo usr/share/locale/de/LC_MESSAGES/gcc-11.mo usr/share/locale/el/LC_MESSAGES/cpplib-11.mo usr/share/locale/el/LC_MESSAGES/gcc-11.mo usr/share/locale/eo/LC_MESSAGES/cpplib-11.mo usr/share/locale/es/LC_MESSAGES/cpplib-11.mo usr/share/locale/es/LC_MESSAGES/gcc-11.mo usr/share/locale/fi/LC_MESSAGES/cpplib-11.mo usr/share/locale/fi/LC_MESSAGES/gcc-11.mo usr/share/locale/fr/LC_MESSAGES/cpplib-11.mo usr/share/locale/fr/LC_MESSAGES/gcc-11.mo usr/share/locale/hr/LC_MESSAGES/gcc-11.mo usr/share/locale/id/LC_MESSAGES/cpplib-11.mo usr/share/locale/id/LC_MESSAGES/gcc-11.mo usr/share/locale/ja/LC_MESSAGES/cpplib-11.mo usr/share/locale/ja/LC_MESSAGES/gcc-11.mo usr/share/locale/nl/LC_MESSAGES/cpplib-11.mo usr/share/locale/nl/LC_MESSAGES/gcc-11.mo usr/share/locale/pt_BR/LC_MESSAGES/cpplib-11.mo usr/share/locale/ru/LC_MESSAGES/cpplib-11.mo usr/share/locale/ru/LC_MESSAGES/gcc-11.mo usr/share/locale/sr/LC_MESSAGES/cpplib-11.mo usr/share/locale/sr/LC_MESSAGES/gcc-11.mo usr/share/locale/sv/LC_MESSAGES/cpplib-11.mo usr/share/locale/sv/LC_MESSAGES/gcc-11.mo usr/share/locale/tr/LC_MESSAGES/cpplib-11.mo usr/share/locale/tr/LC_MESSAGES/gcc-11.mo usr/share/locale/uk/LC_MESSAGES/cpplib-11.mo usr/share/locale/uk/LC_MESSAGES/gcc-11.mo usr/share/locale/vi/LC_MESSAGES/cpplib-11.mo usr/share/locale/vi/LC_MESSAGES/gcc-11.mo usr/share/locale/zh_CN/LC_MESSAGES/cpplib-11.mo usr/share/locale/zh_CN/LC_MESSAGES/gcc-11.mo usr/share/locale/zh_TW/LC_MESSAGES/cpplib-11.mo usr/share/locale/zh_TW/LC_MESSAGES/gcc-11.mo gnat-12: usr/bin/gnat usr/bin/gnatbind usr/bin/gnatchop usr/bin/gnatclean usr/bin/gnatgcc usr/bin/gnathtml usr/bin/gnatkr usr/bin/gnatlink usr/bin/gnatls usr/bin/gnatmake usr/bin/gnatname usr/bin/gnatprep usr/bin/x86_64-linux-gnu-gnat usr/bin/x86_64-linux-gnu-gnatbind usr/bin/x86_64-linux-gnu-gnatchop usr/bin/x86_64-linux-gnu-gnatclean usr/bin/x86_64-linux-gnu-gnatgcc usr/bin/x86_64-linux-gnu-gnathtml usr/bin/x86_64-linux-gnu-gnatkr usr/bin/x86_64-linux-gnu-gnatlink usr/bin/x86_64-linux-gnu-gnatls usr/bin/x86_64-linux-gnu-gnatmake usr/bin/x86_64-linux-gnu-gnatname usr/bin/x86_64-linux-gnu-gnatprep usr/lib/x86_64-linux-gnu/libgnarl.so usr/lib/x86_64-linux-gnu/libgnat.so usr/share/man/man1/gnat.1.gz usr/share/man/man1/gnatbind.1.gz usr/share/man/man1/gnatchop.1.gz usr/share/man/man1/gnatclean.1.gz usr/share/man/man1/gnathtml.1.gz usr/share/man/man1/gnatkr.1.gz usr/share/man/man1/gnatlink.1.gz usr/share/man/man1/gnatls.1.gz usr/share/man/man1/gnatmake.1.gz usr/share/man/man1/gnatname.1.gz usr/share/man/man1/gnatprep.1.gz usr/share/man/man1/x86_64-linux-gnu-gnat.1.gz usr/share/man/man1/x86_64-linux-gnu-gnatbind.1.gz usr/share/man/man1/x86_64-linux-gnu-gnatchop.1.gz usr/share/man/man1/x86_64-linux-gnu-gnatclean.1.gz usr/share/man/man1/x86_64-linux-gnu-gnathtml.1.gz usr/share/man/man1/x86_64-linux-gnu-gnatkr.1.gz usr/share/man/man1/x86_64-linux-gnu-gnatlink.1.gz usr/share/man/man1/x86_64-linux-gnu-gnatls.1.gz usr/share/man/man1/x86_64-linux-gnu-gnatmake.1.gz usr/share/man/man1/x86_64-linux-gnu-gnatname.1.gz usr/share/man/man1/x86_64-linux-gnu-gnatprep.1.gz libstdc++6-12-dbg: usr/lib/x86_64-linux-gnu/debug/libstdc++.a usr/lib/x86_64-linux-gnu/debug/libstdc++.so usr/lib/x86_64-linux-gnu/debug/libstdc++.so.6 usr/lib/x86_64-linux-gnu/debug/libstdc++fs.a lib32stdc++6-12-dbg: usr/lib32/debug/libstdc++.a usr/lib32/debug/libstdc++.so usr/lib32/debug/libstdc++.so.6 usr/lib32/debug/libstdc++fs.a libx32stdc++6-12-dbg: usr/libx32/debug/libstdc++.a usr/libx32/debug/libstdc++.so usr/libx32/debug/libstdc++.so.
Bug#1000636: caffe FTBFS: test failures
Source: caffe Version: 1.0.0+git20180821.99bd997-8 Severity: serious Tags: ftbfs bookworm sid https://buildd.debian.org/status/logs.php?pkg=caffe&ver=1.0.0%2Bgit20180821.99bd997-8%2Bb3 ... == ERROR: test_coord_map (unittest.loader._FailedTest) -- ImportError: Failed to import test module: test_coord_map Traceback (most recent call last): File "/usr/lib/python3.9/unittest/loader.py", line 436, in _find_test_path module = self._get_module_from_name(name) File "/usr/lib/python3.9/unittest/loader.py", line 377, in _get_module_from_name __import__(name) File "/<>/python/caffe/test/test_coord_map.py", line 6, in import caffe File "/<>/python/caffe/__init__.py", line 1, in from .pycaffe import Net, SGDSolver, NesterovSolver, AdaGradSolver, RMSPropSolver, AdaDeltaSolver, AdamSolver, NCCL, Timer File "/<>/python/caffe/pycaffe.py", line 13, in from ._caffe import Net, SGDSolver, NesterovSolver, AdaGradSolver, \ SystemError: initialization of _caffe raised unreported exception ...
Bug#1000635: node-monocle is incompatible with current node-readdirp
Package: node-monocle Version: 1.1.51+dfsg-1.1 Severity: grave Tags: upstream Justification: renders package unusable Enabling test proves that this package is broken. Since it is used only by deprecated node-jade, I'll ask a ROM-RM instead of searching a solution (not trivial).
Bug#1000625: marked as done (libopencv-dev: Broken pkg-config file)
Your message dated Fri, 26 Nov 2021 09:18:44 + with message-id and subject line Bug#1000625: fixed in opencv 4.5.4+dfsg-7 has caused the Debian Bug report #1000625, regarding libopencv-dev: Broken pkg-config file to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1000625: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000625 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libopencv-dev Version: 4.5.4+dfsg-6 Severity: serious https://buildd.debian.org/status/logs.php?pkg=mrgingham&ver=1.20-3%2Bb1 ... g++ -Wl,-z,relro -Wl,-z,now -shared -Wl,--default-symver -fPIC -Wl,-soname,libmrgingham.so.2 find_grid.o find_blobs.o find_chessboard_corners.o mrgingham.o ChESS.o -llibopencv_stitching.so.4.5.4d -llibopencv_alphamat.so.4.5.4d -llibopencv_aruco.so.4.5.4d -llibopencv_barcode.so.4.5.4d -llibopencv_bgsegm.so.4.5.4d -llibopencv_bioinspired.so.4.5.4d -llibopencv_ccalib.so.4.5.4d -llibopencv_dnn_objdetect.so.4.5.4d -llibopencv_dnn_superres.so.4.5.4d -llibopencv_dpm.so.4.5.4d -llibopencv_face.so.4.5.4d -llibopencv_freetype.so.4.5.4d -llibopencv_fuzzy.so.4.5.4d -llibopencv_hdf.so.4.5.4d -llibopencv_hfs.so.4.5.4d -llibopencv_img_hash.so.4.5.4d -llibopencv_intensity_transform.so.4.5.4d -llibopencv_line_descriptor.so.4.5.4d -llibopencv_mcc.so.4.5.4d -llibopencv_quality.so.4.5.4d -llibopencv_rapid.so.4.5.4d -llibopencv_reg.so.4.5.4d -llibopencv_rgbd.so.4.5.4d -llibopencv_saliency.so.4.5.4d -llibopencv_shape.so.4.5.4d -llibopencv_stereo.so.4.5.4d -llibopencv_structured_light.so.4.5.4d -llibopencv_phase_unwrapping.so.4.5.4d -llibopencv_superres.so.4.5.4d -llibopencv_optflow.so.4.5.4d -llibopencv_surface_matching.so.4.5.4d -llibopencv_tracking.so.4.5.4d -llibopencv_highgui.so.4.5.4d -llibopencv_datasets.so.4.5.4d -llibopencv_text.so.4.5.4d -llibopencv_plot.so.4.5.4d -llibopencv_ml.so.4.5.4d -llibopencv_videostab.so.4.5.4d -llibopencv_videoio.so.4.5.4d -llibopencv_viz.so.4.5.4d -llibopencv_wechat_qrcode.so.4.5.4d -llibopencv_ximgproc.so.4.5.4d -llibopencv_video.so.4.5.4d -llibopencv_xobjdetect.so.4.5.4d -llibopencv_objdetect.so.4.5.4d -llibopencv_calib3d.so.4.5.4d -llibopencv_imgcodecs.so.4.5.4d -llibopencv_features2d.so.4.5.4d -llibopencv_dnn.so.4.5.4d -llibopencv_flann.so.4.5.4d -llibopencv_xphoto.so.4.5.4d -llibopencv_photo.so.4.5.4d -llibopencv_imgproc.so.4.5.4d -llibopencv_core.so.4.5.4d -lpthread -o libmrgingham.so.2.1 /usr/bin/ld: cannot find -llibopencv_stitching.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_alphamat.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_aruco.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_barcode.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_bgsegm.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_bioinspired.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_ccalib.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_dnn_objdetect.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_dnn_superres.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_dpm.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_face.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_freetype.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_fuzzy.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_hdf.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_hfs.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_img_hash.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_intensity_transform.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_line_descriptor.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_mcc.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_quality.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_rapid.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_reg.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_rgbd.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_saliency.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_shape.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_stereo.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_structured_light.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_phase_unwrapping.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_superres.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_optflow.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_surface_matching.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_tracking.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_highgui.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_datasets.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_text.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_plot.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_ml.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_videostab.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_videoio.so.4.5.4d /usr/bi
Bug#998585: marked as done (pillow: FTBFS: /<>/docs/deprecations.rst:105: WARNING: Unknown directive type "versionremoved".)
Your message dated Fri, 26 Nov 2021 09:55:19 +0100 with message-id <4a18f085-34b6-1d54-5b0c-bcfc3b5b5...@debian.org> and subject line Re: pillow: FTBFS has caused the Debian Bug report #998585, regarding pillow: FTBFS: /<>/docs/deprecations.rst:105: WARNING: Unknown directive type "versionremoved". 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.) -- 998585: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998585 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pillow Version: 8.3.2-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211104 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>/docs' > sphinx-build -b html -W --keep-going -d _build/doctrees . _build/html > Running Sphinx v4.2.0 > making output directory... done > loading intersphinx inventory from https://docs.python.org/3/objects.inv... > building [mo]: targets for 0 po files that are out of date > building [html]: targets for 93 source files that are out of date > updating environment: [new config] 93 added, 0 changed, 0 removed > reading sources... [ 1%] PIL > reading sources... [ 2%] about > reading sources... [ 3%] deprecations > reading sources... [ 4%] handbook/appendices > reading sources... [ 5%] handbook/concepts > reading sources... [ 6%] handbook/image-file-formats > reading sources... [ 7%] handbook/index > reading sources... [ 8%] handbook/overview > reading sources... [ 9%] handbook/text-anchors > reading sources... [ 10%] handbook/tutorial > reading sources... [ 11%] handbook/writing-your-own-file-decoder > reading sources... [ 12%] index > reading sources... [ 13%] installation > reading sources... [ 15%] porting > reading sources... [ 16%] reference/ExifTags > reading sources... [ 17%] reference/Image > reading sources... [ 18%] reference/ImageChops > reading sources... [ 19%] reference/ImageCms > reading sources... [ 20%] reference/ImageColor > reading sources... [ 21%] reference/ImageDraw > reading sources... [ 22%] reference/ImageEnhance > reading sources... [ 23%] reference/ImageFile > reading sources... [ 24%] reference/ImageFilter > reading sources... [ 25%] reference/ImageFont > reading sources... [ 26%] reference/ImageGrab > reading sources... [ 27%] reference/ImageMath > reading sources... [ 29%] reference/ImageMorph > reading sources... [ 30%] reference/ImageOps > reading sources... [ 31%] reference/ImagePalette > reading sources... [ 32%] reference/ImagePath > reading sources... [ 33%] reference/ImageQt > reading sources... [ 34%] reference/ImageSequence > reading sources... [ 35%] reference/ImageShow > reading sources... [ 36%] reference/ImageStat > reading sources... [ 37%] reference/ImageTk > reading sources... [ 38%] reference/ImageWin > reading sources... [ 39%] reference/JpegPresets > reading sources... [ 40%] reference/PSDraw > reading sources... [ 41%] reference/PixelAccess > reading sources... [ 43%] reference/PyAccess > reading sources... [ 44%] reference/TiffTags > reading sources... [ 45%] reference/block_allocator > reading sources... [ 46%] reference/c_extension_debugging > reading sources... [ 47%] reference/features > reading sources... [ 48%] reference/index > reading sources... [ 49%] reference/internal_design > reading sources... [ 50%] reference/internal_modules > reading sources... [ 51%] reference/limits > reading sources... [ 52%] reference/open_files > reading sources... [ 53%] reference/plugins > reading sources... [ 54%] releasenotes/2.7.0 > reading sources... [ 55%] releasenotes/2.8.0 > reading sources... [ 56%] releasenotes/3.0.0 > reading sources... [ 58%] releasenotes/3.1.0 > reading sources... [ 59%] releasenotes/3.1.1 > reading sources... [ 60%] releasenotes/3.1.2 > reading sources... [ 61%] releasenotes/3.2.0 > reading sources... [ 62%] releasenotes/3.3.0 > reading sources... [ 63%] releasenotes/3.3.2 > reading sources... [ 64%] releasenotes/3.4.0 > reading sources... [ 65%] releasenotes/4.0.0 > reading sources... [ 66%] releasenotes/4.1.0 > reading sources... [ 67%] releasenotes/4.1.1 > reading sources... [ 68%] releasenotes/4.2.0 > reading sources... [ 69%] releasenotes/4.2.1 > reading sources... [ 70%] releasenotes/4.3.0 > reading sources... [ 72%] releasenotes/5.0.0 > reading sources... [ 73%] releasenotes/5.1.0 > reading sources... [ 74%] releasenotes/5.2.0 > reading sources... [ 75%] releasenotes/5.3.0 > reading sources... [ 76%] releasenotes/5.4.0 > reading sources... [ 77%]
Bug#1000576: closing 1000576
On 25.11.2021 17.38, Salvo Tomaselli wrote: What about the evdev one? What about it? -libinput replaced it and has more features. -- t
Bug#984159: gnubiff: ftbfs with GCC-11
Package: gnubiff Version: 2.2.17-3 Followup-For: Bug #984159 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu jammy ubuntu-patch X-Debbugs-Cc: simon.cho...@canonical.com Control: tags -1 patch Dear Maintainer, In Ubuntu, the attached patch was applied to achieve the following: * d/rules: force G++ to use C++14 (Closes: #984159) Thanks for considering the patch. -- System Information: Debian Release: 11.0 APT prefers impish-updates APT policy: (500, 'impish-updates'), (500, 'impish-security'), (500, 'impish'), (50, 'impish-proposed') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.13.0-20-lowlatency (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_USER, TAINT_OOT_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled diff -Nru gnubiff-2.2.17/debian/rules gnubiff-2.2.17/debian/rules --- gnubiff-2.2.17/debian/rules 2018-10-17 00:37:55.0 +0200 +++ gnubiff-2.2.17/debian/rules 2021-11-26 09:13:33.0 +0100 @@ -1,5 +1,6 @@ #!/usr/bin/make -f +export DEB_CXXFLAGS_MAINT_APPEND=-std=c++14 %: dh $@
Processed: Re: gnubiff: ftbfs with GCC-11
Processing control commands: > tags -1 patch Bug #984159 [src:gnubiff] gnubiff: ftbfs with GCC-11 Added tag(s) patch. -- 984159: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984159 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
