Bug#996951: marked as done (linux-image-5.14.0-3-amd64: iouring looses requests)

2021-11-15 Thread Debian Bug Tracking System
Your message dated Mon, 15 Nov 2021 10:00:20 + with message-id and subject line Bug#996951: fixed in linux 5.15.2-1~exp1 has caused the Debian Bug report #996951, regarding linux-image-5.14.0-3-amd64: iouring looses requests to be marked as done. This means that you claim that the problem has

Processed: Bug#995281 marked as pending in lomiri-download-manager

2021-11-15 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #995281 [src:lomiri-download-manager] lomiri-download-manager: FTBFS due to symbols changes Added tag(s) pending. -- 995281: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995281 Debian Bug Tracking System Contact ow...@bugs.debian.org with p

Bug#995281: marked as pending in lomiri-download-manager

2021-11-15 Thread Marius Gripsgard
Control: tag -1 pending Hello, Bug #995281 in lomiri-download-manager 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/ubports-team/lomiri-download-manager/-/com

Bug#998565: Errors due to changes in iso-codes data

2021-11-15 Thread Dr. Tobias Quathamer
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 t

Bug#998587: marked as done (isoquery: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2)

2021-11-15 Thread Debian Bug Tracking System
Your message dated Mon, 15 Nov 2021 11:48:46 + with message-id and subject line Bug#998587: fixed in isoquery 3.2.6-1 has caused the Debian Bug report #998587, regarding isoquery: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2 to be marked as done. This means that

Bug#996225: marked as pending in ruby-fakeredis

2021-11-15 Thread Thomas Goirand
Control: tag -1 pending Hello, Bug #996225 in ruby-fakeredis 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-fakeredis/-/commit/bd0f9fbcaee35603c

Processed: Bug#996225 marked as pending in ruby-fakeredis

2021-11-15 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #996225 [src:ruby-fakeredis] ruby-fakeredis: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: Added tag(s) pending. -- 996225: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996225 Debian Bug Tracking System Contact ow..

Bug#995281: marked as done (lomiri-download-manager: FTBFS due to symbols changes)

2021-11-15 Thread Debian Bug Tracking System
Your message dated Mon, 15 Nov 2021 12:36:35 + with message-id and subject line Bug#995281: fixed in lomiri-download-manager 0.1.0-9 has caused the Debian Bug report #995281, regarding lomiri-download-manager: FTBFS due to symbols changes to be marked as done. This means that you claim that t

Bug#996225: marked as done (ruby-fakeredis: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError:)

2021-11-15 Thread Debian Bug Tracking System
Your message dated Mon, 15 Nov 2021 12:48:43 + with message-id and subject line Bug#996225: fixed in ruby-fakeredis 0.8.0-5 has caused the Debian Bug report #996225, regarding ruby-fakeredis: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: to be marked as done. This me

Bug#996529: marked as done (vagrant: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: RuntimeError:)

2021-11-15 Thread Debian Bug Tracking System
Your message dated Mon, 15 Nov 2021 12:48:51 + with message-id and subject line Bug#996529: fixed in vagrant 2.2.19+dfsg-1 has caused the Debian Bug report #996529, regarding vagrant: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: RuntimeError: to be marked as done. This means that y

Bug#999711: netselect-apt: ERROR: The certificate of 'www.debian.org' is not trusted.

2021-11-15 Thread Jakub Wilk
Package: netselect-apt Severity: serious netselect-apt doesn't work in a minimal environment: # netselect-apt /usr/bin/which: this version of `which' is deprecated; use `command -v' in scripts instead. Using distribution stable. Retrieving the list of mirrors from www.debian.org...

Bug#998867: debootstrap: --no-merged-usr became a no-op

2021-11-15 Thread Dimitri John Ledkov
There are multiple issues reported in a single bug. > This means that I cannot create a Debian chroot from Debian unstable from 10 > years ago from snapshot.debian.org without merged-/usr and thus my chroot > will behave differently as it did back then. > Please re-enable --no-merged-usr so that

Processed: Re: Bug#984087: libayatana-appindicator: ftbfs with GCC-11

2021-11-15 Thread Debian Bug Tracking System
Processing control commands: > close -1 Bug #984087 [src:libayatana-appindicator] libayatana-appindicator: ftbfs with GCC-11 Marked Bug as done > fixed -1 0.5.5-3 Bug #984087 {Done: Mike Gabriel } [src:libayatana-appindicator] libayatana-appindicator: ftbfs with GCC-11 Marked as fixed in version

Bug#999715: ruby-omniauth-github: FTBFS with ruby-omniauth 2.0.x: ERROR: Test "ruby2.7" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block in activate_dependencies':

2021-11-15 Thread Antonio Terceiro
Source: ruby-omniauth-github Version: 1.4.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby-omniauth-2.0 Hi, I would like to upload ruby-omniauth 2.0.4 to unstable soon. During a test rebuild, ruby-omniauth-github was found to fa

Bug#999716: ruby-omniauth-google-oauth2: FTBFS with ruby-omniauth 2.0.x: ERROR: Test "ruby2.7" failed: NoMethodError:

2021-11-15 Thread Antonio Terceiro
Source: ruby-omniauth-google-oauth2 Version: 0.6.0-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby-omniauth-2.0 Hi, I would like to upload ruby-omniauth 2.0.4 to unstable soon. During a test rebuild, ruby-omniauth-google-oauth2 w

Bug#999717: ruby-omniauth-jwt: FTBFS with ruby-omniauth 2.0.x: ERROR: Test "ruby2.7" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block in activate_dependencies': Cou

2021-11-15 Thread Antonio Terceiro
Source: ruby-omniauth-jwt Version: 0.0.2-1.1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby-omniauth-2.0 Hi, I would like to upload ruby-omniauth 2.0.4 to unstable soon. During a test rebuild, ruby-omniauth-jwt was found to fail t

Bug#999718: ruby-omniauth-ldap: FTBFS with ruby-omniauth 2.0.x: ERROR: Test "ruby2.7" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block in activate_dependencies': Co

2021-11-15 Thread Antonio Terceiro
Source: ruby-omniauth-ldap Version: 2.1.1-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby-omniauth-2.0 Hi, I would like to upload ruby-omniauth 2.0.4 to unstable soon. During a test rebuild, ruby-omniauth-ldap was found to fail t

Bug#999712: ruby-omniauth-azure-oauth2: FTBFS with ruby-omniauth 2.0.x: ERROR: Test "ruby2.7" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block in activate_dependenc

2021-11-15 Thread Antonio Terceiro
Source: ruby-omniauth-azure-oauth2 Version: 0.0.10-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby-omniauth-2.0 Hi, I would like to upload ruby-omniauth 2.0.4 to unstable soon. During a test rebuild, ruby-omniauth-azure-oauth2 wa

Bug#999719: ruby-omniauth-multipassword: FTBFS with ruby-omniauth 2.0.x: ERROR: Test "ruby2.7" failed: NoMethodError:

2021-11-15 Thread Antonio Terceiro
Source: ruby-omniauth-multipassword Version: 0.4.2-1.1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby-omniauth-2.0 Hi, I would like to upload ruby-omniauth 2.0.4 to unstable soon. During a test rebuild, ruby-omniauth-multipassword

Bug#999720: ruby-omniauth-oauth: FTBFS with ruby-omniauth 2.0.x: ERROR: Test "ruby2.7" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block in activate_dependencies': C

2021-11-15 Thread Antonio Terceiro
Source: ruby-omniauth-oauth Version: 1.1.0-2.1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby-omniauth-2.0 Hi, I would like to upload ruby-omniauth 2.0.4 to unstable soon. During a test rebuild, ruby-omniauth-oauth was found to fa

Bug#999721: ruby-omniauth-openid-connect: FTBFS with ruby-omniauth 2.0.x: ERROR: Test "ruby2.7" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block in activate_depende

2021-11-15 Thread Antonio Terceiro
Source: ruby-omniauth-openid-connect Version: 0.4.0-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby-omniauth-2.0 Hi, I would like to upload ruby-omniauth 2.0.4 to unstable soon. During a test rebuild, ruby-omniauth-openid-connect

Bug#999713: ruby-omniauth-cas3: FTBFS with ruby-omniauth 2.0.x: ERROR: Test "ruby2.7" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block in activate_dependencies': Co

2021-11-15 Thread Antonio Terceiro
Source: ruby-omniauth-cas3 Version: 1.1.4-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby-omniauth-2.0 Hi, I would like to upload ruby-omniauth 2.0.4 to unstable soon. During a test rebuild, ruby-omniauth-cas3 was found to fail t

Bug#999722: ruby-omniauth-openid: FTBFS with ruby-omniauth 2.0.x: ERROR: Test "ruby2.7" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block in activate_dependencies':

2021-11-15 Thread Antonio Terceiro
Source: ruby-omniauth-openid Version: 1.0.1-4 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby-omniauth-2.0 Hi, I would like to upload ruby-omniauth 2.0.4 to unstable soon. During a test rebuild, ruby-omniauth-openid was found to fa

Bug#999714: ruby-omniauth-crowd: FTBFS with ruby-omniauth 2.0.x: ERROR: Test "ruby2.7" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block in activate_dependencies': C

2021-11-15 Thread Antonio Terceiro
Source: ruby-omniauth-crowd Version: 2.4.0-1.1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby-omniauth-2.0 Hi, I would like to upload ruby-omniauth 2.0.4 to unstable soon. During a test rebuild, ruby-omniauth-crowd was found to fa

Bug#999723: ruby-omniauth-remote-user: FTBFS with ruby-omniauth 2.0.x: ERROR: Test "ruby2.7" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block in activate_dependenci

2021-11-15 Thread Antonio Terceiro
Source: ruby-omniauth-remote-user Version: 0.1.3-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby-omniauth-2.0 Hi, I would like to upload ruby-omniauth 2.0.4 to unstable soon. During a test rebuild, ruby-omniauth-remote-user was f

Bug#999725: ruby-omniauth-saml: FTBFS with ruby-omniauth 2.0.x: ERROR: Test "ruby2.7" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block in activate_dependencies': Co

2021-11-15 Thread Antonio Terceiro
Source: ruby-omniauth-saml Version: 1.10.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby-omniauth-2.0 Hi, I would like to upload ruby-omniauth 2.0.4 to unstable soon. During a test rebuild, ruby-omniauth-saml was found to fail

Bug#999724: ruby-omniauth-salesforce: FTBFS with ruby-omniauth 2.0.x: ERROR: Test "ruby2.7" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block in activate_dependencie

2021-11-15 Thread Antonio Terceiro
Source: ruby-omniauth-salesforce Version: 1.0.5-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby-omniauth-2.0 Hi, I would like to upload ruby-omniauth 2.0.4 to unstable soon. During a test rebuild, ruby-omniauth-salesforce was fou

Bug#999726: ruby-omniauth-shibboleth: FTBFS with ruby-omniauth 2.0.x: ERROR: Test "ruby2.7" failed: Failure/Error: expect(last_response.status).to eq(302)

2021-11-15 Thread Antonio Terceiro
Source: ruby-omniauth-shibboleth Version: 1.3.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby-omniauth-2.0 Hi, I would like to upload ruby-omniauth 2.0.4 to unstable soon. During a test rebuild, ruby-omniauth-shibboleth was fou

Bug#999693: php8.1: Regular expression functions warn "Compilation failed" and return null

2021-11-15 Thread Ondřej Surý
It’s still a bug, but I think it might be a bug in pcre2. The other Matthew (in CC) might need to bump the shlibs on the shared lib to >= 10.39 -- Ondřej Surý (He/Him) > On 15. 11. 2021, at 14:54, Matthew Krauss wrote: > > After running apt upgrade, it works fine. I honestly thought I had up

Bug#998565: Errors due to changes in iso-codes data

2021-11-15 Thread Stuart Prescott
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

Bug#999693: php8.1: Regular expression functions warn "Compilation failed" and return null

2021-11-15 Thread Ondřej Surý
This appears when built with 10.39, but the runtime version is less than that. My guess is that this needs manual debian/libpcre2-8.shlibs override. (Or just mangle the symbols file, so it always generates correct versioned dependency.) We can also as upstream, perhaps this is something that sho

Bug#999693: php8.1: Regular expression functions warn "Compilation failed" and return null

2021-11-15 Thread Matthew Vernon
Hi, On 15/11/2021 14:03, Ondřej Surý wrote: It’s still a bug, but I think it might be a bug in pcre2. The other Matthew (in CC) might need to bump the shlibs on the shared lib to >= 10.39 I'm slightly confused - this appears to be an issue in a php function that went away after an upgrade? Or

Bug#997490: marked as pending in python-twilio

2021-11-15 Thread Neil Williams
Control: tag -1 pending Hello, Bug #997490 in python-twilio 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/python-team/packages/python-twilio/-/commit/b106a239

Processed: Bug#997490 marked as pending in python-twilio

2021-11-15 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #997490 [src:python-twilio] python-twilio: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13 Added tag(s) pending. -- 997490: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997490 Debian

Bug#997225: marked as done (crun: FTBFS: ./libocispec/src/runtime_spec_schema_config_schema.c:2661: undefined reference to `gen_runtime_spec_schema_config_zos')

2021-11-15 Thread Debian Bug Tracking System
Your message dated Mon, 15 Nov 2021 14:55:48 + with message-id and subject line Bug#997225: fixed in crun 0.17+dfsg-1.1 has caused the Debian Bug report #997225, regarding crun: FTBFS: ./libocispec/src/runtime_spec_schema_config_schema.c:2661: undefined reference to `gen_runtime_spec_schema_

Bug#999693: php8.1: Regular expression functions warn "Compilation failed" and return null

2021-11-15 Thread Matthew Vernon
Hi, On 15/11/2021 14:34, Ondřej Surý wrote: This appears when built with 10.39, but the runtime version is less than that. My guess is that this needs manual debian/libpcre2-8.shlibs override. (Or just mangle the symbols file, so it always generates correct versioned dependency.) I've had a

Bug#997490: marked as done (python-twilio: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13)

2021-11-15 Thread Debian Bug Tracking System
Your message dated Mon, 15 Nov 2021 15:19:58 + with message-id and subject line Bug#997490: fixed in python-twilio 7.1.0+ds-1 has caused the Debian Bug report #997490, regarding python-twilio: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit cod

Bug#997604: marked as done (x2gobroker: FTBFS: error in x2gobroker setup command: use_2to3 is invalid.)

2021-11-15 Thread Debian Bug Tracking System
Your message dated Mon, 15 Nov 2021 15:20:05 + with message-id and subject line Bug#997604: fixed in x2gobroker 0.0.4.3-2 has caused the Debian Bug report #997604, regarding x2gobroker: FTBFS: error in x2gobroker setup command: use_2to3 is invalid. to be marked as done. This means that you c

Bug#998482: marked as pending in e2guardian

2021-11-15 Thread Mike Gabriel
Control: tag -1 pending Hello, Bug #998482 in e2guardian 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-edu-pkg-team/e2guardian/-/commit/910419c624b5ca4

Processed: Bug#998482 marked as pending in e2guardian

2021-11-15 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #998482 [src:e2guardian] e2guardian: FTBFS: configure.ac:12: error: AM_INIT_AUTOMAKE expanded multiple times Added tag(s) pending. -- 998482: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998482 Debian Bug Tracking System Contact ow...@bugs.

Bug#998482: marked as done (e2guardian: FTBFS: configure.ac:12: error: AM_INIT_AUTOMAKE expanded multiple times)

2021-11-15 Thread Debian Bug Tracking System
Your message dated Mon, 15 Nov 2021 16:19:40 + with message-id and subject line Bug#998482: fixed in e2guardian 5.3.5-2 has caused the Debian Bug report #998482, regarding e2guardian: FTBFS: configure.ac:12: error: AM_INIT_AUTOMAKE expanded multiple times to be marked as done. This means tha

Bug#999730: mtr: Fix FTBFS with glib2.0 >= 2.70 and deprecated GTimeVal of gtk+2.0

2021-11-15 Thread Lukas Märdian
Package: mtr Version: 0.94-2 Severity: serious Tags: patch ftbfs Justification: fails to build from source (but built successfully in the past) User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu jammy ubuntu-patch X-Debbugs-Cc: sl...@ubuntu.com Hi Robert, mtr fails to build from source,

Bug#997745: marked as done (rdkit: FTBFS: Error: debian/control needs updating from debian/control.in. Run 'pg_buildext updatecontrol'.)

2021-11-15 Thread Debian Bug Tracking System
Your message dated Mon, 15 Nov 2021 17:00:21 + with message-id and subject line Bug#997745: fixed in rdkit 202103.5-1 has caused the Debian Bug report #997745, regarding rdkit: FTBFS: Error: debian/control needs updating from debian/control.in. Run 'pg_buildext updatecontrol'. to be marked as

Bug#998141: marked as done (opencv: ABI breakage causes autopkgtest failures)

2021-11-15 Thread Debian Bug Tracking System
Your message dated Mon, 15 Nov 2021 17:00:17 + with message-id and subject line Bug#998141: fixed in opencv 4.5.4+dfsg-2 has caused the Debian Bug report #998141, regarding opencv: ABI breakage causes autopkgtest failures to be marked as done. This means that you claim that the problem has be

Bug#999494: marked as done (zycore-c: FTBFS on at least mips64el)

2021-11-15 Thread Debian Bug Tracking System
Your message dated Mon, 15 Nov 2021 17:00:24 + with message-id and subject line Bug#999494: fixed in zycore-c 1.1.0-1 has caused the Debian Bug report #999494, regarding zycore-c: FTBFS on at least mips64el to be marked as done. This means that you claim that the problem has been dealt with.

Bug#998142: marked as done (opencv: ABI breakage causes autopkgtest failures)

2021-11-15 Thread Debian Bug Tracking System
Your message dated Mon, 15 Nov 2021 17:00:17 + with message-id and subject line Bug#998141: fixed in opencv 4.5.4+dfsg-2 has caused the Debian Bug report #998141, regarding opencv: ABI breakage causes autopkgtest failures to be marked as done. This means that you claim that the problem has be

Bug#994833: OpenCL programs abort when intel-opencl-icd is installed

2021-11-15 Thread Yuri D'Elia
Is there any progress on the FTBS? libigc is now at 1.0.8744-2 which breaks 21.32.20609-1, making the icd uninstallable.

Processed: [bts-link] source package src:gammapy

2021-11-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:gammapy > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Set

Processed: [bts-link] source package python3-typed-ast

2021-11-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package python3-typed-ast > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.o

Processed: [bts-link] source package gnome-shell-extension-gamemode

2021-11-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package > gnome-shell-extension-gamemode > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l..

Processed: reassign 998510 to gem2deb-test-runner, forcibly merging 998497 998510

2021-11-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 998510 gem2deb-test-runner 1.6 Bug #998510 [src:ruby-premailer-rails] ruby-premailer-rails: FTBFS: ERROR: Test "ruby3.0" failed: cannot load such file -- rails Bug reassigned from package 'src:ruby-premailer-rails' to 'gem2deb-test-run

Bug#996210: marked as pending in ruby-css-parser

2021-11-15 Thread Daniel Leidert
Control: tag -1 pending Hello, Bug #996210 in ruby-css-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-css-parser/-/commit/ade387b157c6884

Processed: Bug#996210 marked as pending in ruby-css-parser

2021-11-15 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #996210 [src:ruby-css-parser] ruby-css-parser: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed. Added tag(s) pending. -- 996210: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996210 Debian Bug Tracking System Contact ow...@bugs.debian.org w

Processed: [bts-link] source package gnome-shell-extension-disconnect-wifi

2021-11-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package > gnome-shell-extension-disconnect-wifi > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-

Processed (with 1 error): reassign 996216 to ruby-faker, forcibly merging 996224 996216

2021-11-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 996216 ruby-faker 1.9.1-2 Bug #996216 [src:ruby-devise-two-factor] ruby-devise-two-factor: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: Bug reassigned from package 'src:ruby-devise-two-factor' to 'ruby-faker'. No

Bug#984332: marked as done (simdjson: ftbfs with GCC-11)

2021-11-15 Thread Debian Bug Tracking System
Your message dated Mon, 15 Nov 2021 18:04:41 + with message-id and subject line Bug#984332: fixed in simdjson 1.0.2-1 has caused the Debian Bug report #984332, regarding simdjson: ftbfs with GCC-11 to be marked as done. This means that you claim that the problem has been dealt with. If this i

Processed: fixed 994569 in 2.0.10-2+deb10u1, fixed 994569 in 2.0.10-2+deb11u1

2021-11-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # DSA 5010-1 > fixed 994569 2.0.10-2+deb10u1 Bug #994569 {Done: Markus Koschany } [src:libxml-security-java] libxml-security-java: CVE-2021-40690 Marked as fixed in versions libxml-security-java/2.0.10-2+deb10u1. > fixed 994569 2.0.10-2+deb11u1 B

Processed: reassign 996216 to src:ruby-faker, forcibly merging 996224 996216

2021-11-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 996216 src:ruby-faker 1.9.1-2 Bug #996216 [ruby-faker] ruby-devise-two-factor: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: Bug reassigned from package 'ruby-faker' to 'src:ruby-faker'. No longer marked as found

Bug#996210: marked as done (ruby-css-parser: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed.)

2021-11-15 Thread Debian Bug Tracking System
Your message dated Mon, 15 Nov 2021 18:24:46 + with message-id and subject line Bug#996210: fixed in ruby-css-parser 1.6.0-2 has caused the Debian Bug report #996210, regarding ruby-css-parser: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed. to be marked as done. This means that you claim t

Bug#996215: marked as pending in ruby-dbf

2021-11-15 Thread Daniel Leidert
Control: tag -1 pending Hello, Bug #996215 in ruby-dbf 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-dbf/-/commit/68debea50349b3f7d8914a21b6327

Processed: Bug#996215 marked as pending in ruby-dbf

2021-11-15 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #996215 [src:ruby-dbf] ruby-dbf: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Failure/Error: @encoding ? value.force_encoding(@encoding).encode(*ENCODING_ARGS) : value Added tag(s) pending. -- 996215: https://bugs.debian.org/cgi-bin/

Bug#997656: marked as done (xfsprogs: FTBFS: mkdir: cannot create directory ‘/usr/include/xfs’: Permission denied)

2021-11-15 Thread Debian Bug Tracking System
Your message dated Mon, 15 Nov 2021 18:25:19 + with message-id and subject line Bug#997656: fixed in xfsprogs 5.14.0-rc1-1 has caused the Debian Bug report #997656, regarding xfsprogs: FTBFS: mkdir: cannot create directory ‘/usr/include/xfs’: Permission denied to be marked as done. This mean

Bug#996215: marked as done (ruby-dbf: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Failure/Error: @encoding ? value.force_encoding(@encoding).encode(*ENCODING_ARGS) : value)

2021-11-15 Thread Debian Bug Tracking System
Your message dated Mon, 15 Nov 2021 18:37:56 + with message-id and subject line Bug#996215: fixed in ruby-dbf 3.0.5-2 has caused the Debian Bug report #996215, regarding ruby-dbf: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Failure/Error: @encoding ? value.force_encoding(@encodin

Bug#999743: xfsprogs FTBFS: .gitcensus: No such file or directory

2021-11-15 Thread Adrian Bunk
Source: xfsprogs Version: 5.14.0-rc1-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=xfsprogs&ver=5.14.0-rc1-1 ... cat: .gitcensus: No such file or directory /bin/tar: .gitcensus: Cannot stat: No such file or directory /bin/tar: Exiting with failure status due to pre

Bug#984403: warzone2100 version 3.4.0 to 4.2.1 CMake build problem

2021-11-15 Thread Markus Koschany
Hi Russell, is your build problem related to Debian bug #984403 "FTBFS with GCC 11" ? I don't intend to investigate this problem soon. We need a new upstream version too. I presume this will fix the current build failures. Regards, Markus #Am Samstag, dem 13.11.2021 um 15:57 +1100 schrieb Ru

Bug#984232: status

2021-11-15 Thread Ryan Pavlik
Upstream has fixed this, and I have a package with the latest upstream sources in progress, happy to accept help to put it over the edge. Ryan OpenPGP_signature Description: OpenPGP digital signature

Bug#998497: marked as done (gem2deb-test-runner: Remove Gemfile.lock files before running the tests)

2021-11-15 Thread Debian Bug Tracking System
Your message dated Mon, 15 Nov 2021 20:54:47 + with message-id and subject line Bug#998497: fixed in gem2deb 1.7 has caused the Debian Bug report #998497, regarding gem2deb-test-runner: Remove Gemfile.lock files before running the tests to be marked as done. This means that you claim that th

Bug#996141: marked as done (ruby-bootsnap: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed.)

2021-11-15 Thread Debian Bug Tracking System
Your message dated Mon, 15 Nov 2021 20:54:47 + with message-id and subject line Bug#998497: fixed in gem2deb 1.7 has caused the Debian Bug report #998497, regarding ruby-bootsnap: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed. to be marked as done. This means that you claim that the proble

Bug#998510: marked as done (ruby-premailer-rails: FTBFS: ERROR: Test "ruby3.0" failed: cannot load such file -- rails)

2021-11-15 Thread Debian Bug Tracking System
Your message dated Mon, 15 Nov 2021 20:54:47 + with message-id and subject line Bug#998497: fixed in gem2deb 1.7 has caused the Debian Bug report #998497, regarding ruby-premailer-rails: FTBFS: ERROR: Test "ruby3.0" failed: cannot load such file -- rails to be marked as done. This means th

Bug#998623: marked as done (pysha3: FTBFS with dh-python 5.20211105 due to missing tox.ini)

2021-11-15 Thread Debian Bug Tracking System
Your message dated Mon, 15 Nov 2021 20:58:05 + with message-id and subject line Bug#998623: fixed in pysha3 1.0.2-4.2 has caused the Debian Bug report #998623, regarding pysha3: FTBFS with dh-python 5.20211105 due to missing tox.ini to be marked as done. This means that you claim that the pro

Processed: Add tag patch

2021-11-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tag 984180 + patch Bug #984180 [src:htdig] htdig: ftbfs with GCC-11 Added tag(s) patch. > End of message, stopping processing here. Please contact me if you need assistance. -- 984180: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984180 Deb

Bug#999642: marked as done (muttdown: FTBFS due to missing B-D: python3-six)

2021-11-15 Thread Debian Bug Tracking System
Your message dated Mon, 15 Nov 2021 21:22:29 + with message-id and subject line Bug#999642: fixed in muttdown 0.3.5-1 has caused the Debian Bug report #999642, regarding muttdown: FTBFS due to missing B-D: python3-six to be marked as done. This means that you claim that the problem has been d

Bug#984301: marked as pending in proftmb

2021-11-15 Thread Étienne Mollier
Control: tag -1 pending Hello, Bug #984301 in proftmb 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/med-team/proftmb/-/commit/bf153faa70740ee6b35127c133de2d8a

Bug#994239: marked as done (work around ftbfs with GCC 11)

2021-11-15 Thread Debian Bug Tracking System
Your message dated Mon, 15 Nov 2021 21:34:43 + with message-id and subject line Bug#994239: fixed in micropython 1.17+ds-1.1 has caused the Debian Bug report #994239, regarding work around ftbfs with GCC 11 to be marked as done. This means that you claim that the problem has been dealt with.

Processed: Bug#984301 marked as pending in proftmb

2021-11-15 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #984301 [src:proftmb] proftmb: ftbfs with GCC-11 Added tag(s) pending. -- 984301: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984301 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#984301: marked as done (proftmb: ftbfs with GCC-11)

2021-11-15 Thread Debian Bug Tracking System
Your message dated Mon, 15 Nov 2021 22:19:14 + with message-id and subject line Bug#984301: fixed in proftmb 1.1.12-10 has caused the Debian Bug report #984301, regarding proftmb: ftbfs with GCC-11 to be marked as done. This means that you claim that the problem has been dealt with. If this i

Bug#997531: marked as done (extra-xdg-menus: FTBFS: rmdir: failed to remove '/<>/debian/extra-xdg-menus/usr/@DATADIRNAME@/': No such file or directory)

2021-11-15 Thread Debian Bug Tracking System
Your message dated Mon, 15 Nov 2021 22:33:59 + with message-id and subject line Bug#997531: fixed in extra-xdg-menus 1.0-6 has caused the Debian Bug report #997531, regarding extra-xdg-menus: FTBFS: rmdir: failed to remove '/<>/debian/extra-xdg-menus/usr/@DATADIRNAME@/': No such file or dire

Bug#999750: lix FTBFS with ldc 1.28.0

2021-11-15 Thread peter green
Source: lix Version: 0.9.29-1.1 Severity: serious Tags: ftbfs The attempts to rebuild lix against ldc 1.28.0 failed, on amd64, i386 and armhf the build failed with. /usr/lib/ldc/x86_64-linux-gnu/include/d/std/algorithm/comparison.d(1531,6): Warning: skipping definition of function `std.algori

Processed: di-netboot-assistant: please drop shellcheck autopkgtest

2021-11-15 Thread Debian Bug Tracking System
Processing control commands: > affects -1 src:shellcheck Bug #999751 [src:di-netboot-assistant] di-netboot-assistant: please drop shellcheck autopkgtest Added indication that 999751 affects src:shellcheck -- 999751: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999751 Debian Bug Tracking Sy

Bug#999751: di-netboot-assistant: please drop shellcheck autopkgtest

2021-11-15 Thread Samuel Henrique
Source: di-netboot-assistant Version: 0.71 Severity: serious X-Debbugs-CC: debian...@lists.debian.org, shellch...@packages.debian.org Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:shellcheck Dear maintainer(s), With a recent upload of shellchec

Processed: tagging 995625

2021-11-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 995625 + patch Bug #995625 [src:httping] httping FTBFS: error: format not a string literal and no format arguments [-Werror=format-security] Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. --

Processed: Re: Bug#995653: django-mailman3 breaks hyperkitty autopkgtest: 'str' object has no attribute 'display_name'

2021-11-15 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 src:hyperkitty 1.3.4-4 Bug #995653 [src:django-mailman3, src:hyperkitty] django-mailman3 breaks hyperkitty autopkgtest: 'str' object has no attribute 'display_name' Bug reassigned from package 'src:django-mailman3, src:hyperkitty' to 'src:hyperkitty'. N

Processed: Bug#996208 marked as pending in ruby-commander

2021-11-15 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #996208 [src:ruby-commander] ruby-commander: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: RuntimeError: Added tag(s) pending. -- 996208: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996208 Debian Bug Tracking System Contact ow...@

Bug#995653: django-mailman3 breaks hyperkitty autopkgtest: 'str' object has no attribute 'display_name'

2021-11-15 Thread Adrian Bunk
Control: reassign -1 src:hyperkitty 1.3.4-4 Control: retitle -1 hyperkitty FTBFS with django-mailman3 1.3.7 Control: tags -1 ftbfs bookworm sid On Sun, Oct 03, 2021 at 07:15:18PM +0200, Paul Gevers wrote: >... >passfail > django-mailman3from testing1

Bug#996208: marked as pending in ruby-commander

2021-11-15 Thread Daniel Leidert
Control: tag -1 pending Hello, Bug #996208 in ruby-commander 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-commander/-/commit/c00887d3bebbd0cc9

Bug#997101: marked as done (gimp-texturize: FTBFS: type_traits:44:3: error: template with C linkage)

2021-11-15 Thread Debian Bug Tracking System
Your message dated Tue, 16 Nov 2021 01:49:07 + with message-id and subject line Bug#997101: fixed in gimp-texturize 2.2-1 has caused the Debian Bug report #997101, regarding gimp-texturize: FTBFS: type_traits:44:3: error: template with C linkage to be marked as done. This means that you clai

Bug#998555: marked as done (cinnamon-session: FTBFS: ../meson.build:2:0: ERROR: Unknown options: "frequent-warnings")

2021-11-15 Thread Debian Bug Tracking System
Your message dated Tue, 16 Nov 2021 01:49:00 + with message-id and subject line Bug#998555: fixed in cinnamon-session 5.0.1-3 has caused the Debian Bug report #998555, regarding cinnamon-session: FTBFS: ../meson.build:2:0: ERROR: Unknown options: "frequent-warnings" to be marked as done. Thi

Bug#999753: wine-development: unsatisfiable build-dependency on unicode-data (< 14)

2021-11-15 Thread Ralf Treinen
Source: wine-development Version: 6.0+repack-1 Severity: serious Usertag: edos-uninstallable Hi, wine-development build-deoends on unicode-data (< 14) but the version in testing and in sid is 14.0.0-1.1. -Ralf.

Bug#996208: marked as done (ruby-commander: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: RuntimeError:)

2021-11-15 Thread Debian Bug Tracking System
Your message dated Tue, 16 Nov 2021 02:39:01 + with message-id and subject line Bug#996208: fixed in ruby-commander 4.5.2-2 has caused the Debian Bug report #996208, regarding ruby-commander: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: RuntimeError: to be marked as done. This mean

Bug#999754: tcsh: character class expansion is badly broken

2021-11-15 Thread Jon Leech
Package: tcsh Version: 6.21.00-1.1 Severity: grave Tags: newcomer Justification: causes non-serious data loss Dear Maintainer, tcsh does not respect character classes. Minimal example: $ mkdir a $ touch a/a a/B $ echo a/[a-z] a/a a/B I expect the result to simply be 'a/a' since 'B' is not in [a

Bug#994335: marked as done (pynfft: Removal of the python3-*-dbg packages in sid/bookworm)

2021-11-15 Thread Debian Bug Tracking System
Your message dated Tue, 16 Nov 2021 05:18:49 + with message-id and subject line Bug#994335: fixed in pynfft 1.3.2-4 has caused the Debian Bug report #994335, regarding pynfft: Removal of the python3-*-dbg packages in sid/bookworm to be marked as done. This means that you claim that the proble

Bug#999754: tcsh: character class expansion is badly broken

2021-11-15 Thread Kimmo Suominen
Please consider applying the following three patches as a minimal fix. 1) To fix the character range comparison bug: https://github.com/tcsh-org/tcsh/commit/4679bde3e1ceca63d6eb4de5ce41c996405e61aa.patch 2) To pass the current more stringent compiler options: https://github.com/tcsh-org/tcsh/comm