upgrading from CentOS 4.3 -> 4.4 Missing Dependency: glibc-common

jamesbond

Well-Known Member
Oct 9, 2002
738
1
168
I tried upgrading from CentOS 4.3 to 4.4 but I get this error:

Code:
--> Running transaction check
--> Processing Dependency: libgomp = 4.1.0-18.EL4 for package: gcc4
--> Processing Dependency: glibc-common = 2.3.4-2.19 for package: glibc-dummy-centos-4
--> Restarting Dependency Resolution with new changes.
--> Populating transaction set with selected packages. Please wait.
---> Package libgomp.i386 0:4.1.0-18.EL4 set to be updated
--> Running transaction check
--> Processing Dependency: glibc-common = 2.3.4-2.19 for package: glibc-dummy-centos-4
--> Finished Dependency Resolution
Error: Missing Dependency: glibc-common = 2.3.4-2.19 is needed by package glibc-dummy-centos-4
I tried updating/installing glibc, which didn't work.
 

chilihost

Well-Known Member
Mar 1, 2005
72
0
156
this upgrade has been DISASTEROUS. After up2date, I have had to set the cPanel updates to STABLE tree and then to a /scripts/upcp - I believe the problem is CentOS 4.4 installs a new version of Perl which cPanel cannot locate, plus there was heaps of issues with named too.
 

rachweb

Well-Known Member
Jun 26, 2004
268
0
166
amsterdam
jamesbond said:
I'm trying this on a VPS, I doubt removing the kernel form yum.conf will do any good...
The problem is that centos 4.4 requires the new kernel version. If you don't want install the new one then you can't upgrade.
 

rachweb

Well-Known Member
Jun 26, 2004
268
0
166
amsterdam
chilihost said:
this upgrade has been DISASTEROUS. After up2date, I have had to set the cPanel updates to STABLE tree and then to a /scripts/upcp - I believe the problem is CentOS 4.4 installs a new version of Perl which cPanel cannot locate, plus there was heaps of issues with named too.
Use yum upgrade instead of up2date -u
 

chilihost

Well-Known Member
Mar 1, 2005
72
0
156
really??? is it that easy...holy cow!!! I am all for that new kernel - I was installing it as a seperate task to be safe. Thanks for the tip, will give it a go right now :)
 

jamesbond

Well-Known Member
Oct 9, 2002
738
1
168
rachweb said:
The problem is that centos 4.4 requires the new kernel version. If you don't want install the new one then you can't upgrade.
Thanks, I was not aware of that.
 

imkite

Member
Sep 3, 2006
5
0
151
jamesbond said:
I'm trying this on a VPS, I doubt removing the kernel form yum.conf will do any good...
add exclude=glibc* to /etc/yum.conf

had the same problem that fixed it
 

jamesbond

Well-Known Member
Oct 9, 2002
738
1
168
Thanks, that worked! Did you remove glibc* from the exclude line after updating to 4.4 or are you leaving it there?
 

jamesbond

Well-Known Member
Oct 9, 2002
738
1
168
It seems /scripts/upcp removes the glibc* entry at the end of the exclude line for some reason.

Haven't tried adding exclude=glibc* on a seperate line.
 

chirpy

Well-Known Member
Verifed Vendor
Jun 15, 2002
13,465
30
473
Go on, have a guess
That's naughty - I'd log a bugzilla entry asking that /scripts/checkyum doesn't strip out any exclusions that you've added yourself.
 

rikgarner

Well-Known Member
Mar 31, 2006
75
1
158
/dev/null
I popped a "yum upgrade" on our development (read test) Centos 4.3 boxes, and it all went through to 4.4 pretty much seamlessly. I did remove kernel* from the yum excludes before doing it (and have since put it back in), but as far as I can tell, it didnt break anything.

I have stopped using up2date - it seems to cause more problems than yum does (do they perform dependancy checking in a different way? I generally feel yum is more thorough).

Rich
 

jamesbond

Well-Known Member
Oct 9, 2002
738
1
168
Just to be clear, the glibc problem described in my opening post is occuring on VPS only, dedicated servers are fine.