Commit issue

[Philippe Mouawad <ph...@gmail.com>]

Hello,
I am having an issue commiting files, getting this message:
Some of selected resources were not committed.
svn: Commit failed (details follow):
svn: The specified baseline is not the latest baseline, so it may not be
checked out.
svn: CHECKOUT of '/repos/asf/!svn/bln/1240617': 409 Conflict (
https://svn.apache.org)

Do you know what's the issue ?
Thanks
Regards
Philippe

Re: Commit issue

[Philippe Mouawad <ph...@gmail.com>]

Yes i succeeded commiting this morning ,  did nothing except wait.
Thanks for your help Sebb and rainer .
On Sunday, February 5, 2012, Rainer Jung <ra...@kippdata.de> wrote:
> On 05.02.2012 01:35, sebb wrote:
>>
>> On 4 February 2012 23:57, Philippe Mouawad<ph...@gmail.com>
 wrote:
>>>
>>> Maybe getting this issue:
>>> http://www.apache.org/dev/version-control.html
>>>
>>> "specified baseline is not the latest baseline" errors
>>>
>>> If you're getting an error message like the following:
>>>
>>> svn: Commit failed (details follow):
>>> svn: The specified baseline is not the latest baseline, so it may not be
>>> checked out.
>>>
>>> This may be because of a short lag in the synchronization between
>>> Subversion mirrors, and can occur if multiple commits are run
immediately
>>> after each other. This error will usually only happen if you are
located in
>>> Europe, or explicitly using the European mirror.
>>>
>>> Waiting for 10 seconds and repeating the command should succeed.
>>>
>>
>> I've never had that problem, and I use the EU mirror.
>>
>> I think it mainly applies to multiple commits in sequence, as are
>> sometimes generated by Maven.
>
> I sometimes do experience a similar problem, e.g. when trying to do "svn
up" directly after a commit (not sure about the exact error message). That
one definitely has to do with the sync lag. If I wait a few seconds, then
"svn up" succceeds.
>
> Rainer
>

-- 
Cordialement.
Philippe Mouawad.

Re: Commit issue

[Rainer Jung <ra...@kippdata.de>]

On 05.02.2012 01:35, sebb wrote:
> On 4 February 2012 23:57, Philippe Mouawad<ph...@gmail.com>  wrote:
>> Maybe getting this issue:
>> http://www.apache.org/dev/version-control.html
>>
>> "specified baseline is not the latest baseline" errors
>>
>> If you're getting an error message like the following:
>>
>> svn: Commit failed (details follow):
>> svn: The specified baseline is not the latest baseline, so it may not be
>> checked out.
>>
>> This may be because of a short lag in the synchronization between
>> Subversion mirrors, and can occur if multiple commits are run immediately
>> after each other. This error will usually only happen if you are located in
>> Europe, or explicitly using the European mirror.
>>
>> Waiting for 10 seconds and repeating the command should succeed.
>>
>
> I've never had that problem, and I use the EU mirror.
>
> I think it mainly applies to multiple commits in sequence, as are
> sometimes generated by Maven.

I sometimes do experience a similar problem, e.g. when trying to do "svn 
up" directly after a commit (not sure about the exact error message). 
That one definitely has to do with the sync lag. If I wait a few 
seconds, then "svn up" succceeds.

Rainer

Re: Commit issue

[sebb <se...@gmail.com>]

On 4 February 2012 23:57, Philippe Mouawad <ph...@gmail.com> wrote:
> Maybe getting this issue:
> http://www.apache.org/dev/version-control.html
>
> "specified baseline is not the latest baseline" errors
>
> If you're getting an error message like the following:
>
> svn: Commit failed (details follow):
> svn: The specified baseline is not the latest baseline, so it may not be
> checked out.
>
> This may be because of a short lag in the synchronization between
> Subversion mirrors, and can occur if multiple commits are run immediately
> after each other. This error will usually only happen if you are located in
> Europe, or explicitly using the European mirror.
>
> Waiting for 10 seconds and repeating the command should succeed.
>

I've never had that problem, and I use the EU mirror.

I think it mainly applies to multiple commits in sequence, as are
sometimes generated by Maven.

>
>
> On Sun, Feb 5, 2012 at 12:54 AM, Philippe Mouawad <
> philippe.mouawad@gmail.com> wrote:
>
>> I did it.
>> To check , I created a new Eclipse project downloading VN trunk and tried
>> to commit, same issue.
>>
>> I am having the same message.
>> Regards
>> Philippe
>>
>>
>> On Sun, Feb 5, 2012 at 12:49 AM, sebb <se...@gmail.com> wrote:
>>
>>> On 4 February 2012 23:45, Philippe Mouawad <ph...@gmail.com>
>>> wrote:
>>> > Hello,
>>> > I am having an issue commiting files, getting this message:
>>> > Some of selected resources were not committed.
>>> > svn: Commit failed (details follow):
>>> > svn: The specified baseline is not the latest baseline, so it may not be
>>> > checked out.
>>> > svn: CHECKOUT of '/repos/asf/!svn/bln/1240617': 409 Conflict (
>>> > https://svn.apache.org)
>>> >
>>> > Do you know what's the issue ?
>>>
>>> Make sure you run svn update regularly?
>>>
>>> > Thanks
>>> > Regards
>>> > Philippe
>>>
>>
>>
>>
>> --
>> Cordialement.
>> Philippe Mouawad.
>>
>>
>>
>>
>
>
> --
> Cordialement.
> Philippe Mouawad.

Re: Commit issue

[Philippe Mouawad <ph...@gmail.com>]

Maybe getting this issue:
http://www.apache.org/dev/version-control.html

"specified baseline is not the latest baseline" errors

If you're getting an error message like the following:

svn: Commit failed (details follow):
svn: The specified baseline is not the latest baseline, so it may not be
checked out.

This may be because of a short lag in the synchronization between
Subversion mirrors, and can occur if multiple commits are run immediately
after each other. This error will usually only happen if you are located in
Europe, or explicitly using the European mirror.

Waiting for 10 seconds and repeating the command should succeed.




On Sun, Feb 5, 2012 at 12:54 AM, Philippe Mouawad <
philippe.mouawad@gmail.com> wrote:

> I did it.
> To check , I created a new Eclipse project downloading VN trunk and tried
> to commit, same issue.
>
> I am having the same message.
> Regards
> Philippe
>
>
> On Sun, Feb 5, 2012 at 12:49 AM, sebb <se...@gmail.com> wrote:
>
>> On 4 February 2012 23:45, Philippe Mouawad <ph...@gmail.com>
>> wrote:
>> > Hello,
>> > I am having an issue commiting files, getting this message:
>> > Some of selected resources were not committed.
>> > svn: Commit failed (details follow):
>> > svn: The specified baseline is not the latest baseline, so it may not be
>> > checked out.
>> > svn: CHECKOUT of '/repos/asf/!svn/bln/1240617': 409 Conflict (
>> > https://svn.apache.org)
>> >
>> > Do you know what's the issue ?
>>
>> Make sure you run svn update regularly?
>>
>> > Thanks
>> > Regards
>> > Philippe
>>
>
>
>
> --
> Cordialement.
> Philippe Mouawad.
>
>
>
>


-- 
Cordialement.
Philippe Mouawad.

Re: Commit issue

[Philippe Mouawad <ph...@gmail.com>]

I did it.
To check , I created a new Eclipse project downloading VN trunk and tried
to commit, same issue.

I am having the same message.
Regards
Philippe

On Sun, Feb 5, 2012 at 12:49 AM, sebb <se...@gmail.com> wrote:

> On 4 February 2012 23:45, Philippe Mouawad <ph...@gmail.com>
> wrote:
> > Hello,
> > I am having an issue commiting files, getting this message:
> > Some of selected resources were not committed.
> > svn: Commit failed (details follow):
> > svn: The specified baseline is not the latest baseline, so it may not be
> > checked out.
> > svn: CHECKOUT of '/repos/asf/!svn/bln/1240617': 409 Conflict (
> > https://svn.apache.org)
> >
> > Do you know what's the issue ?
>
> Make sure you run svn update regularly?
>
> > Thanks
> > Regards
> > Philippe
>



-- 
Cordialement.
Philippe Mouawad.

Re: Commit issue

[sebb <se...@gmail.com>]

On 4 February 2012 23:45, Philippe Mouawad <ph...@gmail.com> wrote:
> Hello,
> I am having an issue commiting files, getting this message:
> Some of selected resources were not committed.
> svn: Commit failed (details follow):
> svn: The specified baseline is not the latest baseline, so it may not be
> checked out.
> svn: CHECKOUT of '/repos/asf/!svn/bln/1240617': 409 Conflict (
> https://svn.apache.org)
>
> Do you know what's the issue ?

Make sure you run svn update regularly?

> Thanks
> Regards
> Philippe