[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: emacs-guix (upstream) needs more love: a survey of repositories, hom
From: |
Kaelyn |
Subject: |
Re: emacs-guix (upstream) needs more love: a survey of repositories, homepage and issues |
Date: |
Thu, 26 May 2022 23:15:34 +0000 |
Hello Gio'
On Thursday, May 26th, 2022 at 8:01 AM, Giovanni Biscuolo <g@xelera.eu> wrote:
> Hello Kaelyn and Ludo'
>
> thank you for your help!
>
> Kaelyn kaelyn.alexi@protonmail.com writes:
>
>
> [...]
>
> > > First, we need to cherry-pick relevant commits from gitlab.com. Any
> > > takers? If you Giovanni or anyone else is willing to help,
>
>
> I'd be really happy to help, I just saw Kaelyn was already working on
> this
>
> unfortunately I'm not the right person to maintain emacs-guix since my
> *-lisp foo is still Panda-style
>
> > > we can grant commit access so we share the work. Another way to help
> > > is by listing commits that should be applied.
> > >
> > > Volunteers?
> >
> > I'd be happy to help with the efforts! I just took a few minutes and
> > checked both repos out into a single working tree, and there aren't
> > many commits unique to each repository. The official savannah repo has
> > 5 commits since they diverged, with the 3 oldest looking like
> > variations of the 6 oldest in the gitlab repo. Likewise, not counting
> > the 6 just mentioned, there are 4 unique commits in the gitlab repo.
>
>
> how is your cherry-picking going?
>
> is there anything I can do to help?
I've attempted to cherry-pick the four gitlab commits (by interactively
rebasing the gitlab HEAD on the savannah HEAD and dropping the overlapping
commits) but haven't made progress beyond that. The rebase/cherry-pick was
pretty simple as there didn't seem to be conflicts. However, I keep getting
elisp errors about something having the wrong number of arguments, and I'm
still new enough to emacs that I don't know how to debug it or to get a useful
backtrace of where the error is coming from.
Basically it seems like the same error compiling any of the elisp files (at
least with emacs 27), but the errors are ignored by default and so installation
fails because all of the .elc files to be installed are missing. A sample of
the repeated error:
ELC elisp/guix-hash.elc
Wrong number of arguments: #[nil "ÁÂÃ \"Ä\")" [autoloads mapcan
guix-emacs-find-autoloads guix-emacs--non-core-load-path mapc #[(f) "Â\"" [f
load noerror] 3]] 3
("/gnu/store/wl48zzhf6gvvi7vml7w0yzg14ks4b0ls-profile/share/emacs/site-lisp/guix-emacs.elc"
. 1084) nil], 1
make[1]: [Makefile:1285: elisp/guix-hash.elc] Error 255 (ignored)
ELC elisp/guix-derivation.elc
Wrong number of arguments: #[nil "ÁÂÃ \"Ä\")" [autoloads mapcan
guix-emacs-find-autoloads guix-emacs--non-core-load-path mapc #[(f) "Â\"" [f
load noerror] 3]] 3
("/gnu/store/wl48zzhf6gvvi7vml7w0yzg14ks4b0ls-profile/share/emacs/site-lisp/guix-emacs.elc"
. 1084) nil], 1
make[1]: [Makefile:1285: elisp/guix-derivation.elc] Error 255 (ignored)
I wanted to at least make sure the package built with the included guix.scm
before figuring out how to send a pull request (or patch series) to a
savannah-hosted project, but that error has me stumped.
Cheers,
Kaelyn
>
> Thanks, Gio'
>
> [...]
>
> --
> Giovanni Biscuolo
>
> Xelera IT Infrastructures