Project

General

Profile

Bug #154

[librerelease] Doesn't force SIGEXT and SIGID to be set

aurelien - over 11 years ago - . Updated over 11 years ago.

Status:
fixed
Priority:
bug
Category:
-
Assignee:
% Done:

0%


Description

It seems that during the 'librerelease' command the gpg fail ::
$ librerelease
> WARNING: Empty SIGEXT var, using default .sig
-> Signing /home/uncle/packages/staging/gnu/gnun-0.4-1-any.pkg.tar.xz...
gpg: no default secret key: No secret key
gpg: signing failed: No secret key
> ERROR: Signing failed

History

#2

Updated by mtjm over 11 years ago

There are two different problems. SIGEXT always needs to be set to the same non-default value, as #parabola logs show it is confusing. Is there any reason to not change it to use always ".sig" and remove the variable?

Do you have SIGID set correctly, do you run librerelease as your user (not root) and do you have that your GPG key available on the machine you use?

#4

Updated by lukeshu over 11 years ago

It now defaults to ".sig"

#5

Updated by lukeshu over 11 years ago

I take it back, I thought I did, but didn't change it.

Please answer me this: Why would SIGEXT ever be something other than ".sig".

#7

Updated by lukeshu over 11 years ago

I should comment that the documentation states that having the two variables unset disables package signing--apparently false.

#8

Updated by lukeshu over 11 years ago

libretools.conf now forces them to be set (in git).

Also available in: Atom PDF