Port Selfupdate failed - Mountain Lion OS X

[Lawrence Velázquez]

On Aug 29, 2014, at 8:02 AM, Ryan Schmidt <ryandesign at macports.org> wrote:

> However I would not think this difference would matter. I'm afraid I'm at a loss for why your system claims that files and directories that exist don't exist. There is something unusual about your computer, but I cannot figure out what it is.

There's something weird about these error messages.

> sh: error: /usr/bin/rsync -rtzv --delete-after rsync://rsync.macports.org/release/tarballs/base.tar /opt/local/var/macports/sources/rsync.macports.org/release/tarballs: No such file or directory


> sh: error: /usr/bin/bzip2 -d -c /opt/local/var/macports/software/zlib/zlib-1.2.8_0.darwin_12.x86_64.tbz2 | ( /usr/bin/tar -xvpf - ): No such file or directory

Why is the shell throwing the errors? These are not the messages I'd expect if rsync and bzip2 were trying to access inaccessible directories.


    % sh -c '/usr/bin/bzip2 -d -c ~larryv/foobar.tbz2'
    bzip2: Can't open input file /Users/larryv/foobar.tbz2: No such file or directory.
    %

Note that the error comes from the executable, not the shell, and the entire pipeline is not printed out. (The bit after "Command failed:" is expected.) The OP's error messages look like overzelaous quoting:

    % sh -c '"/usr/bin/bzip2 -d -c ~larryv/foobar.tbz2"'
    sh: /usr/bin/bzip2 -d -c ~larryv/foobar.tbz2: No such file or directory
    %

But I have no idea how that could be happening.

vq