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 4LTzNUT0xF43IgAA0tVLHw (envelope-from ) for ; Wed, 20 May 2020 09:11: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 mp1 with LMTPS id GECZMUT0xF5mVQAAbx9fmQ (envelope-from ) for ; Wed, 20 May 2020 09:11: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 2736B940390 for ; Wed, 20 May 2020 09:11:32 +0000 (UTC) Received: from localhost ([::1]:51426 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jbKl9-00054y-05 for larch@yhetil.org; Wed, 20 May 2020 05:11:31 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:48644) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jbKkz-0004zV-QB for guix-devel@gnu.org; Wed, 20 May 2020 05:11:21 -0400 Received: from aibo.runbox.com ([91.220.196.211]:59434) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1jbKkx-00049i-OL for guix-devel@gnu.org; Wed, 20 May 2020 05:11:20 -0400 Received: from [10.9.9.203] (helo=mailfront21.runbox) by mailtransmit03.runbox with esmtp (Exim 4.86_2) (envelope-from ) id 1jbKku-0002uc-9V; Wed, 20 May 2020 11:11:16 +0200 Received: by mailfront21.runbox with esmtpsa [Authenticated alias (924257)] (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) id 1jbKkq-0003uD-GX; Wed, 20 May 2020 11:11:12 +0200 Date: Wed, 20 May 2020 11:11:11 +0200 From: Nikita Gillmann To: Begley Brothers Inc Subject: Re: Guix mirrors Message-ID: <20200520091111.uoxct2a4tznuqltv@hex> Mail-Followup-To: Begley Brothers Inc , guix-devel References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: Received-SPF: pass client-ip=91.220.196.211; envelope-from=nikita@n0.is; helo=aibo.runbox.com X-detected-operating-system: by eggs.gnu.org: First seen = 2020/05/20 05:11:16 X-ACL-Warn: Detected OS = ??? X-Spam_score_int: -25 X-Spam_score: -2.6 X-Spam_bar: -- X-Spam_report: (-2.6 / 5.0 requ) BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, 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=none; dmarc=fail reason="SPF not aligned (relaxed), No valid DKIM" header.from=n0.is (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.41 X-TUID: apDmPrZV+HLh Begley Brothers Inc transcribed 2.6K bytes: > 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? I suspect this is mostly project guidelines which disocurage this (see GNU Free Systems Distribution Guidelines). I don't know if I'm correct about this, so one of the project maintainers will likely comment. > 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. >