Re: "Fetching archive" fails for all ports on multiple systems, different networks

On 2019-4-14 15:17 , Lee Finn wrote: > Hi Joshua,  > > The curl is the MacPorts curl. The linking is the same as your reference.  OK, so do you get the same result with /usr/bin/curl? - Josh signature.asc Description: OpenPGP digital signature

Re: "Fetching archive" fails for all ports on multiple systems, different networks

Hi Joshua, The curl is the MacPorts curl. The linking is the same as your reference. Best, Sam — Sam Finn lsf...@gmail.com > On Apr 13, 2019, at 8:03 PM, Joshua Root > wrote: > > Lee Finn wrote: >> Hi Dave et al. >> >> I repeated the cu

Re: "Fetching archive" fails for all ports on multiple systems, different networks

Lee Finn wrote: > Hi Dave et al. > > I repeated the curl. The md5 checks: the xfer was completed correctly. Which curl was it though, MacPorts or system? (Running 'type curl' will answer this.) > Advice welcome! I would check if you have any proxies configured, via any of System Preferences, en

Re: "Fetching archive" fails for all ports on multiple systems, different networks

The problem arises on both my home network and my work network. — Sam Finn lsf...@gmail.com > On Apr 13, 2019, at 1:28 PM, Chris Jones > wrote: > > > What network are you on ? Home or work ? Could something have changed with > that

Re: "Fetching archive" fails for all ports on multiple systems, different networks

Otherwise, I am a macports novice. In the absence of better advice, I would be inclined to some hacking along the lines of uninstalling and reinstalling things. Wait and see if there is better advice from those who know macports internals. On Sat, Apr 13, 2019 at 6:20 PM Lee Finn wrote: > Hi

Re: "Fetching archive" fails for all ports on multiple systems, different networks

Hi Dave et al. I repeated the curl. The md5 checks: the xfer was completed correctly. Advice welcome! Sam — Sam Finn lsf...@gmail.com > On Apr 13, 2019, at 5:57 PM, Dave Allured - NOAA Affiliate via macports-users > > wro

Re: "Fetching archive" fails for all ports on multiple systems, different networks

I think you all are overlooking this report from a few days back. The requested "curl" test passed on Sam's machine. This strongly indicates a problem within Sam's Macports software, NOT a network problem. Excerpt: On Mon, Apr 8, 2019 at 10:54 AM Lee Finn wrote: > Hi Chris ... Thanks for yo

Re: "Fetching archive" fails for all ports on multiple systems, different networks

What network are you on ? Home or work ? Could something have changed with that ? > On 13 Apr 2019, at 8:04 pm, Lee Finn wrote: > > Thank for your note. > > A quick question: since everything was working up until 1 Apr (I routinely > update my macports every monday, and did so as recently a

Re: "Fetching archive" fails for all ports on multiple systems, different networks

Thank for your note. A quick question: since everything was working up until 1 Apr (I routinely update my macports every monday, and did so as recently as 25 Mar), is there anything you can advise I look to first? The only system updates that I’m aware of in that week were the 10.14.4 and xCode

Re: "Fetching archive" fails for all ports on multiple systems, different networks

On Apr 10, 2019, at 10:28, Lee Finn wrote: > Hi, > > This is a more directed followup to an earlier message. Three specific > questions: > > * How should I interpret the error message ":debug:archivefetch Fetching > archive failed: The requested URL returned error: 403 OK”, which appear

Re: "Fetching archive" fails for all ports on multiple systems, different networks

Hi, This is a more directed followup to an earlier message. Three specific questions: * How should I interpret the error message ":debug:archivefetch Fetching archive failed: The requested URL returned error: 403 OK”, which appears in the logfile for the installation of gettext? - Fu

Re: "Fetching archive" fails for all ports on multiple systems, different networks

Hi, On Mon, Apr 08, 2019 at 10:53:51AM -0600, Lee Finn wrote: > The log file at > > is attached: I'd agree that this seems like a problem with your network, especially since - you get the same response for all mirrors - the response is always 403 OK (which is weird, because 403 should be "F

Re: "Fetching archive" fails for all ports on multiple systems, different networks

Hi Chris, Thanks for your note. Running the indicated command gives the following: Quedo [2] Yeah? curl -O -R https://packages.macports.org/libiconv/libiconv-1.15_0.darwin_18.x86_64.tbz2  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current                                 D

Re: "Fetching archive" fails for all ports on multiple systems, different networks

Hi, On a first guess, I would say you have an issue with your network. what does running > curl -O -R https://packages.macports.org/libiconv/libiconv-1.15_0.darwin_18.x86_64.tbz2 give ? It would also help post the complete logs referred to below. I doubt Xcode 10.2 has anything to do with

"Fetching archive" fails for all ports on multiple systems, different networks

Hi All - I’m stuck and looking for advice on how to get unstuck. H/W & S/W configuration: Two systems: iMac Pro & MacBook Pro (problem is common to both) OS X 10.4.4 xCode 10.2 MacPorts 2.5.4 The problems I’m encountering are * A failure in archivefetch for many (all?) ports; * ports diagno