> From: Philip Martin
> Sent: Friday, 9 August 2013 18:10 PM
> Geoff Field <geoff_fi...@aapl.com.au> writes:
> 
> > What about the Commit New Files error?  Will this be fixed 
> with 1.8.2, 
> > do you think?
> 
> I don't know how to reproduce it.  You said:
> 
>   Second issue: When committing new files, we get the message 
> that one of
>   them 'already exists'.  I've found as a workaround that 
> doing a clean
>   checkout to a NEW directory, then copying everything across 
> and running
>   a commit will work - once.
> 
> but if I were to attempt to reproduce it I would do
> 
>   svnadmin create repo
>   svn co http://localhost/repo wc
>   cp /bin/true wc/foo  # error message was for a binary file
>   svn add wc/foo
>   svn ci -mm wc
> 
> but that works.  That's no surprise because what I have done 
> is essentially what you say is a "workaround".  Until you can 
> come up with a better description of how to reproduce the 
> problem not much can be done.

Hello Philip,

Sometimes the workaround works, sometimes it doesn't.

Here's a log of a trial I have just done with a relatively fresh repository:

C:\>svn co https://aapleng1/Subversion/Playground/trunk/ \SVN_Test
A    SVN_Test\test.txt
Checked out revision 897.

C:\>cd SVN_Test

C:\SVN_Test>dir
 Volume in drive C is OSDisk
 Volume Serial Number is E49F-06D7

 Directory of C:\SVN_Test

12/08/2013  09:54 AM    <DIR>          .
12/08/2013  09:54 AM    <DIR>          ..
12/08/2013  09:54 AM                20 test.txt
               1 File(s)             20 bytes
               2 Dir(s)  160,268,779,520 bytes free

C:\SVN_Test>copy test.txt test2.txt
        1 file(s) copied.

C:\SVN_Test>svn add test2.txt
A         test2.txt

C:\SVN_Test>svn ci test2.txt --message "test 1.8.1 checkin"
Adding         test2.txt
svn: E155011: Commit failed (details follow):
svn: E155011: File 'C:\SVN_Test\test2.txt' is out of date
svn: E175005: File 'test2.txt' already exists

C:\SVN_Test>svn --version
svn, version 1.8.1 (r1503906)
   compiled Jul 22 2013, 18:46:03 on x86-microsoft-windows

Copyright (C) 2013 The Apache Software Foundation.
This software consists of contributions made by many people;
see the NOTICE file for more information.
Subversion is open source software, see http://subversion.apache.org/

The following repository access (RA) modules are available:

* ra_svn : Module for accessing a repository using the svn network protocol.
  - with Cyrus SASL authentication
  - handles 'svn' scheme
* ra_local : Module for accessing a repository on local disk.
  - handles 'file' scheme
* ra_serf : Module for accessing a repository via WebDAV protocol using serf.
  - handles 'http' scheme
  - handles 'https' scheme


C:\SVN_Test>


Again, server version is 1.2 (yes, yes, I will update this at some stage in the 
near future, but apparently I also have to update Apache, which adds an extra 
layer of nuisance).

This was the first time this repository had been touched since 2009.

"test.txt" is a standard ASCII text file containing the sentence "A quick test 
file." with one carriage return.

I hope this helps.

Regards,

Geoff
- The contents of this email, and any attachments, are strictly private
and confidential.
- It may contain legally privileged or sensitive information and is intended
solely for the individual or entity to which it is addressed.
- Only the intended recipient may review, reproduce, retransmit, disclose,
disseminate or otherwise use or take action in reliance upon the information
contained in this email and any attachments, with the permission of
Australian Arrow Pty. Ltd.
- If you have received this communication in error, please reply to the sender
immediately and promptly delete the email and attachments, together with
any copies, from all computers.
- It is your responsibility to scan this communication and any attached files
for computer viruses and other defects and we recommend that it be
subjected to your virus checking procedures prior to use.
- Australian Arrow Pty. Ltd. does not accept liability for any loss or damage
of any nature, howsoever caused, which may result
directly or indirectly from this communication or any attached files. 


Reply via email to