Bug 406167

Summary:	repoman commit gives an error: unknown option `gpg-sign'
Product:	Portage Development	Reporter:	Martin Mokrejš <mmokrejs>
Component:	Repoman	Assignee:	Portage team <dev-portage>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	dschridde+gentoobugs
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Martin Mokrejš 2012-02-28 15:23:52 UTC

Since about 2-3 weeks I cannot commit to science overlay, due to some version incompatibility of repoman/git/gnupg?

$ repoman commit -m "blah"

RepoMan scours the neighborhood...
>>> Creating Manifest for /home/mmokrejs/proj/sci/sci-biology/gbrowse

Note: use --include-dev (-d) to check dependencies for 'dev' profiles

* 3 files being committed... 
error: unknown option `gpg-sign'
usage: git commit [options] [--] <filepattern>...

    -q, --quiet           suppress summary after successful commit
    -v, --verbose         show diff in commit message template

Commit message options
    -F, --file <file>     read message from file
    --author <author>     override author for commit
    --date <date>         override date for commit
[cut]

I see this went into git at about http://www.spinics.net/lists/git/msg169101.html.

# emerge -pv git portage gnupg

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild   R    ] sys-apps/portage-2.1.10.49  USE="(ipc) -build -doc -epydoc (-pypy1_8) -python2 -python3 (-selinux) -xattr" LINGUAS="-pl" 0 kB
[ebuild   R    ] dev-vcs/git-1.7.8.5  USE="blksha1 cgi curl gtk iconv perl python threads tk webdav -cvs -doc -emacs (-ppcsha1) -subversion -xinetd" 0 kB
[ebuild   R    ] app-crypt/gnupg-2.0.18  USE="bzip2 nls readline usb -adns -doc -ldap (-selinux) -smartcard -static" 0 kB
#

Is there an ENV variable to prevent calls to gnupg from repoman?

Comment 1 Martin Mokrejš 2012-02-28 15:26:41 UTC

Actually, shouldn't there be a USE=gpg or similar used by portage or git packages?

Comment 2 Martin Mokrejš 2012-02-28 15:37:36 UTC

Yup, I unmasked dev-vcs/git-1.7.9.2 and now get just:


RepoMan scours the neighborhood...
>>> Creating Manifest for /home/mmokrejs/proj/sci/sci-biology/gbrowse

Note: use --include-dev (-d) to check dependencies for 'dev' profiles

* 3 files being committed... 
gpg: skipped "Martin Mokrejs <mmokrejs@fold.natur.cuni.cz>": No secret key
gpg: signing failed: No secret key
error: gpg failed to sign the data
fatal: failed to write commit object
!!! Exiting on git (shell) error code: 128

Comment 3 Zac Medico gentoo-dev

2012-02-28 16:16:38 UTC

Use `git config user.signingkey key_id` to configure your gpg key.

*** This bug has been marked as a duplicate of bug 403323 ***

Comment 4 Martin Mokrejš 2012-02-28 16:27:19 UTC

(In reply to comment #3)
> Use `git config user.signingkey key_id` to configure your gpg key.
> 
> *** This bug has been marked as a duplicate of bug 403323 ***

works, thanks. How about repoman catching this type of an error and give more infomational error message out? Actually, I don't think it is desired to die if gpg key isn't configured, specially unless there is the IUSE=+gpg or so.