Debian KDE/Plasma Status 2021-02-18
Lots of time has passed since the last status update, and Debian is going into pre-release freeze, so let us report a bit about the most recent changes: Debian/bullseye will have Plasma 5.20.5, Frameworks 5.78, Apps 20.12. Debian/experimental already carries Plasma 5.21 and Frameworks 5.79, and that is also the level at the OSC builds.
We are in soft freeze now, and only targeted fixes are allowed, but Bullseye is carrying a good mixture consisting of the KDE Frameworks 5.78, including several backports of fixes from 5.79 to get smooth operation. Plasma 5.20.5, again with several cherry picks for bugs will be in Bullseye, too. The KDE/Apps are mostly at 20.12 level, and the KDE PIM group packages (akonadi, kmail, etc) are at 20.08.
In the last days I have uploaded frameworks 5.79 and Plasma 5.21 to Debian/experimental. For Plasma there is still some NEW processing to be done, but in due time the packages will be available and installable from experimental.
The OBS packages as usual follow the latest release, and currently ship KDE Frameworks 5.79, KDE Apps 20.12.2, and Plasma 5.21.0. The package sources are as usual (note the different path for the Plasma packages and the App packages, containing the release version!), for Debian/unstable:
deb https://download.opensuse.org/repositories/home:/npreining:/debian-kde:/frameworks/Debian_Unstable/ ./ deb https://download.opensuse.org/repositories/home:/npreining:/debian-kde:/plasma521/Debian_Unstable/ ./ deb https://download.opensuse.org/repositories/home:/npreining:/debian-kde:/apps2012/Debian_Unstable/ ./ deb https://download.opensuse.org/repositories/home:/npreining:/debian-kde:/other/Debian_Unstable/ ./
and the same with
Testing instead of
Unstable for Debian/testing.
There is also a separate repository for the upcoming digikam release:
deb https://download.opensuse.org/repositories/home:/npreining:/debian-kde:/digikam-beta/Debian_Unstable/ ./
just in case you want to test the rc release of digikam 7.2.0.
Thank you so much Norbert. It feels great to have such quality packaging readily available. As usual, I’m now running on Plasma 5.21, upgraded from your OBS repository without any hassle
Thanks for the positive feedback. Just FYI, you can get the same packages from experimental – after NEW processing, though 😉
5.21 is really looking nice and has a good feel.
Only could not install / update Digikam 7.1. in debian testing, Version number from your repo is lower than in testing. Tried to force 7.1 from your repo but no succes. 7.2RC installed correctly so using that one :-). Thanks!
It should be fine to use the digikam that is in testing, why do you want to force the version from my repo?
Version from official testing demanded a downgrade of a collection of the 5.21 packages. Your version is a part of 5.21 so I tried to force that.
Updated both my Debian/Testing Desktop and KVM.
Thanks a lot, once more 🙂
I noted issue launching scripts/application pinned in kde panel. I some case instead starting the script Kate opens the .desktop file. In some others a msg appears :”For security reasons, launching executables is not allowed in this context”.
Could it be related to this bug ?
Seems to be fixed in 5.21.1, which will come out in 2 days, so please wait a bit, both experimental and the OBS repos will be updated.
Thanks. Take your time, it’s not a big issue .
updated to 5.21.1, issue fixed.
Hello Mr. Preining! I using Debian Testing, I recently connected your repos and installed KDE Plasma 5.21 from them – everything is installed and working fine. Thank you so much for that!
But today I ran into the fact that when I try to update packages from your repository, other packages from KDE are removed from me … I took a screenshot from the terminal, but I am Russian and my operating system is in Russian. For your convenience, I have translated the lines into English. Can this problem be solved?
The screenshot is uploaded to jpegshare: https://jpegshare.net/85/cf/85cfbff08c3582a65261ddfebc304008.png.html
The OBS packages are not fully build, please wait until all packages are built and upgrade does NOT uninstall anything. Patience for 1-2 days should be enough 😉
Yes, indeed, I went to your repository from a browser and saw that not all packages have been updated to version 5.21.1 .. But it’s okay, we’ll wait =)
Thank you very much for your work! =)
Should be all available now, I checked the OBS server an hour ago.
For folks who many not be aware, Plasma 5.21 brings nicer systemd integration. As in, now processes are grouped into cgroup groups appropriately.
More details on it can be read here: http://blog.davidedmundson.co.uk/blog/plasma-and-the-systemd-startup/
On my system, where I now have Plasma 5.21 from Norbert’s repo, I am effectively running the new Plasma, without any glitch so far. How all the systemd integration should be enabled and verified, is documented in the blog post linked in this comment.
thanks for your comment. Yes, systemd-based starting is getting more and more supported – but honestly, by now I have no idea how we could integrate this into the Debian packaging.
How should that work on a multi-user system, where some display manager authorizes users? Unfortunately the blog post is very thin on these issues, do you have any further insights? If yes, it would be great if you could join the #debian-kde channel on oftc/irc.debian and we discuss there, or via email to the debian kde talk mailing list.
an “apt upgrade” works fine on my sid.
With an “apt dist-upgrade” kmymoney, kio-gdrive, libkf5kaddressbookgrantlee5 and libkf5kaddressbookimportexport5 should be removed.
Do you have a solution for this?
Thanks for the report. I have re-added kmymoney to the “other” repository, and included kio-gdrive in the “apps2012” repository. If you have both of them activated, it should be possible to upgrade all packages. Some lib* might get uninstalled, but that is less an issue.
Now I was able to upgrade completely.
Thanks for your great work, Norbert.
I’m no more reluctant to consider using Plasma with Debian.
Thanks for the positive feedback – but it is not *my* work, but that of the whole team.
That’s what I meant of course 😉 Such great distro and maintainers.
Looks like your repo keys expired over the weekend.
N: Skipping acquire of configured file ‘non-free/binary-i386/Packages’ as repository ‘http://repositories.apertis.org/apertis v2021pre InRelease’ doesn’t support architecture ‘i386’
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://www.preining.info/debian unstable InRelease: The following signatures were invalid: EXPKEYSIG D80E09B087140066 Norbert Preining
W: Failed to fetch http://www.preining.info/debian/dists/unstable/InRelease The following signatures were invalid: EXPKEYSIG D80E09B087140066 Norbert Preining
W: Some index files failed to download. They have been ignored, or old ones used instead.
You need to update my gpg key in your apt trust database. I keep a expiry on the sub-keys that I extended once a year, just in case the key gets stolen. Please get the updated key either from the Debian keyring, or from https://www.preining.info/preining-norbert.asc
Yes I have those added to my apt key db. I will double check but I think that the sub-key for preining-norbert.asc may have expired. The other one, obs-npreining.asc, is still active.
Yes, but you have to re-import my personal key, the current at the web page has the expiry extended.
Hello, im trying to to install new plasma on my Debian Sid but dont have any luck, i tried to add your key from here and still dont have luck. Can u help me Norbert?
Have you installed the obs key from https://www.preining.info/obs-npreining.asc as mentioned in several of the blog posts?
Ok thx, i managed to do that. Solved
I did installing keys through terminal that didnt work. Obviously it was needed to download .asc and then move it to /etc/apt/trusted.gpg.d/
Here, on my sid(uction) computer all recent KDE/Plasma packages – 20.12.3 app releases, KDE frameworks 5.80.0 and KDE Plasma 5.21.3 from Norbert’s obs repos – run without a hitch.
We could help you, @Draguljche, if you gave us additional info, f. i. terminal output, while installing.
Again and again thanks go to Norbert an the team for their work.