similar to: Missing Dependency problem while upgraing a pure (?) whitebox 4 install to Centos 4.2

Here is the output from yum -y upgrade without the error parts... Its odd because it updated all of these first time round. I have dared reboot the box yet, for fear it won't come back up... Setting up Upgrade Process Setting up Repos Reading repository metadata in from local files Resolving Dependencies --> Populating transaction set with selected packages. Please wait. --->

Hello *, i get following error: Downloading needed headers Resolving dependencies .....Unable to satisfy dependencies Package rpm-libs needs rpm = 4.2.3-13.WB2, this is not available. I switch from WhiteBox to Centos. How can resolve this problem?

CentOS Errata and Security Advisory 2005:xxx This is 'rest of the U1 level updates'. Notable still missing anaconda, but everything else should be there now. The file list below does contain some previously updated files as it's the list of _all_ updated files. The following updated files have been uploaded and are currently syncing to the mirrors: files:

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

Hello several months ago I install WhiteBox Linux on several severs, I was happy, not woriing about upgrading every 1,5 year as when I use RH 4.0, 6.0, 7.3, 9.0 .... And then WhiteBox went black, WBEL updates release slowed down and maintainer wont help form anybody. Just telling "If you want quick updates, build it yourself.". I prefer wasting time for customizations and/or

Hi Is it possible to swap the yum.conf from my centos box onto my whitebox box and have the whitebox machine use centos updates through yum? CentOS seems further ahead and far quicker at roll outs than whitebox? thanks

I've been following the faq for moving from whitebox to centos (which admittedly is for release 3, but using the equivalent release 4 files) and keep getting stuck when installing the centos-release-4-2.1 rpm which says it should replace whitebox-release4.2 However this is not happening, giving me the following rpm -Uvh

Hello all I migrated my Centos installation from a whitebox install few months ago. Only one minor issue...on booting up X, the login screen shows whitebox logos. At that time, I did not tackle it because I assumed that it will automatically be upgraded with yum...and again it was not essential to running the OS. What whitebox rpms do I need to substitute with centos ones to correct this

Error: mount.ocfs2: Transport endpoint is not connected while mounting /dev/sdc1 on /u02, could not mount /dev/sdc1. The installation step is: 1. install all rpms on int-rac1, int-rac2 2. interconnect int-rac1, int-rac2, ping each other using private ip and public ip ok. Add EMC SAN as shared disk and visable for two nodes. 3. configure int-rac1 using ocfs2console, add two nodes 4. according

Hi all Can you tell me what is the different between fedora / redhat enterprise / centos and whitebox? Thank you ____________________________________________________________________________________ 8:00? 8:25? 8:40? Find a flick in no time with the Yahoo! Search movie showtime shortcut. http://tools.search.yahoo.com/shortcuts/#news

Hello I am leaving Whitebox because of lack of up to date sec. updates. Did any body try to "upgrade" WBEL to CentOS? Any dificulty or problems? Thanks Petr Klima

Good evening everyone, I am used to using R under Windows, but have done an install of 1.9.1 under WhiteBox linux 3 (based on RHEL 3). This all went without a hitch, along with most of the additional package installs. However, while trying to install car and rgl I hit a problem regarding the X environment not being found. As I was doing the install from a console *within* the X environment,

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

Japanese input - the final frontier. This is the last obstacle before I can work completely within Centos and be free of Windows. But it's still not working. To cut to the chase, in my quest to get Japanese working, I came across the following: https://www.redhat.com/archives/fedora-i18n-list/2004-November/msg00030.html ... where someone says: "You need to have httx (htt_xbe) running

Greetings, This is a new install on CentOs 4.1 dvd from a couple weeks ago. The initial yum updates worked fine but now There are about 15 things that get dependency errors and yum will not install the updates. Rebuild the RPM database, removed /var/cache/yum/* , yum update yum for the latest version and the errors still exist. When you query the rpm database the dependency are installed. Here

On 18/09/2019 12:34, Roy Eastwood via samba wrote: > I used the DC rejoin method as described in the WiKi to upgrade one of my DCs to version 4.11.0. Following the steps, when I came > to rejoin the domain, it initially failed, complaining that the DC already existed, but to force the rejoin, remove the files: > secrets.ldb and secrets.tdb. I assume you don't demote the DC before

On 18/09/2019 13:10, Rowland penny via samba wrote: > On 18/09/2019 12:34, Roy Eastwood via samba wrote: > > I used the DC rejoin method as described in the WiKi to upgrade one of my DCs to version 4.11.0. Following the steps, when I came > > to rejoin the domain, it initially failed, complaining that the DC already existed, but to force the rejoin, remove the files: > >

I used the DC rejoin method as described in the WiKi to upgrade one of my DCs to version 4.11.0. Following the steps, when I came to rejoin the domain, it initially failed, complaining that the DC already existed, but to force the rejoin, remove the files: secrets.ldb and secrets.tdb. I assume you don't demote the DC before the upgrade, as there's no mention of this? Anyway, I

Hi, I was doing updates on a server and I think that the network connection got reset. So I guess the yum update didn't complete and I now get this when I run 'yum update': ======================= Setting up Update Process Setting up repositories Reading repository metadata in from local files Resolving Dependencies --> Populating transaction set with selected packages. Please

Well, I'm a recent convert from WBEL. My biggest concern with CentOS is that the community here seems to want to be more than a recompile of RHEL. But WBEL is floundering, what with Katrina and Rita, and there really being only 1 developer behind it, etc. I offer an automated shell script to switch from WBEL4 to CentOS4 (easy, it's hosted on my home DSL line!) It assumes that