kosmindoormap_22.12.1-2_source.changes ACCEPTED into unstable

Thank you for your contribution to Debian. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 01 Feb 2023 00:28:31 +0100 Source: kosmindoormap Architecture: source Version: 22.12.1-2 Distribution: unstable Urgency: medium Maintainer: Debian Qt/KDE Maintainers

Processing of kosmindoormap_22.12.1-2_source.changes

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

Re: qtwebengine-opensource-src_5.15.12+dfsg-3_source.changes REJECTED

Dmitry, Do you know why this error occurred? There is already a Lintian override for this in debian/source/lintian-overrides and when running Lintian in my sbuild it is correctly applied. You can see this in the build log at the following link (search for "running lintian” to jump to the

qtwebengine-opensource-src_5.15.12+dfsg-3_source.changes REJECTED

qtwebengine-opensource-src source: lintian output: 'license-problem-json-evil src/3rdparty/chromium/third_party/angle/third_party/rapidjson/src/license.txt', automatically rejected package. qtwebengine-opensource-src source: If you have a good reason, you may override this lintian tag.

Processing of qtwebengine-opensource-src_5.15.12+dfsg-3_source.changes

qtwebengine-opensource-src_5.15.12+dfsg-3_source.changes uploaded successfully to localhost along with the files: qtwebengine-opensource-src_5.15.12+dfsg-3.dsc qtwebengine-opensource-src_5.15.12+dfsg-3.debian.tar.xz qtwebengine-opensource-src_5.15.12+dfsg-3_source.buildinfo Greetings,

qt6-base_6.4.2+dfsg-1_source.changes ACCEPTED into unstable

Thank you for your contribution to Debian. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 31 Jan 2023 19:16:32 +0100 Source: qt6-base Architecture: source Version: 6.4.2+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian Qt/KDE Maintainers

Bug#1025663: marked as done (qmake6: how should users query for QT_INSTALL_PLUGINS?)

Your message dated Tue, 31 Jan 2023 19:10:16 + with message-id and subject line Bug#1025663: fixed in qt6-base 6.4.2+dfsg-1 has caused the Debian Bug report #1025663, regarding qmake6: how should users query for QT_INSTALL_PLUGINS? to be marked as done. This means that you claim that the

Bug#1023054: marked as done (qt6-base FTCBFS: multiple reasons)

Your message dated Tue, 31 Jan 2023 19:10:16 + with message-id and subject line Bug#1023054: fixed in qt6-base 6.4.2+dfsg-1 has caused the Debian Bug report #1023054, regarding qt6-base FTCBFS: multiple reasons to be marked as done. This means that you claim that the problem has been dealt

Processing of qt6-base_6.4.2+dfsg-1_source.changes

qt6-base_6.4.2+dfsg-1_source.changes uploaded successfully to localhost along with the files: qt6-base_6.4.2+dfsg-1.dsc qt6-base_6.4.2+dfsg.orig.tar.xz qt6-base_6.4.2+dfsg-1.debian.tar.xz qt6-base_6.4.2+dfsg-1_source.buildinfo Greetings, Your Debian queue daemon (running on host

itinerary_22.12.1-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, 31 Jan 2023 17:44:26 +0100 Source: itinerary Architecture: source Version: 22.12.1-2 Distribution: unstable Urgency: medium Maintainer: Debian/Kubuntu Qt/KDE Maintainers

itinerary_22.12.1-1_source.changes ACCEPTED into unstable

Thank you for your contribution to Debian. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 31 Jan 2023 17:37:34 +0100 Source: itinerary Architecture: source Version: 22.12.1-1 Distribution: unstable Urgency: medium Maintainer: Debian/Kubuntu Qt/KDE Maintainers

Processing of itinerary_22.12.1-2_source.changes

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

Bug#1030004: marked as done (itinerary: missing dependency on qml-module-qt-labs-qmlmodels)

Your message dated Tue, 31 Jan 2023 17:05:03 + with message-id and subject line Bug#1030004: fixed in itinerary 22.12.1-1 has caused the Debian Bug report #1030004, regarding itinerary: missing dependency on qml-module-qt-labs-qmlmodels to be marked as done. This means that you claim that

Processing of itinerary_22.12.1-1_source.changes

itinerary_22.12.1-1_source.changes uploaded successfully to localhost along with the files: itinerary_22.12.1-1.dsc itinerary_22.12.1.orig.tar.xz itinerary_22.12.1.orig.tar.xz.asc itinerary_22.12.1-1.debian.tar.xz itinerary_22.12.1-1_source.buildinfo Greetings, Your Debian

Bug#1029904: marked as done (drkonqi: Wait for the resolution of the libkscreen transition before migrating to testing)

Your message dated with message-id and subject line has caused the Debian Bug report #1029904, regarding drkonqi: Wait for the resolution of the libkscreen transition before migrating to testing to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#1029903: marked as done (oxygen-sounds: Wait for the resolution of the libkscreen transition before migrating to testing)

Your message dated with message-id and subject line has caused the Debian Bug report #1029903, regarding oxygen-sounds: Wait for the resolution of the libkscreen transition before migrating to testing to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1029902: marked as done (kwallet-pam: Wait for the resolution of the libkscreen transition before migrating to testing)

Your message dated with message-id and subject line has caused the Debian Bug report #1029902, regarding kwallet-pam: Wait for the resolution of the libkscreen transition before migrating to testing to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#1029901: marked as done (oxygen: Wait for the resolution of the libkscreen transition before migrating to testing)

Your message dated with message-id and subject line has caused the Debian Bug report #1029901, regarding oxygen: Wait for the resolution of the libkscreen transition before migrating to testing to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#1029900: marked as done (kpipewire: Wait for the resolution of the libkscreen transition before migrating to testing)

Your message dated with message-id and subject line has caused the Debian Bug report #1029900, regarding kpipewire: Wait for the resolution of the libkscreen transition before migrating to testing to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#1029899: marked as done (kinfocenter: Wait for the resolution of the libkscreen transition before migrating to testing)

Your message dated with message-id and subject line has caused the Debian Bug report #1029899, regarding kinfocenter: Wait for the resolution of the libkscreen transition before migrating to testing to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#1029898: marked as done (kmenuedit: Wait for the resolution of the libkscreen transition before migrating to testing)

Your message dated with message-id and subject line has caused the Debian Bug report #1029898, regarding kmenuedit: Wait for the resolution of the libkscreen transition before migrating to testing to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#1029897: marked as done (kde-cli-tools: Wait for the resolution of the libkscreen transition before migrating to testing)

Your message dated with message-id and subject line has caused the Debian Bug report #1029897, regarding kde-cli-tools: Wait for the resolution of the libkscreen transition before migrating to testing to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1029896: marked as done (kscreenlocker: Wait for the resolution of the libkscreen transition before migrating to testing)

Your message dated with message-id and subject line has caused the Debian Bug report #1029896, regarding kscreenlocker: Wait for the resolution of the libkscreen transition before migrating to testing to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1029893: marked as done (kwrited: Wait for the resolution of the libkscreen transition before migrating to testing)

Your message dated with message-id and subject line has caused the Debian Bug report #1029893, regarding kwrited: Wait for the resolution of the libkscreen transition before migrating to testing to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#1029895: marked as done (libksysguard: Wait for the resolution of the libkscreen transition before migrating to testing)

Your message dated with message-id and subject line has caused the Debian Bug report #1029895, regarding libksysguard: Wait for the resolution of the libkscreen transition before migrating to testing to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#1029894: marked as done (kdeplasma-addons: Wait for the resolution of the libkscreen transition before migrating to testing)

Your message dated with message-id and subject line has caused the Debian Bug report #1029894, regarding kdeplasma-addons: Wait for the resolution of the libkscreen transition before migrating to testing to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1029892: marked as done (breeze-gtk: Wait for the resolution of the libkscreen transition before migrating to testing)

Your message dated with message-id and subject line has caused the Debian Bug report #1029892, regarding breeze-gtk: Wait for the resolution of the libkscreen transition before migrating to testing to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#1029891: marked as done (breeze: Wait for the resolution of the libkscreen transition before migrating to testing)

Your message dated with message-id and subject line has caused the Debian Bug report #1029891, regarding breeze: Wait for the resolution of the libkscreen transition before migrating to testing to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#1029889: marked as done (systemsettings: Wait for the resolution of the libkscreen transition before migrating to testing)

Your message dated with message-id and subject line has caused the Debian Bug report #1029889, regarding systemsettings: Wait for the resolution of the libkscreen transition before migrating to testing to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1029887: marked as done (xdg-desktop-portal-kde: Wait for the resolution of the libkscreen transition before migrating to testing)

Your message dated with message-id and subject line has caused the Debian Bug report #1029887, regarding xdg-desktop-portal-kde: Wait for the resolution of the libkscreen transition before migrating to testing to be marked as done. This means that you claim that the problem has been dealt

Bug#1029886: marked as done (qqc2-breeze-style: Wait for the resolution of the libkscreen transition before migrating to testing)

Your message dated with message-id and subject line has caused the Debian Bug report #1029886, regarding qqc2-breeze-style: Wait for the resolution of the libkscreen transition before migrating to testing to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1029884: marked as done (plymouth-kcm: Wait for the resolution of the libkscreen transition before migrating to testing)

Your message dated with message-id and subject line has caused the Debian Bug report #1029884, regarding plymouth-kcm: Wait for the resolution of the libkscreen transition before migrating to testing to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#1029885: marked as done (plasma-desktop: Wait for the resolution of the libkscreen transition before migrating to testing)

Your message dated with message-id and subject line has caused the Debian Bug report #1029885, regarding plasma-desktop: Wait for the resolution of the libkscreen transition before migrating to testing to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1029883: marked as done (kde-gtk-config: Wait for the resolution of the libkscreen transition before migrating to testing)

Your message dated with message-id and subject line has caused the Debian Bug report #1029883, regarding kde-gtk-config: Wait for the resolution of the libkscreen transition before migrating to testing to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1029882: marked as done (plasma-workspace: Wait for the resolution of the libkscreen transition before migrating to testing)

Your message dated with message-id and subject line has caused the Debian Bug report #1029882, regarding plasma-workspace: Wait for the resolution of the libkscreen transition before migrating to testing to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1029880: marked as done (kgamma5: Wait for the resolution of the libkscreen transition before migrating to testing)

Your message dated with message-id and subject line has caused the Debian Bug report #1029880, regarding kgamma5: Wait for the resolution of the libkscreen transition before migrating to testing to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#1029876: marked as done (layer-shell-qt: Wait for the resolution of the libkscreen transition before migrating to testing)

Your message dated with message-id and subject line has caused the Debian Bug report #1029876, regarding layer-shell-qt: Wait for the resolution of the libkscreen transition before migrating to testing to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1029878: marked as done (khotkeys: Wait for the resolution of the libkscreen transition before migrating to testing)

Your message dated with message-id and subject line has caused the Debian Bug report #1029878, regarding khotkeys: Wait for the resolution of the libkscreen transition before migrating to testing to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#1029879: marked as done (kactivitymanagerd: Wait for the resolution of the libkscreen transition before migrating to testing)

Your message dated with message-id and subject line has caused the Debian Bug report #1029879, regarding kactivitymanagerd: Wait for the resolution of the libkscreen transition before migrating to testing to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1029874: marked as done (plasma-discover: Wait for the resolution of the libkscreen transition before migrating to testing)

Your message dated with message-id and subject line has caused the Debian Bug report #1029874, regarding plasma-discover: Wait for the resolution of the libkscreen transition before migrating to testing to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1029875: marked as done (plasma-sdk: Wait for the resolution of the libkscreen transition before migrating to testing)

Your message dated with message-id and subject line has caused the Debian Bug report #1029875, regarding plasma-sdk: Wait for the resolution of the libkscreen transition before migrating to testing to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#1029873: marked as done (plasma-systemmonitor: Wait for the resolution of the libkscreen transition before migrating to testing)

Your message dated with message-id and subject line has caused the Debian Bug report #1029873, regarding plasma-systemmonitor: Wait for the resolution of the libkscreen transition before migrating to testing to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1029871: marked as done (powerdevil: Wait for the resolution of the libkscreen transition before migrating to testing)

Your message dated with message-id and subject line has caused the Debian Bug report #1029871, regarding powerdevil: Wait for the resolution of the libkscreen transition before migrating to testing to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#1029869: marked as done (kscreen: Wait for the resolution of the libkscreen transition before migrating to testing)

Your message dated with message-id and subject line has caused the Debian Bug report #1029869, regarding kscreen: Wait for the resolution of the libkscreen transition before migrating to testing to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#1029868: marked as done (plasma-integration: Wait for the resolution of the libkscreen transition before migrating to testing)

Your message dated with message-id and subject line has caused the Debian Bug report #1029868, regarding plasma-integration: Wait for the resolution of the libkscreen transition before migrating to testing to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1029870: marked as done (plasma-remotecontrollers: Wait for the resolution of the libkscreen transition before migrating to testing)

Your message dated with message-id and subject line has caused the Debian Bug report #1029870, regarding plasma-remotecontrollers: Wait for the resolution of the libkscreen transition before migrating to testing to be marked as done. This means that you claim that the problem has been dealt

Bug#1029867: marked as done (plasma-browser-integration: Wait for the resolution of the libkscreen transition before migrating to testing)

Your message dated with message-id and subject line has caused the Debian Bug report #1029867, regarding plasma-browser-integration: Wait for the resolution of the libkscreen transition before migrating to testing to be marked as done. This means that you claim that the problem has been dealt

Bug#1029866: marked as done (plasma-thunderbolt: Wait for the resolution of the libkscreen transition before migrating to testing)

Your message dated with message-id and subject line has caused the Debian Bug report #1029866, regarding plasma-thunderbolt: Wait for the resolution of the libkscreen transition before migrating to testing to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1029865: marked as done (plasma-pa: Wait for the resolution of the libkscreen transition before migrating to testing)

Your message dated with message-id and subject line has caused the Debian Bug report #1029865, regarding plasma-pa: Wait for the resolution of the libkscreen transition before migrating to testing to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#1029864: marked as done (plasma-nano: Wait for the resolution of the libkscreen transition before migrating to testing)

Your message dated with message-id and subject line has caused the Debian Bug report #1029864, regarding plasma-nano: Wait for the resolution of the libkscreen transition before migrating to testing to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#1029863: marked as done (plasma-workspace-wallpapers: Wait for the resolution of the libkscreen transition before migrating to testing)

Your message dated with message-id and subject line has caused the Debian Bug report #1029863, regarding plasma-workspace-wallpapers: Wait for the resolution of the libkscreen transition before migrating to testing to be marked as done. This means that you claim that the problem has been

Bug#1029862: marked as done (kdecoration: Wait for the resolution of the libkscreen transition before migrating to testing)

Your message dated with message-id and subject line has caused the Debian Bug report #1029862, regarding kdecoration: Wait for the resolution of the libkscreen transition before migrating to testing to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#1029861: marked as done (breeze-grub: Wait for the resolution of the libkscreen transition before migrating to testing)

Your message dated with message-id and subject line has caused the Debian Bug report #1029861, regarding breeze-grub: Wait for the resolution of the libkscreen transition before migrating to testing to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#1029859: marked as done (plasma-vault: Wait for the resolution of the libkscreen transition before migrating to testing)

Your message dated with message-id and subject line has caused the Debian Bug report #1029859, regarding plasma-vault: Wait for the resolution of the libkscreen transition before migrating to testing to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#1029858: marked as done (polkit-kde-agent-1: Wait for the resolution of the libkscreen transition before migrating to testing)

Your message dated with message-id and subject line has caused the Debian Bug report #1029858, regarding polkit-kde-agent-1: Wait for the resolution of the libkscreen transition before migrating to testing to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1029857: marked as done (breeze-plymouth: Wait for the resolution of the libkscreen transition before migrating to testing)

Your message dated with message-id and subject line has caused the Debian Bug report #1029857, regarding breeze-plymouth: Wait for the resolution of the libkscreen transition before migrating to testing to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1029860: marked as done (kwin: Wait for the resolution of the libkscreen transition before migrating to testing)

Your message dated with message-id and subject line has caused the Debian Bug report #1029860, regarding kwin: Wait for the resolution of the libkscreen transition before migrating to testing to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#1029856: marked as done (plasma-nm: Wait for the resolution of the libkscreen transition before migrating to testing)

Your message dated with message-id and subject line has caused the Debian Bug report #1029856, regarding plasma-nm: Wait for the resolution of the libkscreen transition before migrating to testing to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#1029855: marked as done (plasma-disks: Wait for the resolution of the libkscreen transition before migrating to testing)

Your message dated with message-id and subject line has caused the Debian Bug report #1029855, regarding plasma-disks: Wait for the resolution of the libkscreen transition before migrating to testing to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#1029854: marked as done (kwayland-integration: Wait for the resolution of the libkscreen transition before migrating to testing)

Your message dated with message-id and subject line has caused the Debian Bug report #1029854, regarding kwayland-integration: Wait for the resolution of the libkscreen transition before migrating to testing to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1029877: marked as done (ksystemstats: Wait for the resolution of the libkscreen transition before migrating to testing)

Your message dated with message-id and subject line has caused the Debian Bug report #1029877, regarding ksystemstats: Wait for the resolution of the libkscreen transition before migrating to testing to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#1029853: marked as done (bluedevil: Wait for the resolution of the libkscreen transition before migrating to testing)

Your message dated with message-id and subject line has caused the Debian Bug report #1029853, regarding bluedevil: Wait for the resolution of the libkscreen transition before migrating to testing to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#1029888: marked as done (plasma-firewall: Wait for the resolution of the libkscreen transition before migrating to testing)

Your message dated with message-id and subject line has caused the Debian Bug report #1029888, regarding plasma-firewall: Wait for the resolution of the libkscreen transition before migrating to testing to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1029890: marked as done (milou: Wait for the resolution of the libkscreen transition before migrating to testing)

Your message dated with message-id and subject line has caused the Debian Bug report #1029890, regarding milou: Wait for the resolution of the libkscreen transition before migrating to testing to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#1029872: marked as done (ksshaskpass: Wait for the resolution of the libkscreen transition before migrating to testing)

Your message dated with message-id and subject line has caused the Debian Bug report #1029872, regarding ksshaskpass: Wait for the resolution of the libkscreen transition before migrating to testing to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#1029881: marked as done (sddm-kcm: Wait for the resolution of the libkscreen transition before migrating to testing)

Your message dated with message-id and subject line has caused the Debian Bug report #1029881, regarding sddm-kcm: Wait for the resolution of the libkscreen transition before migrating to testing to be marked as done. This means that you claim that the problem has been dealt with. If this is