From: Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org>
To: bug-guix@gnu.org, poiNt_3D <point4d@gmail.com>,
54370@debbugs.gnu.org, 54370-done@debbugs.gnu.org
Subject: bug#54370: network problem or intentional blocking?
Date: Sun, 13 Mar 2022 11:43:23 +0000 [thread overview]
Message-ID: <E500DC4E-B265-4469-A66F-946DF5D6535E@tobias.gr> (raw)
In-Reply-To: <CAOT6rO-TzDWnOtCXc9d+fZFzvSUNKNXnyzhjNEwxPD7mVVOCeA@mail.gmail.com>
Hi Point4d,
Specifically, from the thread linked by Evgeny:
"At the MDC level there’s an unrelated recent ban of some Russian IP ranges in place due to massively increased port scans and intrusion attempts since about one week. I hope you can use the Chinese mirror for the time being."
That mirror is at https://mirrors.sjtug.sjtu.edu.cn/guix . Let us know if it works.
Kind regards,
T G-R
Sent on the go. Excuse or enjoy my brevity.
next prev parent reply other threads:[~2022-03-13 11:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-13 6:14 bug#54370: network problem or intentional blocking? poiNt_3D
2022-03-13 9:05 ` bug#54370: Guix in Russia Evgeny Pisemsky
2022-03-13 11:43 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix [this message]
2022-03-13 12:15 ` bug#54370: network problem or intentional blocking? Tobias Geerinckx-Rice via Bug reports for GNU Guix
2022-03-13 12:36 ` Christopher Baines
2022-03-13 14:30 ` Ludovic Courtès
2022-03-13 15:30 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2022-03-13 20:03 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
[not found] ` <3F8ECF7D-4C80-4D03-B7A1-60EBAD3EE206@tobias.gr>
[not found] ` <CAOT6rO__s7aLsK_ZOE-RO49CyJ=VptAJBf79F=bE8pJ2XHcEOA@mail.gmail.com>
2022-03-13 19:50 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2022-03-13 20:36 ` Maxime Devos
2022-03-15 7:57 ` Ludovic Courtès
2022-03-19 11:04 ` bug#54370: guix.gnu.org is inaccessible from Russia Ludovic Courtès
2023-02-07 15:33 ` bug#54370: network problem or intentional blocking? Christopher Baines
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=E500DC4E-B265-4469-A66F-946DF5D6535E@tobias.gr \
--to=bug-guix@gnu.org \
--cc=54370-done@debbugs.gnu.org \
--cc=54370@debbugs.gnu.org \
--cc=me@tobias.gr \
--cc=point4d@gmail.com \
/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).