Fwd: hi, need help with svn command checkout
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: > > > i build a system that store revision id when a branch is ready for QA. > > the developer use "ready to qa" string in his comment when commit. > > there is a post commit script that collect the revision and insert it to > a DB. > > > > the QA goes to a web page that populate the "ready to QA" projects. > > after the QA choose the project he wants to check, the web page generate > install_rev.bat file for the QA to run on his machine. > > > > until this point everything is working like it should. > > > > my question is whats the command that should be in install_rev.bat file? > > > > i want that the QA will start from fresh. for example if now the QA > checks for a project "mobile" revision 1000. > > and he wants to check after that "mobile" revision 900. > > > > the environment should be clean from revision 1000 files and folders and > should have only 900 files and folders. > > > > whats the command i should use? > > i cant delete the folder, fresh chcekout takes about 20 minutes. > > Assuming the QA person has not made any changes in the working copy (that > is, "svn status" returns nothing), then they can simply run "svn up -r 900". > > > >
Re: Issue in commit: Can't open activity db: Unrecognized resolver error
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. > > (the error text comes from apr_os_strerror(), see there for pointers on > how to interpret the error number) > > Daniel wrote on Thu, May 19, 2011 at 18:12:10 -0300: > > In a working repository, I started to having the following error message: > > > > Commit > > Commit failed (details follow): > > Can't open activity db: Unrecognized resolver error > > > > I checked that svn/repo/dav and it has 777 permissions, then I chown all > the > > repo with 777 but still have the same error > > > > Any ideas? > > > > Note: the environment is Solaris > > > > Thanks, > > Daniel > -- _ * Daniel Oliva Bianco* _
Re: Decompression of svndiff data failed
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 clients?
Re: Decompression of svndiff data failed
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 during or after commit? Am I right or > there's another reason of these errors (I googled, but what I found is > not my case)? svndiff is used both in the backend (for storing revisions of files as binary deltas against previous revisions) and on the wire (if both client and server ≥1.4, for transmitting the delta from what the client has (or from the empty file) to the request revision's contents).
SVN - restriction to checkout only the latest version
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 only the latest version or last 10 versions? Thanks for your answers, Rado
Re: SVN - restriction to checkout only the latest version
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 right solution to a non-problem, etc. So you'll understand why I'm unable to say I recommend doing this. [radoo] wrote on Mon, May 23, 2011 at 16:16:53 +0200: > 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 only the latest > version or last 10 versions? > > Thanks for your answers, > > Rado
Re: SVN - restriction to checkout only the latest version
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 verbatim. But the opposite (copying trunk to /$date without history) should be fine.
Re: SVN - restriction to checkout only the latest version
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 updating to an earlier version, too, by simply not giving out anything but the most recent data, you also couldn't update, since that just passes the changes relative to the WC's BASE revision. So this isn't just a missing feature but rather a fundamental thing. > My idea is (due to security) to allow only access only to the latest > revision of the file stored in subversion repository. I'm not sure what you would achieve with that or how that is related to "security". If you elaborated on that, maybe people could suggest a different approach? > Or is there an option to set which would tell to keep only the latest > version or last 10 versions? Neither. This is also a fundamental design choice that no data is ever discarded. Of course, with raw repository access you still could erase things from a repository, but this isn't the "normal" operation mode. If you want, you could install a post-commit script that takes some source code and publishes it via FTP/HTTP. You could then immediately remove old versions when a new version is available. However, this basically boils down to blocking all repository access and doing the distribution/publishing with something else, not with Subversion. Cheers! Uli ** Domino Laser GmbH, Fangdieckstraße 75a, 22547 Hamburg, Deutschland Geschäftsführer: Thorsten Föcking, Amtsgericht Hamburg HR B62 932 ** Visit our website at http://www.dominolaser.com ** Diese E-Mail einschließlich sämtlicher Anhänge ist nur für den Adressaten bestimmt und kann vertrauliche Informationen enthalten. Bitte benachrichtigen Sie den Absender umgehend, falls Sie nicht der beabsichtigte Empfänger sein sollten. Die E-Mail ist in diesem Fall zu löschen und darf weder gelesen, weitergeleitet, veröffentlicht oder anderweitig benutzt werden. E-Mails können durch Dritte gelesen werden und Viren sowie nichtautorisierte Änderungen enthalten. Domino Laser GmbH ist für diese Folgen nicht verantwortlich. **
svnsync path not found
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' path not found That file looks fine using svn log and svn cat.I get the following errors on the target SVN server: Could not CHECKOUT resource /svn/ repo /!svn/ver/222731/PROJECTTest/trunk/PROJECT/Util/Test/TestSvn/TestCommitFile/ExistingFile.txt. [409, #0] Could not get created-rev of transaction node. [404, #160013] File not found: transaction '222731-4rvu', path '/PROJECTTest/trunk/PROJECT/Util/Test/TestSvn/TestCommitFile/ExistingFile.txt' [404, #160013] Attempting to find that transition on the source server fails with: svnlook: No such transaction Running the syncsync again errors with a different transaction number. Any ideas what could be causing this. I'm using svn version 1.6.16 on VisualSVN Server 2.1.7 Thanks Chris *bypass*
Re: svnsync path not found
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/PROJECTTest/trunk/PROJECT/Util/Test/TestSvn/TestCommitFile/ExistingFile.txt' > path not found > > That file looks fine using svn log and svn cat.I get the following errors on > the target SVN server: > > Could not CHECKOUT resource /svn/ repo > /!svn/ver/222731/PROJECTTest/trunk/PROJECT/Util/Test/TestSvn/TestCommitFile/ExistingFile.txt. > [409, #0] > > Could not get created-rev of transaction node. [404, #160013] > > File not found: transaction '222731-4rvu', path > '/PROJECTTest/trunk/PROJECT/Util/Test/TestSvn/TestCommitFile/ExistingFile.txt' > [404, #160013] > > Attempting to find that transition on the source server fails with: > > svnlook: No such transaction > > Running the syncsync again errors with a different transaction number. > > > Any ideas what could be causing this. issue #3641 (to be fixed in 1.6.17) perhaps? > I'm using svn version 1.6.16 on VisualSVN Server 2.1.7 > > Thanks > Chris > > *bypass*
SVN question
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");
my $output = `svn update --depth=infinity mang $options`;
die "svn failed with errorcode $?" if $?;
print "We survived!\n";
==
This command works if the "mang" above is changed to "main"
(which does exist at c:\source).
However, both code have this result:
==
C:\source\cm\script>perl svntest.pl
We survived!
C:\source\cm\script>perl svntest.pl
We survived!
==
What am I doing wrong?
Chris
[cid:image001.png@01CC193A.444C7240]
Christopher Hahn
The Dude
Software Production Engineering
R&D Services, Hewlett-Packard
Phone: 858-655-4096
Cell: 619-630-9791
ch...@hp.com
Visit our SPE Portal
<>
RE: SVN question
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: Hahn, Christopher (SAN DIEGO)
Sent: Monday, May 23, 2011 11:34 AM
To: users@subversion.apache.org
Subject: SVN question
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");
my $output = `svn update --depth=infinity mang $options`;
die "svn failed with errorcode $?" if $?;
print "We survived!\n";
==
This command works if the "mang" above is changed to "main"
(which does exist at c:\source).
However, both code have this result:
==
C:\source\cm\script>perl svntest.pl
We survived!
C:\source\cm\script>perl svntest.pl
We survived!
==
What am I doing wrong?
Chris
[cid:image001.png@01CAF080.AD65F1E0]
Christopher Hahn
The Dude
Software Production Engineering
R&D Services, Hewlett-Packard
Phone: 858-655-4096
Cell: 619-630-9791
ch...@hp.com
Visit our SPE Portal
<>
RE: SVN question
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 string like "exit: #" where the underlying commands success or
failure
was specified. Is there perhaps some similar technique for SVN?
I checked the svn Global Options and did not see anything similar.
I suppose that I can just use a pipe and watch for strings that I expect.
Take care,
Christopher
From: Varnau, Steve (Neoview)
Sent: Monday, May 23, 2011 1:33 PM
To: Hahn, Christopher (SAN DIEGO); users@subversion.apache.org
Subject: RE: SVN question
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: Hahn, Christopher (SAN DIEGO)
Sent: Monday, May 23, 2011 11:34 AM
To: users@subversion.apache.org
Subject: SVN question
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");
my $output = `svn update --depth=infinity mang $options`;
die "svn failed with errorcode $?" if $?;
print "We survived!\n";
==
This command works if the "mang" above is changed to "main"
(which does exist at c:\source).
However, both code have this result:
==
C:\source\cm\script>perl svntest.pl
We survived!
C:\source\cm\script>perl svntest.pl
We survived!
==
What am I doing wrong?
Chris
[cid:image001.png@01CC1950.9640A9C0]
Christopher Hahn
The Dude
Software Production Engineering
R&D Services, Hewlett-Packard
Phone: 858-655-4096
Cell: 619-630-9791
ch...@hp.com
Visit our SPE Portal
<>
Re: SVN question
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” switch which
> causes the
> tool to emit a string like “exit: #” where the underlying commands success or
> failure
> was specified. Is there perhaps some similar technique for SVN?
>
> I checked the svn Global Options and did not see anything similar.
>
> I suppose that I can just use a pipe and watch for strings that I expect.
I think most people doing a lot of SVN work within Perl are using the
Perl bindings, or SVN module off CPAN.
>
> From: Varnau, Steve (Neoview)
> Sent: Monday, May 23, 2011 1:33 PM
> To: Hahn, Christopher (SAN DIEGO); users@subversion.apache.org
> Subject: RE: SVN question
>
>
>
> 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: Hahn, Christopher (SAN DIEGO)
> Sent: Monday, May 23, 2011 11:34 AM
> To: users@subversion.apache.org
> Subject: SVN question
>
>
>
> 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");
>
> my $output = `svn update --depth=infinity mang $options`;
>
>
>
> die "svn failed with errorcode $?" if $?;
>
> print "We survived!\n";
>
> ==
>
>
>
> This command works if the “mang” above is changed to “main”
>
> (which does exist at c:\source).
>
>
>
> However, both code have this result:
>
> ==
>
> C:\source\cm\script>perl svntest.pl
>
> We survived!
>
>
>
> C:\source\cm\script>perl svntest.pl
>
> We survived!
>
> ==
>
>
>
> What am I doing wrong?
>
>
>
> Chris
>
>
>
>
>
> Christopher Hahn
> The Dude
>
> Software Production Engineering
> R&D Services, Hewlett-Packard
> Phone: 858-655-4096
> Cell: 619-630-9791
> ch...@hp.com
>
>
>
> Visit our SPE Portal
>
>
>
>
>
>
RE: SVN question
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 PM
To: Varnau, Steve (Neoview); users@subversion.apache.org
Subject: RE: SVN question
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 string like "exit: #" where the underlying commands success or
failure
was specified. Is there perhaps some similar technique for SVN?
I checked the svn Global Options and did not see anything similar.
I suppose that I can just use a pipe and watch for strings that I expect.
Take care,
Christopher
From: Varnau, Steve (Neoview)
Sent: Monday, May 23, 2011 1:33 PM
To: Hahn, Christopher (SAN DIEGO); users@subversion.apache.org
Subject: RE: SVN question
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: Hahn, Christopher (SAN DIEGO)
Sent: Monday, May 23, 2011 11:34 AM
To: users@subversion.apache.org
Subject: SVN question
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");
my $output = `svn update --depth=infinity mang $options`;
die "svn failed with errorcode $?" if $?;
print "We survived!\n";
==
This command works if the "mang" above is changed to "main"
(which does exist at c:\source).
However, both code have this result:
==
C:\source\cm\script>perl svntest.pl
We survived!
C:\source\cm\script>perl svntest.pl
We survived!
==
What am I doing wrong?
Chris
[cid:image001.png@01CAF080.AD65F1E0]
Christopher Hahn
The Dude
Software Production Engineering
R&D Services, Hewlett-Packard
Phone: 858-655-4096
Cell: 619-630-9791
ch...@hp.com
Visit our SPE Portal
<>
RE: SVN question
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 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 PM
To: Varnau, Steve (Neoview); users@subversion.apache.org
Subject: RE: SVN question
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 string like "exit: #" where the underlying commands success or
failure
was specified. Is there perhaps some similar technique for SVN?
I checked the svn Global Options and did not see anything similar.
I suppose that I can just use a pipe and watch for strings that I expect.
Take care,
Christopher
From: Varnau, Steve (Neoview)
Sent: Monday, May 23, 2011 1:33 PM
To: Hahn, Christopher (SAN DIEGO); users@subversion.apache.org
Subject: RE: SVN question
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: Hahn, Christopher (SAN DIEGO)
Sent: Monday, May 23, 2011 11:34 AM
To: users@subversion.apache.org
Subject: SVN question
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");
my $output = `svn update --depth=infinity mang $options`;
die "svn failed with errorcode $?" if $?;
print "We survived!\n";
==
This command works if the "mang" above is changed to "main"
(which does exist at c:\source).
However, both code have this result:
==
C:\source\cm\script>perl svntest.pl
We survived!
C:\source\cm\script>perl svntest.pl
We survived!
==
What am I doing wrong?
Chris
[cid:image001.png@01CC1956.37A19540]
Christopher Hahn
The Dude
Software Production Engineering
R&D Services, Hewlett-Packard
Phone: 858-655-4096
Cell: 619-630-9791
ch...@hp.com
Visit our SPE Portal
<>
Re: SVN question
'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 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 PM
> To: Varnau, Steve (Neoview); users@subversion.apache.org
> Subject: RE: SVN question
>
> 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 string like "exit: #" where the underlying commands success or
> failure
> was specified. Is there perhaps some similar technique for SVN?
>
> I checked the svn Global Options and did not see anything similar.
>
> I suppose that I can just use a pipe and watch for strings that I expect.
>
> Take care,
>
> Christopher
>
> From: Varnau, Steve (Neoview)
> Sent: Monday, May 23, 2011 1:33 PM
> To: Hahn, Christopher (SAN DIEGO); users@subversion.apache.org
> Subject: RE: SVN question
>
> 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: Hahn, Christopher (SAN DIEGO)
> Sent: Monday, May 23, 2011 11:34 AM
> To: users@subversion.apache.org
> Subject: SVN question
>
> 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");
> my $output = `svn update --depth=infinity mang $options`;
>
> die "svn failed with errorcode $?" if $?;
> print "We survived!\n";
> ==
>
> This command works if the "mang" above is changed to "main"
> (which does exist at c:\source).
>
> However, both code have this result:
> ==
> C:\source\cm\script>perl svntest.pl
> We survived!
>
> C:\source\cm\script>perl svntest.pl
> We survived!
> ==
>
> What am I doing wrong?
>
> Chris
>
>
>
> [cid:image001.png@01CAF080.AD65F1E0]
>
> Christopher Hahn
> The Dude
> Software Production Engineering
> R&D Services, Hewlett-Packard
> Phone: 858-655-4096
> Cell: 619-630-9791
> ch...@hp.com
>
> Visit our SPE Portal
>
>
>
>
>
Cannot delete revprop?
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/myRepo --username=... --password=... I get: property 'svn:sync-lock' deleted from repository revision 0 But when I do this thereafter: svn proplist --revprop -r 0 https://myserver/svn/myRepo --username=... --password=... I get this: Unversioned properties on revision 0: svn:sync-from-uuid svn:sync-lock svn:sync-currently-copying svn:sync-last-merged-rev svn:date svn:sync-from-url So obviously it was not delete at all? What can I do? Regards, Mala
RE: SVN question
> -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 (inappropriately) called
> 'nonexistent' that has been created on the server in a revision newer
> than the BASE revision of the working copy.
Quite true, but update does not complain whether or not it finds such a file.
That seems a bit surprising.
It also does not give an error if the current directory is not a working copy,
and it can't figure out where to update from:
> svn update foobar
Skipped 'foobar'
Okay, at least it gives a message, but not returning error, seems... surprising.
-Steve
>
> Varnau, Steve (Neoview) wrote on Mon, May 23, 2011 at 21:30:26 +:
> > 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 PM
> > To: Varnau, Steve (Neoview); users@subversion.apache.org
> > Subject: RE: SVN question
> >
> > 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 string like "exit: #" where the underlying commands
> success or failure
> > was specified. Is there perhaps some similar technique for SVN?
> >
> > I checked the svn Global Options and did not see anything similar.
> >
> > I suppose that I can just use a pipe and watch for strings that I
> expect.
> >
> > Take care,
> >
> > Christopher
> >
> > From: Varnau, Steve (Neoview)
> > Sent: Monday, May 23, 2011 1:33 PM
> > To: Hahn, Christopher (SAN DIEGO); users@subversion.apache.org
> > Subject: RE: SVN question
> >
> > 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: Hahn, Christopher (SAN DIEGO)
> > Sent: Monday, May 23, 2011 11:34 AM
> > To: users@subversion.apache.org
> > Subject: SVN question
> >
> > 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");
> > my $output = `svn update --depth=infinity mang $options`;
> >
> > die "svn failed with errorcode $?" if $?;
> > print "We survived!\n";
> > ==
> >
> > This command works if the "mang" above is changed to "main"
> > (which does exist at c:\source).
> >
> > However, both code have this result:
> > ==
> > C:\source\cm\script>perl svntest.pl
> > We survived!
> >
> > C:\source\cm\script>perl svntest.pl
> > We survived!
> > ==
> >
> > What am I doing wrong?
> >
> > Chris
> >
> >
> >
> > [cid:image001.png@01CAF080.AD65F1E0]
> >
> > Christopher Hahn
> > The Dude
> > Software Production Engineering
> > R&D Services, Hewlett-Packard
> > Phone: 858-655-4096
> > Cell: 619-630-9791
> > ch...@hp.com
> >
> > Visit our SPE
> Portal
> >
> >
> >
> >
> >
>
RE: SVN question
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 Shahaf
Cc: Hahn, Christopher (SAN DIEGO); users@subversion.apache.org
Subject: RE: SVN question
> -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 (inappropriately) called
> 'nonexistent' that has been created on the server in a revision newer
> than the BASE revision of the working copy.
Quite true, but update does not complain whether or not it finds such a file.
That seems a bit surprising.
It also does not give an error if the current directory is not a working copy,
and it can't figure out where to update from:
> svn update foobar
Skipped 'foobar'
Okay, at least it gives a message, but not returning error, seems... surprising.
-Steve
>
> Varnau, Steve (Neoview) wrote on Mon, May 23, 2011 at 21:30:26 +:
> > 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 PM
> > To: Varnau, Steve (Neoview); users@subversion.apache.org
> > Subject: RE: SVN question
> >
> > 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 string like "exit: #" where the underlying commands
> success or failure
> > was specified. Is there perhaps some similar technique for SVN?
> >
> > I checked the svn Global Options and did not see anything similar.
> >
> > I suppose that I can just use a pipe and watch for strings that I
> expect.
> >
> > Take care,
> >
> > Christopher
> >
> > From: Varnau, Steve (Neoview)
> > Sent: Monday, May 23, 2011 1:33 PM
> > To: Hahn, Christopher (SAN DIEGO); users@subversion.apache.org
> > Subject: RE: SVN question
> >
> > 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: Hahn, Christopher (SAN DIEGO)
> > Sent: Monday, May 23, 2011 11:34 AM
> > To: users@subversion.apache.org
> > Subject: SVN question
> >
> > 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");
> > my $output = `svn update --depth=infinity mang $options`;
> >
> > die "svn failed with errorcode $?" if $?;
> > print "We survived!\n";
> > ==
> >
> > This command works if the "mang" above is changed to "main"
> > (which does exist at c:\source).
> >
> > However, both code have this result:
> > ==
> > C:\source\cm\script>perl svntest.pl
> > We survived!
> >
> > C:\source\cm\script>perl svntest.pl
> > We survived!
> > ==
> >
> > What am I doing wrong?
> >
> > Chris
> >
> >
> >
> > [cid:image001.png@01CAF080.AD65F1E0]
> >
> > Christopher Hahn
> > The Dude
> > Software Production Engineering
> > R&D Services, Hewlett-Packard
> > Phone: 858-655-4096
> > Cell: 619-630-9791
> > ch...@hp.com
> >
> > Visit our SPE
> Portal
> >
> >
> >
> >
> >
>
AW: SVN - restriction to checkout only the latest version
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 subversion repository. My gut feeling is that if you try to base security on an assumption like this, something in your security design is fundamentally broken. > Or is there an option to set which would tell to keep only the latest > version or last 10 versions? You can either dump the repository from that revision, and then build a new repository from the dump. Maybe svndumpfilter can also help. If your problem is that you accidentally committed some files into the repository which should not be seen by anyone, that your problem could be solved by an action like that. Maybe you try to describe us the problem you want to solve, and then we can help you to find a (better) solution? Best regards Markus Schaber ___ We software Automation. 3S-Smart Software Solutions GmbH Markus Schaber | Developer Memminger Str. 151 | 87439 Kempten | Germany | Tel. +49-831-54031-0 | Fax +49-831-54031-50 Email: m.scha...@3s-software.com | Web: http://www.3s-software.com CoDeSys internet forum: http://forum.3s-software.com Download CoDeSys sample projects: http://www.3s-software.com/index.shtml?sample_projects Managing Directors: Dipl.Inf. Dieter Hess, Dipl.Inf. Manfred Werner | Trade register: Kempten HRB 6186 | Tax ID No.: DE 167014915
AW: SVN question
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 | Germany | Tel. +49-831-54031-0 | Fax
+49-831-54031-50
Email: m.scha...@3s-software.com | Web: http://www.3s-software.com
CoDeSys internet forum: http://forum.3s-software.com
Download CoDeSys sample projects:
http://www.3s-software.com/index.shtml?sample_projects
Managing Directors: Dipl.Inf. Dieter Hess, Dipl.Inf. Manfred Werner | Trade
register: Kempten HRB 6186 | Tax ID No.: DE 167014915
Von: Hahn, Christopher (SAN DIEGO) [mailto:christopher.h...@hp.com]
Gesendet: Montag, 23. Mai 2011 22:54
An: Varnau, Steve (Neoview); users@subversion.apache.org
Betreff: RE: SVN question
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 string like “exit: #” where the underlying commands success or
failure
was specified. Is there perhaps some similar technique for SVN?
I checked the svn Global Options and did not see anything similar.
I suppose that I can just use a pipe and watch for strings that I expect.
Take care,
Christopher
From: Varnau, Steve (Neoview)
Sent: Monday, May 23, 2011 1:33 PM
To: Hahn, Christopher (SAN DIEGO); users@subversion.apache.org
Subject: RE: SVN question
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: Hahn, Christopher (SAN DIEGO)
Sent: Monday, May 23, 2011 11:34 AM
To: users@subversion.apache.org
Subject: SVN question
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");
my $output = `svn update --depth=infinity mang $options`;
die "svn failed with errorcode $?" if $?;
print "We survived!\n";
==
This command works if the “mang” above is changed to “main”
(which does exist at c:\source).
However, both code have this result:
==
C:\source\cm\script>perl svntest.pl
We survived!
C:\source\cm\script>perl svntest.pl
We survived!
==
What am I doing wrong?
Chris
Christopher Hahn
The Dude
Software Production Engineering
R&D Services, Hewlett-Packard
Phone: 858-655-4096
Cell: 619-630-9791
ch...@hp.com
Visit our SPE Portal
