Hello Dominique, On Jul 19 11:33 Dominique Leuenberger / DimStar wrote (excerpt):
On Tue, 2016-07-19 at 11:01 +0200, Johannes Meixner wrote:
Yesterday I did what I was told to do last time (and what seems to have helped last time): --------------------------------------------------------------- $ osc signkey --extend Printing <status code="ok" /> $ ---------------------------------------------------------------
This is indeed the right thing to do... you can also check if the new key has indeed been created by:
osc signkey Printing | gpg pub dsa1024 2008-01-22 [SC] [expires: 2018-09-26] 7C8A8DA1722FC4DFDA9FF1EF669DEC9F98C4529D uid Printing OBS Project
=> the expiration date has indeed been corrected
But that seems to no longer make it work because I tried afterwards yesterday and also today and I still get (on my Leap 42.1 system):
Has the repo been published since you extended the key? At least one package needs to be published to make the repo re-appear; that's when the new key is being published.
Many thanks for your helpful information.
I did a small fix for Printing/epson-inkjet-printer-escpr and
waited until "osc results" no longer shows "unpublished" and
now it works for me on my openSUSE Leap 42.1 system:
----------------------------------------------------------------
# zypper -v ar -cg \
http://download.opensuse.org/repositories/Printing/openSUSE_Leap_42.1/Printi...
...
# zypper -v refresh 1
...
New repository or package signing key received:
Repository: Printing System Development Project (openSUSE_Leap_42.1)
Key Name: Printing OBS Project
Might be worthy though to file an issue on https://github.com/openSUSE/open-build-service/issues to ask for a publisher run when the key is changed
https://github.com/openSUSE/open-build-service/issues/1949 Kind Regards Johannes Meixner -- SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard, Graham Norton - HRB 21284 (AG Nuernberg)