Opened 3 years ago

Closed 3 years ago

#65078 closed defect (invalid)

fetch failure(s) but packages available using webbrowser

Reported by: dd5fz Owned by:
Priority: Normal Milestone:
Component: ports Version: 2.7.2
Keywords: Cc:
Port: SDRAngel

Description (last modified by reneeotten (Renee Otten))

MacPorts, freshly installed so that I could install SDRAngel, is failing to fetch packages, which I can see when browse the servers with Safari, e.g. https://packages.macports.org/libtool/ or https://packages.macports.org/SoapySDR/

As a MacPort newbie, I'm afraid I've not able to figure out what is actually going wrong. I haven't noticed any irregularities in my network or my internet connection.

I've tried experimentally to install couple of other ports, but the same thing happens. Here is an example of what I'm seeing (see attached log).

Attachments (1)

PortInstallDebugInfo.txt (365.7 KB) - added by dd5fz 3 years ago.

Download all attachments as: .zip

Change History (5)

Changed 3 years ago by dd5fz

Attachment: PortInstallDebugInfo.txt added

comment:1 Changed 3 years ago by dd5fz

I've added this:

sudo port -d install sdrangel &> PortInstallDebugInfo.txt

as an attachment, in the hope that it helps.

comment:2 Changed 3 years ago by reneeotten (Renee Otten)

Description: modified (diff)
Keywords: fetch install removed
Port: SDRAngel added
Priority: HighNormal
Summary: Fetch appears to fail constantly on M1 Mac (Monterey 12.3.1)fetch failure(s) but packages available using webbrowser

comment:3 Changed 3 years ago by dd5fz

Strangely after several re-installs and re-boots, it now is working. The only difference I can see is that Safari isn’t running concurrently.

I would now assume a MacOS bug was the cause.

comment:4 Changed 3 years ago by ryandesign (Ryan Carsten Schmidt)

Resolution: invalid
Status: newclosed

All of your fetch attempts in the log failed with timeout errors:

DEBUG: Fetching archive failed: SSL connection timeout
DEBUG: Fetching archive failed: Recv failure: Socket is not connected

Since all servers failed with such messages, that wouldn't be a problem with any of the servers; it would be a problem with your computer or its internet connection.

Note: See TracTickets for help on using tickets.