Hi, yes the dpupdate1 to dpupdate was a hand edit at the time when
darwinports.org didn't work for some reason and change to macports.org
was the solution...
I like to know what's in my .conf files and dpupdate1/base
was strange to me since dpupdate/base worked too... :-)
As I mentioned it would be better to have something like
dpupdate_relese and dpupdate_dev instead of meaningless dpupdate1....
after seting rsync_path to dpupdate1/base the selfupdate
downgraded to 1.4 and works ok.
In fact I have to say that the version 1.5 worked for me too,
but I am using just a few ports on a powerbook (tetex, emacs, gcc)
J.
On Apr 9, 2007, at 16:28 , Juan Manuel Palacios wrote:
Hello Jaroslav.
On Apr 7, 2007, at 12:18 PM, Jaroslav Hron wrote:
My settings in port.conf are:
rsync_server rsync.macports.org
rsync_dir dpupdate/base/
I am really curious how you got that particular setting for the
rsync_dir, do you happen to remember? That rsync repo (the value of
rsync_dir) is fed with MacPorts sources from svn's trunk at the
server level, and those sources currently correspond to the still
unreleased 1.5 version of MacPorts (more than still unreleased
actually, practically not even fully planned out).
And I say I am really curious because the ports.conf file does not
ship that value by default, not in trunk and not in any release
branch we've ever created, so it must have been a hand edit. Other
than that.... I am really curious!
In any case, to get back to a released version of MacPorts all you
have to do is change its current value to "dpupdate1/base/" (note
the 1) and force a selfupdate run. Tell us your results (you might
end up with stray sources /opt/local/var/db/dports/sources/
rsync.rsync.darwinports.org_dpupdate, once you make sure you're
back at 1.4.0 you can freely remove that directory).
Thanks, J.
HTH!
-jmpp
_______________________________________________
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users
