qtbase-opensource-src_5.15.17+dfsg-1_source.changes ACCEPTED into experimental

Thank you for your contribution to Debian. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 24 May 2025 22:32:13 +0300 Source: qtbase-opensource-src Architecture: source Version: 5.15.17+dfsg-1 Distribution: experimental Urgency: medium Maintainer: Debian Qt/KDE

Processing of meta-kde_163_source.changes

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

meta-kde_163_source.changes ACCEPTED into experimental

Thank you for your contribution to Debian. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 24 May 2025 22:21:39 +0200 Source: meta-kde Architecture: source Version: 5:163 Distribution: experimental Urgency: medium Maintainer: Debian Qt/KDE Maintainers Changed-

Processing of qtbase-opensource-src_5.15.17+dfsg-1_source.changes

qtbase-opensource-src_5.15.17+dfsg-1_source.changes uploaded successfully to localhost along with the files: qtbase-opensource-src_5.15.17+dfsg-1.dsc qtbase-opensource-src_5.15.17+dfsg.orig.tar.xz qtbase-opensource-src_5.15.17+dfsg-1.debian.tar.xz qtbase-opensource-src_5.15.17+dfsg-1_sourc

Bug#1096960: marked as done (kf6-kcolorscheme: ftbfs with GCC-15)

Your message dated Sat, 24 May 2025 15:51:27 +0200 with message-id and subject line ftbfs with GCC-15 has caused the Debian Bug report #1096960, regarding kf6-kcolorscheme: 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

Bug#1096977: marked as done (kf6-kholidays: ftbfs with GCC-15)

Your message dated Sat, 24 May 2025 15:57:54 +0200 with message-id and subject line ftbfs with GCC-15 has caused the Debian Bug report #1096977, regarding kf6-kholidays: 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#1096955: marked as done (kf6-kauth: ftbfs with GCC-15)

Your message dated Sat, 24 May 2025 15:49:25 +0200 with message-id and subject line ftbfs with GCC-15 has caused the Debian Bug report #1096955, regarding kf6-kauth: 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#1096953: marked as done (kf6-bluez-qt: ftbfs with GCC-15)

Your message dated Sat, 24 May 2025 15:49:25 +0200 with message-id and subject line ftbfs with GCC-15 has caused the Debian Bug report #1096953, regarding kf6-bluez-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#1096979: marked as done (kf6-ki18n: ftbfs with GCC-15)

Your message dated Sat, 24 May 2025 15:57:54 +0200 with message-id and subject line ftbfs with GCC-15 has caused the Debian Bug report #1096979, regarding kf6-ki18n: 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#1096978: marked as done (kf6-kiconthemes: ftbfs with GCC-15)

Your message dated Sat, 24 May 2025 15:57:54 +0200 with message-id and subject line ftbfs with GCC-15 has caused the Debian Bug report #1096978, regarding kf6-kiconthemes: 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#1096975: marked as done (kf6-kfilemetadata: ftbfs with GCC-15)

Your message dated Sat, 24 May 2025 15:57:54 +0200 with message-id and subject line ftbfs with GCC-15 has caused the Debian Bug report #1096975, regarding kf6-kfilemetadata: 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

Bug#1096974: marked as done (kf6-kglobalaccel: ftbfs with GCC-15)

Your message dated Sat, 24 May 2025 15:57:54 +0200 with message-id and subject line ftbfs with GCC-15 has caused the Debian Bug report #1096974, regarding kf6-kglobalaccel: 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

Bug#1096972: marked as done (kf6-kdnssd: ftbfs with GCC-15)

Your message dated Sat, 24 May 2025 15:55:41 +0200 with message-id and subject line ftbfs with GCC-15 has caused the Debian Bug report #1096972, regarding kf6-kdnssd: 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#1096973: marked as done (kf6-kdoctools: ftbfs with GCC-15)

Your message dated Sat, 24 May 2025 15:55:41 +0200 with message-id and subject line ftbfs with GCC-15 has caused the Debian Bug report #1096973, regarding kf6-kdoctools: 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#1096971: marked as done (kf6-kded: ftbfs with GCC-15)

Your message dated Sat, 24 May 2025 15:55:41 +0200 with message-id and subject line ftbfs with GCC-15 has caused the Debian Bug report #1096971, regarding kf6-kded: 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#1096970: marked as done (kf6-kdesu: ftbfs with GCC-15)

Your message dated Sat, 24 May 2025 15:55:41 +0200 with message-id and subject line ftbfs with GCC-15 has caused the Debian Bug report #1096970, regarding kf6-kdesu: 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#1096969: marked as done (kf6-kdeclarative: ftbfs with GCC-15)

Your message dated Sat, 24 May 2025 15:55:41 +0200 with message-id and subject line ftbfs with GCC-15 has caused the Debian Bug report #1096969, regarding kf6-kdeclarative: 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

Bug#1096968: marked as done (kf6-kdbusaddons: ftbfs with GCC-15)

Your message dated Sat, 24 May 2025 15:53:37 +0200 with message-id and subject line ftbfs with GCC-15 has caused the Debian Bug report #1096968, regarding kf6-kdbusaddons: 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#1096966: marked as done (kf6-kdav: ftbfs with GCC-15)

Your message dated Sat, 24 May 2025 15:53:37 +0200 with message-id and subject line ftbfs with GCC-15 has caused the Debian Bug report #1096966, regarding kf6-kdav: 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#1096964: marked as done (kf6-kcontacts: ftbfs with GCC-15)

Your message dated Sat, 24 May 2025 15:53:37 +0200 with message-id and subject line ftbfs with GCC-15 has caused the Debian Bug report #1096964, regarding kf6-kcontacts: 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#1096965: marked as done (kf6-kcoreaddons: ftbfs with GCC-15)

Your message dated Sat, 24 May 2025 15:53:37 +0200 with message-id and subject line ftbfs with GCC-15 has caused the Debian Bug report #1096965, regarding kf6-kcoreaddons: 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#1096963: marked as done (kf6-kconfigwidgets: ftbfs with GCC-15)

Your message dated Sat, 24 May 2025 15:51:27 +0200 with message-id and subject line ftbfs with GCC-15 has caused the Debian Bug report #1096963, regarding kf6-kconfigwidgets: 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 th

Bug#1096961: marked as done (kf6-kcompletion: ftbfs with GCC-15)

Your message dated Sat, 24 May 2025 15:51:27 +0200 with message-id and subject line ftbfs with GCC-15 has caused the Debian Bug report #1096961, regarding kf6-kcompletion: 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#1096958: marked as done (kf6-kcodecs: ftbfs with GCC-15)

Your message dated Sat, 24 May 2025 15:51:27 +0200 with message-id and subject line ftbfs with GCC-15 has caused the Debian Bug report #1096958, regarding kf6-kcodecs: 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#1096959: marked as done (kf6-kcmutils: ftbfs with GCC-15)

Your message dated Sat, 24 May 2025 15:51:27 +0200 with message-id and subject line ftbfs with GCC-15 has caused the Debian Bug report #1096959, regarding kf6-kcmutils: 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#1096956: marked as done (kf6-kbookmarks: ftbfs with GCC-15)

Your message dated Sat, 24 May 2025 15:49:25 +0200 with message-id and subject line ftbfs with GCC-15 has caused the Debian Bug report #1096956, regarding kf6-kbookmarks: 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#1096954: marked as done (kf6-karchive: ftbfs with GCC-15)

Your message dated Sat, 24 May 2025 15:49:25 +0200 with message-id and subject line ftbfs with GCC-15 has caused the Debian Bug report #1096954, regarding kf6-karchive: 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#1106398: plasma-nm: Cannot get hotspot working on desktop

Package: plasma-nm Version: 4:6.3.4-1 Severity: normal Dear Maintainer, I've been trying for a while, and failing, to get a hotspot working on my (testing) desktop, so my phone can connect through it. At first, it was a problem with autentication. But that has been solved now. The phone connect