If you are stuck, and you want to give me a brevette promotion to committer, I'll make some time to try and cook this in the next few evenings.
On Mon, Oct 26, 2009 at 12:32 PM, Grant Ingersoll <[email protected]>wrote: > What happens if you run with mvn -e -X > > Here's how I've been running: > mvn -Prelease,mahout_release release:prepare // I've updated the Wiki > > In my settings.xml, I have: > <profile> > <id>mahout_release</id> > > <properties> > <gpg.passphrase>*****</gpg.passphrase> > <deploy.altRepository>mahout.releases::default::scp:// > people.apache.org/home/gsingers/public_html/staging-repo > /mahout</deploy.altRepository> > <username>...</username> > <user.name>...</user.name> > <deploy.url>scp://people.apache.org/home/gsingers/public_html/ > staging-repo/mahout</deploy.url> > </properties> > </profile> > > > http://www.google.com/search?q=gpg%3A+signing+failed%3A+General+Error&ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla:en-US:official&client=firefox-a > might > be of interest. > > Sean, can you summarize your errors on your local machine? I don't want to > rely on p.a.o for doing builds. > > Also, are you able to sign other files on your machine (foo.txt) using GPG, > as in: gpg -s foo.txt > > What version of GPG do you have? > > > > On Oct 26, 2009, at 7:58 AM, Sean Owen wrote: > > Ah, I see how that works now. I was using the apache-release profile >> but it also needed to be configured with <gpg.keyname> as well. >> >> (Actually I found I needed to run my own gpg-agent too -- "eval >> 'gpg-agent --daemon'" -- anyone think that sounds wrong? checking >> before I add it to the wiki.) >> >> I now get: >> >> [INFO] [INFO] [gpg:sign {execution: default}] >> [INFO] gpg: WARNING: "--no-use-agent" is an obsolete option - it has no >> effect >> [INFO] Warning: using insecure memory! >> >> You need a passphrase to unlock the secret key for >> user: "Sean Owen <[email protected]>" >> 4096-bit RSA key, ID 021F6670, created 2009-10-16 >> >> [INFO] gpg: cancelled by user >> [INFO] gpg: skipped "Sean Owen": General error >> [INFO] gpg: signing failed: General error >> >> >> Is that not the right keyname? that previously worked locally (where I >> had to supply the passphrase manually). I tried "Sean Owen" too with >> the same result. >> >> So our build instructions also talk about this mahout_release profile, >> which doesn't seem to be used? is that out of date? >> >> >> We seem to be stuck just in the release process in three different >> ways. Grant is stuck on long-mode and the release profile or >> something. I am both stuck on this gpg issue on people.apache.org, and >> on some possible svn.apache.org problem locally. >> >> I've done about a full day of head-banging on this and am ready to >> throw in the towel. If we are truly dead in the water with the release >> process... is there any kind soul to appeal to here? >> >> >> >> On Mon, Oct 26, 2009 at 7:21 AM, Isabel Drost <[email protected]> wrote: >> >>> On Mon Sean Owen <[email protected]> wrote: >>> >>>> I don't know enough about GPG to know whether I should be seeing this >>>> at all (since my passphrase is already in settings.xml?) or how else >>>> this is supposed to work? does anyone see this? >>>> >>> >>> You shouldn't be asked for the password if you set it in your >>> settings.xml and are using the profile you set it in for building. >>> >>> So, if your setting.xml says: >>> >>> <profiles> >>> <profile> >>> <id>apache-release</id> >>> <properties> >>> <gpg.passphrase>*********</gpg.passphrase> >>> </properties> >>> </profile> >>> </profiles >>> >>> and you are building with mvn -Papache-release <goal> you shouldn't be >>> asked for the password. >>> >>> Isabel >>> >>> >
