exit status of svn commands

[Vincent Lefevre]

The exit status of svn commands doesn't seem to be specified,
at least not by "svn help ".

In particular, "svn update " and "svn status " seem
to always return with a 0 exit status on non-existing files.
This may be normal for "svn update" in a working copy, because
the command makes sense in case the file was added. Ditto for
"svn status": the user may want to test whether the file is in
base but has been removed with "rm", for instance. But I wonder
whether the 0 exit status is correct when not in a working copy.

There has already been a too short discussion about this:

  http://svn.haxx.se/users/archive-2006-03/0918.shtml

and there doesn't seem to be an entry in the issue tracker.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / Arénaire project (LIP, ENS-Lyon)

Re: Subversion 1.6 on Ubuntu Server 11.x

[Nico Kadel-Garcia]

On Sat, Jun 11, 2011 at 12:57 PM, Geoff Hoffman
 wrote:

>> Frankly, I find it more effective, and safer, to use SSH keys and a
>> key agent as necessary, with a key specifically dedicated to the SVN
>> access. This can be mandated with "SVN_SSH='ssh -l username -i
>> keyname'" to avoid using other keys.
>
>
> I don't mind doing this, but is this something that goes in .bash_profile?
> And would I then use svn+ssh://localhost/svn/repo/etc
> instead of http://localhost/svn/repo/etc?

Depends on your shell. .bashrc is good on Linux boxes with the default
shell of "bash". It's especially useful to configure when sudo'ing to
root environments, using hte "$SUDO_USER" setting. If willing to take
the thought out risks, one can even enable sudo to propagate the
"SVN_SSH" and "SSH_AUTH_SOCK" environment variables for just such
usage. This makes committing changes as a root user noticeably easier
and safer.

I still run into people who prefer tcsh or zsh or ksh, so the exact
implementation is sensitive.

Re: Index of Subversion add-on projects and products

[Mark Phippard]

I recall there was at least one Wikipedia page that was fairly accurate.

Sent from my iPhone

On Jun 11, 2011, at 5:34 PM, Daniel Shahaf  wrote:

> Ryan Schmidt wrote on Fri, Jun 10, 2011 at 18:37:24 -0500:
>> 
>> On Jun 10, 2011, at 17:09,  
>>  wrote:
>> 
>>> I was wondering if there is some sort of global list of Subversion 
>>> plug-ins, etc., including both open source projects and commercial products.
>>> 
>>> For example, it would be nice if there was a unified list of all the 
>>> different svn clients, integrations with build systems, etc.
>> 
>> The Subversion project used to maintain such a list but it became
>> unwieldy and was deleted. They now recommend you use Google to find
>> such things.
> 
> Or, you know, if someone in the community wants to maintain such a list
> themselves, there's no way (or want) for us to stop them from doing so...
> 
> How much does 10KB of web space cost these days again?
> 
>> You can still find the last version of this list in the
>> 1.6.x branch but it is gone from trunk:
>> 
>> http://svn.apache.org/repos/asf/subversion/branches/1.6.x/www/links.html
>> 
>> 
>> 
>> 
>> 
>> 

Re: Sparse check outs

[Daniel Shahaf]

There is svn-viewspec.py (somewhere under tools/ in the source tree),
I'm not sure if it can do what you ask for but it might be a starting
point.

Stuempfig, Thomas wrote on Fri, Jun 10, 2011 at 10:08:23 +:
> We use svn as a document management system.
> In our case we have different Roles in the same Project. We have Roles like 
> Project Manager, Business Consultants and Technical Consultants.
> 
> Each of them have their own kind of files they are interested in.
> My colleagues would like to sparse check out things based on some Rules like 
> "*pptx" in a folder and its sub folders. Would like to ignore specific 
> extensions like "*c,*cpp,*txt". Much the same way as the ignore list for non 
> versioned files, but just for co.
> 
> Did somebody come along such a requirement?
> 
> Regards
> Thomas

Re: Index of Subversion add-on projects and products

[Daniel Shahaf]

Ryan Schmidt wrote on Fri, Jun 10, 2011 at 18:37:24 -0500:
> 
> On Jun 10, 2011, at 17:09,  
>  wrote:
> 
> > I was wondering if there is some sort of global list of Subversion 
> > plug-ins, etc., including both open source projects and commercial products.
> >  
> > For example, it would be nice if there was a unified list of all the 
> > different svn clients, integrations with build systems, etc.
> 
> The Subversion project used to maintain such a list but it became
> unwieldy and was deleted. They now recommend you use Google to find
> such things.

Or, you know, if someone in the community wants to maintain such a list
themselves, there's no way (or want) for us to stop them from doing so...

How much does 10KB of web space cost these days again?

> You can still find the last version of this list in the
> 1.6.x branch but it is gone from trunk:
> 
> http://svn.apache.org/repos/asf/subversion/branches/1.6.x/www/links.html
> 
> 
> 
> 
> 
> 

Re: SVN Best Practices

[Daniel Shahaf]

Andreas Tscharner wrote on Fri, Jun 10, 2011 at 07:34:14 +0200:
> > I'm working on a document that states the industry's best
> > practices for SVN and would appreciate some guidance.  Can
> > anyone share or direct me to a good site that has useful
> > information that engineers have discovered while working with
> > SVN?  I know I can read the SVN manual and did, but looking
> > for real life experiences.  I did a google search for some
> > information but a helping hand to further my research would
> > be appreciated.
> 
> Did you see: 
> http://svn.apache.org/repos/asf/subversion/trunk/doc/user/svn-best-practices.html
> 

Did you check the last modification date of that file?

> Best regards
>   Andreas
> --
> Andreas Tscharner  
> --
> "Intruder on level one. All Aliens please proceed to level one."
>   -- Call in "Alien: Resurrection"
> 
> 
> CT-Dienstleistungen neu bei Wenzel Metromec
> ===
> 
> Haben Sie einen Prototyp ohne Zeichnung oder Konstruktionsmodell?
> Suchen Sie in Ihren Bauteilen Materialschäden, Risse und Poren?
> Dann sind unsere neuen Dienstleistungen im Bereich der Computertomographie 
> die perfekte Lösung für Ihre Anforderungen!
> 
> Testen Sie uns und unsere neue WENZEL exaCT Anlage.
> Zögern Sie nicht und nehmen Sie noch heute mit uns Kontakt auf.
> mailto:c...@metromec.ch?subject=CT-Dienstleistungen
> 

Re: Subversion 1.6 on Ubuntu Server 11.x

[Geoff Hoffman]

On Sat, Jun 11, 2011 at 8:27 AM, Nico Kadel-Garcia  wrote:

> On Fri, Jun 10, 2011 at 6:26 PM, Geoff Hoffman
>  wrote:
> > I posted about this on the Ubuntu forums but thus far nobody has replied.
> > When SSH'd into the box and using svn operations, I'm getting the
> dastardly
> > warning about my password is going to get stored to disk unencrypted.
> > I read about Subversion 1.6 security changes.
> > I read about Subversion 1.6 on Ubuntu Server over at superuser.com.
> > I read about gnome-keyring over at stackoverflow.
> > I've been doing a lot of reading on it.
> > I have done the following:
> > * installed gnome-keyring
> > *edited my ~/.subversion/config to turn
> > password-stores = gnome-keyring
> > edited my ~/.subversion/servers to
> > store-passwords = yes
> > store-plaintext-passwords = no
> > Thing is, I'm not using any GUI so it's still not working. Should I try
> > encfs ?
> > I read another post about a tool from CollabNet called keyring_tool but I
> > don't have it on this system. Where do I get that? I've never run into
> these
> > issues before (new distro, new svn version).
> > Any additional insight would be very much appreciated.
>
> I have *never* gotten the gnome keyrings working well with Subversion.
> I'm afraid there are a lot of subtly distinct implementations of the
> necessary toolchain out therem abd the lot of them tend to be pretty
> fragile.
>
>
Hmm.



> Frankly, I find it more effective, and safer, to use SSH keys and a
> key agent as necessary, with a key specifically dedicated to the SVN
> access. This can be mandated with "SVN_SSH='ssh -l username -i
> keyname'" to avoid using other keys.
>


I don't mind doing this, but is this something that goes in .bash_profile?

And would I then use svn+ssh://localhost/svn/repo/etc
instead of http://localhost/svn/repo/etc?





> The stored SSH public keys on the remote server can even be set to
> restrict access to only svnserve tunneling, even to read-only access.
> Coupled with the kind of single svn user account setup described in
> passing in the "Red Book", it's a better security model than giving
> all SVN clients shell access to the server.
>

Re: Subversion 1.6 on Ubuntu Server 11.x

[Nico Kadel-Garcia]

On Fri, Jun 10, 2011 at 6:26 PM, Geoff Hoffman
 wrote:
> I posted about this on the Ubuntu forums but thus far nobody has replied.
> When SSH'd into the box and using svn operations, I'm getting the dastardly
> warning about my password is going to get stored to disk unencrypted.
> I read about Subversion 1.6 security changes.
> I read about Subversion 1.6 on Ubuntu Server over at superuser.com.
> I read about gnome-keyring over at stackoverflow.
> I've been doing a lot of reading on it.
> I have done the following:
> * installed gnome-keyring
> *edited my ~/.subversion/config to turn
> password-stores = gnome-keyring
> edited my ~/.subversion/servers to
> store-passwords = yes
> store-plaintext-passwords = no
> Thing is, I'm not using any GUI so it's still not working. Should I try
> encfs ?
> I read another post about a tool from CollabNet called keyring_tool but I
> don't have it on this system. Where do I get that? I've never run into these
> issues before (new distro, new svn version).
> Any additional insight would be very much appreciated.

I have *never* gotten the gnome keyrings working well with Subversion.
I'm afraid there are a lot of subtly distinct implementations of the
necessary toolchain out therem abd the lot of them tend to be pretty
fragile.

Frankly, I find it more effective, and safer, to use SSH keys and a
key agent as necessary, with a key specifically dedicated to the SVN
access. This can be mandated with "SVN_SSH='ssh -l username -i
keyname'" to avoid using other keys.

The stored SSH public keys on the remote server can even be set to
restrict access to only svnserve tunneling, even to read-only access.
Coupled with the kind of single svn user account setup described in
passing in the "Red Book", it's a better security model than giving
all SVN clients shell access to the server.