"Michael Abele" wrote
> Ok, I'll try to do...
> Please tell me what it should include beside a full transcript
> and our system configuration?
Sorry, you're asking the wrong person. I am only guessing at what will be
important. I would think the essential part is to establish a command line
recipe that works repeatably on your system, preferably with a fresh
repository and not an existing huge one. If you can do that then any other
differences can probably be tracked down later, so long as you can continue
to reproduce the problem. I would suggest for starters:
Server OS
Server program & version (apache/svnserve/file)
Connection protocol
Connection method (LAN/internet)
Client OS
Client SVN version
Simon
-----Original Message-----
"Michael Abele" wrote
> Yes, you're right.
> So I did another quick command line test:
> ...
> svn: REPORT request failed on '/svn/test/testrepos/!svn/vcc/default'
> svn: File not found: transaction '10', path
'/folder1/folder2/text5.txt'
>
> So full paths in folders below the root folder seem to cause the
> problem... Any comments on this?
Yes. If this recipe works reliably and you can document it fully so the
SVN devs can reproduce it as well, you are a hero :-)
Full paths had been identified as a contributory factor a few days ago
(see the issue tracker), but so far no-one has been able to reproduce it
reliably enough to debug.
You might want to include the info on server config, access protocol,
whether access is over LAN/WAN, client & server OS, etc. The difficulty
in reproducing may be due to some combination of circumstances; who
knows which ones are relevant?
Simon
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Sep 15 15:00:52 2004