Upstream released Plasma 5.13.3. Are there any reasons why Plasma is still at 5.13.1 in Rawhide and not even in testing for F28?
Hi,
I was offline whole last week and no one supposedly other had the capacity to bump to 5.13.2 (which I finally did 2 days ago). Also, there was a binutils issue breaking build of some packages in rawhide. I just pushed the 5.13.3 bump in the respective component git repos and I am building the stack in rawhide. The build for F28 is already present in copr: https://copr.fedorainfracloud.org/coprs/mkyral/plasma-unstable/ - it's the build from the rawhide srpms.
Hope it helps you, Martin
st 11. 7. 2018 v 12:52 odesílatel Matthieu Gras grasm@student.ethz.ch napsal:
Upstream released Plasma 5.13.3. Are there any reasons why Plasma is still at 5.13.1 in Rawhide and not even in testing for F28?
kde mailing list -- kde@lists.fedoraproject.org To unsubscribe send an email to kde-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kde@lists.fedoraproject.org/me...
On mercredi 11 juillet 2018 19:46:31 CEST Martin Kyral wrote:
Hi,
I was offline whole last week and no one supposedly other had the capacity to bump to 5.13.2 (which I finally did 2 days ago). Also, there was a binutils issue breaking build of some packages in rawhide. I just pushed the 5.13.3 bump in the respective component git repos and I am building the stack in rawhide. The build for F28 is already present in copr: https://copr.fedorainfracloud.org/coprs/mkyral/plasma-unstable/ - it's the build from the rawhide srpms.
Thanks for the great work, it is really appreciated.
Hi,
I would like to also get Plasma 5.13 to Fedora 28. There is already a third bug fix release and many people have been using it from COPR (me included) so it should be safe enough to do the update. Do you agree with that? I would do the update myself on Monday if there are no objections.
Regards, Jan
On středa 11. července 2018 12:45:36 CEST Matthieu Gras wrote:
Upstream released Plasma 5.13.3. Are there any reasons why Plasma is still at
5.13.1 in Rawhide and not even in testing for F28?
On Friday, July 13, 2018 2:06:58 PM CEST Jan Grulich wrote:
Hi,
I would like to also get Plasma 5.13 to Fedora 28. There is already a third bug fix release and many people have been using it from COPR (me included) so it should be safe enough to do the update. Do you agree with that? I would do the update myself on Monday if there are no objections.
Regards, Jan
Sounds great, 5.13.0 had some issues but starting from 5.13.1-5.13.2 everything was fixed.
Hi,
given there were no objections to push Plasma 5.13 to F28, I did the update today and you can find it here [1]. I set stable karma to 6 so there is need for more testers before this goes to stable.
[1] - https://bodhi.fedoraproject.org/updates/FEDORA-2018-6729457bc2
Regards, Jan
On pátek 13. července 2018 19:39:02 CEST Matthieu Gras wrote:
On Friday, July 13, 2018 2:06:58 PM CEST Jan Grulich wrote:
Hi,
I would like to also get Plasma 5.13 to Fedora 28. There is already a third bug fix release and many people have been using it from COPR (me included) so it should be safe enough to do the update. Do you agree with that? I would do the update myself on Monday if there are no objections.
Regards, Jan
Sounds great, 5.13.0 had some issues but starting from 5.13.1-5.13.2 everything was fixed.
Jan Grulich wrote:
given there were no objections to push Plasma 5.13 to F28, I did the update today and you can find it here [1]. I set stable karma to 6 so there is need for more testers before this goes to stable.
[1] - https://bodhi.fedoraproject.org/updates/FEDORA-2018-6729457bc2
Thanks for working on that. Though I'd feel better with autokarma off, with lower stable karma threshold (leave the decision up to us humans)
-- Rex
well, for testing sake, I've disabled copr/plasma-unstabe, dist-sync'ed to 5.12, and now the update fials with missing kf5-plasma and kf5-kwayland >5.48
$ dnf --enablerepo=updates-testing upgrade --advisory FEDORA-2018-6729457bc2 Dernière vérification de l’expiration des métadonnées effectuée il y a 0:01:04 le ven. 27 juil. 2018 02:26:59 +03. Dépendances résolues.
Problème 1: cannot install the best update candidate for package kwin-common-5.12.6-1.fc28.x86_64 - nothing provides kf5-kwayland(x86-64) >= 5.48.0 needed by kwin-common-5.13.3-3.fc28.x86_64 Problème 2: cannot install the best update candidate for package plasma-desktop-5.12.6-1.fc28.x86_64 - nothing provides kf5-plasma(x86-64) >= 5.48.0 needed by plasma-desktop-5.13.3-2.fc28.x86_64 Problème 3: cannot install the best update candidate for package plasma-workspace-5.12.6-1.fc28.x86_64 - nothing provides kf5-plasma(x86-64) >= 5.48.0 needed by plasma-workspace-5.13.3-3.fc28.x86_64 Problème 4: cannot install the best update candidate for package sddm-breeze-5.12.6-1.fc28.noarch - nothing provides kf5-plasma >= 5.48.0 needed by sddm-breeze-5.13.3-3.fc28.noarch Problème 5: package plasma-workspace-wayland-5.13.3-3.fc28.x86_64 requires plasma-workspace = 5.13.3-3.fc28, but none of the providers can be installed (...)
ok, it works now: I was probably between mirror syncs while 5.48 was being pushed to stable.
well, the update works. But changing desktop layout crashes the shell. not kwin though.
Sinan H wrote:
well, for testing sake, I've disabled copr/plasma-unstabe, dist-sync'ed to 5.12, and now the update fials with missing kf5-plasma and kf5-kwayland
5.48
$ dnf --enablerepo=updates-testing upgrade --advisory FEDORA-2018-6729457bc2 Dernière vérification de l’expiration des métadonnées effectuée il y a 0:01:04 le ven. 27 juil. 2018 02:26:59 +03. Dépendances résolues.
As you noticed, kf5-5.48 (at the time) was also in updates-testing, you'd have to update that first (or at the same time).
-- Rex