KDEPIM 21.08 coming to unstable
Hi! KDE Gear already mostly went through, except a few applications and KDEPIM. Norbert is uploading KDEPIM / Akonadi 21.08. Please wait for builds to complete their work. In generally be careful. Unstable is much more unstable again, also for other reasons like breaking changes in debianutils. So I strongly recommend to install apt-listbugs, it will warn you in case someone else stumbled upon an issue of a certain severity and reported it already. Anyway, breakage can happen especially in the first weeks after a stable release. You may choose to stay on stable for a month or two and then switch to unstable or testing again. In case you are prepared for a potentially more bumpy ride: Have fun. Best, -- Martin
Re: Testing : do not upgrade to 5.21 (yet)
Erwan David ha scritto: > After upgrade to 5.21 this morning (plasma-workspace 4:5.21.5-3), I get > > kf.plasma.core: > "/usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/applets/org.kde.plasma.systemtray.so" > : this plugin is compiled against incompatible Plasma version 348928 This > build is compatible with 5 .0.0 ( 327680 ) to 5.78.0 ( 347708 ) > kf.plasma.core: Applet "org.kde.plasma.systemtray" could not be loaded. > > So better wait for a newer version... > plasma-workspace alone is not Plasma. You need all the packages which makes up Plasma, those are the upstream sources https://download.kde.org/stable/plasma/5.21.5/ Please also consider that Frameworks is only partially migrated to testing, which means other stuff may not work for different reasons than not having all Plasma bits. -- Luigi
Re: Testing : do not upgrade to 5.21 (yet)
Message d'origine De : Luigi Toscano [mailto:luigi.tosc...@tiscali.it] Envoyé : lundi 23 août 2021 à 10:50 UTC+2 Pour : Erwan David , Debian Kde Objet : Testing : do not upgrade to 5.21 (yet) Erwan David ha scritto: After upgrade to 5.21 this morning (plasma-workspace 4:5.21.5-3), I get kf.plasma.core: "/usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/applets/org.kde.plasma.systemtray.so" : this plugin is compiled against incompatible Plasma version 348928 This build is compatible with 5 .0.0 ( 327680 ) to 5.78.0 ( 347708 ) kf.plasma.core: Applet "org.kde.plasma.systemtray" could not be loaded. So better wait for a newer version... plasma-workspace alone is not Plasma. You need all the packages which makes up Plasma, those are the upstream sources https://download.kde.org/stable/plasma/5.21.5/ Please also consider that Frameworks is only partially migrated to testing, which means other stuff may not work for different reasons than not having all Plasma bits. I know; There were more than 400 packages, however error message is kf.plasma.core: "/usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/applets/org.kde.plasma.systemtray.so" : this plugin is compiled against incompatible Plasma version 348928 This build is compatible with 5 .0.0 ( 327680 ) to 5.78.0 ( 347708 ) and according to apt-file org.kde.plasma.systemtray.so comes in plasma-workspace package. See bug #992760
Re: Bug#992760: ksystemtray: cannot be started, wrong version
Hi Erwan, > kf.plasma.core: > "/usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/applets/org.kde.plasma.systemtray.so" > : this plugin is compiled against incompatible Plasma version 348928 This > build is compatible with 5 .0.0 ( 327680 ) to 5.78.0 ( 347708 ) > kf.plasma.core: Applet "org.kde.plasma.systemtray" could not be loaded. > ii libkf5plasma5 5.78.0-3 The problem is that this packages (and several others) from the frameworks are not updated. I guess we have to introduce a breaks somewhere ... this incompatibility is somehow surprising, because it is not documented in the CMakeList files - at least as far I see... > So better wait for a newer version... No, wait for all frameworks being updated ... Best Norbert -- PREINING Norbert https://www.preining.info Fujitsu Research + IFMGA Guide + TU Wien + TeX Live + Debian Dev GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
Re: Testing : do not upgrade to 5.21 (yet)
Erwan David ha scritto: > > Message d'origine > De : Luigi Toscano [mailto:luigi.tosc...@tiscali.it] > Envoyé : lundi 23 août 2021 à 10:50 UTC+2 > Pour : Erwan David , Debian Kde > > Objet : Testing : do not upgrade to 5.21 (yet) > >> Erwan David ha scritto: >>> After upgrade to 5.21 this morning (plasma-workspace 4:5.21.5-3), I get >>> >>> kf.plasma.core: >>> "/usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/applets/org.kde.plasma.systemtray.so" >>> >>> : this plugin is compiled against incompatible Plasma version 348928 This >>> build is compatible with 5 .0.0 ( 327680 ) to 5.78.0 ( 347708 ) >>> kf.plasma.core: Applet "org.kde.plasma.systemtray" could not be loaded. >>> >>> So better wait for a newer version... >>> >> >> plasma-workspace alone is not Plasma. You need all the packages which makes >> up >> Plasma, those are the upstream sources >> https://download.kde.org/stable/plasma/5.21.5/ >> >> Please also consider that Frameworks is only partially migrated to testing, >> which means other stuff may not work for different reasons than not having >> all >> Plasma bits. >> > > I know; There were more than 400 packages, however error message is > kf.plasma.core: > "/usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/applets/org.kde.plasma.systemtray.so" > : this plugin is compiled against incompatible Plasma version 348928 This > build is compatible with 5 .0.0 ( 327680 ) to 5.78.0 ( 347708 ) > > and according to apt-file org.kde.plasma.systemtray.so comes in > plasma-workspace package. > > See bug #992760 > You have a mix of Frameworks packages from 5.78 and 5.83: ii libkf5plasma5 5.78.0-3 ii libkf5plasmaquick55.78.0-3 ii libkf5prison5 5.83.0-2 Make sure you fully get all Frameworks 5.83 (which should be upgraded as a single block). -- Luigi
Re: Bug#992760: ksystemtray: cannot be started, wrong version
De : Norbert Preining [mailto:norb...@preining.info] Hi Erwan, kf.plasma.core: "/usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/applets/org.kde.plasma.systemtray.so" : this plugin is compiled against incompatible Plasma version 348928 This build is compatible with 5 .0.0 ( 327680 ) to 5.78.0 ( 347708 ) kf.plasma.core: Applet "org.kde.plasma.systemtray" could not be loaded. ii libkf5plasma5 5.78.0-3 The problem is that this packages (and several others) from the frameworks are not updated. I guess we have to introduce a breaks somewhere ... this incompatibility is somehow surprising, because it is not documented in the CMakeList files - at least as far I see... So better wait for a newer version... No, wait for all frameworks being updated ... Best Norbert I know it is a big work, but with ~ 400 package upgrades, it is difficult to check everything will be updated. And version naming does not help either (it would be a big work to change, I know). I am on testing, so I am OK with minor inconveniences like this (by the way the plasmoid to get network, CPU or RAM load does not start either). But I wanted to warn people of this (obviously transient) problem.
Re: Testing : do not upgrade to 5.21 (yet)
Le 23/08/2021 à 11:25, Luigi Toscano a écrit : u have a mix of Frameworks packages from 5.78 and 5.83: ii libkf5plasma5 5.78.0-3 ii libkf5plasmaquick55.78.0-3 ii libkf5prison5 5.83.0-2 Make sure you fully get all Frameworks 5.83 (which should be upgraded as a single block). And what would be the best way to be sure ? Given I have some libkf5* packages with another numbering scheme : eg libkf5cddb5 : 4:20.12.0-1 There are alos many packages in the framework, what would be the best tool to be sure we upgrade the framework as a whole ?
Re: Testing : do not upgrade to 5.21 (yet)
Erwan David ha scritto: > Le 23/08/2021 à 11:25, Luigi Toscano a écrit : > u have a mix of Frameworks packages from 5.78 and 5.83: >> >> ii libkf5plasma5 5.78.0-3 >> ii libkf5plasmaquick5 5.78.0-3 >> ii libkf5prison5 5.83.0-2 >> >> Make sure you fully get all Frameworks 5.83 (which should be upgraded as a >> single block). >> > > And what would be the best way to be sure ? > Given I have some libkf5* packages with another numbering scheme : > eg libkf5cddb5 : 4:20.12.0-1 Those are not the Frameworks product, they are shipped with a different cycle. > There are alos many packages in the framework, what would be the best tool to > be sure we upgrade the framework as a whole ? I don't have an answer - I usually check whether all the packages are available using also the version numbers. -- Luigi
Re: KDEPIM 21.08 coming to unstable
On maandag 23 augustus 2021 09:21:59 CEST Martin Steigerwald wrote: > Norbert is uploading KDEPIM / Akonadi 21.08. Please wait for builds to > complete their work. > > In generally be careful. Unstable is much more unstable again If you stick to using 'safe-upgrade' you should be fine in Unstable. You will see sth like "and 51 not upgraded" and that is fine. When all the dependencies are there, safe-upgrade will upgrade KDEPIM/Akonadi too. signature.asc Description: This is a digitally signed message part.
[OT] Dolphin, tags and ratings, user experience?
Hello, Dolphin shows functions to add ratings and tags to files and folders. I am interested to read about your experience using them, especially: (1) Where are they (tags and stars) stored for the directories and the files? (2) Are they (tags and stars) preserved in copied or moved items (directories and files)? (3) Have they (tags and stars) over years shown to be preserved after upgrades? Well, any feedback is welcome! I am wondering if it would be worth to start using these features, or if nasty pitfalls would be known. --- Always stay in good spirits! Marco
Re: Testing : do not upgrade to 5.21 (yet)
Hi! On Mon, 23 Aug 2021 at 07:23, Luigi Toscano wrote: > > Erwan David ha scritto: > > Le 23/08/2021 à 11:25, Luigi Toscano a écrit : > > u have a mix of Frameworks packages from 5.78 and 5.83: > >> > >> ii libkf5plasma5 5.78.0-3 > >> ii libkf5plasmaquick55.78.0-3 > >> ii libkf5prison5 5.83.0-2 > >> > >> Make sure you fully get all Frameworks 5.83 (which should be upgraded as a > >> single block). > >> > > > > And what would be the best way to be sure ? > > Given I have some libkf5* packages with another numbering scheme : > > eg libkf5cddb5 : 4:20.12.0-1 > > Those are not the Frameworks product, they are shipped with a different cycle. > > > > There are alos many packages in the framework, what would be the best tool > > to > > be sure we upgrade the framework as a whole ? There is surely some dependency that needs to be tighten. I have just run into the same issue. -- Lisandro Damián Nicanor Pérez Meyer https://perezmeyer.com.ar/
Re: Testing : do not upgrade to 5.21 (yet)
De : Lisandro Damián Nicanor Pérez Meyer [mailto:perezme...@gmail.com] Hi! On Mon, 23 Aug 2021 at 07:23, Luigi Toscano wrote: Erwan David ha scritto: Le 23/08/2021 à 11:25, Luigi Toscano a écrit : u have a mix of Frameworks packages from 5.78 and 5.83: ii libkf5plasma5 5.78.0-3 ii libkf5plasmaquick55.78.0-3 ii libkf5prison5 5.83.0-2 Make sure you fully get all Frameworks 5.83 (which should be upgraded as a single block). And what would be the best way to be sure ? Given I have some libkf5* packages with another numbering scheme : eg libkf5cddb5 : 4:20.12.0-1 Those are not the Frameworks product, they are shipped with a different cycle. There are alos many packages in the framework, what would be the best tool to be sure we upgrade the framework as a whole ? There is surely some dependency that needs to be tighten. I have just run into the same issue. Upgrading this morning, it now works...
