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

Can't copy 'man3\.svn\tmp\text-base\qpicture.3qt.svn-base'

From: cppjavaperl <cppjavaperl_at_yahoo.com>
Date: 2005-06-18 07:36:09 CEST

Hello everyone,

  While trying to checkout Qt 3.3.3 from my own local repository, I got
this error message (the ... indicates paths I've shortened):

svn: Can't copy '...man3\.svn\tmp\text-base\qpicture.3qt.svn-base' to
'...man3\qpicture.3qt.tmp': The system cannot find the file specified.

So, I did a Google search, and found out that others are having the
same problem (with Qt in a different repository):

http://lists.kde.org/?l=kde-devel&m=111874813312841&w=4

<quoting-from-above-link>

Hello,

While checking out qt-copy from SVN using this command:
svn co https://svn.kde.org/home/kde/trunk/qt-copy

I get the following error message (after it has checked out a large
portion of qt-copy successfully):

A qt-copy/doc/man/man3/QBig5Codec.3qt
A qt-copy/doc/man/man3/qxmllocator.3qt
subversion/libsvn_wc/log.c:329: (apr_err=155009)
svn: In directory 'qt-copy/doc/man/man3'
subversion/libsvn_subr/io.c:548: (apr_err=2)
svn: Can't copy
'qt-copy/doc/man/man3/.svn/tmp/text-base/qpicture.3qt.svn-base' to
'qt-copy/doc/man/man3/qpicture.3qt.tmp': No such file or directory

If I then try to 'cd qt-copy; svn up', I get:

subversion/libsvn_wc/lock.c:157: (apr_err=155004)
svn: Working copy 'doc/man/man3' locked
svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for
details)

<end-quoting>

So, I decided to try checking out from another repository also, and
found the anonymous svn access for KDE. I ran the following command...

svn co svn://anonsvn.kde.org/home/kde/trunk/qt-copy/doc/man/man3

... and got the following error message:

svn: Can't copy 'man3\.svn\tmp\text-base\qpicture.3qt.svn-base' to
'man3\qpicture.3qt.tmp': The system cannot find the file specified.

Bingo! It was the exact same problem I had.

I only get this error when I check out on a Windows 2000 box. The
Windows 2000 machine has the latest Subversion client binaries -- 1.2.0
(downloaded from the subversion.tigris.org website).

My Subversion server is running on a Suse 9.1 Linux box. The
Subversion version on the server is 1.1.2. The Subversion client on
the Linux box, is (as would be expected) also version 1.1.2. When I
checkout to a local directory on the Linux box (the same one hosting
the server process), I don't have any trouble. I suspect that the
problem is the different version of Subversion client vs. Subversion
server, but have not verified that yet.

Here are the version/revision numbers for each of the two machines:

Windows 2000 Box (subversion client): version 1.2.0 (r14790)
Linux Box (subversion client): version 1.1.2 (r12471)
Linux Box (subversion server): version 1.1.2 (r12471)

Acting on the hunch that it was a problem of mismatching client/server
versions, I installed version 1.1.2 (r12471) of the Subversion client
on my Windows 2000 box. But alas, no dice, even with the matching
client for Windows 2000. I ran the following command (again)...

svn co svn://anonsvn.kde.org/home/kde/trunk/qt-copy/doc/man/man3

... and got the following error message:

svn: Can't copy 'man3\.svn\tmp\text-base\qpicture.3qt.svn-base' to
'man3\qpicture.3qt.tmp': The system cannot find the file specified.

Sigh.

Anyone have any idea what's causing this? I got the same results (as I
expected I would) whether running 'svn' from the command line or using
Tortoise SVN from the GUI in Windows 2000.

cppjavaperl

                
____________________________________________________
Yahoo! Sports
Rekindle the Rivalries. Sign up for Fantasy Football
http://football.fantasysports.yahoo.com

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Jun 18 12:28:42 2005

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.