Hi, Steve,
Maybe one of the libsvn bindings for perl does a better service than calling
the command line utility?
Best regards
Markus Schaber
___
We software Automation.
3S-Smart Software Solutions GmbH
Markus Schaber | Developer
Memminger Str. 151 | 87439 Kempten | Ge
Hi, Rado,
> Von: [radoo] [mailto:ondas.rado...@gmail.com]
>
> I have a question whether subversion has possibility to allow checkout
> only the latest version of the repository.
No.
> My idea is (due to security) to allow only access only to the latest
> revision of the file stored in subversio
Yes, that is my take on it too Steve.
Not a problem. I will either figure out the SVN::Alien thing
or I will have to run the command from a pipe and watch it's
output.
Thank you all,
Chris
-Original Message-
From: Varnau, Steve (Neoview)
Sent: Monday, May 23, 2011 3:23 PM
To: Daniel
> -Original Message-
> From: Daniel Shahaf [mailto:d...@daniel.shahaf.name]
> Sent: Monday, May 23, 2011 2:37 PM
> To: Varnau, Steve (Neoview)
> Cc: Hahn, Christopher (SAN DIEGO); users@subversion.apache.org
> Subject: Re: SVN question
>
> 'svn up nonexistent' will pull in a file (inappr
Hi,
after some failed svnsync command, there is a svn-sync revprop on my repository
which keeps me from restoring synchronisation.
Failed to get lock on destination repos, currently held by 'ubuntu-05:...'
So I did the following:
svn propdel svn:sync-lock --revprop -r 0 https://myserver/svn/
'svn up nonexistent' will pull in a file (inappropriately) called
'nonexistent' that has been created on the server in a revision newer
than the BASE revision of the working copy.
Varnau, Steve (Neoview) wrote on Mon, May 23, 2011 at 21:30:26 +:
> svn does not always return success. For instan
Steve,
This is useful. I will keep an open mind.
Thank you,
Chris
From: Varnau, Steve (Neoview)
Sent: Monday, May 23, 2011 2:30 PM
To: Hahn, Christopher (SAN DIEGO); users@subversion.apache.org
Subject: RE: SVN question
svn does not always return success. For instance:
> svn ls
svn: '.' is
svn does not always return success. For instance:
> svn ls
svn: '.' is not a working copy
> echo $?
1
I think this is the more normal mode that I script against. I'm not sure why
the update sub-command is so forgiving.
-Steve
From: Hahn, Christopher (SAN DIEGO)
Sent: Monday, May 23, 2011 1:54
On Mon, May 23, 2011 at 16:54, Hahn, Christopher (SAN DIEGO)
wrote:
>
>
> I also saw thisI was wondering what users do to get something similar
> working.
>
> The same thing happens under Perforce. The command “p4” always returns a
> successful exit code. The way around that is the odd “-s”
Steve,
Thank you for taking the time.
I also saw thisI was wondering what users do to get something similar
working.
The same thing happens under Perforce. The command "p4" always returns a
successful exit code. The way around that is the odd "-s" switch which causes
the
tool to emit a s
Christopher,
The problem is not with your perl code. Apparently, update returns success if
you give it a path that does not exist in the current working directory.
Ø svn update foobar
At revision 3158.
Ø echo $?
0
For Svn 1.6.15, anyway. Seems to hold for linux & windows.
-Steve
From: H
Hello,
I have been wondering how best to capture errors from
the SVN command line.
I wanted to show you how a basic test is failing.
Consider the simple code snippet:
==
use strict;
my $options=" --username builduser --password ";
chdir("C:\\source");
Chris Evans wrote on Mon, May 23, 2011 at 18:28:15 +0100:
> Hi,
>
> I'm having issues using svnsync between 2 HTTP repositories. All was working
> well, but now I get the following error when running "svnsync.exe synchronize
> https://server/svn/repo/";
>
> svnsync:
> '/svn/repo/PROJECTT
Hi,
I'm having issues using svnsync between 2 HTTP repositories. All was working
well, but now I get the following error when running "svnsync.exe synchronize
https://server/svn/repo/";
svnsync:
'/svn/repo/PROJECTTest/trunk/PROJECT/Util/Test/TestSvn/TestCommitFile/ExistingFile.txt'
pa
On Monday 23 May 2011, [radoo] wrote:
> I have a question whether subversion has possibility to allow checkout
> only the latest version of the repository.
No. Let's assume that it could, you could still check out a recent version and
then update to the earlier version. Now, if you would disallow
Daniel Shahaf wrote on Mon, May 23, 2011 at 18:02:03 +0300:
> You could pretty easily cron something to move ^/trunk to ^/date/$date
> and then copy it back *without history*, along with suitable authz
> rules. But I've not the slightest clue why you'd want to do this.
Well, this won't work verba
There is no such feature built-in.
You could pretty easily cron something to move ^/trunk to ^/date/$date
and then copy it back *without history*, along with suitable authz
rules. But I've not the slightest clue why you'd want to do this.
It may well be the wrong solution to your problem, or the
Hello,
I have a question whether subversion has possibility to allow checkout
only the latest version of the repository.
My idea is (due to security) to allow only access only to the latest
revision of the file stored in subversion repository.
Or is there an option to set which would tell to keep
vys...@oksystem.cz wrote on Tue, May 10, 2011 at 12:20:36 +0200:
> I found "Decompression of svndiff data failed" message only in one
> file in sources - /libsvn_delta/svndiff.c - in the zlib_decode
> function. So, probably data in the repository in the file for this
> revision somehow corrupted du
On Tue, May 10, 2011 at 12:20:36PM +0200, vys...@oksystem.cz wrote:
> Hello.
>
>
> I use svn co to checkout my repo. All worked fine for a while, but today I
> get error
>
>
>
> Decompression of svndiff data failed: no size
What versions of Subversion are you running on your server and the c
This is the apache log:
[error] [client 10.48.129.165] could not open dbm files. [500, #5527096]
[error] [client 10.48.129.165] Can't open activity db: Unrecognized resolver
error [500, #5527096]
On Sat, May 21, 2011 at 6:47 AM, Daniel Shahaf wrote:
> Try figuring out what the error number is
Of course, have a thorough "make clean" target, and run it before
rebuilding. If necessary, run "svn st" and check that no unversioned files
remain (considering possible svn:ignore's you might have).
On Mon, May 23, 2011 at 01:10, Ryan Schmidt wrote:
>
> On May 22, 2011, at 14:36, Elad A wrote:
22 matches
Mail list logo
