Changes between Initial Version and Version 1 of Ticket #50168


Ignore:
Timestamp:
Dec 29, 2015, 5:41:15 PM (8 years ago)
Author:
ryandesign (Ryan Carsten Schmidt)
Comment:

Why is the rsync connection going through an http proxy? Is that normal / is that supposed to work? I've never heard of that.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #50168

    • Property Component changed from ports to base

  • Ticket #50168 – Description

    initial v1  
    11Greetings. When I try to self update ports, I receive and HTTP error message:
    22
     3{{{
    34[09:45 user@host ~] > sudo port -v selfupdate
    45--->  Updating MacPorts base sources using rsync
    … …  
    1112Error: /opt/local/bin/port: port selfupdate failed: Error synchronizing MacPorts sources: command execution failed
    1213sent 36 bytes  received 69 bytes  70.00 bytes/sec
     14}}}
    1315
    1416The rsync command works outside of the selfupdate:
    1517
     18{{{
    1619[09:45 user@host-mitll ~] > 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
    1720
    1821receiving file list ... done
    1922total size is 27013120  speedup is 257267.81 `
    20 
     23}}}
    2124
    2225I am behind a proxy:
    2326
     27{{{
    2428[09:52 user@host-mitll ~] > sudo env | grep http
    2529http_proxy=http://xxx.xxx.xxx.xxx:8080
    2630
    2731https_proxy=http://xxx.xxx.xxx.xxx:8080
    28 
     32}}}
    2933
    3034