From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp1 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms11 with LMTPS id 8GDVMz4uxV4IXAAA0tVLHw (envelope-from ) for ; Wed, 20 May 2020 13:18:54 +0000 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp1 with LMTPS id VLeuLz4uxV4/AgAAbx9fmQ (envelope-from ) for ; Wed, 20 May 2020 13:18:54 +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 763499400C3 for ; Wed, 20 May 2020 13:18:54 +0000 (UTC) Received: from localhost ([::1]:51910 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jbOcX-0000IM-7i for larch@yhetil.org; Wed, 20 May 2020 09:18:53 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:47264) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jbOcN-0000G0-O1 for guix-devel@gnu.org; Wed, 20 May 2020 09:18:43 -0400 Received: from mail-lf1-x130.google.com ([2a00:1450:4864:20::130]:43384) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1jbOcM-0008Ky-Nb for guix-devel@gnu.org; Wed, 20 May 2020 09:18:43 -0400 Received: by mail-lf1-x130.google.com with SMTP id c12so2268087lfc.10 for ; Wed, 20 May 2020 06:18:41 -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 :cc:content-transfer-encoding; bh=c5THyXEyhTZFf2kOEupAoTCM2ma2bTiZYFy/CVZL5Ls=; b=giiGVzq2CCTHIfepwSBpAwAx7jG94za53JOkXYa7+G3ahv7hORxalxNyrq2EDq04UK z2Go3eQU4Z3QwBt4/I+z9S6NyvU875WtUoMBNW8fcySnnBxUZ5eM7cJC6m5Fu/596BqL o8S9M4M/LystLXDrwJ/FLL7eDLLNTR7dqZxnBR51xUstZf8INwjZf2NlnpXWjaNVO4+9 IdD+uZirtNoLNs4SRbe9Kg6kZDB2El7ry2hjJXUWp9NgFcJl/qh+7h1XC+wQNKkbFR1h GA5Jjz4yLMjqcbsq8hkdVSTa5ez1YfFqRQM3Zl6MNLxHglBXlNUNOuzxt17T0JROgjGO 3GbA== 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:cc:content-transfer-encoding; bh=c5THyXEyhTZFf2kOEupAoTCM2ma2bTiZYFy/CVZL5Ls=; b=Wz9UQdpAYY6PzoLDNe4HINbDe9S9VOtHiSoUBgsXSOFgrLks3u1sgMECnpzdewpRjr CSx3ouFkdjQP7dOAYJcPkB3Nl0UuB879bUdHpvpV1y57K+QxjVvAd4dUNqK9R2SsQl+H 7mzq9oWE5ahiKi1kwtf9P38rCY9vH0TGxH3qu5BE7gFNgmzV8Ki3kndMn+YFECaaOxRj DKxXfrBYG2uyTIc3MUCBLjaKDvFQb4qdk5pCBsVvp+6cKnPoUzJ1/9CtCx94XKrV09Bb fOw0NXlH+OkFSdimfkVvAYe1FTMASFnNMcYaxwsT276VJUtqIsKKx/bPzb6y++gYrRDc 1LVA== X-Gm-Message-State: AOAM533qEN3giRrgVtBLDWyzXZOi5COfwM34FwPT7RKQVujvM1V7h666 +vzhkMkzGSSXDDiNdVj9MxHevP1KeruUax0NKDI= X-Google-Smtp-Source: ABdhPJwAO0/KbUYJXMv1bjoFiYuH0XVgHWkCHcv1v503/MZNJc205R5W/tTl3HEwH8wIEQKFosh/U+OkLbxRt+qiYHo= X-Received: by 2002:a19:cbd7:: with SMTP id b206mr2551242lfg.163.1589980720433; Wed, 20 May 2020 06:18:40 -0700 (PDT) MIME-Version: 1.0 References: <87v9kqeupc.fsf@elephly.net> In-Reply-To: From: Begley Brothers Inc Date: Wed, 20 May 2020 08:18:03 -0500 Message-ID: Subject: Re: Guix mirrors To: zimoun Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Received-SPF: pass client-ip=2a00:1450:4864:20::130; envelope-from=begleybrothers@gmail.com; helo=mail-lf1-x130.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: , Cc: Guix Devel Errors-To: guix-devel-bounces+larch=yhetil.org@gnu.org Sender: "Guix-devel" X-Scanner: scn0 Authentication-Results: aspmx1.migadu.com; dkim=fail (rsa verify failed) header.d=gmail.com header.s=20161025 header.b=giiGVzq2; dmarc=fail reason="SPF not aligned (relaxed)" header.from=gmail.com (policy=none); 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: 0.09 X-TUID: uehWxMsyF+qY Hi, Thanks for taking the time to respond. Sounds like good news overall.... On Wed, May 20, 2020 at 6:57 AM zimoun wrote: > > Hi Ricardo, > > On Wed, 20 May 2020 at 13:02, Ricardo Wurmus wrote: > > > I expect that this will change soon after some more discussion of the > > details. > > Last time we discussed that was on December [1]. What is missing is: dis= cuss if > > a) an "official" mirror is hard-coded in '%default-channels' > or > b) an "official" mirror is documented in the manual and it is up to > the user to setup it via ~/.config/guix/channels.scm. > > The a) annoys people who do not want the mirror, so they have to tweak > the list by themself and in the same a) is more newcomer-friendly > because it just works. > The b) annoys newcomers because it is another step and in the same > time b) is more customizable. > > Obviously, there is option c): guix-install.sh asks a question and > then do the b) dance. > > > And discuss if a channel is described as: > > (channel > (name 'guix) > (url "https://savannah=E2=80=A6") > (mirror (list "https://mirror-one=E2=80=A6" > "https://mirror-two=E2=80=A6"))) > > [ where mirror is optional ] > > or something else? There should be a built in (hard-coded) failover list - ideally three - without the user being told or asked to do anything during setup. Ideally the user could alter that list - but that seems a stage 2 feature given the curent state. Stage 3 might alllow the default list to vary by country code - driven by and env var set to two letter ISO code? I was surprised guix doesn't seem to be mirrored to gnu.io - or is that the same machine(s)? On reflection in this context 'mirror' is not descriptive in the channel config - 'failover' might better communicate the intent and context (channel (name 'guix) (url "https://savannah=E2=80=A6") (failover (list (url "https://mirror-one=E2=80=A6") (url "https://mirror-two=E2=80=A6")))) where **overriding** the failover list is optional, but you cannot unset the default list HTH > Well, Ludo suggested [2] to address "Trustable guix pull" [3]; which > should be really cool! > Now, I am not sure to understand if there is no mirror mechanism > because no one took the time to implement it or if any other reasons > related to "trustable guix pull". > > > [1] https://lists.gnu.org/archive/html/guix-devel/2019-12/msg00150.html > [2] https://lists.gnu.org/archive/html/guix-devel/2019-12/msg00276.html > [3] http://issues.guix.gnu.org/issue/22883 > > > Cheers, > simon --=20 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.