[MacPorts] #72298: selfupdate fails but resources claimed inaccessible are accessible

[MacPorts]

#72298: selfupdate fails but resources claimed inaccessible are accessible
---------------------------------+--------------------
 Reporter:  vitaprimo            |      Owner:  (none)
     Type:  defect               |     Status:  new
 Priority:  Low                  |  Milestone:
Component:  base                 |    Version:  2.10.5
 Keywords:  catalina selfupdate  |       Port:
---------------------------------+--------------------
 I just installed Catalina from scratch (the machine was using Fedora 41
 before it), I got the Xcode CLI tools using the proper installer, which I
 already had as a dmg on the network (EULAs and all that are accepted
 ''before'' installation), and finally I installed MacPorts.

 I had no issues with any of it, until it was time to actually use it that
 I couldn't, or rather ''can't'' get the repos synced. I get a connection
 refused error, but if I go to the [only complete] address on the browser
 or fetch it using `curl` right in the same terminal, it does work. The
 other URL that's missing a resource (or the URI, I guess) at the end, also
 works; in the browser it shows one of those Apache's httpd-like directory
 listings typical of repos seen on a browser.

 In the output I found the address to report it and in them some
 instructions about what to check first, in hindsight those might've been
 meant for a specific port — not the client itself — though, couldn't hurt
 in any case. I'm attaching the terminal's I/O below (as text. No files):
 {{{
 [Sat05 at 21:52:02][v at vterminal:~] $〉pkgutil --pkg-
 info=com.apple.pkg.{CLTools_Executables,CLTools_Base,DeveloperToolsCLI,DeveloperToolsCLILeo}
 2>/dev/null | sed -n 's/^version: //p'
 12.4.0.0.1.1610135815
 [Sat05 at 21:52:14][v at vterminal:~] $〉sudo -s

 The default interactive shell is now zsh.
 To update your account to use zsh, please run `chsh -s /bin/zsh`.
 For more details, please visit https://support.apple.com/kb/HT208050.
 [Sat05 at 21:53:36][root at vterminal:~] #〉port clean --all
 Can't map the URL 'file://.' to a port description file ("Could not find
 Portfile in /Users/v").
 Please verify that the directory and portfile syntax are correct.
 To use the current port, you must be in a port's directory.
 [Sat05 at 21:53:37][root at vterminal:~] #〉port -v selfupdate
 --->  Checking for newer releases of MacPorts
   % Total    % Received % Xferd  Average Speed   Time    Time     Time
 Current
                                  Dload  Upload   Total   Spent    Left
 Speed
 100    63  100    63    0     0     48      0  0:00:01  0:00:01 --:--:--
 48
 MacPorts base version 2.10.5 installed,
 MacPorts base version 2.10.5 available.
 --->  MacPorts base is already the latest version
 --->  Updating the ports tree
 Synchronizing local ports tree from
 rsync://rsync.macports.org/macports/release/tarballs/ports.tar.gz
 rsync: failed to connect to rsync.macports.org: Connection refused (61)
 rsync error: error in socket IO (code 10) at
 /AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/rsync/rsync-54.120.1/rsync/clientserver.c(106)
 [receiver=2.6.9]
 Command failed: /usr/bin/rsync -rtzvl --delete-after
 --include=/ports.tar.gz --include=/ports.tar.gz.rmd160 --exclude=*
 rsync://rsync.macports.org/macports/release/tarballs/
 /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/remote
 Exit code: 10
 Error: Synchronization of the local ports tree failed doing rsync
 Error: Couldn't sync the ports tree: Synchronization of 1 source failed
 Error: Follow https://guide.macports.org/#project.tickets if you believe
 there
 is a bug.
 Error: /opt/local/bin/port: port selfupdate failed: Couldn't sync the
 ports tree: Synchronization of 1 source failed
 [Sat05 at 22:18:27][root at vterminal:~] #〉curl -LO
 rsync.macports.org/macports/release/tarballs/ports.tar.gz
   % Total    % Received % Xferd  Average Speed   Time    Time     Time
 Current
                                  Dload  Upload   Total   Spent    Left
 Speed
 100   325  100   325    0     0    868      0 --:--:-- --:--:-- --:--:--
 866
 100 36.1M  100 36.1M    0     0  4302k      0  0:00:08  0:00:08 --:--:--
 6170k
 [Sat05 at 22:21:33][root at vterminal:~] #〉
 }}}

 My firewall is very strict, all services such as DNS, email or time are
 served internally thus it really only needs to allow two ports of the TCP
 protocol. It does it in a per-client basis provided they don't match
 preemptive DNS-/reputation/ASN-based blocklists and default denies
 everything else, that said, I already verified the files are accessible
 right on the very same system. Because it says it's using `rsync` I was
 worried about port 22, or the other ''port 5-'' or ''8-hundred-something''
 used with the rsync daemon. I installed Little Snitch to be sure and I
 have found no evidence of it so far.

 I don't know what else to test but one more thing that may be worth
 noting: my system is running with SIP disabled, GateKeeper disabled
 (`spctl --master-disable`) and runs with the system disk (`/` volume)
 mounted writable (it's the reason why I'm not using a newer macOS.)

 Thank you for your time.

-- 
Ticket URL: <https://trac.macports.org/ticket/72298>
MacPorts <https://www.macports.org/>
Ports system for macOS