Mac OS X + SVN 1.5.1 = Branch problem

[Ash Angell]

Hi guys, I have run into the exact same issue, but when trying to perform a tagging operation.  Like the others here, I have confirmed that there is no existing folder as described.

I can however confirm that this is happening on the Windows binary 1.5.1 - is there any news on a fix?  I am going to try to rollback to v1.4.x and see if that solves the immediate problem - something which is quite sad because 1.5.1 up until now has been much better.

Ash

[Jeremy Whitlock]

> Hi guys, I have run into the exact same issue, but when trying to perform a
> tagging operation.  Like the others here, I have confirmed that there is no
> existing folder as described.

That makes sense because making a tag and a branch is the same (copy)
command but with a different destination.

> I can however confirm that this is happening on the Windows binary 1.5.1 -
> is there any news on a fix?  I am going to try to rollback to v1.4.x and see
> if that solves the immediate problem - something which is quite sad because
> 1.5.1 up until now has been much better.

To help you better, I need to know what tool you're using to create
the copy?  If you're using Maven, this is a known, unresolved
incompatibility of Maven.  If you're using something else, we'll need
to know so we can help you find a fix or help report the problem to
the proper people.

--
Take care,

Jeremy Whitlock
http://www.thoughtspark.org

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[jrduncans]

Jeremy Whitlock wrote:

To help you better, I need to know what tool you're using to create
the copy?  If you're using Maven, this is a known, unresolved
incompatibility of Maven.

It is?  Is there already a bug filed against Maven to fix this known problem?  I've been posting here with information to try to get an OK to say this is a bug in Subversion so I (or someone) can file it.

[Jeremy Whitlock]

> It is?  Is there already a bug filed against Maven to fix this known
> problem?  I've been posting here with information to try to get an OK to say
> this is a bug in Subversion so I (or someone) can file it.

Here are a few of the bugs filed for Maven:

http://jira.codehaus.org/browse/SCM-406
http://jira.codehaus.org/browse/MRELEASE-375

--
Take care,

Jeremy Whitlock
http://www.thoughtspark.org

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[James William Dumay]

Hey guys,
I'm the reporter of http://jira.codehaus.org/browse/SCM-406 - just dropping in to confirm that Maven does call out to the svn executable and that the problem occurs in the Subversion 1.5.2 release.

Running the same operation manually on the command line produces the same error experienced by maven users.
(eg, svn --non-interactive copy --file /tmp/maven-scm-33408250.commit . https://svn.atlassian.com/svn/private/atlassian/release-testing/tags/maven-release-testing-2)

I have a suspicion that this might be a compatibility issue between the 1.5 client and the 1.4 server - can anyone else confirm this?

Thanks
James

jrduncans wrote:

Mark Phippard-3 wrote:

On Tue, Aug 19, 2008 at 12:48 PM, Jeremy Whitlock <[e-mail]> wrote:
> Koichi,
>    I was informed by Mark Phippard today that there was a change in
> Subversion's copy feature from 1.4.x to 1.5.x that might be the cause
> of this:
>
> * correctly set the peg revision for copy in JavaHL (r31994)

I think someone said this worked in 1.5.0 and not 1.5.1, so I flagged
the above change from 1.5.1.

One thing I am not sure of is whether Maven even uses JavaHL.  It
might just run the SVN command line.  If it does not use JavaHL, then
all bets are off.  Likewise, someone should make sure it does not use
SVNKit, as that would then need to go to [e-mail]

--
Thanks

Mark Phippard
http://markphip.blogspot.com/

---------------------------------------------------------------------
To unsubscribe, e-mail: [e-mail]
For additional commands, e-mail: [e-mail]

The problem occurs on the command-line as discussed on the Maven mailing list in this thread: http://www.nabble.com/Release-fails-during-SVN-commit-td19084270.html and particularly this response: http://www.nabble.com/Re%3A-AW%3A-Release-fails-during-SVN-commit-p19089435.html

Specifically, it appears to be a problem using svn cp with the working-copy as the first argument.

-Stephen

[Jeremy Whitlock]

> Running the same operation manually on the command line produces the same
> error experienced by maven users.
> (eg, svn --non-interactive copy --file /tmp/maven-scm-33408250.commit .
> https://svn.atlassian.com/svn/private/atlassian/release-testing/tags/maven-release-testing-2)

Now that I see how Maven does it, I see that you may be experiencing a
Leopard bug.  Basically, the --non-interactive flag on Leopard does
not work.  For more details, here is the issue we have tracking this:

http://subversion.tigris.org/issues/show_bug.cgi?id=3059

I'm not completely up to date with it but check that out.  Issue 3059
also has links to other resources that might be useful.

> I have a suspicion that this might be a compatibility issue between the 1.5
> client and the 1.4 server - can anyone else confirm this?

That shouldn't be the case.  Better chance it's related to the issue
mentioned above.

--
Take care,

Jeremy Whitlock
http://www.thoughtspark.org

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[James William Dumay]

Jeremy,
If you read the issue I posted a link to you can see that this problem
occurs on both Mac OS 10.5 and Linux (Ubuntu).

Whats even stranger is that this problem occurs even if you run the
command manually without --non-interactive

I don't know how this would be related to svn's bug 3059 - this almost
certainly is a problem with Subversion.

Cheers,
James
 

On Mon, 2008-09-01 at 20:47 -0600, Jeremy Whitlock wrote:

> > Running the same operation manually on the command line produces the same
> > error experienced by maven users.
> > (eg, svn --non-interactive copy --file /tmp/maven-scm-33408250.commit .
> > https://svn.atlassian.com/svn/private/atlassian/release-testing/tags/maven-release-testing-2)
>
> Now that I see how Maven does it, I see that you may be experiencing a
> Leopard bug.  Basically, the --non-interactive flag on Leopard does
> not work.  For more details, here is the issue we have tracking this:
>
> http://subversion.tigris.org/issues/show_bug.cgi?id=3059
>
> I'm not completely up to date with it but check that out.  Issue 3059
> also has links to other resources that might be useful.
>
> > I have a suspicion that this might be a compatibility issue between the 1.5
> > client and the 1.4 server - can anyone else confirm this?
>
> That shouldn't be the case.  Better chance it's related to the issue
> mentioned above.
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Jeremy Whitlock]

> If you read the issue I posted a link to you can see that this problem
> occurs on both Mac OS 10.5 and Linux (Ubuntu).
>
> Whats even stranger is that this problem occurs even if you run the
> command manually without --non-interactive
>
> I don't know how this would be related to svn's bug 3059 - this almost
> certainly is a problem with Subversion.

It was just a shot in the dark.  I did, for some reason, forget that
this was not specific to OSX.  I guess the mystery continues on.

--
Take care,

Jeremy Whitlock
http://www.thoughtspark.org

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[James William Dumay]

On Mon, 2008-09-01 at 21:19 -0600, Jeremy Whitlock wrote:

> > If you read the issue I posted a link to you can see that this problem
> > occurs on both Mac OS 10.5 and Linux (Ubuntu).
> >
> > Whats even stranger is that this problem occurs even if you run the
> > command manually without --non-interactive
> >
> > I don't know how this would be related to svn's bug 3059 - this almost
> > certainly is a problem with Subversion.
>
> It was just a shot in the dark.  I did, for some reason, forget that
> this was not specific to OSX.  I guess the mystery continues on.
>

Thats cool :) Ill continue looking into it too...

James



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Michael Johns]

I have a little color I can add to this discussion.  We too use Maven, but I'm 99% sure this has nothing to do with it.  Here's what I've done:

1. Ran a release in Maven; failed with the error everyone else is seeing (svn: File '...' already exists)
2. In a command prompt on our build box, changed to the project's working directory that was created by the Maven build.  From there, ran a "svn --non-interactive copy -m <message> . <test destination>" manually (same command that Maven runs, save for an explicit message rather than --file).  Got the same error.
3. Queried the working copy to see if any files were changed.  No files were changed, but about 10 new files were present (relics from the aborted build).
4. Deleted the new files and ran the command again.  Failed again with same error.
5. Ran an update on my working copy.  No changes happened (no new files, deleted files, or changed files), but something happened because...
6. Ran the command again, and it worked.

Some things to note:

- We're on Windows Server 2003.
- I installed SVN using various methods (msi, unzip), and they all fail.  We have 1.5.2 with the Apache 2.0 bindings.
- This problem doesn't happen with SVN 1.5.0, but it does happen with 1.5.1.

To me, this most definitely appears to be a SVN bug.


Michael

-----Original Message-----
From: Jeremy Whitlock [mailto:jcscoobyrs@...]
Sent: Monday, September 01, 2008 11:19 PM
To: James William Dumay
Cc: users@...
Subject: Re: Mac OS X + SVN 1.5.1 = Branch problem

> If you read the issue I posted a link to you can see that this problem
> occurs on both Mac OS 10.5 and Linux (Ubuntu).
>
> Whats even stranger is that this problem occurs even if you run the
> command manually without --non-interactive
>
> I don't know how this would be related to svn's bug 3059 - this almost
> certainly is a problem with Subversion.

It was just a shot in the dark.  I did, for some reason, forget that
this was not specific to OSX.  I guess the mystery continues on.

--
Take care,

Jeremy Whitlock
http://www.thoughtspark.org

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...