Re: NonGNU ELPA work

[Philip Kaludercic]

Stefan Monnier <monnier@iro.umontreal.ca> writes:

>> Some further testing indicated that the issue only arose when no
>> origin/elpa/... branch could be found on the remote target. As I had
>> unintentionally pushed a few branches a few days ago, I could test and
>> see that these were being build as intended.
>
> Hmm... I just tried here to add
>
>      ("lua-mode"              :url "https://github.com/immerrr/lua-mode/";
>       :ignored-files ("test" "travis" "init-tryout.el"))
>
> to `elpa-packages` in my clone of nongnu, and then I did
>
>     make fetch/lua-mode
>     make build/lua-mode
>
> and it "worked for me".  I tried re-running `make build/lua-mode`
> a second time (after deleting the tarballs) and again it worked:
>
>     % make build/lua-mode
>     emacs --batch -l /home/monnier/src/emacs/nongnu/admin/elpa-admin.el     \
>              -f elpaa-batch-make-one-package lua-mode
>     Updating worktree in "/home/monnier/src/emacs/nongnu/packages/lua-mode/"
>     Updated lua-mode: fatal: No remote for the current branch.
>     
>     Warning: lm-maintainer is obsolete!
>     Built new package archive-devel/lua-mode-20210802.0.20210802.174715.tar!
>     Built new package archive/lua-mode-20210802.tar!
>     %

I just tried it out, and it seems that this issue seems to resolve
itself, after making sync/lua-mode.

> Indeed I also see the "No remote for the current branch" error
> message, but it doesn't prevent the production of the tarballs.

So the package specifications should all be ok?

>         Stefan

-- 
        Philip Kaludercic