Bug 1000550

Summary: yum update bug
Product: [Fedora] Fedora Reporter: George R. Goffe <grgoffe>
Component: kde-settingsAssignee: Rex Dieter <rdieter>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 19CC: admiller, dvratil, ffesti, firas.alkafri, jgrulich, jreznik, jzeleny, kevin, ltinkl, mbriza, packaging-team-maint, rdieter, rnovacek, smparrish, than, tim.lauridsen, zpavlas
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-08-26 13:05:33 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
flat file containing output of "yum update" and "yum check none

Description George R. Goffe 2013-08-23 15:59:21 UTC
Created attachment 789650 [details]
flat file containing output of "yum update" and "yum check

Description of problem:

Running yum update on newly installed Fedora 19 x86_64 fails

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


How reproducible:

Always.

Steps to Reproduce:
1.Type in "yum update"
2.Observe error messages (enclosed)
3.

Actual results:

yum failure

Expected results:

yum success

Additional info:

See attached console log for "yum update" and "yum check"

Comment 1 Jan Zeleny 2013-08-26 08:04:52 UTC
There are several problems I can see, none of which point to a bug in yum. First of all you have some multilib problems (caused either by faulty installation or by packages themselves) - just uninstall one architecture of the libusb and libusb-devel and you should be fine.

The other problem probably lies in the package kde-settings itself. Reassigning the bug for further evaluation.

Comment 2 George R. Goffe 2013-08-26 08:13:46 UTC
Jan,

Thank you for your information.

I'll check this out in the morning. One of the rpm's (I think it was one of the settings rpms) I tried to remove got a "scriptlet" error of some kind.

I don't see how one can get a faulty installation. Do you mean installation via DVD or a "yum install" problem? This system is x86_64 but does have some ix86 pkgs for the software that doesn't know about x86_64 yet.

Thanks again,

George...

Comment 3 Jan Zeleny 2013-08-26 10:21:41 UTC
(In reply to George R. Goffe from comment #2)
> Jan,
> 
> Thank you for your information.
> 
> I'll check this out in the morning. One of the rpm's (I think it was one of
> the settings rpms) I tried to remove got a "scriptlet" error of some kind.

Yeah, that's the reason why I reassigned this bug to kde-settings component, the uninstallation failed in that package.

> I don't see how one can get a faulty installation. Do you mean installation
> via DVD or a "yum install" problem? This system is x86_64 but does have some
> ix86 pkgs for the software that doesn't know about x86_64 yet.

That's probably the root cause of the multilib problem that yum reports. I am no expert in multilib but I don't think there is anything yum can do about it, the solution is IMO to uninstall one arch of the libusb library - either the i686 or x86_64.

Comment 4 Rex Dieter 2013-08-26 13:05:33 UTC
See bug #989145 for the kde-settings scriptlet issue.

The other problem(s) can likely be resolved with 'yum distro-sync'

*** This bug has been marked as a duplicate of bug 989145 ***