Bastien Guerry <b...@gnu.org> writes: >> What about the other approach I proposed? >> (where we export skipping errors first, upload, and then re-export, >> catching all errors this time just to trigger an email to notify about >> the failure). > > Yes, let's do this.
Ok. I added a new --debug command line argument to publish.sh and a new "check" task that will generate non-zero exit code yet uploading the successfully exported pages. https://git.sr.ht/~bzg/worg/commit/b38a1f08 https://git.sr.ht/~bzg/worg/commit/f049752b ... And we are (hopefully) done with a side line of the original bug report. The original problem was Cannot open load file: No such file or directory, ess So, there is still a problem with ESS installation. We may need to update the build manifest yet more. Probably "elpa-ess" is installed into some weird place, out of load-path. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at <https://orgmode.org/>. Support Org development at <https://liberapay.com/org-mode>, or support my work at <https://liberapay.com/yantar92>
