This morning update TW using KDE4 break kio_file, keyboard control, and other things module!
Seems it is not reversable!
???
KDE4 (the desktop) has been replaced with Plamsa5 over a month ago already.
Can you please describe your exact problems in more detail?
What is “broken” in which way?
Just to be clear, today’s update so far doesn’t include a new Tumbleweed snapshot, the last one was openSUSE 20150612.
I’m just updating 155 packages and they seem to be all from Packman. My zypper dup produced a conflict concerning VLC dependencies, and offering 6 solutions to choose from! Life is too short, so I’m updating with the equivalent of a “zypper up” I think (actually a PackageKit updater on Plasma 5) and no conflicts. I might look at the conflicts later.
Yeah, right.
The newest packages in the Tumbleweed repo are from June 14th, but those are unrelated to KDE either. virtualbox, kernel, and the kmp packages…
The last KDE4 related update, kdebase4 and its sub packages, was on the 11th, and should not break anything. It actually just fixed the “Create New” templates for KDE4.
I’m just updating 155 packages and they seem to be all from Packman. My zypper dup produced a conflict concerning VLC dependencies, and offering 6 solutions to choose from!
Maybe that’s vlc still built against libdvdpsi9 as mentioned in some other thread?
I see it has been rebuilt against the current libdvbpsi10 19 hours ago, but this might not be on the mirror you are using yet.
zypper up (or PackageKit) will just skip the update in the case of such conflicts (if you have the old versions installed).
This should resolve itself in the next days then.
OP may be running behind with updates including “the 11th”.
Maybe that’s vlc still built against libdvdpsi9 as mentioned in some other thread?
I see it has been rebuilt against the current libdvbpsi10 19 hours ago, but this might not be on the mirror you are using yet.
zypper up (or PackageKit) will just skip the update in the case of such conflicts (if you have the old versions installed).
This should resolve itself in the next days then.
A small typo in yours - my libdvbpsi9 was retained as obsolete so I didn’t suffer that conflict before. I see libdvbpsi10 is there but not installed, although it should when I remove the older one.
Today it was a different one, see here:
Problem: vlc-noX-2.2.1-285.3.x86_64 requires libstdc++.so.6(GLIBCXX_3.4.21)(64b
it), but this requirement cannot be provided
uninstallable providers: libstdc++6-gcc5-5.1.1+r223279-1.1.x86_64[Tumbleweed]
Yeah, right. Sorry.
I did notice it and correct it in the second line though before submitting the reply…
I see libdvbpsi10 is there but not installed, although it should when I remove the older one.
If your vlc (or other packages) are built against libdvbpsi9, they require libdvbpsi9 and don’t work with libdvbpsi10.
libdvbpsi9 and libdvbpsi10 are incompatible, so you won’t get the other when uninstalling the 9. You’d rather get another conflict, or zypper will want to remove vlc as well…
Today it was a different one, see here:
Problem: vlc-noX-2.2.1-285.3.x86_64 requires libstdc++.so.6(GLIBCXX_3.4.21)(64b it), but this requirement cannot be provided uninstallable providers: libstdc++6-gcc5-5.1.1+r223279-1.1.x86_64[Tumbleweed]
Seems to be related to the new gcc5 then.
Strange though.
AFAICS, the Packman vlc packages only require libstdc++.so.6(GLIBCXX_3.4.9) and below, not libstdc++.so.6(GLIBCXX_3.4.21), the former should be provided by libstdc+±gcc48.
https://pmbs.links2linux.de/package/binary/Essentials/vlc?arch=x86_64&filename=vlc-noX-2.2.1-285.3.x86_64.rpm&repository=openSUSE_Tumbleweed
I just spotted the gcc5 in the package name when returning from posting elsewhere, and gcc5 stuff is probably still held up in Factory with build errors. BTW I noticed yesterday our plasma5-pk-updates showing build errors for Tumbleweed on OBS - also looked like gcc5 was involved.
Yes, there are still some problems with the switch to gcc5 in Factory.
But I don’t see any build error for plasma5-pk-updates now. Probably it was just a temporary inconsistency in Factory because not all package had been built yet.
Such things happen on a moving target like Factory.