You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by David Crossley <cr...@apache.org> on 2010/03/17 07:34:38 UTC

trouble publishing project docs with forrestbot

Would another committer try to publish the Forrest project docs:

$] cat etc/publishing_our_site.txt

I haven't tried since before the recent SVN access changes.

Note that i have edited my $FORREST_HOME/deploy.svn.settings file.

I can commit changes to the sources.

Just having recent trouble with:
$] forrest -f publish.xml deploy

-David

Re: trouble publishing project docs with forrestbot

Posted by David Crossley <cr...@apache.org>.
I did just now use https://svn.apache.org/change-password
to "sync" the two.

However the situation is still the same.

-David

Re: trouble publishing project docs with forrestbot

Posted by David Crossley <cr...@apache.org>.
Gav... wrote:
> From: David Crossley
> > 
> > I haven't tried since before the recent SVN access changes.
> 
> hmm, LDAP has been introduced but this shouldn't have affected svn access in
> any way.
> 
> Your old svn password is still your svn password. The main change is that
> your people.a.o changed to using LDAP.
> 
> There is the ability to sync the two (LDAP + svn) into one using
> https://svn.apache.org/change-password - you will need to use your SVN
> password to log in to this area , so is a good test to know you are using
> the correct one in your settings file.

The message to all committers in February said that we
could change it if we needed to. I already knew my shell
password (even though i always use SSH for machine logins)
so that automatically became my new SVN password.
No worries, that all worked as expected. See below.

> > Note that i have edited my $FORREST_HOME/deploy.svn.settings file.
> 
> Edited in what way? As noted your svn password should not have changed,
> unless you have synced it with LDAP already, in which case try your
> people.a.o password.

Yep, that is what my edit was. That file is used by the
local forrestbot.

> > I can commit changes to the sources.
> > 
> > Just having recent trouble with:
> > $] forrest -f publish.xml deploy
> 
> So you can commit to repos/asf/forrest/trunk via the command line but not
> repos/asf/forrest/site via forrestbot.

Correct.

> As the acl is the same for both is
> 'sounds' like at least you are using the wrong p/w in the
> deploy.svn.settings file.

Tried both of course, to no avail.

> Let me know if you continue to have trouble and we'll dig some more.

I wondered if "jsvn" (which Forrestbot uses) has cached the old
settings. However, have not had time to investigate.

-David

RE: trouble publishing project docs with forrestbot

Posted by "Gav..." <ga...@16degrees.com.au>.

> -----Original Message-----
> From: David Crossley [mailto:crossley@apache.org]
> Sent: Wednesday, 17 March 2010 4:35 PM
> To: dev@forrest.apache.org
> Subject: trouble publishing project docs with forrestbot
> 
> Would another committer try to publish the Forrest project docs:
> 
> $] cat etc/publishing_our_site.txt

Done.

> 
> I haven't tried since before the recent SVN access changes.

hmm, LDAP has been introduced but this shouldn't have affected svn access in
any way.

Your old svn password is still your svn password. The main change is that
your people.a.o
changed to using LDAP.

There is the ability to sync the two (LDAP + svn) into one using

https://svn.apache.org/change-password - you will need to use your SVN
password to log in to this area , so is a good test to know you are using
the correct one in your settings file.

> 
> Note that i have edited my $FORREST_HOME/deploy.svn.settings file.

Edited in what way? As noted your svn password should not have changed,
unless you have synced it with LDAP already, in which case try your
people.a.o password.

> 
> I can commit changes to the sources.
> 
> Just having recent trouble with:
> $] forrest -f publish.xml deploy

So you can commit to repos/asf/forrest/trunk via the command line but not
repos/asf/forrest/site via forrestbot. As the acl is the same for both is
'sounds' like at least you are using the wrong p/w in the
deploy.svn.settings file.

Let me know if you continue to have trouble and we'll dig some more.

Gav...

> 
> -David

Re: trouble publishing project docs

Posted by David Crossley <cr...@apache.org>.
David Crossley wrote:
> 
> That is why i wonder if Ant or Jsvn might cache it.
> 
> I also tried removing my deploy.svn.settings file,
> thinking that i would then get prompted for the password.
> But it didn't. And still gave the same credentials error.

I tried a complete new forrest checkout on this same
machine. Same trouble.

On another machine, forrest never installed. After making
a source commit to get set up ... same issue!

However after removing the ~/.subversion/auth it now
worked.

Anyway, that is it. Give up, and look forward to the
svn executable via Ant.

As noted above, the deploy.svn.settings didn't seem
to have any effect.

-David

Re: trouble publishing project docs

Posted by "Sina K. Heshmati" <si...@khakbaz.com>.
David Crossley wrote:
> Sina K. Heshmati wrote:
>>
>> I think we should stop using the svncommit and svncheckout tasks since:
>>
>> - There's almost no documentation available for them.
>> - They don't remove the need for executing the svn command.
>>
>> Maybe we could consider using [1], which is BTW released under ASL 1.1 [2].
>>
>> Kind regards,
>> Sina
>>
>> [1] http://subclipse.tigris.org/svnant.html
>> [2] http://subclipse.tigris.org/licenses/svnAnt.html
> 
> Thanks Sina. However, if i read correctly then the version
> of SvnAnt is "bound against subversion" to a particular
> version of Subversion.
> 
> So i suppose that we would need to provide different versions
> of SvnAnt to match their client version. Sounds messy.

True. I had not realized the implications.

> I like Tim's suggestion better.

Executing the SVN command directly from Ant? Sure. We already have them and they have posed less problems than the alternative methods. Besides, targets like publish are most likely to be used on the server.

Kind regards,
SinDoc

Re: trouble publishing project docs

Posted by David Crossley <cr...@apache.org>.
Sina K. Heshmati wrote:
> 
> I think we should stop using the svncommit and svncheckout tasks since:
> 
> - There's almost no documentation available for them.
> - They don't remove the need for executing the svn command.
> 
> Maybe we could consider using [1], which is BTW released under ASL 1.1 [2].
> 
> Kind regards,
> Sina
> 
> [1] http://subclipse.tigris.org/svnant.html
> [2] http://subclipse.tigris.org/licenses/svnAnt.html

Thanks Sina. However, if i read correctly then the version
of SvnAnt is "bound against subversion" to a particular
version of Subversion.

So i suppose that we would need to provide different versions
of SvnAnt to match their client version. Sounds messy.

I like Tim's suggestion better.

-David

Re: trouble publishing project docs

Posted by Tim Williams <wi...@gmail.com>.
On Fri, Jun 4, 2010 at 4:01 AM, David Crossley <cr...@apache.org> wrote:
> David Crossley wrote:
>> Tim Williams wrote:
>> >
>> > I guess I've never investigated how forrestbot actually works, but
>> > this jsvn library is terrible.  I can't find any documentation and all
>> > the useful links are broken.  I was trying to find out if there was a
>> > "--no-auth-cache" equivalent for that svncheckout task.  I wonder why
>> > we don't just call out to external svn commands in all places (just
>> > like svn status) since svn is a dependency anyway?
>>
>> That is a good question.
>>
>> It seems that the affected files are
>>  forrestbot/core/getsrc.xml
>>  forrestbot/core/deploy.xml
>> which use "svncheckout" and "svncommit".
>
> and plugins/build.xml
>
> So not only forrestbot.

Thanks David, I switched my forrestbot over this morning to straight
svn commands.  All seems well.  I'll try to take a look at the
plugins/build.xml file some time this weekend.

--tim

Re: trouble publishing project docs

Posted by David Crossley <cr...@apache.org>.
David Crossley wrote:
> Tim Williams wrote:
> > 
> > I guess I've never investigated how forrestbot actually works, but
> > this jsvn library is terrible.  I can't find any documentation and all
> > the useful links are broken.  I was trying to find out if there was a
> > "--no-auth-cache" equivalent for that svncheckout task.  I wonder why
> > we don't just call out to external svn commands in all places (just
> > like svn status) since svn is a dependency anyway?
> 
> That is a good question.
> 
> It seems that the affected files are
>  forrestbot/core/getsrc.xml
>  forrestbot/core/deploy.xml
> which use "svncheckout" and "svncommit".

and plugins/build.xml

So not only forrestbot.

-David

> It is interesting to note that we already use
> Ant to call the "svn" executable do to the 'svn add'
> and 'svn status' operations.
> 
> I am in favour of dropping dependencies where possible.
> 
> -David

Re: trouble publishing project docs

Posted by Thorsten Scherler <th...@apache.org>.
On Tue, 2010-06-01 at 10:17 +0200, Thorsten Scherler wrote:
...
> 
> I will try to setup the forrestbot on my box and will let you know how
> it goes.

It is working fine for me as you can see in r950437. Not sure what your
problem can be David.

BTW tested on ubuntu 10.4.

salu2

-- 
Thorsten Scherler <thorsten.at.apache.org>
Open Source Java <consulting, training and solutions>

Re: trouble publishing project docs

Posted by Thorsten Scherler <sc...@gmail.com>.
On Tue, 2010-06-01 at 07:46 +0200, Sina K. Heshmati wrote:
> David Crossley wrote:
> > Tim Williams wrote:
> >>
> >> I guess I've never investigated how forrestbot actually works, but
> >> this jsvn library is terrible.  I can't find any documentation and all
> >> the useful links are broken.  I was trying to find out if there was a
> >> "--no-auth-cache" equivalent for that svncheckout task.  I wonder why
> >> we don't just call out to external svn commands in all places (just
> >> like svn status) since svn is a dependency anyway?
> > 
> > That is a good question.
> > 
> > It seems that the affected files are
> >  forrestbot/core/getsrc.xml
> >  forrestbot/core/deploy.xml
> > which use "svncheckout" and "svncommit".
> > 
> > It is interesting to note that we already use
> > Ant to call the "svn" executable do to the 'svn add'
> > and 'svn status' operations.
> > 
> > I am in favour of dropping dependencies where possible.
> 
> I think we should stop using the svncommit and svncheckout tasks since:
> 
> - There's almost no documentation available for them.
> - They don't remove the need for executing the svn command.
> 
> Maybe we could consider using [1], which is BTW released under ASL 1.1 [2].

Actually that is kind of the same in the sense of dependencies:

"With the help of the underlying svnClientAdapter, <svn> task uses
javahl - a native (JNI) java interface for the subversion api if it can
find the corresponding library.
(See the subclipse FAQ for hints how to get it for your operating
system)."

That we execute the svn commit by hand has the reason to examine our
changes.

I will try to setup the forrestbot on my box and will let you know how
it goes.

salu2 


> 
> Kind regards,
> Sina
> 
> [1] http://subclipse.tigris.org/svnant.html
> [2] http://subclipse.tigris.org/licenses/svnAnt.html
> 

-- 
Thorsten Scherler <thorsten.at.apache.org>
Open Source Java <consulting, training and solutions>

Re: trouble publishing project docs

Posted by "Sina K. Heshmati" <si...@khakbaz.com>.
David Crossley wrote:
> Tim Williams wrote:
>>
>> I guess I've never investigated how forrestbot actually works, but
>> this jsvn library is terrible.  I can't find any documentation and all
>> the useful links are broken.  I was trying to find out if there was a
>> "--no-auth-cache" equivalent for that svncheckout task.  I wonder why
>> we don't just call out to external svn commands in all places (just
>> like svn status) since svn is a dependency anyway?
> 
> That is a good question.
> 
> It seems that the affected files are
>  forrestbot/core/getsrc.xml
>  forrestbot/core/deploy.xml
> which use "svncheckout" and "svncommit".
> 
> It is interesting to note that we already use
> Ant to call the "svn" executable do to the 'svn add'
> and 'svn status' operations.
> 
> I am in favour of dropping dependencies where possible.

I think we should stop using the svncommit and svncheckout tasks since:

- There's almost no documentation available for them.
- They don't remove the need for executing the svn command.

Maybe we could consider using [1], which is BTW released under ASL 1.1 [2].

Kind regards,
Sina

[1] http://subclipse.tigris.org/svnant.html
[2] http://subclipse.tigris.org/licenses/svnAnt.html

Re: trouble publishing project docs

Posted by David Crossley <cr...@apache.org>.
Tim Williams wrote:
> 
> I guess I've never investigated how forrestbot actually works, but
> this jsvn library is terrible.  I can't find any documentation and all
> the useful links are broken.  I was trying to find out if there was a
> "--no-auth-cache" equivalent for that svncheckout task.  I wonder why
> we don't just call out to external svn commands in all places (just
> like svn status) since svn is a dependency anyway?

That is a good question.

It seems that the affected files are
 forrestbot/core/getsrc.xml
 forrestbot/core/deploy.xml
which use "svncheckout" and "svncommit".

It is interesting to note that we already use
Ant to call the "svn" executable do to the 'svn add'
and 'svn status' operations.

I am in favour of dropping dependencies where possible.

-David

Re: trouble publishing project docs

Posted by Tim Williams <wi...@gmail.com>.
On Mon, May 31, 2010 at 1:04 AM, David Crossley <cr...@apache.org> wrote:
> Gav... wrote:
>> > >
>> > > maybe:
>> > > rm -Rf ~/.ssh/auth
>> >
>> > I suppose that you mean ~/.subversion/auth
>> >
>> > Yeah already tried that in desperation. Tried again now
>> > but same issue.
>>
>> So now you have removed the auth/svn.ssh directory, can you still
>> commit normally to trunk, using the same password you are using in
>> the deploy.svn.settings file -- if you have removed auth then you
>> will be prompted for a password from the command line.
>
> Yes, that is what i have been saying all along.
>
> Everything else is as expected, just the local forrestbot
> cannot commit using its Jsvn task.

I guess I've never investigated how forrestbot actually works, but
this jsvn library is terrible.  I can't find any documentation and all
the useful links are broken.  I was trying to find out if there was a
"--no-auth-cache" equivalent for that svncheckout task.  I wonder why
we don't just call out to external svn commands in all places (just
like svn status) since svn is a dependency anyway?

--tim

Re: trouble publishing project docs

Posted by David Crossley <cr...@apache.org>.
Gav... wrote:
> > >
> > > maybe:
> > > rm -Rf ~/.ssh/auth
> > 
> > I suppose that you mean ~/.subversion/auth
> > 
> > Yeah already tried that in desperation. Tried again now
> > but same issue.
> 
> So now you have removed the auth/svn.ssh directory, can you still
> commit normally to trunk, using the same password you are using in
> the deploy.svn.settings file -- if you have removed auth then you
> will be prompted for a password from the command line.

Yes, that is what i have been saying all along.

Everything else is as expected, just the local forrestbot
cannot commit using its Jsvn task.

-David

RE: trouble publishing project docs

Posted by "Gav..." <ga...@16degrees.com.au>.

> -----Original Message-----
> From: David Crossley [mailto:crossley@apache.org]
> Sent: Friday, 28 May 2010 5:24 PM
> To: dev@forrest.apache.org
> Subject: Re: trouble publishing project docs
> 
> Tim Williams wrote:
> > David Crossley wrote:
> > > Tim Williams wrote:
> > >>
> > >> Just a guess, if you use keychain, is it out of sync with a
> recently
> > >> updated password change?
> > >
> > > Thanks for trying. No, it is not that. The "ASF Committers"
> > > password is there, and i can commit okay.
> > >
> > > However, it is just my local forrestbot that is not working.
> > >
> > > That is why i wonder if Ant or Jsvn might cache it.
> > >
> > > I also tried removing my deploy.svn.settings file,
> > > thinking that i would then get prompted for the password.
> > > But it didn't. And still gave the same credentials error.
> >
> > maybe:
> > rm -Rf ~/.ssh/auth
> 
> I suppose that you mean ~/.subversion/auth
> 
> Yeah already tried that in desperation. Tried again now
> but same issue.

So now you have removed the auth/svn.ssh directory, can you still
commit normally to trunk, using the same password you are using in
the deploy.svn.settings file -- if you have removed auth then you
will be prompted for a password from the command line.

Gav...

> 
> -David
> 
> > Though, it'd be strange that the command line would use keychain yet
> > the ant task would use these credentials.  I'm wildly guessing at
> this
> > stage in case you haven't noticed:)
> >
> > --tim
> >
> > http://svnbook.red-bean.com/en/1.1/ch07.html#svn-ch-7-sect-1.1

Re: trouble publishing project docs

Posted by David Crossley <cr...@apache.org>.
Tim Williams wrote:
> David Crossley wrote:
> > Tim Williams wrote:
> >>
> >> Just a guess, if you use keychain, is it out of sync with a recently
> >> updated password change?
> >
> > Thanks for trying. No, it is not that. The "ASF Committers"
> > password is there, and i can commit okay.
> >
> > However, it is just my local forrestbot that is not working.
> >
> > That is why i wonder if Ant or Jsvn might cache it.
> >
> > I also tried removing my deploy.svn.settings file,
> > thinking that i would then get prompted for the password.
> > But it didn't. And still gave the same credentials error.
> 
> maybe:
> rm -Rf ~/.ssh/auth

I suppose that you mean ~/.subversion/auth

Yeah already tried that in desperation. Tried again now
but same issue.

-David

> Though, it'd be strange that the command line would use keychain yet
> the ant task would use these credentials.  I'm wildly guessing at this
> stage in case you haven't noticed:)
> 
> --tim
> 
> http://svnbook.red-bean.com/en/1.1/ch07.html#svn-ch-7-sect-1.1

Re: trouble publishing project docs

Posted by Tim Williams <wi...@gmail.com>.
On Wed, May 26, 2010 at 9:36 PM, David Crossley <cr...@apache.org> wrote:
> Tim Williams wrote:
>>
>> Just a guess, if you use keychain, is it out of sync with a recently
>> updated password change?
>
> Thanks for trying. No, it is not that. The "ASF Committers"
> password is there, and i can commit okay.
>
> However, it is just my local forrestbot that is not working.
>
> That is why i wonder if Ant or Jsvn might cache it.
>
> I also tried removing my deploy.svn.settings file,
> thinking that i would then get prompted for the password.
> But it didn't. And still gave the same credentials error.

maybe:
rm -Rf ~/.ssh/auth

Though, it'd be strange that the command line would use keychain yet
the ant task would use these credentials.  I'm wildly guessing at this
stage in case you haven't noticed:)

--tim

http://svnbook.red-bean.com/en/1.1/ch07.html#svn-ch-7-sect-1.1

Re: trouble publishing project docs

Posted by David Crossley <cr...@apache.org>.
Tim Williams wrote:
> 
> Just a guess, if you use keychain, is it out of sync with a recently
> updated password change?

Thanks for trying. No, it is not that. The "ASF Committers"
password is there, and i can commit okay.

However, it is just my local forrestbot that is not working.

That is why i wonder if Ant or Jsvn might cache it.

I also tried removing my deploy.svn.settings file,
thinking that i would then get prompted for the password.
But it didn't. And still gave the same credentials error.

-David

Re: trouble publishing project docs

Posted by Tim Williams <wi...@gmail.com>.
On Wed, May 26, 2010 at 8:13 PM, Tim Williams <wi...@gmail.com> wrote:
> On Wed, May 26, 2010 at 8:04 AM, Tim Williams <wi...@gmail.com> wrote:
>> On Wed, May 26, 2010 at 4:46 AM, David Crossley <cr...@apache.org> wrote:
>>> I am still having this trouble deploying our website.
>>>
>>> Would another committer please see how they go:
>>>
>>> $] cat $FORREST_HOME/etc/publishing_our_site.txt
>>>
>>>
>>> Note that i have confirmed my $FORREST_HOME/deploy.svn.settings file.
>>>
>>> I can commit changes to the sources.
>>>
>>> Just having trouble with:
>>> $] forrest -f publish.xml deploy
>>>
>>> which gives ...
>>>
>>> BUILD FAILED
>>> com.alternatecomputing.jsvn.command.CommandException: svn: Commit failed (details follow):
>>> svn: MKACTIVITY of '/repos/asf/!svn/act/09d75e90-9268-4792-aad1-352ccc57da41': authorization failed: Could not authenticate to server: rejected Basic challenge (https://svn.apache.org)
>>
>> I can give it a try tonight if no one beats me too it.
>
> I just published and all appeared to go well.  I got a complaint from
> an svn step of "svn: invalid option character:" but I don't see an
> obvious negative side effect of that.

Just a guess, if you use keychain, is it out of sync with a recently
updated password change?

--tim

Re: trouble publishing project docs

Posted by Tim Williams <wi...@gmail.com>.
On Wed, May 26, 2010 at 8:04 AM, Tim Williams <wi...@gmail.com> wrote:
> On Wed, May 26, 2010 at 4:46 AM, David Crossley <cr...@apache.org> wrote:
>> I am still having this trouble deploying our website.
>>
>> Would another committer please see how they go:
>>
>> $] cat $FORREST_HOME/etc/publishing_our_site.txt
>>
>>
>> Note that i have confirmed my $FORREST_HOME/deploy.svn.settings file.
>>
>> I can commit changes to the sources.
>>
>> Just having trouble with:
>> $] forrest -f publish.xml deploy
>>
>> which gives ...
>>
>> BUILD FAILED
>> com.alternatecomputing.jsvn.command.CommandException: svn: Commit failed (details follow):
>> svn: MKACTIVITY of '/repos/asf/!svn/act/09d75e90-9268-4792-aad1-352ccc57da41': authorization failed: Could not authenticate to server: rejected Basic challenge (https://svn.apache.org)
>
> I can give it a try tonight if no one beats me too it.

I just published and all appeared to go well.  I got a complaint from
an svn step of "svn: invalid option character:" but I don't see an
obvious negative side effect of that.

--tim

Re: trouble publishing project docs

Posted by Tim Williams <wi...@gmail.com>.
On Wed, May 26, 2010 at 4:46 AM, David Crossley <cr...@apache.org> wrote:
> I am still having this trouble deploying our website.
>
> Would another committer please see how they go:
>
> $] cat $FORREST_HOME/etc/publishing_our_site.txt
>
>
> Note that i have confirmed my $FORREST_HOME/deploy.svn.settings file.
>
> I can commit changes to the sources.
>
> Just having trouble with:
> $] forrest -f publish.xml deploy
>
> which gives ...
>
> BUILD FAILED
> com.alternatecomputing.jsvn.command.CommandException: svn: Commit failed (details follow):
> svn: MKACTIVITY of '/repos/asf/!svn/act/09d75e90-9268-4792-aad1-352ccc57da41': authorization failed: Could not authenticate to server: rejected Basic challenge (https://svn.apache.org)

I can give it a try tonight if no one beats me too it.

--tim

Re: trouble publishing project docs

Posted by David Crossley <cr...@apache.org>.
I am still having this trouble deploying our website.

Would another committer please see how they go:

$] cat $FORREST_HOME/etc/publishing_our_site.txt


Note that i have confirmed my $FORREST_HOME/deploy.svn.settings file.

I can commit changes to the sources.

Just having trouble with:
$] forrest -f publish.xml deploy

which gives ...

BUILD FAILED
com.alternatecomputing.jsvn.command.CommandException: svn: Commit failed (details follow):
svn: MKACTIVITY of '/repos/asf/!svn/act/09d75e90-9268-4792-aad1-352ccc57da41': authorization failed: Could not authenticate to server: rejected Basic challenge (https://svn.apache.org)

-David