#49569: selfupdate failed on El Capitan -----------------------------+-------------------------------- Reporter: axknightroad@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.3.4 Resolution: | Keywords: Port: | -----------------------------+-------------------------------- Comment (by axknightroad@…): Replying to [comment:1 ryandesign@…]:

Unfortunately there's not much information in that error message to go on.

Does this problem always happen?

Has it ever worked? If so, what changed since then?

It happened every time I used selfupdate since I have installed MacPorts. -- Ticket URL: <https://trac.macports.org/ticket/49569#comment:2> MacPorts <https://www.macports.org/> Ports system for OS X

#49569: selfupdate failed on El Capitan -----------------------------+-------------------------------- Reporter: axknightroad@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.3.4 Resolution: | Keywords: Port: | -----------------------------+-------------------------------- Comment (by axknightroad@…): I have tried many times in different networks, but it never works. And it worked when I used the '''rsync''' command with '''rsync://rsync.macports.org/release/tarballs/base.tar'''. So I don't think it is network problem. It showed these infromation when I used debug switch (-d)： {{{ $ sudo port -d selfupdate DEBUG: Copying /Users/axel/Library/Preferences/com.apple.dt.Xcode.plist to /opt/local/var/macports/home/Library/Preferences DEBUG: MacPorts sources location: /opt/local/var/macports/sources/rsync.macports.org/release/tarballs ---> Updating MacPorts base sources using rsync Command failed: /usr/bin/rsync -rtzv --delete-after rsync://rsync.macports.org/release/tarballs/base.tar /opt/local/var/macports/sources/rsync.macports.org/release/tarballs Exit code: 1 DEBUG: Error synchronizing MacPorts sources: command execution failed while executing "macports::selfupdate [array get global_options] base_updated" Error: Error synchronizing MacPorts sources: command execution failed To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: /opt/local/bin/port: port selfupdate failed: Error synchronizing MacPorts sources: command execution failed }}} -- Ticket URL: <https://trac.macports.org/ticket/49569#comment:4> MacPorts <https://www.macports.org/> Ports system for OS X

#49569: selfupdate failed on El Capitan -----------------------------+-------------------------------- Reporter: axknightroad@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.3.4 Resolution: | Keywords: Port: | -----------------------------+-------------------------------- Comment (by axknightroad@…): Replying to [comment:5 ryandesign@…]:

Does the directory /opt/local/var/macports/sources/rsync.macports.org/release/tarballs exist and have the correct permissions and ownership?

Yes, this directorie exists and its permissions are 755. I tried changing it to 777, but the selfupdate command failed still. -- Ticket URL: <https://trac.macports.org/ticket/49569#comment:6> MacPorts <https://www.macports.org/> Ports system for OS X

#49569: selfupdate failed on El Capitan -----------------------------+-------------------------------- Reporter: axknightroad@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.3.4 Resolution: | Keywords: Port: | -----------------------------+-------------------------------- Comment (by bernard.jphilippe@…): I exactly have the same problem on my personal computer (running on El Capitan). But I don't have this problem on my professional computer (running on Yosemite). -- Ticket URL: <https://trac.macports.org/ticket/49569#comment:8> MacPorts <https://www.macports.org/> Ports system for OS X

#49569: selfupdate failed on El Capitan -----------------------------+-------------------------------- Reporter: axknightroad@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.3.4 Resolution: | Keywords: Port: | -----------------------------+-------------------------------- Comment (by uncat): Replying to [ticket:49569 axknightroad@…]:

I installed MacPorts using the OS X package installer today. but it failed when I update using port -v selfupdate. {{{ $ sudo port -v selfupdate ---> Updating MacPorts base sources using rsync Command failed: /usr/bin/rsync -rtzv --delete-after rsync://rsync.macports.org/release/tarballs/base.tar /opt/local/var/macports/sources/rsync.macports.org/release/tarballs Exit code: 1 Error: Error synchronizing MacPorts sources: command execution failed To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: /opt/local/bin/port: port selfupdate failed: Error synchronizing MacPorts sources: command execution failed }}}

but the commmand below is worked. {{{ $ sudo /usr/bin/rsync -rtzv --delete-after rsync://rsync.macports.org/release/tarballs/base.tar /opt/local/var/macports/sources/rsync.macports.org/release/tarballs }}}

-- Ticket URL: <https://trac.macports.org/ticket/49569#comment:10> MacPorts <https://www.macports.org/> Ports system for macOS

#49569: selfupdate failed on El Capitan -----------------------------+-------------------------------- Reporter: axknightroad@… | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: base | Version: 2.3.4 Resolution: invalid | Keywords: Port: | -----------------------------+-------------------------------- Changes (by ryandesign): * status: new => closed * resolution: => invalid Comment: Replying to [comment:11 uncat]:

Replying to [comment:9 alfreditomora@…]:

...

Replying to [ticket:49569 axknightroad@…]:

I had the same error over a wifi connection, but when I moved to a wired connection it worked. Additionally I had to change the permissions (chmod 777) to this file (/opt/local/var/macports/sources/rsync.macports.org/release/tarballs/). Finally I used sudo to run the command:

sudo port -v selfupdate

you are right ,but not 777 ,because it is a directory,so you should change the permissions (chmod 664) to that file

Directories need execute permission; 664 does not include execute permission. I'm going to close this ticket since the problem was determined to be due to wrong permissions on the user's system and problems specific to the user's network. -- Ticket URL: <https://trac.macports.org/ticket/49569#comment:12> MacPorts <https://www.macports.org/> Ports system for macOS