I followed this guide on installing KDE 4.9.1 on OS 12.2. Everything seemed to have gone well, and I was happily running KDE 4.9. Monday comes along and in with a bunch of updates is “openSUSE-2012-588 - KDE: 4.8.5 stable update”, marked as an important update. Needless to say, I deselected that in Apper and install all the other updates, but now I’m stuck with that, having to deselect it each time an update comes in. Today, however, there are two other similar looking updates that I’m worried about installing: “openSUSE-2012-592 - java-1_7_0-openjdk: security fix for remote exploit” and “openSUSE-2012-590 - alsa-plugins: clean up the left over config path”. All three are listed as version 1 with no installed version or size listed in Apper. What concerns me about the two new updates is the similar appearance (openSUSE-2012-*), to the 4.8.5 KDE update and not having an installed version listed.
How can I get rid of the 4.8.5 “update” (or, more importantly, why is it appearing if I’m using 4.9.1), and are the other two updates related? Most concerning is the alsa-plugins. How can I tell if they go with 4.8.5 or 4.9.1?
OK. Didn’t know about Online Update, I’ve been using Software Management (Install/Remove Software from the menu) - thank you for that. As soon as I open Software Update, it complains that “patch:openSUSE-2012-588-1.noarch conflicts with libkcddb4.x86_64 < 4.8.5-2.5.1 provided by libkcddb4-4.8.4-3.2.3.x86_64” I told it to not install that patch and marked it to never install. Both java and alsa seem to be ok, so I went ahead and installed them. If they break something, I’ll deal with that at that time.
I see that my original problem stems from openSUSE-2012-588 being a system patch. Shouldn’t patches check to see if what they’re trying to patch has a version grater than or equal to what is installed on the system? I have KDE 4.9.1 installed, the patch should be able to determine that and not try to install an older version.
Thanks caf9426. I did the pointy-clicky way described in the system_update.png. The 4.9 upgrade looks to be instructions to do what I followed in the blog I linked to in the original post, only in a pointy-clicky way.
I too dislike Apper, but it was installed by default, and I haven’t gotten around to finding a replacement for it yet. I do like to be notified (read, reminded every now and then) to update the system on a regular basis.
Right now, I seem to be having motherboard issues. I’m getting consistent segfaults during video processing, and I don’t think it’s software related. It was happening in Kubuntu as well, so I know it’s not openSUSEs fault. I’ve got to work on that before going further into the openSUSE world.
On 09/12/12 20:26, suseconvert pecked at the keyboard and wrote:
> I followed ‘this’ (http://tinyurl.com/9y2chyf) guide on installing KDE
> 4.9.1 on OS 12.2. Everything seemed to have gone well, and I was
> happily running KDE 4.9. Monday comes along and in with a bunch of
> updates is “-openSUSE-2012-588 - KDE: 4.8.5 stable update-”, marked as
> an important update. Needless to say, I deselected that in Apper and
> install all the other updates, but now I’m stuck with that, having to
> deselect it each time an update comes in. Today, however, there are two
> other similar looking updates that I’m worried about installing:
> “-openSUSE-2012-592 - java-1_7_0-openjdk: security fix for remote
> exploit-” and “-openSUSE-2012-590 - alsa-plugins: clean up the left over
> config path-”. All three are listed as version 1 with no installed
> version or size listed in Apper. What concerns me about the two new
> updates is the similar appearance (openSUSE-2012-*), to the 4.8.5 KDE
> update and not having an installed version listed.
>
> How can I get rid of the 4.8.5 “update” (or, more importantly, why is
> it appearing if I’m using 4.9.1), and are the other two updates related?
> Most concerning is the alsa-plugins. How can I tell if they go with
> 4.8.5 or 4.9.1?
>
> Here is zypper lr of my currently enabled repos:
>
> KDE_49
> KDE_Extra
> Oracle VirtualBox openSUSE
> Packman Repository
> libdvdcss repository
> nVidia Graphics Drivers
> openSUSE-12.2-Non-Oss
> openSUSE-12.2-Oss
> openSUSE-12.2-Update
> openSUSE-12.2-Update-Non-Oss
>
> And here’s what they look like in Apper:
>
> [image: http://i.imgur.com/T3IfJ.png]
>
>
And how many future patches are going to be in a similar situation in the next 18 months? This is something that needs to be fixed, not ignored. How can a patch apply itself to a system when the files or packages it’s supposed to be patching are no longer installed? This bug not only breaks the whole patching system and places all official patches under suspicion, it opens the door for an unstable, or perhaps even unusable system.
For the next 18 months I’m going to have to thoroughly examine every patch from openSUSE. This is not how I envisioned my move to openSUSE and it makes the transition a bit uncomfortable…
Considering the last zypper bug I encountered was fixed ASAP.
This was not too long ago, like a couple months (for 12.1), when an update was issued and when you went to apply it, your entire system tried to downgrade itself to 32-bit or uninstall completely… I don’t understand why this new one can’t be fixed, but then again I don’t really know why it’s happening.
Being a bug from zypper, I would of thought that updating a small entry in the .spec file used to make the patch or whatever could be amended.
Maybe they aren’t taking it as seriously because it only affects the “branding” packages of openSUSE or just no time for it right now.
I have found that it still returns with a Yast2 online update and causes many newer versions from openSUSE-update repository and opensuse-oss repository. Also k3b and k3b-codecs conflict need to change all to Packman repository.
Did a clean instal from openSUSE 12.2 KDE Live install CD
KDE 4.9.1 upgrade from KDE 4.8.5 including patch opensuse-2012-588 KDE 4.8.5 using caf4926 upgrade instructions using Yast2 and vender change.
My question is will there be a patch version update like the KDE 4.8.5 to KDE 4.9.1 or downgrade(prefer KDE 4.9.1 without conflicts) to KDE 4.8.5
openSUSE 12.2 with KDE 4.9.1 seems stable to me even better than openSUSE 12.2 with KDE 4.8.5
I read the discussion goes like this
If the user wants to change venders or switch system packages (ie adding repositories KDE SC49 repos) from openSUSE then let them deal with version difference.
As a user I like what the KDE 4.9.1 updates do for my desktop. there is a difference.
I also installed KDE 4.9 because it seemed less resource hungry and more responsive.
Nepomuk/virtuoso-t doesn’t hijack my cpu anymore.
It’s weird that we are able to install a fresh system, apply all patches (including this broken one) THEN upgrade to KDE 4.9 and still be bothered about a “needed” patch which was already installed.*
The simplest solution was already mentioned early in this thread and I
use it for a long time. Whenever I have a system with extra repositories
and switched vendors (that is all systems we have at home and also the
one I use for work - in total 6) I use absolutely nothing else than
“zypper update” or in short “zypper up”.
It does not suffer from the mentioned problem, applies only patches for
installed packages for the same vendor and updates packages from the
extra repositories with newer versions from the same repository (unless
you decide to explicitly deactivate a repository if you do not want to
have further updates).
This works for years without problems for me.
Of course the bug with the conflicting patches is annoying, no doubt.
But for the time until it is resolved there is a way to work around it
(just no gui way).
–
PC: oS 12.2 x86_64 | i7-2600@3.40GHz | 16GB | KDE 4.8.4 | GeForce GT 420
ThinkPad E320: oS 12.2 x86_64 | i3@2.30GHz | 8GB | KDE 4.8.4 | HD 3000
eCAFE 800: oS 12.1 i586 | AMD Geode LX 800@500MHz | 512MB | KDE 3.5.10
Am 14.09.2012 11:56, schrieb caf4926:
>
>> there is a way to work around it
>> (just no gui way).
> Actually Martin
> If you do this:
> https://docs.google.com/open?id=0B3e0lLG3OdqEeXF3VTdwbVdGMUk
> It’s the same as : zypper up
> Assuming the switches are applied correctly
>
>
Thanks, so there is even a gui way, I do not really consider it easier
than a “zypper up” (too many mouse clicks) but you are right of course
–
PC: oS 12.2 x86_64 | i7-2600@3.40GHz | 16GB | KDE 4.8.4 | GeForce GT 420
ThinkPad E320: oS 12.2 x86_64 | i3@2.30GHz | 8GB | KDE 4.8.4 | HD 3000
eCAFE 800: oS 12.1 i586 | AMD Geode LX 800@500MHz | 512MB | KDE 3.5.10
As a new user I would like to make a few comments about the GUI solution and how I solved the same/similar issue. Please forgive me, I have no screen shots but hope to get some added.
