On Friday 08 January 2010, Mayuresh Kasture wrote:
> I followed these steps which didn't work,
>
> I installed svn 1.4.6 because I guess this was the version installed on
> the old server. []
> And then, using tortoise, tried to checkout "svn:\\localhost\". I got
> error "expected FS format 2 f
Sorry for the redundant post. But, I forgot to mention the operating
systems. Old server had Windows Vista and new server has Windows 7.
On Fri, Jan 8, 2010 at 2:21 AM, Mayuresh Kasture
wrote:
> Hi,
>
> I was using subversion with tortoise few months ago. Then, I had to
> change the server. Hence
Hi,
I was using subversion with tortoise few months ago. Then, I had to
change the server. Hence, I copied svn/repos directory from the server
as a backup. I don't remember the version of the svn installed on old
server. What is the best way to get the repository working on new
server?
I followed
On Jan 6, 2010, at 23:53, Shalinda Adikari wrote:
> I’m working on svn mirroring capability and I have following issue when it is
> used.
>
> Once svnsync is configured It takes longer time than normal commit. Simply if
> we can commit a file within 2s without svnsync mirroring , now it takes
Greetings, Robert Ribnitz!
> I have just had a look at subversion from the admin side; I have used it as
> a user for quite some time. I was looking through the manuals, and could
> not find it anywhere:
> - Can the svn server be configured in such as way as to use the Pluggable
> Authentication
OS: Windows Server 2003 R2. Client Server: Windows XP Professional 2002, SP 2
SVN version 1.6.3, File System repository structure
Built custom pre- and post-commit hooks, which make various svn calls to
examine transaction, allow the commit, then examing the revision to extract
information for
Rob van Oostrum wrote:
"Cleaning up" your branches is a bad idea. It just creates that much
more administrative overhead. Not to mention having to tiptoe around
the deletions when merging the branch back to trunk, which will affect
merge tracking's performance.
What I would do instead is leve
There is absolutely no reason why you can't restructure your
repository. The only thing you have to be careful about is people who
currently use your repository layout. If you move the roots of
projects, people who have a current checkout will have problems trying
to do a commit.
How many project
Hi all,
I'm new on this group so thank you by advance for your help and I hope
that this is the good group !
I'm using subversive 2.2.1 with Java Eclipse.
I created my project, I worked on it. I created a tag...continue to
develop, commit, update...all is perfect.
I'm trying to create a new tag
C. Michael Pilato wrote:
> Sure. Ideally, the client would be able to say, "I had trouble parsing the
> XML in the response, namely this bit here: asdf"
>
> Wanna dive in and look into a patch?
>
Actually the svn: in property names should never have been
interpreted as an XML namespace n
Now you sound exactly as my boss sounds when I propose a fix somewhere :)
Not sure where to dive for the moment, we are mere users of SVN at the time
being, but if this error prevails we might have to dig deeper. Thanks for the
help though, great job you guys do!
Geir
-Original Message---
Upon Installation of Setup-Subversion-1.6.6.msi there is following
problem, when installed as superuser: the installer cannot modify the path
variable, apparently it tries to modify the administrator's path.
When installed as administrator, the path is modified, but only for the
administrat
Hi,
I have troubles by using SVN+SSH on the older Solaris machine. If I'm
working with SVN+SSH commands, it's still returning this error message
(if I'm using the same checkout commands on my Ubuntu 9.04 everything
works well):
command-line: line 0: Bad configuration option: ControlMaster
svn:
Shalinda Adikari wrote:
While going through some of the forums, I found following command to do the
task.
$SVNSYNC synchronize URL_TO_MIRROR_REPO --username=svnsync
--password=svnsyncpassword>/dev/null 2>/dev/null&
But this solution is rather different to yours one. As you mention in your repl
Hi Didier,
Thanks for your quick reply. It's really great.
While going through some of the forums, I found following command to do the
task.
$SVNSYNC synchronize URL_TO_MIRROR_REPO --username=svnsync
--password=svnsyncpassword >/dev/null 2>/dev/null &
But this solution is rather different to
Shalinda Adikari wrote:
Hi Team,
I’m working on svn mirroring capability and I have following issue when
it is used.
Once *svnsync* is configured It takes longer time than normal commit.
Simply if we can commit a file within 2s without svnsync mirroring , now
it takes nearly 6s. Therefore,
From: Shalinda Adikari
Sent: Thursday, January 07, 2010 11:15 AM
To: 'iss...@subversion.tigris.org'
Subject: How to run post-commit as a backgorund process??
Hi Team,
I'm working on svn mirroring capability and I have following issue when
it is used.
Once svnsync is configured It
17 matches
Mail list logo