[MacPorts] Notification: ProblemHotlist modified

[MacPorts]

Changed page "ProblemHotlist" by raimue at macports.org from 91.11.245.138*
Page URL: <http://trac.macports.org/wiki/ProblemHotlist>
Diff URL: <http://trac.macports.org/wiki/ProblemHotlist?action=diff&version=35>
Revision 35
Comment: Move the more common problems to the top

-------8<------8<------8<------8<------8<------8<------8<------8<--------
Index: ProblemHotlist
=========================================================================
--- ProblemHotlist (version: 34)
+++ ProblemHotlist (version: 35)
@@ -2,7 +2,35 @@
 
 (Note, if you're using Mac OS X 10.5.x, be sure also to check the LeopardProblems page)
 
-== 1. Fetch failures ==
+== .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.
+
+To work around the problem, download the `postflight` script and run it manually, like this:
+
+{{{
+curl -O http://svn.macports.org/repository/macports/branches/release_1_6/base/portmgr/dmg/postflight && bash postflight
+}}}
+
+This will set up your `.profile` for you. After the `.profile` is set up, the script will attempt to run `sudo port selfupdate` but will fail. This is normal in this case. Please ignore the permission errors the `rsync` process will print. When the script finishes, you should run `sudo port selfupdate` manually.
+
+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].
+
+== man port fails with error message ==
+If you get following error message, when trying to access the man page for port or installed ports.
+{{{
+Cannot open the message catalog "man" for locale "de_DE.UTF-8" (NLSPATH="<none>")
+No manual entry for port
+}}}
+Add the following line to your .profile or .bash_profile.
+{{{
+export MANPATH=/opt/local/share/man:${MANPATH}
+}}}
+Tracked in ticket #13444.
+
+== 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.
 
@@ -22,7 +50,7 @@
 
 '''Note:''' Checksum failures after a fetch are typically a separate issue.  See the [wiki:FAQ#IgetError:checksummd5sha1rmd160mismatchforport.WhatcanIdoaboutit FAQ].
 
-== 2. A port failed to build, upgrade, or run with a message referring to libintl.3.dylib ==
+== A port failed to build, upgrade, or run with a message referring to libintl.3.dylib ==
 
 {{{
 dyld: Library not loaded: /opt/local/lib/libintl.3.dylib
@@ -72,7 +100,7 @@
 port -duf uninstall
 }}}
 
-== 3. A port failed to build with a message referring to 1/lib: No such file or directory ==
+== A port failed to build with a message referring to 1/lib: No such file or directory ==
 
 {{{
 apple-darwin9-gcc-4.0.1: 1/lib: No such file or directory
@@ -92,31 +120,3 @@
 {{{
 port clean --work <port>
 }}}
-
-== 4. .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.
-
-To work around the problem, download the `postflight` script and run it manually, like this:
-
-{{{
-curl -O http://svn.macports.org/repository/macports/branches/release_1_6/base/portmgr/dmg/postflight && bash postflight
-}}}
-
-This will set up your `.profile` for you. After the `.profile` is set up, the script will attempt to run `sudo port selfupdate` but will fail. This is normal in this case. Please ignore the permission errors the `rsync` process will print. When the script finishes, you should run `sudo port selfupdate` manually.
-
-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].
-
-== 5. man port fails with error message ==
-If you get following error message, when trying to access the man page for port or installed ports.
-{{{
-Cannot open the message catalog "man" for locale "de_DE.UTF-8" (NLSPATH="<none>")
-No manual entry for port
-}}}
-Add the following line to your .profile or .bash_profile.
-{{{
-export MANPATH=/opt/local/share/man:${MANPATH}
-}}}
-Tracked in ticket #13444.

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