error during update with git-core

[Ryan Schmidt]

On Aug 14, 2013, at 20:10, Wes James wrote:

> I did a seflupdate then port upgrade outdated.  All went fine until git...  This is from the log:
> 
> :info:extract /usr/bin/gnutar: git-1.8.3.4/xdiff/xutils.h: Cannot open: No such file or directory
> :info:extract /usr/bin/gnutar: git-1.8.3.4/zlib.c: Cannot open: No such file or directory
> :info:extract /usr/bin/gnutar: git-1.8.3.4/git.spec: Cannot open: No such file or directory
> :info:extract /usr/bin/gnutar: git-1.8.3.4/configure: Cannot open: No such file or directory
> :info:extract /usr/bin/gnutar: git-1.8.3.4/version: Cannot open: No such file or directory
> :info:extract /usr/bin/gnutar: git-1.8.3.4/git-gui/version: Cannot open: No such file or directory
> :info:extract /usr/bin/gnutar: Error exit delayed from previous errors
> :info:extract Command failed:  cd "/opt/local/var/macports/build/_Volumes_qlRAID_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_git-core/git-core/work" && /usr/bin/gzip -dc '/opt/local/var/macports/distfiles/git-core/git-1.8.3.4.tar.gz' | /usr/bin/gnutar --no-same-owner -xf - 
> :info:extract Exit code: 2
> :error:extract org.macports.extract for port git-core returned: command execution failed
> :debug:extract Error code: NONE
> :debug:extract Backtrace: command execution failed
>     while executing
> "$procedure $targetname"
> :info:extract Warning: targets not executed for git-core: org.macports.install org.macports.extract org.macports.patch org.macports.configure org.macports.build org.macports.destroot
> :notice:extract Please see the log file for port git-core for details:
>     /opt/local/var/macports/logs/_Volumes_qlRAID_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_git-core/git-core/main.log
> 
> What can I do to fix this?

Is /opt/local a symlink? Based on "_Volumes_qlRAID" above I assume it is. Having /opt/local be a symlink is unfortunately broken in MacPorts 2.2. You can monitor this ticket for progress on resolving this issue:

https://trac.macports.org/ticket/39850