> We still don't have enough information to understand the problem. Does
> the problem occur if update individual subdirectories of files? What is
> the smallest part of the working copy that causes the problem?
I deleted the all of the relevant code subdirectories and still got the
exception, s
If you start Perforce without a license file you are restricted in the number
of users/clients allowed, but it is still possible to use a suitable repository
(or copy thereof). The "free" limit used to be 2 users/5 clients, but I see
the latest release (2011.1) allows 20 users/20 clients withou
On Jan 19, 2012, at 13:52 , Markus Schaber wrote:
> Hi,
>
> For our SharpSVN based client, we want to include some regression tests for
> scenarios including SSL and/or server authentication. For this, we need
> several servers (svnserve, svn+ssh, mod_svn) in different setups (e. G.
> plain,
Hi,
For our SharpSVN based client, we want to include some regression tests for
scenarios including SSL and/or server authentication. For this, we need several
servers (svnserve, svn+ssh, mod_svn) in different setups (e. G. plain, SSL, SSL
+ client certificates).
We cannot rely on a fixed test
On Jan 17, 2012, at 16:10 , Evan Wee wrote:
> How would we open a ticket for this issue? Or would Issue 4091 cover this
> case?
>
(cc-ing users@ again)
I made a test and opened a ticket, since it's a different symptom than
the #4091 problem.
http://subversion.tigris.org/issues/show_bug.cgi?id
Frank Capodieci writes:
>> What is the nature of the changes that update was trying to pull? (You
>> can determine that with 'svn log -q -v -r BASE:HEAD', or with the
>> equivalent Tortoise screen.) Specifically, do they include any tree
>> changes, or symlink changes?
>
> There were a couple o
All,
I was trying to migrate a perforce database to SVN using p42svn.pl (0.21
version) script. This requires the perforce to be 2006 or later. However my
perforce version is 2005.2. Is there a way I can migrate the database from
perforce to svn retaining the version history ? Upgrading perforce
