Bug#1106689: marked as done (libvpx: double-free in vpx_codec_enc_init_multi)

2025-05-27 Thread Debian Bug Tracking System
Your message dated Wed, 28 May 2025 04:52:11 + with message-id and subject line Bug#1106689: fixed in libvpx 1.15.0-2.1 has caused the Debian Bug report #1106689, regarding libvpx: double-free in vpx_codec_enc_init_multi to be marked as done. This means that you claim that the problem has bee

Processed: closing 1106686

2025-05-27 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1106686 Bug #1106686 [src:nagvis] nagvis: CVE-2024-38866 CVE-2024-47090 Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1106686: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1106686 D

Bug#1084690: marked as done (python-discord: removal of Python standard libraries in Python 3.13)

2025-05-27 Thread Debian Bug Tracking System
Your message dated Wed, 28 May 2025 03:22:23 + with message-id and subject line Fixed in new upstream version has caused the Debian Bug report #1084690, regarding python-discord: removal of Python standard libraries in Python 3.13 to be marked as done. This means that you claim that the probl

Bug#1105827: marked as done (abseil: autopkgtest regression in testing)

2025-05-27 Thread Debian Bug Tracking System
Your message dated Wed, 28 May 2025 02:49:02 + with message-id and subject line Bug#1105827: fixed in abseil 20240722.0-4 has caused the Debian Bug report #1105827, regarding abseil: autopkgtest regression in testing to be marked as done. This means that you claim that the problem has been de

Bug#882452: marked as done (FTBFS: unknown opcode pause in delaunay_3d.cpp)

2025-05-27 Thread Debian Bug Tracking System
Your message dated Wed, 28 May 2025 01:14:13 +0200 with message-id and subject line FTBFS: unknown opcode pause in delaunay_3d.cpp has caused the Debian Bug report #882452, regarding FTBFS: unknown opcode pause in delaunay_3d.cpp to be marked as done. This means that you claim that the problem ha

Bug#1082128: marked as done (python-thinc FTBFS with Python 3.13)

2025-05-27 Thread Debian Bug Tracking System
Your message dated Tue, 27 May 2025 23:04:17 + with message-id and subject line Bug#1082128: fixed in python-thinc 9.1.1-1 has caused the Debian Bug report #1082128, regarding python-thinc FTBFS with Python 3.13 to be marked as done. This means that you claim that the problem has been dealt w

Bug#1089717: marked as done (python-thinc: Drop cython3-legacy)

2025-05-27 Thread Debian Bug Tracking System
Your message dated Tue, 27 May 2025 23:04:17 + with message-id and subject line Bug#1089717: fixed in python-thinc 9.1.1-1 has caused the Debian Bug report #1089717, regarding python-thinc: Drop cython3-legacy to be marked as done. This means that you claim that the problem has been dealt wit

Bug#1106609: marked as done (rust-hurl ftbfs with libxml 2.14.x from experimental)

2025-05-27 Thread Debian Bug Tracking System
Your message dated Tue, 27 May 2025 21:51:30 + with message-id and subject line Bug#1106609: fixed in rust-hurl 6.1.1-1 has caused the Debian Bug report #1106609, regarding rust-hurl ftbfs with libxml 2.14.x from experimental to be marked as done. This means that you claim that the problem ha

Bug#1106451: marked as done (unblock: reproc/14.2.5-2)

2025-05-27 Thread Debian Bug Tracking System
Your message dated Tue, 27 May 2025 22:23:31 + with message-id and subject line unblock reproc has caused the Debian Bug report #1106451, regarding unblock: reproc/14.2.5-2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

Bug#1106665: marked as done (unblock: flask/3.1.1-1)

2025-05-27 Thread Debian Bug Tracking System
Your message dated Tue, 27 May 2025 21:58:15 + with message-id and subject line unblock flask has caused the Debian Bug report #1106665, regarding unblock: flask/3.1.1-1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now you

Bug#1084450: marked as done (android-file-transfer: move from fuse to fuse3)

2025-05-27 Thread Debian Bug Tracking System
Your message dated Tue, 27 May 2025 21:49:27 + with message-id and subject line Bug#1084450: fixed in android-file-transfer 4.5-1 has caused the Debian Bug report #1084450, regarding android-file-transfer: move from fuse to fuse3 to be marked as done. This means that you claim that the proble

Bug#1104823: marked as done (pre-approval/unblock: dpkg/1.22.19)

2025-05-27 Thread Debian Bug Tracking System
Your message dated Tue, 27 May 2025 21:53:58 + with message-id and subject line unblock dpkg has caused the Debian Bug report #1104823, regarding pre-approval/unblock: dpkg/1.22.19 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it

Bug#1106403: marked as done (unblock: archivemount/1b-1)

2025-05-27 Thread Debian Bug Tracking System
Your message dated Tue, 27 May 2025 21:48:11 + with message-id and subject line unblock archivemount has caused the Debian Bug report #1106403, regarding unblock: archivemount/1b-1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it

Bug#1035175: marked as done (metaphlan: please add autopkgtests (to add coverage for python3-numpy))

2025-05-27 Thread Debian Bug Tracking System
Your message dated Tue, 27 May 2025 21:19:03 + with message-id and subject line Bug#1035175: fixed in metaphlan 4.0.4+ds-1 has caused the Debian Bug report #1035175, regarding metaphlan: please add autopkgtests (to add coverage for python3-numpy) to be marked as done. This means that you clai

Bug#882451: marked as done (ovito: FTBFS on armel: QOpenGLFunctions_* does not name a type)

2025-05-27 Thread Debian Bug Tracking System
Your message dated Tue, 27 May 2025 22:46:21 +0200 with message-id and subject line FTBFS on armel: QOpenGLFunctions_* does not name a type has caused the Debian Bug report #882451, regarding ovito: FTBFS on armel: QOpenGLFunctions_* does not name a type to be marked as done. This means that you

Bug#886340: marked as done (FTBFS: Could not connect to display :0 during doc build)

2025-05-27 Thread Debian Bug Tracking System
Your message dated Tue, 27 May 2025 22:44:05 +0200 with message-id and subject line FTBFS: Could not connect to display :0 during doc build has caused the Debian Bug report #886340, regarding FTBFS: Could not connect to display :0 during doc build to be marked as done. This means that you claim t

Bug#1106670: marked as done (nmu: ovito_3.10.5~ds-1)

2025-05-27 Thread Debian Bug Tracking System
Your message dated Tue, 27 May 2025 21:11:14 +0200 with message-id and subject line nmu: ovito_3.10.5~ds-1 has caused the Debian Bug report #1106670, regarding nmu: ovito_3.10.5~ds-1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it i

Bug#1071132: marked as done (ovito accesses the internet during the build)

2025-05-27 Thread Debian Bug Tracking System
Your message dated Tue, 27 May 2025 19:06:20 + with message-id and subject line Bug#1071132: fixed in ovito 3.10.5~ds-2 has caused the Debian Bug report #1071132, regarding ovito accesses the internet during the build to be marked as done. This means that you claim that the problem has been d

Bug#1106663: marked as done (unblock: setuptools/78.1.1-0.1)

2025-05-27 Thread Debian Bug Tracking System
Your message dated Tue, 27 May 2025 17:59:29 + with message-id and subject line unblock setuptools has caused the Debian Bug report #1106663, regarding unblock: setuptools/78.1.1-0.1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case

Bug#1106672: marked as done (nmu: fragments_3.0.1-8)

2025-05-27 Thread Debian Bug Tracking System
Your message dated Tue, 27 May 2025 18:50:51 +0200 with message-id and subject line Re: Bug#1106672: nmu: fragments_3.0.1-8 has caused the Debian Bug report #1106672, regarding nmu: fragments_3.0.1-8 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#1106602: marked as done (unblock: iproute2/6.15.0-1)

2025-05-27 Thread Debian Bug Tracking System
Your message dated Tue, 27 May 2025 16:53:53 + with message-id and subject line unblock iproute2 has caused the Debian Bug report #1106602, regarding unblock: iproute2/6.15.0-1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is

Bug#1106422: marked as done (black: FTBFS: E SyntaxError: f-string: newlines are not allowed in format specifiers for single quoted f-strings)

2025-05-27 Thread Debian Bug Tracking System
Your message dated Tue, 27 May 2025 15:49:13 + with message-id and subject line Bug#1106422: fixed in black 25.1.0-3 has caused the Debian Bug report #1106422, regarding black: FTBFS: E SyntaxError: f-string: newlines are not allowed in format specifiers for single quoted f-strings to be mark

Bug#1105970: marked as done (setuptools: CVE-2025-47273)

2025-05-27 Thread Debian Bug Tracking System
Your message dated Tue, 27 May 2025 15:01:10 + with message-id and subject line Bug#1105970: fixed in setuptools 78.1.1-0.1 has caused the Debian Bug report #1105970, regarding setuptools: CVE-2025-47273 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1106651: marked as done (golang-github-go-ap-errors: FTBFS: cannot find package "github.com/go-ap/jsonld")

2025-05-27 Thread Debian Bug Tracking System
Your message dated Tue, 27 May 2025 14:52:19 + with message-id and subject line Bug#1106651: fixed in golang-github-go-ap-errors 0.0~git20250501.cd50c6a-3 has caused the Debian Bug report #1106651, regarding golang-github-go-ap-errors: FTBFS: cannot find package "github.com/go-ap/jsonld" to

Processed: close 1106284

2025-05-27 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1106284 wontfix Bug #1106284 [systemd] systemd: duplicated line for /run/lock Added tag(s) wontfix. > close 1106284 Bug #1106284 [systemd] systemd: duplicated line for /run/lock Marked Bug as done > End of message, stopping processing here.

Processed: Re: systemd: syntax of /usr/lib/environment.d/99-environment.conf is invalid

2025-05-27 Thread Debian Bug Tracking System
Processing control commands: > tags -1 wontfix Bug #1106484 [systemd] systemd: syntax of /usr/lib/environment.d/99-environment.conf is invalid Added tag(s) wontfix. > close -1 Bug #1106484 [systemd] systemd: syntax of /usr/lib/environment.d/99-environment.conf is invalid Marked Bug as done --

Processed: Re: systemd: SetCredentialEncrypted broken for user services

2025-05-27 Thread Debian Bug Tracking System
Processing control commands: > tags -1 wontfix Bug #1106502 [systemd] systemd: SetCredentialEncrypted broken for user services Added tag(s) wontfix. > close -1 Bug #1106502 [systemd] systemd: SetCredentialEncrypted broken for user services Marked Bug as done -- 1106502: https://bugs.debian.org/c

Bug#1104179: marked as done (ITP: fretboard -- Guitar chord lookup app for GNOME)

2025-05-27 Thread Debian Bug Tracking System
Your message dated Tue, 27 May 2025 13:51:04 + with message-id and subject line Bug#1104179: fixed in fretboard 9.1-2 has caused the Debian Bug report #1104179, regarding ITP: fretboard -- Guitar chord lookup app for GNOME to be marked as done. This means that you claim that the problem has b

Bug#1106606: marked as done (unblock: iotop-c/1.30-1)

2025-05-27 Thread Debian Bug Tracking System
Your message dated Tue, 27 May 2025 13:57:35 + with message-id and subject line unblock iotop-c has caused the Debian Bug report #1106606, regarding unblock: iotop-c/1.30-1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

Bug#1106530: marked as done (asterisk: CVE-2025-47780)

2025-05-27 Thread Debian Bug Tracking System
Your message dated Tue, 27 May 2025 13:04:50 + with message-id and subject line Bug#1106530: fixed in asterisk 1:22.4.1~dfsg+~cs6.15.60671435-1 has caused the Debian Bug report #1106530, regarding asterisk: CVE-2025-47780 to be marked as done. This means that you claim that the problem has be

Bug#1103048: marked as done (asterisk: depends on obsolete uw-imap)

2025-05-27 Thread Debian Bug Tracking System
Your message dated Tue, 27 May 2025 13:04:50 + with message-id and subject line Bug#1103048: fixed in asterisk 1:22.4.1~dfsg+~cs6.15.60671435-1 has caused the Debian Bug report #1103048, regarding asterisk: depends on obsolete uw-imap to be marked as done. This means that you claim that the p

Bug#1106528: marked as done (asterisk: CVE-2025-47779)

2025-05-27 Thread Debian Bug Tracking System
Your message dated Tue, 27 May 2025 13:04:50 + with message-id and subject line Bug#1106528: fixed in asterisk 1:22.4.1~dfsg+~cs6.15.60671435-1 has caused the Debian Bug report #1106528, regarding asterisk: CVE-2025-47779 to be marked as done. This means that you claim that the problem has be

Bug#1106115: marked as done (plymouth: Unrecoverable postinst error in initramfs-tools hook when fc-match -f %{file} == fc-match -f %{file} monospace)

2025-05-27 Thread Debian Bug Tracking System
Your message dated Tue, 27 May 2025 09:19:05 + with message-id and subject line Bug#1106115: fixed in plymouth 24.004.60-5 has caused the Debian Bug report #1106115, regarding plymouth: Unrecoverable postinst error in initramfs-tools hook when fc-match -f %{file} == fc-match -f %{file} monosp

Bug#873499: marked as done (Should depend on "gnupg | gnupg2 | gpg")

2025-05-27 Thread Debian Bug Tracking System
Your message dated Tue, 27 May 2025 11:19:04 + with message-id and subject line Bug#873499: fixed in password-store 1.7.4-8 has caused the Debian Bug report #873499, regarding Should depend on "gnupg | gnupg2 | gpg" to be marked as done. This means that you claim that the problem has been dea

Bug#1089933: marked as done (llvm-toolchain-19: allow multiple version of libc++* and libunwind* to be installed at the same time)

2025-05-27 Thread Debian Bug Tracking System
Your message dated Tue, 27 May 2025 09:06:53 + with message-id and subject line Bug#1089933: fixed in llvm-toolchain-20 1:20.1.5-1~exp3 has caused the Debian Bug report #1089933, regarding llvm-toolchain-19: allow multiple version of libc++* and libunwind* to be installed at the same time to