[MacPorts] Notification: ProblemHotlist modified
MacPorts
noreply at macports.org
Mon Jul 14 18:52:04 PDT 2008
Changed page "ProblemHotlist" by raimue at macports.org from 91.11.253.69*
Page URL: <http://trac.macports.org/wiki/ProblemHotlist>
Diff URL: <http://trac.macports.org/wiki/ProblemHotlist?action=diff&version=25>
Revision 25
Comment: Removing reference to a closed ticket and add more general information
-------8<------8<------8<------8<------8<------8<------8<------8<--------
Index: ProblemHotlist
=========================================================================
--- ProblemHotlist (version: 24)
+++ ProblemHotlist (version: 25)
@@ -1,12 +1,11 @@
= Problem Hotlist =
-== 1. Fetch failures - readline port and others ==
+== 1. Fetch failures ==
-When MacPorts' fetches via ftp, it contacts servers in passive mode by trying "EPSV" first and then, if that fails, trying "PASV". The server at ftp.cwru.edu, and presumable more servers, break the connection after the "EPSV" request, making it impossible to try "PASV" so the fetch fails. #10832.
+If fetch failed for a port, you can still get the distfile from anywhere else. Maybe the homepage of the software lists alternative download locations for source tarballs. Just download the distfile and save it to `${prefix}/var/macports/distfiles/<portname>/`. Make sure you get a file with exactly the same name (watch out for `.tar.gz` and `.tar.bz2`!) If a `port clean --all` has been done the distfile directory will have been removed. The directory for each port is created at the beginning of the fetch phase.
-Various options are being considered to deal with this in a future release. Right now many ports exhibit this behavior behind firewalls and the only solution is to download the file with the ftp link in a browser or ftp client and copy the file to ${prefix}/var/macports/distfiles/<portname>/. If a 'port clean --all' has been done the distfile directory will have been removed. The directory for each port is created at the beginning of the fetch phase.
-
-If a fetch fails with 1.6.x, try:
+There is in additional possibility to use our new [http://distfiles.macports.org distfiles mirror], which will be automatically used as of the 1.7.0 release.
+If a fetch fails with MacPorts 1.6.x, try:
{{{
sudo env MASTER_SITE_LOCAL=http://distfiles.macports.org/<portname> port -v fetch <portname>
}}}
-------8<------8<------8<------8<------8<------8<------8<------8<--------
* The IP shown here might not mean anything if the user is behind a proxy.
--
MacPorts <http://www.macports.org/>
Ports system for Mac OS
This is an automated message. Someone at http://www.macports.org/
added your email address to be notified of changes on MacPorts.
If it was not you, please report to http://www.macports.org/.
More information about the macports-changes
mailing list