From: Giovanni Biscuolo <g@xelera.eu>
To: guix-devel@gnu.org
Subject: plz is there a roadmap for a more resilient substitutes infrastructure?
Date: Fri, 02 Nov 2018 13:16:03 +0100 [thread overview]
Message-ID: <87wopv7jzw.fsf@roquette.mug.biscuolo.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1835 bytes --]
Ciao,
recently users and developers are facing hard to manage problems due to
the maintainance of hydra.gnu.org and its proxy mirror.hydra.gnu.org [1]
since 23 Oct 2018
unfortunately many recent reports from users in help-guix and guix-devel
mailing list clearly shows that berlin.guixsd.org it's still not a
solution, since several missing substitutes are forcing users to "build
the world" [2]
please is there a roadmap in GNU and/or Guix devel team to address this
problems?
GuixSD is now well known in the free software community, please
aknowledge that this king of problems are detrimental to project
reputation
given the prolonged issue, please also consider writing an *official*
blog post explaining the current situation and steps adopted to prevent
similar issues in the future
Me and many others would be very happy to help building a more resilient
substitutes infrastructure: just tell us how to do
for example:
1. is there a method to "replicate the whole store of an official server
(e.g. hydra.gnu.org once healed)" so we can just "guix publish" a
*complete* mirror? In this case a ready to use official
mirror-config.scm could be useful
2. is there an official mirrors directory users can look at when needed?
3. is there a plan to build a service similar to
http://httpredir.debian.org/? (I looked on the web but did not find any
reference to such plan)
ciao
Giovanni
[1] https://debbugs.gnu.org/cgi/bugreport.cgi?bug=33151
[2] peronally I'm trying to install a bare-bones.scm machine in a VM and
guix is compiling many many packages, including texlive... :-S (using
berlin.guixsd.org as substitute URL)
[3] https://www.gnu.org/software/guix/manual/en/html_node/Invoking-guix-publish.html
--
Giovanni Biscuolo
Xelera IT Infrastructures
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next reply other threads:[~2018-11-02 12:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-02 12:16 Giovanni Biscuolo [this message]
2018-11-02 21:04 ` plz is there a roadmap for a more resilient substitutes infrastructure? Pjotr Prins
2018-11-02 22:51 ` Julien Lepiller
2018-11-03 6:10 ` Pjotr Prins
2018-11-02 21:13 ` Devan Carpenter
2018-11-06 11:23 ` Ludovic Courtès
2018-11-06 11:31 ` Pierre Neidhardt
2018-11-11 18:56 ` Giovanni Biscuolo
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=87wopv7jzw.fsf@roquette.mug.biscuolo.net \
--to=g@xelera.eu \
--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).