Bug#984158: grfcodec: diff for NMU version 6.0.6-5.1
Hi Adrian, > I've prepared an NMU for grfcodec (versioned as 6.0.6-5.1) and uploaded > it to DELAYED/15. Please feel free to tell me if I should cancel it, or > to use the changes for a maintainer upload instead. Thanks for your interest and picking this up! However, I had actually *just* uploaded a new version myself yesterday, but it seems they are not picked up. I suspect this is because my gpg key expired and the validity extension I did a while ago isn't picked up by the keyring yet. As soon as it is, I expect my pending packages will be processed. See also https://salsa.debian.org/openttd-team/grfcodec/-/commits/master/ I suspect it would be best to cancel your upload, and use my version instead. Gr. Matthijs signature.asc Description: PGP signature
Bug#1000466: [Debichem-devel] Bug#1000466: phonopy: autopkgtest failure
Hi, On 2021-11-23 20:20, Adrian Bunk wrote: > /usr/lib/python3/dist-packages/phonopy/qha/eos.py:137: SystemExit > - Captured stdout call > - > You need to install python-scipy. > === short test summary info > > FAILED test/qha/test_QHA.py::test_QHA_Si - SystemExit: 1 > = 1 failed, 138 passed, 1 skipped in 62.19s (0:01:02) > == > autopkgtest [15:31:27]: test command1: ---] > autopkgtest [15:31:27]: test command1: - - - - - - - - - - results - - - - - > - - - - - > > > python3-scipy is a !nocheck build dependency. This most likely is limited to testing, as I cannot reproduce the autopkgtest failure in clean sid chroot. Most likely some dependency in unstable pulls python3-scipy in. It would make sense to add explicit autopkgtest dependency on python3-scipy, though. Thanks, Andrius
Bug#1000491: FTBFS with Why3 1.4.0
Source: frama-c Version: 20201209+titanium-4.1 Severity: serious Tags: ftbfs Dear Maintainer, Frama-c FTBFS with Why3 1.4.0: > [...] > File "src/plugins/wp/Why3Provers.ml", line 31, characters 19-61: > 31 | let config = Why3.Whyconf.load_default_config_if_needed config in > ^^ > Error: Unbound value Why3.Whyconf.load_default_config_if_needed > make[1]: *** [share/Makefile.generic:78: src/plugins/wp/Why3Provers.cmo] > Error 2 > make[1]: *** Waiting for unfinished jobs > make[1]: Leaving directory '/<>' > dh_auto_build: error: make -j4 returned exit code 2 > make: *** [debian/rules:45: binary-arch] Error 25 > dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit > status 2 This may be fixed by the new upstream release v23 (Vanadium). Cheers, -- Stéphane -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.14.0-4-amd64 (SMP w/4 CPU threads) 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#998565: Errors due to changes in iso-codes data
Hi Scott > > The tests look easy enough to fix, so it's worth trying to do that. (and > > it's in the Debian group on salsa to make that easy :) I've looked at them and fixed most of the tests locally without issues. I guess I should push that somewhere so that it is visible. I'll start a draft PR with upstream for it. > > I'm a bit surprised by some of the data changes though -- apparently > > England is no longer a part of the UK. Yes, that's quite complicated, but > > the ISO-3166-2 info does still list ENG and EAW. As the pycountry tests > > highlight, those divisions disappeared from iso_3166-2.json with the > > switch over to a different data harvester. > > > > https://www.iso.org/obp/ui/#iso:code:3166:GB > > > > Is that correct and intended? > > Good question. I not sure how to adapt one test to the new data, so I'll > leave it on to you to deal with. I'm happy to look for alternate sets of divisions to replace these UK ones in the test if that's appropriate. I guess I need the input from Tobias to know whether the pycountry test failure has found a bug in the pycountry test code or a bug in the iso-codes data. The test failures regarding AL-BU look like an intended data change that needs a fix in the pycountry data. Finding a different second level division and then coming back to the national and first level divisions is needed... Tobias might have a suggestion there, otherwise I'll trawl the ISO database to find a different test case. https://www.iso.org/obp/ui/#iso:code:3166:AL https://en.wikipedia.org/wiki/ISO_3166-2:AL > Please address this before it gets auto-removed. Yes, will do. (and just discussing this bug keeps resetting the autoremoval timer, of course!) cheers Stuart -- Stuart Prescotthttp://www.nanonanonano.net/ stu...@nanonanonano.net Debian Developer http://www.debian.org/ stu...@debian.org GPG fingerprint90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7
Bug#998565: Errors due to changes in iso-codes data
On Tue, 16 Nov 2021 01:30:55 +1100 Stuart Prescott wrote: > Hi Scott & Tobias > > On Monday, 15 November 2021 21:13:09 AEDT Dr. Tobias Quathamer wrote: > > On Sun, 14 Nov 2021 20:30:06 -0500 Scott Kitterman > > > > wrote: > > > I looked at this a bit today and it looks like the test failures are due > > > to > > > updates in the iso-codes data used by the tests, not any real failures. I > > > think disabling the failing tests for now would be a reasonable way to > > > keep > > > this in testing (I'm interested to avoid transitive removal of xml2rfc). > > > > > > Unless there's some objection to this, I will probably NMU later in the > > > week. > > > > > > Scott K > > > > Hi Scott, > > > > iso-codes maintainer here -- I've just seen this bug and your mail. Your > > analysis is correct, from my point of view, you should go ahead with the > > NMU. > > The tests look easy enough to fix, so it's worth trying to do that. (and it's > in the Debian group on salsa to make that easy :) > > I'm a bit surprised by some of the data changes though -- apparently England > is no longer a part of the UK. Yes, that's quite complicated, but the > ISO-3166-2 info does still list ENG and EAW. As the pycountry tests > highlight, > those divisions disappeared from iso_3166-2.json with the switch over to a > different data harvester. > > https://www.iso.org/obp/ui/#iso:code:3166:GB > > Is that correct and intended? Good question. I not sure how to adapt one test to the new data, so I'll leave it on to you to deal with. Please address this before it gets auto-removed. Scott K
Bug#996239: marked as done (ruby-hashie: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError:)
Your message dated Wed, 24 Nov 2021 05:18:31 + with message-id and subject line Bug#996239: fixed in ruby-hashie 3.5.5-3 has caused the Debian Bug report #996239, regarding ruby-hashie: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: 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.) -- 996239: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996239 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-hashie Version: 3.5.5-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-hashie was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): > ArgumentError: >wrong number of arguments (given 1, expected 0) > # ./spec/hashie/extensions/mash/symbolize_keys_spec.rb:21:in `block (4 > levels) in ' > # ./spec/hashie/extensions/mash/symbolize_keys_spec.rb:29:in `block (3 > levels) in ' > # ./spec/hashie/extensions/mash/symbolize_keys_spec.rb:32:in `block (3 > levels) in ' > > Finished in 1.81 seconds (files took 2.61 seconds to load) > 650 examples, 1 failure > > Failed examples: > > rspec ./spec/hashie/extensions/mash/symbolize_keys_spec.rb:31 # > Hashie::Extensions::Mash::SymbolizeKeys implicit to_hash on double splat is > converted on method calls > > /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 > ./spec/hashie/array_spec.rb ./spec/hashie/clash_spec.rb > ./spec/hashie/dash_spec.rb ./spec/hashie/extensions/autoload_spec.rb > ./spec/hashie/extensions/coercion_spec.rb > ./spec/hashie/extensions/dash/coercion_spec.rb > ./spec/hashie/extensions/dash/indifferent_access_spec.rb > ./spec/hashie/extensions/deep_fetch_spec.rb > ./spec/hashie/extensions/deep_find_spec.rb > ./spec/hashie/extensions/deep_locate_spec.rb > ./spec/hashie/extensions/deep_merge_spec.rb > ./spec/hashie/extensions/ignore_undeclared_spec.rb > ./spec/hashie/extensions/indifferent_access_spec.rb > ./spec/hashie/extensions/indifferent_access_with_rails_hwia_spec.rb > ./spec/hashie/extensions/key_conversion_spec.rb > ./spec/hashie/extensions/mash/keep_original_keys_spec.rb > ./spec/hashie/extensions/mash/safe_assignment_spec.rb > ./spec/hashie/extensions/mash/symbolize_keys_spec.rb > ./spec/hashie/extensions/merge_initializer_spec.rb > ./spec/hashie/extensions/method_access_spec.rb > ./spec/hashie/extensions/strict_key_access_spec.rb > ./spec/hashie/extensions/stringify_keys_spec.rb > ./spec/hashie/extensions/symbolize_keys_spec.rb ./spec/hashie/hash_spec.rb > ./spec/hashie/mash_spec.rb ./spec/hashie/parsers/yaml_erb_parser_spec.rb > ./spec/hashie/rash_spec.rb ./spec/hashie/trash_spec.rb > ./spec/hashie/utils_spec.rb ./spec/hashie/version_spec.rb > ./spec/hashie_spec.rb ./spec/integration/omniauth/integration_spec.rb > ./spec/integration/rails-without-dependency/integration_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-hashie/ruby-hashie_3.5.5-2+rebuild1633382477_amd64.build.txt signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: ruby-hashie Source-Version: 3.5.5-3 Done: Daniel Leidert We believe that the bug you reported is fixed in the latest version of ruby-hashie, 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-hashie 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 05:48:59 +0100 Source: ruby-hashie Architecture: source Version: 3.5.5-3 Distribution: unstable Urgency: medium Maintainer: Debian Ruby
Processed: tagging 996319, severity of 996319 is normal
Processing commands for cont...@bugs.debian.org: > tags 996319 + unreproducible moreinfo Bug #996319 [src:ruby-mini-magick] ruby-mini-magick: FTBFS: ERROR: Test "ruby2.7" failed: Failure/Error: expect(described_class.new(output_path.to_s)).to be_valid Added tag(s) moreinfo and unreproducible. > severity 996319 normal Bug #996319 [src:ruby-mini-magick] ruby-mini-magick: FTBFS: ERROR: Test "ruby2.7" failed: Failure/Error: expect(described_class.new(output_path.to_s)).to be_valid Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 996319: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996319 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996239: marked as pending in ruby-hashie
Control: tag -1 pending Hello, Bug #996239 in ruby-hashie 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-hashie/-/commit/ecc355f37ea1712b938f578d4093fd9be39a60a5 Add patch to fix FTBFS * d/patches/0002-Suppress-keyword-arguments-warning-for-Ruby-2.7.0.patch: Add - Fix ArgumentError with Ruby 3 (closes: #996239). * d/patches/series: Enable new patch. (this message was generated automatically) -- Greetings https://bugs.debian.org/996239
Processed: Bug#996239 marked as pending in ruby-hashie
Processing control commands: > tag -1 pending Bug #996239 [src:ruby-hashie] ruby-hashie: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: Added tag(s) pending. -- 996239: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996239 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 997933 ...
Processing commands for cont...@bugs.debian.org: > tags 997933 + patch Bug #997933 [offlineimap3] offlineimap3: 'int' object is not subscriptable when connecting to outlook.office365.com Added tag(s) patch. > forwarded 997933 https://github.com/OfflineIMAP/offlineimap3/pull/98 > https://github.com/OfflineIMAP/offlineimap/issues/706 Bug #997933 [offlineimap3] offlineimap3: 'int' object is not subscriptable when connecting to outlook.office365.com Changed Bug forwarded-to-address to 'https://github.com/OfflineIMAP/offlineimap3/pull/98 https://github.com/OfflineIMAP/offlineimap/issues/706' from 'https://github.com/OfflineIMAP/offlineimap/issues/706'. > thanks Stopping processing here. Please contact me if you need assistance. -- 997933: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997933 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996370: marked as done (ruby-rgen: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed.)
Your message dated Wed, 24 Nov 2021 03:19:34 + with message-id and subject line Bug#996370: fixed in ruby-rgen 0.9.0-1 has caused the Debian Bug report #996370, regarding ruby-rgen: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed. to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 996370: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996370 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-rgen Version: 0.8.4-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-rgen was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): > /usr/bin/ruby3.0 /usr/bin/gem2deb-test-runner > > ┌──┐ > │ Run tests for ruby3.0 from debian/ruby-tests.rb > │ > └──┘ > > RUBYLIB=/<>/debian/ruby-rgen/usr/lib/ruby/vendor_ruby:. > GEM_PATH=/<>/debian/ruby-rgen/usr/share/rubygems-integration/all:/var/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0 > ruby3.0 debian/ruby-tests.rb > Run options: --seed 22447 > > # Running: > > F..F..F...F.. > > Finished in 3.114809s, 83.7933 runs/s, 561.8322 assertions/s. > > 1) Failure: > MetamodelFromEcoreTest#test_many_to_many > [/<>/test/metamodel_builder_test.rb:619]: > Expected /In (\w+::)+BClassMM : Can not use a Symbol\(:notaaclass\) where a > (\w+::)+AClassMM is expected/ to match "In > MetamodelFromEcoreTest::MetamodelFromEcore::BClassMM : Can not use a > Symbol(notaaclass)(:notaaclass) where a > MetamodelFromEcoreTest::MetamodelFromEcore::AClassMM is expected". > > 2) Failure: > MetamodelFromEcoreTest#test_has_attr > [/<>/test/metamodel_builder_test.rb:229]: > Expected /In (\w+::)+SimpleClass : Can not use a Symbol\(:someSymbol\) where > a \[true,false\] is expected/ to match "In > MetamodelFromEcoreTest::MetamodelFromEcore::SimpleClass : Can not use a > Symbol(someSymbol)(:someSymbol) where a [true,false] is expected". > > 3) Failure: > MetamodelBuilderTest#test_many_to_many > [/<>/test/metamodel_builder_test.rb:619]: > Expected /In (\w+::)+BClassMM : Can not use a Symbol\(:notaaclass\) where a > (\w+::)+AClassMM is expected/ to match "In > MetamodelBuilderTest::TestMetamodel::BClassMM : Can not use a > Symbol(notaaclass)(:notaaclass) where a > MetamodelBuilderTest::TestMetamodel::AClassMM is expected". > > 4) Failure: > MetamodelBuilderTest#test_has_attr > [/<>/test/metamodel_builder_test.rb:229]: > Expected /In (\w+::)+SimpleClass : Can not use a Symbol\(:someSymbol\) where > a \[true,false\] is expected/ to match "In > MetamodelBuilderTest::TestMetamodel::SimpleClass : Can not use a > Symbol(someSymbol)(:someSymbol) where a [true,false] is expected". > > 261 runs, 1750 assertions, 4 failures, 0 errors, 0 skips > ERROR: Test "ruby3.0" failed. The full build log is available at https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-rgen/ruby-rgen_0.8.4-1+rebuild1633393340_amd64.build.txt signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: ruby-rgen Source-Version: 0.9.0-1 Done: Daniel Leidert We believe that the bug you reported is fixed in the latest version of ruby-rgen, 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-rgen 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
Bug#996370: marked as pending in ruby-rgen
Control: tag -1 pending Hello, Bug #996370 in ruby-rgen 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-rgen/-/commit/bacd0489d2c81cea85b7595a90026108258d4dc5 Fix tests * d/patches/Handle-Ruby-3-test-failures-fue-to-new-name-method.patch: Add. - In Ruby 3 some classes got name methods. This leads to an unexpected error message in some tests, so we ignore them (closes: #996370). * d/patches/series: Adjust file. (this message was generated automatically) -- Greetings https://bugs.debian.org/996370
Processed: Bug#996370 marked as pending in ruby-rgen
Processing control commands: > tag -1 pending Bug #996370 [src:ruby-rgen] ruby-rgen: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed. Added tag(s) pending. -- 996370: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996370 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 996383 ...
Processing commands for cont...@bugs.debian.org: > tags 996383 + fixed-upstream Bug #996383 [src:ruby-semantic-puppet] ruby-semantic-puppet: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: RuntimeError: Added tag(s) fixed-upstream. > forwarded 996383 > https://github.com/puppetlabs/semantic_puppet/commit/980019ca2c3661670398da9a83839f7a2ea8ca18 > > https://github.com/puppetlabs/semantic_puppet/commit/a25b837b30e766a027fd843519caa0a0f80ef434 > https://github.com/puppetlabs/semantic_puppet/pull/38 Bug #996383 [src:ruby-semantic-puppet] ruby-semantic-puppet: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: RuntimeError: Set Bug forwarded-to-address to 'https://github.com/puppetlabs/semantic_puppet/commit/980019ca2c3661670398da9a83839f7a2ea8ca18 https://github.com/puppetlabs/semantic_puppet/commit/a25b837b30e766a027fd843519caa0a0f80ef434 https://github.com/puppetlabs/semantic_puppet/pull/38'. > thanks Stopping processing here. Please contact me if you need assistance. -- 996383: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996383 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: gpgme1.0: diff for NMU version 1.16.0-1.2
Processing control commands: > tags 998471 + patch Bug #998471 [src:gpgme1.0] gpgme1.0: b-d on python3-all-dev, but not built for all supported Python3 versions Added tag(s) patch. > tags 998471 + pending Bug #998471 [src:gpgme1.0] gpgme1.0: b-d on python3-all-dev, but not built for all supported Python3 versions Added tag(s) pending. -- 998471: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998471 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#998471: gpgme1.0: diff for NMU version 1.16.0-1.2
Control: tags 998471 + patch
Control: tags 998471 + pending
Dear maintainer,
Turns out the bug is actually that autoconf has a hardcoded list of
Python versions and 3.10 isn't in the list. When it is in the list,
there is also a bug somewhere that treats it as python 3.1.
But... Let's just avoid the hardcoded list entirely, I've prepared an
NMU to do that.
I've prepared an NMU for gpgme1.0 (versioned as 1.16.0-1.2) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
Also filed as https://salsa.debian.org/debian/gpgme/-/merge_requests/3
Regards,
SR
diff -Nru gpgme1.0-1.16.0/debian/changelog gpgme1.0-1.16.0/debian/changelog
--- gpgme1.0-1.16.0/debian/changelog 2021-09-15 01:31:55.0 -0400
+++ gpgme1.0-1.16.0/debian/changelog 2021-11-23 21:15:08.0 -0400
@@ -1,3 +1,10 @@
+gpgme1.0 (1.16.0-1.2) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Patch: Avoid a hardcoded list of known Python versions. (Closes: #998471)
+
+ -- Stefano Rivera Tue, 23 Nov 2021 21:15:08 -0400
+
gpgme1.0 (1.16.0-1.1) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru gpgme1.0-1.16.0/debian/patches/0004-core-Fix-use-after-free-issue-in-test.patch gpgme1.0-1.16.0/debian/patches/0004-core-Fix-use-after-free-issue-in-test.patch
--- gpgme1.0-1.16.0/debian/patches/0004-core-Fix-use-after-free-issue-in-test.patch 1969-12-31 20:00:00.0 -0400
+++ gpgme1.0-1.16.0/debian/patches/0004-core-Fix-use-after-free-issue-in-test.patch 2021-11-23 21:15:08.0 -0400
@@ -0,0 +1,122 @@
+From: =?utf-8?q?Ingo_Kl=C3=B6cker?=
+Date: Sat, 26 Jun 2021 18:02:47 +0200
+Subject: core: Fix use-after-free issue in test
+
+* tests/gpg/t-edit-sign.c (sign_key, verify_key_signature): New.
+(main): Factored out signing and verifying the result.
+--
+
+Factoring the two steps of the test into different functions fixes the
+use-after-free issue that was caused by accidentaly using a variable
+of the first step in the second step.
+
+GnuPG-bug-id: 5509
+---
+ tests/gpg/t-edit-sign.c | 54 +
+ 1 file changed, 37 insertions(+), 17 deletions(-)
+
+diff --git a/tests/gpg/t-edit-sign.c b/tests/gpg/t-edit-sign.c
+index 2f98362..e0494c5 100644
+--- a/tests/gpg/t-edit-sign.c
b/tests/gpg/t-edit-sign.c
+@@ -107,31 +107,19 @@ interact_fnc (void *opaque, const char *status, const char *args, int fd)
+ }
+
+
+-int
+-main (int argc, char **argv)
++void
++sign_key (const char *key_fpr, const char *signer_fpr)
+ {
+ gpgme_ctx_t ctx;
+ gpgme_error_t err;
+ gpgme_data_t out = NULL;
+- const char *signer_fpr = "A0FF4590BB6122EDEF6E3C542D727CC768697734"; /* Alpha Test */
+ gpgme_key_t signing_key = NULL;
+- const char *key_fpr = "D695676BDCEDCC2CDD6152BCFE180B1DA9E3B0B2"; /* Bravo Test */
+ gpgme_key_t key = NULL;
+- gpgme_key_t signed_key = NULL;
+- gpgme_user_id_t signed_uid = NULL;
+- gpgme_key_sig_t key_sig = NULL;
+ char *agent_info;
+- int mode;
+-
+- (void)argc;
+- (void)argv;
+-
+- init_gpgme (GPGME_PROTOCOL_OpenPGP);
+
+ err = gpgme_new ();
+ fail_if_err (err);
+
+- /* Sign the key */
+ agent_info = getenv("GPG_AGENT_INFO");
+ if (!(agent_info && strchr (agent_info, ':')))
+ gpgme_set_passphrase_cb (ctx, passphrase_cb, 0);
+@@ -159,8 +147,23 @@ main (int argc, char **argv)
+ gpgme_data_release (out);
+ gpgme_key_unref (key);
+ gpgme_key_unref (signing_key);
++ gpgme_release (ctx);
++}
++
++
++void
++verify_key_signature (const char *key_fpr, const char *signer_keyid)
++{
++ gpgme_ctx_t ctx;
++ gpgme_error_t err;
++ gpgme_key_t signed_key = NULL;
++ gpgme_user_id_t signed_uid = NULL;
++ gpgme_key_sig_t key_sig = NULL;
++ int mode;
++
++ err = gpgme_new ();
++ fail_if_err (err);
+
+- /* Verify the key signature */
+ mode = gpgme_get_keylist_mode (ctx);
+ mode |= GPGME_KEYLIST_MODE_SIGS;
+ err = gpgme_set_keylist_mode (ctx, mode);
+@@ -168,7 +171,7 @@ main (int argc, char **argv)
+ err = gpgme_get_key (ctx, key_fpr, _key, 0);
+ fail_if_err (err);
+
+- signed_uid = key->uids;
++ signed_uid = signed_key->uids;
+ if (!signed_uid)
+ {
+ fprintf (stderr, "Signed key has no user IDs\n");
+@@ -180,7 +183,7 @@ main (int argc, char **argv)
+ exit (1);
+ }
+ key_sig = signed_uid->signatures->next;
+- if (strcmp ("2D727CC768697734", key_sig->keyid))
++ if (strcmp (signer_keyid, key_sig->keyid))
+ {
+ fprintf (stderr, "Unexpected key ID in second user ID sig: %s\n",
+ key_sig->keyid);
+@@ -196,6 +199,23 @@ main (int argc, char **argv)
+
+ gpgme_key_unref (signed_key);
+ gpgme_release (ctx);
++}
++
++
++int
++main (int argc, char **argv)
++{
++ const char *signer_fpr = "A0FF4590BB6122EDEF6E3C542D727CC768697734"; /* Alpha Test */
++ const char *signer_keyid = signer_fpr + strlen(signer_fpr) - 16;
++ const char *key_fpr = "D695676BDCEDCC2CDD6152BCFE180B1DA9E3B0B2"; /* Bravo Test */
++
++ (void)argc;
++ (void)argv;
++
++
Processed: tagging 997635
Processing commands for cont...@bugs.debian.org: > tags 997635 + pending Bug #997635 [src:flask-openid] flask-openid: FTBFS: error in Flask-OpenID setup command: use_2to3 is invalid. Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 997635: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997635 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 996370 is forwarded to https://github.com/mthiede/rgen/issues/35
Processing commands for cont...@bugs.debian.org: > forwarded 996370 https://github.com/mthiede/rgen/issues/35 Bug #996370 [src:ruby-rgen] ruby-rgen: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed. Set Bug forwarded-to-address to 'https://github.com/mthiede/rgen/issues/35'. > thanks Stopping processing here. Please contact me if you need assistance. -- 996370: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996370 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000421: in package dpkg marked as pending
Control: tag 1000421 pending Hi! Bug #1000421 in package dpkg reported by you has been fixed in the dpkg/dpkg.git Git repository. You can see the changelog below, and you can check the diff of the fix at: https://git.dpkg.org/cgit/dpkg/dpkg.git/diff/?id=ecbd9f1b1 --- Dpkg::Shlibs::Objdump: Fix apply_relocations to work with versioned symbols Since binutils 2.26 (commit bb4d2ac2cc637c61232624d9d359b8d3f031e3e9) versioned symbols in copy relocations are output as «symbol@@version» when they are in an undefined section (otherwise they use «@»). We were not taking this into account which meant these did not match and did not get marked as undefined, and got ignored for symbol dependency calculation. Try both the version qualified symbol and the bare symbol name to cope with old and new formats. Known to be affected are at least any-amd64, hppa and m68k architectures. Closes: #1000421
Processed: Bug#1000421 in package dpkg marked as pending
Processing control commands: > tag 1000421 pending Bug #1000421 [dpkg-dev] dpkg-shlibdeps: Wrong minimum version requirement on libc6 Added tag(s) pending. -- 1000421: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000421 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1000419
Processing commands for cont...@bugs.debian.org: > tags 1000419 + ftbfs Bug #1000419 [src:pymatgen] pymatgen: FTBFS - Test failure: BSPlotterProjectedTest.test_methods Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1000419: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000419 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1000428
Processing commands for cont...@bugs.debian.org: > tags 1000428 + ftbfs Bug #1000428 [src:gammapy] gammapy: FTBFS with matplotlib 3.5 Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1000428: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000428 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996381: marked as done (ruby-sanitize: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: wrong number of arguments (given 4, expected 1..3))
Your message dated Wed, 24 Nov 2021 01:20:07 +
with message-id
and subject line Bug#996381: fixed in ruby-sanitize 5.2.3-1
has caused the Debian Bug report #996381,
regarding ruby-sanitize: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed:
ArgumentError: wrong number of arguments (given 4, expected 1..3)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
996381: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996381
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-sanitize
Version: 5.2.1-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.0
Hi,
We are about to enable building against ruby3.0 on unstable. During a test
rebuild, ruby-sanitize was found to fail to build in that situation.
To reproduce this locally, you need to install ruby-all-dev from experimental
on an unstable system or build chroot.
Relevant part (hopefully):
> ArgumentError: wrong number of arguments (given 4, expected 1..3)
> /usr/lib/ruby/vendor_ruby/nokogumbo/html5/document.rb:4:in `parse'
> /usr/lib/ruby/vendor_ruby/nokogumbo/html5.rb:22:in `parse'
>
> /<>/debian/ruby-sanitize/usr/lib/ruby/vendor_ruby/sanitize.rb:126:in
> `document'
>
> /<>/debian/ruby-sanitize/usr/lib/ruby/vendor_ruby/sanitize.rb:61:in
> `document'
> /<>/test/test_clean_element.rb:522:in `block (3 levels) in
> '
> /usr/lib/ruby/vendor_ruby/minitest/test.rb:98:in `block (3 levels) in run'
> /usr/lib/ruby/vendor_ruby/minitest/test.rb:195:in `capture_exceptions'
> /usr/lib/ruby/vendor_ruby/minitest/test.rb:95:in `block (2 levels) in run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:270:in `time_it'
> /usr/lib/ruby/vendor_ruby/minitest/test.rb:94:in `block in run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:365:in `on_signal'
> /usr/lib/ruby/vendor_ruby/minitest/test.rb:211:in `with_info_handler'
> /usr/lib/ruby/vendor_ruby/minitest/test.rb:93:in `run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:1029:in `run_one_method'
> /usr/lib/ruby/vendor_ruby/minitest/parallel.rb:33:in `block (2 levels) in
> start'
>
> 227 runs, 1483 assertions, 0 failures, 17 errors, 8 skips
> rake aborted!
> Command failed with status (1): [ruby -w -I"test"
> /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/rake_test_loader.rb
> "test/test_clean_comment.rb" "test/test_clean_css.rb"
> "test/test_clean_doctype.rb" "test/test_clean_element.rb"
> "test/test_config.rb" "test/test_malicious_css.rb"
> "test/test_malicious_html.rb" "test/test_parser.rb" "test/test_sanitize.rb"
> "test/test_sanitize_css.rb" "test/test_transformers.rb" -v]
>
> Tasks: TOP => default
> (See full trace by running task with --trace)
> ERROR: Test "ruby3.0" failed:
The full build log is available at
https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-sanitize/ruby-sanitize_5.2.1-2+rebuild1633394782_amd64.build.txt
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ruby-sanitize
Source-Version: 5.2.3-1
Done: Daniel Leidert
We believe that the bug you reported is fixed in the latest version of
ruby-sanitize, 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-sanitize 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 00:34:42 +0100
Source: ruby-sanitize
Architecture: source
Version: 5.2.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team
Changed-By: Daniel Leidert
Closes: 996381
Changes:
ruby-sanitize (5.2.3-1) unstable; urgency=medium
.
* Team upload.
* New upstream release.
- Fixes issue when using keyword arguments (closes: #996381).
* d/control: Add Rules-Requires-Root field.
(Standards-Version): Bump to 4.6.0.
(Build-Depends): Bump ruby-nokogiri version. Bump ruby-nokogumbo to
Ruby 3.0 compatible version (causing #996381 as well).
(Depends): Remove interpreters and use ${ruby:Depends}.
* d/copyright (Copyright): Update and add team.
*
Bug#995040: marked as done (iverilog FTBFS: configure: error: C preprocessor "/lib/cpp" fails sanity check)
Your message dated Wed, 24 Nov 2021 01:19:49 + with message-id and subject line Bug#995040: fixed in iverilog 11.0-1.1 has caused the Debian Bug report #995040, regarding iverilog FTBFS: configure: error: C preprocessor "/lib/cpp" fails sanity check 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.) -- 995040: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995040 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: iverilog Version: 11.0-1 Severity: serious Tags: ftbfs iverilog fails to build from source in unstable on amd64. I'm not exactly sure what the relevant parts of the build log are. Here is my guess: | ... | checking how to run the C preprocessor... /lib/cpp | configure: error: in `/<>': | configure: error: C preprocessor "/lib/cpp" fails sanity check | See `config.log' for more details | tail -v -n \+0 config.log | ==> config.log <== | ... | configure:8905: result: /lib/cpp | configure:8919: -Wdate-time -D_FORTIFY_SOURCE=2 conftest.c | ./configure: line 2189: -Wdate-time: command not found | configure:8919: $? = 127 | ... | configure:8952: error: in `/<>': | configure:8954: error: C preprocessor "/lib/cpp" fails sanity check | See `config.log' for more details | ... Seems to reproduce reliably. Also seen in cross builds: http://crossqa.debian.net/build/iverilog_11.0-1_amd64_20210825212934.log Hope this helps. Helmut --- End Message --- --- Begin Message --- Source: iverilog Source-Version: 11.0-1.1 Done: Adrian Bunk We believe that the bug you reported is fixed in the latest version of iverilog, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 995...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Adrian Bunk (supplier of updated iverilog 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, 07 Nov 2021 19:15:21 +0200 Source: iverilog Architecture: source Version: 11.0-1.1 Distribution: unstable Urgency: medium Maintainer: Debian Electronics Team Changed-By: Adrian Bunk Closes: 995040 Changes: iverilog (11.0-1.1) unstable; urgency=medium . * Non-maintainer upload. * Add upstream fix for FTBFS with autoconf >= 2.70. (Closes: #995040) Checksums-Sha1: 3442e8ea2464fb9ec99145c692227a19e962bcd5 2039 iverilog_11.0-1.1.dsc c38751c8aa991e7be7fb4aee4e82dc9b17510ec4 10532 iverilog_11.0-1.1.debian.tar.xz Checksums-Sha256: b5182a7c7cad657dc090675971c839547cfcb8f2de5a887cbd32cdb332050b7f 2039 iverilog_11.0-1.1.dsc 2f29cceecda3d0f56107f09fb276fb616a9505c063d772ca2877f30ffb9437dd 10532 iverilog_11.0-1.1.debian.tar.xz Files: 3efb49d22ab38fed7e937ae7ea2ab8af 2039 electronics optional iverilog_11.0-1.1.dsc 0d65b13e9c5048081fc3ddab02b554b7 10532 electronics optional iverilog_11.0-1.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmGICwQACgkQiNJCh6LY mLEHTQ/+Pfo1wrI9RTs1Qsktcev/IJ2i2HjaeAWatm+Y/rUF593IcQ4e4DReAwu7 MGO8+Awa2z92sjIX1rxRv7F4h9iCKLxytzNRIy12/F9IR4MQIj/j1oY0vU7IyGdF qH2w7ffIyMdZnVsEZDKL7QG+qGETpfcauE/IdBMfpdZR/krxHDTGeqVA3qcoRLm7 HauQccACwrBK6zUU9jkgKpIYCJChEls4o8OyRdzjHxgRYfxdB+I0L6UNXfcNTQEF 3mGbZuKJLaQwFjQrBx5NV3fqKF8niOfZ81iM1BT3oVRq0Tfm6FhTeWDyja7umJic awqEcg2gAj1cRTFaADMkfMaN2nwrkIXLN0qNqW/+VwkpzMgkqVC8kcv4+oRPrhgk 5lO+sZxot3obupXmJ1Af8crvFZ9VQcmUfXjJjTxZYcvfY4p79pP2hOxC3eDquX3s j4Hv1qa73SgjfndjQYPUHdC41fWD/Tmby6DP0jYMNTOrvgksjLhRv7Ak3bM4l5iz QQzHOD3KuI0+CL0NSqW5BJ0Mj9pMLc0rUD7cGqtQWgdCP9A8oMsTUVPACmJDgEcK xGWjMmyMbeW7gy0gM6Cn6vqsUIh5kmkz8z7IMTKSP+g5JcBuufpVmN1jm9Rk0wxY 94nZhiQ+AbgeFNmWT9k6wOLUAy3nC0RJ+gPObx1ebPKCB4AyayA= =/D+n -END PGP SIGNATURE End Message ---
Bug#1000488: marked as done (nokogumbo/html5.rb:74: warning: Using the last argument as keyword parameters is deprecated)
Your message dated Wed, 24 Nov 2021 01:20:00 + with message-id and subject line Bug#1000488: fixed in ruby-nokogumbo 2.0.2-3 has caused the Debian Bug report #1000488, regarding nokogumbo/html5.rb:74: warning: Using the last argument as keyword parameters is deprecated 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.) -- 1000488: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000488 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-sanitize Version: 5.2.1-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-sanitize was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): > ArgumentError: wrong number of arguments (given 4, expected 1..3) > /usr/lib/ruby/vendor_ruby/nokogumbo/html5/document.rb:4:in `parse' > /usr/lib/ruby/vendor_ruby/nokogumbo/html5.rb:22:in `parse' > > /<>/debian/ruby-sanitize/usr/lib/ruby/vendor_ruby/sanitize.rb:126:in > `document' > > /<>/debian/ruby-sanitize/usr/lib/ruby/vendor_ruby/sanitize.rb:61:in > `document' > /<>/test/test_clean_element.rb:522:in `block (3 levels) in > ' > /usr/lib/ruby/vendor_ruby/minitest/test.rb:98:in `block (3 levels) in run' > /usr/lib/ruby/vendor_ruby/minitest/test.rb:195:in `capture_exceptions' > /usr/lib/ruby/vendor_ruby/minitest/test.rb:95:in `block (2 levels) in run' > /usr/lib/ruby/vendor_ruby/minitest.rb:270:in `time_it' > /usr/lib/ruby/vendor_ruby/minitest/test.rb:94:in `block in run' > /usr/lib/ruby/vendor_ruby/minitest.rb:365:in `on_signal' > /usr/lib/ruby/vendor_ruby/minitest/test.rb:211:in `with_info_handler' > /usr/lib/ruby/vendor_ruby/minitest/test.rb:93:in `run' > /usr/lib/ruby/vendor_ruby/minitest.rb:1029:in `run_one_method' > /usr/lib/ruby/vendor_ruby/minitest/parallel.rb:33:in `block (2 levels) in > start' > > 227 runs, 1483 assertions, 0 failures, 17 errors, 8 skips > rake aborted! > Command failed with status (1): [ruby -w -I"test" > /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/rake_test_loader.rb > "test/test_clean_comment.rb" "test/test_clean_css.rb" > "test/test_clean_doctype.rb" "test/test_clean_element.rb" > "test/test_config.rb" "test/test_malicious_css.rb" > "test/test_malicious_html.rb" "test/test_parser.rb" "test/test_sanitize.rb" > "test/test_sanitize_css.rb" "test/test_transformers.rb" -v] > > Tasks: TOP => default > (See full trace by running task with --trace) > ERROR: Test "ruby3.0" failed: The full build log is available at https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-sanitize/ruby-sanitize_5.2.1-2+rebuild1633394782_amd64.build.txt signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: ruby-nokogumbo Source-Version: 2.0.2-3 Done: Daniel Leidert We believe that the bug you reported is fixed in the latest version of ruby-nokogumbo, 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. Daniel Leidert (supplier of updated ruby-nokogumbo 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 01:40:01 +0100 Source: ruby-nokogumbo Architecture: source Version: 2.0.2-3 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Team Changed-By: Daniel Leidert Closes: 993828 1000488 Changes: ruby-nokogumbo (2.0.2-3) unstable; urgency=medium . * Team upload. . [ Debian Janitor ] * Bump debhelper from old 12 to 13. * Set upstream metadata fields: Repository, Repository-Browse. * Update standards version to 4.5.1, no changes needed. . [ Daniel Leidert ] * d/control (Build-Depends): Add libxslt1-dev for nokogiri.h. * d/rules: Use gem installation layout. Exclude sources from installation. * d/patches/Fix-Ruby3-keywords-issue.patch: Add patch. - Fixes deprecated keyword
Processed: tagging 1000360
Processing commands for cont...@bugs.debian.org: > tags 1000360 + ftbfs Bug #1000360 [src:segyio] segyio: FTBFS with Python 3.10 Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1000360: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000360 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#996381 marked as pending in ruby-sanitize
Processing control commands: > tag -1 pending Bug #996381 [src:ruby-sanitize] ruby-sanitize: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: wrong number of arguments (given 4, expected 1..3) Added tag(s) pending. -- 996381: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996381 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996381: marked as pending in ruby-sanitize
Control: tag -1 pending Hello, Bug #996381 in ruby-sanitize 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-sanitize/-/commit/56462205a3c0b8529533a88bc20e86c6c2450c78 ruby-sanitize (5.2.3-1) UNRELEASED * New upstream release. - Fixes issue when using keyword arguments (closes: #996381). (this message was generated automatically) -- Greetings https://bugs.debian.org/996381
Processed: Bug#1000488 marked as pending in ruby-nokogumbo
Processing control commands: > tag -1 pending Bug #1000488 [ruby-nokogumbo] nokogumbo/html5.rb:74: warning: Using the last argument as keyword parameters is deprecated Added tag(s) pending. -- 1000488: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000488 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000488: marked as pending in ruby-nokogumbo
Control: tag -1 pending Hello, Bug #1000488 in ruby-nokogumbo 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-nokogumbo/-/commit/614048c6710572a43789c2f048026c451cefa089 Add patch to make nokogumbo Ruby 3.0 compatible * d/patches/Fix-Ruby3-keywords-issue.patch: Add patch. - Fixes deprecated keyword parameters handling (closes: #1000488). * d/patches/series: Enable new patch. (this message was generated automatically) -- Greetings https://bugs.debian.org/1000488
Processed: tagging 1000423
Processing commands for cont...@bugs.debian.org: > tags 1000423 + ftbfs Bug #1000423 [src:python-biom-format] python-biom-format: FTBFS with Python 3.10 - Test failures Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1000423: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000423 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: cloning 996381, reassign -1 to ruby-nokogumbo ..., block 996381 with -1
Processing commands for cont...@bugs.debian.org: > clone 996381 -1 Bug #996381 [src:ruby-sanitize] ruby-sanitize: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: wrong number of arguments (given 4, expected 1..3) Bug 996381 cloned as bug 1000488 > reassign -1 ruby-nokogumbo 2.0.2-2 Bug #1000488 [src:ruby-sanitize] ruby-sanitize: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: wrong number of arguments (given 4, expected 1..3) Bug reassigned from package 'src:ruby-sanitize' to 'ruby-nokogumbo'. No longer marked as found in versions ruby-sanitize/5.2.1-2. Ignoring request to alter fixed versions of bug #1000488 to the same values previously set Bug #1000488 [ruby-nokogumbo] ruby-sanitize: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: wrong number of arguments (given 4, expected 1..3) Marked as found in versions ruby-nokogumbo/2.0.2-2. > retitle -1 nokogumbo/html5.rb:74: warning: Using the last argument as keyword > parameters is deprecated Bug #1000488 [ruby-nokogumbo] ruby-sanitize: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: wrong number of arguments (given 4, expected 1..3) Changed Bug title to 'nokogumbo/html5.rb:74: warning: Using the last argument as keyword parameters is deprecated' from 'ruby-sanitize: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: wrong number of arguments (given 4, expected 1..3)'. > block 996381 with -1 Bug #996381 [src:ruby-sanitize] ruby-sanitize: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: wrong number of arguments (given 4, expected 1..3) 996381 was not blocked by any bugs. 996381 was not blocking any bugs. Added blocking bug(s) of 996381: 1000488 > thanks Stopping processing here. Please contact me if you need assistance. -- 1000488: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000488 996381: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996381 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996524: marked as done (ruby-whitequark-parser: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed.)
Your message dated Tue, 23 Nov 2021 23:33:35 + with message-id and subject line Bug#996524: fixed in ruby-whitequark-parser 3.0.2.0-1 has caused the Debian Bug report #996524, regarding ruby-whitequark-parser: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed. to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 996524: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996524 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-whitequark-parser Version: 2.7.1.4-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-whitequark-parser was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): > /usr/bin/ruby3.0 /usr/bin/gem2deb-test-runner > > ┌──┐ > │ Checking Rubygems dependency resolution on ruby3.0 > │ > └──┘ > > GEM_PATH=/<>/debian/ruby-whitequark-parser/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.0.0:/var/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0 > ruby3.0 -e gem\ \"parser\" > > ┌──┐ > │ Run tests for ruby3.0 from debian/ruby-tests.rake > │ > └──┘ > > RUBYLIB=. > GEM_PATH=/<>/debian/ruby-whitequark-parser/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.0.0:/var/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0 > ruby3.0 -S rake -f debian/ruby-tests.rake > /usr/bin/ruby3.0 -w -I"test" > /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/rake_test_loader.rb > "test/test_ast_processor.rb" "test/test_base.rb" "test/test_current.rb" > "test/test_diagnostic.rb" "test/test_diagnostic_engine.rb" > "test/test_encoding.rb" "test/test_lexer.rb" "test/test_lexer_stack_state.rb" > "test/test_meta.rb" "test/test_parse_helper.rb" "test/test_parser.rb" > "test/test_runner_parse.rb" "test/test_runner_rewrite.rb" > "test/test_source_buffer.rb" "test/test_source_comment.rb" > "test/test_source_comment_associator.rb" "test/test_source_map.rb" > "test/test_source_range.rb" "test/test_source_rewriter.rb" > "test/test_source_rewriter_action.rb" "test/test_source_tree_rewriter.rb" > "test/test_static_environment.rb" -v > warning: parser/current is loading parser/ruby27, which recognizes > warning: 2.7.x-compliant syntax, but you are running 3.0.2. > warning: please see > https://github.com/whitequark/parser#compatibility-with-ruby-mri. > Run options: -v --seed 1073 > > # Running: > > TestSourceTreeRewriter#test_empty = 0.00 s = . > TestSourceTreeRewriter#test_insert_after = 0.00 s = . > TestSourceTreeRewriter#test_inserts_on_empty_ranges = 0.07 s = . > TestSourceTreeRewriter#test_replace = 0.00 s = . > TestSourceTreeRewriter#test_ordered_replacements = 0.00 s = . > TestSourceTreeRewriter#test_swallowed_insertions = 0.00 s = . > TestSourceTreeRewriter#test_merge = 0.02 s = . > TestSourceTreeRewriter#test_nested_actions = 0.00 s = . > TestSourceTreeRewriter#test_insert_before = 0.00 s = . > TestSourceTreeRewriter#test_replace_same_range = 0.00 s = . > TestSourceTreeRewriter#test_crossing_non_deletions = 0.00 s = . > TestSourceTreeRewriter#test_multiple_actions = 0.00 s = . > TestSourceTreeRewriter#test_out_of_range_ranges = 0.00 s = . > TestSourceTreeRewriter#test_remove = 0.00 s = . > TestSourceTreeRewriter#test_crossing_deletions = 0.00 s = . > TestSourceTreeRewriter#test_wrap = 0.00 s = . > TestSourceTreeRewriter#test_wraps_same_range = 0.00 s = . > TestParser#test_beginless_range_before_27 = 0.00 s = . > TestParser#test_comments_before_leading_dot__27 = 0.00 s = . > TestParser#test_parser_bug_490 = 0.06 s = . > TestParser#test_asgn_cmd =
Bug#996526: marked as done (rubygems: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed.)
Your message dated Tue, 23 Nov 2021 23:21:43 + with message-id and subject line Bug#996526: fixed in rubygems 3.2.27-3 has caused the Debian Bug report #996526, regarding rubygems: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed. to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 996526: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996526 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rubygems Version: 3.2.27-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, rubygems was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): > /usr/bin/ruby3.0 /usr/bin/gem2deb-test-runner > > ┌──┐ > │ Checking Rubygems dependency resolution on ruby3.0 > │ > └──┘ > > GEM_PATH=/<>/debian/ruby-bundler/usr/share/rubygems-integration/all:/<>/debian/ruby-rubygems/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.0.0:/var/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0 > ruby3.0 -e gem\ \"rubygems-update\" > GEM_PATH=/<>/debian/ruby-bundler/usr/share/rubygems-integration/all:/<>/debian/ruby-rubygems/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.0.0:/var/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0 > ruby3.0 -e gem\ \"bundler\" > > ┌──┐ > │ Run tests for ruby3.0 from debian/ruby-tests.rake > │ > └──┘ > > RUBYLIB=. > GEM_PATH=/<>/debian/ruby-bundler/usr/share/rubygems-integration/all:/<>/debian/ruby-rubygems/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.0.0:/var/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0 > ruby3.0 -S rake -f debian/ruby-tests.rake > > File does not exist: webrick > > rake aborted! > Command failed with status (1) > > Tasks: TOP => default => test > (See full trace by running task with --trace) > ERROR: Test "ruby3.0" failed. Note that webrick has been removed from the standard library. It's already been packaged and is currently in NEW, but this package now needs an explicit build dependency on it. The full build log is available at https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/rubygems/rubygems_3.2.27-1+rebuild1633399251_amd64.build.txt signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: rubygems Source-Version: 3.2.27-3 Done: Daniel Leidert We believe that the bug you reported is fixed in the latest version of rubygems, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 996...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Daniel Leidert (supplier of updated rubygems package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 23 Nov 2021 23:36:03 +0100 Source: rubygems Architecture: source Version: 3.2.27-3 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Team Changed-By: Daniel Leidert Closes: 996526 Changes: rubygems
Bug#996524: marked as pending in ruby-whitequark-parser
Control: tag -1 pending Hello, Bug #996524 in ruby-whitequark-parser 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-whitequark-parser/-/commit/50a09bacea441200b52d5554c816f644eb4775ca ruby-whitequark-parser (3.0.2.0-1) unstable This version adds Ruby 3.0 support (closes: #996524). (this message was generated automatically) -- Greetings https://bugs.debian.org/996524
Processed: Bug#996524 marked as pending in ruby-whitequark-parser
Processing control commands: > tag -1 pending Bug #996524 [src:ruby-whitequark-parser] ruby-whitequark-parser: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed. Added tag(s) pending. -- 996524: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996524 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#996526 marked as pending in rubygems
Processing control commands: > tag -1 pending Bug #996526 [src:rubygems] rubygems: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed. Added tag(s) pending. -- 996526: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996526 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996526: marked as pending in rubygems
Control: tag -1 pending Hello, Bug #996526 in rubygems 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/rubygems/-/commit/e848598f1d036f952d53ddb50d0610619f06de95 Update packaging files and fix FTBFS * d/bundler.docs: Add bundler/UPGRADING.md. * d/control (Standards-Version): Don't use the minor patch level. (Build-Depends): Add ruby-webrick (closes: #996526). * d/copyright: Add bundler copyright and license information. (Copyright): Update and add team. * d/watch: Update file. (this message was generated automatically) -- Greetings https://bugs.debian.org/996526
Bug#1000471: marked as done (glewlwyd FTBFS can't find functions.)
Your message dated Tue, 23 Nov 2021 22:37:30 +
with message-id
and subject line Bug#1000471: fixed in glewlwyd 2.6.0-1
has caused the Debian Bug report #1000471,
regarding glewlwyd FTBFS can't find functions.
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.)
--
1000471: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000471
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: glewlwyd
Version: 2.5.2-3
Severity: serious
Tags: ftbfs
Unfortunately it seems that even after the cross-fetch fix, glewlwyd still
FTBFS as a
result of changes in iddawc/rhonabwy.
/usr/bin/cc -D_GNU_SOURCE -Dschememodoauth2_EXPORTS -I/include -g -O2
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Werror -fPIC -Wextra -std=gnu99 -MD -MT
CMakeFiles/schememodoauth2.dir/src/scheme/oauth2.c.o -MF
CMakeFiles/schememodoauth2.dir/src/scheme/oauth2.c.o.d -o
CMakeFiles/schememodoauth2.dir/src/scheme/oauth2.c.o -c /<>/src/scheme/oauth2.c
/<>/src/scheme/oauth2.c: In function 'complete_session_identify':
/<>/src/scheme/oauth2.c:265:32: error: implicit declaration of
function 'i_load_userinfo'; did you mean 'i_get_userinfo'?
[-Werror=implicit-function-declaration]
265 | if ((res = i_load_userinfo(_session)) == I_OK &&
i_session.j_userinfo != NULL) {
|^~~
|i_get_userinfo
/<>/src/scheme/oauth2.c: In function
'user_auth_scheme_module_init':
/<>/src/scheme/oauth2.c:1197:28: error: implicit declaration of
function 'i_load_openid_config'; did you mean 'i_get_openid_config'?
[-Werror=implicit-function-declaration]
1197 | } else if (i_load_openid_config(_session) != I_OK) {
|^~~~
|i_get_openid_config
make -f CMakeFiles/protocol_oidc.dir/build.make
CMakeFiles/protocol_oidc.dir/depend
<---snip>
/usr/bin/cc -D_GNU_SOURCE -Dprotocol_register_EXPORTS -I/include -g -O2
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Werror -fPIC -Wextra -std=gnu99 -MD -MT
CMakeFiles/protocol_register.dir/src/plugin/register.c.o -MF
CMakeFiles/protocol_register.dir/src/plugin/register.c.o.d -o
CMakeFiles/protocol_register.dir/src/plugin/register.c.o -c
/<>/src/plugin/register.c
/<>/src/plugin/protocol_oidc.c: In function 'check_parameters':
/<>/src/plugin/protocol_oidc.c:272:45: error: implicit declaration
of function 'r_jwks_import_from_str'; did you mean 'r_jwks_import_from_uri'?
[-Werror=implicit-function-declaration]
272 | if (r_jwks_init() != RHN_OK || r_jwks_import_from_str(jwks,
json_string_value(json_object_get(j_params, "jwks-public"))) != RHN_OK) {
| ^~
| r_jwks_import_from_uri
I initially saw this on a raspbian bookworm-staging autobuilder, but I was also
able to reproduce
it in a Debian sid chroot.
I found upstream patches fixing the above errors and applied them in raspbian
bookworm-staging,
I also imported the cross-fetch fix into raspbian bookworm-staging from Debian
sid. After doing
so I was able to get a successful build of glewlwyd. A debdiff should appear
soon at
https://debdiffs.raspbian.org/main/g/glewlwyd
P.S. The cross-fetch fix also seems to be blocked from migrating to debian
testing as a result
of an autopkgtest failure.
--- End Message ---
--- Begin Message ---
Source: glewlwyd
Source-Version: 2.6.0-1
Done: Nicolas Mora
We believe that the bug you reported is fixed in the latest version of
glewlwyd, 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.
Nicolas Mora (supplier of updated glewlwyd 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 20:50:23 -0500
Source: glewlwyd
Architecture: source
Version: 2.6.0-1
Distribution: unstable
Processed: reopening 997311, found 997311 in 3.8.0-1 ...
Processing commands for cont...@bugs.debian.org:
> reopen 997311
Bug #997311 {Done: Daniel Leidert }
[src:ruby-rufus-scheduler] ruby-rufus-scheduler: FTBFS: ERROR: Test "ruby2.7"
failed: Failure/Error: expect(job.last_work_time).to be < 0.099
'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 ruby-rufus-scheduler/3.8.0-1.
> found 997311 3.8.0-1
Bug #997311 [src:ruby-rufus-scheduler] ruby-rufus-scheduler: FTBFS: ERROR: Test
"ruby2.7" failed: Failure/Error: expect(job.last_work_time).to be < 0.099
The source 'ruby-rufus-scheduler' and version '3.8.0-1' do not appear to match
any binary packages
Marked as found in versions ruby-rufus-scheduler/3.8.0-1.
> forwarded 997311 https://github.com/jmettraux/rufus-scheduler/issues/330
Bug #997311 [src:ruby-rufus-scheduler] ruby-rufus-scheduler: FTBFS: ERROR: Test
"ruby2.7" failed: Failure/Error: expect(job.last_work_time).to be < 0.099
Set Bug forwarded-to-address to
'https://github.com/jmettraux/rufus-scheduler/issues/330'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
997311: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997311
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#997959: git-annex: FTBFS on 32-bit ARM architectures, but built successfully before
Hello, On Wed 24 Nov 2021 at 02:21AM +0530, Nilesh Patra wrote: > Hi Sean, Richard, > > On Wed, 27 Oct 2021 12:20:04 -0700 Sean Whitton > wrote: >> Source: git-annex >> Version: 8.20210223-2 >> Severity: serious >> git-annex recently began to FTBFS on 32-bit ARM architectures, and I am >> not really in a position atm to dig deeply into the problem. >> [.. log ..] > > This bug is now triggering removals of its reverse-dependencies. > Would you (or any list member) have some bandwidth to take a deeper look into > this? I don't, I'm afraid. -- Sean Whitton signature.asc Description: PGP signature
Bug#1000471: glewlwyd FTBFS can't find functions.
Hello, Le 2021-11-23 à 15 h 20, peter green a écrit : Package: glewlwyd Version: 2.5.2-3 Severity: serious Tags: ftbfs Unfortunately it seems that even after the cross-fetch fix, glewlwyd still FTBFS as a result of changes in iddawc/rhonabwy. Thanks, that's because the dependencies were updated lately, and some api was changed. I have the package glewlwyd 2.6.0 ready to upload, as soon as node-i18next-http-backend 1.3.1+dfsg-3 will be available on my schroot, today or tomorrow. /Nicolas
Processed: Re: Bug#1000476: lintian: autopkgtest regression: autopkgtest_tmp/build-and-evaluate-test-packages/eval/checks/binaries/corrupted/legacy-debug/generic.t
Processing control commands: > tags -1 + pending Bug #1000476 [src:lintian] lintian: autopkgtest regression: autopkgtest_tmp/build-and-evaluate-test-packages/eval/checks/binaries/corrupted/legacy-debug/generic.t Added tag(s) pending. -- 1000476: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000476 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000476: lintian: autopkgtest regression: autopkgtest_tmp/build-and-evaluate-test-packages/eval/checks/binaries/corrupted/legacy-debug/generic.t
Control: tags -1 + pending Hi, Thanks for this message. On Tue, Nov 23, 2021 at 12:48 PM Paul Gevers wrote: > > ../../autopkgtest_tmp/build-and-evaluate-test-packages/eval/odd-inputs/strings-elf-detection/generic.t That test was already dropped from Lintian. [1] > ../../autopkgtest_tmp/build-and-evaluate-test-packages/eval/checks/binaries/corrupted/legacy-debug/generic.t That test was adjusted for recent versions of Binutils. [2] Kind regards Felix Lechner [1] https://salsa.debian.org/lintian/lintian/-/commit/deba665363a3dd4da8b806df07091c9c482206d7 [2] https://salsa.debian.org/lintian/lintian/-/commit/c16b75a7547e547a13a1f1add4d80bb72e16c361
Bug#996780: gnome-boxes: Systematic system freeze few seconds after launching a Windows WM
i'm not, i'm using intel drivers Le sam. 20 nov. 2021, 18 h 43, Gunnar Hjalmarsson a écrit : > Are you possibly using a NVIDIA driver? Asking because of this: > > https://github.com/NVIDIA/egl-wayland/issues/27#issuecomment-951725683 > > -- > Cheers, > Gunnar Hjalmarsson >
Bug#997959: git-annex: FTBFS on 32-bit ARM architectures, but built successfully before
Hi Sean, Richard, On Wed, 27 Oct 2021 12:20:04 -0700 Sean Whitton wrote: > Source: git-annex > Version: 8.20210223-2 > Severity: serious > git-annex recently began to FTBFS on 32-bit ARM architectures, and I am > not really in a position atm to dig deeply into the problem. > [.. log ..] This bug is now triggering removals of its reverse-dependencies. Would you (or any list member) have some bandwidth to take a deeper look into this? Let me know. Regards, Nilesh signature.asc Description: PGP signature
Bug#1000476: lintian: autopkgtest regression: autopkgtest_tmp/build-and-evaluate-test-packages/eval/checks/binaries/corrupted/legacy-debug/generic.t
Source: lintian Version: 2.113.0 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of lintian the autopkgtest of lintian fails in testing when that autopkgtest is run with the binary packages of lintian from unstable. It passes when run with only packages from testing. In tabular form: passfail lintianfrom testing2.113.0 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration to testing [1]. Can you please investigate the situation and fix it? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=lintian https://ci.debian.net/data/autopkgtest/testing/armhf/l/lintian/16912872/log.gz ../../autopkgtest_tmp/build-and-evaluate-test-packages/eval/tracking/generic-dh-make-2008/generic.t ok ../../autopkgtest_tmp/build-and-evaluate-test-packages/eval/lintian-features/lintian-suppress-tags/generic.t ... ok # Literal output does not match # # --- ../../autopkgtest_tmp/build-and-evaluate-test-packages/eval/odd-inputs/strings-elf-detection/literal # +++ ../../autopkgtest_tmp/build-and-evaluate-test-packages/eval/odd-inputs/strings-elf-detection/literal.actual.parsed # +W: strings-elf-detection-dbgsym: elf-error In program headers: Unable to find program interpreter name [usr/lib/debug/.build-id/45/e1c08eeb668890993873e92eb9c047c87cfb25.debug] # # Failed test 'Lintian passes for strings-elf-detection' # at /usr/share/lintian/lib/Test/Lintian/Run.pm line 341. # Looks like you failed 1 test of 1. ../../autopkgtest_tmp/build-and-evaluate-test-packages/eval/odd-inputs/strings-elf-detection/generic.t . Dubious, test returned 1 (wstat 256, 0x100) Failed 1/1 subtests ../../autopkgtest_tmp/build-and-evaluate-test-packages/eval/runner-features/runtests-options/generic.t . ok ../../autopkgtest_tmp/build-and-evaluate-test-packages/eval/tracking/generic-dh-make-2005/generic.t ok ../../autopkgtest_tmp/build-and-evaluate-test-packages/eval/lintian-features/lintian-display-level/generic.t ... ok ../../autopkgtest_tmp/build-and-evaluate-test-packages/eval/runner-features/runtests-calibration/generic.t . ok Test Summary Report --- ../../autopkgtest_tmp/build-and-evaluate-test-packages/eval/checks/binaries/corrupted/legacy-debug/generic.t (Wstat: 256 Tests: 1 Failed: 1) Failed test: 1 Non-zero exit status: 1 ../../autopkgtest_tmp/build-and-evaluate-test-packages/eval/odd-inputs/strings-elf-detection/generic.t (Wstat: 256 Tests: 1 Failed: 1) Failed test: 1 Non-zero exit status: 1 Files=1447, Tests=62792, 303 wallclock secs (11.66 usr 23.72 sys + 4309.74 cusr 32394.30 csys = 36739.42 CPU) Result: FAIL The test suite ran for 5 minutes and 4 seconds. autopkgtest [00:18:34]: test build-and-evaluate-test-packages OpenPGP_signature Description: OpenPGP digital signature
Bug#1000475: minimac4: autopkgtest regression: *** stack smashing detected ***: terminated
Source: minimac4 Version: 1.0.2-3 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of minimac4 the autopkgtest of minimac4 fails in testing when that autopkgtest is run with the binary packages of minimac4 from unstable. It passes when run with only packages from testing. In tabular form: passfail minimac4 from testing1.0.2-3 all others from testingfrom testing I copied some of the output at the bottom of this report. Similar to bug #1000413 I think this issue points at ABI breakage. The following in the changelog looks very suspicious: * Rebuild minimac4 against new version of libstatgen This is a hint. The test passes in unstable. Currently this regression is blocking the migration to testing [1]. Can you please investigate the situation and fix it? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=minimac4 https://ci.debian.net/data/autopkgtest/testing/amd64/m/minimac4/16920779/log.gz Minimac4 - Fast Imputation Based on State Space Reduction HMM (c) 2014 - Sayantan Das, Christian Fuchsberger, David Hinds Mary Kate Wing, Goncalo Abecasis Version: 1.0.2; Built: 2021-11-11 by Reproducible Command Line Options:Reference Haplotypes : --refHaps [refPanel.m3vcf.gz], --passOnly, --rsid, --referenceEstimates [ON], --mapFile [docs/geneticMapFile.b38.map.txt.gz] Target Haplotypes : --haps [targetStudy.vcf.gz] Output Parameters : --prefix [testRun], --estimate, --nobgzip, --vcfBuffer [200], --format [GT,DS], --allTypedSites, --meta, --memUsage Chunking Parameters : --ChunkLengthMb [20.00], --ChunkOverlapMb [3.00] Subset Parameters : --chr [], --start, --end, --window Approximation Parameters : --minimac3, --probThreshold [0.01], --diffThreshold [0.01], --topThreshold [0.01] Other Parameters : --log, --help, --cpus [5], --params PhoneHome : --noPhoneHome [ON], --phoneHomeThinning [50] URL = http://genome.sph.umich.edu/wiki/Minimac4 Starting Main Imputation/Estimation Analysis ... Performing preliminary check on input parameters... -- PRELIMINARY FILE CHECK -- Checking GWAS haplotype file : targetStudy.vcf.gz Gathering variant information ... ERROR !!! Empty Value for Individual : TA98 at First Marker Most probably a corrupted VCF file. Please check input VCF file !!! *** stack smashing detected ***: terminated Aborted autopkgtest [07:10:54]: test run-sample-analysis OpenPGP_signature Description: OpenPGP digital signature
Bug#992927: mutt: Mutt 2.1.2 is available, fixing a potential data-loss IMAP bug
On Tue, Nov 23, 2021 at 08:45:47PM +0100, Hannes von Haugwitz wrote: Is there any progress with this bug? Mutt 2.1.3 included the corrected sort commit referenced in my last email. So, for unstable/testing it would be nice to get 2.1.3 uploaded. For stable/oldstable I guess it rests in the hands of Debian process, but ideally the three links from my last email would be backported to those. -Kevin
Processed: Re: Bug#1000255: mpv: autopkgtest failures
Processing control commands: > reassign -1 src:python-mpv 0.5.2-1 Bug #1000255 [src:mpv] mpv: autopkgtest failures Bug reassigned from package 'src:mpv' to 'src:python-mpv'. No longer marked as found in versions mpv/0.34.0-1. Ignoring request to alter fixed versions of bug #1000255 to the same values previously set Bug #1000255 [src:python-mpv] mpv: autopkgtest failures Marked as found in versions python-mpv/0.5.2-1. > forwarded -1 https://github.com/jaseg/python-mpv/issues/187 Bug #1000255 [src:python-mpv] mpv: autopkgtest failures Set Bug forwarded-to-address to 'https://github.com/jaseg/python-mpv/issues/187'. -- 1000255: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000255 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000255: mpv: autopkgtest failures
Control: reassign -1 src:python-mpv 0.5.2-1 Control: forwarded -1 https://github.com/jaseg/python-mpv/issues/187 On 2021-11-21 23:21:24, Sebastian Ramacher wrote: > Control: tags -1 help > > On 2021-11-20 09:34:37 +0100, Gianfranco Costamagna wrote: > > Source: mpv > > Version: 0.34.0-1 > > Severity: serious > > > > > > Hello, the last version 0.34.0 is regressed on arm64 armhf and probably > > other architectures. > > > > Look, e.g. > > https://ci.debian.net/data/autopkgtest/testing/arm64/p/python-mpv/16812363/log.gz > > > > (Reading database ... 16518 files and directories currently installed.) > > Removing autopkgtest-satdep (0) ... > > autopkgtest [18:11:22]: test unittests: [--- > > === python3.9 === > > Segmentation fault > > autopkgtest [18:11:43]: test unittests: ---] > > autopkgtest [18:11:43]: test unittests: - - - - - - - - - - results - - - > > - - - - - - - > > unittestsFAIL non-zero exit status 139 > > autopkgtest [18:11:43]: summary > > unittestsFAIL non-zero exit status 139 > > > > I don't know which update triggered the regression, if the program itself > > or something else in the toolchain. > > > > Can you please have a look? > > > > https://ci.debian.net/packages/p/python-mpv/testing/arm64/ > > The failing test is test_write. It crashes due to an infinte recursion > in libx11-6's XPutImage which calls PutSubImage: > > #0 0xf4f3e31c in PutSubImage (dpy=dpy@entry=0x5776b8, d=d@entry=2097154, > gc=gc@entry=0x5a01e0, image=image@entry=0x5a2ca8, req_xoffset=0, > req_yoffset=req_yoffset@entry=0, x=0, y=y@entry=0, req_width=2096928, > req_height=req_height@entry=1, > dest_bits_per_pixel=dest_bits_per_pixel@entry=32, > dest_scanline_pad=dest_scanline_pad@entry=32) at ../../src/PutImage.c:878 > #1 0xf4f3e7a4 in PutSubImage (dpy=dpy@entry=0x5776b8, d=d@entry=2097154, > gc=gc@entry=0x5a01e0, image=image@entry=0x5a2ca8, req_xoffset=0, > req_yoffset=req_yoffset@entry=0, x=0, y=y@entry=0, req_width=2096928, > req_height=req_height@entry=1, > dest_bits_per_pixel=dest_bits_per_pixel@entry=32, > dest_scanline_pad=dest_scanline_pad@entry=32) at ../../src/PutImage.c:920 > #2 0xf4f3e7a4 in PutSubImage (dpy=dpy@entry=0x5776b8, d=d@entry=2097154, > gc=gc@entry=0x5a01e0, image=image@entry=0x5a2ca8, req_xoffset=0, > req_yoffset=req_yoffset@entry=0, x=0, y=y@entry=0, req_width=2096928, > req_height=req_height@entry=1, > dest_bits_per_pixel=dest_bits_per_pixel@entry=32, > dest_scanline_pad=dest_scanline_pad@entry=32) at ../../src/PutImage.c:920 > #3 0xf4f3e7a4 in PutSubImage (dpy=dpy@entry=0x5776b8, d=d@entry=2097154, > gc=gc@entry=0x5a01e0, image=image@entry=0x5a2ca8, req_xoffset=0, > req_yoffset=req_yoffset@entry=0, x=0, y=y@entry=0, req_width=2096928, > req_height=req_height@entry=1, > dest_bits_per_pixel=dest_bits_per_pixel@entry=32, > dest_scanline_pad=dest_scanline_pad@entry=32) at ../../src/PutImage.c:920 > #4 0xf4f3e7a4 in PutSubImage (dpy=dpy@entry=0x5776b8, d=d@entry=2097154, > gc=gc@entry=0x5a01e0, image=image@entry=0x5a2ca8, req_xoffset=0, > req_yoffset=req_yoffset@entry=0, x=0, y=y@entry=0, req_width=2096928, > req_height=req_height@entry=1, > dest_bits_per_pixel=dest_bits_per_pixel@entry=32, > dest_scanline_pad=dest_scanline_pad@entry=32) at ../../src/PutImage.c:920 > #5 0xf4f3e7a4 in PutSubImage (dpy=dpy@entry=0x5776b8, d=d@entry=2097154, > gc=gc@entry=0x5a01e0, image=image@entry=0x5a2ca8, req_xoffset=0, > req_yoffset=req_yoffset@entry=0, x=0, y=y@entry=0, req_width=2096928, > req_height=req_height@entry=1, > dest_bits_per_pixel=dest_bits_per_pixel@entry=32, > dest_scanline_pad=dest_scanline_pad@entry=32) at ../../src/PutImage.c:920 > #6 0xf4f3e7a4 in PutSubImage (dpy=dpy@entry=0x5776b8, d=d@entry=2097154, > gc=gc@entry=0x5a01e0, image=image@entry=0x5a2ca8, req_xoffset=0, > req_yoffset=req_yoffset@entry=0, x=0, y=y@entry=0, req_width=2096928, > req_height=req_height@entry=1, > dest_bits_per_pixel=dest_bits_per_pixel@entry=32, > dest_scanline_pad=dest_scanline_pad@entry=32) at ../../src/PutImage.c:920 > #7 0xf4f3e7a4 in PutSubImage (dpy=dpy@entry=0x5776b8, d=d@entry=2097154, > gc=gc@entry=0x5a01e0, image=image@entry=0x5a2ca8, req_xoffset=0, > req_yoffset=req_yoffset@entry=0, x=0, y=y@entry=0, req_width=2096928, > req_height=req_height@entry=1, > dest_bits_per_pixel=dest_bits_per_pixel@entry=32, > dest_scanline_pad=dest_scanline_pad@entry=32) at ../../src/PutImage.c:920 > #8 0xf4f3e7a4 in PutSubImage (dpy=dpy@entry=0x5776b8, d=d@entry=2097154, > gc=gc@entry=0x5a01e0, image=image@entry=0x5a2ca8, req_xoffset=0, > req_yoffset=req_yoffset@entry=0, x=0, y=y@entry=0, req_width=2096928, > req_height=req_height@entry=1, > dest_bits_per_pixel=dest_bits_per_pixel@entry=32, > dest_scanline_pad=dest_scanline_pad@entry=32) at ../../src/PutImage.c:920 > #9
Bug#1000471: glewlwyd FTBFS can't find functions.
Package: glewlwyd
Version: 2.5.2-3
Severity: serious
Tags: ftbfs
Unfortunately it seems that even after the cross-fetch fix, glewlwyd still
FTBFS as a
result of changes in iddawc/rhonabwy.
/usr/bin/cc -D_GNU_SOURCE -Dschememodoauth2_EXPORTS -I/include -g -O2
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Werror -fPIC -Wextra -std=gnu99 -MD -MT
CMakeFiles/schememodoauth2.dir/src/scheme/oauth2.c.o -MF
CMakeFiles/schememodoauth2.dir/src/scheme/oauth2.c.o.d -o
CMakeFiles/schememodoauth2.dir/src/scheme/oauth2.c.o -c /<>/src/scheme/oauth2.c
/<>/src/scheme/oauth2.c: In function 'complete_session_identify':
/<>/src/scheme/oauth2.c:265:32: error: implicit declaration of
function 'i_load_userinfo'; did you mean 'i_get_userinfo'?
[-Werror=implicit-function-declaration]
265 | if ((res = i_load_userinfo(_session)) == I_OK &&
i_session.j_userinfo != NULL) {
|^~~
|i_get_userinfo
/<>/src/scheme/oauth2.c: In function
'user_auth_scheme_module_init':
/<>/src/scheme/oauth2.c:1197:28: error: implicit declaration of
function 'i_load_openid_config'; did you mean 'i_get_openid_config'?
[-Werror=implicit-function-declaration]
1197 | } else if (i_load_openid_config(_session) != I_OK) {
|^~~~
|i_get_openid_config
make -f CMakeFiles/protocol_oidc.dir/build.make
CMakeFiles/protocol_oidc.dir/depend
<---snip>
/usr/bin/cc -D_GNU_SOURCE -Dprotocol_register_EXPORTS -I/include -g -O2
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Werror -fPIC -Wextra -std=gnu99 -MD -MT
CMakeFiles/protocol_register.dir/src/plugin/register.c.o -MF
CMakeFiles/protocol_register.dir/src/plugin/register.c.o.d -o
CMakeFiles/protocol_register.dir/src/plugin/register.c.o -c
/<>/src/plugin/register.c
/<>/src/plugin/protocol_oidc.c: In function 'check_parameters':
/<>/src/plugin/protocol_oidc.c:272:45: error: implicit declaration
of function 'r_jwks_import_from_str'; did you mean 'r_jwks_import_from_uri'?
[-Werror=implicit-function-declaration]
272 | if (r_jwks_init() != RHN_OK || r_jwks_import_from_str(jwks,
json_string_value(json_object_get(j_params, "jwks-public"))) != RHN_OK) {
| ^~
| r_jwks_import_from_uri
I initially saw this on a raspbian bookworm-staging autobuilder, but I was also
able to reproduce
it in a Debian sid chroot.
I found upstream patches fixing the above errors and applied them in raspbian
bookworm-staging,
I also imported the cross-fetch fix into raspbian bookworm-staging from Debian
sid. After doing
so I was able to get a successful build of glewlwyd. A debdiff should appear
soon at
https://debdiffs.raspbian.org/main/g/glewlwyd
P.S. The cross-fetch fix also seems to be blocked from migrating to debian
testing as a result
of an autopkgtest failure.
Bug#992927: mutt: Mutt 2.1.2 is available, fixing a potential data-loss IMAP bug
Hello, Is there any progress with this bug? Best regards Hannes
Bug#997311: marked as done (ruby-rufus-scheduler: FTBFS: ERROR: Test "ruby2.7" failed: Failure/Error: expect(job.last_work_time).to be < 0.099)
Your message dated Tue, 23 Nov 2021 19:34:35 +
with message-id
and subject line Bug#997311: fixed in ruby-rufus-scheduler 3.8.0-1
has caused the Debian Bug report #997311,
regarding ruby-rufus-scheduler: FTBFS: ERROR: Test "ruby2.7" failed:
Failure/Error: expect(job.last_work_time).to be < 0.099
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.)
--
997311: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997311
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-rufus-scheduler
Version: 3.4.2-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> Failure/Error: expect(job.last_work_time).to be < 0.099
>
>expected: < 0.099
> got: 0.10007190704345703
> # ./spec/job_spec.rb:634:in `block (4 levels) in '
>
> Finished in 3 minutes 6 seconds (files took 0.21446 seconds to load)
> 353 examples, 1 failure, 2 pending
>
> Failed examples:
>
> rspec ./spec/job_spec.rb:622 # Rufus::Scheduler::Job work time
> #mean_work_time gathers work times and computes the mean
>
> /usr/bin/ruby2.7
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib
> /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/exe/rspec
> --pattern ./spec/\*\*/\*_spec.rb --format documentation failed
> ERROR: Test "ruby2.7" failed:
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/ruby-rufus-scheduler_3.4.2-1_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: ruby-rufus-scheduler
Source-Version: 3.8.0-1
Done: Daniel Leidert
We believe that the bug you reported is fixed in the latest version of
ruby-rufus-scheduler, 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 997...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Daniel Leidert (supplier of updated ruby-rufus-scheduler
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 23 Nov 2021 18:39:17 +0100
Source: ruby-rufus-scheduler
Architecture: source
Version: 3.8.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team
Changed-By: Daniel Leidert
Closes: 997311
Changes:
ruby-rufus-scheduler (3.8.0-1) unstable; urgency=medium
.
* Team upload.
* New upstream release.
- Improves upstream tests and hopefully closes: #997311.
.
[ Debian Janitor ]
* Trim trailing whitespace.
* Use secure copyright file specification URI.
* Use secure URI in Homepage field.
* Bump debhelper from deprecated 9 to 13.
* Set debhelper-compat version in Build-Depends.
* Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
Repository-Browse.
* Update Vcs-* headers from URL redirect.
* Use canonical URL in Vcs-Git.
.
[ Daniel Leidert ]
* d/control: Add Rules-Requires-Root field.
(Standards-Version): Bump to 4.6.0.
(Build-Depends): Remove ruby-et-orbi and add ruby-fugit instead.
(Depends): Remove interpreters and use ${ruby:Depends}.
* d/copyright: Add Upstream-Contact field.
(Copyright): Update and add team.
* d/rules: Use gem installation layout and install upstream changelog.
* d/watch: Update file.
* d/patches/Modernize-spec-job_spec.rb.patch: Add patch.
- Add latest test improvements from upstream's master branch (see #997311).
* d/patches/0002-Relax-path-related-tests-for-buildds.patch: Add patch.
- Relax some tests checking the assumed path on our buildds.
- Sort array before comparison.
* d/patches/series: Enable patch.
*
Bug#997467: marked as done (python-certbot-dns-rfc2136: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13)
Your message dated Tue, 23 Nov 2021 14:24:53 -0500
with message-id
and subject line Re: Bug#997467: python-certbot-dns-rfc2136: FTBFS:
dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9
returned exit code 13
has caused the Debian Bug report #997467,
regarding python-certbot-dns-rfc2136: FTBFS: dh_auto_test: error: pybuild
--test --test-pytest -i python{version} -p 3.9 returned exit code 13
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.)
--
997467: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997467
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-certbot-dns-rfc2136
Version: 1.10.1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 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 '/<>'
> dh_auto_build
> I: pybuild base:232: /usr/bin/python3 setup.py build
> running build
> running build_py
> creating
> /<>/.pybuild/cpython3_3.9_certbot-dns-rfc2136/build/certbot_dns_rfc2136
> copying certbot_dns_rfc2136/__init__.py ->
> /<>/.pybuild/cpython3_3.9_certbot-dns-rfc2136/build/certbot_dns_rfc2136
> creating
> /<>/.pybuild/cpython3_3.9_certbot-dns-rfc2136/build/certbot_dns_rfc2136/_internal
> copying certbot_dns_rfc2136/_internal/dns_rfc2136.py ->
> /<>/.pybuild/cpython3_3.9_certbot-dns-rfc2136/build/certbot_dns_rfc2136/_internal
> copying certbot_dns_rfc2136/_internal/__init__.py ->
> /<>/.pybuild/cpython3_3.9_certbot-dns-rfc2136/build/certbot_dns_rfc2136/_internal
> running egg_info
> writing certbot_dns_rfc2136.egg-info/PKG-INFO
> writing dependency_links to certbot_dns_rfc2136.egg-info/dependency_links.txt
> writing entry points to certbot_dns_rfc2136.egg-info/entry_points.txt
> writing requirements to certbot_dns_rfc2136.egg-info/requires.txt
> writing top-level names to certbot_dns_rfc2136.egg-info/top_level.txt
> reading manifest file 'certbot_dns_rfc2136.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> warning: no previously-included files matching '__pycache__' found anywhere
> in distribution
> warning: no previously-included files matching '*.py[cod]' found anywhere in
> distribution
> adding license file 'LICENSE.txt'
> writing manifest file 'certbot_dns_rfc2136.egg-info/SOURCES.txt'
> PYTHONPATH=. \
> http_proxy='127.0.0.1:9' \
> https_proxy='127.0.0.1:9' \
> sphinx-build -N -bhtml docs/ build/html
> Running Sphinx v4.2.0
> loading translations [en]... done
> making output directory... done
> WARNING: html_static_path entry '_static' does not exist
> loading intersphinx inventory from https://docs.python.org/objects.inv...
> loading intersphinx inventory from
> https://acme-python.readthedocs.org/en/latest/objects.inv...
> loading intersphinx inventory from https://certbot.eff.org/docs/objects.inv...
> WARNING: failed to reach any of the inventories with the following issues:
> intersphinx inventory 'https://docs.python.org/objects.inv' not fetchable due
> to : Proxy URL had no scheme, should
> start with http:// or https://
> WARNING: failed to reach any of the inventories with the following issues:
> intersphinx inventory
> 'https://acme-python.readthedocs.org/en/latest/objects.inv' not fetchable due
> to : Proxy URL had no scheme, should
> start with http:// or https://
> WARNING: failed to reach any of the inventories with the following issues:
> intersphinx inventory 'https://certbot.eff.org/docs/objects.inv' not
> fetchable due to : Proxy URL had no
> scheme, should start with http:// or https://
> building [mo]: targets for 0 po files that are out of date
> building [html]: targets for 2 source files that are out of date
> updating environment: [new config] 2 added, 0 changed, 0 removed
> reading sources... [ 50%] api
> reading sources... [100%] index
>
> looking for now-outdated files... none found
> pickling environment... done
> checking consistency... done
> preparing documents... done
> writing output... [ 50%] api
> writing output... [100%] index
>
> generating indices... genindex py-modindex done
> writing additional pages... search done
> copying static files... done
> copying extra files... done
> dumping search index in English (code: en)... done
> dumping object inventory... done
> build succeeded, 4 warnings.
>
> The HTML pages are in build/html.
> make[1]: Leaving directory '/<>'
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:232: cd
>
Processed: hashdeep: diff for NMU version 4.4-7.1
Processing control commands: > tags 984166 + patch Bug #984166 [src:hashdeep] hashdeep: ftbfs with GCC-11 Added tag(s) patch. > tags 984166 + pending Bug #984166 [src:hashdeep] hashdeep: ftbfs with GCC-11 Added tag(s) pending. -- 984166: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984166 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#984166: hashdeep: diff for NMU version 4.4-7.1
Control: tags 984166 + patch
Control: tags 984166 + pending
Dear maintainer,
I've prepared an NMU for hashdeep (versioned as 4.4-7.1) and uploaded
it to DELAYED/14. Please feel free to tell me if I should cancel it.
cu
Adrian
diff -Nru hashdeep-4.4/debian/changelog hashdeep-4.4/debian/changelog
--- hashdeep-4.4/debian/changelog 2021-02-02 18:41:47.0 +0200
+++ hashdeep-4.4/debian/changelog 2021-11-23 20:46:29.0 +0200
@@ -1,3 +1,10 @@
+hashdeep (4.4-7.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Add upstream fix for FTBFS with gcc 11. (Closes: #984166)
+
+ -- Adrian Bunk Tue, 23 Nov 2021 20:46:29 +0200
+
hashdeep (4.4-7) unstable; urgency=medium
[ Debian Janitor ]
diff -Nru hashdeep-4.4/debian/patches/0001-Fix-errors-found-by-clang.patch hashdeep-4.4/debian/patches/0001-Fix-errors-found-by-clang.patch
--- hashdeep-4.4/debian/patches/0001-Fix-errors-found-by-clang.patch 1970-01-01 02:00:00.0 +0200
+++ hashdeep-4.4/debian/patches/0001-Fix-errors-found-by-clang.patch 2021-11-23 20:46:15.0 +0200
@@ -0,0 +1,32 @@
+From 6ef69a26126ee4e69a25392fd456b8a66c51dffd Mon Sep 17 00:00:00 2001
+From: Khem Raj
+Date: Tue, 15 Nov 2016 02:46:55 +
+Subject: Fix errors found by clang
+
+Fixes errors like
+
+../../git/src/hash.cpp:282:19: error: ordered comparison between pointer and zero ('const unsigned char *' and 'int')
+if(fdht->base>0){
+ ~~^~
+
+Signed-off-by: Khem Raj
+---
+ src/hash.cpp | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/src/hash.cpp b/src/hash.cpp
+index 4216157..52f419b 100644
+--- a/src/hash.cpp
b/src/hash.cpp
+@@ -279,7 +279,7 @@ void file_data_hasher_t::hash()
+ MAP_FILE|
+ #endif
+ MAP_SHARED,fd,0);
+- if(fdht->base>0){
++ if(fdht->base != (void *) -1){
+ /* mmap is successful, so set the bounds.
+ * if it is not successful, we default to reading the fd
+ */
+--
+2.20.1
+
diff -Nru hashdeep-4.4/debian/patches/series hashdeep-4.4/debian/patches/series
--- hashdeep-4.4/debian/patches/series 2021-02-02 18:41:47.0 +0200
+++ hashdeep-4.4/debian/patches/series 2021-11-23 20:46:29.0 +0200
@@ -1,2 +1,3 @@
fix-manpages.patch
fix-FTBFS-Hurd.patch
+0001-Fix-errors-found-by-clang.patch
Processed: This is a FTBFS
Processing commands for cont...@bugs.debian.org: > reassign 1000388 src:parlatype 3.0-1 Bug #1000388 [parlatype] FTBFS on s390x due to whitespace damage Bug reassigned from package 'parlatype' to 'src:parlatype'. No longer marked as found in versions parlatype/3.0-1. Ignoring request to alter fixed versions of bug #1000388 to the same values previously set Bug #1000388 [src:parlatype] FTBFS on s390x due to whitespace damage Marked as found in versions parlatype/3.0-1. > tags 1000388 ftbfs Bug #1000388 [src:parlatype] FTBFS on s390x due to whitespace damage Added tag(s) ftbfs. > severity 1000388 serious Bug #1000388 [src:parlatype] FTBFS on s390x due to whitespace damage Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 1000388: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000388 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000467: rpm, autopkgtest failure on armhf
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
Bug#1000466: phonopy: autopkgtest failure
Source: phonopy
Version: 2.12.0-1
Severity: serious
https://ci.debian.net/data/autopkgtest/testing/amd64/p/phonopy/16901578/log.gz
...
=== FAILURES ===
_ test_QHA_Si __
self =
initial_parameters = [-43.375124, 1.0, 4.0, 163.32]
def fit(self, initial_parameters):
"""Fit."""
import logging
import sys
import warnings
try:
> import scipy
E ModuleNotFoundError: No module named 'scipy'
/usr/lib/python3/dist-packages/phonopy/qha/eos.py:133: ModuleNotFoundError
During handling of the above exception, another exception occurred:
def test_QHA_Si():
"""Test of QHA calculation by Si."""
indices = list(range(11))
> phonopy_qha = PhonopyQHA(
volumes=ev_vs_v[indices, 0],
electronic_energies=ev_vs_v[indices, 1],
eos="vinet",
temperatures=temperatures,
free_energy=fe_phonon[:, indices],
cv=cv[:, indices],
entropy=entropy[:, indices],
t_max=1000,
verbose=True,
)
test/qha/test_QHA.py:154:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
/usr/lib/python3/dist-packages/phonopy/api_qha.py:105: in __init__
self._bulk_modulus = BulkModulus(volumes, electronic_energies, eos=eos)
/usr/lib/python3/dist-packages/phonopy/qha/core.py:82: in __init__
) = fit_to_eos(volumes, self._energies, self._eos)
/usr/lib/python3/dist-packages/phonopy/qha/eos.py:101: in fit_to_eos
fit.fit([fe[len(fe) // 2], 1.0, 4.0, volumes[len(volumes) // 2]])
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
self =
initial_parameters = [-43.375124, 1.0, 4.0, 163.32]
def fit(self, initial_parameters):
"""Fit."""
import logging
import sys
import warnings
try:
import scipy
from scipy.optimize import leastsq
except ImportError:
print("You need to install python-scipy.")
> sys.exit(1)
E SystemExit: 1
/usr/lib/python3/dist-packages/phonopy/qha/eos.py:137: SystemExit
- Captured stdout call -
You need to install python-scipy.
=== short test summary info
FAILED test/qha/test_QHA.py::test_QHA_Si - SystemExit: 1
= 1 failed, 138 passed, 1 skipped in 62.19s (0:01:02) ==
autopkgtest [15:31:27]: test command1: ---]
autopkgtest [15:31:27]: test command1: - - - - - - - - - - results - - - - - -
- - - -
python3-scipy is a !nocheck build dependency.
Processed: closing 998706
Processing commands for cont...@bugs.debian.org: > close 998706 6.0~rc0-1 Bug #998706 [mercurial] git breaks mercurial autopkgtest: Failed test-convert-git.t: output changed Marked as fixed in versions mercurial/6.0~rc0-1. Bug #998706 [mercurial] git breaks mercurial autopkgtest: Failed test-convert-git.t: output changed Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 998706: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998706 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 1 error): Re: git breaks mercurial autopkgtest: Failed test-convert-git.t: output changed
Processing control commands: > reassign -1 mercurial 5.9.3-1 Bug #998706 [src:git, src:mercurial] git breaks mercurial autopkgtest: Failed test-convert-git.t: output changed Bug reassigned from package 'src:git, src:mercurial' to 'mercurial'. No longer marked as found in versions mercurial/5.9.3-1 and git/1:2.33.1-1. Ignoring request to alter fixed versions of bug #998706 to the same values previously set Bug #998706 [mercurial] git breaks mercurial autopkgtest: Failed test-convert-git.t: output changed Marked as found in versions mercurial/5.9.3-1. > close -1 mercurial/6.0~rc0-1 Unknown command or malformed arguments to command. -- 998706: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998706 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#998706: git breaks mercurial autopkgtest: Failed test-convert-git.t: output changed
Control: reassign -1 mercurial 5.9.3-1 Control: close -1 mercurial/6.0~rc0-1 On Sat, Nov 06, 2021 at 09:57:34PM +0100, Paul Gevers wrote: > Source: git, mercurial > Control: found -1 git/1:2.33.1-1 > Control: found -1 mercurial/5.9.3-1 > Severity: serious > Tags: sid bookworm > X-Debbugs-CC: debian...@lists.debian.org > User: debian...@lists.debian.org > Usertags: breaks needs-update > > Dear maintainer(s), > > With a recent upload of git the autopkgtest of mercurial fails in > testing when that autopkgtest is run with the binary packages of git > from unstable. It passes when run with only packages from testing. In > tabular form: > >passfail > gitfrom testing1:2.33.1-1 > mercurial from testing5.9.3-1 > all others from testingfrom testing > Fixed in mercurial 6.0 by https://www.mercurial-scm.org/repo/hg/rev/fd3d4b7f8e62 Cheers, Julien
Processed: grfcodec: diff for NMU version 6.0.6-5.1
Processing control commands: > tags 984158 + patch Bug #984158 [src:grfcodec] grfcodec: ftbfs with GCC-11 Added tag(s) patch. > tags 984158 + pending Bug #984158 [src:grfcodec] grfcodec: ftbfs with GCC-11 Added tag(s) pending. -- 984158: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984158 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#984158: grfcodec: diff for NMU version 6.0.6-5.1
Control: tags 984158 + patch
Control: tags 984158 + pending
Dear maintainer,
I've prepared an NMU for grfcodec (versioned as 6.0.6-5.1) and uploaded
it to DELAYED/15. Please feel free to tell me if I should cancel it, or
to use the changes for a maintainer upload instead.
cu
Adrian
diff -Nru grfcodec-6.0.6/debian/changelog grfcodec-6.0.6/debian/changelog
--- grfcodec-6.0.6/debian/changelog 2020-08-12 15:39:33.0 +0300
+++ grfcodec-6.0.6/debian/changelog 2021-11-23 19:42:54.0 +0200
@@ -1,3 +1,10 @@
+grfcodec (6.0.6-5.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Backport upstream fixes for FTBFS with gcc 11. (Closes: #984158)
+
+ -- Adrian Bunk Tue, 23 Nov 2021 19:42:54 +0200
+
grfcodec (6.0.6-5) unstable; urgency=medium
* [99dfb79] Fix FTBFS with gcc-10 (Closes: 957307)
diff -Nru grfcodec-6.0.6/debian/patches/0001-Fix-name-conflict-with-std-data-c-17.patch grfcodec-6.0.6/debian/patches/0001-Fix-name-conflict-with-std-data-c-17.patch
--- grfcodec-6.0.6/debian/patches/0001-Fix-name-conflict-with-std-data-c-17.patch 1970-01-01 02:00:00.0 +0200
+++ grfcodec-6.0.6/debian/patches/0001-Fix-name-conflict-with-std-data-c-17.patch 2021-11-23 19:42:17.0 +0200
@@ -0,0 +1,95 @@
+From 18ab320d97e2312f18f8fc69f9c610f86dd2ca05 Mon Sep 17 00:00:00 2001
+From: glx
+Date: Fri, 29 Nov 2019 01:12:45 +0100
+Subject: Fix: name conflict with std::data (c++17)
+
+---
+ src/data.cpp | 26 +-
+ 1 file changed, 13 insertions(+), 13 deletions(-)
+
+diff --git a/src/data.cpp b/src/data.cpp
+index e319c40..0781240 100644
+--- a/src/data.cpp
b/src/data.cpp
+@@ -1046,7 +1046,7 @@ struct dat{
+ #undef DATA
+ #undef DATA_FILE
+ #undef END_DATA
+-#define DATA() static const dat data[]={
++#define DATA() static const dat datafiles[]={
+ #define DATA_FILE(name)\
+ {(char*)_dat##name,"/.nforenum/" #name ".dat",sizeof(_dat##name)-1},\
+
+@@ -1126,11 +1126,11 @@ FILE*tryopen(const char*name,const char*mode,bool allownull=false){
+ }
+
+ FILE*_myfopen(files file, bool write){
+- FILE*pFile=tryopen(data[file].name,"rb",true);
++ FILE*pFile=tryopen(datafiles[file].name,"rb",true);
+ if(pFile){
+- if(fgetc(pFile)==data[file].data[0]&(pFile)>=data[file].data[1]){
++ if(fgetc(pFile)==datafiles[file].data[0]&(pFile)>=datafiles[file].data[1]){
+ if(file>datfeat && (uint)fgetc(pFile)(data[file].data), data[file].len, "rb");
++ pFile = fmemopen(const_cast(datafiles[file].data), datafiles[file].len, "rb");
+ if (pFile == NULL) {
+- IssueMessage(0, DATAFILE_ERROR, OPEN, data[file].name + 1, ERRNO, errno);
++ IssueMessage(0, DATAFILE_ERROR, OPEN, datafiles[file].name + 1, ERRNO, errno);
+ perror(NULL);
+ assert(false);
+ exit(EDATA);
+@@ -1150,19 +1150,19 @@ FILE*_myfopen(files file, bool write){
+ } else
+ #endif /* WITH_FMEMOPEN */
+ {
+- pFile = tryopen(data[file].name,"wb");
+- if (fwrite(data[file].data, 1, data[file].len, pFile) != data[file].len) {
+- IssueMessage(0, DATAFILE_ERROR, WRITE, data[file].name + 1, -1);
++ pFile = tryopen(datafiles[file].name,"wb");
++ if (fwrite(datafiles[file].data, 1, datafiles[file].len, pFile) != datafiles[file].len) {
++ IssueMessage(0, DATAFILE_ERROR, WRITE, datafiles[file].name + 1, -1);
+ assert(false);
+ exit(EDATA);
+ }
+ fclose(pFile);
+- pFile = tryopen(data[file].name,"rb");
++ pFile = tryopen(datafiles[file].name,"rb");
+ }
+ fgetc(pFile);
+ fgetc(pFile);
+ if(file>datfeat && (uint)fgetc(pFile)
+Bug-Debian: https://bugs.debian.org/984158
+Forwarded: https://github.com/OpenTTD/grfcodec/commit/8ed61cfc3a1c97b221027b0a511e018768bac69d
+
+--- grfcodec-6.0.6.orig/Makefile
grfcodec-6.0.6/Makefile
+@@ -96,7 +96,7 @@ FLAGS += -DWITH_PNG $(shell $(LIBPNG_CON
+ endif
+ endif
+
+-MY_CXXFLAGS ?= $(FLAGS) $(CXXFLAGS)
++MY_CXXFLAGS ?= $(FLAGS) $(CXXFLAGS) -std=gnu++11
+
+ # ===
+ # setup verbose/non-verbose make process
diff -Nru grfcodec-6.0.6/debian/patches/series grfcodec-6.0.6/debian/patches/series
--- grfcodec-6.0.6/debian/patches/series 2020-08-12 15:39:33.0 +0300
+++ grfcodec-6.0.6/debian/patches/series 2021-11-23 19:42:49.0 +0200
@@ -1,3 +1,5 @@
# Series of quilt patches
endian_check_cpp_abort_on_ftbfs.patch
gcc_10_ftbfs.patch
+cxx11.patch
+0001-Fix-name-conflict-with-std-data-c-17.patch
Processed: block 984145 with 998143
Processing commands for cont...@bugs.debian.org:
> block 984145 with 998143
Bug #984145 {Done: Andreas Tille } [src:gatb-core] gatb-core:
ftbfs with GCC-11
984145 was not blocked by any bugs.
984145 was not blocking any bugs.
Added blocking bug(s) of 984145: 998143
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
984145: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984145
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#984382: vdr: diff for NMU version 2.4.1-4.2
Control: tags 984382 + patch
Control: tags 984382 + pending
Dear maintainer,
I've prepared an NMU for vdr (versioned as 2.4.1-4.2) and uploaded
it to DELAYED/7. Please feel free to tell me if I should cancel it.
cu
Adrian
diff -Nru vdr-2.4.1/debian/changelog vdr-2.4.1/debian/changelog
--- vdr-2.4.1/debian/changelog 2020-07-19 20:22:51.0 +0300
+++ vdr-2.4.1/debian/changelog 2021-11-23 19:13:46.0 +0200
@@ -1,3 +1,10 @@
+vdr (2.4.1-4.2) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Add upstream fixes for gcc 11. (Closes: #984382)
+
+ -- Adrian Bunk Tue, 23 Nov 2021 19:13:46 +0200
+
vdr (2.4.1-4.1) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru vdr-2.4.1/debian/patches/0001-Fixed-checking-the-return-value-of-the-Open-call-in-.patch vdr-2.4.1/debian/patches/0001-Fixed-checking-the-return-value-of-the-Open-call-in-.patch
--- vdr-2.4.1/debian/patches/0001-Fixed-checking-the-return-value-of-the-Open-call-in-.patch 1970-01-01 02:00:00.0 +0200
+++ vdr-2.4.1/debian/patches/0001-Fixed-checking-the-return-value-of-the-Open-call-in-.patch 2021-11-23 19:13:46.0 +0200
@@ -0,0 +1,28 @@
+From 515e34727df9aad10f91af8f359cbf65255ab341 Mon Sep 17 00:00:00 2001
+From: Klaus Schmidinger
+Date: Wed, 16 Sep 2020 13:30:59 +0200
+Subject: Fixed checking the return value of the Open() call in
+ cFileName::SetOffset()
+
+---
+ recording.c | 4 ++--
+ 1 file changed, 2 insertions(+), 2 deletions(-)
+
+diff --git a/recording.c b/recording.c
+index 810ef809..045f14ed 100644
+--- a/recording.c
b/recording.c
+@@ -3025,8 +3025,8 @@ cUnbufferedFile *cFileName::SetOffset(int Number, off_t Offset)
+}
+ // found a non existing file suffix
+ }
+- if (Open() >= 0) {
+-if (!record && Offset >= 0 && file && file->Seek(Offset, SEEK_SET) != Offset) {
++ if (Open()) {
++if (!record && Offset >= 0 && file->Seek(Offset, SEEK_SET) != Offset) {
+LOG_ERROR_STR(fileName);
+return NULL;
+}
+--
+2.20.1
+
diff -Nru vdr-2.4.1/debian/patches/0002-Now-using-__cplusplus-instead-of-DISABLE_TEMPLATES_C.patch vdr-2.4.1/debian/patches/0002-Now-using-__cplusplus-instead-of-DISABLE_TEMPLATES_C.patch
--- vdr-2.4.1/debian/patches/0002-Now-using-__cplusplus-instead-of-DISABLE_TEMPLATES_C.patch 1970-01-01 02:00:00.0 +0200
+++ vdr-2.4.1/debian/patches/0002-Now-using-__cplusplus-instead-of-DISABLE_TEMPLATES_C.patch 2021-11-23 19:13:46.0 +0200
@@ -0,0 +1,49 @@
+From 6ead2ee35e94e70fc464f48e69d6d06371fbd9af Mon Sep 17 00:00:00 2001
+From: Klaus Schmidinger
+Date: Wed, 26 May 2021 13:37:53 +0200
+Subject: Now using __cplusplus instead of
+ DISABLE_TEMPLATES_COLLIDING_WITH_STL, and using std::min(), std::max() and
+ std::swap() if available
+
+---
+ tools.h | 20 +++-
+ 1 file changed, 11 insertions(+), 9 deletions(-)
+
+diff --git a/tools.h b/tools.h
+index 614130d0..6a016c70 100644
+--- a/tools.h
b/tools.h
+@@ -51,19 +51,21 @@ template inline void DELETENULL(T *) { T *q = p; p = NULL; delete q;
+ #define CHECK(s) { if ((s) < 0) LOG_ERROR; } // used for 'ioctl()' calls
+ #define FATALERRNO (errno && errno != EAGAIN && errno != EINTR)
+
+-// In case some plugin needs to use the STL and gets an error message regarding one
+-// of these functions, you can #define DISABLE_TEMPLATES_COLLIDING_WITH_STL before
+-// including tools.h.
+-#if !defined(__STL_CONFIG_H) // for old versions of the STL
+-#if !defined(DISABLE_TEMPLATES_COLLIDING_WITH_STL) && !defined(_STL_ALGOBASE_H)
++#if __cplusplus >= 201103L
++// any gcc >= 4.8.1; we have swap, min, max
++#include // std::min, std::max, (c++98: also swap)
++#include // std::swap (since c++11)
++using std::min;
++using std::max;
++using std::swap;
++#else
++// no c++11 and old compiler, let's include our own templates
+ template inline T min(T a, T b) { return a <= b ? a : b; }
+ template inline T max(T a, T b) { return a >= b ? a : b; }
+-#endif
+-template inline int sgn(T a) { return a < 0 ? -1 : a > 0 ? 1 : 0; }
+-#if !defined(DISABLE_TEMPLATES_COLLIDING_WITH_STL) && !defined(_MOVE_H)
+ template inline void swap(T , T ) { T t = a; a = b; b = t; }
+ #endif
+-#endif
++
++template inline int sgn(T a) { return a < 0 ? -1 : a > 0 ? 1 : 0; }
+
+ template inline T constrain(T v, T l, T h) { return v < l ? l : v > h ? h : v; }
+
+--
+2.20.1
+
diff -Nru vdr-2.4.1/debian/patches/series vdr-2.4.1/debian/patches/series
--- vdr-2.4.1/debian/patches/series 2020-07-19 20:22:51.0 +0300
+++ vdr-2.4.1/debian/patches/series 2021-11-23 19:13:40.0 +0200
@@ -7,3 +7,5 @@
use-cpp-flags.patch
configurable-pkg-config.patch
glibc-stime.patch
+0001-Fixed-checking-the-return-value-of-the-Open-call-in-.patch
+0002-Now-using-__cplusplus-instead-of-DISABLE_TEMPLATES_C.patch
Processed: vdr: diff for NMU version 2.4.1-4.2
Processing control commands: > tags 984382 + patch Bug #984382 [src:vdr] vdr: ftbfs with GCC-11 Added tag(s) patch. > tags 984382 + pending Bug #984382 [src:vdr] vdr: ftbfs with GCC-11 Added tag(s) pending. -- 984382: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984382 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1000439: fcitx5: icons of individual input methods are not being displayed
Processing control commands: > severity -1 serious Bug #1000439 [fcitx5] fcitx5: icons of individual input methods are not being displayed Severity set to 'serious' from 'normal' -- 1000439: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000439 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#995015: marked as done (dnsdiag: Error when running: DeprecationWarning)
Your message dated Tue, 23 Nov 2021 16:48:49 + with message-id and subject line Bug#995015: fixed in dnsdiag 1.7.0-1.1 has caused the Debian Bug report #995015, regarding dnsdiag: Error when running: DeprecationWarning 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.) -- 995015: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995015 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: dnsdiag Version: 1.7.0-1 Severity: grave Justification: renders package unusable When running dnseval, it gives the following error: abrantes@FLS12STI-D002:~$ dnseval -f /tmp/dns -c 1000 web.whatsapp.com server avg(ms) min(ms) max(ms) stddev(ms) lost(%) ttl flags --- /bin/dnseval:176: DeprecationWarning: please use dns.resolver.Resolver.resolve() instead answers = resolver.query(fqdn, dnsrecord, tcp=use_tcp, 221.182.100.10 1.124 0.613 7.534 0.410 %0 3242 QR -- -- RD RA -- -- abrantes@FLS12STI-D002:~$ cat /tmp/dns 8.8.8.8 abrantes@FLS12STI-D002:~$ Any other DNS also occurs. I noticed that on Debian 10, it works normally. On Debian 11 and 12 the same error occurs. Regards -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (990, 'testing'), (400, 'unstable'), (300, 'experimental'), (200, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-8-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), LANGUAGE=pt_BR:pt:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages dnsdiag depends on: ii python3 3.9.2-3 ii python3-cymruwhois 1.6-3.2 ii python3-dnspython 2.0.0-1 dnsdiag recommends no packages. dnsdiag suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: dnsdiag Source-Version: 1.7.0-1.1 Done: Adrian Bunk We believe that the bug you reported is fixed in the latest version of dnsdiag, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 995...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Adrian Bunk (supplier of updated dnsdiag package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 23 Nov 2021 17:49:52 +0200 Source: dnsdiag Architecture: source Version: 1.7.0-1.1 Distribution: unstable Urgency: medium Maintainer: Ana Custura Changed-By: Adrian Bunk Closes: 995015 Changes: dnsdiag (1.7.0-1.1) unstable; urgency=medium . * Non-maintainer upload. * Add upstream fix for runtime warning with dnspython 2. (Closes: #995015) * Build depend on python3, not python3-all. Checksums-Sha1: bd62939c741af989fcc28f77ef422fa022d66506 1958 dnsdiag_1.7.0-1.1.dsc 48048ec1edd2b141e405c1467fa2e45671ce36c2 5576 dnsdiag_1.7.0-1.1.debian.tar.xz Checksums-Sha256: 6ce8bd69fdba0c8e49b97a3816f4fec5660f4c892ba22b590c9fe4f84455e6ea 1958 dnsdiag_1.7.0-1.1.dsc af97465d46bacea0c3d18875d961cc8b5e74e239bb1061f3c5a3209e87c0ccb1 5576 dnsdiag_1.7.0-1.1.debian.tar.xz Files: 5d1c08c7e94caf9765dffcbf10f5bf69 1958 net optional dnsdiag_1.7.0-1.1.dsc 9f4c127dde4b2b64779ffb628d222b0c 5576 net optional dnsdiag_1.7.0-1.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmGdFDgACgkQiNJCh6LY mLEMFw//SnALaRZak5Hz6Ktp7YSalD7u2CX9VAAfece9DjaAEJLKwcbPH2Cvxeoa glNXaXA+WAEkkMeIePlOgdwqQIjKq8b1bBZwcTw0NLZMBoHLEyVwiC1VLr0vankR fI5YWe4wd8/Pnf09i7kcTGH1qGm7BomnTZ61hJSoMRMB2TaJTgLCRjXYaCnBsaoe PlrisxY6ozQrK02kTmmUPEYBB6VaplqDIOY12+wy2Qps3X+fW+DZ8kOzFFvj3df+ Uxyzrn+xfYP9vxsHdx0nqqV3oeHlw4b4SITEllTn5oWsHxeIlA4kd7WGzBIXzV39 9MYK8mYurLECrYf168bEjOGBf8wPv9ywy/T6LwfN4OzE9bKIGNRhh59ZhPrEY+/g l+LifPIhTJbtlUPr4+msBsn/MbTg+GHg5WfNaP7ETxvCbxvVpJzkTm+Zcs+m0PDS bEv/kzJdIwddOcLxSMCvvn+Cd3iPKNmJ/Hin/6OWYJz10s6Fe8kmlwHAIAKC51Pq 8RYmQxcDZ9T/eKzfGyLOfbw2frjLZPo1VULMzEEbEXxYYkGYhdbXQkytHgRPvAuS
Bug#995016: marked as done (dnsdiag: Error when running: DeprecationWarning)
Your message dated Tue, 23 Nov 2021 16:48:49 + with message-id and subject line Bug#995015: fixed in dnsdiag 1.7.0-1.1 has caused the Debian Bug report #995015, regarding dnsdiag: Error when running: DeprecationWarning 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.) -- 995015: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995015 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: dnsdiag Version: 1.7.0-1 Severity: grave Justification: renders package unusable When running dnseval, it gives the following error: abrantes@FLS12STI-D006:~$ dnseval -f /tmp/dns -c 1000 web.whatsapp.com server avg(ms) min(ms) max(ms) stddev(ms) lost(%) ttl flags --- /bin/dnseval:176: DeprecationWarning: please use dns.resolver.Resolver.resolve() instead answers = resolver.query(fqdn, dnsrecord, tcp=use_tcp, 221.182.100.10 1.124 0.613 7.534 0.410 %0 3242 QR -- -- RD RA -- -- abrantes@FLS12STI-D006:~$ cat /tmp/dns 8.8.8.8 abrantes@FLS12STI-D006:~$ Any other DNS also occurs. I noticed that on Debian 10, it works normally. On Debian 11 and 12 the same error occurs. Regards -- System Information: Debian Release: 11.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-8-amd64 (SMP w/2 CPU threads) Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), LANGUAGE=pt_BR:pt:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages dnsdiag depends on: ii python3 3.9.2-3 ii python3-cymruwhois 1.6-3.2 ii python3-dnspython 2.0.0-1 dnsdiag recommends no packages. dnsdiag suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: dnsdiag Source-Version: 1.7.0-1.1 Done: Adrian Bunk We believe that the bug you reported is fixed in the latest version of dnsdiag, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 995...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Adrian Bunk (supplier of updated dnsdiag package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 23 Nov 2021 17:49:52 +0200 Source: dnsdiag Architecture: source Version: 1.7.0-1.1 Distribution: unstable Urgency: medium Maintainer: Ana Custura Changed-By: Adrian Bunk Closes: 995015 Changes: dnsdiag (1.7.0-1.1) unstable; urgency=medium . * Non-maintainer upload. * Add upstream fix for runtime warning with dnspython 2. (Closes: #995015) * Build depend on python3, not python3-all. Checksums-Sha1: bd62939c741af989fcc28f77ef422fa022d66506 1958 dnsdiag_1.7.0-1.1.dsc 48048ec1edd2b141e405c1467fa2e45671ce36c2 5576 dnsdiag_1.7.0-1.1.debian.tar.xz Checksums-Sha256: 6ce8bd69fdba0c8e49b97a3816f4fec5660f4c892ba22b590c9fe4f84455e6ea 1958 dnsdiag_1.7.0-1.1.dsc af97465d46bacea0c3d18875d961cc8b5e74e239bb1061f3c5a3209e87c0ccb1 5576 dnsdiag_1.7.0-1.1.debian.tar.xz Files: 5d1c08c7e94caf9765dffcbf10f5bf69 1958 net optional dnsdiag_1.7.0-1.1.dsc 9f4c127dde4b2b64779ffb628d222b0c 5576 net optional dnsdiag_1.7.0-1.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmGdFDgACgkQiNJCh6LY mLEMFw//SnALaRZak5Hz6Ktp7YSalD7u2CX9VAAfece9DjaAEJLKwcbPH2Cvxeoa glNXaXA+WAEkkMeIePlOgdwqQIjKq8b1bBZwcTw0NLZMBoHLEyVwiC1VLr0vankR fI5YWe4wd8/Pnf09i7kcTGH1qGm7BomnTZ61hJSoMRMB2TaJTgLCRjXYaCnBsaoe PlrisxY6ozQrK02kTmmUPEYBB6VaplqDIOY12+wy2Qps3X+fW+DZ8kOzFFvj3df+ Uxyzrn+xfYP9vxsHdx0nqqV3oeHlw4b4SITEllTn5oWsHxeIlA4kd7WGzBIXzV39 9MYK8mYurLECrYf168bEjOGBf8wPv9ywy/T6LwfN4OzE9bKIGNRhh59ZhPrEY+/g l+LifPIhTJbtlUPr4+msBsn/MbTg+GHg5WfNaP7ETxvCbxvVpJzkTm+Zcs+m0PDS bEv/kzJdIwddOcLxSMCvvn+Cd3iPKNmJ/Hin/6OWYJz10s6Fe8kmlwHAIAKC51Pq 8RYmQxcDZ9T/eKzfGyLOfbw2frjLZPo1VULMzEEbEXxYYkGYhdbXQkytHgRPvAuS +8ggGOV2c580LYF1YVfWAJxYSbD63GjxsjthFOWzsmeT6hBNXc3VBsdlpjaWP6t4 2hmVm6d/ztOLwus1az/DvWX5A7qaJNpqfcZKEx3jegnLMMOBK/4= =c6WE -END PGP
Processed: bug 997488 is forwarded to https://github.com/qiime2/q2cli/issues/259
Processing commands for cont...@bugs.debian.org:
> forwarded 997488 https://github.com/qiime2/q2cli/issues/259
Bug #997488 [src:q2cli] q2cli: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p 3.9 returned exit code 13
Ignoring request to change the forwarded-to-address of bug#997488 to the same
value
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
997488: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997488
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#995015: dnsdiag: diff for NMU version 1.7.0-1.1
Dear Adrian, Thank you for the upload, this is appreciated as I don't have much time atm. Ana On 23/11/2021 16:19, Adrian Bunk wrote: Control: tags 995015 + patch Control: tags 995015 + pending Dear maintainer, I've prepared an NMU for dnsdiag (versioned as 1.7.0-1.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should cancel it. cu Adrian
Bug#1000365: pre-rebuild?
I _think_ this would expected with 22.3.0-1 and python 3.10, since that package was built only for python 3.9. Can you reproduce this with 22.3.0-1+b1 now the python 3.10 binNMUs have (mostly) happened? I can certainly import `zmq` in python3.10 without immediate errors.
Processed: dnsdiag: diff for NMU version 1.7.0-1.1
Processing control commands: > tags 995015 + patch Bug #995015 [dnsdiag] dnsdiag: Error when running: DeprecationWarning Bug #995016 [dnsdiag] dnsdiag: Error when running: DeprecationWarning Added tag(s) patch. Added tag(s) patch. > tags 995015 + pending Bug #995015 [dnsdiag] dnsdiag: Error when running: DeprecationWarning Bug #995016 [dnsdiag] dnsdiag: Error when running: DeprecationWarning Added tag(s) pending. Added tag(s) pending. -- 995015: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995015 995016: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995016 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#995015: dnsdiag: diff for NMU version 1.7.0-1.1
Control: tags 995015 + patch
Control: tags 995015 + pending
Dear maintainer,
I've prepared an NMU for dnsdiag (versioned as 1.7.0-1.1) and uploaded
it to DELAYED/2. Please feel free to tell me if I should cancel it.
cu
Adrian
diff -Nru dnsdiag-1.7.0/debian/changelog dnsdiag-1.7.0/debian/changelog
--- dnsdiag-1.7.0/debian/changelog 2020-02-08 20:16:44.0 +0200
+++ dnsdiag-1.7.0/debian/changelog 2021-11-23 17:49:52.0 +0200
@@ -1,3 +1,12 @@
+dnsdiag (1.7.0-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Add upstream fix for runtime warning with dnspython 2.
+(Closes: #995015)
+ * Build depend on python3, not python3-all.
+
+ -- Adrian Bunk Tue, 23 Nov 2021 17:49:52 +0200
+
dnsdiag (1.7.0-1) unstable; urgency=medium
[ Ondřej Nový ]
diff -Nru dnsdiag-1.7.0/debian/control dnsdiag-1.7.0/debian/control
--- dnsdiag-1.7.0/debian/control 2020-02-08 20:16:44.0 +0200
+++ dnsdiag-1.7.0/debian/control 2021-11-23 17:49:52.0 +0200
@@ -3,7 +3,7 @@
Priority: optional
Maintainer: Ana Custura
Uploaders: Debian Python Modules Team
-Build-Depends: debhelper-compat (= 11), dh-python, python3-all, python3-setuptools, dh-exec
+Build-Depends: debhelper-compat (= 11), dh-python, python3, python3-setuptools, dh-exec
Standards-Version: 4.4.1
Homepage: https://dnsdiag.org/
Vcs-Git: https://salsa.debian.org/python-team/modules/dnsdiag.git
diff -Nru dnsdiag-1.7.0/debian/patches/0001-Adapt-new-dnspython-v2.0.0.patch dnsdiag-1.7.0/debian/patches/0001-Adapt-new-dnspython-v2.0.0.patch
--- dnsdiag-1.7.0/debian/patches/0001-Adapt-new-dnspython-v2.0.0.patch 1970-01-01 02:00:00.0 +0200
+++ dnsdiag-1.7.0/debian/patches/0001-Adapt-new-dnspython-v2.0.0.patch 2021-11-23 17:48:29.0 +0200
@@ -0,0 +1,82 @@
+From 3d9eb79e0037837586be5e3d01ffecbe3c442065 Mon Sep 17 00:00:00 2001
+From: Babak Farrokhi
+Date: Thu, 20 Aug 2020 23:47:11 +0200
+Subject: Adapt new dnspython v2.0.0
+
+- Adapt new resolve() function (Fixes #67)
+- Update dependency to newer dnspython
+---
+ dnseval.py | 4 ++--
+ dnsping.py | 4 ++--
+ dnstraceroute.py | 2 +-
+ requirements.txt | 2 +-
+ setup.py | 2 +-
+ 5 files changed, 7 insertions(+), 7 deletions(-)
+
+diff --git a/dnseval.py b/dnseval.py
+index d3d0afb..63820c6 100755
+--- a/dnseval.py
b/dnseval.py
+@@ -172,8 +172,8 @@ def dnsping(host, server, dnsrecord, timeout, count, use_tcp=False, use_edns=Fal
+ fqdn = host
+
+ stime = time.perf_counter()
+-answers = resolver.query(fqdn, dnsrecord, tcp=use_tcp,
+- raise_on_no_answer=False) # todo: response validation in future
++answers = resolver.resolve(fqdn, dnsrecord, tcp=use_tcp,
++ raise_on_no_answer=False) # todo: response validation in future
+
+ except (dns.resolver.NoNameservers, dns.resolver.NoAnswer):
+ break
+diff --git a/dnsping.py b/dnsping.py
+index 6845cdb..a243ab5 100755
+--- a/dnsping.py
b/dnsping.py
+@@ -186,8 +186,8 @@ def main():
+
+ try:
+ stime = time.perf_counter()
+-answers = resolver.query(hostname, dnsrecord, source_port=src_port, source=src_ip, tcp=use_tcp,
+- raise_on_no_answer=False)
++answers = resolver.resolve(hostname, dnsrecord, source_port=src_port, source=src_ip, tcp=use_tcp,
++ raise_on_no_answer=False)
+ etime = time.perf_counter()
+ except dns.resolver.NoNameservers as e:
+ if not quiet:
+diff --git a/dnstraceroute.py b/dnstraceroute.py
+index 8a58e40..44a4770 100755
+--- a/dnstraceroute.py
b/dnstraceroute.py
+@@ -194,7 +194,7 @@ def ping(resolver, hostname, dnsrecord, ttl, src_ip, use_edns=False):
+ resolver.use_edns(edns=0, payload=8192, ednsflags=dns.flags.edns_from_text('DO'))
+
+ try:
+-resolver.query(hostname, dnsrecord, source=src_ip, raise_on_no_answer=False)
++resolver.resolve(hostname, dnsrecord, source=src_ip, raise_on_no_answer=False)
+
+ except dns.resolver.NoNameservers as e:
+ if not quiet:
+diff --git a/requirements.txt b/requirements.txt
+index 7fe56ca..f1238bd 100644
+--- a/requirements.txt
b/requirements.txt
+@@ -1,2 +1,2 @@
+-dnspython>=1.16.0
++dnspython>=2.0.0
+ cymruwhois>=1.6
+diff --git a/setup.py b/setup.py
+index 39233d2..2db02ca 100644
+--- a/setup.py
b/setup.py
+@@ -5,7 +5,7 @@ setup(
+ version="1.7.0",
+ packages=find_packages(),
+ scripts=["dnseval.py", "dnsping.py", "dnstraceroute.py"],
+-install_requires=['dnspython>=1.16.0', 'cymruwhois>=1.6'],
++install_requires=['dnspython>=2.0.0', 'cymruwhois>=1.6'],
+
+ classifiers=[
+ "Topic :: System :: Networking",
+--
+2.20.1
+
diff -Nru dnsdiag-1.7.0/debian/patches/series dnsdiag-1.7.0/debian/patches/series
--- dnsdiag-1.7.0/debian/patches/series 2020-02-08
Bug#1000460: tf does not trap errors from make
Source: tf Version: 1:4.0s1-21 Severity: serious Justification: policy 4.6 When building tf fails, the failure is not propagated and debian/rules proceeds with dh_auto_install after a failed dh_auto_build. Such behaviour violates policy section 4.6 and thus this issue deserves rc-severity. At least one cause is unix/Makefile line 25. https://sources.debian.org/src/tf/1:4.0s1-21/unix/Makefile/#L25 There, the result of the sub-make is ignored. Helmut
Processed: notfixed 1000427 in 2.1.1-1
Processing commands for cont...@bugs.debian.org:
> notfixed 1000427 2.1.1-1
Bug #1000427 {Done: Stefano Rivera } [src:pyregion]
pyregion: FTBFS with setuptools >= 58
No longer marked as fixed in versions 2.1.1-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1000427: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000427
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#984270: marked as done (onednn: ftbfs with GCC-11)
Your message dated Tue, 23 Nov 2021 15:49:04 + with message-id and subject line Bug#984270: fixed in onednn 2.2.2+ds-3 has caused the Debian Bug report #984270, regarding onednn: 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.) -- 984270: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984270 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:onednn Version: 2.0+ds-2 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://people.debian.org/~doko/logs/20210228/filtered/gcc11/onednn_2.0+ds-2_unstable_gcc11.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] 389 | default:return std::[01;31m[Knumeric_limits[m[K::max(); | [01;31m[K^~[m[K [01m[K../src/gpu/jit/ngen/ngen_auto_swsb.hpp:389:52:[m[K [01;31m[Kerror: [m[Kexpected primary-expression before ‘[01m[Kint[m[K’ 389 | default:return std::numeric_limits<[01;31m[Kint[m[K>::max(); |[01;31m[K^~~[m[K [01m[K../src/gpu/jit/ngen/ngen_auto_swsb.hpp:389:52:[m[K [01;31m[Kerror: [m[Kexpected ‘[01m[K;[m[K’ before ‘[01m[Kint[m[K’ 389 | default:return std::numeric_limits<[01;31m[Ki[m[K[32m[Knt[m[K>::max(); | [01;31m[K^[m[K[32m[K~~[m[K |[32m[K;[m[K [01m[K../src/gpu/jit/ngen/ngen_auto_swsb.hpp:389:55:[m[K [01;31m[Kerror: [m[Kexpected unqualified-id before ‘[01m[K>[m[K’ token 389 | default:return std::numeric_limits[m[K::max(); | [01;31m[K^[m[K [01m[K../src/gpu/jit/ngen/ngen_auto_swsb.hpp:[m[K In function ‘[01m[Kuint8_t ngen::autoswsb::chooseSBID(ngen::HW, Program&, int32_t, int32_t, const ngen::autoswsb::DependencyTable&, const ngen::autoswsb::DependencyTable&, uint32_t)[m[K’: [01m[K../src/gpu/jit/ngen/ngen_auto_swsb.hpp:1000:39:[m[K [01;31m[Kerror: [m[K‘[01m[Knumeric_limits[m[K’ is not a member of ‘[01m[Kstd[m[K’ 1000 | constexpr int32_t infinite = std::[01;31m[Knumeric_limits[m[K::max(); | [01;31m[K^~[m[K [01m[K../src/gpu/jit/ngen/ngen_auto_swsb.hpp:1000:61:[m[K [01;31m[Kerror: [m[Kexpected primary-expression before ‘[01m[K>[m[K’ token 1000 | constexpr int32_t infinite = std::numeric_limits[m[K::max(); | [01;31m[K^[m[K [01m[K../src/gpu/jit/ngen/ngen_auto_swsb.hpp:1000:64:[m[K [01;31m[Kerror: [m[K‘[01m[K::max[m[K’ has not been declared; did you mean ‘[01m[Kstd::max[m[K’? 1000 | constexpr int32_t infinite = std::numeric_limits::[01;31m[Kmax[m[K(); | [01;31m[K^~~[m[K | [32m[Kstd::max[m[K In file included from [01m[K/usr/include/c++/11/algorithm:62[m[K,
Processed: notfound 1000427 in pyregion/2.1.1-1
Processing commands for cont...@bugs.debian.org:
> notfound 1000427 pyregion/2.1.1-1
Bug #1000427 {Done: Stefano Rivera } [src:pyregion]
pyregion: FTBFS with setuptools >= 58
No longer marked as found in versions pyregion/2.1.1-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1000427: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000427
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1000427: marked as done (pyregion: FTBFS with setuptools >= 58)
Your message dated Tue, 23 Nov 2021 11:37:42 -0400
with message-id <20211123153742.orlfycl7pid2y...@haydn.kardiogramm.net>
and subject line Re: Bug#1000427: pyregion: FTBFS with setuptools >= 58
has caused the Debian Bug report #1000427,
regarding pyregion: FTBFS with setuptools >= 58
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.)
--
1000427: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000427
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pyregion
Version: 2.1.1-1
Severity: serious
Tags: upstream
Justification: FTBFS
pyregion fails to build with setuptools >= 58, which dropped use_2to3
support.:
/usr/lib/python3/dist-packages/setuptools/dist.py:294: DistDeprecationWarning:
use_2to3 is ignored.
warnings.warn(f"{attr} is ignored.", DistDeprecationWarning)
See the full log:
https://buildd.debian.org/status/fetch.php?pkg=pyregion=amd64=2.1.1-1%2Bb1=1637589214=0
SR
--- End Message ---
--- Begin Message ---
Version: 2.1.1-1
Whoops, I misread the build log, it's fine.
SR
--
Stefano Rivera
http://tumbleweed.org.za/
+1 415 683 3272--- End Message ---
Bug#997627: pixmap: FTBFS: ar: libdeps specified more than once
On Sat 23 Oct 2021, Lucas Nussbaum wrote: > Source: pixmap > Version: 2.6pl4-20 > Severity: serious > Justification: FTBFS > Tags: bookworm sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20211023 ftbfs-bookworm > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. > > rm -f libXgnu.a > > ar clq libXgnu.a SelFile.o Path.o Dir.o Draw.o > > ar: libdeps specified more than once > > make[2]: *** [Makefile:1062: libXgnu.a] Error 1 This seems related to #981072 binutils: 'ar clq' does not longer work in latest binutils. With binutils 2.35.2 it works. I suspect that this will affect all packages that use Imake, see also #997628 and #994276. Not that much that I can do about it until xutils-dev gets patched. (Besides patching the output of Imake which is just papering over the binutils screwup.) Paul
Bug#1000457: virtualbox: Outdated dependency on libgsoap-2.8.104
Package: virtualbox Version: 6.1.28-dfsg-1 Severity: grave Justification: renders package unusable Dear Maintainer, Trying to upgrade virtualbox to Version: 6.1.28-dfsg-1 aptitude was not able to resolve dependencies. I uninstalled the previous version and then tryed to install again, but foud that virtualbox depends on libgsoap-2.8.104, that is not available in unstable. Proposed solution: depend on libgsoap-2.8.117 Thank you for maintaining the package. *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing'), (100, 'bullseye-fasttrack'), (100, 'bullseye-backports-staging') Architecture: amd64 (x86_64) Kernel: Linux 5.14.0-4-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=it_IT:it Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages virtualbox depends on: ii adduser 3.118 ii iproute2 5.15.0-1 ii libc6 2.32-4 ii libcurl3-gnutls 7.79.1-2 ii libdevmapper1.02.12:1.02.175-2.1 ii libgcc-s1 11.2.0-10 ii libgl11.3.4-2+b1 pn libgsoap-2.8.104 ii liblzf1 3.6-3 ii libopus0 1.3.1-0.1 ii libpng16-16 1.6.37-3 ii libpython3.9 3.9.9-1 ii libsdl1.2debian 1.2.15+dfsg2-6 ii libssl1.1 1.1.1l-1 ii libstdc++611.2.0-10 ii libvncserver1 0.9.13+dfsg-3 ii libvpx6 1.10.0-2 ii libx11-6 2:1.7.2-2+b1 ii libxcursor1 1:1.2.0-2 ii libxml2 2.9.12+dfsg-5+b1 ii libxt61:1.2.0-1 ii procps2:3.3.17-5 ii python3 3.9.7-1 ii python3.9 3.9.9-1 ii virtualbox-dkms [virtualbox-modules] 6.1.28-dfsg-1~fto11+1 ii zlib1g1:1.2.11.dfsg-2 Versions of packages virtualbox recommends: ii libqt5core5a5.15.2+dfsg-13 ii libqt5gui5 5.15.2+dfsg-13 ii libqt5opengl5 5.15.2+dfsg-13 ii libqt5widgets5 5.15.2+dfsg-13 ii libxcb1 1.14-3 ii libxext62:1.3.4-1 pn virtualbox-qt Versions of packages virtualbox suggests: pn vde2 pn virtualbox-guest-additions-iso
Processed (with 1 error): pymatgen
Processing commands for cont...@bugs.debian.org: > forwarded 1000419 https://github.com/materialsproject/pymatgen/issues/2305 Bug #1000419 [src:pymatgen] pymatgen: FTBFS - Test failure: BSPlotterProjectedTest.test_methods Set Bug forwarded-to-address to 'https://github.com/materialsproject/pymatgen/issues/2305'. > . Unknown command or malformed arguments to command. > End of message, stopping processing here. Please contact me if you need assistance. -- 1000419: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000419 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: debomatic: FTBFS: '! LaTeX Error: File `tgtermes.sty' not found.'
Processing control commands: > tag -1 patch Bug #997414 [src:debomatic] debomatic: FTBFS: '! LaTeX Error: File `tgtermes.sty' not found.' Added tag(s) patch. -- 997414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997414 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997414: debomatic: FTBFS: '! LaTeX Error: File `tgtermes.sty' not found.'
Package: debomatic Followup-For: Bug #997414 Control: tag -1 patch Hello. This issue is fixed by tex-gyre in Build-Depends.
Bug#997718: marked as done (glewlwyd: FTBFS: Module not found: Error: Can't resolve 'cross-fetch' in '/<>/webapp-src/node_modules/i18next-http-backend/cjs')
Your message dated Tue, 23 Nov 2021 13:03:40 +
with message-id
and subject line Bug#997718: fixed in node-i18next-http-backend 1.3.1+dfsg-3
has caused the Debian Bug report #997718,
regarding glewlwyd: FTBFS: Module not found: Error: Can't resolve 'cross-fetch'
in '/<>/webapp-src/node_modules/i18next-http-backend/cjs'
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.)
--
997718: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997718
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: glewlwyd
Version: 2.5.2-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 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 '/<>'
> # Build webapp
> cp -RL /usr/share/nodejs webapp-src/node_modules || true
> cp -RL /usr/lib/nodejs/* webapp-src/node_modules/ || true
> (cd webapp-src && webpack --config webpack.config.js)
> Hash: a8dcd07a19fb3af83c81
> Version: webpack 4.43.0
> Time: 29020ms
> Built at: 10/23/2021 7:31:30 AM
> 6 assets
> Entrypoint admin = vendors~admin~callback~login~profile.js admin.js
> Entrypoint login = vendors~admin~callback~login~profile.js login.js
> Entrypoint profile = vendors~admin~callback~login~profile.js
> vendors~profile.js profile.js
> Entrypoint callback = vendors~admin~callback~login~profile.js callback.js
> [1] ./node_modules/i18next/dist/esm/i18next.js + 13 modules 98.8 KiB {0}
> [built]
> |14 modules
> [2] ./src/lib/MessageDispatcher.js 1.67 KiB {1} {2} {3} {4} [built]
> [3] ./src/lib/APIManager.js 3.08 KiB {1} {2} {3} {4} [built]
> [4] ./src/lib/Notification.js 7.63 KiB {1} {3} {4} [built]
> [8] ./src/lib/ErrorConfig.js 3.51 KiB {1} {2} {3} {4} [built]
> [9] ./src/Modal/Message.js 5.76 KiB {1} {3} {4} [built]
> [12] (webpack)/buildin/global.js 472 bytes {1} {2} {3} {4} [built]
> [13] ./src/Modal/Confirm.js 5.57 KiB {1} {4} [built]
> [23] ./src/admin.js + 30 modules 1010 KiB {1} [built]
> | ./src/admin.js 2.11 KiB [built]
> | ./src/Admin/App.js 87.2 KiB [built]
> | ./src/Modal/EditRecord.js 48.6 KiB [built]
> | ./src/Admin/Navbar.js 19.6 KiB [built]
> | ./src/Admin/Users.js 18.1 KiB [built]
> | ./src/Admin/Clients.js 15.4 KiB [built]
> | ./src/Admin/Scopes.js 14.6 KiB [built]
> | ./src/Admin/UserMod.js 14.3 KiB [built]
> | ./src/Admin/ClientMod.js 14.4 KiB [built]
> | ./src/Admin/SchemeMod.js 12.5 KiB [built]
> | ./src/Admin/Plugin.js 12.5 KiB [built]
> | ./src/Admin/ScopeEdit.js 22.1 KiB [built]
> | ./src/Admin/ModEdit.js 21.8 KiB [built]
> | ./src/Admin/PluginEdit.js 14.8 KiB [built]
> | ./src/Admin/APIKey.js 14.7 KiB [built]
> | + 16 hidden modules
> [24] ./src/login.js + 20 modules 205 KiB {3} [built]
> | ./src/login.js 2.6 KiB [built]
> | ./src/Login/App.js 30.1 KiB [built]
> | ./src/Login/Buttons.js 19 KiB [built]
> | ./src/Login/Body.js 7.62 KiB [built]
> | ./src/Login/PasswordForm.js 8.47 KiB [built]
> | ./src/Login/NoPasswordForm.js 10.9 KiB [built]
> | ./src/Login/SelectAccount.js 10.8 KiB [built]
> | ./src/Login/EndSession.js 6.32 KiB [built]
> | ./src/Login/SessionClosed.js 4.63 KiB [built]
> | ./src/Login/DeviceAuth.js 8.84 KiB [built]
> | ./src/Login/ResetCredentials.js 10.6 KiB [built]
> | ./src/Login/GrantScope.js 16.7 KiB [built]
> | ./src/Login/scheme/MockSchemeForm.js 9.97 KiB [built]
> | ./src/Login/scheme/EmailSchemeForm.js 8.28 KiB [built]
> | ./src/Login/scheme/WebauthnForm.js 10.1 KiB [built]
> | + 6 hidden modules
> [25] ./src/profile.js + 15 modules 290 KiB {4} [built]
> | ./src/profile.js 2.77 KiB [built]
> | ./src/Profile/App.js 34.4 KiB [built]
> | ./src/Profile/Navbar.js 20.9 KiB [built]
> | ./src/Profile/User.js 31.3 KiB [built]
> | ./src/Profile/UserDelegate.js 4.03 KiB [built]
> | ./src/Profile/UserResetCredentials.js 11.6 KiB [built]
> | ./src/Profile/Register.js 40.5 KiB [built]
> | ./src/Profile/Session.js 18.2 KiB [built]
> | ./src/Profile/Password.js 25.8 KiB [built]
> | ./src/Profile/SchemePage.js 5.86 KiB [built]
> | ./src/Modal/Edit.js 6.42 KiB [built]
> | ./src/Profile/SchemeMock.js 7.72 KiB [built]
> | ./src/Profile/SchemeWebauthn.js 28.6 KiB [built]
> | ./src/Profile/SchemeOTP.js 18.7 KiB [built]
> | ./src/Profile/SchemeCertificate.js 22.2 KiB [built]
> | + 1 hidden module
> [26]
Processed: Bug#1000210 marked as pending in devscripts
Processing control commands: > tag -1 pending Bug #1000210 [devscripts] [regression] uscan die: filenamemangle failed Bug #999543 [devscripts] devscripts: uscan crash with cmus package Added tag(s) pending. Added tag(s) pending. -- 1000210: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000210 999543: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999543 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000210: marked as pending in devscripts
Control: tag -1 pending Hello, Bug #1000210 in devscripts reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/debian/devscripts/-/commit/8246ebbe2b4aac700b8a5e4358e4152e71979737 Revert "uscan: Assign $newfile_base a filename, not a URL, when filenamemangling" This reverts commit 9e65c07737425748e396291d9c20442d11b0641b. Closes: #1000210 Signed-off-by: Mattia Rizzolo (this message was generated automatically) -- Greetings https://bugs.debian.org/1000210
Bug#999534: marked as done (python-bayespy: FTBFS with matplotlib 3.5 (in experimental): dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13)
Your message dated Tue, 23 Nov 2021 12:03:45 +
with message-id
and subject line Bug#999534: fixed in python-bayespy 0.5.22-1
has caused the Debian Bug report #999534,
regarding python-bayespy: FTBFS with matplotlib 3.5 (in experimental):
dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9
returned exit code 13
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.)
--
999534: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999534
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-bayespy
Version: 0.5.18-3
Severity: important
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-matplotlib35
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64, using matplotlib 3.5 currently in experimental. This version
will soon be uploaded to unstable.
If you have questions about this, please contact Sandro Tosi
.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> xvfb-run -a dh_auto_test
> I: pybuild base:232: cd /<>/.pybuild/cpython3_3.9_bayespy/build;
> python3.9 -m pytest
> = test session starts
> ==
> platform linux -- Python 3.9.7, pytest-6.2.5, py-1.10.0, pluggy-0.13.0
> rootdir: /<>
> collected 124 items / 1 error / 123 selected
>
> ERRORS
>
> _ ERROR collecting
> .pybuild/cpython3_3.9_bayespy/build/bayespy/tests/test_plot.py _
> ImportError while importing test module
> '/<>/.pybuild/cpython3_3.9_bayespy/build/bayespy/tests/test_plot.py'.
> Hint: make sure your test modules/packages have valid Python names.
> Traceback:
> /usr/lib/python3.9/importlib/__init__.py:127: in import_module
> return _bootstrap._gcd_import(name[level:], package, level)
> bayespy/tests/__init__.py:8: in
> import bayespy.plot as bpplt
> bayespy/plot.py:60: in
> import matplotlib.pyplot as plt
> /usr/lib/python3/dist-packages/matplotlib/pyplot.py:2226: in
> switch_backend(rcParams["backend"])
> /usr/lib/python3/dist-packages/matplotlib/pyplot.py:267: in switch_backend
> class backend_mod(matplotlib.backend_bases._Backend):
> /usr/lib/python3/dist-packages/matplotlib/pyplot.py:268: in backend_mod
> locals().update(vars(importlib.import_module(backend_name)))
> /usr/lib/python3.9/importlib/__init__.py:127: in import_module
> return _bootstrap._gcd_import(name[level:], package, level)
> /usr/lib/python3/dist-packages/matplotlib/backends/backend_tkagg.py:1: in
>
> from . import _backend_tk
> /usr/lib/python3/dist-packages/matplotlib/backends/_backend_tk.py:14: in
>
> from PIL import Image, ImageTk
> E ImportError: cannot import name 'ImageTk' from 'PIL'
> (/usr/lib/python3/dist-packages/PIL/__init__.py)
> === warnings summary
> ===
> bayespy/utils/misc.py:272
>
> /<>/.pybuild/cpython3_3.9_bayespy/build/bayespy/utils/misc.py:272:
> DeprecationWarning: invalid escape sequence \c
> """
>
> bayespy/inference/vmp/nodes/binomial.py:102
>
> /<>/.pybuild/cpython3_3.9_bayespy/build/bayespy/inference/vmp/nodes/binomial.py:102:
> DeprecationWarning: invalid escape sequence \p
> """
>
> bayespy/inference/vmp/nodes/binomial.py:111
>
> /<>/.pybuild/cpython3_3.9_bayespy/build/bayespy/inference/vmp/nodes/binomial.py:111:
> DeprecationWarning: invalid escape sequence \m
> """
>
> bayespy/inference/vmp/nodes/beta.py:74
>
> /<>/.pybuild/cpython3_3.9_bayespy/build/bayespy/inference/vmp/nodes/beta.py:74:
> DeprecationWarning: invalid escape sequence \p
> """
>
> bayespy/inference/vmp/nodes/beta.py:81
>
> /<>/.pybuild/cpython3_3.9_bayespy/build/bayespy/inference/vmp/nodes/beta.py:81:
> DeprecationWarning: invalid escape sequence \m
> """
>
> bayespy/inference/vmp/nodes/poisson.py:84
>
> /<>/.pybuild/cpython3_3.9_bayespy/build/bayespy/inference/vmp/nodes/poisson.py:84:
> DeprecationWarning: invalid escape sequence \p
> """
>
> bayespy/inference/vmp/nodes/poisson.py:94
>
> /<>/.pybuild/cpython3_3.9_bayespy/build/bayespy/inference/vmp/nodes/poisson.py:94:
> DeprecationWarning: invalid escape sequence \m
> """
>
> bayespy/inference/vmp/nodes/poisson.py:132
>
> /<>/.pybuild/cpython3_3.9_bayespy/build/bayespy/inference/vmp/nodes/poisson.py:132:
> DeprecationWarning: invalid escape sequence \m
> """
>
> bayespy/inference/vmp/nodes/wishart.py:119
>
>
Processed: tagging 1000417
Processing commands for cont...@bugs.debian.org: > tags 1000417 + pending Bug #1000417 [src:devscripts] devscripts: autopkgtest regression: zstd: not found Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1000417: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000417 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000357: Module build is still failing
The module is still failing to build on my machine. I believe the problem is that ddcci_device_remove() returns in two different places. The new patch wraps the return at the end of the function in an #if, but does not fix the mid-function `return -EINVAL;`. (In case it is useful: there is a patch on the Ubuntu version of this bug that uses a wrapper function instead of conditional compilation within the function: https://bugs.launchpad.net/ubuntu/+source/ddcci-driver-linux/+bug/1951608 .) Here's my make.log from today: DKMS make.log for ddcci-0.4.1 for kernel 5.15.0-1-amd64 (x86_64) Tue 23 Nov 11:25:56 GMT 2021 make: Entering directory '/var/lib/dkms/ddcci/0.4.1/build' make -C "ddcci" make[1]: Entering directory '/var/lib/dkms/ddcci/0.4.1/build/ddcci' make -C "/lib/modules/5.15.0-1-amd64/build" M="/var/lib/dkms/ddcci/0.4.1/build/ddcci" modules make[2]: Entering directory '/usr/src/linux-headers-5.15.0-1-amd64' CC [M] /var/lib/dkms/ddcci/0.4.1/build/ddcci/ddcci.o /var/lib/dkms/ddcci/0.4.1/build/ddcci/ddcci.c: In function ‘ddcci_device_remove’: /var/lib/dkms/ddcci/0.4.1/build/ddcci/ddcci.c:1283:24: error: ‘return’ with a value, in function returning void [-Werror=return-type] 1283 | return -EINVAL; |^ /var/lib/dkms/ddcci/0.4.1/build/ddcci/ddcci.c:1273:13: note: declared here 1273 | static void ddcci_device_remove(struct device *dev) | ^~~ cc1: some warnings being treated as errors make[3]: *** [/usr/src/linux-headers-5.15.0-1-common/scripts/Makefile.build:282: /var/lib/dkms/ddcci/0.4.1/build/ddcci/ddcci.o] Error 1 make[2]: *** [/usr/src/linux-headers-5.15.0-1-common/Makefile:1892: /var/lib/dkms/ddcci/0.4.1/build/ddcci] Error 2 make[2]: Leaving directory '/usr/src/linux-headers-5.15.0-1-amd64' make[1]: *** [Makefile:38: ddcci.ko] Error 2 make[1]: Leaving directory '/var/lib/dkms/ddcci/0.4.1/build/ddcci' make: *** [Makefile:28: ddcci] Error 2 make: Leaving directory '/var/lib/dkms/ddcci/0.4.1/build'
Bug#1000350: marked as done (macaulay2: FTBFS on s390x: i49 : saturate(sing2, sub(irrelTot, ring sing2)) -- SIGSEGV)
Your message dated Tue, 23 Nov 2021 11:33:39 +
with message-id
and subject line Bug#1000350: fixed in macaulay2 1.19+ds-2
has caused the Debian Bug report #1000350,
regarding macaulay2: FTBFS on s390x: i49 : saturate(sing2, sub(irrelTot, ring
sing2)) -- SIGSEGV
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.)
--
1000350: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000350
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: macaulay2
Version: 1.19+ds-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org
| -- making example results for "multiplicity"
-- 0.516413 seconds elapsed
| -- storing example results in
../../../usr-dist/common/share/doc/Macaulay2/ReesAlgebra/example-output/_multiplicity.out
| ../../m2/debugging.m2:23:6:(1):[9]: error: installPackage: 1 error(s)
occurred running examples for package ReesAlgebra:
|
| ___Plane__Curve__Singularities.errors
| *
|
| i48 : time sing2 = ideal singularLocus strictTransform2;
| -- used 0.777859 seconds
|
| ZZ
| o48 : Ideal of -[p ..p , w ..w , x..y]
|32003 0 2 0 1
|
| i49 : saturate(sing2, sub(irrelTot, ring sing2))
| -- SIGSEGV
| -* stack trace, pid: 3693279
| Segmentation fault (core dumped)
|
| ../../m2/installPackage.m2:726:18:(1):[8]: --back trace--
| ../../m2/methods.m2:154:80:(1):[7]: --back trace--
| ../../m2/option.m2:17:8:(1):[6]: --back trace--
| ../../m2/installPackage.m2:604:5:(1):[5]: --back trace--
| ../../m2/methods.m2:154:80:(1):[4]: --back trace--
| ../../m2/option.m2:17:8:(1):[3]: --back trace--
| currentString:1:1:(3):[2]: --back trace--
| Macaulay2/Core/startup.m2.in:561:33:(0):[1]: --back trace--
| Macaulay2/Core/startup.m2.in:661:6:(0): --back trace--
| make[3]: *** [Makefile:94:
/<>/M2/usr-dist/s390x-Linux-Debian-buildd-unstable/lib/s390x-linux-gnu/Macaulay2/ReesAlgebra/.installed]
Error 1
See
https://buildd.debian.org/status/fetch.php?pkg=macaulay2=s390x=1.19%2Bds-1=1637349812=0
Cheers
--
Sebastian Ramacher
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: macaulay2
Source-Version: 1.19+ds-2
Done: Doug Torrance
We believe that the bug you reported is fixed in the latest version of
macaulay2, 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.
Doug Torrance (supplier of updated macaulay2 package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 23 Nov 2021 06:12:52 -0500
Source: macaulay2
Built-For-Profiles: noudeb
Architecture: source
Version: 1.19+ds-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Math Team
Changed-By: Doug Torrance
Closes: 1000348 1000350
Changes:
macaulay2 (1.19+ds-2) unstable; urgency=medium
.
* debian/patches/skip-failing-core-tests.patch
- Skip new failing Core tests:
+ methods; failing on mips64el (Closes: #1000348).
* debian/patches/skip-failing-package-tests
- Skip new failing package tests:
+ check(6, "K3Surfaces"); failing on i386.
+ check({4, 6, 7}, "SpecialFanoFourfolds"); failing on armhf.
+ check(14, "SpecialFanoFourfolds"); sometimes segfaults.
* debian/rules
- Ignore example errors on armel, riscv64, and s390x.
* debian/scripts/Debian.m2
- Cache new failing examples:
+ NoetherianOperators::gCorners; failing on armel.
+ NormalToricVarieties::isNef(ToricDivisor); failing on riscv64.
+ ReesAlgebra::PlaneCurveSingularties; failing on s390x
(Closes: #1000350).
Checksums-Sha1:
5909876267c057c7a313d6d12cb278c0211aa286 2992 macaulay2_1.19+ds-2.dsc
bf68d7c7715a7a23e7f4fcd9ae04c72925bd3ab2 103964
macaulay2_1.19+ds-2.debian.tar.xz
23c2524ebe24094aa5ba45f2b6a71d0958ddc72d 12149
macaulay2_1.19+ds-2_source.buildinfo
Checksums-Sha256:
605a21b88dd89a1c58f1d8afd2060244ab9deeede1c937db1c8b02a93889261e 2992
macaulay2_1.19+ds-2.dsc
Bug#1000348: marked as done (macaulay2: FTBFS on mips64el: assert(timer((m, n) -> apply(m, i -> M(offset,n,1)), (10000,294)) < 1.5) -- timing test)
Your message dated Tue, 23 Nov 2021 11:33:39 +
with message-id
and subject line Bug#1000348: fixed in macaulay2 1.19+ds-2
has caused the Debian Bug report #1000348,
regarding macaulay2: FTBFS on mips64el: assert(timer((m, n) -> apply(m, i ->
M(offset,n,1)), (1,294)) < 1.5) -- timing test
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.)
--
1000348: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000348
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: macaulay2
Version: 1.19+ds-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org
| testing: methods.m2
|
| oo50 : FunctionClosure
|
| ii51 : assert(timer(M, (offset,296,1)) < 0.1) -- recursion test
|
| ii52 : -- WISHLIST: M(0,301,1)
|assert(timer((m, n) -> apply(m, i -> M(offset,n,1)), (1,294)) <
1.5) -- timing test
| Command terminated by signal 9
| 89.71user 0.16system 1:23.64elapsed 107%CPU (0avgtext+0avgdata
125120maxresident)k
| 0inputs+0outputs (0major+6166minor)pagefaults 0swaps
| methods.errors:0: error output left here for the errors above:
| make[5]: *** [../Makefile.test:68: methods.out] Error 137
See
https://buildd.debian.org/status/fetch.php?pkg=macaulay2=mips64el=1.19%2Bds-1=1637251853=0
Cheers
--
Sebastian Ramacher
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: macaulay2
Source-Version: 1.19+ds-2
Done: Doug Torrance
We believe that the bug you reported is fixed in the latest version of
macaulay2, 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.
Doug Torrance (supplier of updated macaulay2 package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 23 Nov 2021 06:12:52 -0500
Source: macaulay2
Built-For-Profiles: noudeb
Architecture: source
Version: 1.19+ds-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Math Team
Changed-By: Doug Torrance
Closes: 1000348 1000350
Changes:
macaulay2 (1.19+ds-2) unstable; urgency=medium
.
* debian/patches/skip-failing-core-tests.patch
- Skip new failing Core tests:
+ methods; failing on mips64el (Closes: #1000348).
* debian/patches/skip-failing-package-tests
- Skip new failing package tests:
+ check(6, "K3Surfaces"); failing on i386.
+ check({4, 6, 7}, "SpecialFanoFourfolds"); failing on armhf.
+ check(14, "SpecialFanoFourfolds"); sometimes segfaults.
* debian/rules
- Ignore example errors on armel, riscv64, and s390x.
* debian/scripts/Debian.m2
- Cache new failing examples:
+ NoetherianOperators::gCorners; failing on armel.
+ NormalToricVarieties::isNef(ToricDivisor); failing on riscv64.
+ ReesAlgebra::PlaneCurveSingularties; failing on s390x
(Closes: #1000350).
Checksums-Sha1:
5909876267c057c7a313d6d12cb278c0211aa286 2992 macaulay2_1.19+ds-2.dsc
bf68d7c7715a7a23e7f4fcd9ae04c72925bd3ab2 103964
macaulay2_1.19+ds-2.debian.tar.xz
23c2524ebe24094aa5ba45f2b6a71d0958ddc72d 12149
macaulay2_1.19+ds-2_source.buildinfo
Checksums-Sha256:
605a21b88dd89a1c58f1d8afd2060244ab9deeede1c937db1c8b02a93889261e 2992
macaulay2_1.19+ds-2.dsc
34fba1272106aa1a8810ebe3607c8ec85b7555c4894e4ba1528edfbf5578ea0d 103964
macaulay2_1.19+ds-2.debian.tar.xz
61e909ea5377cff451cb666efd6b143834ce50c8b66ce6132a2850807621d5f4 12149
macaulay2_1.19+ds-2_source.buildinfo
Files:
dbcbf7b6c78278d781bb578097d5127f 2992 math optional macaulay2_1.19+ds-2.dsc
fc6e62376e60734654acc5c13968e2c0 103964 math optional
macaulay2_1.19+ds-2.debian.tar.xz
2d498ce65cd890cdfdf6e01dec28bfa6 12149 math optional
macaulay2_1.19+ds-2_source.buildinfo
-BEGIN PGP SIGNATURE-
iQJLBAEBCgA1FiEEupghwS4HiU+y5K0AkdxKd57FyRAFAmGczbEXHGR0b3JyYW5j
ZUBwaWVkbW9udC5lZHUACgkQkdxKd57FyRCwNg/+NKdhhlcikFY2sPS91ljQtYx3
+G28l82h+/DSib/aM2oWnOXRb0BvxhH6k9A5F0jAmn69ZiWnkDwx171C5hA4nH7B
A2qbkyKps3VjogkGTAYiT12DI58VeJP3Ejjn+Zrx2ZtaqUwROfMdPy4CoDuunM6n
5h/OelcXNzISb8288PEq0v3SHC/1IdT5YNW9d2R0PdvlZhbTDO1BQ0wQUnTfusnD
Bug#984403: marked as done (warzone2100: ftbfs with GCC-11)
Your message dated Tue, 23 Nov 2021 10:34:30 + with message-id and subject line Bug#984403: fixed in warzone2100 4.2.1-2 has caused the Debian Bug report #984403, regarding warzone2100: 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.) -- 984403: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984403 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:warzone2100 Version: 3.3.0-4 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/warzone2100_3.3.0-4_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. [...] wzglobal.h:688:26: note: in definition of macro ‘likely’ 688 | # define likely(expr) (expr) | ^~~~ debug.h:109:9: note: in expansion of macro ‘ASSERT_HELPER’ 109 | ASSERT_HELPER(expr, AT_MACRO, __FUNCTION__, __VA_ARGS__) | ^ wzstring.cpp:187:17: note: in expansion of macro ‘ASSERT’ 187 | ASSERT(len_distance <= std::numeric_limits::max(), "The length (in codepoints) of a WzString exceeds the max of the return type for length()"); | ^~ wzglobal.h:688:25: note: to match this ‘(’ 688 | # define likely(expr) (expr) | ^ debug.h:95:11: note: in expansion of macro ‘likely’ 95 | likely(expr) ? /* if (expr) */ \ | ^~ debug.h:109:9: note: in expansion of macro ‘ASSERT_HELPER’ 109 | ASSERT_HELPER(expr, AT_MACRO, __FUNCTION__, __VA_ARGS__) | ^ wzstring.cpp:187:17: note: in expansion of macro ‘ASSERT’ 187 | ASSERT(len_distance <= std::numeric_limits::max(), "The length (in codepoints) of a WzString exceeds the max of the return type for length()"); | ^~ wzstring.cpp:187:164: error: expected ‘)’ before ‘;’ token 187 | ASSERT(len_distance <= std::numeric_limits::max(), "The length (in codepoints) of a WzString exceeds the max of the return type for length()"); | ^ In file included from string_ext.h:24, from frame.h:44, from wzstring.cpp:20: debug.h:94:9: note: to match this ‘(’ 94 | ( \ | ^ debug.h:109:9: note: in expansion of macro ‘ASSERT_HELPER’ 109 | ASSERT_HELPER(expr, AT_MACRO, __FUNCTION__, __VA_ARGS__) | ^ wzstring.cpp:187:17: note: in expansion of macro ‘ASSERT’ 187 | ASSERT(len_distance <= std::numeric_limits::max(), "The length (in codepoints) of a WzString exceeds the max of the return type for length()"); | ^~ wzstring.cpp:188:29: error: ‘numeric_limits’ is not a member of ‘std’ 188 | return std::numeric_limits::max(); | ^~ wzstring.cpp:188:44: error: expected primary-expression before ‘int’ 188 | return std::numeric_limits::max(); |
Bug#999537: marked as done (python-matplotlib-venn: FTBFS with matplotlib 3.5 (in experimental): dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13)
Your message dated Tue, 23 Nov 2021 10:34:11 +
with message-id
and subject line Bug#999537: fixed in python-matplotlib-venn 0.11.6-2
has caused the Debian Bug report #999537,
regarding python-matplotlib-venn: FTBFS with matplotlib 3.5 (in experimental):
dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9
returned exit code 13
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.)
--
999537: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999537
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-matplotlib-venn
Version: 0.11.6-1
Severity: important
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-matplotlib35
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64, using matplotlib 3.5 currently in experimental. This version
will soon be uploaded to unstable.
If you have questions about this, please contact Sandro Tosi
.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> xvfb-run --auto-servernum --server-args="-screen 0 1024x768x24" dh_auto_test
> pybuild --test --test-pytest -i python{version} -p 3.9
> I: pybuild base:232: cd
> /<>/.pybuild/cpython3_3.9_matplotlib-venn/build; python3.9 -m
> pytest
> = test session starts
> ==
> platform linux -- Python 3.9.7, pytest-6.2.5, py-1.10.0, pluggy-0.13.0
> rootdir: /<>, configfile: setup.cfg
> collected 0 items / 8 errors
>
> ERRORS
>
> _ ERROR collecting
> .pybuild/cpython3_3.9_matplotlib-venn/build/matplotlib_venn/__init__.py _
> matplotlib_venn/__init__.py:55: in
> from matplotlib_venn._venn2 import venn2, venn2_circles
> matplotlib_venn/_venn2.py:28: in
> from matplotlib.pyplot import gca
> /usr/lib/python3/dist-packages/matplotlib/pyplot.py:2226: in
> switch_backend(rcParams["backend"])
> /usr/lib/python3/dist-packages/matplotlib/pyplot.py:267: in switch_backend
> class backend_mod(matplotlib.backend_bases._Backend):
> /usr/lib/python3/dist-packages/matplotlib/pyplot.py:268: in backend_mod
> locals().update(vars(importlib.import_module(backend_name)))
> /usr/lib/python3.9/importlib/__init__.py:127: in import_module
> return _bootstrap._gcd_import(name[level:], package, level)
> /usr/lib/python3/dist-packages/matplotlib/backends/backend_tkagg.py:1: in
>
> from . import _backend_tk
> /usr/lib/python3/dist-packages/matplotlib/backends/_backend_tk.py:14: in
>
> from PIL import Image, ImageTk
> E ImportError: cannot import name 'ImageTk' from 'PIL'
> (/usr/lib/python3/dist-packages/PIL/__init__.py)
> _ ERROR collecting
> .pybuild/cpython3_3.9_matplotlib-venn/build/matplotlib_venn/_arc.py _
> /usr/lib/python3.9/importlib/__init__.py:127: in import_module
> return _bootstrap._gcd_import(name[level:], package, level)
> :1030: in _gcd_import
> ???
> :1007: in _find_and_load
> ???
> :972: in _find_and_load_unlocked
> ???
> :228: in _call_with_frames_removed
> ???
> :1030: in _gcd_import
> ???
> :1007: in _find_and_load
> ???
> :986: in _find_and_load_unlocked
> ???
> :680: in _load_unlocked
> ???
> :850: in exec_module
> ???
> :228: in _call_with_frames_removed
> ???
> matplotlib_venn/__init__.py:55: in
> from matplotlib_venn._venn2 import venn2, venn2_circles
> matplotlib_venn/_venn2.py:28: in
> from matplotlib.pyplot import gca
> /usr/lib/python3/dist-packages/matplotlib/pyplot.py:2226: in
> switch_backend(rcParams["backend"])
> /usr/lib/python3/dist-packages/matplotlib/pyplot.py:267: in switch_backend
> class backend_mod(matplotlib.backend_bases._Backend):
> /usr/lib/python3/dist-packages/matplotlib/pyplot.py:268: in backend_mod
> locals().update(vars(importlib.import_module(backend_name)))
> /usr/lib/python3.9/importlib/__init__.py:127: in import_module
> return _bootstrap._gcd_import(name[level:], package, level)
> /usr/lib/python3/dist-packages/matplotlib/backends/backend_tkagg.py:1: in
>
> from . import _backend_tk
> /usr/lib/python3/dist-packages/matplotlib/backends/_backend_tk.py:14: in
>
> from PIL import Image, ImageTk
> E ImportError: cannot import name 'ImageTk' from 'PIL'
> (/usr/lib/python3/dist-packages/PIL/__init__.py)
> _ ERROR collecting
> .pybuild/cpython3_3.9_matplotlib-venn/build/matplotlib_venn/_common.py _
> /usr/lib/python3.9/importlib/__init__.py:127: in import_module
> return _bootstrap._gcd_import(name[level:], package, level)
>
Bug#1000441: nomad: FTBFS in bullseye: certificate has expired
Source: nomad
Version: 0.12.10+dfsg1-3
Severity: serious
Tags: ftbfs
Justification: ftbfs
X-Debbugs-Cc: z...@debian.org
Rebuilding nomad in bullseye chroot, it FTBFS with:
=== RUN TestConfig_wrapTLS_OK
config_test.go:560: wrapTLS err: x509: certificate has expired or is not
yet valid: current time 2021-11-23T09:14:32Z is after 2021-11-09T19:48:00Z
--- FAIL: TestConfig_wrapTLS_OK (0.00s)
FAIL
FAILgithub.com/hashicorp/nomad/helper/tlsutil 0.011s
And
nomad-418 2021-11-23T09:21:37.011Z [ERROR] raft/raft.go:1656: nomad.raft:
failed to make requestVote RPC: target="{Voter 127.0.0.1:9687 127.0.0.1:9687}"
error="x509: certificate has expired
or is not yet valid: current time 2021-11-23T09:21:37Z is after
2021-11-09T19:48:00Z"
Processed: fixed 997776 in 1.1.1+2021-11-10-1
Processing commands for cont...@bugs.debian.org:
> fixed 997776 1.1.1+2021-11-10-1
Bug #997776 {Done: Christoph Berg } [src:pgsphere] pgsphere:
FTBFS: Error: debian/control needs updating from debian/control.in. Run
'pg_buildext updatecontrol'.
Marked as fixed in versions pgsphere/1.1.1+2021-11-10-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
997776: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997776
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Blocked by pandas not build for python3.10
Processing control commands:
> block -1 by 1000422
Bug #999525 [src:bmtk] bmtk: FTBFS with numpy 1.21 (in experimental):
dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9
returned exit code 13
999525 was not blocked by any bugs.
999525 was not blocking any bugs.
Added blocking bug(s) of 999525: 1000422
--
999525: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999525
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Blocked by pandas not build for python3.10
Processing control commands: > block -1 by 1000422 Bug #1000423 [src:python-biom-format] python-biom-format: FTBFS with Python 3.10 - Test failures 1000423 was blocked by: 1000422 1000423 was not blocking any bugs. Ignoring request to alter blocking bugs of bug #1000423 to the same blocks previously set -- 1000423: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000423 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
