On 2011-01-05 03:06 , Ryan Schmidt wrote: > The problem here was I think that you were using a > BitBucket-generated distfile, and they did not keep the distfile > around anywhere; they re-generated it later, after you had already > recorded its checksums into the portfile. I recall there was at least > one other DVCS site that was doing something similar, which made it > unsuitable for use as a MacPorts master_sites location.
Yes, the same problem appeared with github in the past for the MacVim port. The issue was that the tar format contains the access times of the files which changes as soon as you generate the tarball. Therefore the result will be different each time you download this as each download triggered creation of a new tarball. As an alternative I am now using zip files as they do not contain access times. Recently someone reported that the original problem with tar was gone. Actually, I got the same checksum for multiple tries now. But I am not sure if they just cache the file for a limited time period, so I am sticking with zip format for now. Rainer _______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
