Hi everyone,
I have a home computer that I use to develop on, which it is running Whitebox 3.0. I have copied all the required CentOS 3.4 RPMs to /RPM, created a new yum repository and then updated, but when I try to upgrade, it fails on a "recursive dependency on glibc".
Is there any way I can force that dependency?
Would it be easier to upgrade to 4.0 using Anaconda?
Thanks for all the work
Gabriel
___________________________________________________________ ALL-NEW Yahoo! Messenger - all new features - even more fun! http://uk.messenger.yahoo.com
Am Donnerstag, den 27.01.2005, 09:56 +0000 schrieb first last: read this http://www.centos.org/modules/smartfaq/faq.php?faqid=19
Hi everyone,
I have a home computer that I use to develop on, which it is running Whitebox 3.0. I have copied all the required CentOS 3.4 RPMs to /RPM, created a new yum repository and then updated, but when I try to upgrade, it fails on a "recursive dependency on glibc".
Is there any way I can force that dependency?
Would it be easier to upgrade to 4.0 using Anaconda?
Thanks for all the work
Gabriel
___________________________________________________________ ALL-NEW Yahoo! Messenger - all new features - even more fun! http://uk.messenger.yahoo.com _______________________________________________ CentOS mailing list CentOS@caosity.org http://lists.caosity.org/mailman/listinfo/centos
On Thu, Jan 27, 2005 at 11:00:48AM +0100, xspace wrote:
Am Donnerstag, den 27.01.2005, 09:56 +0000 schrieb first last: read this http://www.centos.org/modules/smartfaq/faq.php?faqid=19
This is not enough. There is rpmdb-whitebox and some other packages you have to replace to get fully working system.
rpm -qa | grep 'WB|whitebox'
Replace all packagec from the output above with appropriate packages from Centos. Sometimes this could be a package with -centos instead of -whitebox. In this case you have to remove old and install new by hand (you may use rpm -e --nodeps and then rpm -Uvh to replace package with different name).
In case you have WB only in release number, rpm -Uvh --force package should be sufficient.
I have a home computer that I use to develop on, which it is running Whitebox 3.0. I have copied all the required CentOS 3.4 RPMs to /RPM, created a new yum repository and then updated, but when I try to upgrade, it fails on a "recursive dependency on glibc".
Is there any way I can force that dependency?
Would it be easier to upgrade to 4.0 using Anaconda?
Thanks for all the work
Milan Keršláger wrote:
On Thu, Jan 27, 2005 at 11:00:48AM +0100, xspace wrote:
Am Donnerstag, den 27.01.2005, 09:56 +0000 schrieb first last: read this http://www.centos.org/modules/smartfaq/faq.php?faqid=19
This is not enough. There is rpmdb-whitebox and some other packages you have to replace to get fully working system.
The objective was not to rid ones system of WBEL packages or markings it was to make your WBEL system so it could use CentOS repositories. Except for a couple packages that whitebox upgraded that didn't really need to be upgraded. At the time I wrote migration document John Morris had been AWOL on updates for nearly 2 months.
.dn
On Sat, Jan 29, 2005 at 03:35:50PM -0600, donavan nelson wrote:
Milan Keršláger wrote:
On Thu, Jan 27, 2005 at 11:00:48AM +0100, xspace wrote:
Am Donnerstag, den 27.01.2005, 09:56 +0000 schrieb first last: read this http://www.centos.org/modules/smartfaq/faq.php?faqid=19
This is not enough. There is rpmdb-whitebox and some other packages you have to replace to get fully working system.
The objective was not to rid ones system of WBEL packages or markings it was to make your WBEL system so it could use CentOS repositories. Except for a couple packages that whitebox upgraded that didn't really need to be upgraded. At the time I wrote migration document John Morris had been AWOL on updates for nearly 2 months.
The system will be not fully working. Various errors may occur when using mixed packages.
The objective was not to rid ones system of WBEL packages or markings it was to make your WBEL system so it could use CentOS repositories. Except for a couple packages that whitebox upgraded that didn't really need to be upgraded. At the time I wrote migration document John Morris had been AWOL on updates for nearly 2 months.
The system will be not fully working. Various errors may occur when using mixed packages.
As the instructions are written your system will continue to function properly, however, up2date will still use WBEL repos while yum will use CentOS repos.
Mixing packages among EL3 real or clone isn't really a big problem I have machines that started out as RHEL 3 ES --> WhiteBox --> CentOS 3.1 --> CentOS 3.3 --> CentOS 3.4. That machine reported RH, WB, and c0 packages before it get whipped out to test Fresh 3.4 installs.
.dn
On Sun, Jan 30, 2005 at 02:05:53PM -0600, donavan nelson wrote:
The objective was not to rid ones system of WBEL packages or markings it was to make your WBEL system so it could use CentOS repositories. Except for a couple packages that whitebox upgraded that didn't really need to be upgraded. At the time I wrote migration document John Morris had been AWOL on updates for nearly 2 months.
The system will be not fully working. Various errors may occur when using mixed packages.
As the instructions are written your system will continue to function properly, however, up2date will still use WBEL repos while yum will use CentOS repos.
Mixing packages among EL3 real or clone isn't really a big problem I have machines that started out as RHEL 3 ES --> WhiteBox --> CentOS 3.1 --> CentOS 3.3 --> CentOS 3.4. That machine reported RH, WB, and c0 packages before it get whipped out to test Fresh 3.4 installs.
Advices based on rpmdb will not work. Initscripts will produce erron on startup. There could be troubles with logos etc.
I bet you are able to fix your page and do not stuck on wrong advices.
-
donavan nelson -
first last -
Milan Keršláger -
xspace