Ask Your Question

Fedora 17 - preupgrade problem

asked 2012-05-30 09:14:46 +0000

matthias_muc gravatar image

Yesterday I tried to upgrade from FC16 to FC17 using preupgrade.

Everything seemed fine, but the upgrade process hung up - after it did not continue for one hour I decided to reboot my computer. I was quite surprised when I saw the upgrade process continued again at the point it hung up. Afterwards the upgrade seemed to have run successful and it looks like if I'm working on FC17 - but for example yum still searchs the FC16 repos.

If I try to show the release version both are shown:

# rpm -q fedora-release

There are no packages marked for distro sync:

# yum --releasever=17 distro-sync
Loaded plugins: langpacks, presto, refresh-packagekit
No Packages marked for Distribution Synchronisation

But package cleanup recommends removing almost everything (which I seem to have installed twice FC16 and FC17 - but I'm worried if I continue the packages are actual removed):

# package-cleanup --cleandupes
 xorg-x11-xauth              x86_64 1:1.0.6-1.fc16        @anaconda-0      55 k
 xorg-x11-xkb-utils          x86_64 7.5-5.fc16            @anaconda-0     195 k
 xsane-common                x86_64 0.998-4.fc16          @anaconda-0     2.9 M
 xvidcore                    x86_64 1.3.2-2.fc15          @rpmfusion-free 921 k
 xz                          x86_64 5.1.1-1alpha.fc16     @anaconda-0     638 k
 xz-libs                     x86_64 5.1.1-1alpha.fc16     @anaconda-0     227 k
 y4mscaler                   x86_64 9.0-9.fc16            @rpmfusion-free 155 k
 yajl                        x86_64 1.0.12-1.fc16         @anaconda-0      90 k
 yum-metadata-parser         x86_64 1.1.4-5.fc16          @anaconda-0      53 k
 yum-utils                   noarch 1.1.31-2.fc16         @anaconda-0     307 k
 zeromq                      x86_64 2.1.9-1.fc16          @anaconda-0     806 k
 zip                         x86_64 3.0-3.fc15            @anaconda-0     770 k
 zlib                        x86_64 1.2.5-6.fc16          @updates        173 k
 zlib-devel                  x86_64 1.2.5-6.fc16          @updates        123 k
Removing for dependencies:
 UltraEdit                   x86_64 3.0-0.20.fc16         @/UltraEdit-3.0-0.20.fc16.x86_64
                                                                           43 M
 coreutils-libs              x86_64 8.12-7.fc16           @updates        6.0 k
 gnome-desktop-sharp         x86_64 2.26.0-16.fc17        @anaconda-0/17  571 k
 gnome-sharp                 x86_64 2.24.1-9.fc17         @anaconda-0/17  1.3 M
 google-chrome-stable        x86_64 18.0.1025.162-131933  @google-chrome  100 M
 gtk-sharp2                  x86_64 2.12.11-5.fc17        installed       2.7 M
 libgdiplus                  x86_64 2.10-2.fc16           @fedora         419 k
 mono-addins                 x86_64 0.6.2-5.fc17          installed       1.1 M
 mono-core                   x86_64 2.10.8-2.fc17         installed        43 M
 mono-data                   x86_64 2.10.8-2.fc17         installed       9.4 M
 mono-data-oracle            x86_64 2.10.8-2.fc17         @anaconda-0/17  478 k
 mono-data-postgresql        x86_64 2.10.8-2.fc17         @anaconda-0/17  476 k
 mono-data-sqlite            x86_64 2.10.8-2.fc17         installed       413 k
 mono-debugger               x86_64 2.10-3.fc17           installed       2.7 M
 mono-debugger-devel         x86_64 2.10-3.fc17           @anaconda-0/17  415  
 mono-devel                  x86_64 2.10.8-2.fc17         installed       7.8 M
 mono-extras                 x86_64 2.10.8-2.fc17         installed       2.3 M
 mono-mvc                    x86_64 2.10.8-2.fc17         installed       3.3 M
 mono-nunit                  x86_64 2.10.8-2.fc17         installed       465 k
 mono-wcf                    x86_64 2.10.8-2.fc17         installed       5.6 M
 mono-web                    x86_64 2.10.8-2.fc17         installed       9.4 M
 mono-winforms               x86_64 2.10.8-2.fc17         installed       9.8 M
 mono-winfx                  x86_64 2.10.8-2.fc17         installed       1.1 M
 monodevelop                 x86_64 2.8.5-1.fc17          @anaconda-0/17   25 M
 monodevelop-debugger-gdb    x86_64 2.8.5-1.fc17          @anaconda-0/17   41 k
 monodevelop-devel           x86_64 2.8.5-1.fc17          @anaconda-0/17  2.1 k
 monodevelop-vala            x86_64 2.8.5-1.fc17          @anaconda-0/17  249 k
 monodoc                     x86_64 2.10.8-2.fc17         installed        11 M
 openmotif                   x86_64 2.3.3-1.fc14          @rpmfusion-nonfree
                                                                          3.6 M

Transaction Summary
Remove  1032 Packages (+29 Dependent packages)

Installed size: 2.1 G
Is this ok [y/N]: ^CExiting on user Command

How can I finish the upgrade, what would you recommend?

edit retag flag offensive close delete

5 Answers

Sort by ยป oldest newest most voted

answered 2012-05-30 20:22:54 +0000

misc gravatar image

I would first fix the fedora-release issue, with :

yum reinstall fedora-release

Then make sure that indexes are clean, with :

yum clean all

And then try to do a upgrade and or a distro-sync. I suspect that the configuration of yum is broken due to the fedora-release duplicate ( since this is the package with the yum configuration )

edit flag offensive delete publish link more


Thanks, I did fix the duplicate fedora releases.

Upgrade and distro sync practically does not do much, "package-cleanup --cleandupes" still suggest erasing many (way too many) packages. :-/

matthias_muc ( 2012-05-30 20:27:57 +0000 )edit

Thanks, I did fix the duplicate fedora releases.

matthias_muc ( 2012-05-30 20:27:57 +0000 )edit

Do you have other packages duplicated ( for example , what does rpm -q xz say ? )

misc ( 2012-05-30 20:32:02 +0000 )edit

Many package seem to be there in one fc16 and one fc17 version:

rpm -q xz



I'm worried if I allow package-cleanup to cleanup that it will erase also the actual installed version.

matthias_muc ( 2012-05-30 20:32:49 +0000 )edit

I think, but I am not sure, that package-cleanup --clean-dupes will do the right thing and just remove the package from the rpm database. I am asking ot others people to confirm.

misc ( 2012-05-30 21:22:40 +0000 )edit

answered 2013-03-27 10:56:38 +0000

ABC gravatar image

hi i tried to upgrade from fc 16 to fc 17, all the download went well but after reboot i still find fc 16 only. what can i do to get the fc17?

edit flag offensive delete publish link more

answered 2012-06-01 13:07:24 +0000

updated 2012-06-02 10:57:12 +0000

solution that worked for me:

1st) fix grub2 problem with loading wrong (older) f16 kernel during first boot, after preupgrade 2nd) run preupgrade again.

what happens (as I understand it) some installation software read the version from the kernel, which was -- erroneously - set as f16 and messes up the whole repository configuration, which uses environmental variables to determine what to download.

after first install with the error in kernel, you fix the kernel, and by running again preupgrade (which btw downloads nothing) straighten the thing somehow.

if it still gives you trouble with the version of repos,

vi /etc/yum/vars/releasever

write: '17'

yum repolist

should give you the right ones.

now, if you issue:

package-cleanup --orphans

should give you all the older non-f17 packages "out-there"

package-cleanup --dupes|grep f17|less

unfortunately gives still TOO many f17 packages

I'd consider getting rid of the orphans, although it's going to chop freecad that I had to install through zultron fc16 repo, which did not upgrade to fc17

followed the advice to:

yum reinstall fedora-release
Loaded plugins: presto, refresh-packagekit
Resolving Dependencies
--> Running transaction check
---> Package fedora-release.noarch 0:16-1 will be updated
---> Package fedora-release.noarch 0:17-1 will be an update
---> Package fedora-release.noarch 0:17-1 will be erased
--> Finished Dependency Resolution

Dependencies Resolved

 Package                 Arch            Version       Repository          Size
 fedora-release          noarch          17-1          fedora              27 k
 fedora-release          noarch          17-1          installed           29 k
Not available:
 fedora-release          noarch          16-1          -                  0.0  

Transaction Summary
Upgrade        1 Package
Remove         1 Package
Not available  1 Package

Total download size: 27 k
Is this ok [y/N]: y
Downloading Packages:
Setting up and reading Presto delta metadata
fedora-release-17-1.noarch.rpm                           |  27 kB     00:00     
warning: rpmts_HdrFromFdno: Header V3 RSA/SHA256 Signature, key ID 1aca3465: NOKEY
Public key for fedora-release-17-1.noarch.rpm is not installed
Retrieving key from file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-x86_64
Importing GPG key 0x1ACA3465:
 Userid     : "Fedora (17) <fedora@fedoraproject.org>"
 Fingerprint: cac4 3fb7 74a4 a673 d81c 5de7 50e9 4c99 1aca 3465
 Package    : fedora-release-17-1.noarch (installed)
 From       : /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-x86_64
Is this ok [y/N]: y
Running Transaction Check
Running Transaction Test
Transaction Test Succeeded
Running Transaction
  Updating   : fedora-release-17-1.noarch                                   1/3 
  Cleanup    : fedora-release.noarch                                        2/3 
  Verifying  : fedora-release-17-1.noarch                                   1/2 
  Verifying  : fedora-release-17-1.noarch                                   2/2 
  Verifying  : fedora-release-16-1.noarch                                   3/2 

  fedora-release.noarch 0:17-1                                                  

  fedora-release.noarch 0:17-1                                                  


after setting the releasever by hand in the /etc/yum/vars/releasever as '17' Unlike before, it installed 17 over 16 and not vice versa

I think I'll get all the fc16 dupes in a file with:

package-cleanup --dupes|grep fc16 > fc16.dupes

and then yum remove them in a batch:

split -l 50 fc16.dupes fc16-
yum remove $(cat fc16-aa)

(provided that it touches no fc17 packages)

one of the packages that tends to remove lots of fc17's is: libpng-1.2.49-1.fc16.x86_64

so, instead I gave:

yum update libpng-1.2.49-1.fc16.x86_64

(it failed, because already has fc17 package) so,

yum reinstall libpng

which cleaned up the older one.

After a while of yum remove fc16 packages, the system was left with a few even older fc packages (some from the era of my fc11 - since then I preupgrade)

which were chopped with:

yum remove $(package-cleanup --dupes)

and some older kernels which were removed with:

package-cleanup --oldkernels

now I only got a yum-fc16 that I'm stuck with, because it is newer version than current fc17 yum. I'll either downgrade the fc16, or wait for fc17 to upgrade. No worries really, although it became interdependent with many fc17 packages.

This was a nasty upgrade, but gave me the opportunity to rid sh...loads of old crap I had on my laptop :D for which I never bothered since "it worked".

edit flag offensive delete publish link more

answered 2012-06-01 11:31:28 +0000

updated 2012-06-01 11:59:32 +0000

Had the same installation line:

1) had fedora 16 on two systems (+)

2) prepupgrade complained about a broken pipe of grub from the onset

3) downloaded everything

4) rebooted and went about 300 out of 2000 packages and froze (+) only one did this

5) reset and resumed to give a working desktop

6) grub did not install properly, so was booting from older f16 kernel

7) applied the fix to be found on the internet (grub2-mkconfig -o /boot/grub2/grub.cfg)

I'm at the point where some older fedora 16 (and some 15) packages are still there. If I do an --orphans it shows f17 to be the orphans If I attempt to get rid of duplicates, I'm sure beyond 101% certainty that it will send my system to the bin (1.1Gb of uninstall, half are F17).

This new naming convention is jinx!

edit flag offensive delete publish link more

answered 2012-06-05 18:07:55 +0000

mburns gravatar image

It is also necessary to reinstall dracut. I wonder how many Fedora followers will be lost by this transition.

edit flag offensive delete publish link more

Your answer

Please start posting your answer anonymously - your answer will be saved within the current session and published after you log in or create a new account. Please try to give a substantial answer, for discussions, please use comments and please do remember to vote (after you log in)!

Add answer

[hide preview]

Use your votes!

  • Use the 30 daily voting points that you get!
  • Up-vote well framed questions that provide enough information to enable people provide answers.
  • Thank your helpers by up-voting their comments and answers to your questions.
  • Down-voting might cost you karma, but you should consider doing so for incorrect or clearly detrimental questions and answers.

Question tools



Asked: 2012-05-30 09:14:46 +0000

Seen: 9,501 times

Last updated: Mar 27 '13