#46193 closed defect (invalid)
Error synchronizing MacPorts sources: command execution failed
Reported by: | whiteexcaliber@… | Owned by: | skarulkar@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | server/hosting | Version: | |
Keywords: | Cc: | ||
Port: |
Description
I've got this error.
$ port -v selfupdate ---> Updating MacPorts base sources using rsync receiving file list ... done rsync: mkstemp "/opt/local/var/macports/sources/rsync.macports.org/release/tarballs/.base.tar.sWMs0z" failed: Permission denied (13) inflate returned -3 (19 bytes) rsync error: error in rsync protocol data stream (code 12) at /SourceCache/rsync/rsync-45/rsync/token.c(419) [receiver=2.6.9] rsync: connection unexpectedly closed (31 bytes received so far) [generator] rsync error: error in rsync protocol data stream (code 12) at /SourceCache/rsync/rsync-45/rsync/io.c(453) [generator=2.6.9] 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: 12 Error: Error synchronizing MacPorts sources: command execution failed Error: Follow http://guide.macports.org/#project.tickets to report a bug. Error: /opt/local/bin/port: port selfupdate failed: Error synchronizing MacPorts sources: command execution failed
Change History (4)
comment:1 follow-up: 2 Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)
Component: | ports → server/hosting |
---|---|
Owner: | changed from macports-tickets@… to skarulkar@… |
Version: | 2.3.3 |
comment:2 Changed 10 years ago by whiteexcaliber@…
Replying to ryandesign@…:
Is this problem repeatable or did it just happen once?
Thi s happens repeatedly.
comment:3 follow-up: 4 Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)
Resolution: | → invalid |
---|---|
Status: | new → closed |
Wait a moment, I see the error is "permission denied", and you show that you are not using "sudo" to run "port selfupdate", which you need to do.
sudo port -v selfupdate
comment:4 Changed 10 years ago by whiteexcaliber@…
Replying to ryandesign@…:
Wait a moment, I see the error is "permission denied", and you show that you are not using "sudo" to run "port selfupdate", which you need to do.
sudo port -v selfupdate
Ypu're right. It works.
Note: See
TracTickets for help on using
tickets.
Is this problem repeatable or did it just happen once?