F17 distro-sync yum upgrading from f16

[Pnx]

I have rpm upgrade an when I:

yum --releasever=17 --disableplugin=presto --skip-broken distro-sync

ERROR Necesita actualizar el rpm para manipular:
rpmlib(X-CheckUnifiedSystemdir) is needed by filesystem-3-2.fc17.x86_64
rpmlib(X-CheckUnifiedSystemdir) is needed by setup-2.8.48-1.fc17.noarch
El RPM necesita ser actualizado
Podría intentar ejecutar: rpm- Va --nofiles --nodigest
Su transacción fue guardada, vuelva a ejecutarla con:
 yum load-transaction /tmp/yum_save_tx.2012-04-22.10-17.VOfwLO.yumtx

Any idea¿?

[j0534ng31]

Originally Posted by Pnx

Any idea¿?

I did it by following the "Upgrading directly using Yum" method of this guide

Good luck!

[Pnx]

Me too, but when I do sync-distro I have that problem...

---------- Post added at 02:03 AM ---------- Previous post was at 02:01 AM ----------

I isn't SOLVED I make distro-sync excluding filesytem and setup packages and then make again dirto-sync...

Now I'm upgrading...

And It isn't solved...

[DBelton]

You did follow the special instructions for F17 since you are upgrading to it, didn't you? F17 made some changes to the filesystem and has special upgrading instructions if you use the distrosync method.

Quote from the Fedora docs:

Fedora 16 -> Fedora 17
Warning (medium size).png
This references an unreleased version of Fedora. The steps here may change before release.

First install the new Fedora 17 gpg key

rpm --import https://fedoraproject.org/static/1ACA3465.txt

Fedora 17 will locate the entire base operating system in /usr. The directories /bin, /sbin, /lib, /lib64 will only be symlinks:

/bin → /usr/bin
/sbin → /usr/sbin
/lib → /usr/lib
/lib64 → /usr/lib64

Some reasoning behind this change is outlined here:

http://www.freedesktop.org/wiki/Soft...ForTheUsrMerge

Currently installed systems need some manual steps to convert the current system to match the layout of Fedora 17. After that, the system can continue to be updated with YUM as usual.

Some RPM packages in Fedora 17 are carrying an RPM dependency guard, which will make sure, they can only be installed when /bin, /sbin, /lib, /lib64 are symlinks and not directories like in Fedora 16 and older.

The installed system’s base filesystem layout can not be safely altered, while the system itself is running on top of it. Dracut, the initramfs used to find and mount the root filesystem, can be instructed to convert the filesystem to match Fedora 17’s expectations.

If your system has a split-off /usr, a separate mount point, the dracut /usr mount conversion logic might not work. If /usr resides on the net, then ou should add "rd.neednet=1" and the network settings like "ip=dhcp" on the kernel command line. /usr on iSCSI, FCoE, NBD also is supported, as long as “netroot=...” is specified on the kernel command line for these disks (see man dracut.kernel(7)). If you have /usr on LVM, MD raid or DM raid, make sure the kernel command line has either all settings like "rd.lvm.lv=..." to ensure the /usr device is accessible in dracut or just remove all restrictions like "rd.lvm...", "rd.md...", "rd.dm...". Either way, you should probably use anaconda to update, if you are experiencing problems with a separate /usr.

Here are the steps to prepare your system, to convert it, and to be able to continue updating your installed system with yum:

Download and install the most recent dracut packages:

# yum update dracut

You should at least have dracut-009-15.fc15 for Fedora 15 or dracut-013-22.fc16 for Fedora 16.

Turn off any "hostonly" settings in /etc/dracut.conf*, if you turned on "hostonly".

Update the installed initramfs image for your current kernel, and instruct dracut to include the dracut module to convert your current filesystem:

# dracut --force --add convertfs

If your system has a split-off /usr, a separate mount point, and you don't know the kernel command line parameter to add, you can also try (dracut tries to generate them internally):

# dracut -H --force --add convertfs

If dracut detects ‘rd.convertfs’ on the kernel command line at bootup, it starts the filesystem conversion of the root filesystem. If it is already converted, it will just do nothing.
Warning (medium size).png
dracut will by default update the initramfs for the currently running kernel. Make sure that no new kernel has been installed since last boot and that you really will boot into the updated initramfs.

Change the following kernel commandline parameter directly in the bootloader menu, which is shown during bootup, or edit the line in /etc/grub*.cfg to remove ro and rhgb and append rw rd.info rd.convertfs enforcing=0

Explanation of the options:

- remove “ro” (read only)
- append “rw” (read write) to let dracut mount your root filesystem writeable
- remove “rhgb” (Red Hat graphical boot) to disable the graphical bootsplash
- append “rd.info” to get a more verbose output from dracut
- append “rd.convertfs” to enable the /usr-move conversion script in dracut
- append “enforcing=0” to disable SELinux enforcement

During bootup, dracut will now convert your filesystem, and /lib, /lib64, /bin and /sbin should then all be symbolic links to the corresponding directories in /usr.

After the conversion, the system needs to be immediately updated to Fedora 17. No packages from Fedora 16 or Fedora 15, or older rawhide packages must be installed anymore. Make sure to disable any Fedora 15 and Fedora 16 repositories in yum!

Any files with conflicting names, which the conversion could not resolve, will be backed up to files named *.usrmove~ residing in /usr/lib, /usr/lib64, /usr/bin and /usr/sbin.

Verify that dracut really completed the conversion. The log messages, which dracut has generated during bootup, can be retrieved with:

# dmesg | grep dracut

After a successful conversion, revert the changes made to the kernel command line in the bootloader config file /etc/grub*.cfg.

Then run,

# yum --releasever=17 update rpm
# rm -f /var/lib/rpm/__*
# rpm --rebuilddb
# yum --releasever=17 --disableplugin=presto --skip-broken distro-sync
# fixfiles onboot

After upgrading, all should be set and done.

Have fun with your system and say “Good bye” to /bin, /sbin, /lib, /lib64 and meet them in /usr.

[j0534ng31]

Originally Posted by DBelton

You did follow the special instructions for F17 since you are upgrading to it, didn't you? F17 made some changes to the filesystem and has special upgrading instructions if you use the distrosync method.

I did it that way (F16 -> F17), a bit adapted to my case, and everything worked flawlessly... I mean, it can be done; there are no errors in the method explained in this guide.