Bug#1106684: marked as done (icu: CVE-2025-5222: Stack buffer overflow in the SRBRoot::addTag function)

2025-05-30 Thread Debian Bug Tracking System
Your message dated Sat, 31 May 2025 06:04:59 + with message-id and subject line Bug#1106684: fixed in icu 76.1-4 has caused the Debian Bug report #1106684, regarding icu: CVE-2025-5222: Stack buffer overflow in the SRBRoot::addTag function to be marked as done. This means that you claim that

Bug#1106163: marked as done (unblock: falkon/25.04.1-1)

2025-05-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 May 2025 22:28:10 + with message-id and subject line unblock falkon has caused the Debian Bug report #1106163, regarding unblock: falkon/25.04.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

Bug#1106870: marked as done (bugs.debian.org: Background noise from the sound system for no reason after the last update)

2025-05-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 May 2025 17:11:44 -0700 with message-id and subject line Re: Bug#1106870: False bug sorry! has caused the Debian Bug report #1106870, regarding bugs.debian.org: Background noise from the sound system for no reason after the last update to be marked as done. This means

Bug#1106839: marked as done (unblock: widelands/2:1.2.1-3)

2025-05-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 May 2025 22:32:42 + with message-id and subject line unblock widelands has caused the Debian Bug report #1106839, regarding unblock: widelands/2:1.2.1-3 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#1106779: marked as done (gpg: "No good signature" when doing `apt- update`)

2025-05-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 May 2025 18:34:02 -0400 with message-id and subject line Re: [Pkg-rust-maintainers] Bug#1106779: gpg: "No good signature" when doing `apt- update` has caused the Debian Bug report #1106779, regarding gpg: "No good signature" when doing `apt- update` to be marked as done

Bug#1106815: marked as done (unblock: mozjs128/128.11.0-1)

2025-05-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 May 2025 22:35:00 + with message-id and subject line unblock mozjs128 has caused the Debian Bug report #1106815, regarding unblock: mozjs128/128.11.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 i

Bug#1106842: marked as done (unblock: catatonit/0.2.1-2)

2025-05-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 May 2025 22:33:16 + with message-id and subject line unblock catatonit has caused the Debian Bug report #1106842, regarding unblock: catatonit/0.2.1-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

Bug#1106843: marked as done (unblock: tktray/1.3.9-6)

2025-05-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 May 2025 22:32:11 + with message-id and subject line unblock tktray has caused the Debian Bug report #1106843, regarding unblock: tktray/1.3.9-6 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 y

Bug#1106840: marked as done (unblock: tkcon/2:2.7.11-6)

2025-05-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 May 2025 22:31:54 + with message-id and subject line unblock tkcon has caused the Debian Bug report #1106840, regarding unblock: tkcon/2:2.7.11-6 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#1106838: marked as done (unblock: tclx8.4/8.4.1-5)

2025-05-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 May 2025 22:30:39 + with message-id and subject line unblock tclx8.4 has caused the Debian Bug report #1106838, regarding unblock: tclx8.4/8.4.1-5 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#956102: marked as done (desktop-base: unwanted metadata within images)

2025-05-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 May 2025 21:49:00 + with message-id and subject line Bug#956102: fixed in desktop-base 13.0.3 has caused the Debian Bug report #956102, regarding desktop-base: unwanted metadata within images to be marked as done. This means that you claim that the problem has been

Bug#1074356: marked as done (Please take potrait mode of phones into account for trixie)

2025-05-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 May 2025 21:49:00 + with message-id and subject line Bug#1074356: fixed in desktop-base 13.0.3 has caused the Debian Bug report #1074356, regarding Please take potrait mode of phones into account for trixie to be marked as done. This means that you claim that the pr

Bug#1095314: marked as done (Unused files wasting space)

2025-05-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 May 2025 21:49:00 + with message-id and subject line Bug#1095314: fixed in desktop-base 13.0.3 has caused the Debian Bug report #1095314, regarding Unused files wasting space to be marked as done. This means that you claim that the problem has been dealt with. If th

Bug#1104776: marked as done (qt-style-kvantum has a file conflict)

2025-05-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 May 2025 23:01:40 +0200 with message-id and subject line has caused the Debian Bug report #1104776, regarding qt-style-kvantum has a file conflict 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 y

Bug#1105850: marked as done (/usr/share/doc/libxdamage1/changelog.gz: version of libxdamage1:loong64 doesn't match the one of amd64)

2025-05-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 May 2025 23:01:04 +0200 with message-id and subject line Re: Bug#1105850: /usr/share/doc/libxdamage1/changelog.gz: version of libxdamage1:loong64 doesn't match the one of amd64 has caused the Debian Bug report #1105850, regarding /usr/share/doc/libxdamage1/changelog.gz:

Bug#1103427: marked as done (pymatgen: autopkgtest regression: exit code 5)

2025-05-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 May 2025 22:47:11 +0200 with message-id and subject line Re: pymatgen: autopkgtest regression: exit code 5 has caused the Debian Bug report #1103427, regarding pymatgen: autopkgtest regression: exit code 5 to be marked as done. This means that you claim that the problem

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

2025-05-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 May 2025 19:51:22 + with message-id and subject line Bug#1106807: fixed in tini 0.19.0-3 has caused the Debian Bug report #1106807, regarding tini: statically linked against glibc without a Built-Using: field to be marked as done. This means that you claim that the

Bug#1106147: marked as done (net-tools: empty packet counters with latest update)

2025-05-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 May 2025 19:48:36 + with message-id and subject line Bug#1106147: fixed in net-tools 2.10-0.1+deb12u2 has caused the Debian Bug report #1106147, regarding net-tools: empty packet counters with latest update to be marked as done. This means that you claim that the pr

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

2025-05-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 May 2025 19:48:29 + with message-id and subject line Bug#1106689: fixed in libvpx 1.12.0-1+deb12u4 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 h

Bug#1105885: marked as done (libavif: CVE-2025-48174)

2025-05-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 May 2025 19:48:22 + with message-id and subject line Bug#1105885: fixed in libavif 0.11.1-1+deb12u1 has caused the Debian Bug report #1105885, regarding libavif: CVE-2025-48174 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1105883: marked as done (libavif: CVE-2025-48175)

2025-05-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 May 2025 19:48:22 + with message-id and subject line Bug#1105883: fixed in libavif 0.11.1-1+deb12u1 has caused the Debian Bug report #1105883, regarding libavif: CVE-2025-48175 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1104872: marked as done (python-django: CVE-2025-32873 -- Denial-of-service possibility in strip_tags())

2025-05-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 May 2025 18:21:31 + with message-id and subject line Bug#1104872: fixed in python-django 3:5.2.1-1 has caused the Debian Bug report #1104872, regarding python-django: CVE-2025-32873 -- Denial-of-service possibility in strip_tags() to be marked as done. This means t

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

2025-05-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 May 2025 17:49:35 + with message-id and subject line Bug#1106796: fixed in busybox 1:1.37.0-5 has caused the Debian Bug report #1106796, regarding busybox-static: statically linked against glibc without a Built-Using: field to be marked as done. This means that you

Bug#1099569: marked as done (Please provide a better package description)

2025-05-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 May 2025 16:49:38 + with message-id and subject line Bug#1099569: fixed in rust-sequoia-sqv 1.3.0-3 has caused the Debian Bug report #1099569, regarding Please provide a better package description to be marked as done. This means that you claim that the problem has

Bug#1106841: marked as done (normalize-audio randomly produces garbage values)

2025-05-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 May 2025 16:20:21 + with message-id and subject line Bug#1106841: fixed in normalize-audio 0.7.7-20 has caused the Debian Bug report #1106841, regarding normalize-audio randomly produces garbage values to be marked as done. This means that you claim that the problem

Bug#1106810: marked as done (unblock: babl/1:0.1.114-2)

2025-05-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 May 2025 12:46:20 + with message-id and subject line unblock babl has caused the Debian Bug report #1106810, regarding unblock: babl/1:0.1.114-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 y

Bug#1106849: marked as done (In privacy mode (where no EXIF data is stored in images) the orientation is not saved.)

2025-05-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 May 2025 14:34:16 + with message-id and subject line Bug#1106849: fixed in lomiri-camera-app 4.0.8+dfsg-4 has caused the Debian Bug report #1106849, regarding In privacy mode (where no EXIF data is stored in images) the orientation is not saved. to be marked as done

Bug#1106850: marked as done (AdvancedOptions.qml: Typo in theme palette name.)

2025-05-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 May 2025 14:34:16 + with message-id and subject line Bug#1106850: fixed in lomiri-camera-app 4.0.8+dfsg-4 has caused the Debian Bug report #1106850, regarding AdvancedOptions.qml: Typo in theme palette name. to be marked as done. This means that you claim that the p

Bug#1105112: marked as done (lomiri-camera-app: image quality on app startup not initialized properly)

2025-05-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 May 2025 14:34:16 + with message-id and subject line Bug#1105112: fixed in lomiri-camera-app 4.0.8+dfsg-4 has caused the Debian Bug report #1105112, regarding lomiri-camera-app: image quality on app startup not initialized properly to be marked as done. This means

Processed: src:actiona: fails to migrate to testing for too long

2025-05-30 Thread Debian Bug Tracking System
Processing control commands: > close -1 3.11.1-1 Bug #1106855 [src:actiona] src:actiona: fails to migrate to testing for too long Marked as fixed in versions actiona/3.11.1-1. Bug #1106855 [src:actiona] src:actiona: fails to migrate to testing for too long Marked Bug as done -- 1106855: https://

Processed: src:mini-buildd: fails to migrate to testing for too long

2025-05-30 Thread Debian Bug Tracking System
Processing control commands: > close -1 2.4.0 Bug #1106853 [src:mini-buildd] src:mini-buildd: fails to migrate to testing for too long Marked as fixed in versions mini-buildd/2.4.0. Bug #1106853 [src:mini-buildd] src:mini-buildd: fails to migrate to testing for too long Marked Bug as done -- 1

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

2025-05-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 May 2025 11:34:43 + with message-id and subject line Bug#1106797: fixed in catatonit 0.2.1-2 has caused the Debian Bug report #1106797, regarding catatonit: statically linked against glibc without a Built-Using: field to be marked as done. This means that you claim

Bug#1106803: marked as done (liblxc-common: statically linked against glibc without a Built-Using: field)

2025-05-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 May 2025 13:19:31 + with message-id and subject line Bug#1106803: fixed in lxc 1:6.0.4-4 has caused the Debian Bug report #1106803, regarding liblxc-common: statically linked against glibc without a Built-Using: field to be marked as done. This means that you claim

Bug#1106702: marked as done ([preauth] unblock: scifem/0.6.0-1)

2025-05-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 May 2025 12:40:00 +0200 with message-id and subject line Re: Bug#1106702: [preauth] unblock: scifem/0.6.0-1 has caused the Debian Bug report #1106702, regarding [preauth] unblock: scifem/0.6.0-1 to be marked as done. This means that you claim that the problem has been d

Bug#1106846: marked as done (qgis: georeferencer erros on saving file until some configuration change is done)

2025-05-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 May 2025 14:51:02 +0200 with message-id <2a73c834-0ecb-40cd-95c9-5b021768d...@xs4all.nl> and subject line Re: [DKIM] Bug#1106846: qgis: georeferencer erros on saving file until some configuration change is done has caused the Debian Bug report #1106846, regarding qgis: g

Bug#1106716: marked as done (unblock: krop/0.7.0-0.1)

2025-05-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 May 2025 14:39:29 +0200 with message-id <51fc60a1-a924-4799-9d2f-b26071af1...@debian.org> and subject line Re: Bug#1106716: unblock: krop/0.7.0-0.1 has caused the Debian Bug report #1106716, regarding unblock: krop/0.7.0-0.1 to be marked as done. This means that you clai

Bug#1106438: marked as done (python-hypothesis: FTBFS: ERROR tests/redis/test_redis_exampledatabase.py - DeprecationWarning: Call to...)

2025-05-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 May 2025 11:35:10 + with message-id and subject line Bug#1106438: fixed in python-hypothesis 6.130.5-2 has caused the Debian Bug report #1106438, regarding python-hypothesis: FTBFS: ERROR tests/redis/test_redis_exampledatabase.py - DeprecationWarning: Call to... to

Bug#1106795: marked as done (libbg-dev: statically linked against glibc without a Built-Using: field)

2025-05-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 May 2025 11:04:41 + with message-id and subject line Bug#1106795: fixed in bglibs 2.04+dfsg-8 has caused the Debian Bug report #1106795, regarding libbg-dev: statically linked against glibc without a Built-Using: field to be marked as done. This means that you clai

Bug#1106836: marked as done (unblock: tk9.0/9.0.1-3)

2025-05-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 May 2025 10:55:01 + with message-id and subject line unblock tk9.0 has caused the Debian Bug report #1106836, regarding unblock: tk9.0/9.0.1-3 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#1106807: marked as done (tini: statically linked against glibc without a Built-Using: field)

2025-05-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 May 2025 10:05:04 + with message-id and subject line Bug#1106807: fixed in tini 0.19.0-2 has caused the Debian Bug report #1106807, regarding tini: statically linked against glibc without a Built-Using: field to be marked as done. This means that you claim that the

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

2025-05-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 May 2025 09:51:03 + with message-id and subject line Bug#1106801: fixed in integrit 4.1-7 has caused the Debian Bug report #1106801, regarding integrit: statically linked against glibc without a Built-Using: field to be marked as done. This means that you claim that

Bug#1106825: marked as done (www.debian.org: new entry for events/merchandise: Ten Thousand Things, LLC (was: Re: Original Debian Merchandise))

2025-05-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 May 2025 11:23:16 +0200 with message-id <26681.30980.760979.286...@cs.uni-koeln.de> and subject line Bug#1106825: www.debian.org: new entry for events/merchandise: Ten Thousand Things, LLC (was: Re: Original Debian Merchandise) has caused the Debian Bug report #1106825,

Bug#1106708: marked as done (openrazer-driver-dkms: module fails to build for Linux 6.15: error: implicit declaration of function 'hrtimer_init')

2025-05-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 May 2025 07:49:11 + with message-id and subject line Bug#1106708: fixed in openrazer 3.10.3+dfsg-1 has caused the Debian Bug report #1106708, regarding openrazer-driver-dkms: module fails to build for Linux 6.15: error: implicit declaration of function 'hrtimer_init

Processed: Re: Processed: Re: Bug#1106376: marked as pending in python-redis

2025-05-30 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # hmmm, just spotted that this reopens the bug too > close 1106376 Bug #1106376 [src:python-redis] redis breaks python-redis autopkgtest on arm64, ppc64el, riscv64 and s390x Marked Bug as done > thanks Stopping processing here. Please contact me

Bug#1106697: marked as done (unblock: wine/10.0~repack-4)

2025-05-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 May 2025 09:21:44 +0200 with message-id and subject line Re: Bug#1106697: unblock: wine/10.0~repack-4 has caused the Debian Bug report #1106697, regarding unblock: wine/10.0~repack-4 to be marked as done. This means that you claim that the problem has been dealt with. I

Bug#1104621: marked as done (unblock: apt-mirror2/13-2)

2025-05-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 May 2025 09:19:41 +0200 with message-id and subject line Re: Bug#1104621: unblock: apt-mirror2/13-2 has caused the Debian Bug report #1104621, regarding unblock: apt-mirror2/13-2 to be marked as done. This means that you claim that the problem has been dealt with. If th