Re: Size of wc.db

2012-12-03 Thread Philip Martin 
Ross Lagerwall  writes:

> The resulting .svn dir is about 19000 files and 522MiB. However, wc.db
> is 203MiB. This seems huge compared with the size of the checkout. Is
> this normal? Is there any way to get this file to be smaller?

Subversion doesn't enable auto_vacuum so run:

  sqlite3 .svn/wc.db "vacuum" 

http://sqlite.org/lang_vacuum.html

-- 
Certified & Supported Apache Subversion Downloads:
http://www.wandisco.com/subversion/download

Re: Offering my time for building & running the test suite

2012-12-03 Thread Philip Martin 
swdev  writes:

> I would like to offer my computer and time to help building and running the
> Subversion test suite, but without impacting my existing configuration.
>
> Is this possible? e.g. to build and run Subversion in a local directory
> i.e. /home/svn-local ?

Yes. You can configure a Subversion build to install into any path you
choose. The testsuite generally runs in the build directory and you
don't need to install Subversion to run the tests.

-- 
Certified & Supported Apache Subversion Downloads:
http://www.wandisco.com/subversion/download

Re: Size of wc.db

2012-12-03 Thread Ross Lagerwall 
On Mon, Dec 03, 2012 at 11:31:53AM +, Philip Martin wrote:
> Ross Lagerwall  writes:
> 
> > The resulting .svn dir is about 19000 files and 522MiB. However, wc.db
> > is 203MiB. This seems huge compared with the size of the checkout. Is
> > this normal? Is there any way to get this file to be smaller?
> 
> Subversion doesn't enable auto_vacuum so run:
> 
>   sqlite3 .svn/wc.db "vacuum" 
> 
> http://sqlite.org/lang_vacuum.html
> 

Thanks!

That reduced the size from 203MiB to 13MiB.

Ross

Setting bugtraq properties to all projects in a repository

2012-12-03 Thread Manuel Ferrero 

I was using cvs as version control and now I'm migrating to Subversion.
On cvs I often wrote commit logs referring to the Bugzilla bug number, 
something like that:

bla bla bla Bug #XXX

TortoiseCVS was configured to convert bug #XXX into a ink to my local 
Bugzilla installation.


I now use TortoiseSVN as a client to interact with my Subversion 
installation and I learned how to setup the integration between 
TortoiseSVN and Bugzilla by adding some properties to the project folder 
as stated in the webpage 
http://tortoisesvn.net/docs/nightly/TortoiseSVN_en/tsvn-dug-bugtracker.html


Now I'd like to know if I can automatically set those properties on each 
new project I'll add to the repository in the future.
Is there some configuration that I can do on the server side to set 
those properties?


TIA
--
Regards,
Manuel Ferrero
R&D department

Reer SpA
Tel.  +39 011 2482215
Fax. +39 011 859867

L'utilizzo non autorizzato del presente messaggio e' vietato e potrebbe 
costituire reato.
Se il presente messaggio non e' a Lei indirizzato, il suo contenuto non deve 
essere considerato
come trasmesso o autorizzato dalla Reer SpA; in tale caso Le saremmo grati se, 
via e-mail,
ce ne comunicasse l'errata ricezione.

The unauthorized use of this e-mail is prohibited and could constitute an 
offence.
If you are not the intended recipient of this message its contents shall be 
understood as neither
given nor endorsed by Reer SpA. Please notify Reer SpA by e-mail immediately in 
that case.

Re: Setting bugtraq properties to all projects in a repository

2012-12-03 Thread Andy Levy 
On Mon, Dec 3, 2012 at 11:20 AM, Manuel Ferrero  wrote:

> I was using cvs as version control and now I'm migrating to Subversion.
> On cvs I often wrote commit logs referring to the Bugzilla bug number,
> something like that:
> bla bla bla Bug #XXX
>
> TortoiseCVS was configured to convert bug #XXX into a ink to my local
> Bugzilla installation.
>
> I now use TortoiseSVN as a client to interact with my Subversion
> installation and I learned how to setup the integration between TortoiseSVN
> and Bugzilla by adding some properties to the project folder as stated in
> the webpage http://tortoisesvn.net/docs/**nightly/TortoiseSVN_en/tsvn-**
> dug-bugtracker.html
>
> Now I'd like to know if I can automatically set those properties on each
> new project I'll add to the repository in the future.
> Is there some configuration that I can do on the server side to set those
> properties?
>
>
You can configure automatic property setting on each client (auto-props in
your config file, and tsvn:autoprops on your folders but only used by
Tortoise, see
http://tortoisesvn.net/docs/nightly/TortoiseSVN_en/tsvn-dug-propertypage.html),
and you can configure a pre-commit hook script to reject any commit where
new items lack the property or existing items have the property removed,
but you can't control client configuration via the server.