How To Upgrade From Fedora 12 To Fedora 13 (Desktop & Server)

Want to support HowtoForge? Become a subscriber!
 
Submitted by falko (Contact Author) (Forums) on Fri, 2010-05-28 10:54. :: Fedora

How To Upgrade From Fedora 12 To Fedora 13 (Desktop & Server)

Version 1.0
Author: Falko Timme <ft [at] falkotimme [dot] com>
Follow me on Twitter
Last edited 05/27/2010

This article describes how you can upgrade your Fedora 12 system to Fedora 13. The upgrade procedure works for both desktop and server installations.

I do not issue any guarantee that this will work for you!

 

1 Preliminary Note

The commands in this article must be executed with root privileges. Open a terminal (on a Fedora 12 desktop, go to Applications > System Tools > Terminal) and log in as root, or if you log in with a regular user, type

su

to become root.

 

2 Upgrading To Fedora 13 (Desktop)

First we must upgrade the rpm package:

yum update rpm

Then we install the latest updates:

yum -y update

Next we clean the yum cache:

yum clean all

If you notice that a new kernel got installed during yum -y update, you should reboot the system now:

reboot

(After the reboot, log in as root again, either directly or with the help of

su

)

Now we come to the upgrade process. We can do this with preupgrade (preupgrade will also take care of your RPMFusion packages).

Install preupgrade...

yum install preupgrade

... and call it like this:

preupgrade

The preupgrade wizard will then start on your desktop. Select Fedora 13 (Goddard). Afterwards the system is being prepared for the upgrade.

At the end, click on the Reboot Now button.

During the reboot, the upgrade is being performed. This can take quite a long time, so please be patient.

Afterwards, you can log into your new Fedora 13 desktop.

 

3 Upgrading To Fedora 13 (Server)

First we must upgrade the rpm package:

yum update rpm

Then we install the latest updates:

yum -y update

Next we clean the yum cache:

yum clean all

If you notice that a new kernel got installed during yum -y update, you should reboot the system now:

reboot

(After the reboot, log in as root again, either directly or with the help of

su

)

Now we come to the upgrade process. We can do this with preupgrade.

Install preupgrade...

yum install preupgrade

... and call it like this:

preupgrade-cli

It will show you a list of releases that you can upgrade to. If all goes well, it should show something like Fedora 13 (Goddard) in the list:

[root@server1 ~]# preupgrade-cli
Loaded plugins: blacklist, whiteout
No plugin match for: rpm-warm-cache
No plugin match for: remove-with-leaves
No plugin match for: auto-update-debuginfo
No plugin match for: presto
Loaded plugins: refresh-packagekit
please give a release to try to pre-upgrade to
valid entries include:
   "Fedora 13 (Goddard)"
   "Rawhide"
[root@server1 ~]#

To upgrade, append the release string to the preupgrade-cli command:

preupgrade-cli "Fedora 13 (Goddard)"

Preupgrade will also take care of your RPMFusion packages, so all you have to do after preupgrade has finished is to reboot:

reboot

During the reboot, the upgrade is being performed. This can take quite a long time, so please be patient. Afterwards, you can log into your new Fedora 13 server.

 

4 Links


Please do not use the comment function to ask for help! If you need help, please use our forum.
Comments will be published after administrator approval.
Submitted by Gregk610 (not registered) on Mon, 2011-08-08 03:32.

Just wanted to pass on to anyone else doing the same as me.   I finally decided to upgrade my Fedora Core 10 server using the Yum method, and ran into a little problem when trying to go from FC 12 to FC 13.

It seems that the regular installer took care of this problem, but the yum method doesn't know about it.   You see they upgraded from an ext3 filesystem to ext4 back around FC11 from what I have read.  

When attempting the upgrade to Fedora Core 13, the installer complained that it couldn't see the previous installation.  Well, you guessed it, it was looking for an ext4 partition, and I didn't have any.   All mine were ext3!   Well, long story short, but after some looking and I found this page, that helped out!   

So, hope all this works out, and helps everyone else!   

 Upgrade ext3 to ext4 file system when upgrading fedora core 13

Submitted by Anonymous (not registered) on Mon, 2010-05-31 18:35.

Fail:

# preupgrade-cli

Loaded plugins: blacklist, dellsysidplugin2, priorities, versionlock, whiteout
No plugin match for: rpm-warm-cache
No plugin match for: auto-update-debuginfo
No plugin match for: refresh-packagekit
No plugin match for: presto
Traceback (most recent call last):
File "/usr/share/preupgrade/preupgrade-cli.py", line 316, in <module>
pu = PreUpgradeCli()
File "/usr/share/preupgrade/preupgrade-cli.py", line 52, in __init__
PreUpgrade.__init__(self)
File "/usr/lib/python2.6/site-packages/preupgrade/__init__.py", line 80, in __init__
self._getConfig()
File "/usr/lib/python2.6/site-packages/yum/__init__.py", line 282, in _getConfig
startupconf.pluginconfpath,disabled_plugins,enabled_plugins)
File "/usr/lib/python2.6/site-packages/yum/__init__.py", line 465, in doPluginSetup
plugin_types, confpath, disabled_plugins, enabled_plugins)
File "/usr/lib/python2.6/site-packages/yum/plugins.py", line 160, in __init__
self.run('config')
File "/usr/lib/python2.6/site-packages/yum/plugins.py", line 177, in run
func(conduitcls(self, self.base, conf, **kwargs))
File "/usr/lib/yum-plugins/versionlock.py", line 153, in config_hook
conduit.registerCommand(VersionLockCommand())
File "/usr/lib/python2.6/site-packages/yum/plugins.py", line 499, in registerCommand
self._base.registerCommand(command)
File "/usr/share/yum-cli/cli.py", line 106, in registerCommand
if name in self.yum_cli_commands:

AttributeError: 'PreUpgradeCli' object has no attribute 'yum_cli_commands'


Submitted by Prabhat Kumar (not registered) on Fri, 2010-07-16 13:50.

I also faced same problem. But by googling I find solution from this article -

http://www.wilyness.com/blog/?p=137

Submitted by otheos (not registered) on Sat, 2010-05-29 21:58.

This, maybe for different reasons, has happened during the 11 to 12 upgrade, and it's happening again.

The error message that says:

"Not enough free space in /boot/upgrade to download install.img"

The /boot partition is the standard 200MB F11 created when it installed. It has 120MB free but apparently install.img is larger than this. Problem is that unlike the 11to12 similar message, this time it doesn't say how much more space it needs. It just stops there and says you can download this after reboot if you have a wire network. No dice, if I go on, all data is downloaded for the upgrade, but once it boots it goes back to 12 without noticing any upgrade scripts.

So, what's the deal with install.img and how do we get around it?

Thanks for the guide and excellent site.

Submitted by Rich Marschall (not registered) on Fri, 2010-06-11 04:18.
The problem your having is because you have to many kernels installed and a limited amount of boot space. Run this command in a terminal as root package-cleanup --oldkernels that will leave the original kernel and the latest you installed, all others will be removed leaving enough space for the upgrade. Like you I ran into the same problem during the last upgrade and that solved the problem. I guess you could allocate more space in the boot partition through LVM to achieve similar results. the preupgrade package should have some checks that will test these prerequisites before hand.
Submitted by Amit Agarwal (not registered) on Fri, 2010-05-28 11:26.

Instead of using preupgrade, you can use yum itself to upgrade with the command

yum --releasever=13 upgrade

 

This should work with most installations, at least that worked with mine.

Find the original article here.

http://blog.amit-agarwal.co.in