I’ve filed several critical bugs against KDE 5.8 and they were closed saying it’s fixed in 5.9, but after I fully update OpenSUSE Leap 42.2 I find that I’m still on KDE 5.8.6
5.8 is an LTS release, 42.2 won’t upgrade to 5.9.
So LTS releases are supposed to be LESS stable than others? I got an update that BROKE Plasma Panel TaskManager, but I won’t get the one that fixes it!?!
On Fri, 31 Mar 2017 18:46:01 +0000, CountBakula wrote:
> So LTS releases are supposed to be LESS stable than others? I got an
> update that BROKE Plasma Panel TaskManager, but I won’t get the one that
> fixes it!?!
The fix may be backported, but in general, openSUSE doesn’t update
versions of major components like KDE because doing so can break
dependencies in unexpected ways.
–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C
They’ll backport the fixes if they’re critical - reporting them vs KDE on their bugtracker isn’t going to do much.
You should report them to openSUSE Bugzilla vs 42.2, I doubt they’ll say “It’s fixed in 5.9”.
afik 42.2 won’t get an “official” 5.9 but it is currently available from the kde:frameworks5 repo which has the latest kde versions
http://download.opensuse.org/repositories/KDE:/Frameworks5/openSUSE_Leap_42.2/
the 5.8 LTS can be found here
http://download.opensuse.org/repositories/KDE:/Frameworks5:/LTS/openSUSE_Leap_42.2/
you’d also need the kde:qt5 repo as the updated plasma needs updated qt libraries
http://download.opensuse.org/repositories/KDE:/Qt5/openSUSE_Leap_42.2/
if you want 5.9 on LEAP add those two repo’s KDE:/Frameworks5 and KDE:/Qt5 and do a full vendor change to them
note there are no delta rpm’s for those repo’s and they are updated often so you will endup downloading a lot of data
My multi-monitor configuration issues are somewhat comparable to the OP’s so this was a very interesting proposition! 
Unfortunately, adding the KDE:/Frameworks5 and KDE:/Qt5 repositories, selecting ‘allow vendor change’ then selecting to ‘upgrade all in this list if a newer package is available’ yielded several hundred dependency conflicts on my freshly installed, fully updated Leap 42.2. Did I misinterpret something? Thanks!
I do not think this is waht was hinted at.
From the View button choose Repositories. Then select the new repo. Above ths package list of the repos there is a line Switch all system packages … Click that line. That is the same as when doing the Vendor switch to Packman.
I think your way of handling can create a mess, because it is based on version “numbers” throughout all repos. And version numbers of packages of the same name in the different repos are not said to be coordinated.
Thank you very much for the clarification! I tried this method and, again, ran into an extremely large number of conflicts that could only be solved by uninstalling many packages. There were also a significant number of conflicts that could be resolved by ‘switching vendor’ to openSUSE Build Service. I’m going to put more time into devising workarounds for the specific problems I’ve encountered and put KDE 5.9 on the ‘back burner’ for awhile. Thanks again!
Switching can be tricky and yes, there will be some choices to make regarding dependencies but it’s usually not as difficult to overcome as it looks.
You can use the switch and just cancel away the dependency error
Why?
Because you can apply each switch required in turn (no changes take place at this point and you can just abort and start again as you get the feel of what the system is saying)
You can always save the error list to a file, by using the expert button in the deps error box
The let us see it
currently I’m on the OSS plasma release but in the past I have used the kde:frameworks repo and using it has been quite simple
with zypper you add both repo’s and then do
zypper lr -d
to see the repo’s alieses and then do a switch to both the kde:frameworks and kde:qt5
zypper dup --from <enter frameworks alias here> --from <enter qt5 alias here> --froom <enter packman alias here>
the packman alias might not be needed but I use it just iin case to keep multimedia from breaking
the question was how to get plasma 5.9 on leap the answer is from the frameworks repo
and expect to download hundreds of packages and have frequent updates as those are stable but development repo’s
Thank you very much for your interest and reply! Being a longtime Linux and SuSE > openSUSE user, I’m reasonably familiar with the options you are suggesting. You’re free to have a look!
https://www.cehartung.com/dl/frameworks5-system-change-conflicts.txt.gz
https://www.cehartung.com/dl/Qt5-system-change-conflicts.txt.gz
I appreciate your interest and comments, so thank you very much for replying. I’m not inexperienced in these matters, overall, but in this case the number of conflicts I’m encountering is quite daunting. Please have a look at the two files I just posted the links for if you have time. Thanks again!
Maybe moving to Tumbleweed or something like KDE Neon is an option for you? Neon is an interesting project where you get the latest KDE packages, but the base is an Ubuntu LTS for stability. Sorry if you already know all of this, but just my thoughts if you want KDE 5.9
from the looks of those messages you didn’t use the proper --from switch
when doing a full vendor change a lot of packages will be replaced that’s normal
tell us your current repo list
zypper lr -d
plasma 5.9 works well on 42.2 but keep in mind your issues might not be fixed
I’d say check kde’s bugzilla if someone reported your issue
https://bugs.kde.org/
if not report them as open suse does not write plasma 5, some of the opensuse developers do work on kde stuff but the fix needs do be done upstream by the kde team
You need the KDE:Applications repo as well to get the latest KDE applications.
https://download.opensuse.org/repositories/KDE:/Applications/KDE_Frameworks5_openSUSE_Leap_42.2/
The latest frameworks need a newer gpgme, but the KDE applications included in 42.2 are built with an older one and that causes most of your conflicts.
Other problems I see in your lists:
-
calibre requires the Qt5 version it is compiled against. So either uninstall it, or forget about upgrading. A workaround may be to install calibre from their home page I think.
-
python-qt5, python3-qt5: those are broken currently because of changes in the python packages. Try to choose “keep obsolete …” or ignore the conflict.
Or uninstall them if you don’t need 'em. -
plasma-framework-private-5.27.0~20160928~b115ea1.git-3.1.x86_64 requires plasma-framework = 5.27.0~20160928~b115ea1.git, but this requirement cannot be provided,
plasma-framework-components-5.27.0~20160928~b115ea1.git-3.1.x86_64 requires plasma-framework = 5.27.0~20160928~b115ea1.git, but this requirement cannot be provided
and
plasma-framework-lang-5.27.0~20160928~b115ea1.git-3.1.noarch requires plasma-framework = 5.27.0~20160928~b115ea1.git, but this requirement cannot be provided
Select:
] install plasma-framework-private-5.32.0-170.1.noarch (with vendor change)
openSUSE –> obs://build.opensuse.org/KDE
and so on.
I hope I haven’t overlooked something something important…
Oh, and as I_A wrote, you need to use something like “zypper dup --from KDE:Qt5 --from KDE:Applications --from KDE:Frameworks5”.
The question about the vendor change seems to indicate that you didn’t use “zypper dup” or didn’t specify all 3 repos at once (which means you would have to resolve some conflicts manually…).
I’d like to mention that while most Qt based apps for me did work with the updated Qt5 from kde:Qt5 repo the lxqt desktop did not so I avoid using the newest plasma/qt5 and stick to the current versions
again I’d recommend checking kde’s bugzilla for your issue, if it was fixed upstream you can report it to the opensuse bugzilla and they will fix it in the current version as opensuse does port fixed to older packages no need for the latest and greatest
Yes, most applications should work with newer Qt5 versions, as Qt5 is upwards compatible.
But some things use internal/private headers (in some cases it’s necessary, e.g. for a desktop platform plugin), those require the exact same version they are compiled with.
again I’d recommend checking kde’s bugzilla for your issue, if it was fixed upstream you can report it to the opensuse bugzilla and they will fix it in the current version as opensuse does port fixed to older packages no need for the latest and greatest
Actually, as Plasma 5.8 is LTS the upstream KDE developers themselves do port (important) fixes in later versions to 5.8 (if possible)…