5 | | == 1. Fetch failures == |
| 5 | == .profile not set up == |
| 6 | |
| 7 | 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. |
| 8 | |
| 9 | To work around the problem, download the `postflight` script and run it manually, like this: |
| 10 | |
| 11 | {{{ |
| 12 | curl -O http://svn.macports.org/repository/macports/branches/release_1_6/base/portmgr/dmg/postflight && bash postflight |
| 13 | }}} |
| 14 | |
| 15 | 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. |
| 16 | |
| 17 | To get the terminal to notice the new `.profile`, close your terminal window and open a new one. |
| 18 | |
| 19 | 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]. |
| 20 | |
| 21 | == man port fails with error message == |
| 22 | If you get following error message, when trying to access the man page for port or installed ports. |
| 23 | {{{ |
| 24 | Cannot open the message catalog "man" for locale "de_DE.UTF-8" (NLSPATH="<none>") |
| 25 | No manual entry for port |
| 26 | }}} |
| 27 | Add the following line to your .profile or .bash_profile. |
| 28 | {{{ |
| 29 | export MANPATH=/opt/local/share/man:${MANPATH} |
| 30 | }}} |
| 31 | Tracked in ticket #13444. |
| 32 | |
| 33 | == Fetch failures == |
95 | | |
96 | | == 4. .profile not set up == |
97 | | |
98 | | 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. |
99 | | |
100 | | To work around the problem, download the `postflight` script and run it manually, like this: |
101 | | |
102 | | {{{ |
103 | | curl -O http://svn.macports.org/repository/macports/branches/release_1_6/base/portmgr/dmg/postflight && bash postflight |
104 | | }}} |
105 | | |
106 | | 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. |
107 | | |
108 | | To get the terminal to notice the new `.profile`, close your terminal window and open a new one. |
109 | | |
110 | | 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]. |
111 | | |
112 | | == 5. man port fails with error message == |
113 | | If you get following error message, when trying to access the man page for port or installed ports. |
114 | | {{{ |
115 | | Cannot open the message catalog "man" for locale "de_DE.UTF-8" (NLSPATH="<none>") |
116 | | No manual entry for port |
117 | | }}} |
118 | | Add the following line to your .profile or .bash_profile. |
119 | | {{{ |
120 | | export MANPATH=/opt/local/share/man:${MANPATH} |
121 | | }}} |
122 | | Tracked in ticket #13444. |