Ticket #11951 (closed defect: fixed)
port selfupdate doesn't work as expected
| Reported by: | vinc17@… | Owned by: | eridius@… |
|---|---|---|---|
| Priority: | High | Milestone: | |
| Component: | base | Version: | 1.4.3 |
| Keywords: | Cc: | vinc17@… | |
| Port: |
Description
First, "port selfupdate" doesn't work as described in the port man page. A second problem is that it tries to update private SVN working copies (i.e. those belonging to a different user, which means a complete mess in the file permissions).
Change History
comment:3 Changed 6 years ago by eridius@…
Ok, updating the svn repos now uses the uid/gid of the owner of the repo. Fixed in r25142. Leaving ticket open until you describe what you mean by "port selfupdate" doesn't work as described.
comment:4 Changed 6 years ago by vinc17@…
The port man page says:
selfupdate
Updates the MacPorts system, dports tree(s) and base tools if needed,
from the MacPorts rsync server, installing the newest infrastructure
^^^^^^^^^^^^^^^^^^^^^
available. To update you would typically do:
Subversion working copies (in particular private ones) are not mentioned.
Note: See
TracTickets for help on using
tickets.


Actually it's port sync that does the SVN updating, it's just that selfupdate calls sync. But the point about the user permissions is a good one.
And can you describe what you mean by doesn't work as described?