Bug 266246

Summary:	Emerge complains about the digests of pexports from kde-windows sourceforge repository
Product:	[Unmaintained] kde-windows	Reporter:	jm.ouwerkerk
Component:	other	Assignee:	KDE-Windows <kde-windows>
Status:	RESOLVED FIXED
Severity:	normal
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Compiled Sources
OS:	Microsoft Windows
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description jm.ouwerkerk 2011-02-14 00:34:05 UTC

Version:           unspecified (using Devel) 
OS:                MS Windows

Trying to follow instructions poited out in here http://techbase.kde.org/Getting_Started/Build/KDE4/Windows/emerge but I'm rather stuck with a bad digest checksum computed for package pexports-x64-0.44-bin.tar.bz2. 
Emerge tries to download it from:
http://kent.dl.sourceforge.net/project/kde-windows/pexports/pexports-x64-0.44-bin.tar.bz2
Then when it compares digest hashes it throws an error because: 
The digest specified in emerge\portage\pexports\pexports-0.44.py: 
bbc02ca7b5475bc5274126bd72a08952ec1734fc
Does not match the one computed for the downloaded file:
dd9497260e89c25e51f120de41949a09f08ee54f

I'm using emerge SVN revision: 1219996

Reproducible: Always

Steps to Reproduce:
Set up a clean KDE root
Checkout emerge from SVN repository into emerge subdir
Configure merge to build x64 packages with the MingW compiler from anonsvn.kde.org
emerge qt from commandline where Sourceforge will assign you the kent.dl.sourceforge.net mirror.
wait a bit... 



kde-settings.bat (things I've changes from the defaults):

KDEROOT=D:\KDE
EMERGE_ARCHITECTURE=x64
PYTHONPATH=C:\Python27

Comment 1 jm.ouwerkerk 2011-02-15 05:24:41 UTC

It's the same story when different Sourceforge mirrors are used:
Both:
ignum.dl.sourceforge.net
mesh.dl.sourceforge.net

Download a package with the same invalid digest.

Comment 2 jm.ouwerkerk 2011-02-15 05:34:49 UTC

And it's the same story with:
surfnet.dl.sourceforge.net 
netcologne.dl.sourceforge.net
puzzle.dl.sourceforge.net

Comment 3 jm.ouwerkerk 2011-02-15 08:30:16 UTC

I gave up on the 64bit KDE for now since the Qt build ends up looking for missing 32bit components anyway. 

Instead I tried building an x86 Qt from a clean KDEROOT and then the hash is valid. Apparently, either I misconfigured something (but what???) and this bug report is bogus; or the emerge tool doesn't distinguish between the x86 and x64 flavours of pexports.

I'd guess the former.

Comment 4 Patrick Spendrin 2012-02-22 22:49:49 UTC

at least the pexports problem should have been fixed now.