On Jul 9, 2007, at 5:56 PM, Randall Wood wrote:

Error updating macports from 1.5.0-rc1 to 1.5.0:

Getafix:~ rhwood$ sudo port selfupdate MacPorts base version 1.5 installed Error: /opt/local/bin/port: selfupdate failed: couldn't open "/opt/ local/var/macports/sources/rsync.macports.org/release/base/config/ mp_version": no such file or directory Getafix:~ rhwood$ sudo port -dv selfupdate DEBUG: Rebuilding the MacPorts base system if needed. DEBUG: Synchronizing ports tree(s) Synchronizing 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

sent 74 bytes received 269017 bytes 19932.67 bytes/sec total size is 14713580 speedup is 54.68 Synchronizing from file:///Users/rhwood/Developer/MacPorts/ WorkingPorts DEBUG: MacPorts base dir: /opt/local/var/macports/sources/ rsync.macports.org/release/base DEBUG: Setting user: root MacPorts base version 1.5 installed DEBUG: Updating using rsync receiving file list ... done config/

sent 73 bytes received 4957 bytes 1437.14 bytes/sec total size is 2093103 speedup is 416.12 DEBUG: couldn't open "/opt/local/var/macports/sources/ rsync.macports.org/release/base/config/mp_version": no such file or directory while executing "open [file join $mp_base_path config mp_version] r" (procedure "macports::selfupdate" line 45) invoked from within "macports::selfupdate [array get global_options]" Error: /opt/local/bin/port: selfupdate failed: couldn't open "/opt/ local/var/macports/sources/rsync.macports.org/release/base/config/ mp_version": no such file or director

Hi Randall! You're only seeing this error 'cause you attempted a selfupdate from a 1.5rc1 installation to the sources provided by the "release/base/" rsync repository on our rsync server, which just as of yesterday correspondded to the 1.4.42 release. So you basically attempted a downgrade which naturally fails (for various reasons, actually, not just the one you experienced here). Nevertheless, I updated the base/config/RELEASE_URL file this early morning to point to the 1.5.0 svn tag, effectively releasing 1.5.0 through selfupdate for all users (default "release/base/" rsync repository). You should be able to selfupdate successfully now. Regards,... -jmpp PS: selfupdating to the "trunk/base/" rsync repo will always get you trunk/base's ToT sources, in case you can't care to svn co them && ./ configure && make && make install.