Opened 19 years ago
Closed 19 years ago
#5103 closed defect (invalid)
port selfupdate does not use URL:port
Reported by: | deant@… | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | base | Version: | 1.0 |
Keywords: | Cc: | ||
Port: |
Description
Background: I need to proxy/tunnel sometimes to rsync from rsync.opendarwin.org. While some things work as expected by configuring port to use an alternate URL, (port sync and port install, for example), selfupdating port does not. For example, if I configure ports.conf and sources.conf to point to a different URL like this for example (real IP and port masked out):
pwd
/opt/local/etc/ports
grep "XXX.XXX.XXX.XXX:ZZZ" *
ports.conf:rsync_server XXX.XXX.XXX.XXX:ZZZ sources.conf:rsync://XXX.XXX.XXX.XXX:ZZZ/dpupdate/dports
Then port is smart enough most of the time to use the rsync URL I've configured, but selfupdate does not honor the alternate IP port. See below (notice how the sync at the beginning works). I don't grok tcl, but my guess from looking at the code is that sources.conf isn't being parsed to handle the protocol://address:port/path/to correctly.
port -d selfupdate
DEBUG: Rebuilding the darwinports base system if needed. Synchronizing from rsync://XXX.XXX.XXX.XXX:ZZZ/dpupdate/dports receiving file list ... done
sent 77 bytes received 183937 bytes 28309.85 bytes/sec total size is 10562695 speedup is 57.40 DEBUG: DarwinPorts base dir: /opt/local/var/db/dports/sources/rsync.XXX.XXX.XXX.XXX_dpupdate1/ base DEBUG: Setting user: root DarwinPorts base version 1.101 installed DEBUG: Updating using rsync rsync: failed to connect to XXX.XXX.XXX.XXX: Connection refused (61) rsync error: error in socket IO (code 10) at /SourceCache/rsync/rsync-20/rsync/clientserver.c(94) DEBUG: Error: rsync failed in selfupdate
while executing
"darwinports::selfupdate" Selfupdate failed: Error: rsync failed in selfupdate
Change History (1)
comment:1 Changed 19 years ago by deant@…
Resolution: | → invalid |
---|---|
Status: | new → closed |
Actually, port does indeed use the PORT in the URL of the form "protocol://server:PORT/pathto" I was being fooled by a user .portsrc overriding the system ports.conf file.