unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
To: help-guix@gnu.org
Subject: Re: How to create a substitute server with substitutes that failed?
Date: Wed, 26 Aug 2020 13:18:15 +0200	[thread overview]
Message-ID: <87o8mxwt8o.fsf@web.de> (raw)
In-Reply-To: <87r1rtwtes.fsf@web.de>

[-- Attachment #1: Type: text/plain, Size: 913 bytes --]


Hi,

I’d like to create a small server that provides substitutes for packages
for which I often have to build a fallback (mostly ungoogled Chromium).

How can I do that? Is there already a simply way?

I tried guix copy, but without luck:

$ LANG=C guix copy ungoogled-chromium --to=guixtmp@localhost
guix copy: error: failed to connect to `#<input-output: channel (open)7effb4657a80>': Protocol error

What I want is just to put the required substitute archives on a server
for others to download. Ungoogled Chromium takes so long that only one
person should ever have to build it (and I need it for work, so I can be
that one person).

It would be ideal if I could put it on a dumb public host with only
HTTPS access and FTP for upload (since I already have that and it has
unlimited bandwidth).

Best wishes,
Arne


-- 
Unpolitisch sein
heißt politisch sein
ohne es zu merken

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 1076 bytes --]

       reply	other threads:[~2020-08-26 11:55 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 ` Dr. Arne Babenhauserheide [this message]
2020-08-26 12:07   ` How to create a substitute server with substitutes that failed? 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
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=87o8mxwt8o.fsf@web.de \
    --to=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).