Ask Your Question

Fedup 18 to 20 questionable: yum rpm not updated

asked 2013-12-28 23:06:03 -0600

updated 2013-12-30 17:41:22 -0600

Second try to fedup from 18 to 20, yum and rpm are not updated to fc20 entries, still have fc18, still pointing to the old fc18 repo-s. Wondering if the installation of the updated packages really took (after fedup reboot).

Another update: looking at the version of bluetoothd, it is still 4.101, but if the fc20 packages "took", it would be 5.12.

After reboot, the install process lists all of the packages being updated; when reaching the end of those packages, a number of things take place, and the system reboots. But I cannot find the messages that flash by (before the second reboot) in a log file anywhere. (later found in /var/spool/plymouth/boot.log)

Any hints as to where to look?

FWIW, I am booting an fc20 kernel. Also, /var is on its own partition, and I had to move the packagedir and cachedir to /share (in root partition) as described. They are up-to-date.


Thanks for the rapid response.

fedora-release: Fedora release 20 (Heisenbug)

/var/log/fedup.log contains:

+++ Following is for fedora 17 to 18

[ 0.124] (II) fedup:<module>() /bin/fedup starting at Tue Dec 24 15:16:26 2013 [ 0.273] (II) fedup.sysprep:remove_cache() removing /var/tmp/fedora-upgrade [ 0.427] (II) fedup.sysprep:remove_cache() removing /var/lib/fedora-upgrade [ 1.648] (II) fedup.sysprep:remove_cache() removing /var/tmp/fedora-upgrade [ 1.648] (II) fedup.sysprep:remove_cache() removing /var/lib/fedora-upgrade [ 1.648] (II) fedup.sysprep:misc_cleanup() removing symlink /system-upgrade [ 1.649] (II) fedup.sysprep:misc_cleanup() removing /system-upgrade-root [ 1.660] (II) fedup.sysprep:misc_cleanup() removing /lib/systemd/system/ [ 1.660] (II) fedup:<module>() /bin/fedup exiting at Tue Dec 24 15:16:27 2013

+++++ Following was first attempt at Fed 18 to 20. At end graphical environment was not set up, and only able to login at prompt. After re-adding X and KDE packages, found that I could log in, but that yum and rpm were both pointing at fc18 distro.

[ 0.970] (II) fedup:<module>() /usr/bin/fedup-cli starting at Fri Dec 27 06:47:13 2013 [ 0.984] (II) fedup.sysprep:remove_cache() removing [ 0.984] (II) fedup.sysprep:remove_cache() removing /var/tmp/system-upgrade [ 0.984] (II) fedup.sysprep:remove_cache() removing /var/lib/system-upgrade [ 0.985] (II) fedup.sysprep:misc_cleanup() removing symlink /system-upgrade [ 0.985] (II) fedup.sysprep:misc_cleanup() removing /system-upgrade-root [ 0.999] (II) fedup.sysprep:misc_cleanup() removing /lib/systemd/system/ [ 1.000] (II) fedup:<module>() /usr/bin/fedup-cli exiting cleanly at Fri Dec 27 06:47:13 2013 [ 0.277] (II) fedup:<module>() /bin/fedup starting at Fri Dec 27 12:41:10 2013 [ 0.479] (II) fedup.sysprep:remove_cache() removing /var/tmp/system-upgrade [ 0.973] (II) fedup.sysprep:remove_cache() removing /var/lib/system-upgrade [ 4.290] (II) fedup.sysprep:remove_cache() removing /var/tmp/system-upgrade [ 4.291] (II) fedup.sysprep:remove_cache() removing /var/lib/system-upgrade [ 4.291] (II) fedup.sysprep:misc_cleanup() removing symlink /system-upgrade [ 4.291] (II) fedup.sysprep:misc_cleanup() removing /system-upgrade-root [ 4.308] (II) fedup.sysprep ... (more)

edit retag flag offensive close merge delete

4 Answers

Sort by ยป oldest newest most voted

answered 2013-12-29 08:50:09 -0600

mether gravatar image

Did you try yum distro-sync? After that run, package-cleanup --cleandupes

edit flag offensive delete link more


yum distro-sync only sync'ed yum with the Fedora 18 repo-s. yum does not point to the Fed 20 repo-s. Something failed in the install, and I cannot find the right log to show what might have happened.

dstockwell gravatar imagedstockwell ( 2013-12-29 15:17:48 -0600 )edit

Can you post the output of yum repolist? What version of fedup are you using? You might want to try the suggestions from @FranciscoD_

mether gravatar imagemether ( 2013-12-29 17:44:38 -0600 )edit

@mether, @FranciscoD_:

[root@freqone-devel fedup]# yum repolist Loaded plugins: langpacks, presto, refresh-packagekit repo id repo name status adobe-linux-x86_64 Adobe Systems Incorporated 2 fedora/18/x86_64 Fedora 18 - x86_64 33,868 updates/18/x86_64 Fedora 18 - x86_64 - Updates 18,495 repolist: 52,365

dstockwell gravatar imagedstockwell ( 2013-12-29 19:02:54 -0600 )edit

sudo yum reinstall <a href="">

Your repos are still pointing to F18 for some reason. The above command should correct that. When you're done, run sudo yum install rpmconf and then sudo rpmconf -a and make sure the maintainers copy of the config file is installed. Rerun sudo yum repolist to check. Your repos should now point to F20. Then, sudo yum distro-sync.

FranciscoD_ gravatar imageFranciscoD_ ( 2013-12-29 20:27:07 -0600 )edit

@mether, @FranciscoD_: After uploading the yum repolist, I did the yum install and the yum distro-sync, which has just about finished running after about two hours. While distro-sync is still finishing up, it looks like this should resolve the issue. Thanks!

dstockwell gravatar imagedstockwell ( 2013-12-29 21:31:08 -0600 )edit

answered 2013-12-28 23:35:33 -0600

FranciscoD_ gravatar image

To start with, you look at /var/log/fedup.log. If you find errors, please edit your question and paste them for us to look at.

Also see what version of fedora-release you have installed. If it isn't the fedora 20 package, you can update it to the correct version by installing the rpm manually:

sudo yum install

Once done,sudo yum distro-sync should get your system up to date.

Fedup should ideally update all these packages for you. There should be some errors in the upgrade process.

edit flag offensive delete link more

answered 2013-12-29 09:22:36 -0600

khaledb gravatar image

fedup 18 to 19 then fedup 19 to 20

edit flag offensive delete link more


While this would work, it does not seem necessary to migrate to Fedora 19 before going directly to 20. While I did have issues (probably not related to this), after sorting out yum/rpm thanks to @FranciscoD_, the upgrade ultimately worked.

dstockwell gravatar imagedstockwell ( 2013-12-30 07:22:07 -0600 )edit

answered 2013-12-29 22:03:28 -0600

Thanks to mether and FranciscoD_ all is now working.

I suspect that in the final stages of fedup-driven upgrade, something happened in the process that rolled the package database back to fc18. Perhaps related to my LVM/mdadm/soft RAID-1 configuration, that also had the /var in its own partition (mirrored across two drives).

Weird thing was that the kernel had been upgraded to Fedora 20, and also that I could not find anything that indicated a problem.

edit flag offensive delete link more



You might be running into There are other bugs listed at Glad it worked out for you nevertheless. Please mark the right answer and upvote answers you found helpful. Thanks!

mether gravatar imagemether ( 2013-12-29 22:48:35 -0600 )edit

Question Tools


Asked: 2013-12-28 23:06:03 -0600

Seen: 1,204 times

Last updated: Dec 30 '13