Problem committing .doc files

[Glen Barber]

Hi folks.  

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.  

Has anyone else had this problem?  Is there a way to fix it?
--
Glen Barber

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

[Mark Reibert]

On Thu, 2007-08-30 at 00:25 -0400, Glen Barber wrote:
> 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:

If you have edited the (non-text-mergeable, aka binary) file then 'svn
up' will simply leave you with a merge conflict that must be manually
resolved. After doing so you should be able to commit. See:

http://svnbook.red-bean.com/en/1.4/svn.branchmerge.copychanges.html#svn.branchmerge.copychanges.bestprac.merge

Note this has nothing to do with a .doc file, per se, but rather it is a
situation that will result from simultaneous edits on a file that cannot
be textually merged. Your best bet is to avoid this situation via locks
and the svn:needs-lock property. See:

http://svnbook.red-bean.com/en/1.4/svn.advanced.locking.html#svn.advanced.locking.lock-communication

--
----------------------
Mark S. Reibert, Ph.D.
svn@...
----------------------

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

[Glen Barber]

Quoting Mark Reibert:

> On Thu, 2007-08-30 at 00:25 -0400, Glen Barber wrote:
> > 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:
>
> If you have edited the (non-text-mergeable, aka binary) file then 'svn
> up' will simply leave you with a merge conflict that must be manually
> resolved. After doing so you should be able to commit. See:
>
> http://svnbook.red-bean.com/en/1.4/svn.branchmerge.copychanges.html#svn.branchmerge.copychanges.bestprac.merge
>
> Note this has nothing to do with a .doc file, per se, but rather it is a
> situation that will result from simultaneous edits on a file that cannot
> be textually merged. Your best bet is to avoid this situation via locks
> and the svn:needs-lock property. See:
>
> http://svnbook.red-bean.com/en/1.4/svn.advanced.locking.html#svn.advanced.locking.lock-communication
>

I (sort of) see what you're saying.  I'll take a look at both docs, and
appreciate your quick response.

--
Glen Barber

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

[Glen Barber]

Quoting Glen Barber:

> Quoting Mark Reibert:
> > On Thu, 2007-08-30 at 00:25 -0400, Glen Barber wrote:
> > > 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:
> >
> > If you have edited the (non-text-mergeable, aka binary) file then 'svn
> > up' will simply leave you with a merge conflict that must be manually
> > resolved. After doing so you should be able to commit. See:
> >
> > http://svnbook.red-bean.com/en/1.4/svn.branchmerge.copychanges.html#svn.branchmerge.copychanges.bestprac.merge
> >
> > Note this has nothing to do with a .doc file, per se, but rather it is a
> > situation that will result from simultaneous edits on a file that cannot
> > be textually merged. Your best bet is to avoid this situation via locks
> > and the svn:needs-lock property. See:
> >
> > http://svnbook.red-bean.com/en/1.4/svn.advanced.locking.html#svn.advanced.locking.lock-communication
> >
> I (sort of) see what you're saying.  I'll take a look at both docs, and
> appreciate your quick response.
>

Actually -- neither of those docs helped... I created locks for the
files, not realizing at first what I was doing (it's late, and i'm tired
:P ).  I am the only editor of those files... I edit from 1 of 2
operating systems, Linux (Ubuntu Feisty, specifically, and Windows XP
Home).  Creating locks created more problems (that I can tell).  

Any other ideas?
--
Glen Barber

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

[T. Wassermann]

Hi,

nothing to the topic - but Glen, can you check your system date and this
of your mailserver?

By now it's 08/29/2007 9:43 UTC - your last mail is timestamped with
08/30/2007 10:18. Writing from the future, eh? ;)

Bye


Tobias

Glen Barber schrieb:

> Quoting Glen Barber:
>  
>> Quoting Mark Reibert:
>>    
>>> On Thu, 2007-08-30 at 00:25 -0400, Glen Barber wrote:
>>>      
>>>> 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:
>>>>        
>>> If you have edited the (non-text-mergeable, aka binary) file then 'svn
>>> up' will simply leave you with a merge conflict that must be manually
>>> resolved. After doing so you should be able to commit. See:
>>>
>>> http://svnbook.red-bean.com/en/1.4/svn.branchmerge.copychanges.html#svn.branchmerge.copychanges.bestprac.merge
>>>
>>> Note this has nothing to do with a .doc file, per se, but rather it is a
>>> situation that will result from simultaneous edits on a file that cannot
>>> be textually merged. Your best bet is to avoid this situation via locks
>>> and the svn:needs-lock property. See:
>>>
>>> http://svnbook.red-bean.com/en/1.4/svn.advanced.locking.html#svn.advanced.locking.lock-communication
>>>
>>>      
>> I (sort of) see what you're saying.  I'll take a look at both docs, and
>> appreciate your quick response.
>>
>>    
> Actually -- neither of those docs helped... I created locks for the
> files, not realizing at first what I was doing (it's late, and i'm tired
> :P ).  I am the only editor of those files... I edit from 1 of 2
> operating systems, Linux (Ubuntu Feisty, specifically, and Windows XP
> Home).  Creating locks created more problems (that I can tell).  
>
> Any other ideas?
>  

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

[Glen Barber]

Quoting T. Wassermann:

> Hi,
>
> nothing to the topic - but Glen, can you check your system date and this of
> your mailserver?
>
> By now it's 08/29/2007 9:43 UTC - your last mail is timestamped with
> 08/30/2007 10:18. Writing from the future, eh? ;)
>
> Bye
>
>

I am from a different internet.  :)  As far as I can tell, my system
time and mailserver times are okay.  (Although, that made me wonder for
a few mintues if that was my SVN commit problem). At the time of this
writing, it is 5:15am EDT, so it may have been just because I literally
am a few hours ahead?

 

--
Glen Barber

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

[Glen Barber]

Quoting T. Wassermann:

> Hi,
>
> nothing to the topic - but Glen, can you check your system date and this of
> your mailserver?
>
> By now it's 08/29/2007 9:43 UTC - your last mail is timestamped with
> 08/30/2007 10:18. Writing from the future, eh? ;)
>
> Bye
>
>
> Tobias
>

Hmm.. now that I actually thought about the Geographics of our world, I
realized my time IS off.  Thanks for pointing that out!
--
Glen Barber

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

[Mark Reibert]

On Thu, 2007-08-30 at 04:18 -0400, Glen Barber wrote:

> Quoting Glen Barber:
> > Quoting Mark Reibert:
> > > On Thu, 2007-08-30 at 00:25 -0400, Glen Barber wrote:
> > > > 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:
> >
> Actually -- neither of those docs helped... I created locks for the
> files, not realizing at first what I was doing (it's late, and i'm tired
> :P ).  I am the only editor of those files... I edit from 1 of 2
> operating systems, Linux (Ubuntu Feisty, specifically, and Windows XP
> Home).  Creating locks created more problems (that I can tell).  
>
> Any other ideas?

Not exactly. I am wondering what kind of problems the lock created.

SVN locks are tied to a particular working copy, not just a user. If you
are editing from multiple systems then, from the lock's perspective,
there are multiple editors and you would need to release the lock from
one system before obtaining it from the other. (Alternatively, you can
break the lock.)

Did you read:

http://svnbook.red-bean.com/en/1.4/svn.advanced.locking.html#svn.advanced.locking.creation

In particular, the "Regarding lock tokens" inset (yellow-ish) box a
little down the page?

--
----------------------
Mark S. Reibert, Ph.D.
svn@...
----------------------

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

[Ryan Schmidt-23]

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

But after running "svn update", your working copy should now be up-to-
date.

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.

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.



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

[Glen Barber]

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
copy.  

> 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@...
For additional commands, e-mail: users-help@...

[Rainer Sokoll]

On Wed, Aug 29, 2007 at 09:08:03PM -0400, Glen Barber wrote:
> Quoting Ryan Schmidt:

> > 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
> copy.  

Do an "svn info" on the doc in your WC as well as on the doc in your
repo.
Do the revisions match?

Rainer

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

[Glen Barber]

Quoting Rainer Sokoll:

> On Wed, Aug 29, 2007 at 09:08:03PM -0400, Glen Barber wrote:
> > Quoting Ryan Schmidt:
>
> > > 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
> > copy.  
>
> Do an "svn info" on the doc in your WC as well as on the doc in your
> repo.
> Do the revisions match?
>
> Rainer
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...

Here is the exact error, copied from TortoiseSVN.  

Modified: E:\backup\New Microsoft Word Document.doc
Error: Commit failed (details follow):
Error: Your file or directory 'New Microsoft Word Document.doc' is
probably out-of-date
Error: The version resource does not correspond to the resource within
the transaction.  Either the requested version resource is out of date
(needs to be updated), or the requested version resource is newer than
the transaction root (restart the commit).

Regarding the revisions in the repository, and the working copy, I was
really hoping for them to differ, since that would provide some clue as
to what is going on -- but (un)fortunately, they are the same.


--
Glen Barber

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

[Ryan Schmidt-23]

On Aug 29, 2007, at 20:08, Glen Barber wrote:

> Quoting Ryan Schmidt:
>
>> 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
> copy.

I know you stated that, but I've never heard of an instance of this  
message that wasn't resolved by "svn update" so I wanted to make  
absolutely sure.

>> 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.

Working copies in Subversion are considered disposable. It occurs  
from time to time that a working copy becomes corrupted in some way,  
and the suggestion in those cases is to check out a new working copy.  
It's a useful troubleshooting step.


On Aug 30, 2007, at 10:11, Glen Barber wrote:

> Here is the exact error, copied from TortoiseSVN.
>
> Modified: E:\backup\New Microsoft Word Document.doc
> Error: Commit failed (details follow):
> Error: Your file or directory 'New Microsoft Word Document.doc' is
> probably out-of-date
> Error: The version resource does not correspond to the resource within
> the transaction.  Either the requested version resource is out of date
> (needs to be updated), or the requested version resource is newer than
> the transaction root (restart the commit).

Ok. And you're absolutely sure that running "svn update" now does not  
allow you to commit?

If so, can you provide us with a reproduction recipe for this issue,  
starting from creating the repository and creating the initial files?  
Otherwise I'm not sure how to troubleshoot this further.

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

[Glen Barber]

>
> I know you stated that, but I've never heard of an instance of this message
> that wasn't resolved by "svn update" so I wanted to make absolutely sure.
>
That's why I'm posting here. :)  I have even done some extensive
Googling, and (as stated in the initial post) deleting the
.svn/all-wcprops file is the only non-extensive way to correct the
working copy to allow me to commit.  (And if I understand correctly, I
risk corruption of my data in both the working copy and the repository.)
>
> Working copies in Subversion are considered disposable. It occurs from time
> to time that a working copy becomes corrupted in some way, and the
> suggestion in those cases is to check out a new working copy. It's a useful
> troubleshooting step.
>
I have tried checking out a new WC, but no avail.
>
>
> Ok. And you're absolutely sure that running "svn update" now does not allow
> you to commit?
>
> If so, can you provide us with a reproduction recipe for this issue,
> starting from creating the repository and creating the initial files?
> Otherwise I'm not sure how to troubleshoot this further.
1.)  Assuming the repository is created, and empty (with all default
settings), check out from the 'client.'

2.)  Create a new .doc file in MS Word.  I have been using the word
"Ping" in the file initially (irrelevant).

3.)  Add & Commit the file.

4.)  Edit the file, appending "Pong" as a second line.

5.)  Commit  (the first edit sometimes succeeds).

6.)  `svn up`

7.)  Edit the file, appending something as a third line.

8.)  Commit -- this is where I receive errors.  

Anything other information needed, let me know.  

(Also, this may be related to .doc files -- I have tried creating .rar
and .zip files containing the documents I need to keep versioned.  I
expected it to 'just work' since it wasn't a .doc file -- but I was
wrong.  I have tested what I am doing with .txt files, and just Unix
'filename', no-extension files, and everything works as it should.)


--
Glen Barber

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

[Mark Reibert]

On Thu, 2007-08-30 at 17:30 -0400, Glen Barber wrote:

> 1.)  Assuming the repository is created, and empty (with all default
> settings), check out from the 'client.'
>
> 2.)  Create a new .doc file in MS Word.  I have been using the word
> "Ping" in the file initially (irrelevant).
>
> 3.)  Add & Commit the file.
>
> 4.)  Edit the file, appending "Pong" as a second line.
>
> 5.)  Commit  (the first edit sometimes succeeds).
>
> 6.)  `svn up`
>
> 7.)  Edit the file, appending something as a third line.
>
> 8.)  Commit -- this is where I receive errors.  

Just followed these steps and cannot reproduce the problem. Everything
worked as expected; that is, the last commit worked just fine.

I am using SVN 1.4.5, both server and client.

--
----------------------
Mark S. Reibert, Ph.D.
svn@...
----------------------

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

[Glen Barber]

Quoting Mark Reibert:

> On Thu, 2007-08-30 at 17:30 -0400, Glen Barber wrote:
> > 1.)  Assuming the repository is created, and empty (with all default
> > settings), check out from the 'client.'
> >
> > 2.)  Create a new .doc file in MS Word.  I have been using the word
> > "Ping" in the file initially (irrelevant).
> >
> > 3.)  Add & Commit the file.
> >
> > 4.)  Edit the file, appending "Pong" as a second line.
> >
> > 5.)  Commit  (the first edit sometimes succeeds).
> >
> > 6.)  `svn up`
> >
> > 7.)  Edit the file, appending something as a third line.
> >
> > 8.)  Commit -- this is where I receive errors.  
>
> Just followed these steps and cannot reproduce the problem. Everything
> worked as expected; that is, the last commit worked just fine.
>
> I am using SVN 1.4.5, both server and client.
>

I have svnserve running as a service on my laptop -- tomorrow I'll see
if I can reproduce the problem following the above steps.  

Say, for instance, I cannot get the problem to reproduce.  Should I look
at the FreeBSD ports version of SVN as the problem?  Perhaps I should
compile from source?  (These are just a few things I thought of off the
top of my head -- if anyone has any other ideas, I'd love to hear them.)

Cheers

--
Glen Barber

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

[Glen Barber]

Also, if it helps, I can attach screen shots of exactly what I am
seeing.  (Although, I don't know how helpful this would be.)
--
Glen Barber

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

[Mark Reibert]

On Fri, 2007-08-31 at 01:50 -0400, Glen Barber wrote:

> Quoting Mark Reibert:
> > On Thu, 2007-08-30 at 17:30 -0400, Glen Barber wrote:
> > > 1.)  Assuming the repository is created, and empty (with all default
> > > settings), check out from the 'client.'
> > >
> > > 2.)  Create a new .doc file in MS Word.  I have been using the word
> > > "Ping" in the file initially (irrelevant).
> > >
> > > 3.)  Add & Commit the file.
> > >
> > > 4.)  Edit the file, appending "Pong" as a second line.
> > >
> > > 5.)  Commit  (the first edit sometimes succeeds).
> > >
> > > 6.)  `svn up`
> > >
> > > 7.)  Edit the file, appending something as a third line.
> > >
> > > 8.)  Commit -- this is where I receive errors.  
> >
> > Just followed these steps and cannot reproduce the problem. Everything
> > worked as expected; that is, the last commit worked just fine.
> >
> > I am using SVN 1.4.5, both server and client.
> >
> I have svnserve running as a service on my laptop -- tomorrow I'll see
> if I can reproduce the problem following the above steps.  

Well now I am confused ... I thought those *were* the reproduction
steps!

> Say, for instance, I cannot get the problem to reproduce.  Should I look
> at the FreeBSD ports version of SVN as the problem?  Perhaps I should
> compile from source?  (These are just a few things I thought of off the
> top of my head -- if anyone has any other ideas, I'd love to hear them.)

Anything is possible, but it just does not feel right that such a
fundamental and catastrophic problem would have slipped into a port. I
compile SVN all the time and the included test suite is extensive.

I think you are going to have to provide the minimum, complete, and
consistent reproduction steps along with the specifics of your client
and server configuration ...

--
----------------------
Mark S. Reibert, Ph.D.
svn@...
----------------------

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

[Glen Barber]

Quoting Mark Reibert:

> On Fri, 2007-08-31 at 01:50 -0400, Glen Barber wrote:
> > Quoting Mark Reibert:
> > > On Thu, 2007-08-30 at 17:30 -0400, Glen Barber wrote:
> > > > 1.)  Assuming the repository is created, and empty (with all default
> > > > settings), check out from the 'client.'
> > > >
> > > > 2.)  Create a new .doc file in MS Word.  I have been using the word
> > > > "Ping" in the file initially (irrelevant).
> > > >
> > > > 3.)  Add & Commit the file.
> > > >
> > > > 4.)  Edit the file, appending "Pong" as a second line.
> > > >
> > > > 5.)  Commit  (the first edit sometimes succeeds).
> > > >
> > > > 6.)  `svn up`
> > > >
> > > > 7.)  Edit the file, appending something as a third line.
> > > >
> > > > 8.)  Commit -- this is where I receive errors.  
> > >
> > > Just followed these steps and cannot reproduce the problem. Everything
> > > worked as expected; that is, the last commit worked just fine.
> > >
> > > I am using SVN 1.4.5, both server and client.
> > >
> > I have svnserve running as a service on my laptop -- tomorrow I'll see
> > if I can reproduce the problem following the above steps.  
>
> Well now I am confused ... I thought those *were* the reproduction
> steps!

They are the steps on my actual SVN server -- I have svnserve installed
on my laptop from a while back.

>
> > Say, for instance, I cannot get the problem to reproduce.  Should I look
> > at the FreeBSD ports version of SVN as the problem?  Perhaps I should
> > compile from source?  (These are just a few things I thought of off the
> > top of my head -- if anyone has any other ideas, I'd love to hear them.)
>
> Anything is possible, but it just does not feel right that such a
> fundamental and catastrophic problem would have slipped into a port. I
> compile SVN all the time and the included test suite is extensive.
>
> I think you are going to have to provide the minimum, complete, and
> consistent reproduction steps along with the specifics of your client
> and server configuration ...

Server configuration:
Apache/2.2.4 (FreeBSD)
mod_ssl/2.2.4
OpenSSL/0.9.7e-p1
DAV/2
SVN/1.4.4
PHP/5.2.3 with Suhosin-Patch


If you need information on how I compiled SVN and created the
repositories, I'd be happy to provide them -- however, I did not use any
'extra' options, or patches, or such.

(Btw, if this matters, I have SVN served via HTTPS, not HTTP on Apache
2.2.4).

--
Glen Barber

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

[Mark Reibert]

On Fri, 2007-08-31 at 03:08 -0400, Glen Barber wrote:

> Quoting Mark Reibert:
> > On Fri, 2007-08-31 at 01:50 -0400, Glen Barber wrote:
> > > Say, for instance, I cannot get the problem to reproduce.  Should I look
> > > at the FreeBSD ports version of SVN as the problem?  Perhaps I should
> > > compile from source?  (These are just a few things I thought of off the
> > > top of my head -- if anyone has any other ideas, I'd love to hear them.)
> >
> > Anything is possible, but it just does not feel right that such a
> > fundamental and catastrophic problem would have slipped into a port. I
> > compile SVN all the time and the included test suite is extensive.
> >
> > I think you are going to have to provide the minimum, complete, and
> > consistent reproduction steps along with the specifics of your client
> > and server configuration ...
>
> Server configuration:
> Apache/2.2.4 (FreeBSD)
> mod_ssl/2.2.4
> OpenSSL/0.9.7e-p1
> DAV/2
> SVN/1.4.4
> PHP/5.2.3 with Suhosin-Patch
>
>
> If you need information on how I compiled SVN and created the
> repositories, I'd be happy to provide them -- however, I did not use any
> 'extra' options, or patches, or such.
>
> (Btw, if this matters, I have SVN served via HTTPS, not HTTP on Apache
> 2.2.4).

Should not matter ...

Is there anything else you can provide regarding the client side of the
problem? Have you tried tracking your steps in a parallel working copy
to make sure the commits are getting into the repo?

Have you run "svn cleanup" on your working copy?

If you have access to the repo, does "svnadmin verify <path>" look
normal?

I am reaching a bit here, but am running out of ideas since I cannot
reproduce the problem nor envision a scenario in which it would exist.

Mark

--
----------------------
Mark S. Reibert, Ph.D.
svn@...
----------------------

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