From: "Ludovic Courtès" <ludo@gnu.org>
To: "Mădălin Ionel Patrașcu" <madalinionel.patrascu@mdc-berlin.de>
Cc: 57077-done@debbugs.gnu.org
Subject: bug#57077: guix-jupyter fails a test
Date: Fri, 20 Jan 2023 12:24:07 +0100 [thread overview]
Message-ID: <877cxh8n54.fsf_-_@gnu.org> (raw)
In-Reply-To: <20220915163740.11672-1-madalinionel.patrascu@mdc-berlin.de> ("Mădălin Ionel Patrașcu"'s message of "Thu, 15 Sep 2022 18:37:40 +0200")
Hi Mădălin,
Mădălin Ionel Patrașcu <madalinionel.patrascu@mdc-berlin.de> skribis:
> Build drops warnings regarding 'guild' and the check phase does not
> have write permissions for its tests.
> [build]: Remove the warnings generated by the 'guild' by setting the
> "GUILE_AUTO_COMPILE" to 0.
> [check]: Set the homeless-shelter to /tmp for write permission.
I had completely overlooked this message of yours and committed just now
a similar fix in b60f3941b95dc5351e2336cf694480d099a91233. This is
embarrassing, sorry about that!
Do feel free to ping me or whoever last touched the package or the
relevant team¹ for the package when a patch of yours gets stuck.
The good news is that Guix-Jupyter is finally fixed. :-)
I hope it’s useful to you.
My apologies again, and thank you for your work!
Ludo’.
¹ https://guix.gnu.org/manual/devel/en/html_node/Teams.html
next prev parent reply other threads:[~2023-01-20 11:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-09 13:23 bug#57077: guix-jupyter fails a test Andreas Enge
2022-08-09 21:17 ` Ludovic Courtès
2022-09-08 19:35 ` Ludovic Courtès
2022-09-14 20:34 ` Ricardo Wurmus
2022-09-15 16:35 ` bug#57077: gnu: guix-jupyter: Fix build and check phase MadalinIonel.Patrascu
2022-09-15 16:37 ` bug#57077: [PATCH] " Mădălin Ionel Patrașcu
2023-01-20 11:24 ` Ludovic Courtès [this message]
2023-01-22 2:02 ` bug#57077: [ext] Re: bug#57077: guix-jupyter fails a test MadalinIonel.Patrascu
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=877cxh8n54.fsf_-_@gnu.org \
--to=ludo@gnu.org \
--cc=57077-done@debbugs.gnu.org \
--cc=madalinionel.patrascu@mdc-berlin.de \
/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.