Probably this PR should be backported to 2.10 branch https://github.com/openSUSE/obs-sign/pull/19 VP. On Mon, 05 Aug 2019 10:29:49 +0200 Andreas Schwab wrote:

On Aug 05 2019, Stefan Botter wrote:

...

I have a problem with my own installation of obs 2.10. Building works, but all builds are stuck in the "signing" phase. /srv/obs/log/signer.log shows lines like these: ====== gpg: decryption failed: No secret key sign failed: 256 - checking digest /srv/obs/jobs/x86_64/userweb::openSUSE_Leap_15.1::pure-ftpd-c0ae603b4c4953d7a0b214f7c15554b7:dir/pure-ftpd-1.0.47-lp151.95.1.src.rpm: digests OK sign failed: sign /srv/obs/jobs/x86_64/userweb::openSUSE_Leap_15.1::pure-ftpd-c0ae603b4c4953d7a0b214f7c15554b7:dir/pure-ftpd-1.0.47-lp151.95.1.src.rpm failed ====

I'm seeing that too. There seems to be a bug what causes a failure in providing the pass phrase to gpg. It works when the pass phrase is empty.

Andreas.

-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

But the patch only works with: obs-signd-2.5.3-lp151.2.1.x86_64 But not with: obs-signd-2.5.4-lp151.1.1.x86_64 which comes with the appliance or updates. running into the following signing error: gpg: skipped "rpm@scorpio-it.net": No secret key gpg: signing failed: No secret key sign failed: 512 - checking digest /srv/obs/jobs/x86_64/home:computersalat::openSUSE_Leap_15.1::iso-repo-0a72bb8dcb145347afa42a2942175996:dir/iso-repo-3.1.0-lp151.2.1.noarch.rpm: digests OK sign failed: sign /srv/obs/jobs/x86_64/home:computersalat::openSUSE_Leap_15.1::iso-repo-0a72bb8dcb145347afa42a2942175996:dir/iso-repo-3.1.0-lp151.2.1.noarch.rpm failed so what is the problem now ? any help is really appreciated. Thanks :-) Am 05.08.19 um 12:17 schrieb Stefan Botter:

Andreas, Victor,

thank you very much!

On Monday, August 5, 2019 10:44:10 AM CEST Victor Pereira wrote:

...

Probably this PR should be backported to 2.10 branch https://github.com/openSUSE/obs-sign/pull/19

VP.

On Mon, 05 Aug 2019 10:29:49 +0200

Andreas Schwab wrote: :

...

I'm seeing that too. There seems to be a bug what causes a failure in providing the pass phrase to gpg. It works when the pass phrase is empty.

Andreas.

Indeed, my key has a passphrase, and manually adding the changes from the PR let the signer work again!

Greetings,

Stefan

-- Christian ------------------------------------------------------------ https://join.worldcommunitygrid.org?recruiterId=177038 ------------------------------------------------------------ http://www.sc24.de - Sportbekleidung ------------------------------------------------------------