I just noticed you can do that without editing the pass script: just call bash -x `which pass` insert test
On 14.03.2015 12:02, Lenz Weber wrote: > Okay, > I've got one more idea. > > Edit your pass script, at the top insert > `set -o xtrace` in the line after `set -o pipefail` > > Now every command that is executed by pass will be output to the > command line. > > Then just do your gpg insert again - after entering both passwords, > it will print your failing gpg call. > > Maybe that will give us an indication of what might be wrong. > > Regards, > Lenz > > > On 14.03.2015 11:50, Matthias Beyer wrote: >> Hi, >> >> On 14-03-2015 11:41:57, Lenz Weber wrote: >>> Phew. That's a bummer. >>> >>> Only thing I can think of is that pass is using another gpg >>> binary than you are on the cli that is not aware of your key. >>> >>> Do you have any combination of gpg1/gpg2/gpg2.1 installed? >> >> I have only a gpg2 binary. I had installed gnupg1compat which is a >> wrapper so gpg2 can be called by calling "gpg", but I removed it as >> it did not work, too. >> >> gpg2 --version gives 2.1.2 >> >>> >>> If so: do you have a gpg2 binary? Is your key both in the output >>> of `gpg -k` and `gpg2 -k`? >> >> gpg2 -k | grep [email protected] lists my key, so yes. >> >>> >>> Other than that: anyone else got an idea on this? >>> >> > _______________________________________________ > Password-Store mailing list > [email protected] > http://lists.zx2c4.com/mailman/listinfo/password-store > _______________________________________________ Password-Store mailing list [email protected] http://lists.zx2c4.com/mailman/listinfo/password-store
