From: Simon Tournier <zimon.toutoune@gmail.com>
To: Timothy Washington <twashing@gmail.com>, Guix Devel <guix-devel@gnu.org>
Subject: Re: Howto reference a custom package from a manifest
Date: Sun, 21 May 2023 18:46:04 +0200 [thread overview]
Message-ID: <CAJ3okZ2yyZQNOT=g+4ym-L2m65F741x6_5EPa8kon5=aTGDMNg@mail.gmail.com> (raw)
In-Reply-To: <CAADtM-bc9FU6B+k5UaJctk3+T2aPO_z2edp=SM5LoZgd5JeNYA@mail.gmail.com>
Hi,
Please keep CC guix-devel.
On Sun, 21 May 2023 at 04:44, Timothy Washington <twashing@gmail.com> wrote:
> $ cat guix/packages/manifest.scm
> (define-module (guix packages manifest))
> (use-modules (gnu packages))
Well, I am not sure these two lines are required.
> building /gnu/store/x695f07186dwqpw2jk48b62p2s18f5ry-rust-rustscan-2.1.1.drv...
> \ 'build' phasebuilder for `/gnu/store/x695f07186dwqpw2jk48b62p2s18f5ry-rust-rustscan-2.1.1.drv' failed with exit code 1
It means your custom package rust-rustscan does not build.
Could you share your local file: ./guix/packages/shaka.scm containing
the definition of this custom package?
Cheers,
simon
next prev parent reply other threads:[~2023-05-21 17:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-18 6:51 Howto reference a custom package from a manifest Timothy Washington
2023-05-19 16:15 ` Simon Tournier
[not found] ` <CAADtM-bc9FU6B+k5UaJctk3+T2aPO_z2edp=SM5LoZgd5JeNYA@mail.gmail.com>
2023-05-21 16:46 ` Simon Tournier [this message]
2023-05-21 20:35 ` Timothy Washington
2023-05-22 8:41 ` issue with packaging 'rustscan' Simon Tournier
2023-05-22 9:56 ` Tobias Kortkamp
2023-05-22 20:21 ` Timothy Washington
2023-05-22 18:17 ` Howto reference a custom package from a manifest Kaelyn
2023-05-22 20:20 ` Timothy Washington
2023-05-23 16:39 ` Kaelyn
2023-05-24 20:25 ` Timothy Washington
2023-05-24 22:16 ` Kaelyn
2023-05-26 23:27 ` Timothy Washington
2023-05-23 16:54 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-05-24 20:10 ` Timothy Washington
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='CAJ3okZ2yyZQNOT=g+4ym-L2m65F741x6_5EPa8kon5=aTGDMNg@mail.gmail.com' \
--to=zimon.toutoune@gmail.com \
--cc=guix-devel@gnu.org \
--cc=twashing@gmail.com \
/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.