I can’t find a ticket. Is there one I’m missing, or should I make one? Thanks, -Greg
> On Jan 10, 2017, at 11:23 AM, Ryan Schmidt <[email protected]> wrote: > >> >> On Jan 10, 2017, at 10:13, Gregory Allen <[email protected]> wrote: >> >> I’ve noticed a number of issues with the distfiles repo/mirrors over the >> past few months. After the ports migration to git, a number of packages >> don’t make it into the distfiles mirrors. That causes issues for us behind a >> firewall, where we depend on distfiles. I’ve had to manually find and >> download the distfiles for some packages to install or update. >> >> For example: mercurial is at 4.0.2 in the ports repo, but the distfiles >> mirror stopped at 4.0.tar.gz. This particular package is far from the only >> one. Right now, this is my list of ports that I can’t update: mercurial >> p5.24-io-socket-ssl p5.24-net-http p5.24-net-ssleay py27-pyqt4 >> >> Are these issues with individual packages? Is distfiles deprecated (I hope >> not)? Is this an issue with the build bots? What can I do to help? > > We have not yet brought automatic distfile mirroring online on the new server > after moving away from macOS forge. I've manually added a few files to the > server since then.
smime.p7s
Description: S/MIME cryptographic signature
