From: Nicolas Graves via Guix-patches via <guix-patches@gnu.org>
To: Hilton Chain <hako@ultrarare.space>
Cc: Katherine Cox-Buday <cox.katherine.e+guix@gmail.com>,
Liliana Marie Prikler <liliana.prikler@gmail.com>,
66298@debbugs.gnu.org, Andrew Tropin <andrew@trop.in>
Subject: [bug#66298] [PATCH] gnu: emacs-buttercup: Fix native comp tests with emacs-next.
Date: Mon, 02 Oct 2023 15:27:18 +0200 [thread overview]
Message-ID: <87ttr9i289.fsf@ngraves.fr> (raw)
In-Reply-To: <8734yt41md.wl-hako@ultrarare.space>
On 2023-10-02 21:04, Hilton Chain wrote:
> Hi Nicolas,
>
> On Mon, 02 Oct 2023 04:12:15 +0800,
> Nicolas Graves via Guix-patches via wrote:
>>
>> * gnu/packages/emacs-xyz.scm (emacs-buttercup): Add patch emacs-buttercup-fix-native-comp-pretty-test.
>> * gnu/packages/patches/emacs-buttercup-fix-native-comp-pretty-test.patch: Add
>> file.
>> ---
>
> With the patch applied, I'm getting the same error when without it from:
> $ guix build emacs-buttercup --with-input=emacs-minimal=emacs-next-minimal
>
> Is this true for you? 🤔
>
> Thanks
You're right Hilton, for some reason I thought it worked (I did put
emacs-next in native-inputs and propagated-inputs), but it seems that
when I try it your command, it doesn't work. I guess we'd better
revert the patch and continue to investigate.
--
Best regards,
Nicolas Graves
next prev parent reply other threads:[~2023-10-02 13:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-01 20:12 [bug#66298] [PATCH] gnu: emacs-buttercup: Fix native comp tests with emacs-next Nicolas Graves via Guix-patches via
2023-10-02 13:04 ` Hilton Chain via Guix-patches via
2023-10-02 13:27 ` Nicolas Graves via Guix-patches via [this message]
2023-10-03 13:03 ` Hilton Chain via Guix-patches via
2023-10-02 13:17 ` bug#66298: " Andrew Tropin
2023-10-03 19:07 ` [bug#66298] " Mekeor Melire
2023-10-18 20:21 ` [bug#66298] Fixed in emacs-buttercup 1.32 Ola Nilsson
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ttr9i289.fsf@ngraves.fr \
--to=guix-patches@gnu.org \
--cc=66298@debbugs.gnu.org \
--cc=andrew@trop.in \
--cc=cox.katherine.e+guix@gmail.com \
--cc=hako@ultrarare.space \
--cc=liliana.prikler@gmail.com \
--cc=ngraves@ngraves.fr \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.