Bug#1010959: nsca-ng FTBFS: test failures

Source: nsca-ng Version: 1.6-4 Severity: serious Tags: ftbfs bookworm sid https://buildd.debian.org/status/logs.php?pkg=nsca-ng&ver=1.6-4%2Bb1 ... /bin/bash './testsuite' -j4 --verbose ## --- ## ## NSCA-ng 1.6 test suite. ## ## --- ## 2. basic.at:32: te

Bug#1010958: sscg FTBFS with OpenSSL 3.0

Source: sscg Version: 3.0.2-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=sscg&ver=3.0.2-1%2Bb1 ... 1/10 generate_rsa_key_test FAIL 0.01s killed by signal 11 SIGSEGV 04:32:21 MALLOC_PERTURB_=87 /<>/obj-x86_64-linux-gnu/generate_rsa_key_test ... S

Processed: omniauth-crowd

Processing commands for cont...@bugs.debian.org: > forwarded 999714 https://github.com/robdimarco/omniauth_crowd/issues/37 Bug #999714 [src:ruby-omniauth-crowd] ruby-omniauth-crowd: FTBFS with ruby-omniauth 2.0.x: ERROR: Test "ruby2.7" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:

Processed: ruby-omniauth-salesforce

Processing commands for cont...@bugs.debian.org: > forwarded 999724 https://github.com/realdoug/omniauth-salesforce/pull/32 Bug #999724 [src:ruby-omniauth-salesforce] ruby-omniauth-salesforce: FTBFS with ruby-omniauth 2.0.x: ERROR: Test "ruby2.7" failed: /usr/lib/ruby/vendor_ruby/rubygems/specif

Processed: ruby-omniauth-openid

Processing commands for cont...@bugs.debian.org: > forwarded 999722 https://github.com/omniauth/omniauth-openid/pull/44 Bug #999722 [src:ruby-omniauth-openid] ruby-omniauth-openid: FTBFS with ruby-omniauth 2.0.x: ERROR: Test "ruby2.7" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1

Processed: ruby-omniauth-google-oauth2

Processing commands for cont...@bugs.debian.org: > forwarded 999716 https://github.com/zquestz/omniauth-google-oauth2/pull/403 Bug #999716 [src:ruby-omniauth-google-oauth2] ruby-omniauth-google-oauth2: FTBFS with ruby-omniauth 2.0.x: ERROR: Test "ruby2.7" failed: NoMethodError: Set Bug forw

Processed: tagging 938921

Processing commands for cont...@bugs.debian.org: > tags 938921 + ftbfs Bug #938921 [src:zorp] zorp: Python2 removal in sid/bullseye Bug #953377 [src:zorp] src:zorp: Depends/Build-Depends on cruft package python-dnspython Bug #966801 [src:zorp] zorp: Unversioned Python removal in sid/bullseye Adde

Bug#1010556: marked as done (undefined symbol extract_begin)

Your message dated Sat, 14 May 2022 05:38:09 + with message-id and subject line Bug#1010556: fixed in qpdfview 0.4.18-7 has caused the Debian Bug report #1010556, regarding undefined symbol extract_begin to be marked as done. This means that you claim that the problem has been dealt with. If

Processed: affects 996422

Processing commands for cont...@bugs.debian.org: > affects 996422 src:mender-client Bug #996422 [src:golang-github-mendersoftware-openssl] golang-github-mendersoftware-openssl: FTBFS with OpenSSL 3.0 Added indication that 996422 affects src:mender-client > thanks Stopping processing here. Please

Processed: ruby-omniauth-saml

Processing commands for cont...@bugs.debian.org: > forwarded 999725 https://github.com/omniauth/omniauth-saml/commit/f7ec7ee Bug #999725 [src:ruby-omniauth-saml] ruby-omniauth-saml: FTBFS with ruby-omniauth 2.0.x: ERROR: Test "ruby2.7" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:

Bug#1010556: undefined symbol extract_begin

On 2022-05-05 04 h 46, Sven Bartscher wrote: > > Since the fix was relatively simple, I opened a merge request on salsa[1]. > > Regards > Sven > > [1]: https://salsa.debian.org/pollo/qpdfview/-/merge_requests/1 Many thanks for the patch. -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷

Processed: reassign 1010946 to wnpp, tagging 999715

Processing commands for cont...@bugs.debian.org: > reassign 1010946 wnpp Bug #1010946 [w3c-keyname] ITP: node-w3c-keyname Warning: Unknown package 'w3c-keyname' Bug reassigned from package 'w3c-keyname' to 'wnpp'. Ignoring request to alter found versions of bug #1010946 to the same values previou

Bug#1010941: python-argcomplete salvaging and possible team (re)join

Hi Marco, Marc and the Team, I have just uploaded to --delayed 5 a workaround fix for #1010941 (FTBFS). The diff is attached I have a clone at https://salsa.debian.org/yoh/python-argcomplete with Marc's NMU imported, and my NMU changes on top. So could be a good starting point to update packagi

Bug#990872: puppetdb.jar crashes out of the box with clojure classpath error

Had a look at similar failures today and I fixed the way libcore-async-clojure exports its classpath [1]. This should _at least_ fix the need for adding tools.analyzer.jar and tools.analyzer.jvm.jar manually to the classpath. I'd be curious to know how that changed things for puppetdb! (maybe thi

Bug#1010941: FTBFS due to tests 56 tests failing

Package: python3-argcomplete Version: 1.12.3-0.1 Severity: serious Tags: ftbfs Justification: fails to build from source Wanted to build a backport but failed to have it built even in current sid. A complete log is at http://www.onerussian.com/tmp/python-argcomplete_1.12.3-0.1_amd64.build and he

Bug#1010232: Processed: severity of 1010232 is serious

Hi Ricardo, Ricardo Mones wrote: > > > # Typos in hard dependencies are clearly release-critical > > Indeed, thanks for adjusting severity. Unfortunately I didn't receive the > original bug report, Oh, I already wondered why there was no reaction from you on that bug report. That explains it wel

Processed: Re: Processed: severity of 1010232 is serious

Processing control commands: > tags -1 fixed pending Bug #1010232 [claws-mail-extra-plugins] claws-mail-extra-plugins: version 4.1.0-1 not installable due to typo in debian/control Added tag(s) pending and fixed. -- 1010232: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010232 Debian Bug T

Bug#1010232: Processed: severity of 1010232 is serious

control: tags -1 fixed pending On Thu, 12 May 2022 23:21:03 + Axel Beckert wrote: > > # Typos in hard dependencies are clearly release-critical Indeed, thanks for adjusting severity. Unfortunately I didn't receive the original bug report, so thanks also for the heads up. Adjusting tags acco

Bug#1008443: golang-github-smartystreets-assertions: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 8 github.com/smartystreets/assertions github.com/smartystreets/assert

Source: golang-github-smartystreets-assertions Version: 1.10.1+ds-1 Followup-For: Bug #1008443 The problem passing tests is still there with smartystreets-assertions 0.13.0 (building with golang 1.18) -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500,

Bug#1009939: sip6: AttributeError: 'YaccProduction' object has no attribute 'parser_manager'

On 4/21/22 05:39, Bas Couwenberg wrote: Since the upgrade to 6.6.1+dfsg-1 qgis FTBFS: According to [0] the current hg tip enables successfull building of QGIS again. That's quite a number of additional changes which I doubt is a good idea to add as patches. That is unless it's going to take a

Bug#1006510: marked as done (myproxy: FTBFS with OpenSSL 3.0)

Your message dated Fri, 13 May 2022 11:36:55 + with message-id and subject line Bug#1006510: fixed in myproxy 6.2.9-3 has caused the Debian Bug report #1006510, regarding myproxy: FTBFS with OpenSSL 3.0 to be marked as done. This means that you claim that the problem has been dealt with. If t

Bug#1009420: marked as done (libotr: FTBFS: client.c:624:30: error: ‘PF_UNIX’ undeclared (first use in this function))

Your message dated Fri, 13 May 2022 10:04:04 + with message-id and subject line Bug#1009420: fixed in libotr 4.1.1-5 has caused the Debian Bug report #1009420, regarding libotr: FTBFS: client.c:624:30: error: ‘PF_UNIX’ undeclared (first use in this function) to be marked as done. This means

Processed: severity of 1010921 is serious

Processing commands for cont...@bugs.debian.org: > # SONAME bump without package rename > severity 1010921 serious Bug #1010921 [src:waylandpp] kodi FTBFS due to outdated shlibs Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance.