KDE/Plasma update for Debian

Norbert Preining norbert at preining.info
Tue Apr 28 14:37:44 BST 2020


Hi Pino,

thanks for your email!

On Tue, 28 Apr 2020, Pino Toscano wrote:

> Plasma 5.18 requires KF 5.64 (or so) which we don't have yet in Debian.
> Updating to a newer KF takes effort as well, and I believe Sandro Knauss

As said, I have updated all relevant packages:
- frameworks to 5.69
- KDE apps to 20.04
- Plasma to 5.18

So in principle everything is ready, with a lot of caveats of course.

> Ideally I'd ask for some kind of coordination with us, rather than a
> "this is the work, take it" approach, as there is lots of things to do,
> and review a monolithic approach IME takes more than the various bits
> of it. If you are interested, please contact Sandro about this.

Complete agreed. I am more than happy to help integrate this into
main Debian, that is anyway the aim, right!

Basically, the update is **extremely** smooth due to all the work you
have done. What was necessary is adjusting the watch file
(applications -> release-service), running uscan --rename, unpacking,
checking that the patches apply, fixing them now and then, building
them and fixing the changed symbols.

Thanks to OBS (I think you suggested it to me once during the cinnamon
update sessions. I didn't use it back then, but now I see how helpful
that service is!), this is all rather trivial as one has to only push
out the changes.

There are a few items that needs more detailed consideration, in
particular disappearing files (the most work was changes in the .install
files), and that some packages have moved. E.g., calendarcore moved from
a KDE Apps to KDE frameworks, so now has version number 5.69, and in
addition the names have changed. I reused the source package name, but
the binary package name have changed.

Then there are new packages necessary: kdsoap and kvcardblabla (have it
somewhere here).

What I did **not** do is meticulously checking the CMakefile for the
**minimum** version, but often put in 5.69 for dependency frameworks.

Let us discuss how to continue, as said, I can send out debdiffs, I can
maybe also commit something to the git repos, but with over 250 packages
I have updated, most of the stuff needs to be working automatically,
that is with a bit of scripting. I have updated practically all packages
automatically, and then only fixed those which were broken.

So, what should be do? What do you prefer? We need to make a plan how to
proceed. I guess first we need to update frameworks. Besides the
calendarcore thing I don't remember anything serious, besides symbol
changes and installed files changes.

Anyway, let me know what kind of contribution you would like to see.
I will try my best to help, but also please understand that alone
updating all packages was a considerable endeavour ...

All the best

Norbert

PS: comments to the rest in private email.

--
PREINING Norbert                              https://www.preining.info
Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13



More information about the pkg-kde-talk mailing list