From: Marius Bakke <mbakke@fastmail.com>
To: sirgazil <sirgazil@zoho.com>, Guix Help <help-guix@gnu.org>
Subject: Re: Appropriate way to use Guix API from a Guile program
Date: Thu, 21 May 2020 14:44:58 +0200 [thread overview]
Message-ID: <878shla245.fsf@devup.no> (raw)
In-Reply-To: <17234059da3.b5e01d1e8240.9032082708652182693@zoho.com>
[-- Attachment #1: Type: text/plain, Size: 1401 bytes --]
sirgazil <sirgazil@zoho.com> writes:
> Hi,
>
> I use Guix's GNU system.
>
> I had written a Guile script that called Guix procedures to manipulate profiles. I put it in a Guix package in a custom channel and installed it. It used to work, but now it fails with an error I can also reproduce when trying to do something similar from a Guile REPL. For instance:
>
> ★★★★★★★★★★★★★★★★★★★★
> $ mkdir profile-x
> $ guile
> GNU Guile 3.0.2
> [...]
> scheme@(guile-user)> (use-modules (guix scripts package))
> scheme@(guile-user)> (guix-package "-m" "manifest.scm" "-p" "profile-x/profile-x")
> error: glibc-bootstrap-system-2.2.5.patch: patch not found
> ★★★★★★★★★★★★★★★★★★★★
There are a couple of things going on here. Calling the Guix APIs from
Guile will use the 'system-installed' Guix, unless you have fiddled with
GUILE_LOAD_PATH.
You can use 'guix repl' to use the _current_ Guix instead (the one
obtained with 'guix pull'), where this problem has been fixed.
The system-installed Guix in turn fails because of a bug that was fixed
in 179e6c524ae4957e6ace83f72a5651767f786ca4, and ultimately
977f478090fd96e73463efb67c56fb32f28828bd which updates the 'guix'
package to include the fix. If you reconfigure on a recent Guix, the
missing patch error should go away.
Hope this helps!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2020-05-21 12:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-20 21:38 Appropriate way to use Guix API from a Guile program sirgazil
2020-05-21 12:31 ` Efraim Flashner
2020-05-21 12:44 ` Marius Bakke [this message]
2020-05-21 13:25 ` sirgazil
2020-05-21 20:43 ` sirgazil
2020-05-21 20:52 ` Marius Bakke
2020-05-21 22:28 ` sirgazil
2020-05-21 23:02 ` zimoun
2020-05-22 7:43 ` Konrad Hinsen
2020-05-22 8:14 ` zimoun
2020-05-26 8:25 ` Konrad Hinsen
2020-05-26 16:00 ` Konrad Hinsen
2020-05-22 8:56 ` Alex Sassmannshausen
2020-05-22 14:28 ` sirgazil
2020-05-22 13:52 ` sirgazil
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=878shla245.fsf@devup.no \
--to=mbakke@fastmail.com \
--cc=help-guix@gnu.org \
--cc=sirgazil@zoho.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.
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).