keep running into issue while commiting [the specified baseline is not the latest baseline]

2012-11-28 Thread Robby Pelssers
http://www.apache.org/dev/version-control.html#latest-baseline

I tried several times to commit the patch for [COCOON3-114] but with no success 
so far.

Anyone experiencing similar issues?

Robby




Re: keep running into issue while commiting [the specified baseline is not the latest baseline]

2012-11-28 Thread Francesco Chicchiriccò

On 28/11/2012 13:56, Robby Pelssers wrote:

http://www.apache.org/dev/version-control.html#latest-baseline

I tried several times to commit the patch for [COCOON3-114] but with no success 
so far.

Anyone experiencing similar issues?


I do: I've solved temporarily the situation by switching to 
svn.us.apache.org from svn.apache.org (which presumably resolves to 
svn.eu.apache.org for both of us).


Hope this helps.
Regards.

--
Francesco Chicchiriccò

ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member
http://people.apache.org/~ilgrosso/



Re: keep running into issue while commiting [the specified baseline is not the latest baseline]

2012-11-28 Thread Francesco Chicchiriccò

On 28/11/2012 13:58, Francesco Chicchiriccò wrote:

On 28/11/2012 13:56, Robby Pelssers wrote:

http://www.apache.org/dev/version-control.html#latest-baseline

I tried several times to commit the patch for [COCOON3-114] but with 
no success so far.


Anyone experiencing similar issues?


I do: I've solved temporarily the situation by switching to 
svn.us.apache.org from svn.apache.org (which presumably resolves to 
svn.eu.apache.org for both of us).


It seems there are quite some issues: http://monitoring.apache.org/status/

Regards.

--
Francesco Chicchiriccò

ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member
http://people.apache.org/~ilgrosso/



Re: keep running into issue while commiting [the specified baseline is not the latest baseline]

2012-11-28 Thread Christian Grobmeier
No, i just had the same.

THe US svn got a huge commit, and it needed to be synced to EU mirror.
This takes a while.

For me it did work meanwhile.
The recommendation is to switch to svn.us or to wait until the sync is over


On Wed, Nov 28, 2012 at 2:07 PM, Francesco Chicchiriccò
ilgro...@apache.org wrote:
 On 28/11/2012 13:58, Francesco Chicchiriccò wrote:

 On 28/11/2012 13:56, Robby Pelssers wrote:

 http://www.apache.org/dev/version-control.html#latest-baseline

 I tried several times to commit the patch for [COCOON3-114] but with no
 success so far.

 Anyone experiencing similar issues?


 I do: I've solved temporarily the situation by switching to
 svn.us.apache.org from svn.apache.org (which presumably resolves to
 svn.eu.apache.org for both of us).


 It seems there are quite some issues: http://monitoring.apache.org/status/


 Regards.

 --
 Francesco Chicchiriccò

 ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member
 http://people.apache.org/~ilgrosso/




-- 
http://www.grobmeier.de
https://www.timeandbill.de


RE: keep running into issue while commiting [the specified baseline is not the latest baseline]

2012-11-28 Thread Robby Pelssers
Ok...  

Franscesco told me how to do the relocate from command line:

svn switch --relocate https://svn.apache.org/repos/asf/cocoon/cocoon3/trunk 
https://svn.us.apache.org/repos/asf/cocoon/cocoon3/trunk

But I also found out how to do this from Intellij:

Make sure you selected trunk folder in project navigation tab.

Next in menu:  VCS  -- Subversion  - relocate

From: https://svn.apache.org/repos/asf/cocoon/cocoon3/trunk
To:   https://svn.us.apache.org/repos/asf/cocoon/cocoon3/trunk 

Robby

-Original Message-
From: Francesco Chicchiriccò [mailto:ilgro...@apache.org] 
Sent: Wednesday, November 28, 2012 1:59 PM
To: dev@cocoon.apache.org
Subject: Re: keep running into issue while commiting [the specified baseline is 
not the latest baseline]

On 28/11/2012 13:56, Robby Pelssers wrote:
 http://www.apache.org/dev/version-control.html#latest-baseline

 I tried several times to commit the patch for [COCOON3-114] but with no 
 success so far.

 Anyone experiencing similar issues?

I do: I've solved temporarily the situation by switching to svn.us.apache.org 
from svn.apache.org (which presumably resolves to svn.eu.apache.org for both of 
us).

Hope this helps.
Regards.

--
Francesco Chicchiriccò

ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member 
http://people.apache.org/~ilgrosso/