From: Leo Famulari <leo@famulari.name>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 42410-done@debbugs.gnu.org
Subject: bug#42410: Copying nars between stores fails for packages with multiple outputs
Date: Tue, 21 Jul 2020 15:33:10 -0400 [thread overview]
Message-ID: <20200721193310.GA593@jasmine.lan> (raw)
In-Reply-To: <87blk8oolv.fsf@gnu.org>
On Tue, Jul 21, 2020 at 05:49:00PM +0200, Ludovic Courtès wrote:
> 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?
Yes, that must be it! Thanks for your reply and I'll re-open this ticket
if necessary.
prev parent reply other threads:[~2020-07-21 19:34 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
2020-07-21 19:33 ` Leo Famulari [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
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=20200721193310.GA593@jasmine.lan \
--to=leo@famulari.name \
--cc=42410-done@debbugs.gnu.org \
--cc=ludo@gnu.org \
/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).