Closed jcs090218 closed 1 year ago
I don't think MELPA will build packages since it would face the same issue.
The commit that I pushed didn't fix the issue for you?
I mean you haven't pushed the commit to MELPA, so MELPA wouldn't update any packages. See the MELPA page, the latest update package is hypedrive 20230601.714 (I checked that yesterday, pretty sure it's stucked).
For me, JCS-ELPA grabs package-build from MELPA so no, JCS-ELPA is still broken.
Ah right, I thought I had not merged the faulty version into Melpa yet.
Thanks for letting me know!
Thank you! ;)
BTW, does MELPA have a system to inform maintainers that the server isn't building packages? Maybe that would help to reduce the downtime? Just a whim. ;)
I recently got this error after the latest three commits 6223cae00a2e6c77864caaa3c5f84330d0ef2b93, 4381b1d7b2141eb60a2b9d494180a52dc7ec71bd and 6e48df3ac055ab98219165de0780c7822682c2f4. 🤔
See full log https://github.com/jcs-emacs/jcs-elpa/actions/runs/5152804123/jobs/9279298809#step:6:18.