unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Chris Marusich <cmmarusich@gmail.com>
To: Pjotr Prins <pjotr.public12@thebird.nl>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: New ‘guix pull’ - guile-sqlite3 problem
Date: Thu, 19 Jul 2018 01:12:22 -0700	[thread overview]
Message-ID: <878t67iqzd.fsf@gmail.com> (raw)
In-Reply-To: <20180719072242.g2wrq4srtbxbdpmz@thebird.nl> (Pjotr Prins's message of "Thu, 19 Jul 2018 09:22:42 +0200")

[-- Attachment #1: Type: text/plain, Size: 1336 bytes --]

Pjotr Prins <pjotr.public12@thebird.nl> writes:

> guix environment guix will only work if the daemon is up-to-date
> (right?). I had to get that upgrade sorted, that was the pain. 

I think "guix environment guix" should drop you into an environment
where the guix package's inputs are available, regardless of what
version of the daemon you're using.  What matters most is the guix
package definition, since it determines the inputs.

Of course, using a version of guix (the package definition, or the
supporting Guile code) that is far removed in time from the Guix source
you're trying to compile will make it less likely to succeed.  I recall
having quite a hard time trying to compile Guix 0.14.0 from source using
a "guix environment guix" environment that was built by a Guix from an
old version, something around 0.10.0 or so.  Too much changed.

Likewise, using a guix-daemon from sufficiently far in the past or
future (compared to the guix client-side code you're running) might also
cause problems.  However, since the guix-daemon and the protocols it
uses change less frequently, it's less likely to cause problems.

> With regards to guile-sqlite3 it was a path that was missing. Maybe it
> got corrected in later versions and I was just unlucky.

Glad to hear you got it working!

-- 
Chris

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2018-07-19  8:12 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-09 10:16 New ‘guix pull’ Ludovic Courtès
2018-06-09 14:25 ` New ‘guix pull’ dosen’t update the guix manual in GuixSD 宋文武
2018-06-10 19:33   ` Ludovic Courtès
2018-06-11 11:27     ` 宋文武
2018-06-12 13:54       ` Ludovic Courtès
2018-07-08 17:31 ` New ‘guix pull’ Pjotr Prins
2018-07-12  9:35 ` Chris Marusich
2018-07-12 11:04   ` Pjotr Prins
2018-07-12 11:12     ` Pjotr Prins
2018-07-12 12:35       ` New ‘guix pull’ - guile-sqlite3 problem Pjotr Prins
2018-07-12 12:43         ` Pjotr Prins
2018-07-18  5:32         ` Chris Marusich
2018-07-19  7:22           ` Pjotr Prins
2018-07-19  8:12             ` Chris Marusich [this message]
2018-07-12 14:17     ` New ‘guix pull’ Ricardo Wurmus
2018-07-12 14:20       ` Pjotr Prins
2018-07-12 14:29         ` Ricardo Wurmus
2018-07-12 16:44           ` Pjotr Prins
2018-07-13  8:39             ` New ‘guix pull’ /root/.config/current/bin/guix: Permission denied Pjotr Prins
2018-07-13  9:08               ` Pjotr Prins
2018-07-13  9:48                 ` Pjotr Prins
2018-07-13  9:54                   ` Pjotr Prins
2018-07-13 12:04               ` Ludovic Courtès
2018-07-13 15:24                 ` Pjotr Prins
2018-07-13  8:41             ` New ‘guix pull’ Pjotr Prins
2018-10-14 18:17           ` Pjotr Prins
2018-10-15 10:14             ` Ludovic Courtès
2018-07-12 16:01   ` Ludovic Courtès
2018-07-12 20:52     ` Brett Gilio

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=878t67iqzd.fsf@gmail.com \
    --to=cmmarusich@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=pjotr.public12@thebird.nl \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).