From: Leo Famulari <leo@famulari.name>
To: 白い熊@相撲道 <help-guix_gnu.org@sumou.com>
Cc: help-guix@gnu.org
Subject: Re: Export archive and import it on another machine
Date: Thu, 18 Feb 2016 17:34:52 -0500 [thread overview]
Message-ID: <20160218223452.GB9390@jasmine> (raw)
In-Reply-To: <C818AB18-E027-44D0-9061-4E01D98F5329@sumou.com>
On Thu, Feb 18, 2016 at 08:01:44PM +0000, 白い熊@相撲道 wrote:
> I'm trying to export Libreoffice from one PC and import it on another one — the reason I'm doing this is that with the latest git checkout when I try to install it on a PC with a newly installed GuixSD it keeps building it from source and failing.
>
> Anyhow, on the machine that I have it installed I ran:
>
> # guix archive --generate-key
> $ guix archive --export -r /gnu/store/hash...libreoffice-5.0.3.2 > libreoffice-5.0.3.2.nar
>
> Then copied the nar and /etc/guix/signing-key.pub to the other PC.
>
> There I ran:
>
> # guix archive --authorize < signing-key.pub
> $ guix archive --import < libreoffice-5.0.3.2.nar
>
> The last command fails with:
>
> guix archive: error: build failed: program `guix-authenticate' failed with exit code 1
>
> What am I doing wrong?
Hm, I'm not sure. Are you sure the source machine's public key is in
/etc/guix/acl?
>
> Side question — why is it building Libreoffice from source on “guix package -i libreoffice”? Recipe there, but not built on Hydra? How can I install an earlier already—built version?
Most likely for this reason:
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=22653
You can install an earlier version by checking out a commit in the Guix
git repo from before Vigra broke, and building based on that commit [0].
When building Guix from git, be sure to pass the correct value to
./configure --localstatedir=. Most likely it is '/var'.
[0]
https://www.gnu.org/software/guix/manual/guix.html#Building-from-Git
> --
> 白い熊@相撲道
>
next prev parent reply other threads:[~2016-02-18 22:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-18 20:01 Export archive and import it on another machine 白い熊@相撲道
2016-02-18 22:34 ` Leo Famulari [this message]
2016-02-19 9:42 ` 白い熊@相撲道
2016-02-19 17:06 ` Leo Famulari
2016-02-20 11:25 ` 白い熊@相撲道
2016-02-20 12:50 ` Leo Famulari
2016-02-27 13:01 ` Ricardo Wurmus
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=20160218223452.GB9390@jasmine \
--to=leo@famulari.name \
--cc=help-guix@gnu.org \
--cc=help-guix_gnu.org@sumou.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).