Gentoo Archives: gentoo-dev

From: "Robert C. Dowdy" <pantropik@×××××××.net>
To: gentoo-dev@g.o
Subject: [gentoo-dev] Re: blackdown-jdk emerge error (bad digest)
Date: Thu, 29 Aug 2002 06:42:47
Message-Id: 1030625045.3199.20.camel@pegasi.robsnet.org
1 >
2 > Message: 12
3 > Date: Thu, 29 Aug 2002 10:58:12 +0200
4 > From: Henti Smith <bain@××××××.org>
5 > To: gentoo-dev@g.o
6 > Subject: [gentoo-dev] The digest /usr/portage/dev-java/blackdown-jdk/files/digest-blackdown-jdk-1.3.1-r7 appears to be corrupt
7 >
8 > When trying to emerge openoffice
9 >
10 > >>> emerge dev-java/blackdown-jdk-1.3.1-r7 to /
11 > !!! The digest /usr/portage/dev-java/blackdown-jdk/files/digest-blackdown-jdk-1.3.1-r7 appears to be corrupt. Aborting.
12 > !!! emerge aborting on /usr/portage/dev-java/blackdown-jdk/blackdown-jdk-1.3.1-r7.ebuild .
13 >
14 > I have deleted the files and rerun emerge rsync made no difference ..
15 >
16 > Henti Smith
17 >
18 I also had this problem, but it's actually pretty simple to solve. :)
19
20 What is happening is, after you delete the files and then emerge rsync
21 again, all you're really doing is deleting the files and then replacing
22 them with another copy of what you just deleted, which, of course you'd
23 have to delete again and then emerge rsync and ... sorry. Anyway,
24 delete:
25
26 /usr/portage/dev-java/blackdown-jdk/files/digest-blackdown-jdk-1.3.1-r7
27
28 Which is where the problem lies. Now do NOT emerge rsync again until
29 after the JDK is installed. Next:
30
31 cd /usr/portage/dev-java/blackdown-jdk
32 ebuild blackdown-jdk-1.3.1-r7.ebuild digest
33
34 This tells portage to create a whole new digest, at which point it will
35 connect to the net, download the tarball, and write out a new digest.
36 Then just "emerge blackdown-jdk" and you should be set (since the JDK
37 sources are already on your system, with the new digest tailored for
38 them).

Replies

Subject Author
Re: [gentoo-dev] Re: blackdown-jdk emerge error (bad digest) Henti Smith <bain@××××××.org>