intrigeri:
> sajolida:
>> 7 hours later, I restarted Tails and I still get the same error when
>> fetching accounting.git and internal.git. I don't get this error when
>> fetching master.git.
>
> anonym has reported similar issues but he cannot see them if he uses
> the IP address directly, which
On Thu 2018-11-01 12:58:21 +0100, intrig...@boum.org wrote:
> anonym has reported similar issues but he cannot see them if he uses
> the IP address directly, which seems to confirm the hypothesis of
> overenthusiastic DNS caching on exit nodes. Nothing we can do about
> exit nodes whose DNS resolve
sajolida:
> 7 hours later, I restarted Tails and I still get the same error when
> fetching accounting.git and internal.git. I don't get this error when
> fetching master.git.
anonym has reported similar issues but he cannot see them if he uses
the IP address directly, which seems to confirm the h
intrigeri:
> sajolida:
>> intrigeri:
>>> There will be some downtime and DNS will take a while to update.
>
>> What the timing window?
>
> The migration is over and things are back into working shape.
>
>> When trying to get accounting.git right now I get:
>
>> gcrypt: Repository not found: ta.
sajolida:
> intrigeri:
>> There will be some downtime and DNS will take a while to update.
> What the timing window?
The migration is over and things are back into working shape.
> When trying to get accounting.git right now I get:
> gcrypt: Repository not found: ta...@git.tails.boum.org:accoun
intrigeri:
> There will be some downtime and DNS will take a while to update.
What the timing window?
When trying to get accounting.git right now I get:
gcrypt: Repository not found: ta...@git.tails.boum.org:accounting.git
gcrypt: ..but repository ID is set. Aborting.
Is this the downtime?
On
