From: "Gábor Boskovits" <boskovits@gmail.com>
To: lainiwa@cock.li
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Cannot package a PyPI tool
Date: Sun, 16 Feb 2020 15:56:28 +0100 [thread overview]
Message-ID: <CAE4v=pg9EK8WZtVb56-o7kfZZRAz=Lj321Wjc9BzLQ6E1oDPEA@mail.gmail.com> (raw)
In-Reply-To: <ef4344ea643cfe172b46aa1fd41e6598@cock.li>
Hello,
<lainiwa@cock.li> ezt írta (időpont: 2020. febr. 16., Vas 15:31):
> Hello!
>
> I was playing around with Guix and I tried to package a termtosvg tool
> just for an exercise.
>
> I have a
> export GUIX_PACKAGE_PATH=~/guix-packages
> setting and I create my *.scm files in that directory.
>
> my-hello.scm from the documentation worked fine, however when I tried to
> package a more "real-world" example I got an error:
>
> ------------------------------
> name: python-termtosvg
> version: 1.1.0
> outputs: out
> Backtrace:
> 1 (primitive-load "/home/lain/.config/guix/current/bin/gu…")
> In guix/ui.scm:
> 1824:12 0 (run-guix-command _ . _)
>
> guix/ui.scm:1824:12: In procedure run-guix-command:
> error: python-lxml: unbound variable
> ------------------------------
>
> My python-termtosvg.scm content: https://pastebin.com/cenixFh7
>
> Can I somehow make Guix see python-lxml from the main channel (or maybe
> solve the problem in some other way)?
>
You should add the package modules providing the inputs into the
define-module form.
I.e. something like (gnu packages python).
You can find out the module of the package using guix package -s
packagename. It reports the location, and file names are mapped to the
modules.
I hope that helps.
Best regards,
g_bor
>
prev parent reply other threads:[~2020-02-16 14:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-16 14:25 Cannot package a PyPI tool lainiwa
2020-02-16 14:56 ` Gábor Boskovits [this message]
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='CAE4v=pg9EK8WZtVb56-o7kfZZRAz=Lj321Wjc9BzLQ6E1oDPEA@mail.gmail.com' \
--to=boskovits@gmail.com \
--cc=help-guix@gnu.org \
--cc=lainiwa@cock.li \
/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.