Ah I guess whatever notes I found on this problem were misleading, sounds like you've shown it is a path length issue. Sounds like the possible ways forward are...
- Can you just do release builds from /tmp or something like /mahout? - Can we switch to .zip packaging? I don't particularly care about tar.gz vs .zip - Does a newer tar binary do the trick? Meantime, I'm figuring out why gpg doesn't work out on p.a.o. Benson if that was actually an offer to try to do a release here... may well be worth taking you up on it if none of this is working. On Mon, Oct 26, 2009 at 12:35 PM, Grant Ingersoll <[email protected]> wrote: > I get past the TAR problem when I check out into /tmp. It really is just an > issue w/ long names. I'm on a Mac, Snow Leopard. I don't know what to do > about TAR. > > My tar is: > tar --version > tar (GNU tar) 1.16.1 > Copyright (C) 2006 Free Software Foundation, Inc. > This is free software. You may redistribute copies of it under the terms of > the GNU General Public License <http://www.gnu.org/licenses/gpl.html>. > There is NO WARRANTY, to the extent permitted by law. > > Written by John Gilmore and Jay Fenlason. > > > I see there is a newer version, so I will try updating to that. > > -Grant > > > 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 >>> > > -------------------------- > Grant Ingersoll > http://www.lucidimagination.com/ > > Search the Lucene ecosystem (Lucene/Solr/Nutch/Mahout/Tika/Droids) using > Solr/Lucene: > http://www.lucidimagination.com/search > >
