#44199: gnutls 3.3.5 org.macports.fetch for port gnutls returned: fetch failed -------------------------+---------------------------- Reporter: phoglund@… | Owner: mschamschula@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.1 Resolution: | Keywords: Port: gnutls | -------------------------+---------------------------- Comment (by mschamschula@…): Replying to [comment:5 phoglund@…]:
Replying to [comment:4 mschamschula@…]:
I'm not sure what is going on here. The binary files may not have been built by the MacPorts buildbot, but your system should download the source files and build it locally.
This too seems to have failed.
I just double checked the GNU master site:
{{{ ftp://ftp.gnutls.org/gcrypt/gnutls/v3.3/ }}} and found the archive to be present. I just had four iMacs in my department's computer lab fetch these tar balls and build gnutls 3.3.5, w/o any problems.
Do you have a DNS issue?
Uh, alright. Do you mean you manually fetched the tarballs from gnutls.org and built manually?
As far I can see the 404's from the mirrors are correct; for instance, looking at {{{ http://fco.it.distfiles.macports.org/mirrors/macports-distfiles/gnutls/ }}} reveals there is no file for 3.3.5. Is it supposed to build locally from source when none of the mirrors yields a hit? Looks in the log like it gives up after all the mirrors give 404's.
Nope. Nothing manual about my builds this morning, matter of fact they were part of a {{{ sudo port upgrade outdated }}} run. 404s are not uncommon, thats why MacPorts checks multiple sites. However, in this case there is something wrong with the MacPorts infrastructure, as the mirrors have not fetched any of the gnutls 3.3.x tar balls. Yet the above mentioned ftp site should not have failed. -- Ticket URL: <https://trac.macports.org/ticket/44199#comment:6> MacPorts <http://www.macports.org/> Ports system for OS X