Opened 13 years ago

Closed 13 years ago

#33560 closed defect (invalid)

selfupdate failing

Reported by: jcmaxwell_99@… Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: base Version: 2.0.4
Keywords: Cc:
Port:

Description (last modified by ryandesign (Ryan Carsten Schmidt))

on OS X 10.6.8 (macports 2.0.4 installed)
selfupdate reports 

DEBUG: MacPorts sources location: /opt/local/var/macports/sources/rsync.macports.org/release/base
--->  Updating MacPorts base sources using rsync
rsync: server sent "<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">" rather than greeting
rsync error: error starting client-server protocol (code 5) at /SourceCache/rsync/rsync-40/rsync/main.c(1398) [receiver=2.6.9]
shell command "/usr/bin/rsync -rtzv --delete-after --port=80 rsync://rsync.macports.org/release/base/ /opt/local/var/macports/sources/rsync.macports.org/release/base" returned error 5
DEBUG: Error synchronizing MacPorts sources: shell command failed (see log for details)
    while executing
"macports::selfupdate [array get global_options] base_updated"
Error: /opt/local/bin/port: port selfupdate failed: Error synchronizing MacPorts

Change History (3)

comment:1 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)

Component: ports → base
Description: modified (diff)

Well, that's an HTML DOCTYPE line. You've reached an HTTP server, instead of our rsync server. Why does it say "--port=80" there? rsync does not occur over port 80; HTTP does. Have you changed rsync_options or proxy_rsync in macports.conf?

comment:2 in reply to:  1 Changed 13 years ago by jcmaxwell_99@…

Replying to ryandesign@…:

Well, that's an HTML DOCTYPE line. You've reached an HTTP server, instead of our rsync server. Why does it say "--port=80" there? rsync does not occur over port 80; HTTP does. Have you changed rsync_options or proxy_rsync in macports.conf?

severe pilot error...removed the reference to port 80 and that fixed it. I was syncing the ports tree via svn for the longest time since I cannot use rsync at work, and consequently never had a need to fiddle with that before (although I must have at one time).

Thanks.

comment:3 Changed 13 years ago by mf2k (Frank Schima)

Resolution: → invalid
Status: new → closed
Note: See TracTickets for help on using tickets.