On Sun, Feb 26, 2017 at 12:14 PM, Ryan Schmidt wrote: > > On Feb 26, 2017, at 12:26, Al Varnell wrote: >> Seem to be problems with the Seattle mirror again: >> >> $ sudo port -v selfupdate >> ---> Updating MacPorts base sources using rsync >> ############################################################################### >> >> This mirror is managed by Pacific Northwest National Labratory. >> It is located in Richland, WA. >> >> If you have any questions, or problems, please email: >> mirror at pnnl dot gov >> >> ############################################################################### >> >> @ERROR: Unknown module 'macports' >> rsync error: error starting client-server protocol (code 5) at >> /SourceCache/rsync/rsync-45/rsync/main.c(1398) [receiver=2.6.9] >> Command failed: /usr/bin/rsync -rtzv --delete-after >> rsync://sea.us.rsync.macports.org/macports/release/tarballs/base.tar >> /opt/local/var/macports/sources/sea.us.rsync.macports.org/macports/release/tarballs >> Exit code: 5 > > I think the only problem is that you're trying to access an rsync module > called "macports", and the Seattle mirror doesn't provide a module by that > name. > > According to https://trac.macports.org/wiki/Mirrors , we've never claimed > that they provide a module by that name. Consult that wiki page for the > correct settings to use for that mirror. > > It would be nice if the Seattle mirror would add a module called "macports", > since that is what we do on our primary server and recommend mirror operators > do as well. Mirror operators may learn more by reading > https://trac.macports.org/wiki/Mirroring .
Thanks. Looks like I forgot to uncomment "release/tarballs/base.tar" in macports.conf on one of my boot drives the last time I switched. -Al-
