all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Leo Famulari <leo@famulari.name>
Cc: 42410@debbugs.gnu.org
Subject: bug#42410: Copying nars between stores fails for packages with multiple outputs
Date: Tue, 21 Jul 2020 17:49:00 +0200	[thread overview]
Message-ID: <87blk8oolv.fsf@gnu.org> (raw)
In-Reply-To: <20200717204319.GA3588@jasmine.lan> (Leo Famulari's message of "Fri, 17 Jul 2020 16:43:19 -0400")

Hi,

Leo Famulari <leo@famulari.name> skribis:

> Exporting a nar and importing it on another machine only works when the
> package being built has a single output.

Note that “guix archive --export foo” only exports foo:out.  If you want
to export other outputs, you have to explicitly list them.

> I set up a signing-key on the sending machine, authorized it on the
> receiving machine, and successfully transferred some nars of
> single-output packages. I say they succeeded because `guix build
> --no-grafts foo` did not need to build foo after having imported the nar
> archive built on the other machine.

‘guix build’ starts building unless all the outputs of the package are
already in the store.

> However, it fails for packages with multiple outputs such as Syncthing
> and libsmf.

Could it be that you copied only one output of the package, and thus
‘guix build’ considered it had to build it because the other outputs
were missing?

Thanks,
Ludo’.




  reply	other threads:[~2020-07-21 15:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-17 20:43 bug#42410: Copying nars between stores fails for packages with multiple outputs Leo Famulari
2020-07-21 15:49 ` Ludovic Courtès [this message]
2020-07-21 19:33   ` Leo Famulari

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=87blk8oolv.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=42410@debbugs.gnu.org \
    --cc=leo@famulari.name \
    /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.