Mozilla-nspr patch conflict

gymnart · August 23, 2011, 5:11pm

I’m using SuSE 11.4 64 bit. I have both Firefox (installed by default from the openSuSE vendor) and I have SeaMonkey 2.2.1-1-x86_64 installed from the mozilla repo (build.opensuse.org/mozilla).
I saw there were security updates so I went to install them and for mozilla-nspr, yast gave me this warning:


patch mozilla-nspr-5022.noarch conflicts with mozilla-nspr-x86_64 < 4.8.9-1.3.1 provided by mozilla-nspr-4.8.9-1.1 x86_64 
conflict resolution:
install with vendor change obs://build.opensuse.org/mozilla --> openSUSE

So, if I do the suggested vendor change, won’t that ruin or conflict with my 64 bit SeaMonkey?

caf4926 · August 23, 2011, 5:29pm

What prompted the patch? Not kpackagekit?

Once I switch to a repo like mozilla, I update like this:
http://dl.dropbox.com/u/10573557/Software%20Management/system_update.png

That way, the original switch should remain. It may be that the openSUSE update repo has a new package as you describe. Don’t use packagekit either!

creatura85 · August 23, 2011, 7:57pm

running daily cronjob scripts

SCRIPT: opensuse.org-online_update exited with RETURNCODE = 4.
SCRIPT: output (stdout && stderr) follows

Problem: patch:mozilla-nspr-5022.noarch conflicts with mozilla-nspr-devel.x86_64 < 4.8.9-1.3.1 provided by mozilla-nspr-devel-4.8.9-1.1.x86_64
 Solution 1: Following actions will be done:
  install mozilla-nspr-devel-4.8.9-1.3.1.x86_64 (with vendor change)
    obs://build.opensuse.org/mozilla  -->  openSUSE
  install mozilla-nspr-32bit-4.8.9-1.3.1.x86_64 (with vendor change)
    obs://build.opensuse.org/mozilla  -->  openSUSE
  install mozilla-nspr-4.8.9-1.3.1.x86_64 (with vendor change)
    obs://build.opensuse.org/mozilla  -->  openSUSE
 Solution 2: do not install patch:mozilla-nspr-5022.noarch

Choose from above solutions by number or cancel [1/2/c] (c): c
SCRIPT: opensuse.org-online_update

As you can see caf is not kpackagekit.

gymnart · August 23, 2011, 8:38pm

So, right now I don’t know what to do. Should I switch Firefox to the mozilla repo to match SeaMonkey?

Here are the packages I have for Mozilla, SeaMonkey and Firefox:

rpm -qa | grep seamonkey

seamonkey-venkman-2.2-1.1.x86_64
seamonkey-irc-2.2-1.1.x86_64
seamonkey-dom-inspector-2.2-1.1.x86_64
seamonkey-2.2-1.1.x86_64

rpm -qa | grep mozilla

mozilla-js20-2.0.1-0.2.2.x86_64
mozilla-nss-certs-3.12.11-1.3.1.x86_64
mozilla-xulrunner20-2.0.1-0.2.2.x86_64
mozilla-nspr-32bit-4.8.7-4.4.x86_64
mozilla-kde4-integration-0.6.3-3.1.x86_64
mozilla-xulrunner20-gnome-2.0.1-0.2.2.x86_64
mozilla-nss-3.12.11-2.1.x86_64
ca-certificates-mozilla-1.70-3.1.noarch
mozilla-nspr-4.8.9-1.1.x86_64
mozilla-nss-32bit-3.12.11-1.3.1.x86_64
mozilla-nss-certs-32bit-3.12.11-1.3.1.x86_64

rpm -qa | grep Firefox
MozillaFirefox-5.0-0.4.1.x86_64
MozillaFirefox-branding-openSUSE-5.0-2.3.1.x86_64

So anyway, maybe one of those prompted the patch?

caf4926 · August 23, 2011, 8:45pm

Leave the switch on the mozilla repo and don’t run: **zypper patch **
only use **zypper up **or the method I posted earlier from software management

gymnart · August 23, 2011, 8:55pm

I’ve been using YaST 's online updater for all my updates.

So, I should switch my Firefox to the Mozilla repo?

caf4926 · August 23, 2011, 9:02pm

If you are using OBS repos, I would use Software Management, switch to the mozilla repo and do updates as I showed earlier.
Online Update brings in patches that will break the switch. Not always harmful. But you have my advice. Take it or leave it

taytong888 · August 24, 2011, 3:29am

Hello,

Using openSUSE 11.4 KDE 4.7. Earlier I was prompted by KPackagekit icon on the panel to upgrade, but failed to notice the red X in front of this mozilla-nspr package. Thanks to your advice, I switched to using “zypper up”!


#zypper up


...
Loading repository data...
Reading installed packages...

The following package updates will NOT be installed:
  gstreamer-0_10-plugins-base gstreamer-0_10-plugins-good gstreamer-0_10-plugins-good-lang 
  liblensfun0 libxine1-gnome-vfs libxine1-pulse linphone mozilla-nspr mozilla-nspr-32bit 
  taglib 

Nothing to do.

F_style · August 24, 2011, 4:56am

I’m on openSUSE 11.3 x64 and had the same issue. I noted that if I refused to install the update it’d keep advising and advising. So I gave a try by changing vendor to obs://build.opensuse.org/mozilla. Now when I open Yast, Software Management and select the Mozilla repo I have mozilla-nspr highlighted in red, which means Mozilla’s version seems to be indeed older than openSUSE’s version, the one I installed. After reading all posts here I still don’t understand what I should do. Should I leave openSUSE’s mozilla-nspr (1.2.1) or apply Mozilla switch to install back older version (1.1)? Is it harmful? By the way, I have Mozilla 6.0.

caf4926 · August 24, 2011, 5:27am

F_style

Typically we let the switch have priority. That means, if you are using the mozilla repo, the packages would be from that repo.

But if anyone is concerned to the extent that they cannot feel comfortable with that. Then let them try updating that package. It may be fine.

My package doesn’t show red. So maybe you never applied the switch (Or perhaps 11.3 differs slightly I don’t recall)

creatura85 · August 24, 2011, 8:47am

I dont like KpackageKit, its so slow and eats memory and CPU…
gymnart: personally i suggest you stick with mozilla-nspr that you already have(i did the same thing) and use only “sudo zypper up” for updates, just like caf suggested.

gymnart · August 24, 2011, 4:16pm

ok, I now have the latest Firefox and SeaMonkey from the Mozilla repos. I did the switch by going to the repository tab in YaST and then choosing the Mozilla repo and then clicking on the “Switch system packages to the versions in this repository” link like it says to do here: SDB:Vendor change update - openSUSE .

Funny (odd) thing is that when I view the suggested updates from YaST’s updater, it still shows the nspr package in the list. It says to update it to version 4.8.9 but then when I look in the right pane, it shows me that it IS updated to 4.8.9-1.1 from the Mozilla repo. (I’m ignoring that one in the list).

So anyway, all seems to be ok now.

caf4926 · August 24, 2011, 4:28pm

Like I said, don’t use the online update of kpackagekit

gymnart · August 24, 2011, 4:33pm

Yup! I use YaST Online Update instead.

caf4926 · August 24, 2011, 6:10pm

No
Online update is the same as: zypper patch

gymnart · August 25, 2011, 4:24pm

Now I have a question about zypper up: Does it give you a choice whether you want to apply an update or not? If you can pick and choose which updates to do, don’t you have to do a lot of typing (the update/software name, etc)? My memory isn’t what it used to be.

I like having a GUI because I can see what’s coming and check off only the ones I want to apply and either ignore the ones I don’t want (the ones that say they will break my software) or simply do those later. I can see if there’s a kernel update coming or an xorg update coming and get myself ready for it (by getting out my notebook that has the instructions for re-installing my graphics card driver). Then I can apply the update when I feel mentally ready (usually in the mornings).

caf4926 · August 25, 2011, 4:55pm

Then use the method in software management
http://dl.dropbox.com/u/10573557/Software%20Management/system_update.png