svn deployment help

[Tom Cruickshank]

Hey Guys,
I'm doing research on svn and wondering if anyone might have an ideas
for this. I'm setting up SVN so that I have a SVN repository on my
development machine which will then be able to deploy files to my production
environment.

I'd like to be able to pick and choose which files I want to deploy (not
automatically deploy all the files which have been recently committed, using
hooks). I'd also like to (preferably) have a GUI based tool (web based also
works) to choose the files
and then have them deployed to the production environment.

Does this type of deployment tool exist?

Would appreciate assistance. Thanks!

Tom

RE: svn deployment help

[Giulio Troccoli]

I don't think such a tool exist but we use svn:externals to do something 
similar.

Basically we have a folder called Public that contains the documentation 
available to customers. We then set svn:externals on that folder pointing to 
the docs we want to make public. The web server just checkouts and update this 
folder and not the whole repository.

Giulio




Linedata Limited
Registered Office: 85 Gracechurch St., London, EC3V 0AA
Registered in England and Wales No 3475006 VAT Reg No 710 3140 03




From: Tom Cruickshank [mailto:tcruic...@gmail.com]
Sent: 20 July 2010 11:47
To: users@subversion.apache.org
Subject: svn deployment help

Hey Guys,
I'm doing research on svn and wondering if anyone might have an ideas for 
this. I'm setting up SVN so that I have a SVN repository on my development 
machine which will then be able to deploy files to my production environment.

I'd like to be able to pick and choose which files I want to deploy (not 
automatically deploy all the files which have been recently committed, using 
hooks). I'd also like to (preferably) have a GUI based tool (web based also 
works) to choose the files
and then have them deployed to the production environment.

Does this type of deployment tool exist?

Would appreciate assistance. Thanks!

Tom

libsvn_ra_neon-1.so.0: undefined symbol: GENERAL_NAME_free

[Angel Tsankov]

When I run kdesvn I get a dialog showing the following message:

Could not find our part: Cannot load library 
/usr/lib/kde4/kdesvnpart.so: (/usr/lib/libsvn_ra_neon-1.so.0: undefined 
symbol: GENERAL_NAME_free)


Files /usr/lib/kde4/kdesvnpart.so and /usr/lib/libsvn_ra_neon-1.so.0 
both exist. The former is part of kdesvn and the latter is part of 
subversion.  In case this is relevant, I have installed the following 
packages:


* openssl 0.9.8j (configured with --prefix=/usr --openssldir=/usr/share);
* neon 0.28.4 (configured with --prefix=/usr --with-ssl);
* subversion 1.6.12 (configured with --prefix=/usr).

Do I need to upgrade openssl or neon? Or is the problem elsewhere?

svn update -r $revision could hang if $revsion is greater than HEAD

[jason_zhuyx]

For instance, when the latest revision of the repository is 100, running the 
following command will hang:
 
    svn update -r 101
 
where the revision given is any positive number greater than HEAD.
 
This happened on both Windows (XP SP2, svn version 1.5.5 (r34862)) and Lunix 
(CentOS 5.3, svn version 1.6.2 r37639) systems.
 
Can someone confirm if this is a bug?
 
Thanks,
- Jason


  

--set-depth missing for svn merge command?

[Gunther Clasen]

Hi,

 

I tried to merge a branch into the trunk, but I did not (yet) want to
merge two directories which were under the top level. The top level had
files and a directory added in the branch. Having read up on the "new"
-depth option, which I hadn't used before, I tried to do the following:

 

# check out trunk, cd into it

# svn merge --depth immediates ^/branches/some_branch .

# svn merge --depth infinity ^/branches/some_branch/som_dir some_dir

 

I did the latter for each of the half dozen or so dirs. The first
command added the files in the top level, the latter command merged the
subdirs, except that it did not add any files from the branch into these
immediate subdirs. (Files were added further down the dirs.)

 

Trying to reproduce the problem with the examples from the book I
realized that I think I should have used --set-depth instead of --depth,
but this option does not exist in svn merge. Wouldn't that be something
for the wish-list? Or have I done something wrong?

 

What's the best solution for this sort of merge? I have created a sparse
checkout, with the directories which I didn't want to merge missing, so
checking out with --depth immediate, then populating some dirs using the
--set-depth infinity. Merging the top level then merges the immediates,
merging the sub dirs again updates the existing files but does not add
the one which were added on the branch.

 

The only solution I have found is to actually svn copy the files which
have been added in the top level dir on the branch. That sounds so
un-cool.

 

Is there any other way???

 

Gunther

 

 

Gunther Clasen - Verification Specialist



EnSilica Limited
The Barn, Waterloo Road
Wokingham
Berkshire
RG40 3BY

Tel:   +44 (0)1183 217 316 
Fax:  +44 (0)1189 798 160
Web: http://www.ensilica.com   
Email:   gunther.cla...@ensilica.com
  

 

EnSilica Ltd is a company registered in England and Wales with company
number 04220106 and VAT registration number 776136704. Confidentiality
Notice: The information contained in this e-mail, and any attachments,
is intended for the named recipients only. It may contain confidential
and/or legally privileged information. If you are not the intended
recipient, you must not copy, store, distribute or take any action in
reliance on it. Any views expressed do not necessarily reflect the views
of the company. If you receive this e-mail by mistake, please advise the
sender by using the reply facility in your e-mail software and then
delete it.

 

Re: svn update -r $revision could hang if $revsion is greater than HEAD

[Andy Levy]

On Mon, Jul 19, 2010 at 18:43, jason_zhuyx  wrote:
>
> For instance, when the latest revision of the repository is 100, running the 
> following command will hang:
>
>     svn update -r 101
>
> where the revision given is any positive number greater than HEAD.
>
> This happened on both Windows (XP SP2, svn version 1.5.5 (r34862)) and Lunix 
> (CentOS 5.3, svn version 1.6.2 r37639) systems.
>
> Can someone confirm if this is a bug?

XP SP3 here, 1.6.6 (r40053), I cannot reproduce the issue.

C:\_Projects\workspace\proj>svn up
At revision 5604.

C:\_Projects\workspace\proj>svn up -r 6000
svn: No such revision 6000

C:\_Projects\workspace\proj>svn --version
svn, version 1.6.6 (r40053)
   compiled Oct 19 2009, 09:36:48

No hangs.

SVN crash on merge

[Bob Sandiford]

Hi,

I was doing some 'svn merge' commands, and got this:

This application has halted due to an unexpected error.
A crash report and minidump file were saved to disk, you can find them here:
c:\tmp\svn-crash-log20100720095803.log
c:\tmp\svn-crash-log20100720095803.dmp
Please send the log file to users@subversion.apache.org to help us analyse
and solve this problem.

NOTE: The crash report and minidump files can contain some sensitive information
(filenames, partial file content, usernames and passwords etc.)

Basically, what I was doing was, after a  SVN server upgrade from svn 1.4.x to 
1.6.12, and using a corresponding 1.6.12 svn client, I was replacing old 
'svnmerge' based tracking info with new 'svn merge' tracking info.

Here's the whole output from my session:

C:\development\pristine ICE-4.0-merge branches\marc>svn pl . -v
Properties on '.':
  svn:ignore
build
dist

  reviewboard:url
http://ironman/reviews
  svnmerge-integrated
/marc/trunk:1-14938

C:\development\pristine ICE-4.0-merge branches\marc>svn pd svnmerge-integrated
property 'svnmerge-integrated' deleted from '.'.

C:\development\pristine ICE-4.0-merge branches\marc>svn info
Path: .
URL: svn://vcrep/UXP/marc/branches/ICE-4.0-merge
Repository Root: svn://vcrep/UXP
Repository UUID: 86b1f47f-8b1c-4ae9-be57-0dbcaf493a63
Revision: 15620
Node Kind: directory
Schedule: normal
Last Changed Author: bobs
Last Changed Rev: 15108
Last Changed Date: 2010-05-07 13:06:36 -0400 (Fri, 07 May 2010)


C:\development\pristine ICE-4.0-merge branches\marc>svn merge -r 1:14938 
svn://vcrep/UXP/marc/trunk --record-only

C:\development\pristine ICE-4.0-merge branches\marc>svn st
 M  .

C:\development\pristine ICE-4.0-merge branches\marc>svn pl . -v
Properties on '.':
  svn:ignore
build
dist

  reviewboard:url
http://ironman/reviews
  svn:mergeinfo
/marc/trunk:394-14938

C:\development\pristine ICE-4.0-merge branches\marc>svn mergeinfo 
svn://vcrep/UXP/marc/trunk --show-revs eligible
r15787
r15850
r15871

C:\development\pristine ICE-4.0-merge branches\marc>svn merge 
svn://vcrep/UXP/marc/trunk
Conflict for property 'svnmerge-integrated' discovered on ''.
Select: (p) postpone,
(mf) mine-full, (tf) theirs-full,
(s) show all options: p
This application has halted due to an unexpected error.
A crash report and minidump file were saved to disk, you can find them here:
c:\tmp\svn-crash-log20100720095803.log
c:\tmp\svn-crash-log20100720095803.dmp
Please send the log file to users@subversion.apache.org to help us analyse
and solve this problem.

NOTE: The crash report and minidump files can contain some sensitive information
(filenames, partial file content, usernames and passwords etc.)

C:\development\pristine ICE-4.0-merge branches\marc>svn st
 M  .

i.e. svnmerge tracking info had previously been in place showing merged from 
trunk revs 1-14938.  I deleted the 'svnmerge-integrated' property, and then ran 
a record-only merge against the trunk from revisions 1-14938 to 'replicate' the 
old merge tracking info.

Then I checked on any pending merge revisions, found there were three, and 
tried to actually do the merge from the trunk back into my feature branch, and 
boom.

log and dmp files are attached...

Here's the "svn -version" output:

C:\development\pristine ICE-4.0-merge branches\marc>svn --version
svn, version 1.6.12 (r955767)
   compiled Jun 21 2010, 16:00:59

Copyright (C) 2000-2009 CollabNet.
Subversion is open source software, see http://subversion.tigris.org/
This product includes software developed by CollabNet (http://www.Collab.Net/).

The following repository access (RA) modules are available:

* ra_neon : Module for accessing a repository via WebDAV protocol using Neon.
  - handles 'http' scheme
  - handles 'https' scheme
* ra_svn : Module for accessing a repository using the svn network protocol.
  - with Cyrus SASL authentication
  - handles 'svn' scheme
* ra_local : Module for accessing a repository on local disk.
  - handles 'file' scheme
* ra_serf : Module for accessing a repository via WebDAV protocol using serf.
  - handles 'http' scheme
  - handles 'https' scheme


Bob Sandiford | Lead Software Engineer | SirsiDynix
P: 519.883.6943 | bob.sandif...@sirsidynix.com
www.sirsidynix.com



svn-crash-log20100720095803.log
Description: svn-crash-log20100720095803.log


svn-crash-log20100720095803.dmp
Description: svn-crash-log20100720095803.dmp

Re: fixing files committed with wrong eol-style

[Les Mikesell]

On 7/20/2010 12:49 AM, Nico Kadel-Garcia wrote:

On Tue, Jul 20, 2010 at 12:26 AM, Les Mikesell  wrote:

On 7/19/2010 10:10 PM, Kitching, Simon wrote:


Ah well, as it appears that nobody here knows the answer I'll just have
to do it the ugly way: try to get the svn repo administrator to install
some hooks to prevent this occurring in future, and then install cygwin
on somebody's windows PC to script the adding of eol-style=native to
relevant existing files.


Maybe you could write your script to check for the need for the change to
run on linux but instead of setting the property there, output a batch file
of the commands to be executed, transfer the file to windows box (perhaps by
committing, and checking back out there with the correct eol's), and then
run the commands from the windows side.


Look, *BREAK* the history. History is overvalued: Make a clean tag
with your final pre-switchover release, with a note explaining what
happened, and make an entirely new repository or branch with entirely
imported code. It will be much cleaner to track and follow what
happened without trying to back-revise history of mixed EOL
configurations.


I have to disagree very much with this.  The ability to easily see what 
changed between any two points is most of the value of using version 
control systems.   Sometimes you won't know why the old way was better 
until long after you've forgotten the details of the changes - or the 
person who made them may no longer be around.


--
  Les Mikesell
   lesmikes...@gmail.com

Re: fixing files committed with wrong eol-style

[Neil Bird]

Around about 20/07/10 04:10, Kitching, Simon typed ...

Ah well, as it appears that nobody here knows the answer I'll just have
to do it the ugly way: try to get the svn repo administrator to install
some hooks to prevent this occurring in future, and then install cygwin
on somebody's windows PC to script the adding of eol-style=native to
relevant existing files.


  I'm thinking aloud here, you may not be able to do it, but if you can add 
props. as a direct repo. mod., them maybe it'd be easier for you to:


- create a temp working branch off trunk
- use a 'find' loop to find the files, but instead of 'svn ps svn:eol-style 
{}' use 'http:/part/to/repo/'{} [if that will work with find!] with a '-m' 
comment.

- merge the whole bally lot back to trunk and delete the branch


  Yes, you'll add a gazillion revs. via the branch, but the mod. will 
appear as atomic on trunk.


--
[n...@fnx ~]# rm -f .signature
[n...@fnx ~]# ls -l .signature
ls: .signature: No such file or directory
[n...@fnx ~]# exit

Build on Solaris 10 with BerkeleyDB.4.7

[Minson, John M CIV SPAWARSYSCEN-ATLANTIC, 82370]

I am trying to build on a Solaris 10 box with BerkeleyDB.4.7  installed in 

/usr/local/BerkeleyDB.4.7

I have tried many combinations of the --with-berkeley-db  option but cannot 
satisfy the configure script . I have made links in /usr/local to no avail . 
Given the db install location what exactly would be the correct syntax of this 
option ?



smime.p7s
Description: S/MIME cryptographic signature

Subversion 1.6.12 and SSPI Authentification Mode under Apache 2.2.15

[Sébastien Filion]

Hi,

Does anybody can tell me if it still possible to connect to our repositories 
using SSPI authentification mode with Subversion 1.6.12 under Apache 2.2.15.
I try both 1.0.3 and 1.0.4 version of mod_auth_sspi but nothing works for the 
moment.

We had a similar working setup under subversion 1.5.6 and Apache 2.0.x but I 
NEED to upgrade but I'm not sure it will be possible to use the SSPI mode.

There is all the steps I did:
1-  Installing CollabNet Subversion Server and Client v1.6.12 (for Windows)
2-  I download mod_auth_sspi-1.0.3 from 
http://sourceforge.net/projects/mod-auth-sspi/ (Note that I also try the 
version 1.0.4)
3-  I copy the mod_auth_sspi.so in the modules folder of apache.
4-  After, I follow all the instruction under "Authentification avec un 
domaine" from this web site: 
http://tortoisesvn.net/docs/release/TortoiseSVN_fr/tsvn-serversetup-apache.html 
including (httpconf modifications, ssl certificate procedures, loading 
appropriate modules, etc...)
5-  I had all the possible rights (R\W and even modify) on the server where 
Apache is installed.
There is no error in the Event viewer even in the apache logs directory. So the 
setup "should" be fine but it seems that there a problem anyway.
After all the setup, I got this error message when connection via web browser 
or tortoiseSVN: Server sent unexpected return value (403 forbidden) in response 
to OPTIONS request "toto/svn/my-first-repo"

question on Subverison confguration

[Chidambarathanupillai_Nagaraj]

Hi,
 
I am new to any version control system.
I need to create an environment to test the below.
How do we create multiple repositries on the Sub version system?
How to tag the branch looping 20 times?
Can anyone help me on this.
 
Create a large NFS file system for the source control repository and connect it 
to the Subversion system referred to as Rep1.

Create a large NFS file system for a second source control repository and 
connect it to the Subversion system referred to as Rep2.

Loop the following 20 times to create a deep Subversion repository for Rep1 and 
Rep2:

Checkout an old version of the Linux source code (Kernel series 2.6.27.44) and 
check it into the Subversion system.

Tag the branch (27.N, where N is 1-20)

Checkout one of the newer version of the Linux source code (Kernel series 
2.6.34) and check it into the Subversion system.

Tag the branch (34.N, where N is 1-20)

Test 1 - Checkout times

>From a server connected to the Subversion server, time how long it takes to do 
>10 sequential mainline checkouts from Rep1.  Note the completion times for 
>each checkout. Repeat using Rep2.

Test 2 - Build times

>From 5 different systems talking to the Subversion server, setup private 
>kernel build areas using Rep1 and another build area using Rep2. 

>From each build server, do a checkout of the kernel source based on 27.N from 
>Rep1 and build it.  Checkout 34.N and build. Repeat this process 5 times.  
>Record total times for the checkouts and builds.

Repeat the above process for Rep2 using the build areas based on private build 
areas.
 
Thanks and Regards,
Nagaraj Chidambarathanupillai

RE: question on Subverison confguration

[Bob Archer]

> I am new to any version control system.
> I need to create an environment to test the below.
> How do we create multiple repositries on the Sub version system?
> How to tag the branch looping 20 times?
> Can anyone help me on this.

I assume you are trying to script this in some way?

use svnadmin create to crate your two repos.

use svn to create your tags

It seems pretty straight forward. Or, do I not understand what you are asking?

BOb


> 
> Create a large NFS file system for the source control repository
> and connect it to the Subversion system referred to as Rep1.
> 
> Create a large NFS file system for a second source control
> repository and connect it to the Subversion system referred to as
> Rep2.
> 
> Loop the following 20 times to create a deep Subversion repository
> for Rep1 and Rep2:
> 
> Checkout an old version of the Linux source code (Kernel series
> 2.6.27.44) and check it into the Subversion system.
> 
> Tag the branch (27.N, where N is 1-20)
> 
> Checkout one of the newer version of the Linux source code (Kernel
> series 2.6.34) and check it into the Subversion system.
> 
> Tag the branch (34.N, where N is 1-20)
> 
> Test 1 - Checkout times
> 
> From a server connected to the Subversion server, time how long it
> takes to do 10 sequential mainline checkouts from Rep1.  Note the
> completion times for each checkout. Repeat using Rep2.
> 
> Test 2 - Build times
> 
> From 5 different systems talking to the Subversion server, setup
> private kernel build areas using Rep1 and another build area using
> Rep2.
> 
> From each build server, do a checkout of the kernel source based on
> 27.N from Rep1 and build it.  Checkout 34.N and build. Repeat this
> process 5 times.  Record total times for the checkouts and builds.
> 
> Repeat the above process for Rep2 using the build areas based on
> private build areas.
> 
> Thanks and Regards,
> Nagaraj Chidambarathanupillai

OSX svn client 1.6.11/1.6.12: SSL negotiation failed: SSL error: parse tlsext

[Martijn Dashorst]

When I try to import a 4.7MB directory structure (not too many files)
to the Apache SVN repository using the collabnet SVN client 1.6.11
(and 1.6.12) I get the following error:

svn: MKCOL of 
'/repos/asf/!svn/wrk/c357a0ad-6c6c-4225-bcba-af72cc55b7ee/wicket/common/site/trunk/_site/2009/12/21':
SSL negotiation failed: SSL error: parse tlsext
(https://svn.apache.org)

Things worthy of note:
 - OSX snow leopard
 - both 1.6.11 and 1.6.12 clients from collab.net give the same error
 - I'm based in the EU (Netherlands), so I go through the EU proxy

I've split up the commit to be able to continue with my work, but did
want to report this.

Bypassing the proxy with help from the infra team did not show this
error, so there is something at work at the svn proxy level.

This is the output of svn --version:

svn, version 1.6.12 (r955767)
   compiled Jun 23 2010, 12:01:54

Copyright (C) 2000-2009 CollabNet.
Subversion is open source software, see http://subversion.tigris.org/
This product includes software developed by CollabNet (http://www.Collab.Net/).

The following repository access (RA) modules are available:

* ra_neon : Module for accessing a repository via WebDAV protocol using Neon.
  - handles 'http' scheme
  - handles 'https' scheme
* ra_svn : Module for accessing a repository using the svn network protocol.
  - with Cyrus SASL authentication
  - handles 'svn' scheme
* ra_local : Module for accessing a repository on local disk.
  - handles 'file' scheme
* ra_serf : Module for accessing a repository via WebDAV protocol using serf.
  - handles 'http' scheme
  - handles 'https' scheme

Best regards

Martijn Dashorst

Re: OSX svn client 1.6.11/1.6.12: SSL negotiation failed: SSL error: parse tlsext

[Mark Phippard]

Looks like the ASF should upgrade their server to httpd 2.2.15 and the
latest OpenSSL. This bug has been fixed.

You should report the problem to the ASF infrastructure team.



On Tue, Jul 20, 2010 at 5:03 PM, Martijn Dashorst
 wrote:
> When I try to import a 4.7MB directory structure (not too many files)
> to the Apache SVN repository using the collabnet SVN client 1.6.11
> (and 1.6.12) I get the following error:
>
> svn: MKCOL of 
> '/repos/asf/!svn/wrk/c357a0ad-6c6c-4225-bcba-af72cc55b7ee/wicket/common/site/trunk/_site/2009/12/21':
> SSL negotiation failed: SSL error: parse tlsext
> (https://svn.apache.org)
>
> Things worthy of note:
>  - OSX snow leopard
>  - both 1.6.11 and 1.6.12 clients from collab.net give the same error
>  - I'm based in the EU (Netherlands), so I go through the EU proxy
>
> I've split up the commit to be able to continue with my work, but did
> want to report this.
>
> Bypassing the proxy with help from the infra team did not show this
> error, so there is something at work at the svn proxy level.
>
> This is the output of svn --version:
>
> svn, version 1.6.12 (r955767)
>   compiled Jun 23 2010, 12:01:54
>
> Copyright (C) 2000-2009 CollabNet.
> Subversion is open source software, see http://subversion.tigris.org/
> This product includes software developed by CollabNet 
> (http://www.Collab.Net/).
>
> The following repository access (RA) modules are available:
>
> * ra_neon : Module for accessing a repository via WebDAV protocol using Neon.
>  - handles 'http' scheme
>  - handles 'https' scheme
> * ra_svn : Module for accessing a repository using the svn network protocol.
>  - with Cyrus SASL authentication
>  - handles 'svn' scheme
> * ra_local : Module for accessing a repository on local disk.
>  - handles 'file' scheme
> * ra_serf : Module for accessing a repository via WebDAV protocol using serf.
>  - handles 'http' scheme
>  - handles 'https' scheme
>
> Best regards
>
> Martijn Dashorst
>



-- 
Thanks

Mark Phippard
http://markphip.blogspot.com/

Re: libsvn_ra_neon-1.so.0: undefined symbol: GENERAL_NAME_free

[Stanimir Stamenkov]

20.7.2010 г. 14:32 +0300, /Angel Tsankov/:


When I run kdesvn I get a dialog showing the following message:

Could not find our part: Cannot load library 
/usr/lib/kde4/kdesvnpart.so: (/usr/lib/libsvn_ra_neon-1.so.0: 
undefined symbol: GENERAL_NAME_free)


Files /usr/lib/kde4/kdesvnpart.so and /usr/lib/libsvn_ra_neon-1.so.0 
both exist. The former is part of kdesvn and the latter is part of 
subversion. In case this is relevant, I have installed the following 
packages:


* openssl 0.9.8j (configured with --prefix=/usr --openssldir=/usr/share);
* neon 0.28.4 (configured with --prefix=/usr --with-ssl);
* subversion 1.6.12 (configured with --prefix=/usr).

Do I need to upgrade openssl or neon? Or is the problem elsewhere?


This is user mailing list for the general Subversion 
distribution/client. I guess your question is more appropriate for the 
kdesvn mailing list.


--
Stanimir

Re: OSX svn client 1.6.11/1.6.12: SSL negotiation failed: SSL error: parse tlsext

[Martijn Dashorst]

Ok thanks for replying. I've created an infra ticket with all the information...

Martijn

On Tue, Jul 20, 2010 at 11:13 PM, Mark Phippard  wrote:
> Looks like the ASF should upgrade their server to httpd 2.2.15 and the
> latest OpenSSL. This bug has been fixed.
>
> You should report the problem to the ASF infrastructure team.
>
>
>
> On Tue, Jul 20, 2010 at 5:03 PM, Martijn Dashorst
>  wrote:
>> When I try to import a 4.7MB directory structure (not too many files)
>> to the Apache SVN repository using the collabnet SVN client 1.6.11
>> (and 1.6.12) I get the following error:
>>
>> svn: MKCOL of 
>> '/repos/asf/!svn/wrk/c357a0ad-6c6c-4225-bcba-af72cc55b7ee/wicket/common/site/trunk/_site/2009/12/21':
>> SSL negotiation failed: SSL error: parse tlsext
>> (https://svn.apache.org)
>>
>> Things worthy of note:
>>  - OSX snow leopard
>>  - both 1.6.11 and 1.6.12 clients from collab.net give the same error
>>  - I'm based in the EU (Netherlands), so I go through the EU proxy
>>
>> I've split up the commit to be able to continue with my work, but did
>> want to report this.
>>
>> Bypassing the proxy with help from the infra team did not show this
>> error, so there is something at work at the svn proxy level.
>>
>> This is the output of svn --version:
>>
>> svn, version 1.6.12 (r955767)
>>   compiled Jun 23 2010, 12:01:54
>>
>> Copyright (C) 2000-2009 CollabNet.
>> Subversion is open source software, see http://subversion.tigris.org/
>> This product includes software developed by CollabNet 
>> (http://www.Collab.Net/).
>>
>> The following repository access (RA) modules are available:
>>
>> * ra_neon : Module for accessing a repository via WebDAV protocol using Neon.
>>  - handles 'http' scheme
>>  - handles 'https' scheme
>> * ra_svn : Module for accessing a repository using the svn network protocol.
>>  - with Cyrus SASL authentication
>>  - handles 'svn' scheme
>> * ra_local : Module for accessing a repository on local disk.
>>  - handles 'file' scheme
>> * ra_serf : Module for accessing a repository via WebDAV protocol using serf.
>>  - handles 'http' scheme
>>  - handles 'https' scheme
>>
>> Best regards
>>
>> Martijn Dashorst
>>
>
>
>
> --
> Thanks
>
> Mark Phippard
> http://markphip.blogspot.com/
>



-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.4 increases type safety for web applications
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.8

Re: Re: fixing files committed with wrong eol-style

[David Weintraub]

On Mon, Jul 19, 2010 at 11:10 PM, Kitching, Simon
 wrote:

> On Wed, 2010-07-14 at 10:35 -0400, David Weintraub wrote:
>> I have a pre-commit hook that will verify that particular files have
>> svn:eol-style set before allowing a commit. This way, you can make
>> sure that the property is set before anyone can do a commit.

> Yes, that might be the best way to prevent the problem reoccurring in
> the future. Unfortunately, it doesn't help with fixing a pre-existing
> repository (ie setting eol:style=native on existing files that really
> should have had it set when they were created but didn't).

Here's a solution you haven't considered: Force all text files to have
"svn:eol-style" set to "CRLF" instead of "native".

I've found that Windows tends to be the system that messes up line
endings. Many developers will open up Notepad or Wordpad which will
muck up line endings if the file doesn't already have Windows style
line endings. However, Linux/Unix users tend to use tools like
Eclipse, VIM, or Emacs which will not mess with the line endings of
files that it is editing. If a file has "CRLF", these editors wont'
change it.

These Unix/Linux tools can also be configured to default to Windows'
CRLF on new files too.

Then, you simply need a hook to enforce the use of Windows line
endings on all text files (except maybe Unix specific files like Shell
scripts and Makefiles which fail if they have CRLF line endings).

-- 
David Weintraub
qazw...@gmail.com

Re: fixing files committed with wrong eol-style

[Ryan Schmidt]

On Jul 20, 2010, at 09:35, Neil Bird wrote:

> I'm thinking aloud here, you may not be able to do it, but if you can add 
> props. as a direct repo. mod., them maybe it'd be easier for you to:
> 
> - create a temp working branch off trunk
> - use a 'find' loop to find the files, but instead of 'svn ps svn:eol-style 
> {}' use 'http:/part/to/repo/'{} [if that will work with find!] with a '-m' 
> comment.
> - merge the whole bally lot back to trunk and delete the branch
> 
> 
>  Yes, you'll add a gazillion revs. via the branch, but the mod. will appear 
> as atomic on trunk.

Or use svnmucc to do it in a single revision in the first place.

RE: question on Subverison confguration

[Chidambarathanupillai_Nagaraj]

Hi,
 
Could you please provide the syntax for tag the branch using svn?
 
Thanks and Regards,
Nagaraj Chidambarathanupillai.



From: Bob Archer [mailto:bob.arc...@amsi.com]
Sent: Tue 7/20/2010 2:24 PM
To: Chidambarathanupillai, Nagaraj; users@subversion.apache.org
Subject: RE: question on Subverison confguration



> I am new to any version control system.
> I need to create an environment to test the below.
> How do we create multiple repositries on the Sub version system?
> How to tag the branch looping 20 times?
> Can anyone help me on this.

I assume you are trying to script this in some way?

use svnadmin create to crate your two repos.

use svn to create your tags

It seems pretty straight forward. Or, do I not understand what you are asking?

BOb


>
> Create a large NFS file system for the source control repository
> and connect it to the Subversion system referred to as Rep1.
>
> Create a large NFS file system for a second source control
> repository and connect it to the Subversion system referred to as
> Rep2.
>
> Loop the following 20 times to create a deep Subversion repository
> for Rep1 and Rep2:
>
> Checkout an old version of the Linux source code (Kernel series
> 2.6.27.44) and check it into the Subversion system.
>
> Tag the branch (27.N, where N is 1-20)
>
> Checkout one of the newer version of the Linux source code (Kernel
> series 2.6.34) and check it into the Subversion system.
>
> Tag the branch (34.N, where N is 1-20)
>
> Test 1 - Checkout times
>
> From a server connected to the Subversion server, time how long it
> takes to do 10 sequential mainline checkouts from Rep1.  Note the
> completion times for each checkout. Repeat using Rep2.
>
> Test 2 - Build times
>
> From 5 different systems talking to the Subversion server, setup
> private kernel build areas using Rep1 and another build area using
> Rep2.
>
> From each build server, do a checkout of the kernel source based on
> 27.N from Rep1 and build it.  Checkout 34.N and build. Repeat this
> process 5 times.  Record total times for the checkouts and builds.
>
> Repeat the above process for Rep2 using the build areas based on
> private build areas.
>
> Thanks and Regards,
> Nagaraj Chidambarathanupillai

RE: question on Subverison confguration

[Chidambarathanupillai_Nagaraj]

Hi,
 
Also if there is any script available please share it even if it needs to be 
modified slightly.
 
Thanks and Regards,
Nagaraj Chidambarathanupillai.



From: Chidambarathanupillai, Nagaraj
Sent: Wed 7/21/2010 1:57 AM
To: Bob Archer; users@subversion.apache.org
Subject: RE: question on Subverison confguration


Hi,
 
Could you please provide the syntax for tag the branch using svn?
 
Thanks and Regards,
Nagaraj Chidambarathanupillai.



From: Bob Archer [mailto:bob.arc...@amsi.com]
Sent: Tue 7/20/2010 2:24 PM
To: Chidambarathanupillai, Nagaraj; users@subversion.apache.org
Subject: RE: question on Subverison confguration



> I am new to any version control system.
> I need to create an environment to test the below.
> How do we create multiple repositries on the Sub version system?
> How to tag the branch looping 20 times?
> Can anyone help me on this.

I assume you are trying to script this in some way?

use svnadmin create to crate your two repos.

use svn to create your tags

It seems pretty straight forward. Or, do I not understand what you are asking?

BOb


>
> Create a large NFS file system for the source control repository
> and connect it to the Subversion system referred to as Rep1.
>
> Create a large NFS file system for a second source control
> repository and connect it to the Subversion system referred to as
> Rep2.
>
> Loop the following 20 times to create a deep Subversion repository
> for Rep1 and Rep2:
>
> Checkout an old version of the Linux source code (Kernel series
> 2.6.27.44) and check it into the Subversion system.
>
> Tag the branch (27.N, where N is 1-20)
>
> Checkout one of the newer version of the Linux source code (Kernel
> series 2.6.34) and check it into the Subversion system.
>
> Tag the branch (34.N, where N is 1-20)
>
> Test 1 - Checkout times
>
> From a server connected to the Subversion server, time how long it
> takes to do 10 sequential mainline checkouts from Rep1.  Note the
> completion times for each checkout. Repeat using Rep2.
>
> Test 2 - Build times
>
> From 5 different systems talking to the Subversion server, setup
> private kernel build areas using Rep1 and another build area using
> Rep2.
>
> From each build server, do a checkout of the kernel source based on
> 27.N from Rep1 and build it.  Checkout 34.N and build. Repeat this
> process 5 times.  Record total times for the checkouts and builds.
>
> Repeat the above process for Rep2 using the build areas based on
> private build areas.
>
> Thanks and Regards,
> Nagaraj Chidambarathanupillai

RE: Subversion 1.6.12 and SSPI Authentification Mode under Apache 2.2.15

[Cooke, Mark]

> -Original Message-
> From: Sébastien Filion [mailto:sfil...@finlogik.com] 
> Sent: 20 July 2010 19:02
> To: users@subversion.apache.org
> Subject: Subversion 1.6.12 and SSPI Authentification Mode 
> under Apache 2.2.15
> 
> Hi, 
> 
> Does anybody can tell me if it still possible to connect to 
> our repositories using SSPI authentification mode with 
> Subversion 1.6.12 under Apache 2.2.15.
> 
> I try both 1.0.3 and 1.0.4 version of mod_auth_sspi but 
> nothing works for the moment.
> 
I am using SSPI OK on a server using apache 2.2 and svn 1.6.6 (I have not had 
time to upgrad to 1.6.12 yet but will do so as soon as I get a chance).  So it 
is likely it will work, I am only a few point releases out from what you want.

Can you post the relevant bits of your apache config (taking care of passwords 
etc)?  It might help work out what is wrong.

Have you tried disabling the SSPI authentication temporarily to make sure you 
can connect properly without it (make sure that svn authentication, if used, is 
working OK.

~ mark c

> We had a similar working setup under subversion 1.5.6 and 
> Apache 2.0.x but I NEED to upgrade but I'm not sure it will 
> be possible to use the SSPI mode.
> 
> There is all the steps I did:
> 
> 1-  Installing CollabNet Subversion Server and Client 
> v1.6.12 (for Windows)
> 
> 2-  I download mod_auth_sspi-1.0.3 from 
> http://sourceforge.net/projects/mod-auth-sspi/ (Note that I 
> also try the version 1.0.4)
> 
> 3-  I copy the mod_auth_sspi.so in the modules folder of apache.
> 
> 4-  After, I follow all the instruction under 
> "Authentification avec un domaine" from this web site: 
> http://tortoisesvn.net/docs/release/TortoiseSVN_fr/tsvn-serversetup-apache.html
>  including (httpconf modifications, ssl > certificate procedures, loading 
> appropriate modules, etc...)
> 
> 5-  I had all the possible rights (R\W and even modify) 
> on the server where Apache is installed.
> 
> There is no error in the Event viewer even in the apache logs 
> directory. So the setup "should" be fine but it seems that 
> there a problem anyway.
> 
> After all the setup, I got this error message when connection 
> via web browser or tortoiseSVN: Server sent unexpected return 
> value (403 forbidden) in response to OPTIONS request 
> "toto/svn/my-first-repo"
> 

Re: libsvn_ra_neon-1.so.0: undefined symbol: GENERAL_NAME_free

[Angel Tsankov]

Stanimir Stamenkov wrote:

20.7.2010 г. 14:32 +0300, /Angel Tsankov/:


When I run kdesvn I get a dialog showing the following message:

Could not find our part: Cannot load library 
/usr/lib/kde4/kdesvnpart.so: (/usr/lib/libsvn_ra_neon-1.so.0: 
undefined symbol: GENERAL_NAME_free)


Files /usr/lib/kde4/kdesvnpart.so and /usr/lib/libsvn_ra_neon-1.so.0 
both exist. The former is part of kdesvn and the latter is part of 
subversion. In case this is relevant, I have installed the following 
packages:


* openssl 0.9.8j (configured with --prefix=/usr --openssldir=/usr/share);
* neon 0.28.4 (configured with --prefix=/usr --with-ssl);
* subversion 1.6.12 (configured with --prefix=/usr).

Do I need to upgrade openssl or neon? Or is the problem elsewhere?


This is user mailing list for the general Subversion 
distribution/client. I guess your question is more appropriate for the 
kdesvn mailing list.




Since the problem is with libsvn_ra_neon-1.so.0 (which is part of 
Subversion), I think my question is appropriate for this mailing list, 
as well.


Angel Tsankov

Re: question on Subverison confguration

[Ryan Schmidt]

On Jul 21, 2010, at 00:57,  
 wrote:

> Could you please provide the syntax for tag the branch using svn?

svn copy  $URL_OF_EXISTING_BRANCH  $URL_OF_NEW_TAG

This kind of usage information about Subversion can be learned by reading the 
book:

http://svnbook.org/

Specifically the branching and merging chapter:

http://svnbook.red-bean.com/nightly/en/svn.branchmerge.tags.html#svn.branchmerge.tags.mksimple

RE: question on Subverison confguration

[Cooke, Mark]

> From: Chidambarathanupillai, Nagaraj
> Sent: Wed 7/21/2010 1:57 AM
> To: Bob Archer; users@subversion.apache.org
> Subject: RE: question on Subverison confguration
> 
> Hi,
>  
> Could you please provide the syntax for tag the branch using svn?
>  
Do you know about the on line manual?  This is a good place to start for
someone "new to any version control system", especially the
introduction:-

http://svnbook.red-bean.com/nightly/en/index.html

Once you have read up to Chapter 2 thoroughly, the section on creating a
tag is at:-

http://svnbook.red-bean.com/nightly/en/svn.branchmerge.tags.html

Good luck!

~ mark c


> Thanks and Regards,
> Nagaraj Chidambarathanupillai.
> 
> 
> 
> From: Bob Archer [mailto:bob.arc...@amsi.com]
> Sent: Tue 7/20/2010 2:24 PM
> To: Chidambarathanupillai, Nagaraj; users@subversion.apache.org
> Subject: RE: question on Subverison confguration
> 
> 
> 
> > I am new to any version control system.
> > I need to create an environment to test the below.
> > How do we create multiple repositries on the Sub version system?
> > How to tag the branch looping 20 times?
> > Can anyone help me on this.
> 
> I assume you are trying to script this in some way?
> 
> use svnadmin create to crate your two repos.
> 
> use svn to create your tags
> 
> It seems pretty straight forward. Or, do I not understand 
> what you are asking?
> 
> BOb
> 
> 
> >
> > Create a large NFS file system for the source control repository
> > and connect it to the Subversion system referred to as Rep1.
> >
> > Create a large NFS file system for a second source control
> > repository and connect it to the Subversion system referred to as
> > Rep2.
> >
> > Loop the following 20 times to create a deep Subversion repository
> > for Rep1 and Rep2:
> >
> > Checkout an old version of the Linux source code (Kernel series
> > 2.6.27.44) and check it into the Subversion system.
> >
> > Tag the branch (27.N, where N is 1-20)
> >
> > Checkout one of the newer version of the Linux source code (Kernel
> > series 2.6.34) and check it into the Subversion system.
> >
> > Tag the branch (34.N, where N is 1-20)
> >
> > Test 1 - Checkout times
> >
> > From a server connected to the Subversion server, time how long it
> > takes to do 10 sequential mainline checkouts from Rep1.  Note the
> > completion times for each checkout. Repeat using Rep2.
> >
> > Test 2 - Build times
> >
> > From 5 different systems talking to the Subversion server, setup
> > private kernel build areas using Rep1 and another build area using
> > Rep2.
> >
> > From each build server, do a checkout of the kernel source based on
> > 27.N from Rep1 and build it.  Checkout 34.N and build. Repeat this
> > process 5 times.  Record total times for the checkouts and builds.
> >
> > Repeat the above process for Rep2 using the build areas based on
> > private build areas.
> >
> > Thanks and Regards,
> > Nagaraj Chidambarathanupillai
> 
> 
> 
> 

Re: libsvn_ra_neon-1.so.0: undefined symbol: GENERAL_NAME_free

[Stefan Sperling]

On Wed, Jul 21, 2010 at 09:19:26AM +0300, Angel Tsankov wrote:
> Stanimir Stamenkov wrote:
> >20.7.2010 г. 14:32 +0300, /Angel Tsankov/:
> >
> >>When I run kdesvn I get a dialog showing the following message:
> >>
> >>Could not find our part: Cannot load library
> >>/usr/lib/kde4/kdesvnpart.so: (/usr/lib/libsvn_ra_neon-1.so.0:
> >>undefined symbol: GENERAL_NAME_free)
> >>
> >>Files /usr/lib/kde4/kdesvnpart.so and
> >>/usr/lib/libsvn_ra_neon-1.so.0 both exist. The former is part of
> >>kdesvn and the latter is part of subversion. In case this is
> >>relevant, I have installed the following packages:
> >>
> >>* openssl 0.9.8j (configured with --prefix=/usr --openssldir=/usr/share);
> >>* neon 0.28.4 (configured with --prefix=/usr --with-ssl);
> >>* subversion 1.6.12 (configured with --prefix=/usr).
> >>
> >>Do I need to upgrade openssl or neon? Or is the problem elsewhere?
> >
> >This is user mailing list for the general Subversion
> >distribution/client. I guess your question is more appropriate for
> >the kdesvn mailing list.
> >
> 
> Since the problem is with libsvn_ra_neon-1.so.0 (which is part of
> Subversion), I think my question is appropriate for this mailing
> list, as well.

The problem is most probably not with Subversion.
We get reports similar to yours quite a lot, and they usually are local
installation problems.

You most likely have a local problem with your installation of Subversion
and related software. Quite possibly your kdesvn libraries were linked
against a different set of libraries than they are combined with at runtime.

You don't mention if you're compiling kdesvn yourself, too.
If not done carefully, installing and running a mixture of vendor-provided
distribution packages and self-compiled binaries can cause subtle problems,
such as apparently random crashes, or unresolved symbol errors like you are
seeing. These can of course be fixed and worked around, but I'd like to
encourage you to use pre-compiled packages from your distribution vendor
instead.

Why are you compiling your own binaries? If you use binary packages
you won't have any such problems.

If your reason for compiling your own binaries is that you are using a
source-based Linux distribution, please seek help at the appropriate forum
of that distribution.

Thanks,
Stefan