unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Kaelyn <kaelyn.alexi@protonmail.com>
To: Giovanni Biscuolo <g@xelera.eu>
Cc: "Ludovic Courtès" <ludo@gnu.org>,
	guix-devel@gnu.org,
	"GNU Guix maintainers" <guix-maintainers@gnu.org>
Subject: Re: emacs-guix (upstream) needs more love: a survey of repositories, homepage and issues
Date: Thu, 26 May 2022 23:15:34 +0000	[thread overview]
Message-ID: <tlEO8FfBiCpMU0MSuKlxARgTEgRZPpef-lpS-K5uAsyEE2g9t7mEClR8vPjccUIY6xXMH8nrvzN-YP-X44D6aPJsmvEjOcz7bl_gK1_1abE=@protonmail.com> (raw)
In-Reply-To: <87pmk0mj75.fsf@xelera.eu>

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


  reply	other threads:[~2022-05-26 23:16 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-27 13:16 emacs-guix (upstream) needs more love: a survey of repositories, homepage and issues Giovanni Biscuolo
2022-04-27 14:01 ` John Soo
2022-04-27 15:31   ` Ryan Prior
2022-04-28 16:31   ` Giovanni Biscuolo
2022-04-28  8:08 ` Ludovic Courtès
2022-04-28 16:27   ` Giovanni Biscuolo
2022-04-29 10:12   ` zimoun
2022-05-23 14:39   ` Ludovic Courtès
2022-05-23 15:36     ` Kaelyn
2022-05-26 15:01       ` Giovanni Biscuolo
2022-05-26 23:15         ` Kaelyn [this message]
2022-05-27  6:32           ` Giovanni Biscuolo
2022-05-26 20:40       ` Théo Maxime Tyburn
2022-05-27  6:45         ` Giovanni Biscuolo
2022-05-27  9:21           ` Théo Maxime Tyburn
2022-09-02 16:13             ` Simon Streit
2022-10-06 14:00               ` Ludovic Courtès
2022-10-26 11:24                 ` Théo Tyburn
2022-05-30 15:33       ` Ludovic Courtès
2022-06-03 22:04         ` Théo Maxime Tyburn
2022-06-07 17:42         ` Kaelyn
2022-06-08 11:15           ` Kaelyn

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='tlEO8FfBiCpMU0MSuKlxARgTEgRZPpef-lpS-K5uAsyEE2g9t7mEClR8vPjccUIY6xXMH8nrvzN-YP-X44D6aPJsmvEjOcz7bl_gK1_1abE=@protonmail.com' \
    --to=kaelyn.alexi@protonmail.com \
    --cc=g@xelera.eu \
    --cc=guix-devel@gnu.org \
    --cc=guix-maintainers@gnu.org \
    --cc=ludo@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).