David H. wrote:
[]
The check fails explaining that the checksum is wrong. The Info file reads:

Source-MD5: b1468d49c1357aebcd1de6ef12cbf3e8
Source-Checksum: SHA1(b236923e7d4909c6fd8873ac87431833fa45069b)

So, I wonder how to best debug this? :)

The fink engine gurus have remained stubbornly silent about this since I reported it 3 weeks ago.

I think the Source-Checksum stuff is just not yet completely implemented, and every package (i.e. all three of them) that uses SHA1 shows the same breakage. When you download the source for the first time, it says the checksum is wrong, because it compares the MD5 sum with the SHA1 sum and finds they are different. Afterwards it compares SHA1 with SHA! and is happy.

A workaround (but certainly not a complete fix) is to change NetAccess.pm as follows:

--- NetAccess.pm_ori    2006-01-18 20:47:28.000000000 +0100
+++ NetAccess.pm        2006-04-15 21:15:33.000000000 +0200
@@ -270,1 +270,1 @@
- if (defined $checksum and (not Fink::Checksum->validate($file, $checksum))) { + if (defined $checksum and (not Fink::Checksum->validate($file, $checksum, $checksum_type))) {

--
Martin



-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fink-devel

Reply via email to