similar to: yum $releasever thinks it's 1 instead of 3

Never mind. I updated with the centos-release rpm and that seemed to fix it. Thanks for any who may have offered already. Original below: I just upgraded one of my Tao boxes to Centos 3. The usual procedure is to do a yum update twice, and all is fine. This time, I had to rebuilddb before I could run the second yum update, and once I started this, yum fails. It says that $releasever is

Sorry for the extra info required, but I had digest mode turned on and wouldn't have received the mailing till tomorrow. I have since updated the data manually, but after 'yum update tzdata' was run, the zdump -v for EST5EDT and America/New_York all still showed a date of April 1, instead of March 11. After manually fixing, it is correct. This was mostly a question about why yum

Hi, I have an old server that originally was a RedHat 8 server. Then I upgraded to RedHat 9, then Tao Linux 1 and last to CentOS 3 when tao was discontinued. Yes I know that this was probably not the smartest thing in the world but now this is the case and I don't want to reinstall it. Now the question. In yum.conf I have distroverpkg=redhat-release and cat /etc/redhat-release gives: CentOS

I installed CentOS 3.4 from a CD image I'd burned a while ago, and then attempted to update with yum to 3.7. All the packages installed OK, but at the very end of final cleanup I got an error message from db4 saying to "RUN RECOVERY". I did "rpm --rebuilddb" which may have been the wrong thing -- it issued an error about "pages missing". I then ran it again,

Mr. Parsley, the main man at the Tao Linux group, has announced that he will no longer be able to do his thing for Tao Linux. Just recently, I had decided to investigate CentOS 4 before his announcement, and liked a lot of what I saw. Due to the Tao announcement, I have decided that CentOS will "have" to be the OS for my company in the future. Hence, my new membership to this list.

I tested moving a box from Tao 1.0 to CentOS 3.7. All went well, as far as I can tell, with the OS upgrades, but I needed to rpm -ivh --force the desktop-* stuff. This was a minor thing to fix for no real purpose other than to just be doing it. I still get, though, the Tao screens when the graphic login screen appears. I have changed the Application->Settings->Login Screen->

Has anyone seen this before? [root at shelob rpm]# yum update rpmdb: Program version 4.2 doesn't match environment version error: db4 error(22) from dbenv->open: Invalid argument error: cannot open Packages index using db3 - Invalid argument (22) error: cannot open Packages database in /var/lib/rpm Traceback (most recent call last): File "/usr/bin/yum", line 30, in ?

I'm sure these sound like stupid questions, or have really simple answers, so sorry. The really bad thing is I originally sent these to samba-bounces. Oops. Once we get this Samba AD thing installed, we'd like to have users login and mount particular shares to drive letters based on their group, not their user. All I've read about this seems to use "user" scripts (along

I still haven't installed Samba, as I'm still in the planning stages. Again, I'm new to Samba, and I discover our Windows pro isn't quite up on the newer stuff since it's been years since he ran domains. I'm a little confused about this thing called "SysVol". Reading up on it, it appears a real important part of an AD, but I don't see how or when it's

When I started considering Samba, the main objective was to have a way for our users to log into something and map the shares they required based on their group (departmental) needs. As I asked more questions, most recommended AD as this would allow the administrator to manage these users. Now that I find I'll probably need VMs to handle the AD/DC and the shares because I only have two

I have performed the 5.1 update via the 5 repo on a couple of systems. I then went to switch these systems to my new local repo using ther $releasever variable. It still has the value of 5, not 5.1 Where is this set? Why was it not changed to 5.1? On the one clean install from the 5.1 isos, $releasever is at 5.1 I think.

After installing clean Centos 5.3 and updating with "yum update" yum starts to fail. I get the following error message YumRepo Error: All mirror URLs are not using ftp, http[s] or file. Eg. 7 is not a valid release or hasnt been released yet/ removing mirrorlist with no valid mirrors: //var/cache/yum/base/mirrorlist.txt It looks like the $releasever variable has value 7. Why does

I should change this to OT, as it's not really CentOS related. I had a post on the list last week asking how the rpmforge rpm was to be implemented in yum. Craig White was kind enough to list how his yum.conf is appended, I assume after he installed the rpm. Unfortunately, mine is not appended with these lines. I am running CentOS 3. I will add these lines manually, and probably remove

I've got a couple of Samba4 DCs running as VMs for testing. The primary AD DC went smoothly. The second VM joined properly and all but it's only when I get to the replication tests that I see errors. This is following the wiki When I run the command "samba-tool drs kcc -Uadministrator windowsdc.mycrap.cnpapers.dom" I get an error indicating that

Hi! I'm trying to upgrade my Redhat 3AS server, but I'm encountering problems. The first problem was, I didn't know what repository to use. I settled on http://mirror.centos.org/, but using it is strange, as not all mirror servers have all of the directories, and so sometimes links appear broken, but the problem goes away if I hit reload. A number of them have empty directories,

I'm still not seeing emails from the list. With help from others, I thought I had the IPs cleared since the change back in February, but apparently not. Can someone PM me and let me know what outgoing IP addresses the list is using please? steve campbell

Over the weekend my workstation (still on CentOS 3) started showing SMART errors, so we shut it down and moved everything onto a new drive. On reboot, the RPM database reports as corrupted and "rpm --rebuilddb" segmentation faults. Is there any reasonable way to recover from this, short of a complete reinstall? The machine is otherwise up though it''s quite likely some files

I usually use a "Desktop" option when installing a new machine. This gives me all I need for an X session and then I add other packages or grouplists on an as-needed basis. I'm putting together a couple of machines that will not have network connectivity until all packages are installed. Is there a way to run yum to install packages/groups from the installation disk instead of

I'd guess this is probably something pretty specific to my test box, but when I yum updated to 3.3 my rpmdb got totally hosed. Unfortunately, I didn't save the error that occured at the time because a rpm --rebuilddb _appeared_ to fix the problem. Unfortunately I found out later that I was left with a db that only contained a subset of the actual install base. I'm now trying to

I am in the process of updating a dozen or so workstations from CentOS 4.3 to CentOS 4.4. I set up a local YUM repository, and have been able to successfully update all systems except for one. Both yum and rpm either hang or core dump on this system. I've done a "yum clean all" and an "rpm --rebuilddb" (after deleting the __db files). I was able to