Using compatibility mode.ĭec 28 22:58:36 mac-name runner: postflight: Unknown shell! Please set your MacPorts compatible environment manually.ĭec 28 22:58:36 mac-name runner: postflight:ĭec 28 22:58:36: - last message repeated 1 time -ĭec 28 22:58:36 mac-name runner: postflight: Checking the shell environment for user "USERNAM".ĭec 28 22:58:36: - last message repeated 2 times -ĭec 28 22:58:36 mac-name runner: postflight: /Users/jester/Downloads/MacPorts-1.6.0.pkg/Contents/Resources/English.lproj/postflight: line 71: /Users/jester/.: Is a directoryĭec 28 22:58:36 mac-name runner: postflight: /Users/jester/Downloads/MacPorts-1.6.0.pkg/Contents/Resources/English.lproj/postflight: line 96: /Users/jester/.: Is a directoryĭec 28 22:58:36 mac-name runner: postflight: Your shell already has the right MANPATH environment variable for use with MacPorts!ĭec 28 22:58:36 mac-name runner: postflight: Your shell already has the right DISPLAY environment variable for use with MacPorts!ĭec 28 22:58:36 mac-name runner: postflight: Synchronizing the MacPorts installation with the project's rsync server.ĭec 28 22:58:37: - last message repeated 1 time -ĭec 28 22:58:37 mac-name runner: postflight: Synchronizing local ports tree from rsync:///release/ports/ The output of postflight contained some error, but they where al related to not running as administrator.ĭec 28 22:58:36 mac-name Installer: run postflight script for MacPorts-1.6.0ĭec 28 22:58:36 mac-name Installer: Localized installer script postflight found in the MacPorts-1.6.0 package. After opening a new shell the PATH, MANPATH, DISPLAY and env where correct (several /opt/ paths added). After running the postflight script ran (withoud sudo), a. I created a new account with no administrator rights and checked the PATH, MANPATH, DISPLAY and env. PS: Do any of you happen to have the /etc/paths.d/macports and /etc/manpaths.d/macports files installed? Lastly, any info that might have been output to the /var/log/install file about the failed run of the postfligth script might also help (hint: the log might have been already rotated, so also look into /var/log/install.log.0.bz2 and possibly higher numbered files). If pasting any terminal output, please enclose it within the wrappers for proper Trac formatting (read WikiFormatting for more info). Setting set -x (debugging mode for bash) might help. Once that's established, try running the postflight script manually (which you can download from here ) and tell me if there are any errors or, on the other hand, if the settings are properly added. the output of the printenv PATH, printenv MANPATH and printenv DISPLAY commands.If you can, please create a virgin account (if on Leopard, the Guest account might suffice) and confirm that it doesn't have any MacPorts Terminal settings through the following: Any more info anyone in this ticket can provide me with? I am unable to reproduce this bug: when I run the script on a virgin account with no MacPorts settings, they are properly added to the ~/.profile file (which is properly created if it doesn't already exist).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |