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