Opened 7 years ago

Closed 7 years ago

#55695 closed defect (invalid)

ncurses-6.0-20171125: Failed to fetch

Reported by: jbnymble Owned by: jmroot (Joshua Root)
Priority: Normal Milestone:
Component: ports Version: 2.4.2
Keywords: Cc:
Port: ncurses

Description


Attachments (2)

fetch_fail.txt (9.5 KB) - added by jbnymble 7 years ago.
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_ncurses/ncurses/main.log
3_fails.txt.zip (1.4 KB) - added by jbnymble 7 years ago.

Download all attachments as: .zip

Change History (10)

Changed 7 years ago by jbnymble

Attachment: fetch_fail.txt added

/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_ncurses/ncurses/main.log

comment:1 Changed 7 years ago by mf2k (Frank Schima)

Component: baseports
Owner: set to jmroot
Port: ncurses added
Status: newassigned
Summary: ncurses-6.0-20171125 "port upgrade outdated" Error: Failed to fetch ncurses: ÒÒncurses-6.0-20171125: Failed to fetch

comment:2 Changed 7 years ago by jmroot (Joshua Root)

Can't reproduce. Those are some very strange strings where the reason for the failure would normally be printed, e.g.

:debug:archivefetch Fetching archive failed: ÿÿÿÿ

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

Yeah. Does your /usr/bin/curl work on the command line?

comment:4 in reply to:  3 Changed 7 years ago by jbnymble

Replying to ryandesign:

Yeah. Does your /usr/bin/curl work on the command line?

Yes indeed, no trouble there.

comment:5 Changed 7 years ago by ryandesign (Ryan Carsten Schmidt)

Presumably this is not a port-specific problem. I assume all ports fail with similar errors.

Has it ever worked for you? If so, what changed between then and now?

Changed 7 years ago by jbnymble

Attachment: 3_fails.txt.zip added

comment:6 Changed 7 years ago by jbnymble

To answer Ryan's question, I have followed the entire prescribed procedure for upgrade to a new major release—a redundant process, my installation was long since high sierra-ed. Of the 49 ports in myports.txt, only 13 were re-installed, 11 having no dependences and 1 with only a single dependency, all 13 already up to date in the previous installation. All ports eligible for updating, and all with multiple dependencies uniformly failed to fetch. This is a problem with fetching archives from repository mirrors. The attachment 3_fails.txt.zip shows the moment of failure for nvi, tidy, and unicode.

comment:7 Changed 7 years ago by jbnymble

CLOSE THIS TICKET. Thanks to all who helped! PF was blocking tclsh. Problem solved.

comment:8 Changed 7 years ago by kencu (Ken)

Resolution: invalid
Status: assignedclosed
Note: See TracTickets for help on using tickets.