On 16.5.2007, at 9.55, source_changes@macosforge.org wrote:

Revision 25234 Author eridius@macports.org Date 2007-05-15 23:55:26 -0700 (Tue, 15 May 2007) Log MessageUpdate the documentation on sync and selfupdate to mention the subversion updating behaviourModified Paths trunk/base/src/port/port.1 Diff Modified: trunk/base/src/port/port.1 (25233 => 25234)--- trunk/base/ src/port/port.1 2007-05-16 06:48:05 UTC (rev 25233) +++ trunk/base/ src/port/port.1 2007-05-16 06:55:26 UTC (rev 25234) @@ -309,6 +309,12 @@ from the MacPorts rsync server. To update you would normally do: .Pp .Dl "sudo port -d sync" +.Pp +If any of the dports tree(s) uses a file: URL that points to a local subversion working copy, +.Ic sync +will perform an +.Ic "svn update" +on the working copy with the user set to the owner of the working copy. .Ss outdated List the installed ports that need upgrading. .Ss upgrade @@ -394,6 +400,10 @@ installing the newest infrastructure available. To update you would typically do: .Pp .Dl "sudo port -d selfupdate" +.Pp +See +.Ic sync +for more information about updating dports tree(s). .Ss help Displays a summary of all available actions and port command syntax on stdout. .Sh DEVELOPER TARGETS _______________________________________________

To me this comment does not describe the situation correctly (the document says, how it should be, not how it is). I use normally 'sudo port selfupdate' or 'sudo port sync', the result is that the subversion working copy owned by me will be tainted by files owned not by me, thereby preventing me updating. I am happy, if I really am wrong! PS This is easy to fix (use chown before svn up), an annoyance nevertheless! ! ! Jyrki Wahlstedt ! skype:jyrkiwahlstedt ! http://www.wahlstedt.fi/jyrki/ ! ! Our life is no dream; but it ought to become one and perhaps will. ! PGP key ID: 0x139CC386 fingerprint: F355 B46F 026C B8C1 89C0 A780 6366 EFD9 139C C386