Bug#965600: marked as done (jack-tools: Removal of obsolete debhelper compat 5 and 6 in bookworm)

2022-12-29 Thread Debian Bug Tracking System
Your message dated Fri, 30 Dec 2022 07:35:09 + with message-id and subject line Bug#965600: fixed in jack-tools 20131226-1.1 has caused the Debian Bug report #965600, regarding jack-tools: Removal of obsolete debhelper compat 5 and 6 in bookworm to be marked as done. This means that you

Processed: found 1027153 in 1.4.3-0.1

2022-12-29 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 1027153 1.4.3-0.1 Bug #1027153 [src:ruby-rails-html-sanitizer] ruby-rails-html-sanitizer: CVE-2022-23517 CVE-2022-23518 CVE-2022-23519 CVE-2022-23520 Marked as found in versions ruby-rails-html-sanitizer/1.4.3-0.1. > thanks Stopping

Bug#919058: its-tool: crashes when freeing bad xmlDocs

2022-12-29 Thread Paul Gevers
Hi Lars, On Thu, 25 Apr 2019 02:03:01 +0200 Lars Skovlund wrote: So far, there is no response on either the RedHat bug or on the respective GitHub issues. There is a new itstool version available, but it only includes the fixes that we've had available as long as this bug has been open.

Bug#1027305: python3-pyglossary: crashes with ModuleNotFoundError

2022-12-29 Thread Raul Benencia
Package: python3-pyglossary Version: 3.2.1-1.1 Severity: grave Justification: renders package unusable Hi, pyglossary is crashing with a simple invocation: $ pyglossary Traceback (most recent call last): File "/usr/lib/python3/dist-packages/pyglossary/plugins/babylon_bgl/bgl_reader.py",

Bug#1005899: mplayer: should not release with bookworm

2022-12-29 Thread Sebastian Ramacher
On 2022-12-30 01:48:56 +0100, Lorenzo wrote: > Hi Sebastian, > > Could you please clarify if this package should be maintained inside the > Debian-Multimedia Team or outside? I.e. an uploader or a new maintainer? Whatever the new maintainer prefers. The multimedia team always is happy to welcome

Bug#1005899: mplayer: should not release with bookworm

2022-12-29 Thread Lorenzo
Hi Sebastian, Could you please clarify if this package should be maintained inside the Debian-Multimedia Team or outside? I.e. an uploader or a new maintainer? Regards, Lorenzo On Wed, 16 Feb 2022 23:25:00 +0100 Sebastian Ramacher wrote: > Source: mplayer > Version: 2:1.4+ds1-3 > Severity:

Processed: Re: Bug#1027176: u-boot-amlogic: broken non-EFI boot on odroid-c2

2022-12-29 Thread Debian Bug Tracking System
Processing control commands: > severity 1027176 serious Bug #1027176 [u-boot-amlogic] u-boot-amlogic: broken non-EFI boot on odroid-c2 Severity set to 'serious' from 'important' -- 1027176: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027176 Debian Bug Tracking System Contact

Bug#1027297: u-boot: guruplug/sheevaplug: FDT and ATAGS support not compiled in

2022-12-29 Thread Vagrant Cascadian
Package: u-boot Version: 2022.04+dfsg-2 Severity: serious Control: fixed -1 2022.10+dfsg-2 X-Debbugs-Cc: vagr...@debian.org, m...@drkrebs.de, t...@cyrius.com, i...@debian.org At least two people have reported the same issue on sheevaplug and guruplug failing to boot with a message "FDT and ATAGS

Processed: u-boot: guruplug/sheevaplug: FDT and ATAGS support not compiled in

2022-12-29 Thread Debian Bug Tracking System
Processing control commands: > fixed -1 2022.10+dfsg-2 Bug #1027297 [u-boot] u-boot: guruplug/sheevaplug: FDT and ATAGS support not compiled in Marked as fixed in versions u-boot/2022.10+dfsg-2. -- 1027297: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027297 Debian Bug Tracking System

Bug#1027296: ruby3.0: do not release with bookworm

2022-12-29 Thread Sebastian Ramacher
Source: ruby3.0 Version: 3.0.4-8 Severity: serious X-Debbugs-Cc: sramac...@debian.org Following the transition to ruby3.1 as only supported ruby version, let's get ruby3.0 removed from bookworm. Cheers -- Sebastian Ramacher

Bug#1010608: openldap: Flaky test test063-delta-multiprovider

2022-12-29 Thread Ryan Tandy
On Wed, Dec 28, 2022 at 10:32:30PM +0100, Paul Gevers wrote: Then not running the script at all is an improvement over the current situation. Flaky tests are bad. Until a better solution is found, how about skipping the test? Not ideal, but yeah, probably an improvement over shipping a flaky

Processed: your mail

2022-12-29 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1027085 normal Bug #1027085 [src:zfs-linux] linux-image-5.10.0-20-amd64: failed to load zfs modules - after automatic update Severity set to 'normal' from 'grave' > thanks Stopping processing here. Please contact me if you need

Processed: Bug#1026469 marked as pending in metakernel

2022-12-29 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1026469 [src:metakernel] metakernel: FTBFS: FAILED metakernel/magics/tests/test_parallel_magic.py::test_parallel_magic Ignoring request to alter tags of bug #1026469 to the same tags previously set -- 1026469:

Bug#1026469: marked as pending in metakernel

2022-12-29 Thread Joseph Nahmias
Control: tag -1 pending Hello, Bug #1026469 in metakernel 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#1003674: marked as done (php-sabre-vobject: (autopkgtest) needs update for php8.1: ValueError: Epoch doesn't fit in a PHP integer)

2022-12-29 Thread Debian Bug Tracking System
Your message dated Thu, 29 Dec 2022 22:19:51 + with message-id and subject line Bug#1003674: fixed in php-sabre-vobject 2.1.7-6.1 has caused the Debian Bug report #1003674, regarding php-sabre-vobject: (autopkgtest) needs update for php8.1: ValueError: Epoch doesn't fit in a PHP integer to

Bug#1026469: marked as pending in metakernel

2022-12-29 Thread Joseph Nahmias
Control: tag -1 pending Hello, Bug #1026469 in metakernel 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#1026469 marked as pending in metakernel

2022-12-29 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1026469 [src:metakernel] metakernel: FTBFS: FAILED metakernel/magics/tests/test_parallel_magic.py::test_parallel_magic Added tag(s) pending. -- 1026469: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026469 Debian Bug Tracking System

Processed: Actually fixed earlier

2022-12-29 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > fixed 1017650 1.1.2-1 Bug #1017650 {Done: Ben Westover } [src:rust-zram-generator] rust-zram-generator: BD-Uninstallable Marked as fixed in versions rust-zram-generator/1.1.2-1. > End of message, stopping processing here. Please contact me if

Bug#1026605: python-avro: FTBFS: AssertionError: 'reader type: null not compatible with writer type: int' not found in {'reader type: SchemaType.NULL not compatible with writer type: SchemaType.INT'}

2022-12-29 Thread Scott Talbert
On Thu, 29 Dec 2022, Scott Kitterman wrote: On Thursday, December 29, 2022 4:13:20 PM EST Andreas Tille wrote: Control: tags -1 help Hi, I wonder whether someone might suggest a fix for == FAIL:

Bug#1026605: marked as pending in python-avro

2022-12-29 Thread Scott Talbert
Control: tag -1 pending Hello, Bug #1026605 in python-avro 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#1026605 marked as pending in python-avro

2022-12-29 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1026605 [src:python-avro] python-avro: FTBFS: AssertionError: 'reader type: null not compatible with writer type: int' not found in {'reader type: SchemaType.NULL not compatible with writer type: SchemaType.INT'} Added tag(s) pending. --

Bug#1017650: marked as done (rust-zram-generator: BD-Uninstallable)

2022-12-29 Thread Debian Bug Tracking System
Your message dated Thu, 29 Dec 2022 21:56:53 + with message-id and subject line Fixed in 1.1.2-2 has caused the Debian Bug report #1017650, regarding rust-zram-generator: BD-Uninstallable to be marked as done. This means that you claim that the problem has been dealt with. If this is not the

Bug#1027020: marked as done (davmail-server: fails to install: insserv: script davmail-server: service davmail already provided!)

2022-12-29 Thread Debian Bug Tracking System
Your message dated Thu, 29 Dec 2022 21:49:24 + with message-id and subject line Bug#1027020: fixed in davmail 6.0.1.3390-4 has caused the Debian Bug report #1027020, regarding davmail-server: fails to install: insserv: script davmail-server: service davmail already provided! to be marked as

Bug#1026605: python-avro: FTBFS: AssertionError: 'reader type: null not compatible with writer type: int' not found in {'reader type: SchemaType.NULL not compatible with writer type: SchemaType.INT'}

2022-12-29 Thread Scott Kitterman
On Thursday, December 29, 2022 4:13:20 PM EST Andreas Tille wrote: > Control: tags -1 help > > Hi, > > I wonder whether someone might suggest a fix for > > > == > FAIL: test_schema_compatibility_type_mismatch >

Processed: Re: python-avro: FTBFS: AssertionError: 'reader type: null not compatible with writer type: int' not found in {'reader type: SchemaType.NULL not compatible with writer type: SchemaType.INT'

2022-12-29 Thread Debian Bug Tracking System
Processing control commands: > tags -1 help Bug #1026605 [src:python-avro] python-avro: FTBFS: AssertionError: 'reader type: null not compatible with writer type: int' not found in {'reader type: SchemaType.NULL not compatible with writer type: SchemaType.INT'} Added tag(s) help. -- 1026605:

Bug#1026605: python-avro: FTBFS: AssertionError: 'reader type: null not compatible with writer type: int' not found in {'reader type: SchemaType.NULL not compatible with writer type: SchemaType.INT'}

2022-12-29 Thread Andreas Tille
Control: tags -1 help Hi, I wonder whether someone might suggest a fix for == FAIL: test_schema_compatibility_type_mismatch (avro.test.test_compatibility.TestCompatibility.test_schema_compatibility_type_mismatch)

Bug#1026619: marked as done (python-fire: FTBFS: AttributeError: module 'asyncio' has no attribute 'coroutine')

2022-12-29 Thread Debian Bug Tracking System
Your message dated Thu, 29 Dec 2022 20:38:37 + with message-id and subject line Bug#1026619: fixed in python-fire 0.5.0-1 has caused the Debian Bug report #1026619, regarding python-fire: FTBFS: AttributeError: module 'asyncio' has no attribute 'coroutine' to be marked as done. This means

Bug#1026539: theano: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.10 returned exit code 13

2022-12-29 Thread Andreas Tille
Hi Rebecca, given that there were some uploads to experimental I'm wondering what might be the best strategy to fix the bug - either in the version in unstable or in 1.1.2 and upload this to unstable. Kind regards Andreas. -- http://fam-tille.de

Processed: RC Bug #1026634: Forwarded upstream

2022-12-29 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 1026634 https://github.com/aio-libs/yarl/issues/803 Bug #1026634 [src:yarl] yarl: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.11 3.10" returned exit code 13 Set Bug forwarded-to-address to

Processed: Re: Bug#1027112: bazel-bootstrap: /usr/include/absl/synchronization/mutex.h:550: error: undefined reference to 'absl::debian3::Mutex::Unlock()'

2022-12-29 Thread Debian Bug Tracking System
Processing control commands: > tag -1 moreinfo Bug #1027112 [src:bazel-bootstrap] bazel-bootstrap: /usr/include/absl/synchronization/mutex.h:550: error: undefined reference to 'absl::debian3::Mutex::Unlock()' Added tag(s) moreinfo. -- 1027112:

Bug#1027112: bazel-bootstrap: /usr/include/absl/synchronization/mutex.h:550: error: undefined reference to 'absl::debian3::Mutex::Unlock()'

2022-12-29 Thread Olek Wojnar
Control: tag -1 moreinfo Hi Sebastian and thanks for the bug report. On 12/27/22 18:15, Sebastian Ramacher wrote: Source: bazel-bootstrap Version: 4.2.3+ds-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc:

Processed: found 1014539 in 3.1-8

2022-12-29 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 1014539 3.1-8 Bug #1014539 [src:squirrel3] squirrel3: CVE-2022-30292 Marked as found in versions squirrel3/3.1-8. > thanks Stopping processing here. Please contact me if you need assistance. -- 1014539:

Processed: found 1014539 in 3.1-7

2022-12-29 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 1014539 3.1-7 Bug #1014539 [src:squirrel3] squirrel3: CVE-2022-30292 Marked as found in versions squirrel3/3.1-7. > thanks Stopping processing here. Please contact me if you need assistance. -- 1014539:

Bug#1027137: marked as done (kicad: FTBFS: #error "KICAD_USE_EGL can only be used when wxWidgets is compiled with the EGL canvas")

2022-12-29 Thread Debian Bug Tracking System
Your message dated Thu, 29 Dec 2022 19:23:03 + with message-id and subject line Bug#1027137: fixed in kicad 6.0.10+dfsg-2 has caused the Debian Bug report #1027137, regarding kicad: FTBFS: #error "KICAD_USE_EGL can only be used when wxWidgets is compiled with the EGL canvas" to be marked as

Processed: matplotlib: axes3d.quiver() fails when providing args to Line3DCollection

2022-12-29 Thread Debian Bug Tracking System
Processing control commands: > forwarded -1 https://github.com/matplotlib/matplotlib/issues/24842 Bug #1027285 [src:matplotlib] matplotlib: axes3d.quiver() fails when providing args to Line3DCollection Set Bug forwarded-to-address to 'https://github.com/matplotlib/matplotlib/issues/24842'. >

Bug#1027285: matplotlib: axes3d.quiver() fails when providing args to Line3DCollection

2022-12-29 Thread Drew Parsons
Source: matplotlib Version: 3.6.2-3 Severity: serious Justification: debci Control: forwarded -1 https://github.com/matplotlib/matplotlib/issues/24842 Control: block 1027170 by -1 mplot3d.axes3d.quiver() accepts boths args and kwargs in its function definition. Both args (any remaining after the

Bug#1017218: ruby-parallel: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity

2022-12-29 Thread Paul Gevers
Hi, On Sun, 14 Aug 2022 09:20:57 +0200 Lucas Nussbaum wrote: Source: ruby-parallel Version: 1.22.1-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220813 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed

Bug#999178: marked as done (libuninum: missing required debian/rules targets build-arch and/or build-indep)

2022-12-29 Thread Debian Bug Tracking System
Your message dated Thu, 29 Dec 2022 19:05:47 + with message-id and subject line Bug#999178: fixed in libuninum 2.7-1.2 has caused the Debian Bug report #999178, regarding libuninum: missing required debian/rules targets build-arch and/or build-indep to be marked as done. This means that you

Bug#999110: marked as done (tcd-utils: missing required debian/rules targets build-arch and/or build-indep)

2022-12-29 Thread Debian Bug Tracking System
Your message dated Thu, 29 Dec 2022 19:06:51 + with message-id and subject line Bug#999110: fixed in tcd-utils 20061127-2.1 has caused the Debian Bug report #999110, regarding tcd-utils: missing required debian/rules targets build-arch and/or build-indep to be marked as done. This means

Bug#965861: marked as done (vcheck: Removal of obsolete debhelper compat 5 and 6 in bookworm)

2022-12-29 Thread Debian Bug Tracking System
Your message dated Thu, 29 Dec 2022 19:07:39 + with message-id and subject line Bug#965861: fixed in vcheck 1.2.1-7.2 has caused the Debian Bug report #965861, regarding vcheck: Removal of obsolete debhelper compat 5 and 6 in bookworm to be marked as done. This means that you claim that the

Bug#965835: marked as done (tcd-utils: Removal of obsolete debhelper compat 5 and 6 in bookworm)

2022-12-29 Thread Debian Bug Tracking System
Your message dated Thu, 29 Dec 2022 19:06:51 + with message-id and subject line Bug#965835: fixed in tcd-utils 20061127-2.1 has caused the Debian Bug report #965835, regarding tcd-utils: Removal of obsolete debhelper compat 5 and 6 in bookworm to be marked as done. This means that you claim

Bug#1022312: marked as done (ruby-parallel: FTBFS: ERROR: Test "ruby3.1" failed: Failure/Error: `TITLE=true ruby spec/cases/progress.rb 2>&1`.sub(/=+/, '==').strip.should == "Progress: |==|")

2022-12-29 Thread Debian Bug Tracking System
Your message dated Thu, 29 Dec 2022 20:07:32 +0100 with message-id <5b902d0c-45f2-bc5b-edc2-a3998e793...@debian.org> and subject line Re: ruby-parallel: FTBFS: ERROR: Test "ruby3.1" failed: Failure/Error: `TITLE=true ruby spec/cases/progress.rb 2>&1`.sub(/=+/, '==').strip.should == "Progress:

Bug#965695: marked as done (libuninum: Removal of obsolete debhelper compat 5 and 6 in bookworm)

2022-12-29 Thread Debian Bug Tracking System
Your message dated Thu, 29 Dec 2022 19:05:47 + with message-id and subject line Bug#965695: fixed in libuninum 2.7-1.2 has caused the Debian Bug report #965695, regarding libuninum: Removal of obsolete debhelper compat 5 and 6 in bookworm to be marked as done. This means that you claim that

Bug#965523: marked as done (flobopuyo: Removal of obsolete debhelper compat 5 and 6 in bookworm)

2022-12-29 Thread Debian Bug Tracking System
Your message dated Thu, 29 Dec 2022 19:04:47 + with message-id and subject line Bug#965523: fixed in flobopuyo 0.20-5.1 has caused the Debian Bug report #965523, regarding flobopuyo: Removal of obsolete debhelper compat 5 and 6 in bookworm to be marked as done. This means that you claim that

Bug#999305: marked as done (iat: missing required debian/rules targets build-arch and/or build-indep)

2022-12-29 Thread Debian Bug Tracking System
Your message dated Thu, 29 Dec 2022 18:42:30 + with message-id and subject line Bug#999305: fixed in iat 0.1.3-7.1 has caused the Debian Bug report #999305, regarding iat: missing required debian/rules targets build-arch and/or build-indep to be marked as done. This means that you claim

Bug#999046: marked as done (netsend: missing required debian/rules targets build-arch and/or build-indep)

2022-12-29 Thread Debian Bug Tracking System
Your message dated Thu, 29 Dec 2022 18:43:52 + with message-id and subject line Bug#999046: fixed in netsend 0.0~svnr250-1.5 has caused the Debian Bug report #999046, regarding netsend: missing required debian/rules targets build-arch and/or build-indep to be marked as done. This means that

Bug#966862: marked as done (gramophone2: FTBFS: ld: /tmp/ccWY0lhU.o:./global.h:70: multiple definition of `midi'; /tmp/ccHnI4GU.o:./global.h:70: first defined here)

2022-12-29 Thread Debian Bug Tracking System
Your message dated Thu, 29 Dec 2022 18:42:14 + with message-id and subject line Bug#966862: fixed in gramophone2 0.8.13a-3.2 has caused the Debian Bug report #966862, regarding gramophone2: FTBFS: ld: /tmp/ccWY0lhU.o:./global.h:70: multiple definition of `midi';

Bug#999156: marked as done (dbench: missing required debian/rules targets build-arch and/or build-indep)

2022-12-29 Thread Debian Bug Tracking System
Your message dated Thu, 29 Dec 2022 18:41:24 + with message-id and subject line Bug#999156: fixed in dbench 4.0-2.1 has caused the Debian Bug report #999156, regarding dbench: missing required debian/rules targets build-arch and/or build-indep to be marked as done. This means that you claim

Bug#998958: marked as done (filler: missing required debian/rules targets build-arch and/or build-indep)

2022-12-29 Thread Debian Bug Tracking System
Your message dated Thu, 29 Dec 2022 18:41:42 + with message-id and subject line Bug#998958: fixed in filler 1.02-6.4 has caused the Debian Bug report #998958, regarding filler: missing required debian/rules targets build-arch and/or build-indep to be marked as done. This means that you

Bug#998956: marked as done (efax-gtk: missing required debian/rules targets build-arch and/or build-indep)

2022-12-29 Thread Debian Bug Tracking System
Your message dated Thu, 29 Dec 2022 18:41:33 + with message-id and subject line Bug#998956: fixed in efax-gtk 3.2.8-2.3 has caused the Debian Bug report #998956, regarding efax-gtk: missing required debian/rules targets build-arch and/or build-indep to be marked as done. This means that you

Bug#965747: marked as done (netsend: Removal of obsolete debhelper compat 5 and 6 in bookworm)

2022-12-29 Thread Debian Bug Tracking System
Your message dated Thu, 29 Dec 2022 18:43:52 + with message-id and subject line Bug#965747: fixed in netsend 0.0~svnr250-1.5 has caused the Debian Bug report #965747, regarding netsend: Removal of obsolete debhelper compat 5 and 6 in bookworm to be marked as done. This means that you claim

Bug#965589: marked as done (iat: Removal of obsolete debhelper compat 5 and 6 in bookworm)

2022-12-29 Thread Debian Bug Tracking System
Your message dated Thu, 29 Dec 2022 18:42:30 + with message-id and subject line Bug#965589: fixed in iat 0.1.3-7.1 has caused the Debian Bug report #965589, regarding iat: Removal of obsolete debhelper compat 5 and 6 in bookworm to be marked as done. This means that you claim that the

Bug#965521: marked as done (filler: Removal of obsolete debhelper compat 5 and 6 in bookworm)

2022-12-29 Thread Debian Bug Tracking System
Your message dated Thu, 29 Dec 2022 18:41:42 + with message-id and subject line Bug#965521: fixed in filler 1.02-6.4 has caused the Debian Bug report #965521, regarding filler: Removal of obsolete debhelper compat 5 and 6 in bookworm to be marked as done. This means that you claim that the

Bug#965578: marked as done (hasciicam: Removal of obsolete debhelper compat 5 and 6 in bookworm)

2022-12-29 Thread Debian Bug Tracking System
Your message dated Thu, 29 Dec 2022 18:42:22 + with message-id and subject line Bug#965578: fixed in hasciicam 1.1.2-1.1 has caused the Debian Bug report #965578, regarding hasciicam: Removal of obsolete debhelper compat 5 and 6 in bookworm to be marked as done. This means that you claim

Bug#965505: marked as done (efax-gtk: Removal of obsolete debhelper compat 5 and 6 in bookworm)

2022-12-29 Thread Debian Bug Tracking System
Your message dated Thu, 29 Dec 2022 18:41:33 + with message-id and subject line Bug#965505: fixed in efax-gtk 3.2.8-2.3 has caused the Debian Bug report #965505, regarding efax-gtk: Removal of obsolete debhelper compat 5 and 6 in bookworm to be marked as done. This means that you claim that

Bug#965567: marked as done (gramophone2: Removal of obsolete debhelper compat 5 and 6 in bookworm)

2022-12-29 Thread Debian Bug Tracking System
Your message dated Thu, 29 Dec 2022 18:42:14 + with message-id and subject line Bug#965567: fixed in gramophone2 0.8.13a-3.2 has caused the Debian Bug report #965567, regarding gramophone2: Removal of obsolete debhelper compat 5 and 6 in bookworm to be marked as done. This means that you

Bug#965484: marked as done (dbench: Removal of obsolete debhelper compat 5 and 6 in bookworm)

2022-12-29 Thread Debian Bug Tracking System
Your message dated Thu, 29 Dec 2022 18:41:24 + with message-id and subject line Bug#965484: fixed in dbench 4.0-2.1 has caused the Debian Bug report #965484, regarding dbench: Removal of obsolete debhelper compat 5 and 6 in bookworm to be marked as done. This means that you claim that the

Bug#1011647: marked as done (RM: netsend -- RoQA, RC-buggy, dead-upstream, unmaintained, low popcon)

2022-12-29 Thread Debian Bug Tracking System
Your message dated Thu, 29 Dec 2022 18:43:52 + with message-id and subject line Bug#1011647: fixed in netsend 0.0~svnr250-1.5 has caused the Debian Bug report #1011647, regarding RM: netsend -- RoQA, RC-buggy, dead-upstream, unmaintained, low popcon to be marked as done. This means that you

Bug#1027137: kicad: FTBFS: #error "KICAD_USE_EGL can only be used when wxWidgets is compiled with the EGL canvas"

2022-12-29 Thread Carsten Schoenert
Hello Andreas, Am 29.12.22 um 18:00 schrieb Andreas Metzler: (Ideally the cmake setup should check wxWidgets's EGL-status and set KICAD_USE_EGL accordingly instead of failing at build-time.) KiCad upstream did have the same idea some time ago and added a wishlist report against wxWidgets.

Processed: tagging 1026705

2022-12-29 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1026705 + pending Bug #1026705 [src:python-kajiki] python-pecan: FTBFS: E AttributeError: 'code' object has no attribute 'co_endlinetable' Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need

Bug#1026499: rows: FTBFS: AssertionError: Lists differ: [] != ['iso', '8859']

2022-12-29 Thread s3v
Dear Maintainer, After adding python3-magic to B-D (and d/t/control Depends), your package builds fine in my sid chroot environment. Kind Regards

Bug#1026055: marked as done (lapack breaks openturns autopkgtest: undefined reference to `ztrsyl3_' (and 3 more))

2022-12-29 Thread Debian Bug Tracking System
Your message dated Thu, 29 Dec 2022 18:18:27 +0100 with message-id and subject line Re: Bug#1026055: lapack breaks openturns autopkgtest: undefined reference to `ztrsyl3_' (and 3 more) has caused the Debian Bug report #1026055, regarding lapack breaks openturns autopkgtest: undefined reference

Bug#1027086: marked as done (ruby-rest-client: FTBFS with ruby-rspec 3.12: ERROR: Test "ruby3.1" failed: Failure/Error:)

2022-12-29 Thread Debian Bug Tracking System
Your message dated Thu, 29 Dec 2022 17:25:14 + with message-id and subject line Bug#1027086: fixed in ruby-rest-client 2.1.0-3 has caused the Debian Bug report #1027086, regarding ruby-rest-client: FTBFS with ruby-rspec 3.12: ERROR: Test "ruby3.1" failed: Failure/Error: to be marked as

Bug#1003767: marked as done (libyang: autopkgtest failure (and tests the src:libyang2 packages))

2022-12-29 Thread Debian Bug Tracking System
Your message dated Thu, 29 Dec 2022 17:13:28 + with message-id and subject line Bug#1027275: Removed package(s) from unstable has caused the Debian Bug report #1003767, regarding libyang: autopkgtest failure (and tests the src:libyang2 packages) to be marked as done. This means that you

Bug#1003766: marked as done (libyang must stop building libyang-tools)

2022-12-29 Thread Debian Bug Tracking System
Your message dated Thu, 29 Dec 2022 17:13:28 + with message-id and subject line Bug#1027275: Removed package(s) from unstable has caused the Debian Bug report #1003766, regarding libyang must stop building libyang-tools to be marked as done. This means that you claim that the problem has

Bug#999208: marked as done (phamm: missing required debian/rules targets build-arch and/or build-indep)

2022-12-29 Thread Debian Bug Tracking System
Your message dated Thu, 29 Dec 2022 17:08:59 + with message-id and subject line Bug#1027274: Removed package(s) from unstable has caused the Debian Bug report #999208, regarding phamm: missing required debian/rules targets build-arch and/or build-indep to be marked as done. This means that

Bug#985673: marked as done (CVE-2020-15400)

2022-12-29 Thread Debian Bug Tracking System
Your message dated Thu, 29 Dec 2022 17:08:28 + with message-id and subject line Bug#1027269: Removed package(s) from unstable has caused the Debian Bug report #985673, regarding CVE-2020-15400 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#965772: marked as done (phamm: Removal of obsolete debhelper compat 5 and 6 in bookworm)

2022-12-29 Thread Debian Bug Tracking System
Your message dated Thu, 29 Dec 2022 17:08:59 + with message-id and subject line Bug#1027274: Removed package(s) from unstable has caused the Debian Bug report #965772, regarding phamm: Removal of obsolete debhelper compat 5 and 6 in bookworm to be marked as done. This means that you claim

Bug#924731: marked as done (phamm: CVE-2018-20806: Reflected XSS in Phamm login page)

2022-12-29 Thread Debian Bug Tracking System
Your message dated Thu, 29 Dec 2022 17:08:59 + with message-id and subject line Bug#1027274: Removed package(s) from unstable has caused the Debian Bug report #924731, regarding phamm: CVE-2018-20806: Reflected XSS in Phamm login page to be marked as done. This means that you claim that the

Bug#1026993: marked as done (cakephp -- seriously outdated branch)

2022-12-29 Thread Debian Bug Tracking System
Your message dated Thu, 29 Dec 2022 17:08:28 + with message-id and subject line Bug#1027269: Removed package(s) from unstable has caused the Debian Bug report #1026993, regarding cakephp -- seriously outdated branch to be marked as done. This means that you claim that the problem has been

Bug#974586: marked as done (loganalyzer: depends on php5 to use mysql db as a backend.)

2022-12-29 Thread Debian Bug Tracking System
Your message dated Thu, 29 Dec 2022 17:06:51 + with message-id and subject line Bug#1027178: Removed package(s) from unstable has caused the Debian Bug report #974586, regarding loganalyzer: depends on php5 to use mysql db as a backend. to be marked as done. This means that you claim that

Bug#771187: marked as done (primesense-nite-nonfree: Package broken because openni.org is gone)

2022-12-29 Thread Debian Bug Tracking System
Your message dated Thu, 29 Dec 2022 17:07:59 + with message-id and subject line Bug#1027184: Removed package(s) from unstable has caused the Debian Bug report #771187, regarding primesense-nite-nonfree: Package broken because openni.org is gone to be marked as done. This means that you claim

Bug#1026853: marked as done (rust-svgdom: (build-)depends on old version of rust-roxmltree)

2022-12-29 Thread Debian Bug Tracking System
Your message dated Thu, 29 Dec 2022 17:05:28 + with message-id and subject line Bug#1027141: Removed package(s) from unstable has caused the Debian Bug report #1026853, regarding rust-svgdom: (build-)depends on old version of rust-roxmltree to be marked as done. This means that you claim

Bug#1002966: marked as done (selfhtml: Removal of obsolete debhelper compat 5 and 6 in bookworm)

2022-12-29 Thread Debian Bug Tracking System
Your message dated Thu, 29 Dec 2022 17:07:31 + with message-id and subject line Bug#1027181: Removed package(s) from unstable has caused the Debian Bug report #1002966, regarding selfhtml: Removal of obsolete debhelper compat 5 and 6 in bookworm to be marked as done. This means that you

Bug#1002887: marked as done (primesense-nite-nonfree: Removal of obsolete debhelper compat 5 and 6 in bookworm)

2022-12-29 Thread Debian Bug Tracking System
Your message dated Thu, 29 Dec 2022 17:07:59 + with message-id and subject line Bug#1027184: Removed package(s) from unstable has caused the Debian Bug report #1002887, regarding primesense-nite-nonfree: Removal of obsolete debhelper compat 5 and 6 in bookworm to be marked as done. This

Bug#1016963: Please test u-boot for dreamplug jetson-tk1 Bananapi Cubieboard2 Cubietruck

2022-12-29 Thread Ian Campbell
On Wed, 2022-12-28 at 16:30 -0800, Vagrant Cascadian wrote: > jetson-tk1 testing: 2022.04+dfsg-2+b1  ok unstable: 2022.10+dfsg-2 ok exp: 2023.01~rc4+dfsg-1 ok > Bananapi I don't seem to have a working setup for this any more, sorry. > Cubieboard2  testing: 2022.04+dfsg-2+b1 ok

Processed: Re: Bug#1027137: kicad: FTBFS: #error "KICAD_USE_EGL can only be used when wxWidgets is compiled with the EGL canvas"

2022-12-29 Thread Debian Bug Tracking System
Processing control commands: > tags -1 patch Bug #1027137 [src:kicad] kicad: FTBFS: #error "KICAD_USE_EGL can only be used when wxWidgets is compiled with the EGL canvas" Added tag(s) patch. -- 1027137: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027137 Debian Bug Tracking System

Bug#1027137: kicad: FTBFS: #error "KICAD_USE_EGL can only be used when wxWidgets is compiled with the EGL canvas"

2022-12-29 Thread Andreas Metzler
Control: tags -1 patch On 2022-12-28 Sebastian Ramacher wrote: > Source: kicad > Version: 6.0.10+dfsg-1 > Severity: serious > Tags: ftbfs > Justification: fails to build from source (but built successfully in the past) > X-Debbugs-Cc: sramac...@debian.org >

Processed: bug 1027114 is forwarded to https://github.com/moby/moby/issues/44698

2022-12-29 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 1027114 https://github.com/moby/moby/issues/44698 Bug #1027114 [src:docker.io] docker.io: FTBFS: daemon/graphdriver/btrfs/btrfs.go:437:11: args.lim.max_referenced undefined (type _Ctype_struct_btrfs_qgroup_limit has no field or method

Bug#1026612: marked as done (libdebug: FTBFS: log.c:557:16: error: ‘facilitynames’ undeclared (first use in this function); did you mean ‘facility’?)

2022-12-29 Thread Debian Bug Tracking System
Your message dated Thu, 29 Dec 2022 16:51:04 + with message-id and subject line Bug#1026612: fixed in libdebug 0.5.3-7 has caused the Debian Bug report #1026612, regarding libdebug: FTBFS: log.c:557:16: error: ‘facilitynames’ undeclared (first use in this function); did you mean ‘facility’?

Bug#1026312: marked as done (Setuptools 65.5.0-1.1 breaks installing Python modules/extensions via meson)

2022-12-29 Thread Debian Bug Tracking System
Your message dated Thu, 29 Dec 2022 16:52:06 + with message-id and subject line Bug#1026312: fixed in meson 1.0.0-1.1 has caused the Debian Bug report #1026312, regarding Setuptools 65.5.0-1.1 breaks installing Python modules/extensions via meson to be marked as done. This means that you

Bug#1027089: marked as done (ruby-simplecov: FTBFS with ruby-rspec 3.12: ERROR: Test "ruby3.1" failed: Failure/Error: Coverage.start(start_arguments))

2022-12-29 Thread Debian Bug Tracking System
Your message dated Thu, 29 Dec 2022 16:28:04 + with message-id and subject line Bug#1027089: fixed in ruby-simplecov 0.22.0-1 has caused the Debian Bug report #1027089, regarding ruby-simplecov: FTBFS with ruby-rspec 3.12: ERROR: Test "ruby3.1" failed: Failure/Error:

Bug#1026691: marked as done (bandit: FTBFS: TypeError: load() missing 1 required positional argument: 'Loader')

2022-12-29 Thread Debian Bug Tracking System
Your message dated Thu, 29 Dec 2022 16:19:48 + with message-id and subject line Bug#1026691: fixed in bandit 1.6.2-2 has caused the Debian Bug report #1026691, regarding bandit: FTBFS: TypeError: load() missing 1 required positional argument: 'Loader' to be marked as done. This means that

Bug#1026722: gst-python1.0: FTBFS: dh_install: error: missing files, aborting

2022-12-29 Thread Andreas Rönnquist
usr/lib/python* in .install misses items that now are installed to /usr/local/lib/*. This is #1026312. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026312 -- Andreas Rönnquist gus...@debian.org

Processed: we're trying to remove vtk7

2022-12-29 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # the other vtk7 blocking bugs are already serious, this one seems to > # have been missed. > severity 1013190 serious Bug #1013190 [openems] openems: Migration from vtk7 to vtk9 Severity set to 'serious' from 'wishlist' > thanks Stopping

Processed: Merge duplicates

2022-12-29 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > unblock 1026598 by 1026588 Bug #1026598 [src:aardvark-dns] aardvark-dns: FTBFS: unsatisfiable build-dependencies: librust-trust-dns-proto-0.21+backtrace-dev (>= 0.21.1-~~), librust-trust-dns-proto-0.21+default-dev (>= 0.21.1-~~),

Processed: closing 1026588

2022-12-29 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1026588 0.22.0-1 Bug #1026588 [src:rust-trust-dns-server] rust-trust-dns-server: FTBFS: unsatisfiable build-dependencies: librust-trust-dns-client-0.21+default-dev Marked as fixed in versions rust-trust-dns-server/0.22.0-1. Bug #1026588

Bug#1026691: marked as pending in bandit

2022-12-29 Thread Thomas Goirand
Control: tag -1 pending Hello, Bug #1026691 in bandit 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#1026691 marked as pending in bandit

2022-12-29 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1026691 [src:bandit] bandit: FTBFS: TypeError: load() missing 1 required positional argument: 'Loader' Added tag(s) pending. -- 1026691: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026691 Debian Bug Tracking System Contact

Bug#1016963: Please test with helping rpi_arm64

2022-12-29 Thread Denis Pynkin
Hi, On 12/29/22 00:55, Vagrant Cascadian wrote: On 2022-12-28, Vagrant Cascadian wrote: I have not received many test results for current or even remotely recent u-boot platforms in Debian, and u-boot has been blocked from migration to testing partly because of this. As the bookworm freeze

Bug#1024239: libequihash: baseline violation on i386 and FTBFS on !x86

2022-12-29 Thread Joost van Baal-Ilić
Thanks, after consulting with upstream this should be fixed in new upstream https://github.com/stef/equihash/archive/refs/tags/v1.0.3.tar.gz which has https://github.com/stef/equihash/commit/0806afadf99837519469449c55dc425763e8eef7 . I'll upload a new package soonishlish. Bye, Joost On

Processed: limit source to ruby-simplecov, tagging 1027089

2022-12-29 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > limit source ruby-simplecov Limiting to bugs with field 'source' containing at least one of 'ruby-simplecov' Limit currently set to 'source':'ruby-simplecov' > tags 1027089 + pending Bug #1027089 [src:ruby-simplecov] ruby-simplecov: FTBFS with

Bug#1026588: Fix pending in the NEW queue

2022-12-29 Thread Paul Tagliamonte
On Thu, Dec 29, 2022 at 08:03:06AM -0500, Reinhard Tartler wrote: >Dear ftp-master, happy holidays! >Any chance you could fast-track this package so that I can fix 2 RC >bugs? I'm concerned that if not fixed in time, aardvark-dns would be >removed from testing, which would break

Bug#1016963: Help with testing u-boot!

2022-12-29 Thread Diederik de Haas
On Thursday, 29 December 2022 04:33:51 CET Rick Thomas wrote: > Rebooting while watching the serial console output says "U-Boot SPL > 2016.05-rc2+dfsg0~20160423~1-1 (Apr 24 2016 - 04:24:21)" So the firmware > does not correspond to what aptitude says. The main difference with your other

Bug#1016963: Please test u-boot for a64-olinuxino

2022-12-29 Thread rodrigo
On 2022-12-28 21:12, Vagrant Cascadian wrote: On 2022-12-28, Vagrant Cascadian wrote: On 2022-12-22, Vagrant Cascadian wrote: On 2022-08-20, Vagrant Cascadian wrote: On 2022-08-10, Vagrant Cascadian wrote: This bug is just to delay migration to testing while more platforms get tested. If

Bug#1027273: openvswitch: CVE-2022-4337 CVE-2022-4338

2022-12-29 Thread Salvatore Bonaccorso
Source: openvswitch Version: 3.1.0~git20221212.739bcf2-3 Severity: grave Tags: security upstream Forwarded: https://github.com/openvswitch/ovs/pull/405 X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerabilities were published for openvswitch. Filling as RC to make

Bug#1027093: marked as done (ruby-thor: FTBFS with ruby-rspec 3.12: ERROR: Test "ruby3.1" failed: Failure/Error: result = Thor::LineEditor.readline(message, options))

2022-12-29 Thread Debian Bug Tracking System
Your message dated Thu, 29 Dec 2022 13:04:56 + with message-id and subject line Bug#1027093: fixed in ruby-thor 1.2.1-2 has caused the Debian Bug report #1027093, regarding ruby-thor: FTBFS with ruby-rspec 3.12: ERROR: Test "ruby3.1" failed: Failure/Error: result =

Processed: Fix pending in the NEW queue

2022-12-29 Thread Debian Bug Tracking System
Processing control commands: > tag 1026588 pending Bug #1026588 [src:rust-trust-dns-server] rust-trust-dns-server: FTBFS: unsatisfiable build-dependencies: librust-trust-dns-client-0.21+default-dev Added tag(s) pending. > block 1026598 by 1026588 Bug #1026598 [src:aardvark-dns] aardvark-dns:

Bug#1026588: Fix pending in the NEW queue

2022-12-29 Thread Reinhard Tartler
Control: tag 1026588 pending Control: block 1026598 by 1026588 I really should have mentioned this bug in debian/changelog before uploading. It is currently pending at https://ftp-master.debian.org/new/rust-trust-dns-server_0.22.0-1.html Dear ftp-master, happy holidays! Any chance you could

Bug#1027186: marked as done (Need to insist on policy query for tainted objects check)

2022-12-29 Thread Debian Bug Tracking System
Your message dated Thu, 29 Dec 2022 12:49:00 + with message-id and subject line Bug#1027186: fixed in dgit 10.4 has caused the Debian Bug report #1027186, regarding Need to insist on policy query for tainted objects check to be marked as done. This means that you claim that the problem has

  1   2   >