"skipping non-regular file" during selfupdate

Ryan Schmidt ryandesign at macports.org
Fri Jul 18 14:19:25 PDT 2008


On Jul 18, 2008, at 15:11, William Davis wrote:

> macintosh:~ frstan$ sudo port -d selfupdate
> Password:
> DEBUG: Rebuilding the MacPorts base system if needed.
> DEBUG: Synchronizing ports tree(s)
> Synchronizing local ports tree from rsync://rsync.macports.org/ 
> release/
> ports/
> DEBUG: /usr/bin/rsync -rtzv --delete-after rsync://rsync.macports.org/
> release/ports/ /opt/local/var/macports/sources/rsync.macports.org/
> release/ports
> receiving file list ... done
> skipping non-regular file "lang/llvm-gcc42/work"
> skipping non-regular file "lang/logtalk/work"
> skipping non-regular file "lang/lua/work"
> skipping non-regular file "lang/mdk/work"
> skipping non-regular file "lang/mercury-extras/work"
> skipping non-regular file "lang/mercury/work"
> skipping non-regular file "lang/mosml/work"
>
> snip
>
> skipping non-regular file "zope/zope-validation/work"
> skipping non-regular file "zope/zope-zopetree/work"
> skipping non-regular file "zope/zope-zopezen/work"
> skipping non-regular file "zope/zope-zphotoslides/work"
> skipping non-regular file "zope/zope-zsyncer/work"
>
> snip
>
> Downloaded MacPorts base version 1.600
>
> The MacPorts installation is not outdated and so was not updated
> DEBUG: Setting ownership to root
> selfupdate done!
>
>
> What is this?

When you start using a port (e.g. "sudo port install <portname>" or  
(in MacPorts earlier than 1.7.0) even things like "sudo port  
livecheck <portname>" or "sudo port lint <portname>"), MacPorts  
creates a work area for the port, and creates a symlink "work" in the  
port's directory pointing to that work area. rsync is skipping over  
these symlinks when synchronizing the ports tree. This is normal.  
This symlink and the work area can be removed by doing "sudo port  
clean --work <portname>" or you can clean all ports' work areas with  
"sudo port clean --work all".



More information about the macports-users mailing list