[MacPorts] ProblemHotlist modified

[MacPorts]

Changed page "ProblemHotlist" by jmr at macports.org from 123.243.246.165*
Page URL: <http://trac.macports.org/wiki/ProblemHotlist>
Diff URL: <http://trac.macports.org/wiki/ProblemHotlist?action=diff&version=39>
Revision 39
Comment: update for 1.7

-------8<------8<------8<------8<------8<------8<------8<------8<--------
Index: ProblemHotlist
=========================================================================
--- ProblemHotlist (version: 38)
+++ ProblemHotlist (version: 39)
@@ -4,9 +4,9 @@
 
 == .profile not set up ==
 
-After a fresh installation of MacPorts 1.6.0, the `.profile` is not set up as it should be, with the consequence that the shell says the `port` command is not found when you try to use it. This is [ticket:13742 a bug in the 1.6.0 installer]. It will be fixed in the next release of MacPorts.
+After a fresh installation of MacPorts 1.6.0, the `.profile` is not set up as it should be, with the consequence that the shell says the `port` command is not found when you try to use it. This is [ticket:13742 a bug in the 1.6.0 installer]. It is fixed in MacPorts 1.7.0.
 
-To work around the problem, download the `postflight` script and run it manually, like this:
+The recommended fix is to install the MacPorts 1.7 .pkg. You could also work around the problem by downloading the corrected `postflight` script and running it manually, like this:
 
 {{{
 curl -O http://svn.macports.org/repository/macports/branches/release_1_6/base/portmgr/dmg/postflight && bash postflight
@@ -16,7 +16,7 @@
 
 To get the terminal to notice the new `.profile`, close your terminal window and open a new one.
 
-Instead of downloading and running the `postflight` script from the repository, you could set up your `.profile` manually, as [http://guide.macports.org/#installing.shell explained in the Guide].
+Instead of downloading and running the `postflight` script from the repository, you could alternatively set up your `.profile` manually, as [http://guide.macports.org/#installing.shell explained in the Guide].
 
 == man port fails with error message ==
 If you get following error message, when trying to access the man page for port or installed ports.
@@ -45,7 +45,7 @@
 
 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 will be automatically used as of the 1.7.0 release.
+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>
@@ -133,11 +133,11 @@
 }}}
 
 == 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 1.6.  The simple fix 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
+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.
-
-This issue has been fixed on trunk.

-------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 .