Hi mates! I am trying to install a program via MacPorts. MacPorts itself is installed correctly in version 1.400. I am using a MacBook ;), like many new users do ;). Well, when I try to install a port, I have to sync before. When I try to sync, I get the following error: port sync failed: sync failed doing rsync It doesn't mean much to me. I am sorry, but I am a new Mac User. To analyse these error, because I need darwinports ;), I installed a shareware called Port Authority, which is a GUI for MacPorts. It displays this error: Synchronizing from rsync://rsync.darwinports.org/dpupdate/dports rsync: failed to connect to rsync.darwinports.org: Operation timed out (60) rsync error: error in socket IO (code 10) at /SourceCache/rsync/ rsync-24.1/rsync/clientserver.c(94) Does anybody know how to fix this error? What is the problem? Yours, Mark
On May 6, 2007, at 07:08, Mark wrote:
port sync failed: sync failed doing rsync
[snip]
Synchronizing from rsync://rsync.darwinports.org/dpupdate/dports rsync: failed to connect to rsync.darwinports.org: Operation timed out (60) rsync error: error in socket IO (code 10) at /SourceCache/rsync/ rsync-24.1/rsync/clientserver.c(94)
Does anybody know how to fix this error? What is the problem?
Let's start by assuming that the problem is what it says it is: it can't connect to the rsync server. Are you on a network that prohibits traffic on the rsync port 873? Perhaps something in your firewall configuration?
Am 06.05.2007 um 16:42 schrieb Ryan Schmidt:
On May 6, 2007, at 07:08, Mark wrote:
port sync failed: sync failed doing rsync
[snip]
Synchronizing from rsync://rsync.darwinports.org/dpupdate/dports rsync: failed to connect to rsync.darwinports.org: Operation timed out (60) rsync error: error in socket IO (code 10) at /SourceCache/rsync/ rsync-24.1/rsync/clientserver.c(94)
Does anybody know how to fix this error? What is the problem?
Let's start by assuming that the problem is what it says it is: it can't connect to the rsync server. Are you on a network that prohibits traffic on the rsync port 873? Perhaps something in your firewall configuration?
Hi! Ah, now I understand the problem. Thank you ;). - Yes, I have to use a network, which prohibits to use port 873. I have to use a proxy server to connect to those services, which require this port, for example. Do you know how to configure MacPorts to connect via a proxy? I didn't find any ways to configure it. - And no, it is not the firewall-configuration. I deactivated it to test it. The problem is the network itself. Yours, Mark
Hi Mark,
- Yes, I have to use a network, which prohibits to use port 873. I have to use a proxy server to connect to those services, which require this port, for example. Do you know how to configure MacPorts to connect via a proxy? I didn't find any ways to configure it.
I'm pretty sure that there's no setting in MacPorts per se. Instead, try setting the RSYNC_PROXY environment variable (see the "Connecting to an rsync server" section of the rsync(1) man page). If that doesn't work, you could also try tunnelling the rsync connection over ssh, though I don't know whether or not this will work. To test this, add '--rsh="<ssh_or_path_to_ssh>" to the rsync_options line in $ {prefix}/etc/ports/ports.conf (see also "Connecting to an rsync server over a remote shell program" in the rsync(1) man page). You might also try running a local proxy to proxy connections to the network proxy, and see if you can tunnel that way. If none of the above work, you could see if you can check out the dports part of the trunk from svn [1] and using that as a local port tree by editing ${prefix}/etc/ports/sources.conf to add the path to which you checked out a working copy (before the rsync one). Keep in mind that this will mean: (a) that you will get warnings about having multiple port definitions (this isn't really a problem); (b) that you will need to update your svn working copy via the "svn update" command rather than "sudo port sync"; (c) you can't use this to automatically update the MacPorts base code (though it's not that much more difficult); and (d) you'll use more space than otherwise necessary, especially if you switch between using svn checkout and using port sync. I hope that this hasn't confused you. Feel free to ask any more questions you may have. Kind regards, Maun Suang [1] http://svn.macports.org/repository/macports/trunk/dports -- Boey Maun Suang (Boey is my surname) Email: boeyms@macports.org
On May 7, 2007, at 00:05, Boey Maun Suang wrote:
If none of the above work, you could see if you can check out the dports part of the trunk from svn [1] and using that as a local port tree by editing ${prefix}/etc/ports/sources.conf to add the path to which you checked out a working copy (before the rsync one). Keep in mind that this will mean: (a) that you will get warnings about having multiple port definitions (this isn't really a problem);
Not true, if your Subversion working copy is your only ports tree (comment out the rsync one).
(b) that you will need to update your svn working copy via the "svn update" command rather than "sudo port sync";
Not true; with MacPorts 1.4.3, "sudo port sync" will update ports trees which are Subversion working copies.
(c) you can't use this to automatically update the MacPorts base code (though it's not that much more difficult);
I do believe that's true. But you can keep a working copy of the latest tag of base, and switch to the new tag when a new version is released, and configure, make and sudo make install it yourself.
and (d) you'll use more space than otherwise necessary, especially if you switch between using svn checkout and using port sync.
Yes, a Subversion working copy will use a bit more than twice the space of a simple directory compared with rsync. That, at least, would be the rational explanation. Sadly, I see that my working copy of the ports tree weighs in at 161MB, while "svn export"ing that to a plain directory reduces it all the way down to 33MB. It hardly seems right that the working copy should be almost 5 times larger than the plain directory. But there we are. C'est la vie.
On 7.5.2007, at 9.35, Ryan Schmidt wrote:
On May 7, 2007, at 00:05, Boey Maun Suang wrote:
If none of the above work, you could see if you can check out the dports part of the trunk from svn [1] and using that as a local port tree by editing ${prefix}/etc/ports/sources.conf to add the path to which you checked out a working copy (before the rsync one). Keep in mind that this will mean: (a) that you will get warnings about having multiple port definitions (this isn't really a problem);
Not true, if your Subversion working copy is your only ports tree (comment out the rsync one).
(b) that you will need to update your svn working copy via the "svn update" command rather than "sudo port sync";
Not true; with MacPorts 1.4.3, "sudo port sync" will update ports trees which are Subversion working copies.
This is a small problem, however, because svn tree should be my territory. After sync (or selfupdate I am using more) svn tree is root-owned. Then I can't update the svn tree without changing the owner, which is done easily, though. This is conceptually an annoyance, anyhow, because my sandbox shouldn't be mixed with the system sandbox.
(c) you can't use this to automatically update the MacPorts base code (though it's not that much more difficult);
I do believe that's true. But you can keep a working copy of the latest tag of base, and switch to the new tag when a new version is released, and configure, make and sudo make install it yourself.
and (d) you'll use more space than otherwise necessary, especially if you switch between using svn checkout and using port sync.
Yes, a Subversion working copy will use a bit more than twice the space of a simple directory compared with rsync. That, at least, would be the rational explanation. Sadly, I see that my working copy of the ports tree weighs in at 161MB, while "svn export"ing that to a plain directory reduces it all the way down to 33MB. It hardly seems right that the working copy should be almost 5 times larger than the plain directory. But there we are. C'est la vie.
! ! Jyrki Wahlstedt ! skype:jyrkiwahlstedt ! http://www.wahlstedt.fi/jyrki/ ! ! Our life is no dream; but it ought to become one and perhaps will. ! PGP key ID: 0x139CC386 fingerprint: F355 B46F 026C B8C1 89C0 A780 6366 EFD9 139C C386
participants (4)
-
Boey Maun Suang
-
Jyrki Wahlstedt
-
Mark
-
Ryan Schmidt