Bug#1106979: marked as done (frr: add libcrypt-dev to Build-Depends)

2025-05-31 Thread Debian Bug Tracking System
Your message dated Sun, 01 Jun 2025 05:49:31 + with message-id and subject line Bug#1106979: fixed in frr 10.3-5 has caused the Debian Bug report #1106979, regarding frr: add libcrypt-dev to Build-Depends to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1104540: marked as done (gnupg2: [INTL:nl] Dutch translation for the gnupg2 package)

2025-05-31 Thread Debian Bug Tracking System
Your message dated Sun, 01 Jun 2025 05:19:09 + with message-id and subject line Bug#1104540: fixed in gnupg2 2.4.7-21 has caused the Debian Bug report #1104540, regarding gnupg2: [INTL:nl] Dutch translation for the gnupg2 package to be marked as done. This means that you claim that the proble

Bug#1104758: marked as done (freetds: FTBFS on armel, armhf, mips64el: FAIL: convert_bounds)

2025-05-31 Thread Debian Bug Tracking System
Your message dated Sun, 01 Jun 2025 03:48:59 + with message-id and subject line Bug#1104758: fixed in freetds 1.5.1+ds-3 has caused the Debian Bug report #1104758, regarding freetds: FTBFS on armel, armhf, mips64el: FAIL: convert_bounds to be marked as done. This means that you claim that the

Processed: Re: Bug#1105903: mate clock crashes on attempt to add a location

2025-05-31 Thread Debian Bug Tracking System
Processing control commands: > close -1 Bug #1105903 [mate-panel] mate clock crashes on attempt to add a location Marked Bug as done -- 1105903: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1105903 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1106940: marked as done (libmath-random-perl: add libcrypt-dev to Build-Depends)

2025-05-31 Thread Debian Bug Tracking System
Your message dated Sun, 01 Jun 2025 00:49:06 + with message-id and subject line Bug#1106940: fixed in libmath-random-perl 0.72-3 has caused the Debian Bug report #1106940, regarding libmath-random-perl: add libcrypt-dev to Build-Depends to be marked as done. This means that you claim that the

Bug#1106513: marked as done (routine-update: --64 / ONLY_64_BITS should also amend existings debian/salsa-ci.yml)

2025-05-31 Thread Debian Bug Tracking System
Your message dated Sun, 1 Jun 2025 08:14:19 +0900 with message-id and subject line Re: [Debian-med-packaging] Bug#1106513: routine-update: --64 / ONLY_64_BITS should also amend existings debian/salsa-ci.yml has caused the Debian Bug report #1106513, regarding routine-update: --64 / ONLY_64_BITS s

Bug#1106145: marked as done (AppStream metadata still missing for pidgin-otr because of a typo)

2025-05-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 May 2025 22:50:38 + with message-id and subject line Bug#1106145: fixed in pidgin-otr 4.0.2-5 has caused the Debian Bug report #1106145, regarding AppStream metadata still missing for pidgin-otr because of a typo to be marked as done. This means that you claim that

Bug#1106145: marked as done (AppStream metadata still missing for pidgin-otr because of a typo)

2025-05-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 May 2025 23:04:45 + with message-id and subject line Bug#1106145: fixed in pidgin-otr 4.0.2-6 has caused the Debian Bug report #1106145, regarding AppStream metadata still missing for pidgin-otr because of a typo to be marked as done. This means that you claim that

Bug#1105792: marked as done (logcheck: Exim print panic since upgrade and messages appear twice)

2025-05-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 May 2025 22:36:54 + with message-id and subject line Bug#1105792: fixed in logcheck 1.4.5 has caused the Debian Bug report #1105792, regarding logcheck: Exim print panic since upgrade and messages appear twice to be marked as done. This means that you claim that the

Bug#1106030: marked as done (logcheck: mails from the systemd timer are delayed by up to 30 mins)

2025-05-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 May 2025 22:36:54 + with message-id and subject line Bug#1106030: fixed in logcheck 1.4.5 has caused the Debian Bug report #1106030, regarding logcheck: mails from the systemd timer are delayed by up to 30 mins to be marked as done. This means that you claim that th

Bug#1106667: marked as done (logcheck: apparently uses systemd rather than cron, but it is undocumented)

2025-05-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 May 2025 22:36:54 + with message-id and subject line Bug#1106667: fixed in logcheck 1.4.5 has caused the Debian Bug report #1106667, regarding logcheck: apparently uses systemd rather than cron, but it is undocumented to be marked as done. This means that you claim

Bug#1078901: marked as done (nvda2speechd: FTBFS: error: failed to select a version for the requirement `rmp-serde = "=1.1.0"`)

2025-05-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 May 2025 21:32:15 + with message-id and subject line Bug#1078901: fixed in nvda2speechd 0.1-6+deb12u1 has caused the Debian Bug report #1078901, regarding nvda2speechd: FTBFS: error: failed to select a version for the requirement `rmp-serde = "=1.1.0"` to be marked

Bug#1100595: marked as done (simplesamlphp: CVE-2025-27773)

2025-05-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 May 2025 21:32:18 + with message-id and subject line Bug#1100595: fixed in simplesamlphp 1.19.7-1+deb12u2 has caused the Debian Bug report #1100595, regarding simplesamlphp: CVE-2025-27773 to be marked as done. This means that you claim that the problem has been dea

Bug#1103525: marked as done (krb5: CVE-2025-3576)

2025-05-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 May 2025 21:32:13 + with message-id and subject line Bug#1103525: fixed in krb5 1.20.1-2+deb12u4 has caused the Debian Bug report #1103525, regarding krb5: CVE-2025-3576 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#1103780: marked as done (webpy: CVE-2025-3818)

2025-05-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 May 2025 21:32:31 + with message-id and subject line Bug#1103780: fixed in webpy 1:0.62-4+deb12u1 has caused the Debian Bug report #1103780, regarding webpy: CVE-2025-3818 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#1105896: marked as done (insighttoolkit5: FTBFS: Test itkOptImageToImageMetricsTest04 fails on single-cpu systems)

2025-05-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 May 2025 21:32:10 + with message-id and subject line Bug#1105896: fixed in insighttoolkit4 4.13.3withdata-dfsg2-4+deb12u1 has caused the Debian Bug report #1105896, regarding insighttoolkit5: FTBFS: Test itkOptImageToImageMetricsTest04 fails on single-cpu systems t

Bug#1105896: marked as done (insighttoolkit5: FTBFS: Test itkOptImageToImageMetricsTest04 fails on single-cpu systems)

2025-05-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 May 2025 21:32:11 + with message-id and subject line Bug#1105896: fixed in insighttoolkit5 5.2.1-5+deb12u1 has caused the Debian Bug report #1105896, regarding insighttoolkit5: FTBFS: Test itkOptImageToImageMetricsTest04 fails on single-cpu systems to be marked as d

Bug#1101745: marked as done (libbpf: segmentation fault with 1.1.0-1 (bookworm))

2025-05-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 May 2025 21:32:13 + with message-id and subject line Bug#1101745: fixed in libbpf 1.1.2-0+deb12u1 has caused the Debian Bug report #1101745, regarding libbpf: segmentation fault with 1.1.0-1 (bookworm) to be marked as done. This means that you claim that the problem

Bug#1106847: marked as done (debvm: autopkgtest failure as debefivm uses the systemd stub binary without a package dependency)

2025-05-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 May 2025 20:35:53 + with message-id and subject line Bug#1106847: fixed in debvm 0.4.3 has caused the Debian Bug report #1106847, regarding debvm: autopkgtest failure as debefivm uses the systemd stub binary without a package dependency to be marked as done. This m

Bug#1107007: marked as done (tightvnc: add libcrypt-dev to Build-Depends)

2025-05-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 May 2025 22:11:30 +0200 with message-id <20250531201130.ga3113...@subdivi.de> and subject line Re: Bug#1107007: tightvnc: add libcrypt-dev to Build-Depends has caused the Debian Bug report #1107007, regarding tightvnc: add libcrypt-dev to Build-Depends to be marked as don

Bug#1106992: marked as done (libnetconf2: add libcrypt-dev to Build-Depends)

2025-05-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 May 2025 19:49:01 + with message-id and subject line Bug#1106992: fixed in libnetconf2 3.7.1-2 has caused the Debian Bug report #1106992, regarding libnetconf2: add libcrypt-dev to Build-Depends to be marked as done. This means that you claim that the problem has be

Processed: forcibly merging 1106289 1106874

2025-05-31 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forcemerge 1106289 1106874 Bug #1106289 {Done: ChangZhuo Chen (陳昌倬) } [src:jq] jq: CVE-2024-23337 Bug #1106874 [src:jq] jq: CVE-2024-23337 (jq-1.6-2.1) Set Bug forwarded-to-address to 'https://github.com/jqlang/jq/issues/3262'. Severity set to 'i

Bug#1106427: marked as done (matplotlib: FTBFS: TypeError: 'int' object is not iterable)

2025-05-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 May 2025 19:08:12 + with message-id and subject line Bug#1106427: fixed in matplotlib 3.10.1+dfsg1-4 has caused the Debian Bug report #1106427, regarding matplotlib: FTBFS: TypeError: 'int' object is not iterable to be marked as done. This means that you claim that

Bug#1106809: marked as done (tsocks: statically linked against glibc without a Built-Using: field)

2025-05-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 May 2025 17:37:35 + with message-id and subject line Bug#1106809: fixed in tsocks 1.8beta5+ds1-3 has caused the Debian Bug report #1106809, regarding tsocks: statically linked against glibc without a Built-Using: field to be marked as done. This means that you claim

Bug#1024269: marked as done (btrfs-progs: Different sizes reported for "btrfs replace /dev/sda2" abd "btrfs replace 2")

2025-05-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 May 2025 13:00:05 -0400 with message-id <87wm9wzpey@navis.mail-host-address-is-not-set> and subject line Re: Bug#1024269: btrfs-progs: Different sizes reported for "btrfs replace /dev/sda2" abd "btrfs replace 2" has caused the Debian Bug report #1024269, regarding bt

Bug#1106789: marked as done (nmu: multiple binNMUs against glibc (>= 2.39) for CVE-2025-4802)

2025-05-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 May 2025 18:53:42 +0200 with message-id and subject line Re: Bug#1106789: nmu: multiple binNMUs against glibc (>= 2.39) for CVE-2025-4802 has caused the Debian Bug report #1106789, regarding nmu: multiple binNMUs against glibc (>= 2.39) for CVE-2025-4802 to be marked as

Bug#1106891: marked as done (unblock: gnupg2/2.4.7-19)

2025-05-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 May 2025 16:33:12 +0200 with message-id and subject line Re: Bug#1106891: unblock: gnupg2/2.4.7-19 has caused the Debian Bug report #1106891, regarding unblock: gnupg2/2.4.7-19 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#1106303: marked as done (openjdk-25: FTBFS in testing: build-dependency not installable: openjdk-24-jdk-headless)

2025-05-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 May 2025 13:41:37 + with message-id and subject line Bug#1106303: fixed in openjdk-25 25~25ea-1 has caused the Debian Bug report #1106303, regarding openjdk-25: FTBFS in testing: build-dependency not installable: openjdk-24-jdk-headless to be marked as done. This m

Bug#1106800: marked as done (gpgv-static: statically linked against glibc without a Built-Using: field)

2025-05-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 May 2025 11:19:13 + with message-id and subject line Bug#1106800: fixed in gnupg2 2.4.7-20 has caused the Debian Bug report #1106800, regarding gpgv-static: statically linked against glibc without a Built-Using: field to be marked as done. This means that you claim

Processed: Re: distribution-gpg-keys: rename package to distribution-pgp-keys

2025-05-31 Thread Debian Bug Tracking System
Processing control commands: > tags -1 wontfix Bug #1106390 [src:distribution-gpg-keys] distribution-gpg-keys: rename package to distribution-pgp-keys Added tag(s) wontfix. > close -1 Bug #1106390 [src:distribution-gpg-keys] distribution-gpg-keys: rename package to distribution-pgp-keys Marked B

Bug#1088105: marked as done (python-scipy-doc: Broken style)

2025-05-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 May 2025 11:37:56 +0200 with message-id and subject line Re: Bug#1088105: python-scipy-doc: Broken style has caused the Debian Bug report #1088105, regarding python-scipy-doc: Broken style to be marked as done. This means that you claim that the problem has been dealt w