From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1RF7sp-0004G7-Fx for garchives@archives.gentoo.org; Sat, 15 Oct 2011 17:18:51 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 9EEB221C203; Sat, 15 Oct 2011 17:18:36 +0000 (UTC) Received: from mail-ww0-f53.google.com (mail-ww0-f53.google.com [74.125.82.53]) by pigeon.gentoo.org (Postfix) with ESMTP id 16B8C21C0EA for ; Sat, 15 Oct 2011 17:17:45 +0000 (UTC) Received: by wwg14 with SMTP id 14so4313364wwg.10 for ; Sat, 15 Oct 2011 10:17:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=from:reply-to:to:subject:date:user-agent:references:in-reply-to :mime-version:content-type:content-transfer-encoding:message-id; bh=IVuxT8eFhJQUJ62IlsSDxSslwypYIk9Z7kMIMIJ3BzA=; b=SRB6E85KvQbS9kAtcGy143iVMzgi/O5z61TUqNsYCyUSo4v1EQ1eZiUg0v6Jz66ROv qBQDL0672OndaH/rzxan/gLigUuL0UGn0MDFHajg4xnhJ78l76WPQYMwxE5BljEsoGQV 3mUc6CybD//TMvNX8ultI1S2kMXHKmeKZWoXw= Received: by 10.227.24.8 with SMTP id t8mr4384109wbb.72.1318699065243; Sat, 15 Oct 2011 10:17:45 -0700 (PDT) Received: from dell_xps.localnet (230.3.169.217.in-addr.arpa. [217.169.3.230]) by mx.google.com with ESMTPS id l40sm20914737wbm.10.2011.10.15.10.17.44 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 15 Oct 2011 10:17:44 -0700 (PDT) From: Mick To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] pam-1.1.4 emerge error on x86 Date: Sat, 15 Oct 2011 18:17:41 +0100 User-Agent: KMail/1.13.7 (Linux/2.6.39-gentoo-r3; KDE/4.6.5; x86_64; ; ) References: <201110151324.21338.michaelkintzios@gmail.com> <20111015150946.5a0a20f9@toxic.dbnet> In-Reply-To: <20111015150946.5a0a20f9@toxic.dbnet> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart25871900.RTNMN0N4nN"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <201110151817.51438.michaelkintzios@gmail.com> X-Archives-Salt: X-Archives-Hash: 0cf31a151ddc3e55ce0902e187bc048b --nextPart25871900.RTNMN0N4nN Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On Saturday 15 Oct 2011 14:09:46 Jonas de Buhr wrote: > Am Sat, 15 Oct 2011 13:24:02 +0100 >=20 > schrieb Mick : > > On Saturday 15 Oct 2011 00:20:14 Jonas de Buhr wrote: > > > Am Sat, 15 Oct 2011 00:01:04 +0100 > > >=20 > > > schrieb Mick : > > > > Have you seen this before? > > > >=20 > > > > `/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 > > >=20 > > > you could try reinstalling app-misc/pax-utils. > > >=20 > > > this is either a missing dependency or for some reason your > > > pax-utils install is broken. > >=20 > > 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. > >=20 > > I have not been able to proceed with pam, because world now wants to > >=20 > > emerge ruby. However, it comes up with this error: > > >>> Verifying ebuild manifests > >=20 > > !!! 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 > >=20 > > 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: > >=20 > > $ 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 > >=20 > > So, is 5574 the wrong size, or is the ebuild file in the latest > > sync'ing of portage wrong? >=20 > 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. >=20 > rm -rf /usr/portage/dev-lang/ruby && emerge --sync >=20 > 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. >=20 > my > /usr/portage/dev-lang/ruby/Manifest > says >=20 > EBUILD ruby-1.8.7_p352.ebuild 5574 RMD160 > e822545306c9e2b2a17767895b851f72c772a149 SHA1 > 0117f543aa6d7ae064af74af7199deefe6e0dc9d SHA256 > 79d0f2b28b0b39bf23b9208071f7d50f04a6d76254f42073b2b3e9cc612955a7 >=20 > so 5574 should be the correct filesize. what does >=20 > grep ruby-1.8.7_p352 /usr/portage/dev-lang/ruby/Manifest >=20 > say? >=20 > 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 >=20 > ebuild /usr/portage/dev-lang/ruby/ruby-1.8.7_p352.ebuild manifest >=20 > 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! :-) =2D-=20 Regards, Mick --nextPart25871900.RTNMN0N4nN Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (GNU/Linux) iEYEABECAAYFAk6ZwD8ACgkQVTDTR3kpaLYUyQCeJ0coqw+NY/Xyo9KH3uCLf9lO TC0Amwa/qNfPjGQh8Av3S/TCs09AK+RO =o8V6 -----END PGP SIGNATURE----- --nextPart25871900.RTNMN0N4nN--