[MacPorts] ProblemHotlist modified

[MacPorts]

Changed page "ProblemHotlist" by raimue at macports.org from 91.11.205.137*
Page URL: <http://trac.macports.org/wiki/ProblemHotlist>
Diff URL: <http://trac.macports.org/wiki/ProblemHotlist?action=diff&version=46>
Revision 46
Comment: Remove old MacPorts 1.6 references

-------8<------8<------8<------8<------8<------8<------8<------8<--------
Index: ProblemHotlist
=========================================================================
--- ProblemHotlist (version: 45)
+++ ProblemHotlist (version: 46)
@@ -39,20 +39,6 @@
 == Fetch failures == #fetch-failures
 
 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.
-
-There is in additional possibility to use our new [http://distfiles.macports.org distfiles mirror], which is 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>
-}}}
-
-Unless it's a port that starts with p5-, py-, py25-, or rb-, in which case you use one of the following:
-{{{
-sudo env MASTER_SITE_LOCAL=http://distfiles.macports.org/perl5 port -v fetch p5-<rest_of_portname>
-sudo env MASTER_SITE_LOCAL=http://distfiles.macports.org/python port -v fetch py-<rest_of_portname>
-sudo env MASTER_SITE_LOCAL=http://distfiles.macports.org/python port -v fetch py25-<rest_of_portname>
-sudo env MASTER_SITE_LOCAL=http://distfiles.macports.org/ruby port -v fetch rb-<rest_of_portname>
-}}}
 
 '''Note:''' Checksum failures after a fetch are typically a separate issue.  See the [wiki:FAQ#IgetError:checksummd5sha1rmd160mismatchforport.WhatcanIdoaboutit FAQ].
 
@@ -161,16 +147,6 @@
 port clean --work <port>
 }}}
 
-== Inactive port can't be removed even though a newer version is installed ==
-If, after upgrading a port, you find you can't remove the older, inactive, version because {{{port}}} tells you it is a dependency of another port, this is a bug in MacPorts 1.6 and earlier. The recommended fix is to upgrade to MacPorts 1.7.0 or later.
-
-In 1.6, the workaround is to force it: {{{sudo port -f uninstall <port> @<older_version>}}} (replacing <port> with the port name and <older_version> with the version string for the older version).  For example, if you've upgraded libpng recently, a {{{port installed libpng}}} may show
-{{{
-  libpng @1.2.30_0
-  libpng @1.2.31_0 (active)
-}}}
-Running {{{sudo port uninstall libpng}}} or {{{sudo port uninstall libpng @1.2.30_0}}} will complain that other ports depend on libpng and you can't uninstall.  Simply add a -f to get it to go: {{{sudo port -f uninstall libpng @1.2.30_0}}}.  Just make sure you remove the older, inactive version.
-
 == Can't install python modules because of unrecognized --no-user-cfg == #no-user-cfg
 
 '''Error message:'''[[BR]]

-------8<------8<------8<------8<------8<------8<------8<------8<--------

* The IP shown here might not mean anything if the user or the server 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 ProblemHotlist. If it was not you, please
report to .