raimue at macports.org
Fri Sep 8 22:50:52 UTC 2017
On 2017-09-08 18:48, Daniel J. Luke wrote:
> One solution might be to separate the build/distfile mirroring from the portfile mirroring. You could probably even do that by running separate rsync's for those on your home connection and doing some QoS setup to depref the build uploads (so they wouldn't block portfile updates).
We have gone a almost a full year without distfile mirroring. We really
should get it back. If we cannot deploy it on Ryan's servers because of
the bandwidth congestion, let's find another solution.
Should we look into running the distfile mirroring job on braeburn, our
server that also hosts website, Trac, and mailing lists? It is a Linux
system, but we have done it this way previously. Other ideas?
Similarly, the jobs for updating the website, guide, and man pages have
all been written for the buildbot, but were never deployed...
>> We do currently have a single static IP with ports 80, 443, and 873 open for the buildbot web site and the rsync server. Although it is not entirely working at the moment, the server is also supposed to be sending emails on failed builds; my understanding is that sending mail from a dynamic address makes other servers more likely to classify the message as spam.
> it shouldn't if it's set up correctly (ie. to relay through a smarthost).
We could of course route the mails over braeburn. However, the mails for
macports-builds@ have stopped as well and there was not even a single
incoming connection from your static IP, so the current problem is not
related to spam checks at all.
More information about the macports-dev