[opensuse-buildservice] unsigned debian release files after update
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 ?
Thanks
Regards
Mathias
--
Mathias Radtke
---
http://uib.de/de/support-schulung/schulung/
uib gmbh
Bonifaziusplatz 1B
55118 Mainz
Tel. 06131 / 27561-16
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.
Any suggestion where to look/set this?
Mathias
--
Mathias Radtke
---
http://uib.de/de/support-schulung/schulung/
uib gmbh
Bonifaziusplatz 1B
55118 Mainz
Tel. 06131 / 27561-16
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)? Cheers, Michael. -- Michael Schroeder mls@suse.de SUSE LINUX GmbH, GF Jeff Hawn, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
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
On Fri, Jul 26, 2019 at 04:24:49PM +0200, Mathias Radtke wrote:
On 26.07.19 16:22, Michael Schroeder wrote:
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";
Looks good. So what about any suspicious messages in the publisher log? Cheers, Michael. -- Michael Schroeder mls@suse.de SUSE LINUX GmbH, GF Jeff Hawn, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On 26.07.19 16:34, Michael Schroeder wrote:
On Fri, Jul 26, 2019 at 04:24:49PM +0200, Mathias Radtke wrote:
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"; Looks good. So what about any suspicious messages in the publisher log?
Cheers, Michael.
I see that the Release.gpg gets removed
2019-07-24 13:20:55: [29525] publishing
home:uibmz:opsi:4.2:experimental/Univention_4.4
- Release.gpg
! all/opsi-linux-bootimage_20190522-2_all.deb
! all/python3-opsi_4.2.0.10-1_all.deb
+ all/opsi-linux-bootimage_20190724-1_all.deb
+ all/python3-opsi_4.2.0.11-1_all.deb
+ opsi-linux-bootimage_20190724-1.dsc
+ opsi-linux-bootimage_20190724-1.tar.gz
+ python3-opsi_4.2.0.11-1.dsc
+ python3-opsi_4.2.0.11-1.tar.gz
fetched 0 patterns
running dpkg-scanpackages
dpkg-scanpackages: warning: Packages in archive but missing from
override file:
dpkg-scanpackages: warning: opsi-linux-bootimage opsi-linux-support
opsi-tftp-hpa opsi-tftp-hpa-dbg opsi-tftpd-hpa opsi-utils
opsi-windows-support opsi4ucs opsiconfd opsiconfd-common opsipxeconfd
opsiwebservice python3-opsi winexe
dpkg-scanpackages: info: Wrote 20 entries to output Packages file.
running dpkg-scansources
dpkg-scanpackages: info: Wrote 0 entries to output Packages file.
syncing database (10 ops)
waiting for an event...
But apart from that, nothing that actually remarks an error
--
Mathias Radtke
---
http://uib.de/de/support-schulung/schulung/
uib gmbh
Bonifaziusplatz 1B
55118 Mainz
Tel. 06131 / 27561-16
participants (2)
-
Mathias Radtke -
Michael Schroeder