Fedora 9 was released on the 13th. I waited a whole three days to make sure I wasn’t going to be the beta-tester. Then I tried out the live release, and finally decided to upgrade my main workstation to Fedora 9 today. To be sure I wouldn’t mess stuff up, I used the DVD installer to upgrade.

The upgrade finished fine, but when I rebooted, XChat would not run.

[14:15:53]$ xchat
xchat: error while loading shared libraries: libperl.so: cannot open shared object file: No such file or directory

What did rpm have to say about this?

[14:26:31]$ rpm -q xchat


Hmm . . .  looks like the package did not get upgraded. Wondering how many others did not get upgraded, I did a quick check:

[14:26:39]$ rpm -qa | grep fc8|wc -l

Wow! 139 packages still carry the fc8 tag! Next I checked if the updates repository has the updates:

[root@rajlin ~]# yum update

Transaction Summary
Install     18 Package(s)
Update     148 Package(s)
Remove       0 Package(s)

While I didn’t check all the packages in the list, XChat is definitely there:

xchat                   i386       1:2.8.4-15.fc9   fedora            1.3 M

So did Fedora just push out a release with old packages just to stay on schedule, and is actually releasing packages now hoping nobody would notice? I mounted the install DVD (all 3.4G of it, by the way) and checked:

[root@rajlin Packages]# rpm -q xchat
[root@rajlin Packages]# rpm -q xinetd
[root@rajlin Packages]# ls -ltrh xch*
ls: cannot access xch*: No such file or directory
[root@rajlin Packages]# ls -ltrh xinet*
ls: cannot access xinet*: No such file or directory
[root@rajlin Packages]#

These packages are just not there! And now I’m doing a network upgrade. It makes me wonder what I got for 3.4G worth of downloaded DVD. Readers — any similar experiences or advice?

Oh well . . .  on to better (!?) things — I will be installing Oracle next to see how that works on this shiny new distribution. Expect a report soon.