[Bug 1714222] [NEW] Cannot pull from gcrypt git remote since 17.04: No secret key

[Alejandro R. Mosteo]

Public bug reported:

Since I upgraded to 17.04 my gcrypted remotes can't be pulled from. I
get this error:

$ git pull
gpg: Oops: keyid_from_fingerprint: no pubkey

This might or not be related to bug 1647364.

Doing the same in a 16.04 schroot works as expected.

While attempting to gain some information I tried to create a repository
from scratch:

1. Create empty repo somewhere (in my case bitbucket)
2. Create empty local repository, add the gcrypt remote:

$ git remote add origin gcrypt::git at bitbucket.org:amosteo/test.git

3. Make a local commit and push it (this worked, I got a pop-up window
instead of being prompted in the command line like in <17.04):

$ git push --set-upstream origin master
gcrypt: Repository not found: git at bitbucket.org:amosteo/test.git
gcrypt: Setting up new repository
gcrypt: Remote ID is :id:o+7umMvaOYf/7p48+Img
Counting objects: 3, done.
Total 3 (delta 0), reused 0 (delta 0)
gcrypt: Encrypting to: --throw-keyids --default-recipient-self
gcrypt: Requesting manifest signature
To bitbucket.org:amosteo/test.git
 * [new branch]      master -> master
Branch master set up to track remote branch master from origin.

4. Doing a pull fails again (same happens for push):

$ git pull
gcrypt: Decrypting manifest
gpg: decryption failed: No secret key
gcrypt: Failed to decrypt manifest!

Note that this error is different to the one in my old repositories, but
I think it's simply because I have this in the older repositories
config:

gcrypt.participants=<my address>
gcrypt.publish-participants=true

Any advice on how to further investigate this is welcome. Some version
details:

$ lsb_release -rd
Description:    Ubuntu 17.04
Release:        17.04

$ apt policy git-remote-gcrypt 
git-remote-gcrypt:
  Installed: 1.0.1-1

This happens to me in several machines (all the ones that I have
upgraded to 17.04).

** Affects: git-remote-gcrypt (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to pinentry in Ubuntu.
https://bugs.launchpad.net/bugs/1714222

Title:
  Cannot pull from gcrypt git remote since 17.04: No secret key

Status in git-remote-gcrypt package in Ubuntu:
  New

Bug description:
  Since I upgraded to 17.04 my gcrypted remotes can't be pulled from. I
  get this error:

  $ git pull
  gpg: Oops: keyid_from_fingerprint: no pubkey

  This might or not be related to bug 1647364.

  Doing the same in a 16.04 schroot works as expected.

  While attempting to gain some information I tried to create a
  repository from scratch:

  1. Create empty repo somewhere (in my case bitbucket)
  2. Create empty local repository, add the gcrypt remote:

  $ git remote add origin gcrypt::git at bitbucket.org:amosteo/test.git

  3. Make a local commit and push it (this worked, I got a pop-up window
  instead of being prompted in the command line like in <17.04):

  $ git push --set-upstream origin master
  gcrypt: Repository not found: git at bitbucket.org:amosteo/test.git
  gcrypt: Setting up new repository
  gcrypt: Remote ID is :id:o+7umMvaOYf/7p48+Img
  Counting objects: 3, done.
  Total 3 (delta 0), reused 0 (delta 0)
  gcrypt: Encrypting to: --throw-keyids --default-recipient-self
  gcrypt: Requesting manifest signature
  To bitbucket.org:amosteo/test.git
   * [new branch]      master -> master
  Branch master set up to track remote branch master from origin.

  4. Doing a pull fails again (same happens for push):

  $ git pull
  gcrypt: Decrypting manifest
  gpg: decryption failed: No secret key
  gcrypt: Failed to decrypt manifest!

  Note that this error is different to the one in my old repositories,
  but I think it's simply because I have this in the older repositories
  config:

  gcrypt.participants=<my address>
  gcrypt.publish-participants=true

  Any advice on how to further investigate this is welcome. Some version
  details:

  $ lsb_release -rd
  Description:    Ubuntu 17.04
  Release:        17.04

  $ apt policy git-remote-gcrypt 
  git-remote-gcrypt:
    Installed: 1.0.1-1

  This happens to me in several machines (all the ones that I have
  upgraded to 17.04).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/git-remote-gcrypt/+bug/1714222/+subscriptions