You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mahout.apache.org by Sean Owen <sr...@gmail.com> on 2009/10/20 17:11:59 UTC
Release help, stuck on gpg-sign?
release:prepare is hanging for me at...
[INFO] [INFO] [gpg:sign {execution: default}]
I dont' think this is to do with the GPG signing I just added, as it
shows up even if I remove that bit. Anyone more familiar with this? is
my settings.xml OK?
<?xml version="1.0" encoding="UTF-8"?>
<settings>
<profiles>
<profile>
<id>mahout_release</id>
<properties>
<gpg.passphrase>[my passphrase for GPG, not my key]</gpg.passphrase>
<deploy.altRepository>mahout.releases::default::scp://people.apache.org/home/srowen/public_html/staging-repo/mahout</deploy.altRepository>
<username>srowen</username>
<deploy.url>scp://people.apache.org/home/srowen/public_html/staging-repo/mahout</deploy.url>
</properties>
</profile>
</profiles>
</settings>
Re: Release help, stuck on gpg-sign?
Posted by Sean Owen <sr...@gmail.com>.
I see, I had done that already. So when those instructions refer to
updating Maven's KEYS, they don't mean it's literally necessary, for
deploying a Maven-based project?
In that case I don't know what's wrong. Grant could I ask you to try
the release, to at least narrow it down to a local problem versus
otherwise?
Sean
On Wed, Oct 21, 2009 at 7:23 AM, Isabel Drost <is...@apache.org> wrote:
> On Tue, 20 Oct 2009 23:53:42 +0100
> Sean Owen <sr...@gmail.com> wrote:
>
>> Thanks, this is probably vital. I had not seen this.
>>
>> Let me ask questions here before taking them to the Apache staff --
>>
>> I am unable to update
>> https://svn.apache.org/repos/asf/maven/project/KEYS -- get a 403
>
> The url for code signing keys for Mahout should be
>
> https://svn.apache.org/repos/asf/lucene/mahout/trunk/KEYS
>
>
> Isabel
>
>
Re: Release help, stuck on gpg-sign?
Posted by Isabel Drost <is...@apache.org>.
On Tue, 20 Oct 2009 23:53:42 +0100
Sean Owen <sr...@gmail.com> wrote:
> Thanks, this is probably vital. I had not seen this.
>
> Let me ask questions here before taking them to the Apache staff --
>
> I am unable to update
> https://svn.apache.org/repos/asf/maven/project/KEYS -- get a 403
The url for code signing keys for Mahout should be
https://svn.apache.org/repos/asf/lucene/mahout/trunk/KEYS
Isabel
Re: Release help, stuck on gpg-sign?
Posted by Jukka Zitting <ju...@gmail.com>.
Hi,
On Wed, Oct 21, 2009 at 12:29 PM, Grant Ingersoll <gs...@apache.org> wrote:
> You shouldn't be uploading to the ASF repo that way, I think. Just put them
> up in your public_html.
As you noted later, the Nexus server supports staged releases, so you
can "mvn deploy" (or "mvn release:perform" if you're using the release
plugin) to repository.apache.org that will automatically collect all
new org.apache.mahout artifacts into a new staged repository.
You can find this staged repository by first logging in to
https://repository.apache.org/ (the login link is in the top right
corner, use your svn username and password) and then looking for the
"Enterprise / Staging" link on the left.
There'll be an entry for "org.apache.mahout", under which you can find
the newly deployed artifacts as an "open" collection. The "open" state
means that any additional Mahout deployments will be added to this
collection until you explicitly "close" it (use a right click). Once
you close the staged repository, it becomes write-protected and you
can include a link to it for review in the release vote. If the vote
passes, you can "promote" the repository (again through a right
click), which will get the release artifacts published on Maven
central.
See http://markmail.org/message/lksyayquaysguyzq for an example
release vote from Jackrabbit, where I'm referring to a such a staged
Maven repository.
If your project source archive (the "project" package) is deployed to
the repository, then you don't necessarily need to upload the release
candidate also to your public_html directory as people can get it also
from the staged Maven repository. But since Apache policy mandates
that source archives of all releases get posted to
www.apache.org/dist, you'll still need to copy those packages to
people.apache.org at some point. In Jackrabbit we copy only the
project source archive and a few standalone binaries to the
public_html directory that'll eventually be copied to
www.apache.org/dist. Other release artifacts are made available only
through the Maven repository.
BR,
Jukka Zitting
Re: Release help, stuck on gpg-sign?
Posted by Grant Ingersoll <gs...@apache.org>.
Finally found some time to try. Will report back
On Oct 22, 2009, at 2:21 PM, Sean Owen wrote:
> Same results.
>
> Grant can you try this?
>
> Is there a way for me to force use of the US servers?
>
> On Thu, Oct 22, 2009 at 4:07 PM, Sean Owen <sr...@gmail.com> wrote:
>> Yep, in London. I will try this shortly. Thanks Jukka!
Re: Release help, stuck on gpg-sign?
Posted by Sean Owen <sr...@gmail.com>.
This is undoubtedly my misunderstanding. I suppose I saw that the
dependencies in question were from the core module so I put it there.
If you know it should be in the parent module, by all means, move the
stanza.
On Fri, Oct 23, 2009 at 10:06 PM, Grant Ingersoll <gs...@apache.org> wrote:
> Why was gpg-plugin just added to the core pom and not higher up? All the
> artifacts produced need to be signed.
>
> -Grant
>
Re: Release help, stuck on gpg-sign?
Posted by Sean Owen <sr...@gmail.com>.
This could again be my misunderstanding. This was my attempt to get
all artifacts signed and this appeared to do it. But if it was already
in place via the parent pom, yes, I doubt it actually does anything.
Let us observe the result -- seems like we're making progress in
integrating with the apache-release profile properly in several
places, so perhaps that will happen to work now.
On Mon, Oct 26, 2009 at 7:15 AM, Isabel Drost <is...@apache.org> wrote:
> On Fri Grant Ingersoll <gs...@apache.org> wrote:
>
>> Why was gpg-plugin just added to the core pom and not higher up?
>> All the artifacts produced need to be signed.
>
> The gpg-plugin is part of the apache-root-pom. See also:
>
> http://svn.apache.org/viewvc/maven/pom/trunk/asf/pom.xml?revision=766951&view=markup
>
> http://maven.apache.org/developers/release/releasing.html
>
> If all our artifacts inherit from that, they should all get signed,
> right?
>
> Isabel
>
Re: Release help, stuck on gpg-sign?
Posted by Isabel Drost <is...@apache.org>.
On Fri Grant Ingersoll <gs...@apache.org> wrote:
> Why was gpg-plugin just added to the core pom and not higher up?
> All the artifacts produced need to be signed.
The gpg-plugin is part of the apache-root-pom. See also:
http://svn.apache.org/viewvc/maven/pom/trunk/asf/pom.xml?revision=766951&view=markup
http://maven.apache.org/developers/release/releasing.html
If all our artifacts inherit from that, they should all get signed,
right?
Isabel
Re: Release help, stuck on gpg-sign?
Posted by Grant Ingersoll <gs...@apache.org>.
Why was gpg-plugin just added to the core pom and not higher up? All
the artifacts produced need to be signed.
-Grant
On Oct 22, 2009, at 2:21 PM, Sean Owen wrote:
> Same results.
>
> Grant can you try this?
>
> Is there a way for me to force use of the US servers?
>
> On Thu, Oct 22, 2009 at 4:07 PM, Sean Owen <sr...@gmail.com> wrote:
>> Yep, in London. I will try this shortly. Thanks Jukka!
Re: Release help, stuck on gpg-sign?
Posted by Sean Owen <sr...@gmail.com>.
Same results.
Grant can you try this?
Is there a way for me to force use of the US servers?
On Thu, Oct 22, 2009 at 4:07 PM, Sean Owen <sr...@gmail.com> wrote:
> Yep, in London. I will try this shortly. Thanks Jukka!
Re: Release help, stuck on gpg-sign?
Posted by Sean Owen <sr...@gmail.com>.
Got it so everything else is basically looking right
On Thu, Oct 22, 2009 at 4:05 PM, Jukka Zitting <ju...@gmail.com> wrote:
> About the svn problems you were seeing earlier: Are you located in
> Europe? The sync delay of the local svn.apache.org mirror causes such
> problems every now and then. Luckily the release plugin can fairly
> well deal with such problems. Simply rerun "mvn release:prepare" a bit
> later, possible with an "svn update" in between, to continue the
> process.
Yep, in London. I will try this shortly. Thanks Jukka!
Re: Release help, stuck on gpg-sign?
Posted by Jukka Zitting <ju...@gmail.com>.
Hi,
On Thu, Oct 22, 2009 at 2:27 PM, Sean Owen <sr...@gmail.com> wrote:
> Are we supposed to run from the parent module, or root level? which
> pom.xml should operate the build?
The root level.
> I'm definitely seeing errors about ${project.version} not being
The INFO messages about "Ignoring artifact version update for
expression: ${project.version}" are expected. In a multimodule build
the release plugin will automatically update the versions of
dependencies that are included in the same build. If such a dependency
is already declared as having version ${project.version}, then there's
no need for the release plugin to explicitly change that setting. The
info message is just printed to highlight this point.
> What is '-Papache-release' -- I'm trying to figure out whether this is
> supposed to be set or not. Some people mentioned this, not seeing it
> in docs.
That comes from the release profile settings in the latest
org.apache:apache parent POM that Mahout is now using. See
http://repo2.maven.org/maven2/org/apache/apache/6/apache-6.pom for the
full details.
> I don't see that we have any instance of maven-release-plugin -- should we?
Things like the release plugin settings mentioned by Benson earlier
are already configured in that parent POM, so unless you explicitly
want to override things, there's no need to have such settings in
Mahout.
> I have Subversion 1.6.2 FWIW.
About the svn problems you were seeing earlier: Are you located in
Europe? The sync delay of the local svn.apache.org mirror causes such
problems every now and then. Luckily the release plugin can fairly
well deal with such problems. Simply rerun "mvn release:prepare" a bit
later, possible with an "svn update" in between, to continue the
process.
BR,
Jukka Zitting
Re: Release help, stuck on gpg-sign?
Posted by Sean Owen <sr...@gmail.com>.
To be more clear on the project.version thing, I see:
[INFO] Updating mahout-core to 0.2
[INFO] Ignoring artifact version update for expression: ${project.version}
[INFO] Transforming 'Mahout utilities'...
[INFO] Updating mahout-core to 0.2
[INFO] Ignoring artifact version update for expression: ${project.version}
[INFO] Transforming 'Mahout examples'...
[INFO] Updating mahout-core to 0.2
[INFO] Ignoring artifact version update for expression: ${project.version}
[INFO] Updating mahout-core to 0.2
[INFO] Ignoring artifact version update for expression: ${project.version}
[INFO] Updating mahout-utils to 0.2
[INFO] Ignoring artifact version update for expression: ${project.version}
On Thu, Oct 22, 2009 at 1:27 PM, Sean Owen <sr...@gmail.com> wrote:
> OK these questions may be for mahout-dev, maybe Grant who set this up --
>
> Are we supposed to run from the parent module, or root level? which
> pom.xml should operate the build? I'm definitely seeing errors about
> ${project.version} not being
>
> What is '-Papache-release' -- I'm trying to figure out whether this is
> supposed to be set or not. Some people mentioned this, not seeing it
> in docs.
>
> I don't see that we have any instance of maven-release-plugin -- should we?
>
> I have Subversion 1.6.2 FWIW.
>
> On Thu, Oct 22, 2009 at 2:37 AM, Benson Margulies <bi...@gmail.com> wrote:
>> Maven always knows how to expand ${project.version} where it is allowed,
>> which does not include inside of <parent/> elements. It's a basic maven
>> feature.
>
Re: Release help, stuck on gpg-sign?
Posted by Jukka Zitting <ju...@gmail.com>.
Hi,
On Wed, Oct 21, 2009 at 6:26 PM, Sean Owen <sr...@gmail.com> wrote:
> I'm at a loss, I backed up and made sure to use the steps and config
> in the Mahout wiki. I am still stuck on gpg:sign.
The apache-release profile expects to find your passphrase in the
${gpg.passphrase} build property. The recommended way to set it is to
add it to your ~/.m2/settings.xml configuration file like this:
<settings>
...
<profiles>
<profile>
<id>apache-release</id>
<properties>
<gpg.passphrase> <!-- YOUR KEY PASSPHRASE --> </gpg.passphrase>
</properties>
</profile>
</profiles>
...
</settings>
Then the release sequence of "mvn release:prepare" followed by "mvn
release:perform" will automatically sign the release artifacts using
your GPG key with the configured passphrase.
If you are having trouble with the Maven settings or the release
plugin, you can test the basic functionality by explicitly specifying
the passphrase on the command line:
mvn clean install -Papache-release -Dgpg.passphrase="your passphrase"
BR,
Jukka Zitting
Re: Release help, stuck on gpg-sign?
Posted by Grant Ingersoll <gs...@apache.org>.
On Oct 22, 2009, at 8:27 AM, Sean Owen wrote:
> OK these questions may be for mahout-dev, maybe Grant who set this
> up --
>
> Are we supposed to run from the parent module, or root level? which
> pom.xml should operate the build? I'm definitely seeing errors about
> ${project.version} not being
>
> What is '-Papache-release' -- I'm trying to figure out whether this is
> supposed to be set or not. Some people mentioned this, not seeing it
> in docs.
Yes, I believe it should be. That was added post 0.1. It tells Maven
to use the release profile.
I will try today.
Re: Release help, stuck on gpg-sign?
Posted by Sean Owen <sr...@gmail.com>.
OK these questions may be for mahout-dev, maybe Grant who set this up --
Are we supposed to run from the parent module, or root level? which
pom.xml should operate the build? I'm definitely seeing errors about
${project.version} not being
What is '-Papache-release' -- I'm trying to figure out whether this is
supposed to be set or not. Some people mentioned this, not seeing it
in docs.
I don't see that we have any instance of maven-release-plugin -- should we?
I have Subversion 1.6.2 FWIW.
On Thu, Oct 22, 2009 at 2:37 AM, Benson Margulies <bi...@gmail.com> wrote:
> Maven always knows how to expand ${project.version} where it is allowed,
> which does not include inside of <parent/> elements. It's a basic maven
> feature.
Re: Release help, stuck on gpg-sign?
Posted by Benson Margulies <bi...@gmail.com>.
Maven always knows how to expand ${project.version} where it is allowed,
which does not include inside of <parent/> elements. It's a basic maven
feature.
It is possible that you don't have the right pom content for the release
plugin, and have hit the remote tagging mess. And/or you don't have an
up-to-date svn client on your machine.
Here's what CXF uses:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-release-plugin</artifactId>
<version>2.0-beta-9</version>
<configuration>
<tagBase>https://svn.apache.org/repos/asf/cxf/tags
</tagBase>
<useReleaseProfile>false</useReleaseProfile>
<preparationGoals>clean install</preparationGoals>
<goals>deploy</goals>
<arguments>-Prelease,deploy</arguments>
<autoVersionSubmodules>true</autoVersionSubmodules>
</configuration>
</plugin>
and here's what we use Internally at Basis:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-release-plugin</artifactId>
<version>2.0-beta-9</version>
<configuration>
<tagBase>
http://svn.basistech.net/engineering/etrog/tags</tagBase>
<useReleaseProfile>true</useReleaseProfile>
<releaseProfiles>release</releaseProfiles>
<remoteTagging>true</remoteTagging>
<preparationGoals>clean install</preparationGoals>
<goals>deploy</goals>
<autoVersionSubmodules>true</autoVersionSubmodules>
<allowTimestampedSnapshots>true</allowTimestampedSnapshots>
</configuration>
</plugin>
On Wed, Oct 21, 2009 at 9:10 PM, Sean Owen <sr...@gmail.com> wrote:
> OK may have spied a related problem -- the build process doesn't know
> how to expand the token ${project.version} -- where should this be
> defined? i don't see it. Is it somehow supposed to be on the command
> line?
>
> On Thu, Oct 22, 2009 at 2:04 AM, Sean Owen <sr...@gmail.com> wrote:
> > Here's a new one, wondering if anyone has seen this and sees the easy
> > answer, while I research it.
>
Re: Release help, stuck on gpg-sign?
Posted by Sean Owen <sr...@gmail.com>.
OK may have spied a related problem -- the build process doesn't know
how to expand the token ${project.version} -- where should this be
defined? i don't see it. Is it somehow supposed to be on the command
line?
On Thu, Oct 22, 2009 at 2:04 AM, Sean Owen <sr...@gmail.com> wrote:
> Here's a new one, wondering if anyone has seen this and sees the easy
> answer, while I research it.
Re: Release help, stuck on gpg-sign?
Posted by Sean Owen <sr...@gmail.com>.
Here's a new one, wondering if anyone has seen this and sees the easy
answer, while I research it.
I get this at the tagging phase...
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Unable to tag SCM
Provider message:
The svn tag command failed.
Command output:
svn: No such revision 828262
If I rerun release:prepare some short time later...
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Unable to tag SCM
Provider message:
The svn tag command failed.
Command output:
svn: Path 'https://svn.apache.org/repos/asf/lucene/mahout/tags/mahout-0.2'
does not exist in revision 828265
I've tried a rollback.
On Thu, Oct 22, 2009 at 12:55 AM, Sean Owen <sr...@gmail.com> wrote:
> It was either the <gpg.keyname>, or Jukka's suggestion to add the
> apache-release profile. I get through key signing now. Thanks! I'll
> update our wiki accordingly.
>
> Now crossing fingers that the rest goes smoothly...
>
> On Wed, Oct 21, 2009 at 11:20 PM, Benson Margulies
> <bi...@gmail.com> wrote:
>> Do you have the right stuff in your .m2/settings.xml?
>>
>> Here is the page I wrote for XmlSchema that might shed some light:
>>
>> When I do apache releases that are not targeted at Nexus, I use:
>>
>> <profile>
>> <id>release</id>
>> <properties>
>> <gpg.passphrase>...my passphrase....</gpg.passphrase>
>> <gpg.keyname>bimargulies@apache.org</gpg.keyname>
>> <deploy.altRepository>apache.releases::default::scp://
>> people.apache.org/home/bimargulies/public_html/maven_staging
>> </deploy.altRepository>
>> </properties>
>> </profile>
>>
>
Re: Release help, stuck on gpg-sign?
Posted by Sean Owen <sr...@gmail.com>.
It was either the <gpg.keyname>, or Jukka's suggestion to add the
apache-release profile. I get through key signing now. Thanks! I'll
update our wiki accordingly.
Now crossing fingers that the rest goes smoothly...
On Wed, Oct 21, 2009 at 11:20 PM, Benson Margulies
<bi...@gmail.com> wrote:
> Do you have the right stuff in your .m2/settings.xml?
>
> Here is the page I wrote for XmlSchema that might shed some light:
>
> When I do apache releases that are not targeted at Nexus, I use:
>
> <profile>
> <id>release</id>
> <properties>
> <gpg.passphrase>...my passphrase....</gpg.passphrase>
> <gpg.keyname>bimargulies@apache.org</gpg.keyname>
> <deploy.altRepository>apache.releases::default::scp://
> people.apache.org/home/bimargulies/public_html/maven_staging
> </deploy.altRepository>
> </properties>
> </profile>
>
Re: Release help, stuck on gpg-sign?
Posted by Benson Margulies <bi...@gmail.com>.
Do you have the right stuff in your .m2/settings.xml?
Here is the page I wrote for XmlSchema that might shed some light:
When I do apache releases that are not targeted at Nexus, I use:
<profile>
<id>release</id>
<properties>
<gpg.passphrase>...my passphrase....</gpg.passphrase>
<gpg.keyname>bimargulies@apache.org</gpg.keyname>
<deploy.altRepository>apache.releases::default::scp://
people.apache.org/home/bimargulies/public_html/maven_staging
</deploy.altRepository>
</properties>
</profile>
On Wed, Oct 21, 2009 at 12:26 PM, Sean Owen <sr...@gmail.com> wrote:
> I'm at a loss, I backed up and made sure to use the steps and config
> in the Mahout wiki. I am still stuck on gpg:sign. While I take some
> more wild guesses, I'd greatly appreciate someone else trying the
> release, simply to see whether the same issue appears. Knowing whether
> it's something specific to my environment would be helpful in figuring
> out where the problem is.
>
> Or, is there any contact at Apache that would be appropriate to
> contact next? is this Jukka's role?
>
> Or, is it necessary to run these steps? Is doing this manually just a
> matter of copying the tarballs to certain places, and updating the SVN
> tag? Just being practical here, if the tool is not working or is
> inscrutable to debug, let's go around it. I imagine that in theory
> there is not much to do here.
>
> On Wed, Oct 21, 2009 at 2:00 PM, Grant Ingersoll <gs...@apache.org>
> wrote:
> >
> > On Oct 21, 2009, at 8:53 AM, Sean Owen wrote:
> >
> >> I see. I had been stuck on mvn release:prepare and still am. However
> >> now I understand that the right configuration is a hybrid of the wiki
> >> below (which I followed first) and Jukka's page (which I followed
> >> second). I will have another run at it.
> >>
> >> I agree it will be good for me to get it working too in order to vet
> >> the process, no problem. At the same time if you are able to just do
> >> the release, and I'm still stuck, might as well get 0.2 out rather
> >> than block merely on my head-scratching.
> >
> > I think your head scratching is worthwhile, actually. It is critical in
> > these early stages that we get these things worked out, since it will
> make
> > it easier in the long run for others to do this stuff and to understand
> the
> > project.
> >
> >>
> >> On Wed, Oct 21, 2009 at 11:29 AM, Grant Ingersoll <gs...@apache.org>
> >> wrote:
> >>>
> >>> You shouldn't be uploading to the ASF repo that way, I think. Just put
> >>> them
> >>> up in your public_html.
> >>>
> >>> And, no, you don't need to add your key to the Maven KEYS file. It
> just
> >>> needs to be in the Mahout KEYS file.
> >>>
> >>> Are you following: http://cwiki.apache.org/MAHOUT/how-to-release.html?
> >>> What step are you stuck on?
> >>>
> >>> Earliest I can try something is tomorrow.
> >
> >
>
Re: Release help, stuck on gpg-sign?
Posted by Sean Owen <sr...@gmail.com>.
I'm at a loss, I backed up and made sure to use the steps and config
in the Mahout wiki. I am still stuck on gpg:sign. While I take some
more wild guesses, I'd greatly appreciate someone else trying the
release, simply to see whether the same issue appears. Knowing whether
it's something specific to my environment would be helpful in figuring
out where the problem is.
Or, is there any contact at Apache that would be appropriate to
contact next? is this Jukka's role?
Or, is it necessary to run these steps? Is doing this manually just a
matter of copying the tarballs to certain places, and updating the SVN
tag? Just being practical here, if the tool is not working or is
inscrutable to debug, let's go around it. I imagine that in theory
there is not much to do here.
On Wed, Oct 21, 2009 at 2:00 PM, Grant Ingersoll <gs...@apache.org> wrote:
>
> On Oct 21, 2009, at 8:53 AM, Sean Owen wrote:
>
>> I see. I had been stuck on mvn release:prepare and still am. However
>> now I understand that the right configuration is a hybrid of the wiki
>> below (which I followed first) and Jukka's page (which I followed
>> second). I will have another run at it.
>>
>> I agree it will be good for me to get it working too in order to vet
>> the process, no problem. At the same time if you are able to just do
>> the release, and I'm still stuck, might as well get 0.2 out rather
>> than block merely on my head-scratching.
>
> I think your head scratching is worthwhile, actually. It is critical in
> these early stages that we get these things worked out, since it will make
> it easier in the long run for others to do this stuff and to understand the
> project.
>
>>
>> On Wed, Oct 21, 2009 at 11:29 AM, Grant Ingersoll <gs...@apache.org>
>> wrote:
>>>
>>> You shouldn't be uploading to the ASF repo that way, I think. Just put
>>> them
>>> up in your public_html.
>>>
>>> And, no, you don't need to add your key to the Maven KEYS file. It just
>>> needs to be in the Mahout KEYS file.
>>>
>>> Are you following: http://cwiki.apache.org/MAHOUT/how-to-release.html ?
>>> What step are you stuck on?
>>>
>>> Earliest I can try something is tomorrow.
>
>
Re: Release help, stuck on gpg-sign?
Posted by Grant Ingersoll <gs...@apache.org>.
On Oct 21, 2009, at 8:53 AM, Sean Owen wrote:
> I see. I had been stuck on mvn release:prepare and still am. However
> now I understand that the right configuration is a hybrid of the wiki
> below (which I followed first) and Jukka's page (which I followed
> second). I will have another run at it.
>
> I agree it will be good for me to get it working too in order to vet
> the process, no problem. At the same time if you are able to just do
> the release, and I'm still stuck, might as well get 0.2 out rather
> than block merely on my head-scratching.
I think your head scratching is worthwhile, actually. It is critical
in these early stages that we get these things worked out, since it
will make it easier in the long run for others to do this stuff and to
understand the project.
>
> On Wed, Oct 21, 2009 at 11:29 AM, Grant Ingersoll
> <gs...@apache.org> wrote:
>> You shouldn't be uploading to the ASF repo that way, I think. Just
>> put them
>> up in your public_html.
>>
>> And, no, you don't need to add your key to the Maven KEYS file. It
>> just
>> needs to be in the Mahout KEYS file.
>>
>> Are you following: http://cwiki.apache.org/MAHOUT/how-to-
>> release.html ?
>> What step are you stuck on?
>>
>> Earliest I can try something is tomorrow.
Re: Release help, stuck on gpg-sign?
Posted by Sean Owen <sr...@gmail.com>.
I see. I had been stuck on mvn release:prepare and still am. However
now I understand that the right configuration is a hybrid of the wiki
below (which I followed first) and Jukka's page (which I followed
second). I will have another run at it.
I agree it will be good for me to get it working too in order to vet
the process, no problem. At the same time if you are able to just do
the release, and I'm still stuck, might as well get 0.2 out rather
than block merely on my head-scratching.
On Wed, Oct 21, 2009 at 11:29 AM, Grant Ingersoll <gs...@apache.org> wrote:
> You shouldn't be uploading to the ASF repo that way, I think. Just put them
> up in your public_html.
>
> And, no, you don't need to add your key to the Maven KEYS file. It just
> needs to be in the Mahout KEYS file.
>
> Are you following: http://cwiki.apache.org/MAHOUT/how-to-release.html ?
> What step are you stuck on?
>
> Earliest I can try something is tomorrow.
Re: Release help, stuck on gpg-sign?
Posted by Isabel Drost <is...@apache.org>.
On Wed Grant Ingersoll <gs...@apache.org> wrote:
> I'd like to make sure our Wiki properly reflects the steps, so once
> it is figured out, then our Wiki should be updated.
+1
Isabel
Re: Release help, stuck on gpg-sign?
Posted by Grant Ingersoll <gs...@apache.org>.
On Oct 21, 2009, at 6:48 AM, Isabel Drost wrote:
> On Wed Grant Ingersoll <gs...@apache.org> wrote:
>
>> Are you following: http://cwiki.apache.org/MAHOUT/how-to-
>> release.html ? What step are you stuck on?
>
> http://maven.apache.org/developers/release/releasing.html (was sent to
> mahout-dev by Jukka some weeks ago and is linked to from
I was under the impression that we should look at that for
suggestions, which is how I arrived at the steps on our Wiki (pre-
Nexus).
> https://issues.apache.org/jira/browse/INFRA-1896 - the jira issue in
> INFRA that deals with releasing to repository.apache.org) - probably I
> just misunderstood some of the steps mentioned therein?
Since we've only done one release before, stuff surely can be
improved. These first couple of releases are going to be more time
consuming as we figure stuff out. It is good that someone other than
me is looking at them as well, so that we have multiple people with
the necessary skills.
I forgot we are now using Nexus, which handles staging too, so not
sure how that factors in. I followed the steps on the Mahout Wiki,
YMMV with other approaches. I'd like to make sure our Wiki properly
reflects the steps, so once it is figured out, then our Wiki should be
updated.
-Grant
Re: Release help, stuck on gpg-sign?
Posted by Isabel Drost <is...@apache.org>.
On Wed Grant Ingersoll <gs...@apache.org> wrote:
> Are you following: http://cwiki.apache.org/MAHOUT/how-to-
> release.html ? What step are you stuck on?
http://maven.apache.org/developers/release/releasing.html (was sent to
mahout-dev by Jukka some weeks ago and is linked to from
https://issues.apache.org/jira/browse/INFRA-1896 - the jira issue in
INFRA that deals with releasing to repository.apache.org) - probably I
just misunderstood some of the steps mentioned therein?
Isabel
Re: Release help, stuck on gpg-sign?
Posted by Grant Ingersoll <gs...@apache.org>.
You shouldn't be uploading to the ASF repo that way, I think. Just
put them up in your public_html.
And, no, you don't need to add your key to the Maven KEYS file. It
just needs to be in the Mahout KEYS file.
Are you following: http://cwiki.apache.org/MAHOUT/how-to-
release.html ? What step are you stuck on?
Earliest I can try something is tomorrow.
-Grant
On Oct 21, 2009, at 5:11 AM, Isabel Drost wrote:
> On Tue Sean Owen <sr...@gmail.com> wrote:
>> I wonder, could whoever did the 0.1 release give it a shot? to see if
>> it's just me? and, to perhaps just do the deployment? the legwork is
>> done, it's ready to publish.
>
> mvn -Papache-release deploy
>
> did the trick for me. Are you sure that gpg is on your path?
>
> Though signing does work for me, the build fails as soon as it tries
> to
> upload our hadoop etc. jars to the Apache repo - I could not figure
> out
> a way to make that work - checking with infra how that is intended to
> be done with the apache repository.
>
> https://repository.apache.org/content/repositories/snapshots/org/apache/mahout/
>
>
> Isabel
Re: Release help, stuck on gpg-sign?
Posted by Isabel Drost <is...@apache.org>.
On Tue Sean Owen <sr...@gmail.com> wrote:
> I wonder, could whoever did the 0.1 release give it a shot? to see if
> it's just me? and, to perhaps just do the deployment? the legwork is
> done, it's ready to publish.
mvn -Papache-release deploy
did the trick for me. Are you sure that gpg is on your path?
Though signing does work for me, the build fails as soon as it tries to
upload our hadoop etc. jars to the Apache repo - I could not figure out
a way to make that work - checking with infra how that is intended to
be done with the apache repository.
https://repository.apache.org/content/repositories/snapshots/org/apache/mahout/
Isabel
Re: Release help, stuck on gpg-sign?
Posted by Sean Owen <sr...@gmail.com>.
Nah maybe this is required, same result.
I wonder, could whoever did the 0.1 release give it a shot? to see if
it's just me? and, to perhaps just do the deployment? the legwork is
done, it's ready to publish.
On Tue, Oct 20, 2009 at 11:53 PM, Sean Owen <sr...@gmail.com> wrote:
> Thanks, this is probably vital. I had not seen this.
>
> Let me ask questions here before taking them to the Apache staff --
>
> I am unable to update
> https://svn.apache.org/repos/asf/maven/project/KEYS -- get a 403
> Forbidden. Grant did you ever have to do this / do you have the power
> to?
>
> I will see how far I can get without it.
Re: Release help, stuck on gpg-sign?
Posted by Sean Owen <sr...@gmail.com>.
Thanks, this is probably vital. I had not seen this.
Let me ask questions here before taking them to the Apache staff --
I am unable to update
https://svn.apache.org/repos/asf/maven/project/KEYS -- get a 403
Forbidden. Grant did you ever have to do this / do you have the power
to?
I will see how far I can get without it.
On Tue, Oct 20, 2009 at 6:04 PM, Isabel Drost <is...@apache.org> wrote:
> On Tuesday 20 October 2009 17:11:59 Sean Owen wrote:
>> release:prepare is hanging for me at...
>>
>> [INFO] [INFO] [gpg:sign {execution: default}]
>> I dont' think this is to do with the GPG signing I just added, as it
>> shows up even if I remove that bit. Anyone more familiar with this? is
>> my settings.xml OK?
>
> Jukka gave me the following guide for releasing according to the new Apache
> parent pom:
>
> http://maven.apache.org/developers/release/releasing.html
>
> It has some additional hints on prerequisites, trouble shooting etc. Not sure
> if that helps in your case.
>
> Isabel
>
> --
> |\ _,,,---,,_ Web: <http://www.isabel-drost.de>
> /,`.-'`' -. ;-;;,_
> |,4- ) )-,_..;\ ( `'-'
> '---''(_/--' `-'\_) (fL) IM: <xm...@spaceboyz.net>
>
>
Re: Release help, stuck on gpg-sign?
Posted by Isabel Drost <is...@apache.org>.
On Tuesday 20 October 2009 17:11:59 Sean Owen wrote:
> release:prepare is hanging for me at...
>
> [INFO] [INFO] [gpg:sign {execution: default}]
> I dont' think this is to do with the GPG signing I just added, as it
> shows up even if I remove that bit. Anyone more familiar with this? is
> my settings.xml OK?
Jukka gave me the following guide for releasing according to the new Apache
parent pom:
http://maven.apache.org/developers/release/releasing.html
It has some additional hints on prerequisites, trouble shooting etc. Not sure
if that helps in your case.
Isabel
--
|\ _,,,---,,_ Web: <http://www.isabel-drost.de>
/,`.-'`' -. ;-;;,_
|,4- ) )-,_..;\ ( `'-'
'---''(_/--' `-'\_) (fL) IM: <xm...@spaceboyz.net>