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

Re: Problem committing .doc files

From: Glen Barber <hexidigital_at_gmail.com>
Date: 2007-08-30 03:08:03 CEST

Quoting Ryan Schmidt:
> On Aug 29, 2007, at 23:25, Glen Barber wrote:
>> I've asked in the #svn channel on irc.freenode.net about this and was
>> told to post this question to the list. As far as right now, I haven't
>> found a solution that won't corrupt my working copies (and possibly my
>> repository).
>> When I edit a .doc file using MS Word 2003, on occasion I get the error
>> stating my "working copy may be out-of-date." This message repeats even
>> after I 'svn up' and try to re-commit. The only 2 solutions I have
>> found are:
>> 1.) Renaming the file, adding the file, committing, and removing the
>> old file.
>> 2.) Deleting the .svn/all-wcprops file will allow me to commit (I found
>> this on google, and I am aware that tinkering with anything in the .svn
>> directory is a very bad idea -- so this isn't my choice solution).
>> I am using TortoiseSVN 1.4.5 on Windows XP Home, and the server runs
>> Subversion 1.4.4 compiled from the FreeBSD 6.2-RELEASE ports.
> I'm not familiar with a message that your working copy *may* be
> out-of-date. I *am* familiar with a message that your working copy *is*
> out-of-date, and it is a perfectly normal message that may occur for
> several reasons which are detailed here:
> http://subversion.tigris.org/faq.html#wc-out-of-date

You're correct -- it is saying it 'is' out of date.
> But after running "svn update", your working copy should now be up-to-date.

As stated in my initial post, `svn update` does not change my working

> Please try checking out a new working copy ("svn checkout <url> <dir>") and
> see if you can replicate the problem there. If not, you've solved your
> problem. Get rid of the old working copy, after manually moving any changes
> over to the new one.

This problem occurs with Microsoft Office 2003 (specifically .doc files
-- I don't use many other office formats). Checking out a new working
copy is not a solution, because I am the only person committing to this
specific repository.

> If you still have the problem in the new working copy, please show us the
> exact error messages you're getting as this should help us isolate the
> problem.

When I get out of work and on my laptop, I'll replicate the problem, and
paste exactly what I did - step by step - and hopefully someone else can
replicate it.

Glen Barber
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Aug 30 03:05:21 2007

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.