Opened 15 years ago

Closed 15 years ago

#6169 closed defect (fixed)

DarwinPorts 1.2 no longer supports RSYNC_PROXY

Reported by: bzhou@… Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: base Version: 1.0
Keywords: Cc:


After selfupdate to 1.2, DarwinPorts can no longer rsync across the firewall.

$ sudo port -d selfupdate DEBUG: Rebuilding the darwinports base system if needed. Synchronizing from rsync:// rsync: failed to connect to Operation timed out rsync error: error in socket IO (code 10) at /SourceCache/rsync/rsync-14/rsync/clientserver.c(93) DEBUG: Couldnt sync dports tree: sync failed doing rsync

while executing

"darwinports::selfupdate [array get global_options]" Error: /opt/local/bin/port: selfupdate failed: Couldnt sync dports tree: sync failed doing rsync

I also tried starting from scratch and it failed at the same stage. Rsync from the shell with RSYNC_PROXY set seems to work.

Attachments (1)

dptcl.diff (778 bytes) - added by blb@… 15 years ago.
Patch to darwinports.tcl

Download all attachments as: .zip

Change History (3)

comment:1 Changed 15 years ago by jberry@…

So RSYNC_PROXY is an environment variable?

DarwinPorts 1.2 now explicitly wipes the environment of variables it doesn't know.

If you really want RSYNC_PROXY to survive that attack, set the following in your /opt/local/etc/ ports.conf:

extra_env RSYNC_PROXY

Any variables in extra_env will not be wiped.

If you feel RSYNC_PROXY should be added the standard list of variables not to wipe, please file a bug report to that effect...

Changed 15 years ago by blb@…

Attachment: dptcl.diff added

Patch to darwinports.tcl

comment:2 Changed 15 years ago by jberry@…

Resolution: fixed
Status: newclosed

Patch applied. Thanks.

Note: See TracTickets for help on using tickets.