It’s definitely an error. Means that the key is invalid or expired.
It must be corrected from the repo manager (the developer).
Nothing can be done from the user.
Please let me, be more specific.
Is there any way (for the developer) to generate a new key or something?
Preferably a non-expired one? :)[LEFT]Rebuilding the package, already tried, but didn’t help.
You show some message out of context and request that we guess what you did. Copy and paste full command invocation and its output that was used to emit error message, someone may be able to suggest next step.
You expect me to waste my time installing Debian for something you would need 5 seconds? Well, I do not have any problems with this key and if I would I know how to troubleshoot it. I would not demand others to do it for me.
I don’t have any problem myself, because I don’t need these repos.
My personal preference is compiling packages locally.
I was just tried to help other people (mostly newcomers) who needs a repo.
I really don’t expected such a hostile behaviour, but it’s your project, your way.
Personally I’ve lost interesting if OBS malfunctioning or not.
I’ll inform the 2 involved developers, just in case who wants to participate in this thread.
The problem with that repository key is that it is only 1024 bits and modern versions of apt and apt-get will not accept anything less than 2048. Unfortunately, the error messages from apt/apt-get do not make any of this clear.