Opened 18 years ago

Closed 18 years ago

#11951 closed defect (fixed)

port selfupdate doesn't work as expected

Reported by: vinc17@… Owned by: kballard (Lily Ballard)
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 (5)

comment:1 Changed 18 years ago by kballard (Lily Ballard)

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?

comment:2 Changed 18 years ago by kballard (Lily Ballard)

Owner: changed from macports-dev@… to eridius@…

comment:3 Changed 18 years ago by kballard (Lily Ballard)

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 18 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.

comment:5 Changed 18 years ago by kballard (Lily Ballard)

Resolution: fixed
Status: newclosed

Ok, I've fixed the documentation to mention it (r25234).

Note: See TracTickets for help on using tickets.