Upgrading to Fedora 19 (continued)
[root@moto F13toF18]# rpm -aq|head
liboil-0.3.16-5.fc15.i686
arj-3.10.22-13.fc15.i686
perl-POE-1.289-6.fc16.noarch
autocorr-sv-3.4.6.2-1.fc16.noarch
python-iniparse-0.4-3.fc15.noarch
unique-1.1.6-5.fc16.i686
kde-i18n-Finnish-3.5.10-17.fc18.noarch
finger-0.17-43.fc15.i686
hyphen-it-0.20071127-6.fc15.noarch
libXrender-devel-0.9.6-2.fc15.i686
[root@moto F13toF18]#
[root@moto F13toF18]#
Which is perfect and we're at FC19 with RPM and glibc and libdb. Now time to see if yum works so we try and get the FC19 repos this time to complete this job. First we cleanup the old rpm's with yum clean all which worked perfectly. Next check free space:
[root@moto yum]# du –max-depth=4|sort -nrk1|head -n 10
4377344 .
2627140 ./updates
2489928 ./updates/packages
1708940 ./fedora
1468708 ./fedora/packages
202024 ./fedora/gen
114036 ./updates/gen
25960 ./rpmfusion-free-updates
21352 ./rpmfusion-free-updates/packages
6896 ./rpmfusion-free
[root@moto yum]# yum clean all
Next check free space on /var since that is where the FC19 repos will be downloaded:
[root@moto yum]# df -m /var
Filesystem 1M-blocks Used Available Use% Mounted on
/dev/sdb6 9813 2023 7290 22% /var
[root@moto yum]#
Now I also check that the rpmlib (librpm.so.3) also has the right string from the error that was plaging us earlier:
[root@moto yum]# strings /usr/lib/librpmio.so.3|grep -i CheckUnifiedSystemdir
[root@moto yum]# strings /usr/lib/librpm.so.3|grep -i CheckUnifiedSystemdir
rpmlib(X-CheckUnifiedSystemdir)
[root@moto yum]#
And it does so filesystem and setupd would or should be satisfied in this update (hopefully). Next run the yum upgrader:
yum –releasever=19 distro-sync
And let's hope this time it get's further along. Deleting a few RPM's the system complains about certainly helps along the way to also clean up the system (As usual, we can get them later):
[root@moto yum]# rpm -e clutter-1.8.4-2.fc16.i686 gnome-color-manager-3.2.4-1.fc16.i686 cheese-libs-3.2.2-1.fc16.i686 pyclutter-1.3.2-2.fc15.i686 clutter-gesture-0.0.2-2.fc13.i686 libmash-0.1.0-2.fc16.i686 gnome-shell-3.2.2.1-1.fc16.i686 libmx-1.4.1-1.fc16.i686 mutter-3.2.2-1.fc16.i686 rhythmbox-2.90.1-17.git20110927.fc16.i686 clutter-gst-1.4.4-1.fc16.i686 clutter-gtk010-0.10.8-5.fc16.i686 clutter-gtk-1.0.4-1.fc16.i686 gthumb-2.14.4-1.fc16.i686 totem-3.2.1-2.fc16.i686 gnome-settings-daemon-3.2.3-1.fc16.i686 caribou-0.4.1-3.fc16.i686 control-center-3.2.3-1.fc16.i686 orca-3.2.1-2.fc16.i686 gnome-bluetooth-3.2.2-1.fc16.i686 gnome-bluetooth-libs-3.2.2-1.fc16.i686 bluez-4.96-3.fc16.i686 pulseaudio-module-bluetooth-0.9.23-1.fc16.i686
(gconftool-2:8479): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Unable to autolaunch a dbus-daemon without a $DISPLAY for X11
(gconftool-2:8508): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Unable to autolaunch a dbus-daemon without a $DISPLAY for X11
(gconftool-2:8519): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Unable to autolaunch a dbus-daemon without a $DISPLAY for X11
I/O warning : failed to load external entity "/usr/share/mime/packages/AdobeReader.xml"
[root@moto yum]#
But we get this sort of error, which is simple to resolve:
Total 2.4 MB/s | 3.4 GB 24:27
Retrieving key from file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-i386
The GPG keys listed for the "Fedora 19 – i386" repository are already installed but they are not correct for this package.
Check that the correct key URLs are configured for this repository.
Failing package is: ftgl-2.1.3-0.8.rc5.fc19.i686
GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-i386
And we update the fedora-release rpm's like this:
[root@moto F13toF18]# ls -altri fedora-release*19*
3320684 -rw-r–r– 1 root root 494316 Feb 25 09:07 fedora-release-notes-17.95.0-1.fc19.noarch.rpm
3581102 -rw-r–r– 1 root root 32472 Jun 21 19:27 fedora-release-19-2.noarch.rpm
3581137 -rw-r–r– 1 root root 573908 Jun 25 15:13 fedora-release-notes-19-0.13.noarch.rpm
[root@moto F13toF18]#
[root@moto F13toF18]# rpm -Uvh fedora-release-19-2.noarch.rpm fedora-release-notes-19-0.13.noarch.rpm
warning: fedora-release-19-2.noarch.rpm: Header V3 RSA/SHA256 Signature, key ID fb4b18e6: NOKEY
Preparing… ################################# [100%]
Updating / installing…
1:fedora-release-notes-19-0.13 ################################# [ 25%]
2:fedora-release-19-2 ################################# [ 50%]
Cleaning up / removing…
3:fedora-release-notes-17.1.0-1.fc1################################# [ 75%]
4:fedora-release-18-1 ################################# [100%]
[root@moto F13toF18]#
[root@moto F13toF18]#
[root@moto F13toF18]#
Then we rerun yum updater from above. We will run yum update instead or yum update rpm. The –releaseserver=19 pulled FC 18 packages for some reason. We use yum because of this (This is normal since we h a c k e d the RPM install and did that manually):
** Found 15 pre-existing rpmdb problem(s), 'yum check' output follows:
rpm-4.10.3.1-1.fc18.i686 has missing requires of libdb-5.3.so
rpm-build-4.10.3.1-1.fc18.i686 has missing requires of libdb-5.3.so
rpm-build-4.10.3.1-1.fc18.i686 has missing requires of librpmbuild.so.3
rpm-build-libs-4.9.1.3-8.fc17.i686 has missing requires of librpm.so.2
rpm-build-libs-4.9.1.3-8.fc17.i686 has missing requires of librpmio.so.2
rpm-build-libs-4.9.1.3-8.fc17.i686 has missing requires of rpm-libs(x86-32) = ('0', '4.9.1.3', '8.fc17')
rpm-devel-4.10.3.1-1.fc18.i686 has missing requires of libdb-5.3.so
rpm-devel-4.10.3.1-1.fc18.i686 has missing requires of librpmbuild.so.3
rpm-devel-4.10.3.1-1.fc18.i686 has missing requires of librpmsign.so.1
rpm-devel-4.10.3.1-1.fc18.i686 has missing requires of rpm-build-libs(x86-32) = ('0', '4.10.3.1', '1.fc18')
rpm-libs-4.10.3.1-1.fc18.i686 has missing requires of libdb-5.3.so
rpm-python-4.10.3.1-1.fc18.i686 has missing requires of libdb-5.3.so
rpm-python-4.10.3.1-1.fc18.i686 has missing requires of librpmbuild.so.3
rpm-python-4.10.3.1-1.fc18.i686 has missing requires of librpmsign.so.1
rpmreaper-0.1.6-9.fc17.i686 has missing requires of librpm.so.2
[root@moto yum]#
And we wait for the 1.1GB of files. After some minor conflict resolutions, we we need to look at some resolutions for rpm, filesystem and systemd:
Transaction Check Error:
file /usr/bin/db_archive from install of libdb-utils-5.3.21-11.fc19.i686 conflicts with file from package db4-utils-4.8.30-3.fc15.i686
file /usr/bin/db_checkpoint from install of libdb-utils-5.3.21-11.fc19.i686 conflicts with file from package db4-utils-4.8.30-3.fc15.i686
file /usr/bin/db_deadlock from install of libdb-utils-5.3.21-11.fc19.i686 conflicts with file from package db4-utils-4.8.30-3.fc15.i686
file /usr/bin/db_dump from install of libdb-utils-5.3.21-11.fc19.i686 conflicts with file from package db4-utils-4.8.30-3.fc15.i686
file /usr/bin/db_dump185 from install of libdb-utils-5.3.21-11.fc19.i686 conflicts with file from package db4-utils-4.8.30-3.fc15.i686
file /usr/bin/db_hotbackup from install of libdb-utils-5.3.21-11.fc19.i686 conflicts with file from package db4-utils-4.8.30-3.fc15.i686
file /usr/bin/db_load from install of libdb-utils-5.3.21-11.fc19.i686 conflicts with file from package db4-utils-4.8.30-3.fc15.i686
file /usr/bin/db_printlog from install of libdb-utils-5.3.21-11.fc19.i686 conflicts with file from package db4-utils-4.8.30-3.fc15.i686
file /usr/bin/db_recover from install of libdb-utils-5.3.21-11.fc19.i686 conflicts with file from package db4-utils-4.8.30-3.fc15.i686
file /usr/bin/db_stat from install of libdb-utils-5.3.21-11.fc19.i686 conflicts with file from package db4-utils-4.8.30-3.fc15.i686
file /usr/bin/db_upgrade from install of libdb-utils-5.3.21-11.fc19.i686 conflicts with file from package db4-utils-4.8.30-3.fc15.i686
file /usr/bin/db_verify from install of libdb-utils-5.3.21-11.fc19.i686 conflicts with file from package db4-utils-4.8.30-3.fc15.i686
file /usr/lib/girepository-1.0/Colord-1.0.typelib from install of colord-libs-1.0.2-1.fc19.i686 conflicts with file from package colord-0.1.21-1.fc16.i686
file /usr/lib/libcolord.so.1 from install of colord-libs-1.0.2-1.fc19.i686 conflicts with file from package colord-0.1.21-1.fc16.i686
file /etc/rpm/macros.systemd from install of systemd-204-9.fc19.i686 conflicts with file from package systemd-units-37-25.fc16.i686
file /usr/share/man/man1/systemctl.1.gz from install of systemd-204-9.fc19.i686 conflicts with file from package systemd-units-37-25.fc16.i686
file /usr/share/pkgconfig/systemd.pc from install of systemd-204-9.fc19.i686 conflicts with file from package systemd-units-37-25.fc16.i686
Error Summary
————-
[root@moto F13toF18]#
[root@moto F13toF18]#
[root@moto F13toF18]#
[root@moto F13toF18]#
[root@moto F13toF18]# rpm -e db4-utils-4.8.30-3.fc15.i686
error: Failed dependencies:
/usr/bin/db_stat is needed by (installed) rpm-4.10.3.1-1.fc18.i686
[root@moto F13toF18]# rpm -ql rpm-4.10.3.1-1.fc18.i686|head -n 10
/bin/rpm
/etc/rpm
/usr/bin/rpm2cpio
/usr/bin/rpmdb
/usr/bin/rpmkeys
/usr/bin/rpmquery
/usr/bin/rpmverify
/usr/lib/rpm
/usr/lib/rpm/macros
/usr/lib/rpm/platform
[root@moto F13toF18]#
Some of the complaints can be unlinked:
[root@moto F13toF18]# ls -al /usr/lib/libcolord.so.1
lrwxrwxrwx 1 root root 19 Jul 19 12:39 /usr/lib/libcolord.so.1 -> libcolord.so.1.0.11
[root@moto F13toF18]# unlink /usr/lib/libcolord.so.1
[root@moto F13toF18]#
But let's restore the link above and do this instead. Copy the old files of a package + the linkeage and overall setup / size like this:
[root@moto colord.fc16]# ls -altri
total 36
1685047 drwxr-xr-x 3 root root 4096 Aug 9 14:38 var
1684514 drwxr-xr-x 6 root root 4096 Aug 9 14:38 usr
1684509 dr-xr-xr-x 4 root root 4096 Aug 9 20:25 lib
1684505 drwxr-xr-x 4 root root 4096 Aug 10 08:20 etc
1653312 drwxr-xr-x 9 root root 4096 Aug 10 09:33 ..
2093063 -rw-r–r– 1 root root 10463 Aug 10 09:49 colord.fc16.config
1684504 drwxr-xr-x 6 root root 4096 Aug 10 09:49 .
[root@moto colord.fc16]#
Using these commands:
mkdir colord.fc16; cd colord.fc16;
ls -altri $(rpm -ql colord-0.1.21-1.fc16.i686) > colord.fc16.config
cp -ip –parents $(rpm -ql colord-0.1.21-1.fc16.i686) .
so in case when re remove the package from the DB using
rpm -e –noscripts –justdb –nodeps colord-0.1.21-1.fc16.i686 we can restore the files using sash. We just need to get the yum installer proceed and replace existing files so we want to just remove stuff from the DB and NOT the filesystem:
[root@moto colord.fc16]# rpm -e –noscripts –justdb colord-0.1.21-1.fc16.i686
error: Failed dependencies:
libcolord.so.1 is needed by (installed) gtk3-3.2.4-1.fc16.i686
colord is needed by (installed) foomatic-4.0.8-8.fc16.i686
[root@moto colord.fc16]# rpm -e –noscripts –justdb –nodeps colord-0.1.21-1.fc16.i686
[root@moto colord.fc16]#
[root@moto colord.fc16]#
[root@moto colord.fc16]# ls -altri /usr/lib/colord-sensors/libcolord_sensor_huey.so
4735235 -rwxr-xr-x 1 root root 22020 May 22 2012 /usr/lib/colord-sensors/libcolord_sensor_huey.so
[root@moto colord.fc16]#
And one of the issues reported should be good without having anything broken in the interim:
file /usr/lib/girepository-1.0/Colord-1.0.typelib from install of colord-libs-1.0.2-1.fc19.i686 conflicts with file from package colord-0.1.21-1.fc16.i686
file /usr/lib/libcolord.so.1 from install of colord-libs-1.0.2-1.fc19.i686 conflicts with file from package colord-0.1.21-1.fc16.i686
And the above error is gone. Now to do the same with the other packages:
db4-utils-4.8.30-3.fc15.i686
systemd-units-37-25.fc16.i686
We'll use slightly modified lines for systemd:
/bin/cp -Rp –parents $(rpm -ql systemd-units-37-25.fc16.i686) .
rpm -e –noscripts –justdb –nodeps systemd-units-37-25.fc16.i686
But unfortunately we got a bunch of these:
uucp-1.07-26.fc16.i686 has missing requires of systemd-units
uucp-1.07-26.fc16.i686 has missing requires of systemd-units
wicd-common-1.7.0-15.fc16.noarch has missing requires of systemd-units
wicd-common-1.7.0-15.fc16.noarch has missing requires of systemd-units
So we restore the files from the new filesystem FC19 rpm to see what it needs:
[root@moto packages]# pwd
/var/cache/yum/updates/packages
[root@moto packages]# cd filesystem
[root@moto filesystem]# ls -altri
total 1308
261118 drwxrwxrwt 2 root root 4096 Jul 8 04:56 tmp
261117 drwxr-xr-x 2 root root 4096 Jul 8 04:56 sys
261116 drwxr-xr-x 2 root root 4096 Jul 8 04:56 srv
261114 drwxr-xr-x 2 root root 4096 Jul 8 04:56 run
261113 dr-xr-x— 2 root root 4096 Jul 8 04:56 root
261112 dr-xr-xr-x 2 root root 4096 Jul 8 04:56 proc
261111 drwxr-xr-x 2 root root 4096 Jul 8 04:56 opt
261110 drwxr-xr-x 2 root root 4096 Jul 8 04:56 mnt
261109 drwxr-xr-x 2 root root 4096 Jul 8 04:56 media
261107 drwxr-xr-x 2 root root 4096 Jul 8 04:56 home
261090 drwxr-xr-x 2 root root 4096 Jul 8 04:56 dev
261089 dr-xr-xr-x 2 root root 4096 Jul 8 04:56 boot
261087 -rw-r–r– 1 root root 1063760 Jul 8 11:44 filesystem-3.2-13.fc19.i686.rpm
259650 drwxr-xr-x 3 root root 200704 Aug 10 10:20 ..
276063 drwxr-xr-x 17 root root 4096 Aug 10 10:21 var
261119 drwxr-xr-x 12 root root 4096 Aug 10 10:21 usr
261115 lrwxrwxrwx 1 root root 8 Aug 10 10:21 sbin -> usr/sbin
261108 lrwxrwxrwx 1 root root 7 Aug 10 10:21 lib -> usr/lib
261091 drwxr-xr-x 11 root root 4096 Aug 10 10:21 etc
261088 lrwxrwxrwx 1 root root 7 Aug 10 10:21 bin -> usr/bin
261086 drwxr-xr-x 17 root root 4096 Aug 10 10:21 .
[root@moto filesystem]#
Then seeing how it now links certain critical folders together now vs the old way, we do some adjustments by running rsync then linking ourselves (we'll use sash if things get messed up) up to the /usr ones:
[root@moto lib]#
[root@moto lib]# du -sm .
3065 .
[root@moto lib]#
[root@moto lib]# ls -altri|wc -l
5538
[root@moto lib]#
[root@moto lib]#
[root@moto lib]# pwd
/usr/lib
[root@moto lib]# rsync -avhr /lib/ ./
sent 300.34M bytes received 184.49K bytes 6.20M bytes/sec
total size is 300.00M speedup is 1.00
[root@moto lib]#
Sure enough it breaks and we need to use sash again:
[root@moto /]# mv lib lib2
[root@moto /]# ln -s /usr/lib lib
-bash: /bin/ln: /lib/ld-linux.so.2: bad ELF interpreter: No such file or directory
Segmentation fault
[root@moto /]# sash
Stand-alone shell (version 3.7)
> -ln -s /usr/lib lib
> quit
[root@moto /]# ln -s /usr/lib lib-test
[root@moto /]# ls -altri lib
47 lrwxrwxrwx 1 root root 8 Aug 10 10:39 lib -> /usr/lib
[root@moto /]# ls -altri lib2
But in the end the above works. (Note we can use /usr/bin/rsync because it's in /usr/bin). We do the same with /sbin and /bin.
[root@moto sbin]# pwd
/usr/sbin
[root@moto sbin]# rsync -avh /sbin/ .
sent 24.27M bytes received 6.06K bytes 9.71M bytes/sec
total size is 24.25M speedup is 1.00
[root@moto /]# mv bin bin-fc13-fc19
[root@moto /]# ln -s /usr/bin bin
-bash: /bin/ln: No such file or directory
Segmentation fault
[root@moto /]# /usr/bin/ln -s /usr/bin bin
[root@moto /]# ls -altrid bin
50 lrwxrwxrwx 1 root root 8 Aug 10 10:53 bin -> /usr/bin
[root@moto /]# ln
ln: missing file operand
Try `ln –help' for more information.
[root@moto /]# which ln
/bin/ln
[root@moto /]# ls -altrid lib sbin bin
47 lrwxrwxrwx 1 root root 8 Aug 10 10:54 sbin -> usr/sbin
50 lrwxrwxrwx 1 root root 7 Aug 10 10:54 lib -> usr/lib
51 lrwxrwxrwx 1 root root 7 Aug 10 10:54 bin -> usr/bin
[root@moto /]# ls -altrid lib* sbin* bin*
784897 dr-xr-xr-x. 21 root root 20480 Aug 9 20:25 lib-fc13-fc19
2779841 dr-xr-xr-x. 2 root root 12288 Aug 10 07:58 sbin-fc13-fc19
3303105 dr-xr-xr-x. 2 root root 4096 Aug 10 07:58 bin-fc13-fc19
45 lrwxrwxrwx 1 root root 7 Aug 10 10:18 bin;52064ba8 -> usr/bin
46 lrwxrwxrwx 1 root root 7 Aug 10 10:18 bin;52064bc9 -> usr/bin
47 lrwxrwxrwx 1 root root 8 Aug 10 10:54 sbin -> usr/sbin
50 lrwxrwxrwx 1 root root 7 Aug 10 10:54 lib -> usr/lib
51 lrwxrwxrwx 1 root root 7 Aug 10 10:54 bin -> usr/bin
[root@moto /]#
And now that all is linked, installing the new filesystem RPM goes without a hitch:
[root@moto filesystem]# rpm -Uvh filesystem-3.2-13.fc19.i686.rpm
Preparing… ################################# [100%]
Updating / installing…
1:filesystem-3.2-13.fc19 ################################# [ 50%]
Cleaning up / removing…
2:filesystem-2.4.44-1.fc16 ################################# [100%]
[root@moto filesystem]#
And we try to update now to see if that made a difference:
wicd-common-1.7.0-15.fc16.noarch has missing requires of systemd-units
1:wpa_supplicant-0.7.3-11.fc16.i686 has missing requires of systemd-units
1:wpa_supplicant-0.7.3-11.fc16.i686 has missing requires of systemd-units
2:xinetd-2.3.14-47.fc16.i686 has missing requires of systemd-units
2:xinetd-2.3.14-47.fc16.i686 has missing requires of systemd-units
ypserv-2.29-1.fc16.i686 has missing requires of systemd-units
ypserv-2.29-1.fc16.i686 has missing requires of systemd-units
zvbi-0.2.33-9.fc16.i686 has missing requires of systemd-units
zvbi-0.2.33-9.fc16.i686 has missing requires of systemd-units
Installing : 3:texlive-base-2013-0.1.20130608_r30832.fc19.noarch 1/2403
Updating : kdesdk-common-4.10.5-1.fc19.noarch 2/2403
Updating : 7:kdenetwork-common-4.10.5-3.fc19.noarch 3/2403
Updating : wine-filesystem-1.6-1.fc19.noarch 4/2403
Updating : shared-desktop-ontologies-0.11.0-1.fc19.noarch 5/2403
Installing : 1:cups-filesystem-1.6.3-4.fc19.noarch 6/2403
Updating : m17n-db-1.6.4-2.fc19.noarch 7/2403
Installing : 3:texlive-texlive-en-doc-svn30632.0-0.1.fc19.noarch 8/2403
Installing : 3:texlive-texlive-common-doc-svn30524.0-0.1.fc19.noarch 9/2403
Updating : xemacs-filesystem-21.5.33-5.fc19.noarch 10/2403
Installing : m17n-db-extras-1.6.4-2.fc19.noarch 11/2403
Installing : wine-mono-0.0.8-1.fc19.noarch 12/2403
Updating : wine-tahoma-fonts-1.6-1.fc19.noarch 13/2403
Installing : tigervnc-icons-1.3.0-3.fc19.noarch 14/2403
Updating : ufraw-common-0.19.2-2.fc19.i686 15/2403
Updating : xorg-x11-server-common-1.14.2-9.fc19.i686 16/2403
And it did! Good, so we're off to an upgrade. ( Perhaps we could have done this step earlier but we could not have until RPM got updated anyway as we did. :/ ). And we got a successful complete:
There are unfinished transactions remaining. You might consider running yum-complete-transaction, or "yum history redo last", first to finish them. If that doesn't work you'll have to try removing/installing packages by hand (maybe package-cleanup can help).
Complete!
You have new mail in /var/spool/mail/root
[root@moto F13toF18]#
Now to do a full update. We'll now try to upgrade with fedup. We tried this before but it didn't work due to the substantial fundamental changes beetween the fedora versions.
fedup –network 19
And we're off. After it downloads stuff, it's time to reboot. Sure enough, after a reboot we're at FC19, the GUI works, aside from some networking issues, but we are back in business. The rest of the errors can be resolved with some basic OS tweaking which we'll leave for other posts.
Cheers,
TK
