FYI, Pete 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. git tag -u 'For git' -s some-tag Sincerely, Gary --- On Tue, 11/18/08, Pete Harlan <pgit@xxxxxxxxxxxx> wrote: > From: Pete Harlan <pgit@xxxxxxxxxxxx> > Subject: Re: "secret key not available". "unable to sign the tag". > To: garyyang6@xxxxxxxxx > Date: Tuesday, November 18, 2008, 5:44 PM > Hi Gary, > > No output doesn't mean anything is wrong, just that my > suggestion wasn't > useful. > > I saw from your other post that you use C-shell. I tried > things here > using C-shell and it all worked as expected. > > One odd-looking thing is that when you show it working from > the > command-line it says: > > > > > You need a passphrase to unlock the secret > key for > > > > user: "Gary Yang (For git.) > > > > <garyyang6@xxxxxxxxx>" > > whereas when you show it not working within Git it says: > > > gpg: skipped `Gary Yang > > <garyyang6@xxxxxxxxx>': secret key not > > available > > gpg: signing failed: secret key not available > > which leads me to believe that you have two similarly-named > keys, and > that the command-line gpg is finding the one that has > "For git" in the > name, but git is finding the one that doesn't, and this > second one > doesn't have a secret key available. > > If you try specifying the first key to git: > > git tag -u 'For git' -s some-tag > > does that work? > > --Pete > > > Gary Yang wrote: > > Hi Pete, > > > > I got no output of the commands you told me. That > means I have no environment setup. Can you please tell me > what kind of environment variables need to setup? Thank you > very much! > > > >> env | grep -i gnupg > >> env | grep -i gpg > >> env | grep -i pgp > > > > > > Gary > > > > --- On Tue, 11/18/08, Pete Harlan > <pgit@xxxxxxxxxxxx> wrote: > > > >> From: Pete Harlan <pgit@xxxxxxxxxxxx> > >> Subject: Re: "secret key not available". > "unable to sign the tag". > >> To: garyyang6@xxxxxxxxx > >> Date: Tuesday, November 18, 2008, 5:16 PM > >> Gary Yang wrote: > >>> Hi Pete, > >>> > >>> What I should export? Do you have any idea? > >> Hi Gary, > >> > >> I'd look for anything that says gnupg or gpg > in the > >> environment. > >> > >> env | grep -i gnupg > >> env | grep -i gpg > >> env | grep -i pgp > >> > >> I'm afriad it's not much of an idea. If > the above > >> don't match > >> anything, I don't know what to suggest. > >> > >> Good luck, > >> > >> --Pete > >> > >> > >> > >>> > >>> Thank you, > >>> > >>> > >>> Gary > >>> > >>> > >>> > >>> > >>> --- On Tue, 11/18/08, Pete Harlan > >> <pgit@xxxxxxxxxxxx> wrote: > >>>> From: Pete Harlan > <pgit@xxxxxxxxxxxx> > >> Subject: Re: "secret key not > >>>> available". "unable to sign the > >> tag". To: garyyang6@xxxxxxxxx Date: > >>>> Tuesday, November 18, 2008, 2:18 PM Gary > Yang > >> wrote: > >>>>> Peter, > >>>>> > >>>>> The gpg works. But, git tag dose not > work. Any > >> idea? > >>>> Could gpg be using something from your > environment > >> that you're not > >>>> exporting, so git can't see it? > >>>> > >>>> --Pete > >>>> > >>>> > >>>>> gpg --detach-sign foo.bar gpg: > WARNING: using > >> insecure memory! > >>>>> gpg: please see > http://www.gnupg.org/faq.html > >> for more > >>>> information > >>>>> You need a passphrase to unlock the > secret key > >> for user: "Gary > >>>>> Yang (For git.) > >>>> <garyyang6@xxxxxxxxx>" > >>>>> 1024-bit DSA key, ID A3F6A45E, created > >> 2008-11-14 > >>>>> Enter passphrase: > >>>>> > >>>>> > >>>>> [garyyang6@svdclc313 > ~/git-repository]% > >>>>> > >>>>> > >>>>> It successfully signed. > >>>>> > >>>>> > >>>>> Gary > >>>>> > > > > > > -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
