On Nov 28, 2011, at 7:13 PM, Ryan Schmidt wrote: > > On Nov 28, 2011, at 21:10, Ryan Schmidt wrote: > >> On Nov 28, 2011, at 20:48, Bradley Giesbrecht wrote: >> >>> sh: line 0: cd: >>> /opt/macports-clean/var/macports/software/zlib/zlib-1.2.5_0.darwin_10.x86_64.tbz2: >>> No such file or directory >>> shell command "cd >>> /opt/macports-clean/var/macports/software/zlib/zlib-1.2.5_0.darwin_10.x86_64.tbz2 >>> && /usr/bin/tar -cjf >>> /opt/macports-clean/var/macports/software/zlib/zlib-1.2.5_0.darwin_10.x86_64.tbz2 >>> * > /opt/macports-clean/var/macpo >> >> Not entirely sure what this is about. Does that file exist? If so, delete it >> and try again? Are the permissions and ownership of that directory and every >> directory leading up to it correct? > > Looking more closely, the really weird part is: "cd > /opt/macports-clean/var/macports/software/zlib/zlib-1.2.5_0.darwin_10.x86_64.tbz2" > -- why's it trying to Change Directory to something that's supposed to be a > file? ...
That is what I found odd. port selfupdate seems to have resolved my issue. I understood that when using base "port selfupdate" did not compile a new base so I have been in the habit of using "svn up" and manually compiling base. Should I be running selfupdate for other reasons? If so, when? After or before each base install or dports update? Regards, Bradley Giesbrecht (pixilla) _______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
