Bug 455949 - xulrunner update failed gpk-update-viewer
xulrunner update failed gpk-update-viewer
Product: Fedora
Classification: Fedora
Component: xulrunner (Show other bugs)
x86_64 Linux
low Severity high
: ---
: ---
Assigned To: Gecko Maintainer
Fedora Extras Quality Assurance
: 456185 (view as bug list)
Depends On:
  Show dependency treegraph
Reported: 2008-07-19 01:36 EDT by Ziggy Dustbin
Modified: 2018-04-11 06:51 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-10-21 18:54:53 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Ziggy Dustbin 2008-07-19 01:36:55 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9) Gecko/2008061712 Fedora/3.0-1.fc9 Firefox/3.0

Description of problem:
More details from package updater:
xulrunner-1.9-1.fc9.x86_64 (which is newer than xulrunner-1.9-0.beta5.fc9.i386) is already installed

The package updater has two obvious bugs.
1) if the package is already installed it should warn, skip that component and continue, rather than just quitting without any possibility of getting past the problem
2) If I uncheck the xulrunner security updates in the review list, it still attempts to install them, and fails with the same message - this is obviously being ignored.  If the check box does not cause the item to be skipped then remove it, or disable it to indicate that the component is required.
I don't want to remove the xulrunner package because of the bug where it will also remove Firefox and a whole lot of other stuff that should not be touched.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. run the current fedora 9 update series including xulrunner-1.9-1.fc9.x86_64

Actual Results:

Expected Results:
if the component is already there, it should skip and continue instead of failing

Additional info:
Comment 1 Ziggy Dustbin 2008-07-19 01:37:45 EDT
this is blocking the installation of all pending updates including security updates
Comment 2 Ziggy Dustbin 2008-07-19 01:38:34 EDT
This problem is blocking all further updates including security updates.
Comment 3 Naveed Hasan 2008-07-22 00:45:19 EDT
The currently released xulrunner.x86_64 has an unnecessary dependency on
xulrunner.i386 - which should really be fixed by the maintainers ASAP. Until
then, you can workaround this and upgrade xulrunner-
manually using rpm with nodeps:

sudo rpm -Uvh --nodeps

Then update everything else as normal with the package manager or yum. This way
you'll have the latest Firefox, et. al.
Comment 4 Matěj Cepl 2008-07-22 07:40:23 EDT
*** Bug 456185 has been marked as a duplicate of this bug. ***
Comment 5 Will Woods 2008-07-23 11:58:28 EDT
*** Bug 456185 has been marked as a duplicate of this bug. ***
Comment 6 Matěj Cepl 2008-07-29 19:54:36 EDT
Could everybody on this bug reproduce it or is it gone already?
Comment 7 Jonathan Underwood 2008-07-29 20:49:14 EDT
Wee, I worked around it by removing nspluginwrapper.i386, updating, then
reinstalling nspluginwrapper.i386. But i expect the problem is still there, as I
still have xulrunner-
Comment 8 Naveed Hasan 2008-07-29 22:28:08 EDT
I worked around the issue as per my comment above
https://bugzilla.redhat.com/show_bug.cgi?id=455949#c3 so I don't have any
problems. I'm not entirely sure if the erroneous dependency was in the xulrunner
rpm or the update server metadata. Someone else who still hasn't been able to
update since mid-July might be able to enlighten us on that front.
Comment 9 Matěj Cepl 2008-09-18 11:13:08 EDT
Is there anybody here who could still hits this bug?
Comment 10 Matěj Cepl 2008-10-20 17:41:44 EDT
Reporter, could you please reply to the previous question? If you won't reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.
Comment 11 Matěj Cepl 2008-10-21 18:54:53 EDT
Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.

Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.


Note You need to log in before you can comment on or make changes to this bug.