Hello all, we're running a private OBS 2.10 instance. We currently have a bunch of projects without a top-level project, i.e. we have <group>:<p1> <group>:<p2> <group>:<p3> but we don't have <group>.
From the old days we also have a global GPG signing key which is still used to sign every RPM for all projects that don't have their own key.
Now I'd like to do two things: - introduce the project <group> - manually force the signing key for <group> Will a new project <group> automatically be the parent for <group>:<p1> etc.? I.e. will <group>:<p1> inherit permissions and in particular the signing key? I understand that forcing a signing key is not supported via osc or the WWW interface, but would I get away with manually replacing/setting /srv/obs/projects/<group>.pkg/_signkey /srv/obs/projects/<group>.pkg/_pubkey ? And if so, how do I generate the format for _signkey? For _pubkey it looks quite straight forward. In case you're wondering why we're looking into that. ;-) Newer versions of OBS seem to be quite eager to introduce a new signing key for new projects, AFAICT, if there's no key in any of the top-level projects. The global signing key seems to be ignored. So, when I create <group>:<p4> it will a have a new signing key. But I want it to use the global one. Unfortunately 'osc signkey --delete <group>:<p4>' doesn't seem to work for getting rid of the new key. TIA + HAND -- Till -- Dipl.-Inform. Till Dörges doerges@pre-sense.de PRESENSE Technologies GmbH Nagelsweg 41, D-20097 HH Geschäftsführer/Managing Directors AG Hamburg, HRB 107844 Till Dörges, Jürgen Sander USt-IdNr.: DE263765024 -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org