Changes between Version 33 and Version 34 of ProblemHotlist
- Timestamp:
- Aug 6, 2008, 4:45:46 AM (16 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ProblemHotlist
v33 v34 98 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 99 100 To work around the problem, download the postflightscript and run it manually, like this:100 To work around the problem, download the `postflight` script and run it manually, like this: 101 101 102 102 {{{ … … 104 104 }}} 105 105 106 '''Note:''' Reopen your Terminal window after running the command! 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 107 108 You could also set up your `.profile` manually, as [http://guide.macports.org/#installing.shell explained in the Guide]. 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]. 109 111 110 112 == 5. man port fails with error message ==