On Mon, Dec 23, 2019, 17:45 J. Scheurich <mufti11@web.de> wrote:

I tried the following:

$ kinit mufti11@FEDORAPROJECT.ORG
rm -rf wdune
fedpkg clone wdune
cd wdune
$ fedpkg import ~/rpmbuild/SRPMS/wdune-1.654-3.fc32.src.rpm > /dev/null

$ git commit -sm "Initial import (#1658153)"

You do not need to sign your git commits.

error: gpg failed to sign the data
fatal: failed to write commit object

So the commit probably failed because git couldn't find a GPG associated with your email address.


Why would you want to sign your commits with fedora GPG keys, and not your own key? And those are the public keys, they wouldn't help you either way ...

I think ,my gpg key are up to date.

How to proove it ?

Just skip the -s argument in "git commit".

$ git commit
error: gpg failed to sign the data
fatal: failed to write commit object

Same problem 8-(

Looks like you have the option to sign your git commits turned on globally, probably in ~/.gitconfig or something.


so long

MUFTI

_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org