Ticket #16375 (closed defect: invalid)
libwww-5.4.0: cannot fetch w3c-libwww-5.4.0.tgz
| Reported by: | darren.weber.lists@… | Owned by: | macports-tickets@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 1.6.0 |
| Keywords: | libwww xmlrpc-c | Cc: | |
| Port: |
Description
elegans:~ root# port install xmlrpc-c ---> Fetching libwww ---> Attempting to fetch w3c-libwww-5.4.0.tgz from http://www.w3.org/Library/Distribution/ ---> Attempting to fetch w3c-libwww-5.4.0.tgz from http://svn.macports.org/repository/macports/distfiles/libwww ---> Attempting to fetch w3c-libwww-5.4.0.tgz from http://svn.macports.org/repository/macports/distfiles/general/ ---> Attempting to fetch w3c-libwww-5.4.0.tgz from http://svn.macports.org/repository/macports/downloads/libwww Error: Target org.macports.fetch returned: fetch failed Error: The following dependencies failed to build: libwww Error: Status 1 encountered during processing. elegans:~ root#
Change History
comment:1 Changed 5 years ago by blb@…
- Milestone set to Port Bugs
- Summary changed from cannot fetch w3c-libwww-5.4.0.tgz to libwww-5.4.0: cannot fetch w3c-libwww-5.4.0.tgz
comment:2 Changed 5 years ago by darren.weber.lists@…
OK, must have been a server glitch, seems to get it now. I was a bit surprised to see that it tried the macports svn (in several places) and still failed. So it appeared that at least 2 servers were not able to cough-up. There's no proxy config here and web access was fine at the time. Still puzzled, but up and running now anyway. Let's close this one, sorry for the inconvenience. Thanks!
Note: See
TracTickets for help on using
tickets.
The file fetches fine here. Do you have any proxy configuration needed? If not, maybe just try again, the server could have been having issues when you tried before. If that doesn't work, have a look at the fetch failures section on the problem hotlist to get port to fetch from the MacPorts mirror.