On Sep 18, 2014, at 4:50 AM, Aljaž Srebrnič wrote: > > On 18/set/2014, at 03:58, Ryan Schmidt wrote: > >> >>> On Sep 17, 2014, at 5:17 AM, [email protected] wrote: >>> >>> Revision >>> 125415 >>> Author >>> [email protected] >>> Date >>> 2014-09-17 03:17:24 -0700 (Wed, 17 Sep 2014) >>> Log Message >>> >>> sysutils/rcm >>> move upstream to github >>> >> >> Checksum mismatch, unsurprisingly: >> […] >> > > Yeah, I figured, but a port clean —all && port checksum didn’t show any > errors. It must have fetched from already cached tarballs.
Yes, this just means github.com is not the closest server to where you are currently located. > Anyway, I updated checksums and applied the “stealth update” procedure in > 125458. > The build now fails: sh: ./configure: No such file or directory >> >> It would be unlikely for a project to have hosted on their own web site a >> tarball that was identical to the automatically-generated tarball provided >> by github. > > Well, could be unlikely, but not so unreasonable: one could just re-use the > generated tarball from github. In this case, they didn't. _______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
