[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: New Files Always Rejected in 1.8.1+

From: Geoff Field <Geoff_Field_at_aapl.com.au>
Date: Fri, 30 Aug 2013 13:11:03 +1000

Hi Alex

________________________________
From: BladeOfLight16 [mailto:bladeoflight16_at_gmail.com]
Sent: Friday, 30 August 2013 12:11 PM
To: users_at_tortoisesvn.tigris.org
Subject: Re: New Files Always Rejected in 1.8.1+

Can you reproduce with the command line tools? If so, this could be a problem with SVN rather than TortoiseSVN, and would need to be reported to the SVN user list.

It has already been reported (although not much has been done about it) and it IS a problem with SVN. Specifically, it's to do with the interaction with older server versions.

For details of what I posted and did, see the thread started by me here:
http://svn.haxx.se/users/archive-2013-08/0035.shtml
 ... or here:
http://mail-archives.apache.org/mod_mbox/subversion-users/201308.mbox/ajax/%3C4A2A8BDDBE6EFE4199FB22121DB971B102486BA6%40AAPLExchange.aapl.com.au%3E
On Thu, Aug 29, 2013 at 4:00 PM, Alex Pasternak <APasternak_at_xrite.com<mailto:APasternak_at_xrite.com>> wrote:
In versions of TortoiseSVN after 1.8.0, I cannot commit any new files to the server, without getting the error message that it already exists. E.g.,

Error: File 'ServiceTests/TestFiles/Service.db.corrupted' already exists
Error: You have to update your working copy first.
Yes, I've seen that message, too, all too often.

This aborts the entire check-in. In all cases, the files do not actually exist, and updating does nothing. 1.8.0 can commit these files in the Added state with no problem. SVN Cleanup does nothing, reboot does nothing.
Important question: What server software version are you running? We were running 1.2.3, which caused all sorts of issues interacting with SVN1.8.1.
The issue is very repeatable for me, as it happens on any new file. I just installed and uninstalled each of the versions to below to confirm.
We found the issue very repeatable, too, although I didn't try backtracking to 1.8.0. We went straight from 1.7.13 (which worked reliably with the old server software) to 1.8.1 (which didn't).

Issue does NOT occur in:
TortoiseSVN-1.8.0.24401-x64-svn-1.8.0

Issue occurs in:
TortoiseSVN-1.8.1.24570-x64-svn-1.8.1
TortoiseSVN-1.8.2.24708-x64-svn-1.8.3

My system: Win 7 Pro, SP1 (6.1), 64-bit OS

I am happy to provide more details if necessary. I do not see this issue being mentioned in either the forum or the change log, so I hope I did my " homework".
The important details that are missing are the details of your SVN server.

I think you might have to upgrade your server software, as we did (if that's an option for you). But here's a caveat: If you have a repository that's in BDB format, it will need to be upgraded to FSFS format. There's a discussion about that archived starting here:
http://svn.haxx.se/users/archive-2013-08/0370.shtml
... or here:
http://mail-archives.apache.org/mod_mbox/subversion-users/201308.mbox/ajax/%3C4A2A8BDDBE6EFE4199FB22121DB971B102515A4E%40AAPLExchange.aapl.com.au%3E
Regards,

Geoff

--
Apologies for the auto-generated legal boilerplate added by our IT department:
- 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.
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3063604
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2013-08-30 05:11:19 CEST

This is an archived mail posted to the TortoiseSVN Users mailing list.