Bug 882143 - yum update fails after upgrading Fedora 16 to 17 using the F17 DVD
Summary: yum update fails after upgrading Fedora 16 to 17 using the F17 DVD
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: yum
Version: 17
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Fedora Packaging Toolset Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 882142 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-11-30 09:08 UTC by goodbye300
Modified: 2013-06-04 13:25 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-06-04 13:25:30 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
yum update errors after upgrading to 16 to 17 (200.55 KB, application/octet-stream)
2012-11-30 09:08 UTC, goodbye300
no flags Details
yum check output (20.38 KB, text/plain)
2012-11-30 09:12 UTC, goodbye300
no flags Details
yum update --skipbroken (504.67 KB, application/octet-stream)
2012-11-30 09:16 UTC, goodbye300
no flags Details
yum install --skipbroken ruby-libs (22.47 KB, application/octet-stream)
2012-11-30 09:18 UTC, goodbye300
no flags Details

Description goodbye300 2012-11-30 09:08:00 UTC
Created attachment 654887 [details]
yum update errors after upgrading to 16 to 17

Description of problem:

After using the Fedora 17 DVD to upgrade from F16, I have multiple problems. I first had to mess with the wireless connection a lot to get it working. Unable to obtain an ip was resolved by setting static ip information. I then attempted to run yum update. The output and errors it generated is in the first attachment. It failed to upgrade any packages.

After talking about the issues in #fedora channel on freenode, FranciscoD told me I should follow the instructions here:
http://fedorasolved.org/Members/fenris02/post_upgrade_cleanup
Once I got to this step:
yum update --skip-broken
I received more errors. I'm only able to upload one attachment on here, so I will have to make another post on this bug to upload it. The end of the output looks like this:

Packages skipped because of dependency problems:
    db4-4.8.30-10.fc17.i686 from fedora
    gdbm-1.10-2.fc17.i686 from fedora
    libyaml-0.1.4-2.fc17.i686 from fedora
    ruby-1.9.3.327-19.fc17.x86_64 from updates
    ruby-irb-1.9.3.194-10.1.fc17.noarch from fedora
    ruby-irb-1.9.3.327-19.fc17.noarch from updates
    ruby-libs-1.9.3.194-10.1.fc17.i686 from fedora
    rubygem-bigdecimal-1.1.0-19.fc17.x86_64 from updates
    rubygem-heroku-2.24.0-2.fc17.noarch from fedora
    rubygem-io-console-0.3-10.1.fc17.x86_64 from fedora
    rubygem-io-console-0.3-19.fc17.x86_64 from updates
    rubygem-json-1.5.4-19.fc17.x86_64 from updates
    rubygem-json-1.6.5-1.fc17.x86_64 from fedora
    rubygem-netrc-0.7.1-1.fc17.noarch from fedora
    rubygem-rake-0.9.2.2-19.fc17.noarch from updates
    rubygem-rdoc-3.9.4-19.fc17.noarch from updates
    rubygem-rdoc-3.12-3.fc17.noarch from fedora
    rubygem-rdoc-3.12-4.fc17.noarch from updates
    rubygem-rubyzip-0.9.4-3.fc17.noarch from fedora
    rubygems-1.8.23-10.1.fc17.noarch from fedora
    rubygems-1.8.23-19.fc17.noarch from updates
    rubygems-1.8.24-1.fc17.noarch from fedora
Error: Protected multilib versions: ruby-libs-1.9.3.327-19.fc17.x86_64 != ruby-libs-1.9.3.194-10.1.fc17.x86_64

I've attempted these commands to fix the problem. None worked.
yum update ruby-libs
yum remove ruby-libs;yum install ruby-libs
package-cleanup --cleandupes # There were no duplicates. I found this from google, worked for a user experiencing similar errors
yum --enablerepo=updates-testing install ruby-libs

This last one gave me the following errors also telling me to report a bug. Here is partial error output from it.

ERROR with transaction check vs depsolve:
ruby(abi) = 1.8 is needed by (installed) rubygem-configuration-1.1.0-2.fc15.noarch
ruby(abi) = 1.8 is needed by (installed) rubygem-rake-0.9.2.2-1.fc16.noarch
ruby(abi) = 1.8 is needed by (installed) rubygem-launchy-0.4.0-1.fc16.noarch
ruby(abi) = 1.8 is needed by (installed) rubygem-term-ansicolor-1.0.7-1.fc16.noarch
ruby(abi) = 1.8 is needed by (installed) rubygem-mime-types-1.16-3.fc15.noarch
ruby(abi) = 1.8 is needed by (installed) rubygem-rest-client-1.6.1-2.fc15.noarch
ruby(abi) = 1.8 is needed by (installed) rubygem-heroku-2.0.4-1.fc16.noarch
ruby(abi) = 1.8 is needed by (installed) rubygems-1.8.11-3.fc16.1.noarch
ruby-libs(x86-64) = 1.8.7.371-1.fc16 is needed by (installed) ruby-1.8.7.371-1.fc16.x86_64
Please report this error in https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=rawhide&component=yum
** Found 239 pre-existing rpmdb problem(s), 'yum check' output follows:

yum --skip-broken --enablerepo=updates-testing install ruby-libs

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

Fedora 17 upgraded from 16 with the Fedora 17 DVD

How reproducible:
On my system, every time. Other systems, uncertain.

Steps to Reproduce:
1. Have a Fedora 16 64-bit installation
2. Get the Fedora 17 64 iso file, burn it, use it to upgrade
3. Have several bugs, attempt to upgrade with yum upgrade (full details described above)
  
Actual results:

Unable to update packages with yum update, several bugs in Fedora 17 that could possibly be fixed if yum would update the system

Expected results:

A working Fedora 17 system with yum update able to update all packages

Additional info:

I will post more output and provide any additional info if needed, ask me.

Comment 1 goodbye300 2012-11-30 09:12:03 UTC
Created attachment 654890 [details]
yum check output

Comment 2 goodbye300 2012-11-30 09:16:22 UTC
Created attachment 654893 [details]
yum update --skipbroken

Comment 3 goodbye300 2012-11-30 09:18:31 UTC
Created attachment 654894 [details]
yum install --skipbroken ruby-libs

Comment 4 Panu Matilainen 2013-05-17 12:46:40 UTC
*** Bug 882142 has been marked as a duplicate of this bug. ***

Comment 5 James Antill 2013-06-04 13:25:30 UTC
> ** Found 239 pre-existing rpmdb problem(s), 'yum check' output follows:

If you fix these then yum will be happy, although given the number of them it's not going to be fun.


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