Closed OJFord closed 1 year ago
Possibly related, xcaddy
seems to fail:
(I didn't kill it)
But I haven't previously built it successfully, so this could be an environment issue & red herring.
@OJFord Did your system run out of memory or something during the build? 🤔
@mholt Quite possibly yes - was a t4g.micro instance iirc. Worked around it in the end by switching to x86_64, not fixing the build; so I haven't tested the binary download again either.
Closing...
Because.. it was fixed?
@OJFord Yes, apparently. :man_shrugging: The link posted above by OP is now downloading the binary.
And as for your issue with xcaddy, the builder/compiler received a kill signal, which came from the system. Check dmesg
to see if it ran out of memory (OOM). Either way, there doesn't appear to be a problem we can do anything about here.
Yes ok does seem to be working now :+1:
I am OP btw, the xcaddy thing was just an attempt to narrow down a cause - I thought perhaps it was failing to build and that's why the download was unavailable (rather than giving say the last successful build).
Sorry, this seems like the wrong venue, I don't know where to report this - downloads (including on the website and by the experimental
caddy add-package
) are failing if I request this package.Works:
Doesn't:
Other packages (such as mholt/caddy-l4) seem fine, as do other architectures.