Re: jitter git repository

[Luca Saiu]

Hello Bruno.

I apologise for the inconvenience and will try to fix it one of these
nights.

The short answer is that I will improve the situation tonight or
otherwise very early.  The details below are probably not very
interesting.

On 2024-12-01 at 10:13 +0000, Bruno Haible wrote:

> Yesterday, for the third time in a row, the gitlab CI failed again, with the
> same error message as the last two ones.
>
> The situation now is like this: Poke depends on jitter, 

Yesterday was indeed an unusual day; I wanted to check if what I was
thinking could be the issue, and it was.
My server hosts a small Tor exit relay.  Near the end of each month,
if I still have a lot of the allotted bandwidth available, I stop
throttling and let Tor run with unlimited bandwidth until the current
metered period ends, on the third day of each month.

I guess I cannot afford that on my underpowered machine.

> and the jitter git repo
> is on a site which refuses to talk to half of the internet.

Well, I can avoid blocking accesses by IP address.

The git configuration can also be improved a lot.  Right now git
requests over HTTP pass through cgit run as a CGI process, which is very
inefficient.

> a) The jitter repo moves to a site where it can be reached from the entire
>    internet.

Moving to Savannah is certainly possible.  I would like to avoid that
and instead making ageinghacker more reliable, in order to keep using my
own infrastructure; if I fail within, say, a week, moving to Savannah is
the solution.

-- 
Luca Saiu      https://ageinghacker.net
  GNU Jitter     https://www.gnu.org/software/jitter
  GNU epsilon    https://www.gnu.org/software/epsilon
  pEp-mail-tool  https://codeberg.org/pEp/pEp-mail-tool

I support everyone's freedom of mocking any opinion or belief, no
matter how deeply held, with open disrespect and the same unrelented
enthusiasm of a toddler who has just learned the word "poo".

sender_key.asc
Description: application/pgp-keys