From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp2 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms11 with LMTPS id f7ZjGGjPxV4gTgAA0tVLHw (envelope-from ) for ; Thu, 21 May 2020 00:46:32 +0000 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp2 with LMTPS id 6HHJE2jPxV6pcQAAB5/wlQ (envelope-from ) for ; Thu, 21 May 2020 00:46:32 +0000 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 9B556940363 for ; Thu, 21 May 2020 00:46:31 +0000 (UTC) Received: from localhost ([::1]:47574 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jbZLy-0004rY-Ee for larch@yhetil.org; Wed, 20 May 2020 20:46:30 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:39736) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jbZLq-0004rS-2O for guix-devel@gnu.org; Wed, 20 May 2020 20:46:22 -0400 Received: from mail-lj1-x242.google.com ([2a00:1450:4864:20::242]:44019) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1jbZLo-0001VY-ND for guix-devel@gnu.org; Wed, 20 May 2020 20:46:21 -0400 Received: by mail-lj1-x242.google.com with SMTP id q2so6095990ljm.10 for ; Wed, 20 May 2020 17:46:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=AkPG4PaohADnuYXiFHVXNba0kTPlMIjmLECIatpDfu0=; b=VKCkoHb4+u4uLDH98yJPoJ/vRCGo6WLbwrBgfsFtqn1ITqLv7tylXX//y9hZNIA/Nm MMMBek/9TPd8InZCEudNwfj94E7F6Dtxvf3/e3o3EIV6MYCLiktSiBlS1uA484kp3xjH L7Zu47MnYg2Xgse18ilP2G5y8Olmbqk8Zhm5C/0zjYX8q/bVFZBq4XqsvBKHsyF//U74 iNOxhhFrW2IV3KE+GekEoFmhFCZglgFWLmdtF/tiBc8FibIs9xg0A13u9B6ySqa/jACp bpt7/0dl/V5fvhiX55qXCRYCBNXWtzL7wnJtIvNbtuxy37aVF9322GniMi5zuUORa71s Z3DA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=AkPG4PaohADnuYXiFHVXNba0kTPlMIjmLECIatpDfu0=; b=ZIktWseucJwqsD6f8Pl4v9IcENsHSxSbdgWfvFhRVZ5WXMydR7Y5hMgZTvVWSQ4BBn EYKhagUnXGLknxmvzhGjxkavoedGbiMdMSdou/vUSe9h6AqufGW5+UvqvXMUC95q181I 6snzCaOyIfQWP8qDbGhwsWm474oEJDk/4HtdDaX0Qrbf61AqrFc4s29hm8wrb9BoAVEN No0O/EubIGz4jyofvoseQR12tPOs/IK+Rx45YLIauYL2XIppuXXlMjjfHiN0uUIzy7NN 1NjLa/xv2TN+0+8eDAepxklvNgd3CQYGBDTwkbfStRp44L5Q/E0PPIFwJ8cS8Yw1NSnY o+sg== X-Gm-Message-State: AOAM530iLIuvaeyZ03VJy2jLCLOAY2oNiZmHME6LR1f5l0bjmwJaqvL6 1BTnHQvqaEWLGEiomwOfOQbXufohnbBYUwrSCbnf13SXtmQ= X-Google-Smtp-Source: ABdhPJyugJRMe8DJHUX3zmnohU6QTEyjJcRm4+GhnSvFDPo5ipm7gQpMs64Z5llUDV5HPM2jQI6/hkDB2JTHYkDEkH4= X-Received: by 2002:a2e:160e:: with SMTP id w14mr1530356ljd.66.1590021978610; Wed, 20 May 2020 17:46:18 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Begley Brothers Inc Date: Wed, 20 May 2020 19:45:41 -0500 Message-ID: Subject: Re: Guix mirrors To: guix-devel Content-Type: text/plain; charset="UTF-8" Received-SPF: pass client-ip=2a00:1450:4864:20::242; envelope-from=begleybrothers@gmail.com; helo=mail-lj1-x242.google.com X-detected-operating-system: by eggs.gnu.org: No matching host in p0f cache. That's all we know. X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001 autolearn=_AUTOLEARN X-Spam_action: no action X-BeenThere: guix-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+larch=yhetil.org@gnu.org Sender: "Guix-devel" X-Scanner: scn0 Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20161025 header.b=VKCkoHb4; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (aspmx1.migadu.com: domain of guix-devel-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=guix-devel-bounces@gnu.org X-Spam-Score: -1.71 X-TUID: CxKzlYQo7ipi Thanks to @kozodev on gitlab.com, a possible workaround, available immediately, is to document the following in the web pages and alt-F2 help as appropriate: 3.6.2 Proceeding with the Installation 8.1 Using the Configuration System with (note the inital root init channel path needs to be inserted) ```bash ... (use-package-modules screen) ;; Your `guix system init /etc/conf.scm` or ;; susequent `guix pull` and `guix system reconfigure` may ;; fail because the Guix server is unavailable - you will see ;; HTTPS errors 404, 504, 502. ;; In this situtaion, please use one of: ;; - "https://mirror1.com/x/y/z/guix.git" ;; - "https://mirror2.com/a/guix.git" ;; - "https://mirror2.com/d/e/guix.git" ;; in the `with-output-to-file` code below. Which you should uncomment, ;; then re-run: ;; ;; # guix system init /etc/conf.scm ;; ;; NOTE: Air-Gapped Facility Users. ;; If you are using guix in an air-gapped facility you will ;; need to add your Guix repository and uncomment this code ;; *before* running: ;; ;; # guix system init /etc/conf.scm ;; ;; There is curently no other way to repoint the init phase ;; to your air-gapped repository. ;;(with-output-to-file "/path/to/roots/first/init/channels.scm" ;; (lambda () ;; (display "(cons* (channel (name 'guix) (url \"https://internal.net/x/y/z/guix.git\")) %default-channels)"))) (operating-system ... ``` HTH? On Tue, May 19, 2020 at 2:32 AM Begley Brothers Inc wrote: > > Hi, > Over the last 24 hours I've experienced `guix pull` etc being > unavailable (HTTP 504's then 502's) more than available. > > Is there a reason why a post receive hook can't be added to the guix > repo to push to github, gitlab, etc. and in that way at least give > users some protection against these outages? > > There is a mirror[1] possibly (unofficial?) but it looks like it is > driven by some chron task. > > The required post receive hook is well documented[2], and not > un-common amoung reputable OS projects: > > - Android > - The Apache Software Foundation > - The Chromium Project > - The Eclipse Foundation > - The FreeBSD Project > - The Glasgow Haskell Compiler > - GNOME > - The Linux kernel source tree > - Qt > > [1]: https://github.com/guix-mirror/guix > [2]: https://git-scm.com/book/en/v2/Customizing-Git-Git-Hooks > > -- > Kind Regards > > Begley Brothers Inc. > > The content of this email is confidential and intended for the > recipient specified in message only. It is strictly forbidden to share > any part of this message with any third party, without a written > consent of the sender. If you received this message by mistake, please > reply to this message and follow with its deletion, so that we can > ensure such a mistake does not occur in the future. > This message has been sent as a part of discussion between Begley > Brothers Inc. and the addressee whose name is specified above. Should > you receive this message by mistake, we would be most grateful if you > informed us that the message has been sent to you. In this case, we > also ask that you delete this message from your mailbox, and do not > forward it or any part of it to anyone else. Thank you for your > cooperation and understanding. > Begley Brothers Inc. puts the security of the client at a high > priority. Therefore, we have put efforts into ensuring that the > message is error and virus-free. Unfortunately, full security of the > email cannot be ensured as, despite our efforts, the data included in > emails could be infected, intercepted, or corrupted. Therefore, the > recipient should check the email for threats with proper software, as > the sender does not accept liability for any damage inflicted by > viewing the content of this email. > The views and opinions included in this email belong to their author > and do not necessarily mirror the views and opinions of the company. > Our employees are obliged not to make any defamatory clauses, > infringe, or authorize infringement of any legal right. Therefore, the > company will not take any liability for such statements included in > emails. In case of any damages or other liabilities arising, employees > are fully responsible for the content of their emails. -- Kind Regards Begley Brothers Inc. The content of this email is confidential and intended for the recipient specified in message only. It is strictly forbidden to share any part of this message with any third party, without a written consent of the sender. If you received this message by mistake, please reply to this message and follow with its deletion, so that we can ensure such a mistake does not occur in the future. This message has been sent as a part of discussion between Begley Brothers Inc. and the addressee whose name is specified above. Should you receive this message by mistake, we would be most grateful if you informed us that the message has been sent to you. In this case, we also ask that you delete this message from your mailbox, and do not forward it or any part of it to anyone else. Thank you for your cooperation and understanding. Begley Brothers Inc. puts the security of the client at a high priority. Therefore, we have put efforts into ensuring that the message is error and virus-free. Unfortunately, full security of the email cannot be ensured as, despite our efforts, the data included in emails could be infected, intercepted, or corrupted. Therefore, the recipient should check the email for threats with proper software, as the sender does not accept liability for any damage inflicted by viewing the content of this email. The views and opinions included in this email belong to their author and do not necessarily mirror the views and opinions of the company. Our employees are obliged not to make any defamatory clauses, infringe, or authorize infringement of any legal right. Therefore, the company will not take any liability for such statements included in emails. In case of any damages or other liabilities arising, employees are fully responsible for the content of their emails.