Page 1 of 1

dependeces inside VPS

Posted: Thu Jan 19, 2006 8:03 pm
by ivan
If i try yum update on a FC2 VPS i get the following error:

Package glibc-dummy-fedora-core-2 needs glibc-common = 2.3.3-27.1, this is not available

Don't know what is exactly it but don't understant this:

# rpm -qa glibc-dummy-fedora-core-2
glibc-dummy-fedora-core-2-2.3.3-27.1.1.swsoft

rpm -qa glibc-common
glibc-common-2.3.3-27.1

So it seems i've it!

I use this yum conf:

[base]
name=Atomic Rocket Turtle - $releasever - Base OS RPMS mirror
baseurl=http://3es.atomicrocketturtle.com/3rd-p ... eleasever/

[updates]
name=Atomic Rocket Turtle - $releasever - OS Update RPMS mirror
baseurl=http://3es.atomicrocketturtle.com/3rd-p ... eleasever/

Posted: Thu Jan 19, 2006 11:09 pm
by scott
You're kind of stuck in a weird spot there. I build my packages for regular servers, not vservers, which in the case of virtuozzo manipulate the base OS. You're not really running the standard OS, so youve got to work around the weird things they did to make it work with their systems.

Posted: Tue Jan 24, 2006 2:09 am
by pepe
Try rebuilding the rpm database...

Whenever my main server company updates its VPSs, the rpm tables get messed up and need to be rebuilt.

Posted: Tue Jan 24, 2006 9:32 pm
by scott
I know exactly what is doing that, I run into the same problem in my build environment. Whats going on is that the master OS that the vservers are running under, uses a more modern version of rpm/db. Probably running FC3/4, or CentOS4/RHEL4. Heres the best way to make sure you clean things up after that:

rm -f /var/lib/rpm/__*
rpm --rebuilddb

Posted: Tue Feb 21, 2006 8:39 am
by breun
Those virtual servers seem to have some kind of dummy glibc package. You can also just tell yum to ignore glibc:

Code: Select all

yum --exclude=glibc\* update
This will get you updates for other packages.