From: Julien Lepiller <julien@lepiller.eu>
To: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
Cc: help-guix@gnu.org
Subject: Re: How to create a substitute server with substitutes that failed?
Date: Wed, 26 Aug 2020 13:00:56 -0400 [thread overview]
Message-ID: <1A27BB06-5667-4602-960E-4A29BD425716@lepiller.eu> (raw)
In-Reply-To: <87ft89wflv.fsf@web.de>
guix build <package> will output all the store names for the outputs of <package> (usually only one). The hash in the directory names is what you want as the narinfo filename.
Le 26 août 2020 12:12:44 GMT-04:00, "Dr. Arne Babenhauserheide" <arne_bab@web.de> a écrit :
>
>Julien Lepiller <julien@lepiller.eu> writes:
>
>> I suppose, but that's going to be a bit of work. I'm not very
>knowledgeable on this part of guix. I think you'll need to generate a
>narinfo and a nar for each store item you want to be available. Maybe
>you can run guix publish locally and mirror the files it serves on your
>server?
>
>That sounds like a viable option.
>
>> You'll need to publish /<store hash of output>.narifo and the other
>files it references (the nar archives themselves).
>
>So I only need a way to get all the hashes referenced for a given
>package. Do you know the command for that?
>
>> So you'd download them from localhost and send them to your server.
>Your guix daemon must trust the builder's public key, or the substitute
>will not be downloaded.
>>
>> Le 26 août 2020 10:56:26 GMT-04:00, "Dr. Arne Babenhauserheide"
><arne_bab@web.de> a écrit :
>>>Julien Lepiller <julien@lepiller.eu> writes:
>>>> The best would be to run "guix publish" on your server, as it will
>>>allow others to use your server as a substitute server, instead of
>>>having to manually download archives of the package and dependencies.
>>>Thank you for your answer!
>>>
>>>Is it possible to do the equivalent of guix publish on a dumb server?
>>>
>>>The webhosts I have are pretty dumb servers that definitely have no
>>>Guix, and I have no root-access (and currently don’t want it, because
>I
>>>don’t like the maintenance burden that comes with it).
>
>
>--
>Unpolitisch sein
>heißt politisch sein
>ohne es zu merken
next prev parent reply other threads:[~2020-08-26 17:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87r1rtwtes.fsf@web.de>
2020-08-26 11:18 ` How to create a substitute server with substitutes that failed? Dr. Arne Babenhauserheide
2020-08-26 12:07 ` Julien Lepiller
2020-08-26 14:56 ` Dr. Arne Babenhauserheide
2020-08-26 15:26 ` Julien Lepiller
2020-08-26 16:12 ` Dr. Arne Babenhauserheide
2020-08-26 17:00 ` Julien Lepiller [this message]
2020-08-26 20:47 ` Christopher Baines
2020-08-27 0:22 ` Dr. Arne Babenhauserheide
2020-08-27 14:10 ` zimoun
2020-08-27 20:32 ` Dr. Arne Babenhauserheide
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=1A27BB06-5667-4602-960E-4A29BD425716@lepiller.eu \
--to=julien@lepiller.eu \
--cc=arne_bab@web.de \
--cc=help-guix@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.
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).