http://bugzilla.opensuse.org/show_bug.cgi?id=998838 Bug ID: 998838 Summary: TW20160909: GPG signing git commits is acting up Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Development Assignee: bnc-team-screening@forge.provo.novell.com Reporter: asarai@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- If I try to auto-sign (using `git config --global commit.gpgSign true`) all of my commits, something odd happens (this issue started happening a few days ago, after I updated Tumbleweed). This was broken in the same update as when zsh was broken (which I think was the snapshot before the one I'm running now). Here's a session: % git commit --amend error: gpg failed to sign the data fatal: failed to write commit object But if I get gpg to sign something explicitly, it will ask me for my passphrase: % gpg --sign --armor SOMETHING [enter passphrase] [snipped signature] And then `git` will act correctly. In addition, it should be noted that gpg is actually asking me to provide the passphrase for a *different* key than the key I'm signing commits with -- which is *VERY* worrying. It just so happens that I use the same passphrase for these two keys, but it's still not great. % rpm -q git gpg2 zsh git-2.10.0-1.1.x86_64 gpg2-2.1.15-1.2.x86_64 zsh-5.2-6.1.x86_64 % zypper info product:openSUSE Information for product openSUSE: --------------------------------- Repository : openSUSE-Tumbleweed-Oss Name : openSUSE Version : 20160909-0 Arch : x86_64 Vendor : openSUSE Flavor : ftp Is Base : Yes Installed : Yes Status : up-to-date Update Repositories : --- CPE Name : cpe:2.3:o:opensuse:opensuse:20160909:*:*:*:*:*:*:* Short Name : openSUSE Summary : openSUSE Tumbleweed Description : openSUSE Tumbleweed is the rolling distribution by the openSUSE.org project. In addition, I'm using i3 (if it matters what my login shell is). I have updated my system to 20160911-0 as well, and the same issue happens (I just titled it the version that I'm fairly sure it broke). -- You are receiving this mail because: You are on the CC list for the bug.