Comments on: Upgrading CentOS 5 to Fedora 12

By: Oded

Oded — Sun, 29 Aug 2010 11:17:42 +0000

Apparently there is a problem with the Textile plugin that I use to format text in the posts – it breaks on long articles and kills them completely, not sure why.

By: Oded

Oded — Fri, 27 Aug 2010 20:32:35 +0000

Theres something weird going on with my blog - i see the post fine in the editor and also the summary shows up when you visit a summary page like http://geek.co.il/wp/2010/02, but not in the blog itself. I'll check it out.

By: Minus

Minus — Fri, 27 Aug 2010 17:10:11 +0000

Hi,

I’m really interested to upgrade a Centos 5 to Fedora 12…
But your article is empty (I really don’t understand why ???)

Could you repost it ?

Thx

By: Oded

Oded — Tue, 20 Apr 2010 00:52:51 +0000

Well, I did mention as such at the start .

There are some issues with the process, but I think I made sure that no system libraries are left out in the cold in my process. Though I did start from a rather empty system and if you have additional non-default libraries and services on the machine in question, you might run into trouble with that – though I believe this is out of scope from the current article.

That being said, I want to readdress the whole process, especially due to CentOS 5.5 coming out, but also because – as AJ mentioned – I should provide pre-built packages for the “Building Required Software” stage instead of forcing people to rebuild it themselves.

By: Alan Horrocks

Alan Horrocks — Tue, 13 Apr 2010 15:56:08 +0000

Cheers, that sorted it.

Unfortunately I had all kinds of other issues – like rpm removing libraries that other system components where relying on (most notably libnss which basically stops anything useful from working). I did manage to get a bit further but in the end I think this is my cue to just ditch Centos and use something else.

Thanks for your help anyway – and if anyone else is considering doing this, definitely consider just using the Fedora CD to do the upgrade for you.

By: Oded

Oded — Fri, 09 Apr 2010 18:21:34 +0000

You have debug info build enabled, and RPM 4.7 doesn’t play nice with old-style debug packages.

You can disable debug symbol generation by adding “%debug_package %{nil}” to /etc/rpm/macros: http://www.redhat.com/archives/rpm-list/2005-November/msg00023.html

By: Alan Horrocks

Alan Horrocks — Thu, 08 Apr 2010 13:35:43 +0000

Hi, I thought that might happen. Here’s the output on pastebin.com

http://pastebin.com/uA7Uw2vx

By: Oded

Oded — Thu, 08 Apr 2010 11:07:14 +0000

The output you pasted was cut short before the interesting part, probably due to WordPress comments size limit

If you want, you can e-mail me the output and I will try to help with that, or you can pastebin.com the output and link it here.

By: Alan Horrocks

Alan Horrocks — Thu, 08 Apr 2010 10:31:21 +0000

Hi, in ‘building required software’ everything works up to step 9 – building rpm 4.7.
This fails to produce any rpms ends with an error about unpackaged files. I guess this is kind of a show stopper. My system is Centos 5.4, fully up to date.
I’ve attached the output from the rpmbuild command: (sorry it’s so long)

Tried with both 4.7.0 and 4.7.1 same results.

[Output removed by editor]

By: Oded

Oded — Thu, 01 Apr 2010 16:28:33 +0000

That is weird – the only reason the initial ramdisk would fail after the upgrade is if the upgrade also changed the kernel associated with the ramdisk, and that shouldn’t happen because you’re supposed to upgrade the kernel to the latest version right before generating the ramdisk.

If you have any more information, please share – I’d like to get to the bottom of this