Mailinglist Archive: opensuse-buildservice (46 mails)
< Previous | Next > |
[opensuse-buildservice] Invalid keydata in home repository
- From: Sebix <sebix@xxxxxxxx>
- Date: Sun, 26 Jul 2020 16:07:27 +0200
- Message-id: <36328b60-e134-3d06-5aa3-948d02b7518a@sebix.at>
Dear list,
I have a problem with the signkey of a home repository. After it
expired, I renewed / extended the sign key using:
osc signkey --extend home:sebix:intelmq
osc signkey --create home:sebix:intelmq
(I do not remember the order which I used anymore)
Now, I get this error on Tumbleweed:
Valid metadata not found at specified URL
An Ubuntu 16.04 user reported a similar error (also after the signkey
renewal):
The following signatures were invalid: KEYEXPIRED 1594988315
How can I fix these errors or properly re-create or extend the signkey?
best regards
Sebastian
I have a problem with the signkey of a home repository. After it
expired, I renewed / extended the sign key using:
osc signkey --extend home:sebix:intelmq
osc signkey --create home:sebix:intelmq
(I do not remember the order which I used anymore)
Now, I get this error on Tumbleweed:
Retrieving repository 'home:sebix:intelmq' metadata...................................................................................................................................................................................[error]
Repository 'home:sebix:intelmq' is invalid.[http-download.opensuse.org-5ac6b65c|http://download.opensuse.org/repositories/home:/sebix:/intelmq/openSUSE_Tumbleweed/]
Valid metadata not found at specified URL
History:valid repository.
- File /var/tmp/TmpFile.vc7Jia doesn't contain public key data
Please check if the URIs defined for this repository are pointing to a
Skipping repository 'home:sebix:intelmq' because of the above error.
An Ubuntu 16.04 user reported a similar error (also after the signkey
renewal):
W: Failed to fetchhttp://download.opensuse.org/repositories/home:/sebix:/intelmq/xUbuntu_16.04/InRelease
The following signatures were invalid: KEYEXPIRED 1594988315
How can I fix these errors or properly re-create or extend the signkey?
best regards
Sebastian
< Previous | Next > |