melpa/package-build

cyclic-variable-indirection package-build-write-badge-images

jcs090218 opened this issue · 7 comments

I recently got this error after the latest three commits 6223cae, 4381b1d and 6e48df3. 🤔

Debugger entered--Lisp error: (cyclic-variable-indirection package-build-write-badge-images)
  set-default-toplevel-value(package-build-write-badge-images nil)
  custom-initialize-reset(package-build-write-badge-images (funcall #'(closure (t) nil "" nil)))
  custom-declare-variable(package-build-write-badge-images (funcall #'(closure (t) nil "" nil)) "When non-nil, write badge images alongside package..." :group package-build :type boolean)
  eval-buffer(#<buffer  *load*-543564> nil "/home/runner/work/jcs-elpa/jcs-elpa/.eask/28.2/elp..." nil t)  ; Reading at buffer position 6611
  load-with-code-conversion("/home/runner/work/jcs-elpa/jcs-elpa/.eask/28.2/elp..." "/home/runner/work/jcs-elpa/jcs-elpa/.eask/28.2/elp..." nil t)
  require(package-build)
  eval-buffer(#<buffer  *load*-401696> nil "/home/runner/work/jcs-elpa/jcs-elpa/.eask/28.2/elp..." nil t)  ; Reading at buffer position [20](https://github.com/jcs-emacs/jcs-elpa/actions/runs/5152804123/jobs/9279298809#step:6:21)63
  load-with-code-conversion("/home/runner/work/jcs-elpa/jcs-elpa/.eask/28.2/elp..." "/home/runner/work/jcs-elpa/jcs-elpa/.eask/28.2/elp..." t t)
  require(github-elpa nil t)

See full log https://github.com/jcs-emacs/jcs-elpa/actions/runs/5152804123/jobs/9279298809#step:6:18.

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. ;)