From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 65056@debbugs.gnu.org, "Ludovic Courtès" <ludo@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: Tue, 12 Sep 2023 09:06:38 -0400 [thread overview]
Message-ID: <87a5try201.fsf@gmail.com> (raw)
In-Reply-To: <87msxr3jd4.fsf@elephly.net> (Ricardo Wurmus's message of "Tue, 12 Sep 2023 10:02:59 +0200")
Hi Ricardo,
Ricardo Wurmus <rekado@elephly.net> writes:
> Ludovic Courtès <ludo@gnu.org> writes:
>
>> 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?
>
> I got one response to ask for more information, which I supplied.
> Nothing since. I requested a response just now.
>
>> 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.)
>
> Yeah, I’d really like this to be fixed. It worked pretty well for
> years, so these seemingly unnecessary changes and the way they are
> applied without any recourse (and without anyone being able to confirm
> that they have in fact changed somehing) really bother me.
Agreed; I think it's premature to jump ship when we've had such a long
and fruitful relationship; let's show some patience and tenacity toward
a resolution.
--
Thanks,
Maxim
next prev parent reply other threads:[~2023-09-12 13:07 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
2023-09-12 8:02 ` Ricardo Wurmus
2023-09-12 13:06 ` Maxim Cournoyer [this message]
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=87a5try201.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=65056@debbugs.gnu.org \
--cc=Altadil@protonmail.com \
--cc=guix-sysadmin@gnu.org \
--cc=ludo@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 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).