Bug#977119: okular: Please package 20.12.0
Package: src:okular Severity: wishlist Tags: patch X-Debbugs-Cc: aeru...@aerusso.net Dear Maintainer, I've taken a stab at updating the packaging for okular [1]. I'd very much like to get okular 20.12.0 ASAP, since it fixes some painful regressions for me. Best, Antonio Russo [1] https://salsa.debian.org/qt-kde-team/kde/okular/-/merge_requests/6 OpenPGP_0xB01C53D5DED4A4EE.asc Description: application/pgp-keys OpenPGP_signature Description: OpenPGP digital signature
print-manager_20.12.0-1_amd64.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 10 Dec 2020 23:03:51 +0100 Source: print-manager Architecture: source Version: 4:20.12.0-1 Distribution: unstable Urgency: medium Maintainer: Debian/Kubuntu Qt/KDE Maintainers Changed-By: Aurélien COUDERC Changes: print-manager (4:20.12.0-1) unstable; urgency=medium . [ Pino Toscano ] * Update lintian overrides. * Bump Standards-Version to 4.5.1, no changes required. . [ Aurélien COUDERC ] * New upstream release (20.12.0). * Update build dependencies according to upstream build system: - remove libkf5iconthemes-dev * Upstream metadata: remove Contact field, already in machine readable copyright. * Add missing runtime QML dependencies: - qml-module-org-kde-kquickcontrolsaddons - qml-module-qtquick-controls - qml-module-qtquick-layouts - qml-module-qtquick2 Checksums-Sha1: e67fbab5b5b9292afa461c951bbd4772191bf409 2969 print-manager_20.12.0-1.dsc 53859f3f4ccb302988a2655836c10199e91cf200 258180 print-manager_20.12.0.orig.tar.xz f6f920619e24b11d8b235ed09bff4842cf8083da 488 print-manager_20.12.0.orig.tar.xz.asc 80f8623e08c2138580886d1d982e7f2b7b0f06bf 11824 print-manager_20.12.0-1.debian.tar.xz 52103470b0ed3fa8fea2e0fd9a8f53fa7ae8594a 23744 print-manager_20.12.0-1_amd64.buildinfo Checksums-Sha256: 40f8dfef67757bf4bb2e87deb5fceba824694b1ed01b9e5edde804014304fcfe 2969 print-manager_20.12.0-1.dsc da373dbc907eda513ee8d41b8b2b3a118d390bae62b829c77076f63b1c3168d3 258180 print-manager_20.12.0.orig.tar.xz 0b36afcdd9cb2488553f7d69e2dffc1cd52a5a21db26398e5c61dddb4673f611 488 print-manager_20.12.0.orig.tar.xz.asc 2573fe94356f7ebd4053318e64b2a4b3df6d1353fdf429c71f5dddeb9dd4df75 11824 print-manager_20.12.0-1.debian.tar.xz fb33153ab4cdb01a6acee31b40449db025c95fd47252d085b8c87aa64a99ee06 23744 print-manager_20.12.0-1_amd64.buildinfo Files: c5610c9fc726d352e2c382fdd27f31ae 2969 kde optional print-manager_20.12.0-1.dsc a790b964d4154033d17bd42afe5c7dba 258180 kde optional print-manager_20.12.0.orig.tar.xz c61457dd786f63c05dc027c5d0c03b44 488 kde optional print-manager_20.12.0.orig.tar.xz.asc 63055d502db3a528883d4130b42e2a81 11824 kde optional print-manager_20.12.0-1.debian.tar.xz fe32f53e0ebcddb12beff31e3746e7b6 23744 kde optional print-manager_20.12.0-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCgAxFiEEIW//QAAaDgcOKDsfcaflM/KRoyQFAl/So/cTHGNvdWNvdWZA ZGViaWFuLm9yZwAKCRBxp+Uz8pGjJAFZEACQnq5z8vEnBsTIo0Jx4lwddu4KNqhN WMi7XjH8zN7UvAmXg36eU2ndUCuj93yXvk8keuyKbPuagoLsIVGqmKW+Gftffq8v LhnYSUXonKsF1Hn8xOxDJh40zXsY/yB8nQ9fZ8QjEs6p+O6M18IAPQsUcZuAuCZS Y+p1JCP0UOVpaNXCecXXJ1etq7ZgAvleh5W+Ov5/36U6BY2lNVnfXMafNFmQEIup 9rEFp/QxkYqEf4kbYMldY0Fuygn8xW4RKds1L3VNXu2EzzGDbU+4t8fNCCiVNJ9T 8rcAxuyrQbc4WE6a73CSytl58ps7OhQtvxT9rR9pub/P9BCtdIwjSMHT6QPXQQ4I WXc0Wr5kzffTFYaT/p01ZVGYDaLuxrGz8NzhTO50ovg1lX67anvTh2vgT4LZZku7 pSHxdM4o2bYVWh3q6C3A4gVekg+drnKnwpkuzA5fBLohewE8/VmyHdkvh/FAxsdE +c/LU++TH49/iROkJw1z+1nqovbttlQVu3fgH8L3D80EV+wSyw3BUE7aEJR1E+Nj A+A6XO1jMBK6clXlFlW45Z5EgIGJPMx6LGgevZ9qocxGCULpv3u8tHh7BC5ceUE4 MbG//++GnBLnrxgl1J8Fgdgey0I62tLtKnBrBhEgXUZ/dKasLYdnbjMjid8MhqgQ izbX8qsaomH1xg== =CH6S -END PGP SIGNATURE- Thank you for your contribution to Debian.
Processing of print-manager_20.12.0-1_amd64.changes
print-manager_20.12.0-1_amd64.changes uploaded successfully to localhost along with the files: print-manager_20.12.0-1.dsc print-manager_20.12.0.orig.tar.xz print-manager_20.12.0.orig.tar.xz.asc print-manager_20.12.0-1.debian.tar.xz print-manager_20.12.0-1_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
dragon_20.12.0-1_amd64.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 10 Dec 2020 23:35:15 +0100 Source: dragon Architecture: source Version: 4:20.12.0-1 Distribution: unstable Urgency: medium Maintainer: Debian/Kubuntu Qt/KDE Maintainers Changed-By: Aurélien COUDERC Changes: dragon (4:20.12.0-1) unstable; urgency=medium . * New upstream release (20.12.0). * Add myself to the uploaders. * Update build dependencies according to upstream build system: - Qt >= 5.12 - KDE Frameworks >= 5.66 * Refresh upstream metadata: - drop Contact and Name fields already present in machine readable copyright - move VCS URLs to invent.kde.org * Fix Source URL in machine readable copyright. * Bump Standards-Version to 4.5.1 (no change needed). * Update project homepage. * Add salsa-ci.yml GitLab CI/CD pipeline. Checksums-Sha1: 1707630ffb26bcc1053e342150a0e30808d1a89e 2930 dragon_20.12.0-1.dsc 1b01b95324da4345fb5ba9df6ca1931decfba48c 1656524 dragon_20.12.0.orig.tar.xz 69a88466e20dea1ff0e0e6cb03d28ac2c7b7b7b5 488 dragon_20.12.0.orig.tar.xz.asc 83e75c0e6a052c71a618a12061b6318c61ce1768 7812 dragon_20.12.0-1.debian.tar.xz f7cb034a957ae8ef2997a43c665ef2fe24da7c67 21342 dragon_20.12.0-1_amd64.buildinfo Checksums-Sha256: bfbd85036d95faa4264d04b887d9789a4786c2be7a68fbfabe049f24f519e5a8 2930 dragon_20.12.0-1.dsc 4462fd75fde78dc8a7c97d2e93e502902d6076c2f2d78021354b359ed4a07c24 1656524 dragon_20.12.0.orig.tar.xz 92b4f6b1fc4fffefa326439002fe50a06894d27175dcce00d0716503a445ba7b 488 dragon_20.12.0.orig.tar.xz.asc 7463888d14856b5b287794ca1aba7b0464a41d8165c1ef3b59437b8e77098925 7812 dragon_20.12.0-1.debian.tar.xz 2bac9bd71821aac84dfbb0d653d4c02ff81343d735f100b8a9f490eae17bb4fe 21342 dragon_20.12.0-1_amd64.buildinfo Files: 27bd9f8335cd82a707c8f1e2843c5c5f 2930 kde optional dragon_20.12.0-1.dsc 1660a9d7ac1cd1b3e633a4eed950e5d3 1656524 kde optional dragon_20.12.0.orig.tar.xz 4577978c9e78c07bc103419c0ba8eac2 488 kde optional dragon_20.12.0.orig.tar.xz.asc 6cbfc6b852cc6297b7586d7a906ec5fe 7812 kde optional dragon_20.12.0-1.debian.tar.xz d7135c18b214dde8c5ffe35fa059c435 21342 kde optional dragon_20.12.0-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCgAxFiEEIW//QAAaDgcOKDsfcaflM/KRoyQFAl/Sou0THGNvdWNvdWZA ZGViaWFuLm9yZwAKCRBxp+Uz8pGjJEOBD/9iMXi8BxXPBNNQdAs/rpMZwNiyd4tn 32iIRvJyTZ2dkIZd7cm9+Qm6oBW2Oo028iUnSv/kKRfu8Oo5S2feW7aiZ4GO11cZ 0iObCm8kUV2B1dHZJ9UA76gehO1P/2dCrY8jYyz2KgBgUPGg/adV6prap/skWEIn eUQg+GQgqMEcw55fT5UV4esRDZNsCY43fVB4sp5/THOcmyylKdMmIsDU3HBqgGSy TIIyDAtb3CW9gP3k4PiHkXc/akJXYmTgLaKHYIryUDORcMkZufbcH/9xkkPGKYgQ 61x2czhNG54XWrBDxPYpP2yazEsU9Qn3atQ5bjc9vjfZyimeq8Fm8Ei8k5VqOdq3 vg3o8FfXMCdLEWO5TKGMLXKuXMxyUpJIqnPcwd0iVMLrhskWwKGhz6sF/jwfj+Xc W3PqzweV28B5BpcKo3dx2aWIhh/hFyt9jDoXLm3GVE/Dvv5ifPEoDpPgVmqiyh8k dItZZWpJbMg0u7qQaY0GeUHmGGGw8i99k84nZ2UzH0bclF++83fIcGOF0rp+o0E6 mEC0WZN7fwFTHUVdiRKaVAPFjil2mjgdzwGTaceM28Jr15Ej2GufO1sL57evpLwz hQlPVDZ23VwLUZK/ktsb8MRen7f8OL5URdvTnFiXBhsETNEPTpQb4etGPlU6sMIa zRoUxVS+yBOfTg== =+QIa -END PGP SIGNATURE- Thank you for your contribution to Debian.
Processing of dragon_20.12.0-1_amd64.changes
dragon_20.12.0-1_amd64.changes uploaded successfully to localhost along with the files: dragon_20.12.0-1.dsc dragon_20.12.0.orig.tar.xz dragon_20.12.0.orig.tar.xz.asc dragon_20.12.0-1.debian.tar.xz dragon_20.12.0-1_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
ktouch_20.12.0-2_amd64.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 10 Dec 2020 23:00:36 +0100 Source: ktouch Architecture: source Version: 4:20.12.0-2 Distribution: unstable Urgency: medium Maintainer: Debian/Kubuntu Qt/KDE Maintainers Changed-By: Aurélien COUDERC Changes: ktouch (4:20.12.0-2) unstable; urgency=medium . * Fix runtime dependencies: - Should be on bin package not on data package. - Add min versions to all Qt and KF5 dependencies, according to upstream build system. Checksums-Sha1: b6b9871bb914d3d5759308b1a6873d721b6735a2 3000 ktouch_20.12.0-2.dsc cae46a248f2f9afa41f1cb4dd1c8754cfac2f250 9004 ktouch_20.12.0-2.debian.tar.xz aa930d3e9ceff1a70b8a1872912ad094d6f10b6d 22011 ktouch_20.12.0-2_amd64.buildinfo Checksums-Sha256: 8bab0e6557b28223a318ee3295c2384937632c45c7df1f495bd98601f955944c 3000 ktouch_20.12.0-2.dsc 8e0a4ee02a2b5f1f6d194e4e0a16bb3ee0166dbc392700f2d91b6f19005fa2d4 9004 ktouch_20.12.0-2.debian.tar.xz 90590bb5da2ee6da9d4b52a94a0824f8b300cf3b19ce081b468cc309b1488709 22011 ktouch_20.12.0-2_amd64.buildinfo Files: c4ac2d97efaf0ab43b7081220a98ea74 3000 kde optional ktouch_20.12.0-2.dsc 602299303acbab933f5b5a99fe615733 9004 kde optional ktouch_20.12.0-2.debian.tar.xz 72856903f134bf4cb1b5838af17d9b2c 22011 kde optional ktouch_20.12.0-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCgAxFiEEIW//QAAaDgcOKDsfcaflM/KRoyQFAl/SmwsTHGNvdWNvdWZA ZGViaWFuLm9yZwAKCRBxp+Uz8pGjJMbHEADRwspcKhXbsWr2JXfSbM43+y3EArg0 VEHQ0WTRQtxTfotakHym+FsSF5+cS38unYwKafNmjKb+tOu/nKDkyFDfzTgBNJM5 ObhQ10CDue4iKJmXN1LK/LJOEMMl5lq9oy0OKWpkRSrliO3TJglu97jJuLy6gLdj zJ9elsO0KvjBTVnRcD6AgA0axTzN9fmtT75ESF1aXJz6OH77M/RdYuhcgWc8IK2G cSs/Ev2o3a+ESi3KUzURs50mfGjurEKS6+wC1yv2glJaBNEaKcVG6tPgpkqDkpmC zBuuEH3cb95Ip1i58M1yqg2VFIZb7Qe+QzIvOUs0ctu1PZkGAzXWb4z9WEpQBQqo XnSs4wgOyrR2fxrobIj87lloWvjqgdyEapB/eB5RYWdSQHeZOXz8PluzVheOXud8 GIyyKF1B0vXOeDKsaMhf2RbsvEcRP9Ol+BsC71jOL7/eDve2BM7d4GOiCGOaLX+/ PhTYlXJK/57ME8P28w3mKLmq6N6jvSkboxkqnxOvBEAAxItwJfENN7r00cmLi+dq zqZ0wV4aWgzEys1qAtAOHA5edMSREUqNlOfwxZQJRe3ElLBG7Mzos3Df/wRNWDnW ZeFkQNIp4a3PPjSGLSeIWwaQIeLIxPWR9qL2fSIBYmha9q4lUwvORR5hSiUqTabV i2LJDit4KkaRbQ== =bjDE -END PGP SIGNATURE- Thank you for your contribution to Debian.
Re: KDE Plasma LTS for Debian stable
Simon Frei - 10.12.20, 18:46:16 CET: > I understand the question as why is debian targeting 5.20 for the next > stable instead of 5.18 LTS. The answer is simple: LTS means 1.5 year > of support, maybe more [1]. That's not long enough for the debian > release cycle: 5.18 was at the beginning of this year. That means > support will end at about the time or shortly after the next debian > stable will be released. Basically as far as I am aware Debian Qt/KDE team never actually cared about that a Plasma LTS release would be used. In the end, critical fixes could be forward- or backported from an LTS release to whatever version Debian stable will have. And after end of LTS, a forward- or backport of a fix would be needed anyway. Also AFAIR this has been discussed here or on another Debian KDE related mailing list before. Best, -- Martin
Processing of ktouch_20.12.0-2_amd64.changes
ktouch_20.12.0-2_amd64.changes uploaded successfully to localhost along with the files: ktouch_20.12.0-2.dsc ktouch_20.12.0-2.debian.tar.xz ktouch_20.12.0-2_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
ktouch_20.12.0-1_amd64.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 10 Dec 2020 22:06:30 +0100 Source: ktouch Architecture: source Version: 4:20.12.0-1 Distribution: unstable Urgency: medium Maintainer: Debian/Kubuntu Qt/KDE Maintainers Changed-By: Aurélien COUDERC Changes: ktouch (4:20.12.0-1) unstable; urgency=medium . * New upstream release (20.12.0). * Update build dependencies according to upstream build system: - remove libkf5declarative-dev * Bump Standards-Version to 4.5.1 (no change needed). * Refresh upstream metadata: - drop Contact and Name fields already present in machine readable copyright - move VCS URLs to invent.kde.org * Adjust runtime dependencies on QML modules: - drop unused qml-module-qtquick-controls - add missing qml-module-qtquick-window2 * Update project homepage. * Add salsa-ci.yml GitLab CI/CD pipeline. Checksums-Sha1: ba54f5c96122a9c4be5e058e1e11877a66c9446a 2828 ktouch_20.12.0-1.dsc c2089cf6b8df66c7a1ff80b53de2ecb9271add53 4940596 ktouch_20.12.0.orig.tar.xz 7f5f8abc8464988f3e318214c2a3a6da028d1411 488 ktouch_20.12.0.orig.tar.xz.asc 7017559bd6cab28d94701f48f9d7db71e7f4c9a7 8924 ktouch_20.12.0-1.debian.tar.xz 8275c1e75c9b1907441c4d253d7578213b99291f 22011 ktouch_20.12.0-1_amd64.buildinfo Checksums-Sha256: 7d19091933a1ecb6abf7ba3aa0a6ce86ba2d8cd083971d8f82003b5ed9104a54 2828 ktouch_20.12.0-1.dsc 22ae749d176ab2aba408f670579bd993c84156d1d757e9ddf38aa43e156717e9 4940596 ktouch_20.12.0.orig.tar.xz 91a42ba9e76857d13dca556e91442ef100f65e0c9e425857a5dd59fd11d16926 488 ktouch_20.12.0.orig.tar.xz.asc 9aadf44ddbf66cffb3428426b819f2d79a8741b382ecfda484dc83ad978cfee8 8924 ktouch_20.12.0-1.debian.tar.xz b0ace670604147ee6fd3c0ca5e5da67ecba2cdaebaa61481d0ff5d034e560a06 22011 ktouch_20.12.0-1_amd64.buildinfo Files: 611632430bd895d6cd7ed91b4610845f 2828 kde optional ktouch_20.12.0-1.dsc 78b37ec268abc01a6dcdb20133834b43 4940596 kde optional ktouch_20.12.0.orig.tar.xz 6eace1ecf6ba079fb8559ab066c00965 488 kde optional ktouch_20.12.0.orig.tar.xz.asc 8e7924072e3f89f658a5107a2fb7ea5b 8924 kde optional ktouch_20.12.0-1.debian.tar.xz 249ef9d8124659d9a6e348d6fe4ce3d0 22011 kde optional ktouch_20.12.0-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCgAxFiEEIW//QAAaDgcOKDsfcaflM/KRoyQFAl/SjhkTHGNvdWNvdWZA ZGViaWFuLm9yZwAKCRBxp+Uz8pGjJGYgD/0Zn9p858FDxkIsxtDVGaIwmscbT7N5 VSJN2dWSOB7HtXIEdnITYAa28Sr2wLkED6t87dHeOpfF5UxUSYFB68CBQ2Hlk4QC xTVHOhxUJpvTx0Y+E2vAAw+9FP+hKnT8rTCpoSR7EV4X3o0bWN6HmVZeF244IEIP PRxzYo4wUzLJJfCQ1xZDDYjAtEqN4u1fYyn2nRgHnJFkGZbT19+yavpMc0+hLJ46 visLN4u1nRNXvaUYCAiFdUnPdmDr3KXHyV0YGRsWCr6AF4hEXiirkLf3JQ0Wo2jr JnTvcRfjgmfOD9oypdh9BVZZVjDlOG9/QAILo5YexksbLkiv4kiFInzoXc10M+VU BYBMeNmwwKJ6ccpr2wPIdgi/+i7S7S2UCZaE7NUT25PxjBlIZVhgchmS5J2aeJVw naImHEHa/83jIjJWVnDiQG+NAbIEviUe8/+UVewY0Vuw/ZtQ65Jgs4w0uX1oT+bJ VvaVOIl8YMe98QBk7F7Z5nNr2r0zOHkRY55GxHtZtC6ZaNqpBRgwuZDsYmUHlGBi GV44gt8RO0G+TLJWouV5YJr7fmXJ2tRyfagm5a7fpsxOlh6a6pt8N/9PKj+jjDEY Wzb+oeH+oKaJpAMYP2faGKBk6gRX2cjHpjyPoXSiSZuvRnkxFkcflcf/A10zFxcS xKMV4HugVpWvYA== =DAgR -END PGP SIGNATURE- Thank you for your contribution to Debian.
Processing of ktouch_20.12.0-1_amd64.changes
ktouch_20.12.0-1_amd64.changes uploaded successfully to localhost along with the files: ktouch_20.12.0-1.dsc ktouch_20.12.0.orig.tar.xz ktouch_20.12.0.orig.tar.xz.asc ktouch_20.12.0-1.debian.tar.xz ktouch_20.12.0-1_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
kde-spectacle_20.12.0-1_amd64.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 10 Dec 2020 19:45:15 +0100 Source: kde-spectacle Architecture: source Version: 20.12.0-1 Distribution: unstable Urgency: medium Maintainer: Debian/Kubuntu Qt/KDE Maintainers Changed-By: Aurélien COUDERC Changes: kde-spectacle (20.12.0-1) unstable; urgency=medium . [ Pino Toscano ] * Switch the transitional libxcb-util0-dev build dependency to libxcb-util-dev. * Bump Standards-Version to 4.5.1, no changes required. . [ Aurélien COUDERC ] * New upstream release (20.12.0). * Update the build dependencies according to the upstream build system: - bump KF packages to 5.73.0 - add libqt5svg5-dev - add libkcolorpicker-dev and libkimageannotator-dev * Update project homepage. * Refresh copyright information. Checksums-Sha1: cc34bddae17a941c266f88523990900a8b8e4027 3216 kde-spectacle_20.12.0-1.dsc 569a216227c2baf119a3b7e479e56fc7b080c167 1163508 kde-spectacle_20.12.0.orig.tar.xz 43f40b2431b2f4b073f8af7c343cd674f4c5c03f 488 kde-spectacle_20.12.0.orig.tar.xz.asc 3bd12b5ea8fd03f7c723bc1c59ae1f5b1aaf58f4 7592 kde-spectacle_20.12.0-1.debian.tar.xz ae4fdb8c42b7e38dfbb01cf030f7213ea65dcf65 23098 kde-spectacle_20.12.0-1_amd64.buildinfo Checksums-Sha256: 75b308c25f0db2eae471384eb631e0b9051b4e4e25863db4686bb6d90be031b2 3216 kde-spectacle_20.12.0-1.dsc 0efa48c9646c8df804d2dd474fbce7f131f3918d9acd10e43cf983f699768e1a 1163508 kde-spectacle_20.12.0.orig.tar.xz c2c82bd971847eb77193c4160239aed24f1d7b767861e6128f806b2aa7b4c226 488 kde-spectacle_20.12.0.orig.tar.xz.asc f73b6d5b441df43dbe557d90747d802682b808a8a889298b8001ce1c3d57770b 7592 kde-spectacle_20.12.0-1.debian.tar.xz 03b4e63f06d74eb0bdbc5f3a6e28ab054b981f22448c52841a42fd16a5f3c01a 23098 kde-spectacle_20.12.0-1_amd64.buildinfo Files: c142deb230fd74316478cc962639f653 3216 kde optional kde-spectacle_20.12.0-1.dsc 576450a5d44d6d2195201cc296009632 1163508 kde optional kde-spectacle_20.12.0.orig.tar.xz 3600e66d68c3f3de2c44660115286011 488 kde optional kde-spectacle_20.12.0.orig.tar.xz.asc b09189dcbfacb9482dfd62d042c40ebf 7592 kde optional kde-spectacle_20.12.0-1.debian.tar.xz 181eb93c9ade7434bab1f67092aed614 23098 kde optional kde-spectacle_20.12.0-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCgAxFiEEIW//QAAaDgcOKDsfcaflM/KRoyQFAl/SgYwTHGNvdWNvdWZA ZGViaWFuLm9yZwAKCRBxp+Uz8pGjJF6wD/0dxObWRJprXaWtkralqYIdqWbmaMc4 uqazqL6yZEPqVPPT65b4tEdlVM84iqLeGlUx6Yi9+8EXlF4s5vFLoN9rqgUXrTJs Gv3PBh34v1KZOZEY1sHqeXeQX9JgtkidTGhpnA4Q1XjVXN3unYeWw6cwjuVMt6EE G5VLPKHO1xxUcyoW+wCt/wfNC3K8JReCiw9WbHRdasD45lucCNF3qJqtRD0NVtRw UVrA1iYcQM0ECvJvnY2Rww/yx+RtZfIH3FiBBNXF9cB/ocs7GZk+H1QsxeQwnpwM qKdHC2pLh5EgIwwH7zXe13PTQtuazBpTFGbfXrpytBYDW8kald9xu54tr9kH6q2K Avuq9b0cJlXYhF8R1HgxRQX/UTMEttT8auypGtXOZoENqNBClmGamhI2g+U9WzsN PNQirBcOGrUmq598KbZxqMKTCGe/HiINDECbD/nuPElChSRDw/4YvKPcxWVw0FmO PHXUOjhgfF1t/AICrzcUQJzt1xyFNUr+ISR5sp76U3v3Q2b/3WzPcWH7yYCmpUvu h/kVCZhsjB01bENUf3pL/18G64D/tk3lfotJK/f7+svnY/CNJuzjcwCv0Ly5if5i SET0KuVaQsHsqjzFgqFLKOyGrTDVW+TMOH+pB82AuAscacrcjpMNm0r7m7e0ETfO zxy4Au5qcjIUeQ== =MnGw -END PGP SIGNATURE- Thank you for your contribution to Debian.
Processing of kde-spectacle_20.12.0-1_amd64.changes
kde-spectacle_20.12.0-1_amd64.changes uploaded successfully to localhost along with the files: kde-spectacle_20.12.0-1.dsc kde-spectacle_20.12.0.orig.tar.xz kde-spectacle_20.12.0.orig.tar.xz.asc kde-spectacle_20.12.0-1.debian.tar.xz kde-spectacle_20.12.0-1_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
Re: KDE Plasma LTS for Debian stable
I get that, and really I think Debian should target LTS with pretty much everything. Unfortunately in my opinion KDE is kind of in a bad state right now with regards to wayland. The newest versions offer a much better experience for people want a modern desktop with better touch support, etc. For instance, I'm using 5.20 on my xps 13 with wayland because I want the touch screen to be better supported. Unfortunately Kontact, trackpad scrolling, and other bugs are making the experience pretty rough under wayland, even on 5.20. I don't think going backwards to 5.18 is going to fix that as those bugs and issues were even worse there. Really I wish that KDE could be kept more up-to-date throughout the life cycle of stable. It feels like if you have a bug in KDE, you're generally going to have to deal with that bug until the next stable, which is why I'm hoping for the newest possible release we can get. As it stands I may even continue to track testing with my laptop simply because I want the 5.21 changes. On Thursday, December 10, 2020 12:46:16 PM EST Simon Frei wrote: On 10/12/2020 18:12, Joe McEntire wrote: > I don't know where this information is coming from, but 5.19.5 is in testing > right now. Experimental has 5.20 and there's talk of getting 5.20.5 in time > for the freeze, so we'll probably end up with some iteration of 5.20 in stable > if I had to take a stab at it. I cannot imagine a world where Debian's KDE > team puts in all the work to get these newer versions in, just to roll back to > something that is older than what is in current stable. Current stable > (Buster) uses 5.14! So rest easy, there's no way we're going to have 5.12 or > 5.8 in stable, it's just not a thing. > > https://tracker.debian.org/pkg/kwin > I understand the question as why is debian targeting 5.20 for the next stable instead of 5.18 LTS. The answer is simple: LTS means 1.5 year of support, maybe more [1]. That's not long enough for the debian release cycle: 5.18 was at the beginning of this year. That means support will end at about the time or shortly after the next debian stable will be released. [1] https://community.kde.org/Schedules/Plasma_5#LTS_releases -- Thanks, Joe McEntire j...@emberlife.com
Re: KDE Plasma LTS for Debian stable
On 10/12/2020 18:12, Joe McEntire wrote: > I don't know where this information is coming from, but 5.19.5 is in testing > right now. Experimental has 5.20 and there's talk of getting 5.20.5 in time > for the freeze, so we'll probably end up with some iteration of 5.20 in > stable > if I had to take a stab at it. I cannot imagine a world where Debian's KDE > team puts in all the work to get these newer versions in, just to roll back > to > something that is older than what is in current stable. Current stable > (Buster) uses 5.14! So rest easy, there's no way we're going to have 5.12 or > 5.8 in stable, it's just not a thing. > > https://tracker.debian.org/pkg/kwin > I understand the question as why is debian targeting 5.20 for the next stable instead of 5.18 LTS. The answer is simple: LTS means 1.5 year of support, maybe more [1]. That's not long enough for the debian release cycle: 5.18 was at the beginning of this year. That means support will end at about the time or shortly after the next debian stable will be released. [1] https://community.kde.org/Schedules/Plasma_5#LTS_releases
Re: KDE Plasma LTS for Debian stable
Hi Joe, I know KDE platform of Debian testing (Bullseye) version is ahead. I was just talking about the past (Buster) and about that approach. It's great the KDE platform is moving on the edge of the versions, but i think we should consider freeze policy for Debian stable release. Maybe it is possible to connecting between KDE Plasma and Debian KDE to match the KDE LTS version with Debian stable. On 12/10/20 8:42 PM, Joe McEntire wrote: On Thursday, December 10, 2020 11:08:59 AM EST you wrote: On Thu, Dec 10, 2020 at 07:20:18PM +0330, peylight wrote: Hi Andy, You are talking about freeze timeline and policies. Please look at this document for that: https://release.debian.org/buster/freeze_policy.html The time and date is defined and any programmer can planning for it. I check the LTS versions of KDE and what can i see Debian choose is v5.14, that is not the LTS version. How ever Debian could choose v5.12 LTS or even v5.8 LTS for bug fixes and security issues. I think Debian should be change the approach for more KDE Desktop stability as for the kernel has taken this approach. If Debian keeps years-old KDE in unstable I'll stop using it, tbh. I don't know where this information is coming from, but 5.19.5 is in testing right now. Experimental has 5.20 and there's talk of getting 5.20.5 in time for the freeze, so we'll probably end up with some iteration of 5.20 in stable if I had to take a stab at it. I cannot imagine a world where Debian's KDE team puts in all the work to get these newer versions in, just to roll back to something that is older than what is in current stable. Current stable (Buster) uses 5.14! So rest easy, there's no way we're going to have 5.12 or 5.8 in stable, it's just not a thing. https://tracker.debian.org/pkg/kwin -- Best Regards, peylight
Re: KDE Plasma LTS for Debian stable
On Thu, Dec 10, 2020 at 12:12:53PM -0500, Joe McEntire wrote: > > On Thursday, December 10, 2020 11:08:59 AM EST you wrote: > > On Thu, Dec 10, 2020 at 07:20:18PM +0330, peylight wrote: > > > Hi Andy, > > > You are talking about freeze timeline and policies. > > > Please look at this document for that: > > > https://release.debian.org/buster/freeze_policy.html > > > The time and date is defined and any programmer can planning for it. > > > I check the LTS versions of KDE and what can i see Debian choose is v5.14, > > > that is not the LTS version. > > > How ever Debian could choose v5.12 LTS or even v5.8 LTS for bug fixes and > > > security issues. > > > I think Debian should be change the approach for more KDE Desktop > > > stability > > > as for the kernel has taken this approach. > > > > If Debian keeps years-old KDE in unstable I'll stop using it, tbh. > > I don't know where this information is coming from This suggestion comes from the email I was replying to. -- WBR, wRAR signature.asc Description: PGP signature
Re: KDE Plasma LTS for Debian stable
On Thursday, December 10, 2020 11:08:59 AM EST you wrote: > On Thu, Dec 10, 2020 at 07:20:18PM +0330, peylight wrote: > > Hi Andy, > > You are talking about freeze timeline and policies. > > Please look at this document for that: > > https://release.debian.org/buster/freeze_policy.html > > The time and date is defined and any programmer can planning for it. > > I check the LTS versions of KDE and what can i see Debian choose is v5.14, > > that is not the LTS version. > > How ever Debian could choose v5.12 LTS or even v5.8 LTS for bug fixes and > > security issues. > > I think Debian should be change the approach for more KDE Desktop > > stability > > as for the kernel has taken this approach. > > If Debian keeps years-old KDE in unstable I'll stop using it, tbh. I don't know where this information is coming from, but 5.19.5 is in testing right now. Experimental has 5.20 and there's talk of getting 5.20.5 in time for the freeze, so we'll probably end up with some iteration of 5.20 in stable if I had to take a stab at it. I cannot imagine a world where Debian's KDE team puts in all the work to get these newer versions in, just to roll back to something that is older than what is in current stable. Current stable (Buster) uses 5.14! So rest easy, there's no way we're going to have 5.12 or 5.8 in stable, it's just not a thing. https://tracker.debian.org/pkg/kwin -- Thanks, Joe
elisa-player_20.12.0-1_amd64.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 10 Dec 2020 16:51:08 +0100 Source: elisa-player Architecture: source Version: 20.12.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Qt/KDE Maintainers Changed-By: Aurélien COUDERC Changes: elisa-player (20.12.0-1) unstable; urgency=medium . * Fix watch file. * New upstream release (20.12.0). * Bump build dependencies according to upstream build system: - Qt >= 5.14 * Add runtime dependencies to QML modules. * Refresh copyright information. * Normalize GitLab CI/CD pipeline to salsa-ci.yml to match the rest of the team’s packages. Checksums-Sha1: ef70abc1b7eedb0aad870e9ff41ef5b932ecce02 3632 elisa-player_20.12.0-1.dsc 3f05a1b84dbc333ef9cdfd7d3eb5be6be08a6bc4 1660052 elisa-player_20.12.0.orig.tar.xz d7d3553238e9270c6dff6eedc9558cdf705b3062 488 elisa-player_20.12.0.orig.tar.xz.asc be8411599d7823a883ccd982f62a2e414f723ba2 12396 elisa-player_20.12.0-1.debian.tar.xz 105c6478b35d3cfc85294936e206d3ff13e2e111 25120 elisa-player_20.12.0-1_amd64.buildinfo Checksums-Sha256: 8050fc4695243a4b68eec425d7228dfbb8d5ee78295c8029fa3a322380779184 3632 elisa-player_20.12.0-1.dsc 0e1bed3836da289361b9a9616caadf24479e184e6b8918747567b46535058508 1660052 elisa-player_20.12.0.orig.tar.xz 1276b2c15710fe61f4c748c498621b88ff9e195e604bab9e06dc31a117883baf 488 elisa-player_20.12.0.orig.tar.xz.asc e0fc25ba8bc0a5c2302d99e71c6c5f169aeeb1de19bbae1568a8b2dd5c484495 12396 elisa-player_20.12.0-1.debian.tar.xz ddfcb004d7e30c5eb5475ca54c543791efc0f93a146e46d20540ab02a610d851 25120 elisa-player_20.12.0-1_amd64.buildinfo Files: 29919c178ed1897d26e1b8389b13448a 3632 kde optional elisa-player_20.12.0-1.dsc 720afbfa6f554ece0d1da650bf9c422d 1660052 kde optional elisa-player_20.12.0.orig.tar.xz 014a638b1eb7f632b05cb10f8ea214f7 488 kde optional elisa-player_20.12.0.orig.tar.xz.asc 0260bd8c806ac84f9bc45c8adc8da4f3 12396 kde optional elisa-player_20.12.0-1.debian.tar.xz ac71fc45206a90bab30cb16585b32959 25120 kde optional elisa-player_20.12.0-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCgAxFiEEIW//QAAaDgcOKDsfcaflM/KRoyQFAl/SRugTHGNvdWNvdWZA ZGViaWFuLm9yZwAKCRBxp+Uz8pGjJGa3D/9ItLdzoFYRNBxRfWBJyar81yFeRenO 2W6+0cJ7z1Poxt1wtkdGmyCi5m4wZMPRFWV9i0dX81NLnNGjJZU157Nnf4pZRGMf fMHH+fTiwc2trmkM2ip5sYe6QNrvKXQaHQgSsTWQ7IvdLNzzzQ0tJGP5J0l+8fei EQFlv74gzZ58uYxbs6JZYTysfsrsDKCLtueoN/lj2YtoooPS+ct3pPMwOMQQP9x8 mCM08HwXZxNtWrX86T+oZKhPFtBadYdDb3QBlibT151F/HYPitguWB4rytzuAWw6 KE9SN253ecPcueVfeRjodZ3EGdzsD3HAs6zO/lu7+AekctgCYkELvZErKArET0XL WnQtDVT79+6vb2gQWjAZlt8Yna2iXvsAj6zoRTHlPKntbpZ/qCSSs/WDatkOvgf9 n2pzgQlr86ySM0J2PyzbRUPFrI0ORkL6KZm7DFPWQSBlv8UnsSDYUOKitIDsCB8v PT1fKpE+3bb94JiiONlh4wU70s0jIisaOktH+Ez27pydgr79z7uB5dsn9OdExkS6 1CzVJLajxcrQ/lQE3ips227JnAXvpFgTG+ZCjES34gUvO+lUGRfTGzXemBm9qd7Y id9ckY6MUBPLgdpVYPF2Or66qNUNW3DAsxABbdNRZ0apFINjpDOzh0s9zxW61xwB wOXdIDh2IQwGJQ== =rYOJ -END PGP SIGNATURE- Thank you for your contribution to Debian.
Processing of elisa-player_20.12.0-1_amd64.changes
elisa-player_20.12.0-1_amd64.changes uploaded successfully to localhost along with the files: elisa-player_20.12.0-1.dsc elisa-player_20.12.0.orig.tar.xz elisa-player_20.12.0.orig.tar.xz.asc elisa-player_20.12.0-1.debian.tar.xz elisa-player_20.12.0-1_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
Re: KDE Plasma LTS for Debian stable
On Thu, Dec 10, 2020 at 07:20:18PM +0330, peylight wrote: > Hi Andy, > You are talking about freeze timeline and policies. > Please look at this document for that: > https://release.debian.org/buster/freeze_policy.html > The time and date is defined and any programmer can planning for it. > I check the LTS versions of KDE and what can i see Debian choose is v5.14, > that is not the LTS version. > How ever Debian could choose v5.12 LTS or even v5.8 LTS for bug fixes and > security issues. > I think Debian should be change the approach for more KDE Desktop stability > as for the kernel has taken this approach. If Debian keeps years-old KDE in unstable I'll stop using it, tbh. -- WBR, wRAR signature.asc Description: PGP signature
Re: KDE Plasma LTS for Debian stable
Hi Andy, You are talking about freeze timeline and policies. Please look at this document for that: https://release.debian.org/buster/freeze_policy.html The time and date is defined and any programmer can planning for it. I check the LTS versions of KDE and what can i see Debian choose is v5.14, that is not the LTS version. How ever Debian could choose v5.12 LTS or even v5.8 LTS for bug fixes and security issues. I think Debian should be change the approach for more KDE Desktop stability as for the kernel has taken this approach. On 12/10/20 2:59 PM, Andy G Wood wrote: On Thursday, 10 December 2020 11:16:17 GMT peylight wrote: Hello Guys, Do you know why Debian is not using KDE Plasma LTS for Stable version? I mean for now DebianBuster is using Plasma 5.14.5, However KDE Community have no support for that version: https://community.kde.org/Schedules/Plasma_5 Why Debian don't choice KDE LTS version for Debian stable version? The freeze for inclusion of major software versions in Buster occurred in early 2019 [1]. Take another look at the Plasma 5 schedule [2] and work out for yourself which version is likely to be in Buster. Andy. [1] https://wiki.debian.org/DebianBuster [2] https://community.kde.org/Schedules/Plasma_5 This email and any attachments are intended solely for the use of the named recipients. If you are not the intended recipient you must not use, disclose, copy or distribute this email or any of its attachments and should notify the sender immediately and delete this email from your system. UK Research and Innovation (UKRI) has taken every reasonable precaution to minimise risk of this email or any attachments containing viruses or malware but the recipient should carry out its own virus and malware checks before opening the attachments. UKRI does not accept any liability for any losses or damages which the recipient may sustain due to presence of any viruses. Opinions, conclusions or other information in this message and attachments that are not related directly to UKRI business are solely those of the author and do not represent the views of UKRI. -- Best Regards, peylight
Re: KDE Plasma LTS for Debian stable
On Thursday, 10 December 2020 11:16:17 GMT peylight wrote: > Hello Guys, > Do you know why Debian is not using KDE Plasma LTS for Stable version? > I mean for now DebianBuster is using Plasma 5.14.5, However KDE > Community have no support for that version: > https://community.kde.org/Schedules/Plasma_5 > Why Debian don't choice KDE LTS version for Debian stable version? The freeze for inclusion of major software versions in Buster occurred in early 2019 [1]. Take another look at the Plasma 5 schedule [2] and work out for yourself which version is likely to be in Buster. Andy. [1] https://wiki.debian.org/DebianBuster [2] https://community.kde.org/Schedules/Plasma_5 This email and any attachments are intended solely for the use of the named recipients. If you are not the intended recipient you must not use, disclose, copy or distribute this email or any of its attachments and should notify the sender immediately and delete this email from your system. UK Research and Innovation (UKRI) has taken every reasonable precaution to minimise risk of this email or any attachments containing viruses or malware but the recipient should carry out its own virus and malware checks before opening the attachments. UKRI does not accept any liability for any losses or damages which the recipient may sustain due to presence of any viruses. Opinions, conclusions or other information in this message and attachments that are not related directly to UKRI business are solely those of the author and do not represent the views of UKRI.
KDE Plasma LTS for Debian stable
Hello Guys, Do you know why Debian is not using KDE Plasma LTS for Stable version? I mean for now DebianBuster is using Plasma 5.14.5, However KDE Community have no support for that version: https://community.kde.org/Schedules/Plasma_5 Why Debian don't choice KDE LTS version for Debian stable version? -- Best Regards, peylight
Bug#977024: marked as done (marble-data and marble-qt-data are not m-a: foreign which blocks cross-building)
Your message dated Thu, 10 Dec 2020 09:34:30 +0100 with message-id <2790206.VdNmn5OnKV@thyrus> and subject line Re: Bug#977024: marble-data and marble-qt-data are not m-a: foreign which blocks cross-building has caused the Debian Bug report #977024, regarding marble-data and marble-qt-data are not m-a: foreign which blocks cross-building 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 your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 977024: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977024 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: marble-data Version: 4:17.08.3-3.2 Severity: important Dear Maintainer, we are cross-compiling our internal packages, which depend on marble. Cross-compilation is failing because of an issue described in the subject. Please add m-a: foreign to the -data packages. -- System Information: Debian Release: 10.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-12-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages marble-data depends on: ii marble-qt-data 4:17.08.3-3.2 marble-data recommends no packages. marble-data suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: marble Source-Version: 4:19.08.1-2 Hi, In data giovedì 10 dicembre 2020 08:21:23 CET, Andrey Loukhnov ha scritto: > Package: marble-data > Version: 4:17.08.3-3.2 > Severity: important > > Dear Maintainer, > > we are cross-compiling our internal packages, which depend on marble. > > Cross-compilation is failing because of an issue described in the subject. > Please add m-a: foreign to the -data packages. This was fixed already with version 4:19.08.1-2: marble (4:19.08.1-2) unstable; urgency=medium * Team upload. * Force the right installation path of Qt plugins, so the Qt Designer plugins are installed in the right place (Closes: #903745) - adjust paths in libmarble-dev.install * Pass -DBUILD_MARBLE_TESTS=FALSE to cmake to disable the build of tests, as they are not run at build time anyway - drop patch kubuntu_disable-MarbleRunnerManagerTest.diff, no more needed now * Add some Multi-Arch annotations. * Remove the marble-data dependency from libastro1, as it does not need it. * Drop the unused 'testsuite' autopkgtest. * Bump the debhelper compatibility to 11: - bump the debhelper build dependency to 11~ - bump compat to 11 * Add Build-Depends-Package in symbols files. * Remove breaks/replaces for versions older than what is in oldstable. * Drop the migration from marble-dbg, no more needed after two Debian stable releases. -- Pino Toscano Sun, 29 Sep 2019 08:22:29 +0200 Since this is a new feature / use case, it is definitely a wishlist (thus the bug severity was lowered), and it will not be fixed in stable. Thanks for your report, -- Pino Toscano signature.asc Description: This is a digitally signed message part. --- End Message ---
Processed: severity of 977024 is wishlist
Processing commands for cont...@bugs.debian.org: > severity 977024 wishlist Bug #977024 [marble-data] marble-data and marble-qt-data are not m-a: foreign which blocks cross-building Severity set to 'wishlist' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 977024: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977024 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
