Re: [gentoo-user] pam-1.1.4 emerge error on x86

[Jonas de Buhr <jonas.de.buhr@gmx.net>]

Am Sat, 15 Oct 2011 18:17:41 +0100
schrieb Mick <michaelkintzios@gmail.com>:

> On Saturday 15 Oct 2011 14:09:46 Jonas de Buhr wrote:
> > Am Sat, 15 Oct 2011 13:24:02 +0100
> > 
> > schrieb Mick <michaelkintzios@gmail.com>:
> > > On Saturday 15 Oct 2011 00:20:14 Jonas de Buhr wrote:
> > > > Am Sat, 15 Oct 2011 00:01:04 +0100
> > > > 
> > > > schrieb Mick <michaelkintzios@gmail.com>:
> > > > > Have you seen this before?
> > > > > 
> > > > > `/var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4'
> > > > > make[1]: Leaving directory
> > > > > `/var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4'
> > > > > /var/tmp/portage/sys-libs/pam-1.1.4/temp/environment: line
> > > > > 2226: scanelf: command not found
> > > > 
> > > > you could try reinstalling app-misc/pax-utils.
> > > > 
> > > > this is either a missing dependency or for some reason your
> > > > pax-utils install is broken.
> > > 
> > > Thank you!  I've remerged pax-utils.  This is an old laptop and
> > > both the main battery and CMOS battery have run out of juice.  I
> > > noticed that the clock was out by more than 100 years - but I
> > > think that I had sync'ed portage in the meanwhile.
> > > 
> > > I have not been able to proceed with pam, because world now wants
> > > to
> > > 
> > > emerge ruby.  However, it comes up with this error:
> > > >>> Verifying ebuild manifests
> > > 
> > > !!! Digest verification failed:
> > > !!! /usr/portage/dev-lang/ruby/ruby-1.8.7_p352.ebuild
> > > !!! Reason: Filesize does not match recorded size
> > > !!! Got: 5574
> > > !!! Expected: 5569
> > > 
> > > I've deleted the ebuild, then resync'ed twice with different
> > > mirrors and the error persists.  Another box I have (which does
> > > not come up with this error) shows:
> > > 
> > > $ ls -la /usr/portage/dev-lang/ruby/ruby-1.8.7_p352.ebuild
> > > -rw-r--r-- 1 root root 5574 Oct 14 09:31 /usr/portage/dev-
> > > lang/ruby/ruby-1.8.7_p352.ebuild
> > > 
> > > So, is 5574 the wrong size, or is the ebuild file in the latest
> > > sync'ing of portage wrong?
> > 
> > did you delete just the ebuild or the Manifest too? i suspect that
> > due to wrong date setting portage did not update the Manifest file
> > which contains the filesize.
> > 
> > rm -rf /usr/portage/dev-lang/ruby && emerge --sync
> > 
> > should help in that case. but you might run into more date related
> > update problems later. maybe you should correct your date and
> > extract a portage snapshot and sync to get rid of those problems
> > once and for all.
> > 
> > my
> > /usr/portage/dev-lang/ruby/Manifest
> > says
> > 
> > EBUILD ruby-1.8.7_p352.ebuild 5574 RMD160
> > e822545306c9e2b2a17767895b851f72c772a149 SHA1
> > 0117f543aa6d7ae064af74af7199deefe6e0dc9d SHA256
> > 79d0f2b28b0b39bf23b9208071f7d50f04a6d76254f42073b2b3e9cc612955a7
> > 
> > so 5574 should be the correct filesize. what does
> > 
> > grep ruby-1.8.7_p352 /usr/portage/dev-lang/ruby/Manifest
> > 
> > say?
> > 
> > if resyncing absolutely does not work, you can compare the SHA256 of
> > the ebuild on your two computers and if they are the same it should
> > be relatively safe to do
> > 
> > ebuild /usr/portage/dev-lang/ruby/ruby-1.8.7_p352.ebuild manifest
> > 
> > which will rebuild the Manifest file containing the filesize and the
> > checksums and after that you can emerge.
> 
> I removed the manifest resync'ed and it emerged without any errors.
> 
> Thank you!  :-)

you're welcome ;)
its really easy to help you because you provide the right information =)