unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Nikita Gillmann <nikita@n0.is>
To: Begley Brothers Inc <begleybrothers@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Guix mirrors
Date: Wed, 20 May 2020 11:11:11 +0200	[thread overview]
Message-ID: <20200520091111.uoxct2a4tznuqltv@hex> (raw)
In-Reply-To: <CAJsH2QmK8wiNehj4LFGT7vk0yC3hKyUJ0uCe+rQtB4-ESsS9oQ@mail.gmail.com>

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.
> 


  reply	other threads:[~2020-05-20  9:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-19  7:32 Guix mirrors Begley Brothers Inc
2020-05-20  9:11 ` Nikita Gillmann [this message]
2020-05-20 11:01 ` Ricardo Wurmus
2020-05-20 11:57   ` zimoun
2020-05-20 12:15     ` Ricardo Wurmus
2020-05-20 12:40       ` zimoun
2020-05-20 12:53         ` Tobias Geerinckx-Rice
2020-05-20 14:37           ` zimoun
2020-06-02 10:02           ` zimoun
2020-05-20 13:18     ` Begley Brothers Inc
2020-05-20 14:41       ` zimoun
2020-05-21  0:45 ` Begley Brothers Inc
2020-05-21  1:24   ` Begley Brothers Inc

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=20200520091111.uoxct2a4tznuqltv@hex \
    --to=nikita@n0.is \
    --cc=begleybrothers@gmail.com \
    --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).