Daniel Macks wrote:
goatbar committed:
Modified Files:
bitvector-py.info
Log Message:
upstream change to the source dist without a version change
added sha1
fink validate still does not know about Source-SHA1:
The validator from fink-0.24.x doesn't know about any checksum except
the traditional MD5 because that's all fink-0.24.x uses.
The validator from fink CVS HEAD doesn't know about the Source-SHA1
field because there is no such field...either it was an earlier
never-released syntax or it was a wishful-thinking syntax:) You're
probably thinking of the SHA1 token in a Source-Checksum field, in its
current syntax (which could change before it gets into a released fink
version). Using HEAD-only features in a released .info is strictly
at-your-own-risk.
...in particular since the SHA1-recognizing code in HEAD is broken, too.
It doesn't recognize a correct checksum when the source is being
downloaded. It does only recognize it when it has already been
downloaded before. I wrote this to the list about the bison-2.1-1
package some days ago.
--
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
