From: "Ludovic Courtès" <ludo@gnu.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 65056@debbugs.gnu.org, Tobias Geerinckx-Rice <me@tobias.gr>,
guix-sysadmin <guix-sysadmin@gnu.org>,
Altadil <Altadil@protonmail.com>
Subject: bug#65056: https://issues.guix.gnu.org/ cannot be accessed through Tor
Date: Fri, 08 Sep 2023 22:24:15 +0200 [thread overview]
Message-ID: <878r9g2z2o.fsf@gnu.org> (raw)
In-Reply-To: <87h6p256ty.fsf@elephly.net> (Ricardo Wurmus's message of "Mon, 14 Aug 2023 11:07:26 +0200")
Hello!
Ricardo Wurmus <rekado@elephly.net> skribis:
> I don’t know. I’m on holidays now, but I’ve opened yet another ticket
> to get a definitive answer to my more elaborate variant of “WTF?”.
Did you eventually get feedback from them?
If not, we can start looking for a way to move public-facing services
elsewhere. (It may not be trivial because bayfront, which is the other
node we’ve traditionally used for that, is super busy these days.)
Thanks again for your support…
Ludo’.
next prev parent reply other threads:[~2023-09-08 21:04 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878r9g2z2o.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=65056@debbugs.gnu.org \
--cc=Altadil@protonmail.com \
--cc=guix-sysadmin@gnu.org \
--cc=me@tobias.gr \
--cc=rekado@elephly.net \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.