Processed: Re: Bug#1107916: libr3: Should libr3 be removed from unstable?

marked as found in versions libr3/1.3.4-1. Ignoring request to alter fixed versions of bug #1107916 to the same values previously set > affects -1 + src:libr3 Bug #1107916 [ftp.debian.org] RM: libr3 -- RoM; rc-buggy Added indication that 1107916 affects src:libr3 -- 1107916: https://bugs

Processed: pam: CVE-2025-6020: pam_namespace: potential privilege escalation

vilege escalation Marked as found in versions pam/1.5.2-6. -- 1107919: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1107919 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1107829: marked as done (coq-elpi:FTBFS:build failed(test Error: too slow: 10.899094 < 10.000000))

Your message dated Tue, 17 Jun 2025 07:04:20 + with message-id and subject line Bug#1107826: fixed in coq-elpi 2.5.0-1.1 has caused the Debian Bug report #1107826, regarding coq-elpi:FTBFS:build failed(test Error: too slow: 10.899094 < 10.00) to be marked as done. This means that

Bug#1107826: marked as done (coq-elpi FTBFS on riscv64: too slow: 10.899094 < 10.000000)

Your message dated Tue, 17 Jun 2025 07:04:20 + with message-id and subject line Bug#1107826: fixed in coq-elpi 2.5.0-1.1 has caused the Debian Bug report #1107826, regarding coq-elpi FTBFS on riscv64: too slow: 10.899094 < 10.00 to be marked as done. This means that you claim that

Processed: uploaded to sid

) pending. -- 1107826: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1107826 1107829: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1107829 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: Bug#1080671 marked as pending in monajat

Processing control commands: > tag -1 pending Bug #1080671 {Done: أحمد المحمودي } [src:monajat] Missing Build-Depends on python3-setuptools Added tag(s) pending. -- 1080671: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080671 Debian Bug Tracking System Contact ow...@bugs.debian.org w

Bug#1080671: marked as done (Missing Build-Depends on python3-setuptools)

Your message dated Tue, 17 Jun 2025 03:41:53 + with message-id <6850e40133548_3f154ca2c22...@godard.mail> and subject line Bug#1080671 fixed in monajat has caused the Debian Bug report #1080671, regarding Missing Build-Depends on python3-setuptools to be marked as done. This means th

Processed: Bug#1080610 marked as pending in hijra

Processing control commands: > tag -1 pending Bug #1080610 {Done: أحمد المحمودي } [src:hijra] Missing Build-Depends on python3-setuptools Added tag(s) pending. -- 1080610: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080610 Debian Bug Tracking System Contact ow...@bugs.debian.org w

Bug#1080610: marked as done (Missing Build-Depends on python3-setuptools)

Your message dated Tue, 17 Jun 2025 03:39:13 + with message-id <6850e361f10d8_3f154c6bc22...@godard.mail> and subject line Bug#1080610 fixed in hijra has caused the Debian Bug report #1080610, regarding Missing Build-Depends on python3-setuptools to be marked as done. This means th

Bug#1080701: marked as done (Missing Build-Depends on python3-setuptools)

Your message dated Tue, 17 Jun 2025 03:34:30 + with message-id and subject line Bug#1080701: fixed in othman 1.0.0-3 has caused the Debian Bug report #1080701, regarding Missing Build-Depends on python3-setuptools to be marked as done. This means that you claim that the problem has been

Bug#1074591: marked as done (acct: cron job needs wtmpdb last and points it to wtmp file)

Your message dated Tue, 17 Jun 2025 03:04:34 + with message-id and subject line Bug#1074591: fixed in acct 6.6.4-6 has caused the Debian Bug report #1074591, regarding acct: cron job needs wtmpdb last and points it to wtmp file to be marked as done. This means that you claim that the problem

Bug#1106786: marked as done (git ftbfs on s390x (test failures))

Your message dated Tue, 17 Jun 2025 02:34:53 + with message-id and subject line Bug#1106786: fixed in git 1:2.49.0-3 has caused the Debian Bug report #1106786, regarding git ftbfs on s390x (test failures) to be marked as done. This means that you claim that the problem has been dealt with

Bug#1107390: marked as done (golang-1.23: CVE-2025-4673)

Your message dated Tue, 17 Jun 2025 02:38:00 + with message-id and subject line Bug#1107390: fixed in golang-1.23 1.23.10-1 has caused the Debian Bug report #1107390, regarding golang-1.23: CVE-2025-4673 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1106786: marked as done (git ftbfs on s390x (test failures))

Your message dated Tue, 17 Jun 2025 02:35:35 + with message-id and subject line Bug#1106786: fixed in git 1:2.50.0-1 has caused the Debian Bug report #1106786, regarding git ftbfs on s390x (test failures) to be marked as done. This means that you claim that the problem has been dealt with

Bug#1072631: marked as done (r-cran-mockr: autopkgtest regression in testing)

Your message dated Tue, 17 Jun 2025 07:23:20 +0900 with message-id <7827dadd-ee1c-41b1-ae5b-5d3a2b374...@oist.jp> and subject line Re: r-cran-mockr: autopkgtest regression in testing has caused the Debian Bug report #1072631, regarding r-cran-mockr: autopkgtest regression in testing to be

Bug#1102544: marked as done (r-cran-patrick: autopkgtest failure)

Your message dated Tue, 17 Jun 2025 07:25:21 +0900 with message-id <3e5eb1e8-7d1e-4c73-a717-67dab3409...@oist.jp> and subject line Re: r-cran-patrick: autopkgtest failure has caused the Debian Bug report #1102544, regarding r-cran-patrick: autopkgtest failure to be marked as done. This mean

Bug#1107168: marked as done (catdoc: CVE-2024-48877 CVE-2024-52035 CVE-2024-54028)

Your message dated Mon, 16 Jun 2025 16:34:09 + with message-id and subject line Bug#1107168: fixed in catdoc 1:0.95-6 has caused the Debian Bug report #1107168, regarding catdoc: CVE-2024-48877 CVE-2024-52035 CVE-2024-54028 to be marked as done. This means that you claim that the problem has

Processed: globjects: FTBFS: error: ‘gl::BufferAccessMask’ has not been declared,thanks

gi-bin/bugreport.cgi?bug=1090229 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: no help required anymore

g/cgi-bin/bugreport.cgi?bug=979656 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: llvm-toolchain-7: Test suite hangs the autobuilder on single-CPU systems

ttps://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979656 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: llvm-toolchain-6.0: Test suite hangs the autobuilder on single-CPU systems

istance. -- 979655: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979655 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1107782: marked as done (python-jq: FTBFS: E ValueError: jq: error: syntax error, unexpected INVALID_CHARACTER)

Your message dated Mon, 16 Jun 2025 10:50:24 + with message-id and subject line Bug#1107782: fixed in python-jq 1.8.0+dfsg-2 has caused the Debian Bug report #1107782, regarding python-jq: FTBFS: E ValueError: jq: error: syntax error, unexpected INVALID_CHARACTER to be marked as done

Processed: severity of 1107868 is serious

://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1107868 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1107743: marked as done (weasyprint: apt weasyprint install fails with unpack error on libboost1.74-dev:arm64)

Your message dated Mon, 16 Jun 2025 07:32:41 +0200 with message-id and subject line Re: Bug#1107743: weasyprint: apt weasyprint install fails with unpack error on libboost1.74-dev:arm64 has caused the Debian Bug report #1107743, regarding weasyprint: apt weasyprint install fails with unpack

Processed: forcibly merging 1107826 1107829

07826 1107829: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1107829 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1099382: marked as done (python3-datalad: recommends unavailable packages)

Your message dated Sun, 15 Jun 2025 10:49:18 + with message-id and subject line Bug#1099382: fixed in datalad 1.1.5-2.1 has caused the Debian Bug report #1099382, regarding python3-datalad: recommends unavailable packages to be marked as done. This means that you claim that the problem has

Bug#1105210: marked as done (auctex: 'update-auctex-elisp.eperl' creates a tmpfile in the root of filesystem in a dangerous way with $(mktemp ./XXXXXXXX-el))

Your message dated Sun, 15 Jun 2025 10:04:22 + with message-id and subject line Bug#1105210: fixed in auctex 13.2-1.1 has caused the Debian Bug report #1105210, regarding auctex: 'update-auctex-elisp.eperl' creates a tmpfile in the root of filesystem in a dangerous way wit

Processed: severity of 1107817 is important

ant' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 1107817: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1107817 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: tagging 1106122, tagging 1106124

kstart - Depends on unsupported isc-dhcp Added tag(s) trixie-ignore. > thanks Stopping processing here. Please contact me if you need assistance. -- 1106122: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1106122 1106124: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1106124 Debian Bug Tracki

Processed: notfixed 1090361 in debian/550.135-1, severity of 1107347 is normal, closing 1107347

Processing commands for cont...@bugs.debian.org: > notfixed 1090361 debian/550.135-1 Bug #1090361 {Done: Andreas Beckmann } [nvidia-open-kernel-dkms] linux-headers-6.12.5-amd64: aptitude install fail The source debian and version 550.135-1 do not appear to match any binary packages No lon

Processed: Uploaded xfishtank to delayed=10

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

Processed: Re: Bug#1107792: apt: hard Depends on security-unsupported package

Processing control commands: > severity -1 important Bug #1107792 [apt] apt: hard Depends on security-unsupported package Severity set to 'important' from 'serious' > reassign -1 debian-security-support Bug #1107792 [apt] apt: hard Depends on security-unsupported p

Bug#1106805: ydotoold: statically linked against glibc without a Built-Using: field

Hello, I have an ITS/RFS that upgrades the package, and from that point onwards it doesn't link to glibc statically anymore. So I added an extra line mentioning on the changelog [1] Although, that won't fix it for current stable (soon oldstable). I'll try to find out how to branch out specifical

Bug#1100482: marked as done (libunwind-19-dev: Please remove Provides: libunwind-dev)

Your message dated Sat, 14 Jun 2025 21:25:33 +0200 with message-id <6f6dcfdc-64c8-4c40-af7d-5809e3cec...@debian.org> and subject line already done has caused the Debian Bug report #1100482, regarding libunwind-19-dev: Please remove Provides: libunwind-dev to be marked as done. This means th

Processed: block 1095054 with 1107789

054: 1107789 > thanks Stopping processing here. Please contact me if you need assistance. -- 1095054: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1095054 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: block 1102953 with 1107789

thanks Stopping processing here. Please contact me if you need assistance. -- 1102953: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1102953 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1107411: marked as done (powerman: FTBFS: httppower.c:327:5: error: call to '_curl_easy_setopt_err_long' declared with attribute warning: curl_easy_setopt expects a long argument [-Werror=attribut

Your message dated Sat, 14 Jun 2025 17:41:05 + with message-id and subject line Bug#1107411: fixed in powerman 2.4.4-4 has caused the Debian Bug report #1107411, regarding powerman: FTBFS: httppower.c:327:5: error: call to '_curl_easy_setopt_err_long' declared with attribu

Processed: Re: python-jq: FTBFS: E ValueError: jq: error: syntax error, unexpected INVALID_CHARACTER

Processing control commands: > affects -1 jq Bug #1107782 [src:python-jq] python-jq: FTBFS: E ValueError: jq: error: syntax error, unexpected INVALID_CHARACTER Added indication that 1107782 affects jq -- 1107782: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1107782 Debian Bug Track

Processed: Re: Bug#1107773: ocaml: FTBFS on ppc64el: Something failed. Exiting with error status.

Processing control commands: > severity -1 important Bug #1107773 [src:ocaml] ocaml: FTBFS on ppc64el: Something failed. Exiting with error status. Severity set to 'important' from 'serious' -- 1107773: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1107773 Deb

Processed: Re: Bug#1106121: isc-dhcp - EOL and not security supported

Processing control commands: > affects -1 debian-installer Bug #1106121 [src:isc-dhcp] isc-dhcp - EOL and not security supported Added indication that 1106121 affects debian-installer > tags -1 d-i Bug #1106121 [src:isc-dhcp] isc-dhcp - EOL and not security supported Added tag(

Processed: Re: Bug#1106121: isc-dhcp - EOL and not security supported

previously set > tags -1 trixie-ignore Bug #1106121 [src:isc-dhcp] isc-dhcp - EOL and not security supported Added tag(s) trixie-ignore. -- 1106121: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1106121 1107781: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1107781 Debian B

Processed: Re: Bug#1107586: unblock (pre-approval): ocaml/5.3.0-3

cgi?bug=1107586 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1027451: marked as done (libunwind-17-dev: Please remove Provides: libunwind-dev)

Your message dated Sat, 14 Jun 2025 09:48:29 + with message-id and subject line Bug#1027451: fixed in llvm-toolchain-17 1:17.0.6-22 has caused the Debian Bug report #1027451, regarding libunwind-17-dev: Please remove Provides: libunwind-dev to be marked as done. This means that you claim

Processed: Re: Bug#1107743: weasyprint: apt weasyprint install fails with unpack error on libboost1.74-dev:arm64

Processing control commands: > tags -1 moreinfo Bug #1107743 [weasyprint] weasyprint: apt weasyprint install fails with unpack error on libboost1.74-dev:arm64 Added tag(s) moreinfo. -- 1107743: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1107743 Debian Bug Tracking System Contact

Processed: severity of 1107638 is critical

stance. -- 1107638: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1107638 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: gimp: CVE-2025-2760

1 2.10.34-1 Bug #1107758 [src:gimp] gimp: CVE-2025-2760 Marked as found in versions gimp/2.10.34-1. > found -1 3.0.2-3.1 Bug #1107758 [src:gimp] gimp: CVE-2025-2760 Marked as found in versions gimp/3.0.2-3.1. -- 1107758: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1107758 Debian Bug Tra

Processed: numba: FTBFS: Fatal Python error: Segmentation fault

09 [src:python3.13] numba: FTBFS: Fatal Python error: Segmentation fault Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1107409: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1107409 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: auctex: diff for NMU version 13.2-1.1

eport.cgi?bug=1105210 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1105981: marked as done (sensorpro-ble: autopkgtest failure on all archs)

Your message dated Fri, 13 Jun 2025 09:34:07 + with message-id and subject line Bug#1105981: fixed in sensorpro-ble 0.7.1-2 has caused the Debian Bug report #1105981, regarding sensorpro-ble: autopkgtest failure on all archs to be marked as done. This means that you claim that the problem

Bug#1107690: marked as done (initramfs-tools: Initramfs unable to mount rootfs in FCP devices for s390x)

Your message dated Thu, 12 Jun 2025 23:48:56 + with message-id and subject line Bug#1107689: fixed in initramfs-tools 0.148.2 has caused the Debian Bug report #1107689, regarding initramfs-tools: Initramfs unable to mount rootfs in FCP devices for s390x to be marked as done. This means that

Bug#1107689: marked as done (initramfs-tools - lost zfcp module, unbootable s390x systems)

Your message dated Thu, 12 Jun 2025 23:48:56 + with message-id and subject line Bug#1107689: fixed in initramfs-tools 0.148.2 has caused the Debian Bug report #1107689, regarding initramfs-tools - lost zfcp module, unbootable s390x systems to be marked as done. This means that you claim that

Bug#1107689: marked as done (initramfs-tools - lost zfcp module, unbootable s390x systems)

Your message dated Thu, 12 Jun 2025 23:04:16 + with message-id and subject line Bug#1107689: fixed in initramfs-tools 0.149 has caused the Debian Bug report #1107689, regarding initramfs-tools - lost zfcp module, unbootable s390x systems to be marked as done. This means that you claim that

Bug#1107690: marked as done (initramfs-tools: Initramfs unable to mount rootfs in FCP devices for s390x)

Your message dated Thu, 12 Jun 2025 23:04:16 + with message-id and subject line Bug#1107689: fixed in initramfs-tools 0.149 has caused the Debian Bug report #1107689, regarding initramfs-tools: Initramfs unable to mount rootfs in FCP devices for s390x to be marked as done. This means that

Bug#1107691: marked as done (RM: hwloc-contrib [ppc64el] -- ROM; NVIDIA has discontinued ppc64el driver support)

Your message dated Thu, 12 Jun 2025 18:03:53 + with message-id and subject line Bug#1107691: Removed package(s) from unstable has caused the Debian Bug report #1107691, regarding RM: hwloc-contrib [ppc64el] -- ROM; NVIDIA has discontinued ppc64el driver support to be marked as done. This

Processed: [bts-link] source package src:golang-1.23

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:golang-1.23 > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # >

Processed: Re: Bug#1051785: workaround

is plugged' from 'gdm3 won't allow logins when a smarcard with a x.509 credential is plugged in'. > severity -1 serious Bug #1051785 [gdm3] gdm3 won't allow logins when a smartcard/yubikey is plugged Severity set to 'serious' from 'important' -- 10

Bug#1103008: marked as done (ocaml: FTBFS on arm64: test_dropped_events.ml flaky)

Your message dated Thu, 12 Jun 2025 12:20:09 + with message-id and subject line Bug#1103008: fixed in ocaml 5.3.0-3 has caused the Debian Bug report #1103008, regarding ocaml: FTBFS on arm64: test_dropped_events.ml flaky to be marked as done. This means that you claim that the problem has

Processed: Re: Bug#1104178: dh-elpa-helper: upgrade fails: cannot overwrite non-directory ... with directory

Processing control commands: > severity -1 important Bug #1104178 [dh-elpa-helper] dh-elpa-helper: upgrade fails: cannot overwrite non-directory ... with directory Severity set to 'important' from 'grave' -- 1104178: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1104

Bug#1069117: marked as done (python3-evtx: evtx_filter_records.py fails to run)

Your message dated Thu, 12 Jun 2025 11:21:10 + with message-id and subject line Bug#1069117: fixed in python-evtx 0.7.4-1.1 has caused the Debian Bug report #1069117, regarding python3-evtx: evtx_filter_records.py fails to run to be marked as done. This means that you claim that the problem

Bug#1066183: marked as done (mate-equake-applet FTBFS due to -Werror=implicit-function-declaration)

Your message dated Thu, 12 Jun 2025 10:52:19 + with message-id and subject line Bug#1066183: fixed in mate-equake-applet 1.3.8.2-2 has caused the Debian Bug report #1066183, regarding mate-equake-applet FTBFS due to -Werror=implicit-function-declaration to be marked as done. This means that

Processed: Re 1100699 security issues

Processing control commands: > tags -1 trixie-ignore Bug #1100699 [screen] screen: hardcopy and screen-exchange are insecure by default Added tag(s) trixie-ignore. -- 1100699: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1100699 Debian Bug Tracking System Contact ow...@bugs.debian.

Bug#1107617: marked as done (libtpms: CVE-2025-49133: Fix potential out-of-bound access & abort due to HMAC signing issue)

Your message dated Thu, 12 Jun 2025 08:34:03 + with message-id and subject line Bug#1107617: fixed in libtpms 0.9.2-3.2 has caused the Debian Bug report #1107617, regarding libtpms: CVE-2025-49133: Fix potential out-of-bound access & abort due to HMAC signing issue to be marked as

Processed: libutf8.h-dev and libutfcpp-dev have an undeclared file conflict on /usr/include/utf8

Processing control commands: > tags -1 patch Bug #1102709 [libutf8.h-dev,libutfcpp-dev] libutf8.h-dev and libutfcpp-dev have an undeclared file conflict on /usr/include/utf8 Added tag(s) patch. -- 1102709: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1102709 Debian Bug Tracking Sys

Processed: libtpms: CVE-2025-49133: Fix potential out-of-bound access & abort due to HMAC signing issue

Processing control commands: > tags -1 patch Bug #1107617 [src:libtpms] libtpms: CVE-2025-49133: Fix potential out-of-bound access & abort due to HMAC signing issue Added tag(s) patch. -- 1107617: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1107617 Debian Bug Tracking System Con

Processed: forcibly merging 1107689 1107690

g processing here. Please contact me if you need assistance. -- 1107689: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1107689 1107690: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1107690 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed (with 2 errors): Re: Bug#1107691: RM: hwloc-contrib [ppc64el] -- ROM; NVIDIA has discontinued ppc64el driver support

e stop building on ppc64el'. > user ftp.debian@packages.debian.org , usertags -1 + remove Unknown command or malformed arguments to command. > user debian-powe...@lists.debian.org , usertags -1 ppc64el Unknown command or malformed arguments to command. -- 1107691: https://bugs.debian.org/cg

Processed: bug 1107689 is forwarded to https://salsa.debian.org/kernel-team/initramfs-tools/-/merge_requests/175

t; thanks Stopping processing here. Please contact me if you need assistance. -- 1107689: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1107689 1107690: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1107690 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: severity is RC

Processing control commands: > severity -1 serious Bug #1107643 {Done: Gianfranco Costamagna } [libserial1] libserial1: Breaking ABI change Severity set to 'serious' from 'normal' -- 1107643: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1107643 Debian Bug Tra

Bug#984810: marked as done (courier-authlib: CVE-2021-28374: /run/courier/authdaemon directory with weak permissions)

Your message dated Wed, 11 Jun 2025 15:40:45 -0700 with message-id <4862509.1oUyQt6lIG@soren-desktop> and subject line courier-authlib: CVE-2021-28374: /run/courier/authdaemon directory with weak permissions has caused the Debian Bug report #984810, regarding courier-authlib: CVE-2021-28374

Bug#1107195: marked as done (python-signxml: CVE-2025-48994 CVE-2025-48995)

Your message dated Wed, 11 Jun 2025 22:34:36 + with message-id and subject line Bug#1107195: fixed in python-signxml 4.0.5+dfsg-1 has caused the Debian Bug report #1107195, regarding python-signxml: CVE-2025-48994 CVE-2025-48995 to be marked as done. This means that you claim that the

Bug#1084293: marked as done (mariadb: FTBFS: Failing test(s): main.timezone)

Your message dated Wed, 11 Jun 2025 18:47:10 + with message-id and subject line Bug#1084293: fixed in mariadb 1:10.11.13-0+deb12u1 has caused the Debian Bug report #1084293, regarding mariadb: FTBFS: Failing test(s): main.timezone to be marked as done. This means that you claim that the

Bug#1107651: marked as done (lomiri-mediaplayer-app: FTBFS on s390x)

Your message dated Wed, 11 Jun 2025 21:38:01 + with message-id and subject line Bug#1107651: fixed in lomiri-mediaplayer-app 1.1.1+dfsg-2 has caused the Debian Bug report #1107651, regarding lomiri-mediaplayer-app: FTBFS on s390x to be marked as done. This means that you claim that the

Bug#1104076: marked as done (nvidia-open-gpu-kernel-modules: CVE-2025-23244)

Your message dated Wed, 11 Jun 2025 21:07:32 + with message-id and subject line Bug#1104076: fixed in nvidia-open-gpu-kernel-modules 550.163.01-1 has caused the Debian Bug report #1104076, regarding nvidia-open-gpu-kernel-modules: CVE-2025-23244 to be marked as done. This means that you

Bug#1104068: marked as done (nvidia-graphics-drivers: CVE-2025-23244)

Your message dated Wed, 11 Jun 2025 21:07:03 + with message-id and subject line Bug#1104068: fixed in nvidia-graphics-drivers 550.163.01-1 has caused the Debian Bug report #1104068, regarding nvidia-graphics-drivers: CVE-2025-23244 to be marked as done. This means that you claim that the

Bug#1101831: marked as done (mariadb: autopkgtest regression in testing)

Your message dated Wed, 11 Jun 2025 18:47:10 + with message-id and subject line Bug#1084293: fixed in mariadb 1:10.11.13-0+deb12u1 has caused the Debian Bug report #1084293, regarding mariadb: autopkgtest regression in testing to be marked as done. This means that you claim that the problem

Processed: konsole: CVE-2025-49091

ccorso } [src:konsole] konsole: CVE-2025-49091 Marked as found in versions konsole/4:22.12.3-1. -- 1107672: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1107672 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1107196: marked as done (modsecurity-apache: CVE-2025-48866)

Your message dated Wed, 11 Jun 2025 18:47:11 + with message-id and subject line Bug#1107196: fixed in modsecurity-apache 2.9.7-1+deb12u1 has caused the Debian Bug report #1107196, regarding modsecurity-apache: CVE-2025-48866 to be marked as done. This means that you claim that the problem

Bug#1106286: marked as done (modsecurity-apache: CVE-2025-47947)

Your message dated Wed, 11 Jun 2025 18:47:11 + with message-id and subject line Bug#1106286: fixed in modsecurity-apache 2.9.7-1+deb12u1 has caused the Debian Bug report #1106286, regarding modsecurity-apache: CVE-2025-47947 to be marked as done. This means that you claim that the problem

Processed: Re: Bug#486914: Default: spamd runs as root (uid/gid 0)

curity. -- 486914: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=486914 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#486914: Default: spamd runs as root (uid/gid 0)

Processing control commands: > severity -1 wishlist Bug #486914 [spamassassin] Default: spamd runs as root (uid/gid 0) Severity set to 'wishlist' from 'serious' -- 486914: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=486914 Debian Bug Tracking System Contact ow.

Bug#1107431: marked as done (src:bluetooth-sensor-state-data: fails to migrate to testing for too long)

Your message dated Wed, 11 Jun 2025 12:33:58 + with message-id and subject line Bug#1107431: fixed in bluetooth-sensor-state-data 1.9.0-2 has caused the Debian Bug report #1107431, regarding src:bluetooth-sensor-state-data: fails to migrate to testing for too long to be marked as done. This

Processed: Re: Bug#486914: Default: spamd runs as root (uid/gid 0)

Processing control commands: > found -1 4.0.1-1~deb12u1 Bug #486914 [spamassassin] Default: spamd runs as root (uid/gid 0) Marked as found in versions spamassassin/4.0.1-1~deb12u1. -- 486914: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=486914 Debian Bug Tracking System Contact

Processed: tagging 1107451

g here. Please contact me if you need assistance. -- 1107451: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1107451 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: libsynthesis: depends on obsolete pcre3 library

Processing control commands: > tags -1 patch Bug #147 [src:libsynthesis] libsynthesis: depends on obsolete pcre3 library Ignoring request to alter tags of bug #147 to the same tags previously set -- 147: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=147 Debian Bug Track

Processed: Re: pytorch-cuda: FTBFS: ld.lld: error: undefined reference: std::ios_base_library_init()@GLIBCXX_3.4.32

g processing here. Please contact me if you need assistance. -- 1105066: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1105066 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#1102947: munge FTBFS failure

rious' > tags -1 trixie-ignore Bug #1102947 [src:munge] munge: FTBFS in testing: sed: can't read /tmp/munge-test-16284/trash directory.0110-munged-origin-addr/log-25689/munged.log.25689: No such file or directory Added tag(s) trixie-ignore. -- 1102947: https://bugs.debian.org/cgi-

Bug#1082053: marked as done (RUSTSEC-2023-0086)

Your message dated Wed, 11 Jun 2025 08:07:24 + with message-id and subject line Bug#1082053: fixed in rust-lexical-core 1.0.5-1 has caused the Debian Bug report #1082053, regarding RUSTSEC-2023-0086 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#1103003: marked as done (gcc-mingw-w64-ucrt64: broken on arm64, libgcc.a can't be linked)

Your message dated Wed, 11 Jun 2025 09:27:26 +0200 with message-id and subject line Re: gdb-mingw-w64: FTBFS in testing/arm64: configure: error: in `/build/reproducible-path/gdb-mingw-w64-13.2/build-gdbserver/x86_64-w64-mingw32ucrt/gnulib' has caused the Debian Bug report #1103003, rega

Bug#1103007: marked as done (gcc-mingw-w64-ucrt64: broken on arm64, libgcc.a can't be linked)

Your message dated Wed, 11 Jun 2025 09:27:26 +0200 with message-id and subject line Re: gdb-mingw-w64: FTBFS in testing/arm64: configure: error: in `/build/reproducible-path/gdb-mingw-w64-13.2/build-gdbserver/x86_64-w64-mingw32ucrt/gnulib' has caused the Debian Bug report #1103003, rega

Processed: Re: Bug#1107523: release.debian.org: Can i386-only bugs be release-critical?

Processing control commands: > severity -1 serious Bug #1104317 [wine] winedbg recursively forks until the memory is exhausted Severity set to 'serious' from 'important' -- 1104317: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1104317 Debian Bug Tra

Processed: re: lwn4chrome: does not work with Chromium >= 136

Processing control commands: > severity -1 important Bug #1106453 [lwn4chrome] lwn4chrome: does not work with Chromium >= 136 Severity set to 'important' from 'grave' -- 1106453: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1106453 Debian Bug Tracking System Con

Bug#1104898: marked as done (apps fail to start with "XIO: fatal IO error 9 (Bad file descriptor) on X server" when using DXVK)

Your message dated Wed, 11 Jun 2025 00:05:48 + with message-id and subject line Bug#1104898: fixed in wine 10.0~repack-5 has caused the Debian Bug report #1104898, regarding apps fail to start with "XIO: fatal IO error 9 (Bad file descriptor) on X server" when using DXVK to be

Processed: your mail

ocessing here. Please contact me if you need assistance. -- 1104898: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1104898 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: python-django: Incomplete mitigation for CVE-2025-48432

Processing control commands: > fixed -1 3:4.2.23-1 Bug #1107616 [src:python-django] python-django: Incomplete mitigation for CVE-2025-48432 Marked as fixed in versions python-django/3:4.2.23-1. -- 1107616: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1107616 Debian Bug Tracking Sys

Processed: closing 1107616

hon-django: Incomplete mitigation for CVE-2025-48432 Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1107616: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1107616 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: fixed 1090361 in nvidia-open-gpu-kernel-modules/550.135-1

5-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1090361: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1090361 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1107410: marked as done (python-covdefaults: FTBFS: E AttributeError: type object 'Plugins' has no attribute 'load_plugins')

Your message dated Tue, 10 Jun 2025 17:39:04 + with message-id and subject line Bug#1107410: fixed in python-covdefaults 2.3.0-3 has caused the Debian Bug report #1107410, regarding python-covdefaults: FTBFS: E AttributeError: type object 'Plugins' has no attribute 'load

Bug#1107304: marked as done (pdfarranger: Fails to start: RuntimeError: context has already been set)

Your message dated Tue, 10 Jun 2025 17:09:44 + with message-id and subject line Bug#1107304: fixed in pdfarranger 1.11.1-3 has caused the Debian Bug report #1107304, regarding pdfarranger: Fails to start: RuntimeError: context has already been set to be marked as done. This means that you

Processed: Bug#1107304 marked as pending in pdfarranger

Processing control commands: > tag -1 pending Bug #1107304 [pdfarranger] pdfarranger: Fails to start: RuntimeError: context has already been set Added tag(s) pending. -- 1107304: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1107304 Debian Bug Tracking System Contact ow...@bugs.debian.

Bug#1107515: marked as done (wireshark: CVE-2025-5601)

Your message dated Tue, 10 Jun 2025 16:36:00 + with message-id and subject line Bug#1107515: fixed in wireshark 4.4.7-1 has caused the Debian Bug report #1107515, regarding wireshark: CVE-2025-5601 to be marked as done. This means that you claim that the problem has been dealt with. If this

  1   2   3   4   5   6   7   8   9   10   >