On Wed, Sep 2, 2020 at 6:05 AM Vít Ondruch <vondruch(a)redhat.com> wrote:
Dne 01. 09. 20 v 19:54 Tom Hughes via devel napsal(a):
> On 01/09/2020 18:29, kevin wrote:
>
>> Just to make sure folks know, the retrace server being down is not this
>> teams fault, it's ours (infrastructure). We planned to just have it down
>> for a week or less when moving it to RDU, but it turned out that
>> datacenter move was not at all what we hoped for and it's been down much
>> longer than intended.
>>
>> That said, we have a machine up now there and it's just needing
>> configuration/setup to get the service back up and running. :)
>> So, hopefully soon it will again be online.
>
> Hasn't it effectively been down for like a year anyway? What was
> the last release it could actually retrace? 30? or was it 31?
The retrace server was not able to handle the backtraces since we
started to use zstd to compress RPMs.
That stopped being a valid reason back in April, since RHEL 8 supports
zstd compressed RPMs with the RHEL 8.2 release.
--
真実はいつも一つ!/ Always, there's only one truth!