Updating YDL 3.0

Lewis Coleman Coleman at tscnet.com
Wed Feb 9 08:10:12 MST 2005


I got one of those errors, too.  Mine was for php-domxml, however.  (I 
knew something was funny when rpm said that it was there, but couldn't 
be removed because it WASN'T there!)  I believe it happened when my 
computer crashed in the middle of a yum transaction.  I think I fixed 
it by rebooting (thereby running fsck?) and running rpm --rebuilddb.  
With glibc, however, rebooting may be fatal.  Anyone else?  Running the 
"yum" method of upgrading from 3.0 to 4.0 is not the greatest.  I 
finally was able to use anaconda on my 4.0 install disc to upgrade my 
"Old World" powerbook 3400--I was able to reformat and start on a clean 
disc.
            Lewis Coleman

On Wednesday, February 9, 2005, at 12:02  AM, Arnór Kristjánsson wrote:

> I tried this. When installing glibc I get:
>
> <I cut a a LOT of lines like this out for brevity>
> rpmdb: fatal region error detected; run recovery
> error: db4 error(-30982) from db->close: DB_RUNRECOVERY: Fatal error, 
> run database recovery
> rpmdb: fatal region error detected; run recovery
> error: db4 error(-30982) from db->close: DB_RUNRECOVERY: Fatal error, 
> run database recovery
> rpmdb: fatal region error detected; run recovery
> error: db4 error(-30982) from dbenv->close: DB_RUNRECOVERY: Fatal 
> error, run database recovery
> Installed:  glibc 1:2.3.1-51a.ppc
> Dep Installed:  glibc-common 1:2.3.1-51a.ppc
> Transaction(s) Complete
> [root at xa root]# rpm -qa | grep ^glibc
> glibc-kernheaders-2.4-8.24
> [root at xa root]#
>
> How do I run database recovery?
>
>
>
>
> On 8.2.2005, at 21:42, mascarasnake wrote:
>
>> Hey A. -
>>
>> Arnór Kristjánsson wrote:
>>> Hi,
>>> Once upon a time I installed YDL 3.0 on an aging B/W G3. The machine 
>>> has been running happily for a few years running http, ftp and one 
>>> custom app.
>>> I was under the impression that I could update the system with yum 
>>> or apt, but somehow that doesn't work.
>>> My yum.conf file looks like its the default one, but somehow there 
>>> are no actions taken, even after years of no updates....I'm getting 
>>> pretty scared that the ftp server is "leaking".
>>> Is this normal?  Can I update to 3.0.1 via yum/apt?
>>> A.
>>
>> You should be able to update to 3.0.1 by adding:
>> 	[updates301]
>> 	name=Yellow Dog Linux 3.0.1 updates
>> 	baseurl=ftp://ftp.oregonstate.edu/pub/ydl/yum/3.0.1/update/
>> to your 'yum.conf' file (or use a comparable mirror). Then run:
>> 	yum update
>> and it should update all. After you've done the update, you can 
>> delete or comment out that suppository, as it only contains the 
>> kernel/mol/X updates.
>>
>> cheers, g'luck and all that stuff
>>
>> -- 
>>     It's what you make it man
>>     Takes time
>>     A little bit
>>     A little bit more
>>
>>             -The Minutemen
>>
>> dontdrill at earthlink.net
>> _______________________________________________
>> yellowdog-general mailing list
>> yellowdog-general at lists.terrasoftsolutions.com
>> http://lists.terrasoftsolutions.com/mailman/listinfo/yellowdog-general
>> HINT: to Google archives, try  '<keywords> 
>> site:terrasoftsolutions.com'
>
> _______________________________________________
> yellowdog-general mailing list
> yellowdog-general at lists.terrasoftsolutions.com
> http://lists.terrasoftsolutions.com/mailman/listinfo/yellowdog-general
> HINT: to Google archives, try  '<keywords> site:terrasoftsolutions.com'
>



More information about the yellowdog-general mailing list