ffmpegthumbs_25.04.0-1_source.changes ACCEPTED into unstable

Thank you for your contribution to Debian. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 21 Apr 2025 19:02:31 -0400 Source: ffmpegthumbs Architecture: source Version: 4:25.04.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Qt/KDE Maintainers Ch

Processing of ffmpegthumbs_25.04.0-1_source.changes

ffmpegthumbs_25.04.0-1_source.changes uploaded successfully to localhost along with the files: ffmpegthumbs_25.04.0-1.dsc ffmpegthumbs_25.04.0.orig.tar.xz ffmpegthumbs_25.04.0.orig.tar.xz.asc ffmpegthumbs_25.04.0-1.debian.tar.xz ffmpegthumbs_25.04.0-1_amd64.buildinfo Greetings,

Processing of plasma-framework_5.116.0-2_source.changes

plasma-framework_5.116.0-2_source.changes uploaded successfully to localhost along with the files: plasma-framework_5.116.0-2.dsc plasma-framework_5.116.0-2.debian.tar.xz plasma-framework_5.116.0-2_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.or

Processing of krunner_5.116.0-1_source.changes

krunner_5.116.0-1_source.changes uploaded successfully to localhost along with the files: krunner_5.116.0-1.dsc krunner_5.116.0.orig.tar.xz krunner_5.116.0.orig.tar.xz.asc krunner_5.116.0-1.debian.tar.xz krunner_5.116.0-1_source.buildinfo Greetings, Your Debian queue daemon (run

plasma-framework_5.116.0-2_source.changes ACCEPTED into unstable

Thank you for your contribution to Debian. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 22 Apr 2025 01:04:38 +0200 Source: plasma-framework Architecture: source Version: 5.116.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Qt/KDE Maintainers

krunner_5.116.0-1_source.changes ACCEPTED into unstable

Thank you for your contribution to Debian. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 13 Apr 2025 00:44:16 +0200 Source: krunner Architecture: source Version: 5.116.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Qt/KDE Maintainers Changed-B

Bug#1103806: akonadi-search FTCBFS: builds rust component for the build architecture

Helmut Grohne: Source: akonadi-search Version: 4:24.12.3-1 Tags: patch User: debian-cr...@lists.debian.org Usertags: ftcbfs X-Debbugs-Cc: debian-cr...@lists.debian.org, debhel...@packages.debian.org, nil...@debian.org akonadi-search fails to cross build from source, because it builds a Rust-bas

Bug#1103774: marked as done (plasma-firewall: Upgrading from bookworm to trixie breaks kdeconnect)

Your message dated Mon, 21 Apr 2025 19:38:53 +0200 with message-id <4975611.GXAFRqVoOG@treadstone-71> and subject line has caused the Debian Bug report #1103774, regarding plasma-firewall: Upgrading from bookworm to trixie breaks kdeconnect to be marked as done. This means that you claim that the

Bug#1099058: marked as done (plasma-firewall: Installing plasma-firewall on a new system breaks mDNS)

Your message dated Mon, 21 Apr 2025 19:38:28 +0200 with message-id <4645010.LvFx2qVVIh@treadstone-71> and subject line has caused the Debian Bug report #1099058, regarding plasma-firewall: Installing plasma-firewall on a new system breaks mDNS to be marked as done. This means that you claim that

Bug#1097600: marked as done (plasma-firewall: ftbfs with GCC-15)

Your message dated Mon, 21 Apr 2025 19:28:40 +0200 with message-id <2778021.mvXUDI8C0e@treadstone-71> and subject line has caused the Debian Bug report #1097600, regarding plasma-firewall: ftbfs with GCC-15 to be marked as done. This means that you claim that the problem has been dealt with. If t

Processed: your mail

Processing commands for cont...@bugs.debian.org: > fixed 1099058 6.3.4-2 Bug #1099058 [plasma-firewall] plasma-firewall: Installing plasma-firewall on a new system breaks mDNS Marked as fixed in versions plasma-firewall/6.3.4-2. > fixed 1103774 6.3.4-2 Bug #1103774 [plasma-firewall] plasma-firewa

Bug#1103806: akonadi-search FTCBFS: builds rust component for the build architecture

Source: akonadi-search Version: 4:24.12.3-1 Tags: patch User: debian-cr...@lists.debian.org Usertags: ftcbfs X-Debbugs-Cc: debian-cr...@lists.debian.org, debhel...@packages.debian.org, nil...@debian.org akonadi-search fails to cross build from source, because it builds a Rust-based component for

Bug#1103774: plasma-firewall: Upgrading from bookworm to trixie breaks kdeconnect

Package: plasma-firewall Version: 6.3.4-1 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** I upgraded from bookworm to trixie and after that kdeconnect stopped working. Purging firewalld and plasma-firewall resolved the issue.

Processing of kidletime_5.116.0-2_source.changes

kidletime_5.116.0-2_source.changes uploaded successfully to localhost along with the files: kidletime_5.116.0-2.dsc kidletime_5.116.0-2.debian.tar.xz kidletime_5.116.0-2_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)

kidletime_5.116.0-2_source.changes ACCEPTED into unstable

Thank you for your contribution to Debian. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 21 Apr 2025 13:01:53 +0200 Source: kidletime Architecture: source Version: 5.116.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Qt/KDE Maintainers Changed

Bug#1096386: marked as done (bomber: ftbfs with GCC-15)

Your message dated Mon, 21 Apr 2025 12:40:41 +0200 with message-id and subject line ftbfs with GCC-15 has caused the Debian Bug report #1096386, regarding bomber: ftbfs with GCC-15 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#1096879: marked as done (juk: ftbfs with GCC-15)

Your message dated Mon, 21 Apr 2025 12:41:58 +0200 with message-id and subject line ftbfs with GCC-15 has caused the Debian Bug report #1096879, regarding juk: ftbfs with GCC-15 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 no

Bug#1096867: marked as done (itinerary: ftbfs with GCC-15)

Your message dated Mon, 21 Apr 2025 12:41:58 +0200 with message-id and subject line ftbfs with GCC-15 has caused the Debian Bug report #1096867, regarding itinerary: ftbfs with GCC-15 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#1096665: marked as done (futuresql: ftbfs with GCC-15)

Your message dated Mon, 21 Apr 2025 12:41:58 +0200 with message-id and subject line ftbfs with GCC-15 has caused the Debian Bug report #1096665, regarding futuresql: ftbfs with GCC-15 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#1096637: marked as done (flatpak-kcm: ftbfs with GCC-15)

Your message dated Mon, 21 Apr 2025 12:41:58 +0200 with message-id and subject line ftbfs with GCC-15 has caused the Debian Bug report #1096637, regarding flatpak-kcm: ftbfs with GCC-15 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case

Bug#1096544: marked as done (dragon: ftbfs with GCC-15)

Your message dated Mon, 21 Apr 2025 12:41:17 +0200 with message-id and subject line ftbfs with GCC-15 has caused the Debian Bug report #1096544, regarding dragon: ftbfs with GCC-15 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#1096630: marked as done (filelight: ftbfs with GCC-15)

Your message dated Mon, 21 Apr 2025 12:41:58 +0200 with message-id and subject line ftbfs with GCC-15 has caused the Debian Bug report #1096630, regarding filelight: ftbfs with GCC-15 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#1096596: marked as done (eventviews: ftbfs with GCC-15)

Your message dated Mon, 21 Apr 2025 12:41:58 +0200 with message-id and subject line ftbfs with GCC-15 has caused the Debian Bug report #1096596, regarding eventviews: ftbfs with GCC-15 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case i

Bug#1096538: marked as done (dolphin-plugins: ftbfs with GCC-15)

Your message dated Mon, 21 Apr 2025 12:41:17 +0200 with message-id and subject line ftbfs with GCC-15 has caused the Debian Bug report #1096538, regarding dolphin-plugins: ftbfs with GCC-15 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the c

Bug#1096629: marked as done (ffmpegthumbs: ftbfs with GCC-15)

Your message dated Mon, 21 Apr 2025 12:41:58 +0200 with message-id and subject line ftbfs with GCC-15 has caused the Debian Bug report #1096629, regarding ffmpegthumbs: ftbfs with GCC-15 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case

Bug#1096571: marked as done (elisa-player: ftbfs with GCC-15)

Your message dated Mon, 21 Apr 2025 12:41:17 +0200 with message-id and subject line ftbfs with GCC-15 has caused the Debian Bug report #1096571, regarding elisa-player: ftbfs with GCC-15 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case

Bug#1096406: marked as done (calendarsupport: ftbfs with GCC-15)

Your message dated Mon, 21 Apr 2025 12:40:41 +0200 with message-id and subject line ftbfs with GCC-15 has caused the Debian Bug report #1096406, regarding calendarsupport: ftbfs with GCC-15 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the c

Bug#1096456: marked as done (colord-kde: ftbfs with GCC-15)

Your message dated Mon, 21 Apr 2025 12:41:17 +0200 with message-id and subject line ftbfs with GCC-15 has caused the Debian Bug report #1096456, regarding colord-kde: ftbfs with GCC-15 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case i

Bug#1096409: marked as done (calligra: ftbfs with GCC-15)

Your message dated Mon, 21 Apr 2025 12:41:17 +0200 with message-id and subject line ftbfs with GCC-15 has caused the Debian Bug report #1096409, regarding calligra: ftbfs with GCC-15 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#1096390: marked as done (bovo: ftbfs with GCC-15)

Your message dated Mon, 21 Apr 2025 12:40:41 +0200 with message-id and subject line ftbfs with GCC-15 has caused the Debian Bug report #1096390, regarding bovo: ftbfs with GCC-15 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 n

Bug#1096392: marked as done (breeze: ftbfs with GCC-15)

Your message dated Mon, 21 Apr 2025 12:40:41 +0200 with message-id and subject line ftbfs with GCC-15 has caused the Debian Bug report #1096392, regarding breeze: ftbfs with GCC-15 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#1096380: marked as done (bluedevil: ftbfs with GCC-15)

Your message dated Mon, 21 Apr 2025 12:40:41 +0200 with message-id and subject line ftbfs with GCC-15 has caused the Debian Bug report #1096380, regarding bluedevil: ftbfs with GCC-15 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#1096771: marked as done (granatier: ftbfs with GCC-15)

Your message dated Mon, 21 Apr 2025 12:28:35 +0200 with message-id and subject line ftbfs with GCC-15 has caused the Debian Bug report #1096771, regarding granatier: ftbfs with GCC-15 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#1096704: marked as done (ghostwriter: ftbfs with GCC-15)

Your message dated Mon, 21 Apr 2025 12:28:35 +0200 with message-id and subject line ftbfs with GCC-15 has caused the Debian Bug report #1096704, regarding ghostwriter: ftbfs with GCC-15 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case

Bug#1096773: marked as done (grantleetheme: ftbfs with GCC-15)

Your message dated Mon, 21 Apr 2025 12:28:35 +0200 with message-id and subject line ftbfs with GCC-15 has caused the Debian Bug report #1096773, regarding grantleetheme: ftbfs with GCC-15 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the cas

Bug#1096688: marked as done (gcompris-qt: ftbfs with GCC-15)

Your message dated Mon, 21 Apr 2025 12:28:35 +0200 with message-id and subject line ftbfs with GCC-15 has caused the Debian Bug report #1096688, regarding gcompris-qt: ftbfs with GCC-15 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case

Bug#1096376: marked as done (blinken: ftbfs with GCC-15)

Your message dated Mon, 21 Apr 2025 12:28:35 +0200 with message-id and subject line ftbfs with GCC-15 has caused the Debian Bug report #1096376, regarding blinken: ftbfs with GCC-15 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

Processing of kguiaddons_5.116.0-2_source.changes

kguiaddons_5.116.0-2_source.changes uploaded successfully to localhost along with the files: kguiaddons_5.116.0-2.dsc kguiaddons_5.116.0-2.debian.tar.xz kguiaddons_5.116.0-2_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)

kguiaddons_5.116.0-2_source.changes ACCEPTED into unstable

Thank you for your contribution to Debian. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 21 Apr 2025 11:33:45 +0200 Source: kguiaddons Architecture: source Version: 5.116.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Qt/KDE Maintainers Change

Bug#1096866: marked as done (isoimagewriter: ftbfs with GCC-15)

Your message dated Mon, 21 Apr 2025 11:19:57 +0200 with message-id and subject line ftbfs with GCC-15 has caused the Debian Bug report #1096866, regarding isoimagewriter: ftbfs with GCC-15 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the ca

Bug#1096835: marked as done (incidenceeditor: ftbfs with GCC-15)

Your message dated Mon, 21 Apr 2025 11:19:57 +0200 with message-id and subject line ftbfs with GCC-15 has caused the Debian Bug report #1096835, regarding incidenceeditor: ftbfs with GCC-15 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the c

Bug#1096794: marked as done (gwenview: ftbfs with GCC-15)

Your message dated Mon, 21 Apr 2025 11:19:57 +0200 with message-id and subject line ftbfs with GCC-15 has caused the Debian Bug report #1096794, regarding gwenview: ftbfs with GCC-15 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#1096774: marked as done (grantlee-editor: ftbfs with GCC-15)

Your message dated Mon, 21 Apr 2025 11:19:57 +0200 with message-id and subject line ftbfs with GCC-15 has caused the Debian Bug report #1096774, regarding grantlee-editor: ftbfs with GCC-15 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the c

Bug#1096355: marked as done (baloo-widgets: ftbfs with GCC-15)

Your message dated Mon, 21 Apr 2025 11:19:57 +0200 with message-id and subject line ftbfs with GCC-15 has caused the Debian Bug report #1096355, regarding baloo-widgets: ftbfs with GCC-15 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the cas

qt6-tools_6.8.2-5_source.changes ACCEPTED into unstable

Thank you for your contribution to Debian. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 21 Apr 2025 10:01:50 +0200 Source: qt6-tools Architecture: source Version: 6.8.2-5 Distribution: unstable Urgency: medium Maintainer: Debian Qt/KDE Maintainers Changed-B

Processing of qt6-tools_6.8.2-5_source.changes

qt6-tools_6.8.2-5_source.changes uploaded successfully to localhost along with the files: qt6-tools_6.8.2-5.dsc qt6-tools_6.8.2-5.debian.tar.xz qt6-tools_6.8.2-5_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)