On 26.07.19 16:22, Michael Schroeder wrote:
On Fri, Jul 26, 2019 at 02:25:16PM +0200, Mathias Radtke wrote:
On 26.07.19 10:09, Mathias Radtke wrote:
Hi
I recently updated our instance from Leap 42.3 to 15.1 and OBS from 2.9 to 2.10. Everything seemed to work smoothly. However now people are complaining that the debian and ubuntu Release files.
This only affect repositories that contain newly build packages since the uprade.
obssigner and obssignd are running. the signer.log only contains: 2019-07-24 12:40:14: [8356] signer started waiting for an event...
Any suggestion on where to look at ? The Release.key files seem to have dissappeared after the mmigration/update and are not lonkger recreated after a new package is build in a repository. This sounds like $sign is no longer set in BSConfig.pm. But I don't see how the update can have changed that. Are there any suspicious messages in the publisher log (/srv/obs/log/publisher.log)? from BSConfig.pm: our $sign = "/usr/bin/sign"; #Extend sign call with project name as argument "--project $NAME" #our $sign_project = 1; #Global sign key our $keyfile = "/srv/obs/obs-default-gpg.asc"; our $gpg_standard_key = "/srv/obs/obs-default-gpg.asc";
Cheers, Michael.
--
Mathias Radtke
---
http://uib.de/de/support-schulung/schulung/
uib gmbh
Bonifaziusplatz 1B
55118 Mainz
Tel. 06131 / 27561-16