From: Tobias Geerinckx-Rice <me@tobias.gr>
To: Greg Hogan <code@greghogan.com>
Cc: guix-devel@gnu.org
Subject: Re: Offline build failure
Date: Fri, 11 Dec 2020 22:42:23 +0100 [thread overview]
Message-ID: <87y2i4j9z4.fsf@nckx> (raw)
In-Reply-To: <CA+3U0ZnxD-SKYk=h=RtWsWecRu_0iP4yZYQWU+XHGy9rN4iPgg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1543 bytes --]
Hullo Greg,
Greg Hogan 写道:
> If there is a better way to setup / configure / execute offline
> builds
> please let me know!
...yes :-)
> I am attempting an offline build without success. I have a Guix
> 1.2.0 node
> with internet access on which I download sources with transitive
> dependencies:
> $ guix build --sources=transitive tzdata > ~/transfer
OK.
> I then copy the files as root to a Guix 1.2.0 node without
> internet access
> (only local network access):
> # cat /home/<user>/transfer | xargs -n 1 -I{} scp -p {}
> <ip>:{}
Now you've basically reinvented ‘guix copy --to=<ip>’, but in a
way that won't update the store database in /var/guix/db. I'm
afraid that won't work.
Guix won't ‘see’ the files you copy to the remote store and will
consider them G to be C'd next time you run ‘guix gc’. Or in this
case:
> Guix starts downloading and the transferred file is gone!
Same thing.
> I'm lost as to
> why a new download attempt is made as the file data and
> timestamps match
> the original server.
If the file isn't registered in the database, the store item is
never considered valid. Guix doesn't (yet) care about the
data/timestamps at this point.
If there's a reason you can't/won't use ‘guix copy’, you might
work around that by copying each file in ~/transfer to, say,
<ip>:/tmp/staging (instead of <ip>:/gnu/store), then running ‘guix
download /tmp/staging/<file>...’ on the remote host.
Kind regards,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2020-12-11 21:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-11 21:11 Offline build failure Greg Hogan
2020-12-11 21:42 ` Tobias Geerinckx-Rice [this message]
2020-12-14 19:33 ` Greg Hogan
2020-12-15 2:47 ` Mark H Weaver
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=87y2i4j9z4.fsf@nckx \
--to=me@tobias.gr \
--cc=code@greghogan.com \
--cc=guix-devel@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).