It's kind of hard to do release management without commit access. I've done
releases for two other Apache projects, but I think I've sent along all the
suggestions I can make from the sidelines.
On Mon, Oct 26, 2009 at 7:58 AM, Sean Owen <sro...@gmail.com> 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 <sro...@apache.org>"
> 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 <isa...@apache.org> wrote:
> > On Mon Sean Owen <sro...@gmail.com> 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
> >
>
