Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-amd64
Navigation:
Lists: gentoo-amd64: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-amd64@g.o
From: Zac Medico <zmedico@...>
Subject: Re: Is 2005 broken?
Date: Fri, 08 Jul 2005 23:44:38 -0700
Tim Ames wrote:
> I'm running it looks like linux-2.6.7-gentoo-r14
> I haven't been able to get online for quite a while now.  When I originally 
> compiled I was on satellite and had a network connection that enabled me to 
> download just about anything I wanted.  I didn't have ppp compiled in the 
> kernel and I kept trying to get wvdial emerged or ppp working in the 
> machine to use a serial modem for dialup as that is all I can afford right 
> now, and probably all I can get in the location I'm living in.
> The problems started trying to emerge wvdial, I downloaded manually off of 
> one of the mirrors and put the files in
> /usr/portage/distfiles and then tried to emerge them on the machine
> I started getting md5 errors trying to emerge the files that I had 
> downloaded and burned to a cd using windows xp.
> I kept trying, deleted the files, put the machine finally online using 
> another machine on dialup and setting internet connection sharing and got 
> the 64bit gentoo machine online that way.  I tried doing and emerge sync 
> several times and still kept coming up with
> this message.
> Digest verification Failed:
> /usr/portage/distfiles/any downloaded .tar.gz file here
> Reason:  failed on MD5 verification
> I kept looking through the forums tried all the suggestions, ie ... 
> changing mirrors, re downloading, rebuilding the digest
> then I downloaded the webrsync file and rewrote the whole portage tree.  I 
> still get the MD5 errors.
> When I go to emerge a file that is in /usr/portage/distfiles  I get this error
> gzip: stdin: not in gzip format
> tar: Child returned status 1
> tar: Error exit delayed from previous errors
> when I try to gunzip the file I get
> !!!ERROR: dev-libs/xplc-0.3.11 failed
> !!!Function unpack, Line 375, Exitcode 2
> !!!failure unpacking   ... yada yada
> I'm at the point where I'm ready to wipe everything out and start over again.
> Can this be fixed??
> thanks in advance
> Tim


> I posted a message in here last week about digest verification failing
> and also in the forums and did not receive a reply.  What is happening
> is that after updating portage when I tried to emerge files and they
> would download and you could see them get larger than the amount that
> was written in the first lookup of the file.  The file would go past 100
> percent and then sometime later it would stop and it would come up with
> a digest verification error.
> 
> So I managed to get the machine online with just a modem after a while
> and the same pattern happened.  So I started out completely from scratch
> and I just compiled 2005.0.  Everything worked out until I tried to
> emerge coldplug from a genkernel.  I got the digest verification error
> again.  I emerge sync ed again and now everthing I try to emerge gets
> the digest verification error.
> 
> I guess I'm going to have to give up and go to another distro.
> 
> I'm running an sk8v asus motherboard with an fx-51 chip.
> 
> Does any of this ring a bell with anyone?
> 
> tia
> 
> Tim
> 
> 

Errors with both md5 and gzip?  Can you use a separate computer to determine if the problem is with md5/gzip programs or corruption of the distfiles themselves?

Zac
-- 
gentoo-amd64@g.o mailing list


Replies:
Re: Is 2005 broken?
-- Tim Ames
References:
Is 2005 broken?
-- Tim Ames
Navigation:
Lists: gentoo-amd64: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Is 2005 broken?
Next by thread:
Re: Is 2005 broken?
Previous by date:
Is 2005 broken?
Next by date:
Re: Is 2005 broken?


Updated Jun 17, 2009

Summary: Archive of the gentoo-amd64 mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.