From: Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: Altadil <Altadil@protonmail.com>, 65056@debbugs.gnu.org
Subject: bug#65056: https://issues.guix.gnu.org/ cannot be accessed through Tor
Date: Fri, 04 Aug 2023 21:29:06 +0200 [thread overview]
Message-ID: <0bd1dfa9c3997becec68dc277b6c93e5@tobias.gr> (raw)
In-Reply-To: <10e9eb490471d421fa709eaa36bdec83@tobias.gr>
On 2023-08-04 21:21, Tobias Geerinckx-Rice via Bug reports for GNU Guix
wrote:
> The Guix project does not block Tor. If the datacentre has decided to
> block Tor like it blocked most of Russia, there is little we can do
> but ask them to reconsider.
Didn't mean to sound quite so fatalistic. We could always migrate
issues. to a different machine, like guix.gnu.org was, but it's not very
satisfying.
Kind regards,
T G-R
Sent from a Web browser. Excuse or enjoy my brevity.
next prev parent reply other threads:[~2023-08-04 19:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-04 16:57 bug#65056: https://issues.guix.gnu.org/ cannot be accessed through Tor Altadil via Bug reports for GNU Guix
2023-08-04 19:21 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2023-08-04 19:29 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix [this message]
2023-08-13 0:25 ` Ludovic Courtès
2023-08-13 11:46 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2023-08-14 9:07 ` Ricardo Wurmus
2023-09-08 20:24 ` Ludovic Courtès
2023-09-12 8:02 ` Ricardo Wurmus
2023-09-12 13:06 ` Maxim Cournoyer
2023-09-14 21:25 ` Ludovic Courtès
2023-09-15 7:41 ` Ricardo Wurmus
2023-09-18 9:51 ` Ludovic Courtès
2023-09-20 21:31 ` Giovanni Biscuolo
2023-09-20 22:45 ` Ricardo Wurmus
2023-09-21 6:27 ` Giovanni Biscuolo
2023-10-02 8:48 ` Ludovic Courtès
2023-09-18 20:31 ` bug#65056: https://issues.guix.gnu.org available through Tor again Altadil via Bug reports for GNU Guix
2023-09-21 6:29 ` Giovanni Biscuolo
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=0bd1dfa9c3997becec68dc277b6c93e5@tobias.gr \
--to=bug-guix@gnu.org \
--cc=65056@debbugs.gnu.org \
--cc=Altadil@protonmail.com \
--cc=me@tobias.gr \
/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).