Talk:How to use PreUpgrade

From FedoraProject

Revision as of 18:02, 15 October 2011 by Kjohnstn (Talk | contribs)

Jump to: navigation, search

Why quaid put the needs_love tag on the page

If a PreUpgrade stand alone page is needed, that can be created separately with feature content, then have this page linked. However, most features use their Features/PreUpgrade-style page as the main reference point, so there is no reason to create a PreUpgrade page.

quaid 04:55, 24 November 2008 (UTC)

Another method to free space: Convert /boot to ext2

If /boot is an ext3 filesystem it's possible to free about 4 MB by converting it to an ext2 filesystem. It goes something like this:

umount /boot
tune2fs -O ^has_journal /dev/sda1 - where /dev/sda1 is the /boot partition
$EDITOR /etc/fstab - change ext3 to ext2 for /boot
mount /boot

-- Abo

Troubleshooting - "characters: ordinal not in range(128)"

I would suggested to add one more item into troubleshooting section. When using multibyte environment with local language, PreUpgrade can end with the message like this:

Traceback (most recent call last):
  File "/usr/share/preupgrade/preupgrade-cli.py", line 329, in <module>
    pu.main(release)
  File "/usr/share/preupgrade/preupgrade-cli.py", line 267, in main
    if not self.userconfirm():
  File "/usr/share/yum-cli/output.py", line 687, in userconfirm
    choice = raw_input(_('Is this ok [y/N]: '))
UnicodeEncodeError: 'ascii' codec can't encode characters in position 4-5: ordinal not in range(128)

Solution is to prepend LANG=C to the preupgrade-cli:

LANG=C;preupgrade-cli "Fedora 15 (Lovelock)"

This bug is still present in the actual repo version of yum (3.2.28-6.fc14) or PreUpgrade (1.1.9-1.fc14). Regarding ticket is 635432.


I just tried using preupgrade as described here, and discovered a couple of errors.

  • First: After downloading the install files, the upgrade did not install upon reboot. Using the instructions, I booted into the grub command line. The grub "kernel" and "initrd" commands show the paths "/boot/upgrade/...". That's wrong, the paths should just be "/upgrade/...".
  • Next: The Advice "Upgrade to current release directly" did not work for me. Current release is 15, my installation is 12. The upgrade died with the message: "Your current installation cannot be upgraded. This is likely due to it being too old. Only the previous two release [sic] may be upgraded. To upgrade older releases you must first upgrade through all intermediate releases".

-- kjohnstn