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

Your message dated Fri, 26 Nov 2021 05:34:22 + with message-id and subject line Bug#994385: fixed in uvloop 0.16.0+ds1-2 has caused the Debian Bug report #994385, regarding uvloop: Removal of the python3-*-dbg packages in sid/bookworm to be marked as done. This means that you claim that the

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

Your message dated Fri, 26 Nov 2021 05:18:59 + with message-id and subject line Bug#997644: fixed in rnc2rng 2.6.6-1 has caused the Debian Bug report #997644, regarding rnc2rng: FTBFS: error in rnc2rng setup command: use_2to3 is invalid. to be marked as done. This means that you claim that

Bug#997620: marked as done (python-dexml: FTBFS: error in dexml setup command: use_2to3 is invalid.)

Your message dated Fri, 26 Nov 2021 05:03:36 + with message-id and subject line Bug#997620: fixed in flask-openid 1.3.0+dfsg-1 has caused the Debian Bug report #997620, regarding python-dexml: FTBFS: error in dexml setup command: use_2to3 is invalid. to be marked as done. This means that

Bug#996780: gnome-boxes: Systematic system freeze few seconds after launching a Windows WM

Gunnar question made me question X server, and apparently it's related to Wayland, cause opening a session with Xorg, i can't reproduce it Le mar. 23 nov. 2021, 15 h 52, Mathieu R. a écrit : > i'm not, i'm using intel drivers > > Le sam. 20 nov. 2021, 18 h 43, Gunnar Hjalmarsson a > écrit : >

Bug#998471: marked as done (gpgme1.0: b-d on python3-all-dev, but not built for all supported Python3 versions)

Your message dated Fri, 26 Nov 2021 03:04:06 + with message-id and subject line Bug#998471: fixed in gpgme1.0 1.16.0-1.2 has caused the Debian Bug report #998471, regarding gpgme1.0: b-d on python3-all-dev, but not built for all supported Python3 versions to be marked as done. This means

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

Your message dated Fri, 26 Nov 2021 02:39:38 + with message-id and subject line Bug#997479: fixed in python-httplib2 0.20.2-1 has caused the Debian Bug report #997479, regarding python-httplib2: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit

Processed: bug 996350 is forwarded to https://github.com/nesquena/rabl/issues/745

Processing commands for cont...@bugs.debian.org: > forwarded 996350 https://github.com/nesquena/rabl/issues/745 Bug #996350 [src:ruby-rabl] ruby-rabl: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed. Set Bug forwarded-to-address to 'https://github.com/nesquena/rabl/issues/745'. > thanks

Bug#996350: Problem can be tracked down to ruby-rr

I was examining the problem. The problem seems to be ruby-rr 3.x. rabl actually requires rr 1.x, and with this version it works. I verified this by building against ruby-rr from Stable. But with ruby-rr 3.x in Testing/Unstable it fails. I don't have a fix for that. -- Regards, Daniel Leidert |

Bug#997479: marked as pending in python-httplib2

Control: tag -1 pending Hello, Bug #997479 in python-httplib2 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:

Processed: Bug#997479 marked as pending in python-httplib2

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

Processed: your mail

Processing commands for cont...@bugs.debian.org: > forwarded 1000597 https://github.com/awaw/dnsproxy/issues/6 Bug #1000597 [dnsproxy] dnsproxy only works with DNS servers at localhost Set Bug forwarded-to-address to 'https://github.com/awaw/dnsproxy/issues/6'. > End of message, stopping

Bug#1000625: libopencv-dev: Broken pkg-config file

Package: libopencv-dev Version: 4.5.4+dfsg-6 Severity: serious https://buildd.debian.org/status/logs.php?pkg=mrgingham=1.20-3%2Bb1 ... g++ -Wl,-z,relro -Wl,-z,now -shared -Wl,--default-symver -fPIC -Wl,-soname,libmrgingham.so.2 find_grid.o find_blobs.o find_chessboard_corners.o mrgingham.o

Bug#996295: marked as done (ruby-i18n-inflector-rails: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError:)

Your message dated Fri, 26 Nov 2021 01:08:40 + with message-id and subject line Bug#996295: fixed in ruby-i18n-inflector-rails 1.0.7-5 has caused the Debian Bug report #996295, regarding ruby-i18n-inflector-rails: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: to be

Processed: tagging 996221

Processing commands for cont...@bugs.debian.org: > # > https://salsa.debian.org/ruby-team/ruby-ethon/-/commit/fc33a6c779b9e95b8799c9803f8a45fa3a358e4a > tags 996221 + pending Bug #996221 [src:ruby-ethon] ruby-ethon: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Failure/Error: require

Processed: Bug#996295 marked as pending in ruby-i18n-inflector-rails

Processing control commands: > tag -1 pending Bug #996295 [src:ruby-i18n-inflector-rails] ruby-i18n-inflector-rails: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: Added tag(s) pending. -- 996295: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996295 Debian Bug

Bug#996295: marked as pending in ruby-i18n-inflector-rails

Control: tag -1 pending Hello, Bug #996295 in ruby-i18n-inflector-rails 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:

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

Your message dated Fri, 26 Nov 2021 00:20:49 + with message-id and subject line Bug#994374: fixed in reprozip 1.1-1 has caused the Debian Bug report #994374, regarding reprozip: Removal of the python3-*-dbg packages in sid/bookworm to be marked as done. This means that you claim that the

Bug#998441: marked as done (reprozip: FTBFS on 2nd reproducible build)

Your message dated Fri, 26 Nov 2021 00:20:49 + with message-id and subject line Bug#998441: fixed in reprozip 1.1-1 has caused the Debian Bug report #998441, regarding reprozip: FTBFS on 2nd reproducible build to be marked as done. This means that you claim that the problem has been dealt

Bug#996306: marked as done (ruby-jsonpath: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: RuntimeError: character '|' not supported in query.)

Your message dated Thu, 25 Nov 2021 23:49:57 + with message-id and subject line Bug#996306: fixed in ruby-jsonpath 1.1.0-1 has caused the Debian Bug report #996306, regarding ruby-jsonpath: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: RuntimeError: character '|' not supported in query.

Bug#1000230: screenruler fails to start

Dear George, On one of the two Debian-stable machines I manage libcanberra-gtk3-module is installed: $ LANG=en_US.utf8 sudo aptitude show libcanberra-gtk3-module | egrep "(State)|(Version)" Version: 0.30-7 State: installed On this machine, screenruler works. I'll check the other machine in

Bug#997342: marked as done (sorl-thumbnail: FTBFS: ImportError: cannot import name 'python_2_unicode_compatible' from 'django.utils.encoding' (/usr/lib/python3/dist-packages/django/utils/encoding.py))

Your message dated Thu, 25 Nov 2021 23:04:12 + with message-id and subject line Bug#997342: fixed in sorl-thumbnail 12.7.0-1 has caused the Debian Bug report #997342, regarding sorl-thumbnail: FTBFS: ImportError: cannot import name 'python_2_unicode_compatible' from 'django.utils.encoding'

Processed: forcibly merging 995410 1000502

Processing commands for cont...@bugs.debian.org: > forcemerge 995410 1000502 Bug #995410 [src:breezy] breezy: FTBFS: Bug #995410 [src:breezy] breezy: FTBFS: Added tag(s) ftbfs. Bug #1000502 [src:breezy] breezy FTBFS: ModuleNotFoundError: No module named 'breezy.testingplugins.plugin' Marked as

Bug#951248: marked as done (origami-pdf: autopkgtest failure: output to stderr: warning: constant ::Bignum is deprecated)

Your message dated Thu, 25 Nov 2021 22:21:57 + with message-id and subject line Bug#951248: fixed in origami-pdf 2.0.4+dfsg-1 has caused the Debian Bug report #951248, regarding origami-pdf: autopkgtest failure: output to stderr: warning: constant ::Bignum is deprecated to be marked as done.

Bug#996155: marked as done (origami-pdf: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: wrong number of arguments (given 2, expected 1))

Your message dated Thu, 25 Nov 2021 22:21:57 + with message-id and subject line Bug#996155: fixed in origami-pdf 2.0.4+dfsg-1 has caused the Debian Bug report #996155, regarding origami-pdf: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: wrong number of arguments (given 2,

Processed: forcibly merging 990443 911735

Processing commands for cont...@bugs.debian.org: > forcemerge 990443 911735 Bug #990443 [origami-pdf] origami-pdf: pdfwalker crashes on start: /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require': superclass mismatch for class Socket (TypeError) Bug #911735

Processed: Bug#951248 marked as pending in origami-pdf

Processing control commands: > tag -1 pending Bug #951248 [src:origami-pdf] origami-pdf: autopkgtest failure: output to stderr: warning: constant ::Bignum is deprecated Added tag(s) pending. -- 951248: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951248 Debian Bug Tracking System Contact

Bug#996155: marked as pending in origami-pdf

Control: tag -1 pending Hello, Bug #996155 in origami-pdf 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:

Bug#951248: marked as pending in origami-pdf

Control: tag -1 pending Hello, Bug #951248 in origami-pdf 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:

Processed: Bug#996155 marked as pending in origami-pdf

Processing control commands: > tag -1 pending Bug #996155 [src:origami-pdf] origami-pdf: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: wrong number of arguments (given 2, expected 1) Added tag(s) pending. -- 996155: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996155

Processed: cloning 990443, reassign -1 to ruby-gtk2 ..., block 990443 with -1

Processing commands for cont...@bugs.debian.org: > clone 990443 -1 Bug #990443 [origami-pdf] origami-pdf: pdfwalker crashes on start: /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require': superclass mismatch for class Socket (TypeError) Bug 990443 cloned as bug 1000618

Processed: bug 990443 is forwarded to https://github.com/ruby-gnome/ruby-gnome/issues/1449

Processing commands for cont...@bugs.debian.org: > forwarded 990443 https://github.com/ruby-gnome/ruby-gnome/issues/1449 Bug #990443 [origami-pdf] origami-pdf: pdfwalker crashes on start: /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require': superclass mismatch for

Bug#1000617: python3-nbclient_0.5.6-1: trying to overwrite '/usr/bin/jupyter-run', which is also in package jupyter-client 7.0.6-2

Package: python3-nbclient Version: 0.5.5-1 Severity: serious -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer, it looks like python3-nbclient / jupyter-client don't play well together: Unpacking python3-nbclient (0.5.6-1) over (0.5.5-1) ... dpkg: error processing archive

Bug#996806: [Pkg-mailman-hackers] Bug#996806: mailmain3: Expected test results for arc_validate tests need updating

Jordi Mallach wrote on 24/11/2021 at 23:39:00+0100: > Source: mailman3 > Version: 3.3.3-1 > Followup-For: Bug #996806 > > Apparently this is fixed in upstream commit > f311b135fe13e3ec07ef2eedadba9c09b25e57ff > > See > >

Bug#990443: [DRE-maint] Bug#990443: Issue seems to be ruby-gtk2

Am Donnerstag, dem 25.11.2021 um 22:15 +0100 schrieb Daniel Leidert: > I did some debugging with this issue and it actually seems to be caused by > ruby-gtk2. It is easy to reproduce. In irb: > > require 'gtk2' > include Gtk > require 'openssl' > > => crash (happens when openssl loads

Bug#1000613: gammapy FTBFS on !amd64: test failures

Source: gammapy Version: 0.19-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=gammapy=0.19-1 ... === FAILURES === __ test_binary_erode ___

Bug#990443: Issue seems to be ruby-gtk2

I did some debugging with this issue and it actually seems to be caused by ruby-gtk2. It is easy to reproduce. In irb: require 'gtk2' include Gtk require 'openssl' => crash (happens when openssl loads openssl.so): Traceback (most recent call last): 28: from /usr/bin/pdfwalker:25:in `'

Bug#999524: python-language-server: 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

Source: python-language-server Followup-For: Bug #999524 Upstream lost write access to the python-language-server repo https://github.com/palantir/python-language-server/issues/935 so have forked the project to python-lsp-server at https://github.com/python-lsp/python-lsp-server As part of the

Bug#1000611: libvtk9{,-qt}: soname change without library transition

Hi Adrian, thanks for the bug report. It was really an accidental upload into unstable instead of experimental. Yes, I will rename the package and upload it ASAP. Regards Anton Am Do., 25. Nov. 2021 um 22:03 Uhr schrieb Adrian Bunk : > > Package: libvtk9 > Version: 9.1.0+dfsg2-2 > Severity:

Bug#1000612: python-cassandra-driver: flaky test

Source: python-cassandra-driver Version: 3.24.0-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=python-cassandra-driver=3.24.0-1%2Bb1 ... == FAIL: Verify that timer timeouts are honored

Processed: libvtk9{,-qt}: soname change without library transition

Processing control commands: > affects -1 libvtk9-qt src:vtk9 Bug #1000611 [libvtk9] libvtk9{,-qt}: soname change without library transition Added indication that 1000611 affects libvtk9-qt and src:vtk9 -- 1000611: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000611 Debian Bug Tracking

Bug#1000611: libvtk9{,-qt}: soname change without library transition

Package: libvtk9 Version: 9.1.0+dfsg2-2 Severity: serious Control: affects -1 libvtk9-qt src:vtk9 https://ci.debian.net/data/autopkgtest/testing/amd64/f/freecad/16980590/log.gz ... ERROR: TestFemApp (unittest.loader._FailedTest)

Processed: tagging 997644

Processing commands for cont...@bugs.debian.org: > tags 997644 + pending Bug #997644 [src:rnc2rng] rnc2rng: FTBFS: error in rnc2rng setup command: use_2to3 is invalid. Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 997644:

Bug#1000601: marked as done (python3-casa-formats-io need to depend on a versioned python3-numpy)

Your message dated Thu, 25 Nov 2021 20:33:59 + with message-id and subject line Bug#1000601: fixed in casa-formats-io 0.1-2 has caused the Debian Bug report #1000601, regarding python3-casa-formats-io need to depend on a versioned python3-numpy to be marked as done. This means that you claim

Processed: reassign 997959 to ftp.debian.org ..., severity of 997959 is normal, tagging 997959

Processing commands for cont...@bugs.debian.org: > reassign 997959 ftp.debian.org Bug #997959 [src:git-annex] git-annex: FTBFS on 32-bit ARM architectures, but built successfully before Bug reassigned from package 'src:git-annex' to 'ftp.debian.org'. No longer marked as found in versions

Bug#997959: RM: git-annex [armel armhf] -- ROM; enduring issues building on 32-bit ARM architectures

reassign -1 ftp.debian.org retitle -1 RM: git-annex [armel armhf] -- ROM; enduring issues building on 32-bit ARM architectures severity -1 normal thanks Recent releases of git-annex fail to build on 32-bit ARM architectures and no-one has been able to figure out why, including upstream. As this

Bug#996352: marked as done (ruby-rack-timeout: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Error: test_zero_wait_timeout(EnvSettingsTest): ArgumentError: wrong number of arguments (given 2, expe

Your message dated Thu, 25 Nov 2021 19:48:36 + with message-id and subject line Bug#996352: fixed in ruby-rack-timeout 0.5.1-3 has caused the Debian Bug report #996352, regarding ruby-rack-timeout: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Error:

Processed: tagging 996223

Processing commands for cont...@bugs.debian.org: > # this is the predecessor of ruby-factory-bot and an RM requets is pending > tags 996223 + wontfix Bug #996223 [src:ruby-factory-girl] ruby-factory-girl: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: Added tag(s) wontfix.

Processed: tagging 996297

Processing commands for cont...@bugs.debian.org: > tags 996297 + upstream Bug #996297 [src:ruby-ice-nine] ruby-ice-nine: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Failure/Error: expect(subject.end).to be_frozen Ignoring request to alter tags of bug #996297 to the same tags

Bug#996352: marked as pending in ruby-rack-timeout

Control: tag -1 pending Hello, Bug #996352 in ruby-rack-timeout 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:

Processed: Bug#996352 marked as pending in ruby-rack-timeout

Processing control commands: > tag -1 pending Bug #996352 [src:ruby-rack-timeout] ruby-rack-timeout: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Error: test_zero_wait_timeout(EnvSettingsTest): ArgumentError: wrong number of arguments (given 2, expected 1) Added tag(s) pending. --

Bug#969157: marked as done (ruby-diaspora-federation-rails: FTBFS with rails 6 - Could not find 'actionpack' (< 6, >= 4.2) - did find: [actionpack-6.0.3.1])

Your message dated Thu, 25 Nov 2021 19:18:53 + with message-id and subject line Bug#969157: fixed in ruby-diaspora-federation-rails 0.2.7-1 has caused the Debian Bug report #969157, regarding ruby-diaspora-federation-rails: FTBFS with rails 6 - Could not find 'actionpack' (< 6, >= 4.2) - did

Processed: retitle 1000603 to specutils FTBFS with astropy 5.0

Processing commands for cont...@bugs.debian.org: > retitle 1000603 specutils FTBFS with astropy 5.0 Bug #1000603 [src:specutils] specutils FTBFS with Python 3.10 Changed Bug title to 'specutils FTBFS with astropy 5.0' from 'specutils FTBFS with Python 3.10'. > thanks Stopping processing here.

Processed: bug 1000603 is forwarded to https://github.com/astropy/specutils/issues/893

Processing commands for cont...@bugs.debian.org: > forwarded 1000603 https://github.com/astropy/specutils/issues/893 Bug #1000603 [src:specutils] specutils FTBFS with astropy 5.0 Set Bug forwarded-to-address to 'https://github.com/astropy/specutils/issues/893'. > thanks Stopping processing here.

Bug#969157: marked as pending in ruby-diaspora-federation-rails

Control: tag -1 pending Hello, Bug #969157 in ruby-diaspora-federation-rails 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:

Processed: Bug#969157 marked as pending in ruby-diaspora-federation-rails

Processing control commands: > tag -1 pending Bug #969157 [ruby-diaspora-federation-rails] ruby-diaspora-federation-rails: FTBFS with rails 6 - Could not find 'actionpack' (< 6, >= 4.2) - did find: [actionpack-6.0.3.1] Ignoring request to alter tags of bug #969157 to the same tags previously

Processed: Bug#969157 marked as pending in ruby-diaspora-federation-rails

Processing control commands: > tag -1 pending Bug #969157 [ruby-diaspora-federation-rails] ruby-diaspora-federation-rails: FTBFS with rails 6 - Could not find 'actionpack' (< 6, >= 4.2) - did find: [actionpack-6.0.3.1] Added tag(s) pending. -- 969157:

Bug#969157: marked as pending in ruby-diaspora-federation-rails

Control: tag -1 pending Hello, Bug #969157 in ruby-diaspora-federation-rails 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:

Bug#1000603: specutils FTBFS with Python 3.10

Source: specutils Version: 1.4.1-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=specutils=1.4.1-1%2Bb1 ... === FAILURES === __ test_continuum_calculation

Bug#1000365: marked as done (Current pyzmq not playing well with Python 3.10 ?)

Your message dated Thu, 25 Nov 2021 20:01:58 +0100 with message-id and subject line Fixed indeed! has caused the Debian Bug report #1000365, regarding Current pyzmq not playing well with Python 3.10 ? to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#1000601: python3-casa-formats-io need to depend on a versioned python3-numpy

Package: python3-casa-formats-io Version: 0.1-1 Severity: serious https://ci.debian.net/data/autopkgtest/testing/arm64/c/casa-formats-io/16993092/log.gz ... ___ ERROR collecting tests/test_casa_dask.py ___ ImportError while importing test module

Bug#1000578: marked as done (liblogfile-rotate-perl: autopkgtest failure: Can't locate logfile.pm in @INC)

Your message dated Thu, 25 Nov 2021 18:04:50 + with message-id and subject line Bug#1000578: fixed in liblogfile-rotate-perl 1.04-6 has caused the Debian Bug report #1000578, regarding liblogfile-rotate-perl: autopkgtest failure: Can't locate logfile.pm in @INC to be marked as done. This

Bug#1000597: dnsproxy only works with DNS servers at localhost

Package: dnsproxy Version: 1.17-2 Severity: serious X-Debbugs-Cc: mar...@talau.info Hi there, The dnsproxy (1.17-2) only works with DNS servers at localhost. This is a problem, as you cannot use DNS servers from other hosts. The problem was introduced by patch 03_fix_listen_udp_port.patch. But

Bug#964607: Massive update necessary

This gem is out-of-date. Upstream is at 3.2.2, which requires packaging for google-cloud-translate-v2 and google-cloud-translate-v3 and updating google- cloud-core to >= 1.6. The tests require packageing google-style. Regards, Daniel -- Regards, Daniel Leidert | https://www.wgdd.de/ GPG-Key

Bug#1000578: marked as pending in liblogfile-rotate-perl

Control: tag -1 pending Hello, Bug #1000578 in liblogfile-rotate-perl reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Processed: Bug#1000578 marked as pending in liblogfile-rotate-perl

Processing control commands: > tag -1 pending Bug #1000578 [src:liblogfile-rotate-perl] liblogfile-rotate-perl: autopkgtest failure: Can't locate logfile.pm in @INC Added tag(s) pending. -- 1000578: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000578 Debian Bug Tracking System Contact

Bug#992564: marked as done (FTBFS: "rpc/rpc.h" not found (removed from glibc 2.32))

Your message dated Thu, 25 Nov 2021 17:33:38 + with message-id and subject line Bug#992564: fixed in caml-crush 1.0.12-1 has caused the Debian Bug report #992564, regarding FTBFS: "rpc/rpc.h" not found (removed from glibc 2.32) to be marked as done. This means that you claim that the problem

Processed: retitle 1000289 to mbedtls: enabling CMAC support changes ABI

Processing commands for cont...@bugs.debian.org: > retitle 1000289 mbedtls: enabling CMAC support changes ABI Bug #1000289 [mbedtls] tests failing when mbedtls is compiled with CMAC support Changed Bug title to 'mbedtls: enabling CMAC support changes ABI' from 'tests failing when mbedtls is

Bug#999626: marked as done (maxima-emacs: fails to install with xemacs21)

Your message dated Thu, 25 Nov 2021 16:48:50 + with message-id and subject line Bug#999626: fixed in maxima 5.45.1-6 has caused the Debian Bug report #999626, regarding maxima-emacs: fails to install with xemacs21 to be marked as done. This means that you claim that the problem has been

Processed: maxima-emacs: fails to install with xemacs21

Processing commands for cont...@bugs.debian.org: > forwarded 999626 maxima-disc...@lists.sourceforge.net Bug #999626 [maxima-emacs] maxima-emacs: fails to install with xemacs21 Set Bug forwarded-to-address to 'maxima-disc...@lists.sourceforge.net'. > thanks Stopping processing here. Please

Bug#996323: marked as done (ruby-mono-logger: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: wrong number of arguments (given 2, expected 0..1))

Your message dated Thu, 25 Nov 2021 16:34:48 + with message-id and subject line Bug#996323: fixed in ruby-mono-logger 1.1.1-1 has caused the Debian Bug report #996323, regarding ruby-mono-logger: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: wrong number of arguments

Processed: update bts with the right meta info

Processing commands for cont...@bugs.debian.org: > reassign 994783 src:gammapy Bug #994783 {Done: Ole Streicher } [src:gammapy] astropy-regions breaks gammapy autopkgtest: KeyError: '.' Ignoring request to reassign bug #994783 to the same package > fixed 994783 0.19-1 Bug #994783 {Done: Ole

Bug#1000587: marked as done (python-fakeredis: (autopkgtest) needs update for python3.10: ModuleNotFoundError: No module named 'lupa._lupa')

Your message dated Thu, 25 Nov 2021 17:30:53 +0100 with message-id <479dc398-1f83-54ec-bd02-cf4c118ee...@debian.org> and subject line Re: python-fakeredis: (autopkgtest) needs update for python3.10: ModuleNotFoundError: No module named 'lupa._lupa' has caused the Debian Bug report #1000587,

Bug#1000197: marked as done (assimp: binary-any FTBFS)

Your message dated Thu, 25 Nov 2021 16:18:33 + with message-id and subject line Bug#1000197: fixed in assimp 5.1.1~ds0-1 has caused the Debian Bug report #1000197, regarding assimp: binary-any FTBFS to be marked as done. This means that you claim that the problem has been dealt with. If this

Processed: reassign 1000289 to mbedtls, severity of 1000289 is serious

Processing commands for cont...@bugs.debian.org: > reassign 1000289 mbedtls 2.16.11-0.1 Bug #1000289 [src:shadowsocks-libev] tests failing when mbedtls is compiled with CMAC support Bug reassigned from package 'src:shadowsocks-libev' to 'mbedtls'. No longer marked as found in versions

Bug#1000292: Why was libpython3.10-dev not available in the test build?

On 25/11/2021 07.52, Graham Inggs wrote: I think you can simply change the build-depends on python3-dev to python3-all-dev. That fixes the build for me. Andreas

Processed: tagging 1000560, tagging 1000559, tagging 1000558, tagging 1000422, tagging 1000491, tagging 998706

Processing commands for cont...@bugs.debian.org: > tags 1000560 + sid bookworm Bug #1000560 [php-laravel-framework] Compatibility with Symfony 5 Added tag(s) sid and bookworm. > tags 1000559 + sid bookworm Bug #1000559 [php-robmorgan-phinx] Compatibility with Symfony 5 Added tag(s) bookworm and

Bug#1000230: screenruler fails to start

Dear Peter, please can you check whether installing the package libcanberra-gtk3-module solves your issue? If so, this package is probably missing as a dependency for screenruler, and I can easily fix this bug. Best regards, Georges. Peter Mueller a écrit : > Package:

Processed: Bug#996323 marked as pending in ruby-mono-logger

Processing control commands: > tag -1 pending Bug #996323 [src:ruby-mono-logger] ruby-mono-logger: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: wrong number of arguments (given 2, expected 0..1) Added tag(s) pending. -- 996323:

Bug#996323: marked as pending in ruby-mono-logger

Control: tag -1 pending Hello, Bug #996323 in ruby-mono-logger 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:

Processed: bug 996324 is forwarded to https://lists.debian.org/debian-gis/2021/10/msg00003.html

Processing commands for cont...@bugs.debian.org: > forwarded 996324 https://lists.debian.org/debian-gis/2021/10/msg3.html Bug #996324 [src:ruby-netcdf] ruby-netcdf: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Segmentation fault at 0x0034 Set Bug forwarded-to-address to

Bug#1000576: closing 1000576

What about the evdev one? Il gio 25 nov 2021, 14:56 Timo Aaltonen ha scritto: > close 1000576 > thanks > > Not going to happen, synaptics is unmaintained and dropped for a reason. > You can still > have both installed and configure X to use synaptics instead after > installing it. >

Bug#996345: marked as done (ruby-packable: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: tried to create Proc object without a block)

Your message dated Thu, 25 Nov 2021 15:23:21 + with message-id and subject line Bug#996345: fixed in ruby-packable 1.3.14-2 has caused the Debian Bug report #996345, regarding ruby-packable: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: tried to create Proc object without

Processed: owner 1000578

Processing commands for cont...@bugs.debian.org: > owner 1000578 tmanc...@debian.org Bug #1000578 [src:liblogfile-rotate-perl] liblogfile-rotate-perl: autopkgtest failure: Can't locate logfile.pm in @INC Owner recorded as tmanc...@debian.org. > thanks Stopping processing here. Please contact me

Bug#996345: marked as pending in ruby-packable

Control: tag -1 pending Hello, Bug #996345 in ruby-packable 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:

Processed: Bug#996345 marked as pending in ruby-packable

Processing control commands: > tag -1 pending Bug #996345 [src:ruby-packable] ruby-packable: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: tried to create Proc object without a block Added tag(s) pending. -- 996345: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996345

Bug#978875: marked as done (ocaml: ftbfs with autoconf 2.70)

Your message dated Thu, 25 Nov 2021 15:05:06 + with message-id and subject line Bug#978875: fixed in ocaml 4.11.1-5 has caused the Debian Bug report #978875, regarding ocaml: ftbfs with autoconf 2.70 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#998108: firefox freezes shortly after start

After the upgrade to 94.0-2, I still experienced some crashes, but disabling hardware acceleration (about:preferences > General > Performance > uncheck both checkboxes and set processing limit to 8) fixed it for me.

Processed: Bug#978875 marked as pending in ocaml

Processing control commands: > tag -1 pending Bug #978875 [src:ocaml] ocaml: ftbfs with autoconf 2.70 Added tag(s) pending. -- 978875: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978875 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#978875: marked as pending in ocaml

Control: tag -1 pending Hello, Bug #978875 in ocaml 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:

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

Your message dated Thu, 25 Nov 2021 14:38:52 + with message-id and subject line Bug#996383: fixed in ruby-semantic-puppet 1.0.4-1 has caused the Debian Bug report #996383, regarding ruby-semantic-puppet: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: RuntimeError: to be marked as

Bug#999650: marked as done (ruby-oily-png FTBFS on 32bit)

Your message dated Thu, 25 Nov 2021 14:38:44 + with message-id and subject line Bug#999650: fixed in ruby-oily-png 1.2.1~dfsg-3 has caused the Debian Bug report #999650, regarding ruby-oily-png FTBFS on 32bit to be marked as done. This means that you claim that the problem has been dealt

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

Your message dated Thu, 25 Nov 2021 14:37:27 + with message-id and subject line Bug#997308: fixed in python-flask-jwt-extended 4.3.1-1 has caused the Debian Bug report #997308, regarding python-flask-jwt-extended: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p

Processed: bug 1000589 is forwarded to https://github.com/Segfault-Inc/Multicorn/issues/271

Processing commands for cont...@bugs.debian.org: > forwarded 1000589 https://github.com/Segfault-Inc/Multicorn/issues/271 Bug #1000589 [src:postgresql-multicorn] Incompatible with PostgreSQL 14 Set Bug forwarded-to-address to 'https://github.com/Segfault-Inc/Multicorn/issues/271'. > thanks

Bug#1000589: Incompatible with PostgreSQL 14

Source: postgresql-multicorn Version: 1.4.0-4 Severity: serious Multicorn is incompatible with PostgreSQL 14 and needs non-trivial porting while upstream work has stalled for the past two years. https://github.com/Segfault-Inc/Multicorn/issues/271 In the meantime, it should be removed from

Processed: bug 996345 is forwarded to https://github.com/marcandre/packable/issues/15

Processing commands for cont...@bugs.debian.org: > forwarded 996345 https://github.com/marcandre/packable/issues/15 Bug #996345 [src:ruby-packable] ruby-packable: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: tried to create Proc object without a block Set Bug

Processed: closing 1000576

Processing commands for cont...@bugs.debian.org: > close 1000576 Bug #1000576 [xserver-xorg-input-all] xserver-xorg-input-all: Please include other input drivers in dependencies Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1000576:

Bug#1000576: closing 1000576

close 1000576 thanks Not going to happen, synaptics is unmaintained and dropped for a reason. You can still have both installed and configure X to use synaptics instead after installing it.

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

Your message dated Thu, 25 Nov 2021 13:49:15 + with message-id and subject line Bug#996300: fixed in ruby-jaeger-client 1.2.0-1 has caused the Debian Bug report #996300, regarding ruby-jaeger-client: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: to be marked as done.

Bug#1000465: libodbc1: Missing dependency and dangling symlink

Hi On 2021-11-25 13:22:12, Guillem Jover wrote: > On Thu, 2021-11-25 at 12:26:29 +0100, [EXT] Vincent Lefevre wrote: > > [Cc Sebastian Ramacher] > > > > On 2021-11-25 21:42:48 +1100, Hugh McMaster wrote: > > > On Thu, 25 Nov 2021 at 03:39, Vincent Lefevre wrote: > > > > > > > > On 2021-11-24

Processed: bug 999650 is forwarded to https://github.com/wvanbergen/oily_png/issues/24

Processing commands for cont...@bugs.debian.org: > forwarded 999650 https://github.com/wvanbergen/oily_png/issues/24 Bug #999650 [src:ruby-oily-png] ruby-oily-png FTBFS on 32bit Set Bug forwarded-to-address to 'https://github.com/wvanbergen/oily_png/issues/24'. > thanks Stopping processing here.

  1   2   >