Changes between Version 33 and Version 34 of ProblemHotlist


Ignore:
Timestamp:
Aug 6, 2008, 4:45:46 AM (16 years ago)
Author:
ryandesign (Ryan Carsten Schmidt)
Comment:

note that rsync permissions errors are normal when running postflight manually; reword surrounding passages

Legend:

Unmodified
Added
Removed
Modified
  • ProblemHotlist

    v33 v34  
    9898After 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.
    9999
    100 To work around the problem, download the postflight script and run it manually, like this:
     100To work around the problem, download the `postflight` script and run it manually, like this:
    101101
    102102{{{
     
    104104}}}
    105105
    106 '''Note:''' Reopen your Terminal window after running the command!
     106This 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.
    107107
    108 You could also set up your `.profile` manually, as [http://guide.macports.org/#installing.shell explained in the Guide].
     108To get the terminal to notice the new `.profile`, close your terminal window and open a new one.
     109
     110Instead 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].
    109111
    110112== 5. man port fails with error message ==