Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 112903 - Digest verification failed on ibm-jdk-bin-1.4.2 for amd64
Summary: Digest verification failed on ibm-jdk-bin-1.4.2 for amd64
Status: RESOLVED UPSTREAM
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: AMD64 Linux
: High normal (vote)
Assignee: Java team
URL: http://forums.gentoo.org/viewtopic-p-...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-11-18 05:04 UTC by Paulo
Modified: 2005-11-23 07:02 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Paulo 2005-11-18 05:04:11 UTC
I've tryed syncing portage, redownloading the file (since it's fetch
restricted), but nothing seems to solve the problem. The digest verification
aways fails.

Reproducible: Always
Steps to Reproduce:
1.Just emerge ibm-jdk-bin on an amd64 or ~amd64 system.
Actual Results:  
Portage refuses to install the package, saying the downloaded file's size
doesn't match the recorded one.

Expected Results:  
Should have installed the package.


PHAF paulo # emerge ibm-jdk-bin
Calculating dependencies ...done!
>>> emerge (1 of 1) dev-java/ibm-jdk-bin-1.4.2 to /
>>> md5 files   ;-) ibm-jdk-bin-1.4.2.ebuild
>>> md5 files   ;-) ibm-jdk-bin-1.4.2.03.ebuild
>>> md5 files   ;-) files/digest-ibm-jdk-bin-1.4.2
>>> md5 files   ;-) files/digest-ibm-jdk-bin-1.4.2.03
>>> md5 files   ;-) files/ibm-jdk-bin-1.4.2.03
>>> md5 files   ;-) files/ibm-jdk-bin-1.4.2
>>> md5 files   ;-) files/cpuinfo

!!! Digest verification Failed:
!!!    /usr/portage/distfiles/IBMJava2-SDK-AMD64-142.x86_64.tgz
!!! Reason: Filesize does not match recorded size

PHAF paulo #
Comment 1 Saleem Abdulrasool (RETIRED) gentoo-dev 2005-11-19 11:17:30 UTC
Please use the IBM JDK that is in ~$ARCH since that resolves this issue.  I do
not have an AMD64 machine so I am unable to unmask it from there.  The issue is
caused by upstream not following a sane naming scheme.
Comment 2 Paulo 2005-11-23 06:38:05 UTC
This solves the problem.
Comment 3 Petteri Räty (RETIRED) gentoo-dev 2005-11-23 07:02:13 UTC
Maybe we should ask the amd64 arch team to stabilize the latest 1.4 version?