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

Issue 2310

From: Giovanni Bajo <rasky_at_develer.com>
Date: 2005-06-01 03:49:09 CEST

Hello,

thank you for the answer. I apologize about my incorrect technical terms, which
might have confused the bug report. I will try to explain it again from
scratch.

I have a working copy of a repository of SVN itself (branch 1.2.x), which is in
a "broken" status. With broken, I mean that if you run "svn up" using a SVN 1.2
client (Linux Fedora Core 3), it will simply hang (or take *forever* to
complete) without displaying anything on stdout/stderr, and it will not
promptly abort if sent CTRL+C (sometimes it manages to quit after a few minutes
after I pressed CTRL+C, other times I just kill it). I postulate this to be a
bug, irrespective of how I managed to produce/corrupt the working copy.

The working copy is a checkout from http://svn.collab.net/repos/svn/trunk/ (I
apologize for mentioning svnserve, this was obviously wrong). The bug can
easily be reproduced by downloading the following tarball:
http://farfetch.intrepid.cx/subversion-1.2-broken.tar.bz2
unpacking it, and running "svn up" from within the directory it creates (under
Linux).

I believe I answered all your questions. Let me know if you are still missing
valuable information.

Thanks,
Giovanni Bajo

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jun 1 03:54:11 2005

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