This was a problem with the pkg-build service, now fixed (commit
bf76ced8ba in the Racket repo).
The problem caused the download of Pollen on the build machine to fail,
which caused the installation attempt on the network-isolated machine
to fail (i.e,. it shouldn't have needed to contact github.c
I don't know if that's a separate error. I've assumed that it's a side effect
of the build failing (= no docs end up where they're expected to be)
On Saturday, August 1, 2015 at 9:02:43 AM UTC-7, Andrew Gwozdziewycz wrote:
> Possibly related? http://pkg-build.racket-lang.org/doc/pollen fails wit
Possibly related? http://pkg-build.racket-lang.org/doc/pollen fails with a 403
forbidden. Maybe some s3 permissions changed?
On August 1, 2015 8:54:11 AM PDT, Matthew Butterick wrote:
>For the last couple of days my pollen builds have failed with this
>"connection failed" error. I don't see any
For the last couple of days my pollen builds have failed with this "connection
failed" error. I don't see any other packages failing to download from GitHub,
suggesting it's my fault. OTOH the supposedly defective URL works fine, so I'm
not sure how to make the build server happier.
Downloading
4 matches
Mail list logo
