#41272: problem with selfupdate ------------------------+-------------------------------- Reporter: pnewell@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.2.1 Resolution: | Keywords: Port: | ------------------------+-------------------------------- Changes (by larryv@…): * cc: pnewell@… (removed) * keywords: selfupdate => * component: ports => base Old description:
I am getting an error that I do not understand how to fix or get around. I looked in the existing issues and found one that involved rsync, but the error message was totally different. I do want to acknowledge that I am new to MacPorts and may be missing "the obvious" as it isn't obvious to me
Here is the output from my attempt to selfupdate:
+++ START +++
yzma:~ paul$ 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.uTJd0g" failed: Permission denied (13) inflate returned -3 (140 bytes) rsync error: error in rsync protocol data stream (code 12) at /SourceCache/rsync/rsync-42/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-42/rsync/io.c(452) [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 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 yzma:~ paul$
+++ END +++
This has worked in the past and, from my newbie POV, it sure looks like my system can't connect with your update given some issue with rsync on my/your/both ends
Thanks for help, Paul
New description: I am getting an error that I do not understand how to fix or get around. I looked in the existing issues and found one that involved rsync, but the error message was totally different. I do want to acknowledge that I am new to MacPorts and may be missing "the obvious" as it isn't obvious to me Here is the output from my attempt to selfupdate: +++ START +++ {{{ yzma:~ paul$ 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.uTJd0g" failed: Permission denied (13) inflate returned -3 (140 bytes) rsync error: error in rsync protocol data stream (code 12) at /SourceCache/rsync/rsync-42/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-42/rsync/io.c(452) [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 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 yzma:~ paul$ }}} +++ END +++ This has worked in the past and, from my newbie POV, it sure looks like my system can't connect with your update given some issue with rsync on my/your/both ends Thanks for help, Paul -- Comment: Did you intend to run `sudo port selfupdate` instead of `port selfupdate`? {{{ rsync: mkstemp "/opt/local/var/macports/sources/rsync.macports.org/release/tarballs/.base.tar.uTJd0g" failed: Permission denied (13) }}} -- Ticket URL: <https://trac.macports.org/ticket/41272#comment:1> MacPorts <http://www.macports.org/> Ports system for OS X