Key mismatch about gerbera HOT 7 CLOSED

There is an issue with that repo

Repository is locked by another user:  at host 06433ec7a862 (phase-1)

I hope it resolves by itself...

from gerbera.

Resolved by itself or not.
For someone with a knowledge of security, it doesn't instill confidence when the key CHANGES, respectively can be changed by some 'another user'. Unavailable would be okay. That can happen. Though returning just another key ... ? Injecting malware through one channel doesn't limit the potential intrusion to just one package ... .

from gerbera.

Just to make things clear: as an unpaid open source community, we are relying on infrastructure provided to us for free. We are not maintaining all of it and only see part of it in configurations.

In case of your problem, it seems that any of our upload tasks got stuck and blocked the creation of hashes, making the download invalid - which is high security.

Before blaming us for things we cannot fully control, I ask you to analyse the issue to gain better understanding. If you do not do say, stay with reporting the facts. Thank you.

from gerbera.

Of course it usually is a repository error. I was simply lead to believe something else due to that "... locked by another user ...". As you wrote, it looks like it couldn't be updated properly. And surely, once it can provide 'clean' files it will resolve itself.
My excuses for the noise. Now waiting for the next clean update ... .

from gerbera.

@whyman Can you take a look at the repo. The lock does not go away automatically.

from gerbera.

Hrm, Ive manually deleted the lock files. Would be interesting to know the cause, a failed upload or something?

from gerbera.

No key change or compromise that I am aware of, FWIW.

from gerbera.