On Oct 2, 2014, at 4:03 PM, Ryan Schmidt <[email protected]> wrote:
> > On Oct 2, 2014, at 3:28 PM, Juan Manuel Palacios wrote: >> I tried that very ingenious shell loop and found I had three mirrors failing >> the checksum for that patch file, each of them giving different checksums >> even among themselves: >> >> Portfile checksum: 1e05d95e4abd32b631d991fa374d030c1651645d (respected by >> most mirrors). >> >> http://lil.fr.distfiles.macports.org/bash/bash43-028: >> SHA1(bash43-028)= 7e96232c3265571fe4f85d33b83684d525b1b246 >> >> This server is on-and-off closing the connection before transfer is >> complete, so sometimes checksum fails and sometimes it doesn't. But in all >> cases HTTP 200 OK is returned, so it might affect builds. >> >> http://aarnet.au.distfiles.macports.org/pub/macports/mpdistfiles/bash/bash43-028: >> SHA1(bash43-028)= 992fa55af8366819627e5fafa686ed956b24bc4f >> >> This one is indeed returning 404, so it can be ignored. >> >> http://svn.macports.org/repository/macports/distfiles/bash/bash43-028: >> SHA1(bash43-028)= 7d05360cf240509e210ac1f81e2cda75addb4b3e >> >> This is also returning 404. >> >> I hadn't noticed these are all our mirrors, so maybe there's something we >> can do to correct the errors? > > The *.distfiles.macports.org servers are donated by and managed by others. > You can contact their administrators at the addresses listed on this page: > > https://trac.macports.org/wiki/Mirrors Right, will do that. Specially with lil.fr.distfiles.macports.org, which seems to be having a bit more serious problems. > > As for svn.macports.org, that's the absolute last resort fallback URL used > for all ports, if the file is not available at any other location. For > 99.999% of our ports, it is normal for there to be no file there. > Oh, I see, hadn't realized that. Thanks for the insights! - jmpp _______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
