| 1 |
Am Sat, 15 Oct 2011 13:24:02 +0100 |
| 2 |
schrieb Mick <michaelkintzios@×××××.com>: |
| 3 |
|
| 4 |
> On Saturday 15 Oct 2011 00:20:14 Jonas de Buhr wrote: |
| 5 |
> > Am Sat, 15 Oct 2011 00:01:04 +0100 |
| 6 |
> > |
| 7 |
> > schrieb Mick <michaelkintzios@×××××.com>: |
| 8 |
> > > Have you seen this before? |
| 9 |
> |
| 10 |
> > > `/var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4' |
| 11 |
> > > make[1]: Leaving directory |
| 12 |
> > > `/var/tmp/portage/sys-libs/pam-1.1.4/work/Linux-PAM-1.1.4' |
| 13 |
> > > /var/tmp/portage/sys-libs/pam-1.1.4/temp/environment: line 2226: |
| 14 |
> > > scanelf: command not found |
| 15 |
> > |
| 16 |
> > you could try reinstalling app-misc/pax-utils. |
| 17 |
> > |
| 18 |
> > this is either a missing dependency or for some reason your |
| 19 |
> > pax-utils install is broken. |
| 20 |
> |
| 21 |
> Thank you! I've remerged pax-utils. This is an old laptop and both |
| 22 |
> the main battery and CMOS battery have run out of juice. I noticed |
| 23 |
> that the clock was out by more than 100 years - but I think that I |
| 24 |
> had sync'ed portage in the meanwhile. |
| 25 |
> |
| 26 |
> I have not been able to proceed with pam, because world now wants to |
| 27 |
> emerge ruby. However, it comes up with this error: |
| 28 |
> |
| 29 |
> >>> Verifying ebuild manifests |
| 30 |
> |
| 31 |
> !!! Digest verification failed: |
| 32 |
> !!! /usr/portage/dev-lang/ruby/ruby-1.8.7_p352.ebuild |
| 33 |
> !!! Reason: Filesize does not match recorded size |
| 34 |
> !!! Got: 5574 |
| 35 |
> !!! Expected: 5569 |
| 36 |
> |
| 37 |
> I've deleted the ebuild, then resync'ed twice with different mirrors |
| 38 |
> and the error persists. Another box I have (which does not come up |
| 39 |
> with this error) shows: |
| 40 |
> |
| 41 |
> $ ls -la /usr/portage/dev-lang/ruby/ruby-1.8.7_p352.ebuild |
| 42 |
> -rw-r--r-- 1 root root 5574 Oct 14 09:31 /usr/portage/dev- |
| 43 |
> lang/ruby/ruby-1.8.7_p352.ebuild |
| 44 |
> |
| 45 |
> So, is 5574 the wrong size, or is the ebuild file in the latest |
| 46 |
> sync'ing of portage wrong? |
| 47 |
|
| 48 |
did you delete just the ebuild or the Manifest too? i suspect that due |
| 49 |
to wrong date setting portage did not update the Manifest file which |
| 50 |
contains the filesize. |
| 51 |
|
| 52 |
rm -rf /usr/portage/dev-lang/ruby && emerge --sync |
| 53 |
|
| 54 |
should help in that case. but you might run into more date related |
| 55 |
update problems later. maybe you should correct your date and extract a |
| 56 |
portage snapshot and sync to get rid of those problems once and for all. |
| 57 |
|
| 58 |
my |
| 59 |
/usr/portage/dev-lang/ruby/Manifest |
| 60 |
says |
| 61 |
|
| 62 |
EBUILD ruby-1.8.7_p352.ebuild 5574 RMD160 |
| 63 |
e822545306c9e2b2a17767895b851f72c772a149 SHA1 |
| 64 |
0117f543aa6d7ae064af74af7199deefe6e0dc9d SHA256 |
| 65 |
79d0f2b28b0b39bf23b9208071f7d50f04a6d76254f42073b2b3e9cc612955a7 |
| 66 |
|
| 67 |
so 5574 should be the correct filesize. what does |
| 68 |
|
| 69 |
grep ruby-1.8.7_p352 /usr/portage/dev-lang/ruby/Manifest |
| 70 |
|
| 71 |
say? |
| 72 |
|
| 73 |
if resyncing absolutely does not work, you can compare the SHA256 of |
| 74 |
the ebuild on your two computers and if they are the same it should be |
| 75 |
relatively safe to do |
| 76 |
|
| 77 |
ebuild /usr/portage/dev-lang/ruby/ruby-1.8.7_p352.ebuild manifest |
| 78 |
|
| 79 |
which will rebuild the Manifest file containing the filesize and the |
| 80 |
checksums and after that you can emerge. |
Archives