{"thread":{"id":"16387","subject":"Re: \"secret key not available\". \"unable to sign the tag\".","startedAt":"2008-11-19T02:19:26Z","lastAt":"2008-11-19T02:19:26Z","messageCount":1,"participants":["Gary Yang"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"96121","messageId":"206215.61260.qm@web37901.mail.mud.yahoo.com","threadId":"16387","inReplyTo":"49236F67.6080807@pcharlan.com","subject":"Re: \"secret key not available\". \"unable to sign the tag\".","fromName":"Gary Yang","fromEmail":"garyyang6@yahoo.com","sentAt":"2008-11-19T02:19:26Z","receivedAt":"2008-11-19T02:19:26Z","isPatch":false,"sender":{"key":"garyyang6@yahoo.com","avatar":null},"body":"FYI,\n\nPete helped me solved the problem. Somehow I got two gpg keys. Pete discovered that and suggested me the proper command to tag the code. I am going to figure out how to remove the extra key. Many thanks to Pete.\n\ngit tag -u 'For git' -s some-tag\n\nSincerely,\n\n\nGary\n\n\n\n--- On Tue, 11/18/08, Pete Harlan <pgit@pcharlan.com> wrote:\n\n> From: Pete Harlan <pgit@pcharlan.com>\n> Subject: Re: \"secret key not available\". \"unable to sign the tag\".\n> To: garyyang6@yahoo.com\n> Date: Tuesday, November 18, 2008, 5:44 PM\n> Hi Gary,\n> \n> No output doesn't mean anything is wrong, just that my\n> suggestion wasn't\n> useful.\n> \n> I saw from your other post that you use C-shell.  I tried\n> things here\n> using C-shell and it all worked as expected.\n> \n> One odd-looking thing is that when you show it working from\n> the\n> command-line it says:\n> \n> > > > You need a passphrase to unlock the secret\n> key for\n> > > > user: \"Gary Yang (For git.)\n> > > > <garyyang6@yahoo.com>\"\n> \n> whereas when you show it not working within Git it says:\n> \n> > gpg: skipped `Gary Yang\n> > <garyyang6@yahoo.com>': secret key not\n> > available\n> > gpg: signing failed: secret key not available\n> \n> which leads me to believe that you have two similarly-named\n> keys, and\n> that the command-line gpg is finding the one that has\n> \"For git\" in the\n> name, but git is finding the one that doesn't, and this\n> second one\n> doesn't have a secret key available.\n> \n> If you try specifying the first key to git:\n> \n>   git tag -u 'For git' -s some-tag\n> \n> does that work?\n> \n> --Pete\n> \n> \n> Gary Yang wrote:\n> > Hi Pete,\n> > \n> > I got no output of the commands you told me. That\n> means I have no environment setup. Can you please tell me\n> what kind of environment variables need to setup? Thank you\n> very much!\n> > \n> >> env | grep -i gnupg\n> >> env | grep -i gpg\n> >> env | grep -i pgp\n> > \n> > \n> > Gary\n> > \n> > --- On Tue, 11/18/08, Pete Harlan\n> <pgit@pcharlan.com> wrote:\n> > \n> >> From: Pete Harlan <pgit@pcharlan.com>\n> >> Subject: Re: \"secret key not available\".\n> \"unable to sign the tag\".\n> >> To: garyyang6@yahoo.com\n> >> Date: Tuesday, November 18, 2008, 5:16 PM\n> >> Gary Yang wrote:\n> >>> Hi Pete,\n> >>>\n> >>> What I should export? Do you have any idea?\n> >> Hi Gary,\n> >>\n> >> I'd look for anything that says gnupg or gpg\n> in the\n> >> environment.\n> >>\n> >> env | grep -i gnupg\n> >> env | grep -i gpg\n> >> env | grep -i pgp\n> >>\n> >> I'm afriad it's not much of an idea.  If\n> the above\n> >> don't match\n> >> anything, I don't know what to suggest.\n> >>\n> >> Good luck,\n> >>\n> >> --Pete\n> >>\n> >>\n> >>\n> >>>\n> >>> Thank you,\n> >>>\n> >>>\n> >>> Gary\n> >>>\n> >>>\n> >>>\n> >>>\n> >>> --- On Tue, 11/18/08, Pete Harlan\n> >> <pgit@pcharlan.com> wrote:\n> >>>> From: Pete Harlan\n> <pgit@pcharlan.com>\n> >> Subject: Re: \"secret key not\n> >>>> available\". \"unable to sign the\n> >> tag\". To: garyyang6@yahoo.com Date:\n> >>>> Tuesday, November 18, 2008, 2:18 PM Gary\n> Yang\n> >> wrote:\n> >>>>> Peter,\n> >>>>>\n> >>>>> The gpg works. But, git tag dose not\n> work. Any\n> >> idea?\n> >>>> Could gpg be using something from your\n> environment\n> >> that you're not \n> >>>> exporting, so git can't see it?\n> >>>>\n> >>>> --Pete\n> >>>>\n> >>>>\n> >>>>> gpg --detach-sign foo.bar gpg:\n> WARNING: using\n> >> insecure memory! \n> >>>>> gpg: please see\n> http://www.gnupg.org/faq.html\n> >> for more\n> >>>> information\n> >>>>> You need a passphrase to unlock the\n> secret key\n> >> for user: \"Gary\n> >>>>> Yang (For git.)\n> >>>> <garyyang6@yahoo.com>\"\n> >>>>> 1024-bit DSA key, ID A3F6A45E, created\n> >> 2008-11-14\n> >>>>> Enter passphrase:\n> >>>>>\n> >>>>>\n> >>>>> [garyyang6@svdclc313\n> ~/git-repository]%\n> >>>>>\n> >>>>>\n> >>>>> It successfully signed.\n> >>>>>\n> >>>>>\n> >>>>> Gary\n> >>>>>\n> > \n> > \n> >\n\n\n      \n"}]}