Bug 458663

Summary:	Failed Security Updates mozilla-xulrunner181
Product:	[openSUSE] openSUSE 11.0	Reporter:	Michael Dunsavage <mikesd1>
Component:	Update Problems	Assignee:	E-mail List <bnc-team-mozilla>
Status:	RESOLVED FIXED	QA Contact:	Jiri Srain <jsrain>
Severity:	Major
Priority:	P5 - None	CC:	meissner, wolfgang
Version:	Final
Target Milestone:	---
Hardware:	x86-64
OS:	Other
Whiteboard:
Found By:	Community User	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	solver testcase My Solver Test New Solver case 12-31-08 My new solver case 12-31-08 07:17

Description Michael Dunsavage 2008-12-12 14:08:39 UTC

When running security updates on OpenSuse 11.0 64 bit I get:

Problem: patch:mozilla-xulrunner181-329.noarch conflicts with mozilla-xulrunner181.x86_64 < 1.8.1.18-0.1 provided by mozilla-xulrunner181-1.8.1.18-1.1.x86_64
 Solution 1: downgrade of mozilla-xulrunner181-1.8.1.18-1.1.x86_64 to mozilla-xulrunner181-1.8.1.18-0.1.x86_64
 Solution 2: do not install patch:mozilla-xulrunner181-329.noarch

Attached is my solver test.

Running KDE 4.1.3 

Any other information needed?

Is this related to bug #447986?

Comment 1 Marcus Meissner 2008-12-12 14:50:17 UTC

do you have the mozilla buildservice repository enabled?

Comment 2 Wolfgang Rosenauer 2008-12-12 14:57:12 UTC

I'm seeing the same issue and yes I have the buildservice repo enabled obviously.
Still I don't understand why that is an issue. The buildservice packages are 'newer' than the updates 0.1<1.1.
This upgrade doesn't look different than the others before. Where can I check the update meta data?

Comment 3 Marcus Meissner 2008-12-12 15:03:43 UTC

orig reporter>: the solver test was not attached btw.


http://download.opensuse.org/update/11.0/repodata/updateinfo.xml.gz   is the full blob, search for xulrunner181 ... i see nothing amiss though

Comment 4 Wolfgang Rosenauer 2008-12-12 15:34:45 UTC

Created attachment 259716 [details]
solver testcase

That is my debug-solver result

Comment 5 Michael Dunsavage 2008-12-17 12:56:38 UTC

Created attachment 260575 [details]
My Solver Test

Comment 6 Dirk Mueller 2008-12-29 14:36:00 UTC

an update was released for bug 447986. does it fix this issue?

Comment 7 Michael Dunsavage 2008-12-29 14:54:29 UTC

I'm not sure. I no longer have the problem, but a few days ago xulrunner did update again and now the security alert is no longer showing.....so...

let's go with yes?

bug 447986 still persists though.

Comment 8 Michael Dunsavage 2008-12-31 12:16:23 UTC

Created attachment 262877 [details]
New Solver case 12-31-08 

Updated suse via zypper, xulrunner updated, now this bug is back. Wants to downgrade.

Comment 9 Michael Dunsavage 2008-12-31 12:17:45 UTC

Created attachment 262879 [details]
My new solver case   12-31-08   07:17

Comment 10 Michael Dunsavage 2009-01-02 22:22:09 UTC

xulrunner came through as an update again today (zypper dup). And the red security symbol is gone. Running zypper up didn't argue with me except the persistent bug 447986. But this happened before too. So what does this mean?

Comment 11 Michael Dunsavage 2009-01-03 06:29:31 UTC

so today epiphany extensions wanted to update again and xulrunner and now xulrunner is asking to downgrade again.


What more info is needed?

Comment 12 Michael Dunsavage 2009-01-19 14:34:03 UTC

This bug seems to be connect to 447986. zypper up just dies silently. I know bug 447986 is reportedly solved, but it still just dies quietly.

Comment 13 Dirk Mueller 2009-02-12 14:02:03 UTC

I think this issue got solved with the latest you stack update. reopen if this is not the case.