svnserve Segmentation fault on Slackware 13.1 64bit

[Hirofumi Saitoh]

I tried to build subversion 1.6.13 and 1.6.12 on Slackware 13.1 64bit with 
apr-1.4.2 apr-util-1.3.9
and run svnserve.

I have Segmentation fault problem, but did not happen same problem on Slackware 
13.1 32bit.

Thank you
-- Hirofumi Saitoh

# gcc -v
Reading specs from /usr/lib64/gcc/x86_64-slackware-linux/4.4.4/specs

# cd arp-1.4.2
# ./configure --prefix=/usr \
--libdir=/usr/lib64 \
--enable-shared
# make
# make check
# make install

# cd arp-util-1.3.9
# ./configure --prefix=/usr \
--libdir=/usr/lib64 \
--with-apr=/usr \
--with-pgsql=/usr/local/pgsql \
--with-mysql=/usr/local/mysql \
--with-berkeley-db \
--with-sqlite3

# make
# make check
# make install

# cd httpd-2.2.16
# ./configure \
--enable-ssl \
--enable-vhost-alias \
--enable-so \
--with-mpm=worker \
--with-include-apr=/usr \
--with-apr=/usr \
--with-apr-utl=/usr \
--enable-mods-shared=all \
--with-ssl=/usr/local/ssl
# make
# make install

# cd subversion-1.6.13
#./autogen.sh
#./configure \
--enable-shared \
--with-berkeley-db \
--with-zlib=/usr/lib64 \
--with-gnu-ld \
--with-ssl \
--with-apxs=/usr/local/apache2/bin/apxs \
--with-apr=/usr \
--with-apr-util=/usr
# make
# make check
# make install

# /usr/local/bin/svnserve -v
Segmentation fault (core dumped)

# which svnserve
/usr/local/bin/svnserve

# ldd /usr/local/bin/svnserve
/usr/local/bin/svnserve:
linux-vdso.so.1 =>  (0x7fff2edff000)
libsvn_repos-1.so.0 => /usr/lib64/libsvn_repos-1.so.0 
(0x7f8782ca2000)
libsvn_fs-1.so.0 => /usr/lib64/libsvn_fs-1.so.0 (0x7f8782a9b000)
libsvn_fs_fs-1.so.0 => /usr/lib64/libsvn_fs_fs-1.so.0 
(0x7f8782874000)
libsvn_fs_base-1.so.0 => /usr/lib64/libsvn_fs_base-1.so.0 
(0x7f8782645000)
libsvn_fs_util-1.so.0 => /usr/lib64/libsvn_fs_util-1.so.0 
(0x7f8782443000)
libsvn_delta-1.so.0 => /usr/lib64/libsvn_delta-1.so.0 
(0x7f8782238000)
libsvn_subr-1.so.0 => /usr/lib64/libsvn_subr-1.so.0 (0x7f8781fe9000)
libsvn_ra_svn-1.so.0 => /usr/lib64/libsvn_ra_svn-1.so.0 
(0x7f8781dd2000)
libz.so.1 => /usr/lib64/libz.so.1 (0x7f8781bba000)
libsqlite3.so.0 => /usr/lib64/libsqlite3.so.0 (0x7f8781926000)
libaprutil-1.so.0 => /usr/lib64/libaprutil-1.so.0 (0x7f8781705000)
libdb-4.7.so => /usr/lib64/libdb-4.7.so (0x7f87813a8000)
libexpat.so.1 => /usr/lib64/libexpat.so.1 (0x7f8781185000)
libapr-1.so.0 => /usr/lib64/libapr-1.so.0 (0x7f8780f57000)
libuuid.so.1 => /lib64/libuuid.so.1 (0x7f8780d54000)
librt.so.1 => /lib64/librt.so.1 (0x7f8780b4c000)
libcrypt.so.1 => /lib64/libcrypt.so.1 (0x7f8780913000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x7f87806f6000)
libsasl2.so.2 => /usr/lib64/libsasl2.so.2 (0x7f87804dd000)
libdl.so.2 => /lib64/libdl.so.2 (0x7f87802d9000)
libresolv.so.2 => /lib64/libresolv.so.2 (0x7f87800c)
libc.so.6 => /lib64/libc.so.6 (0x7f877fd4b000)
libdb-4.4.so => /usr/lib64/libdb-4.4.so (0x7f877fa44000)
libldap-2.4.so.2 => /usr/lib64/libldap-2.4.so.2 (0x7f877f801000)
liblber-2.4.so.2 => /usr/lib64/liblber-2.4.so.2 (0x7f877f5f4000)
/lib64/ld-linux-x86-64.so.2 (0x7f8782ecc000)
libssl.so.0 => /usr/lib64/libssl.so.0 (0x7f877f3a3000)
libcrypto.so.0 => /usr/lib64/libcrypto.so.0 (0x7f877f01e000)

# gdb -core=core --args svnserve -v
Core was generated by `svnserve -v'.
Program terminated with signal 11, Segmentation fault.
#0  apr_pool_create_ex (newpool=0x7fffecf315d8, parent=0x1, 
abort_fn=0x7f8ebf6e8310, allocator=0x0)
at memory/unix/apr_pools.c:854
854 allocator = parent->allocator;

Re: Importing Existing Repository into a New Repository

[Nico Kadel-Garcia]

2010/10/5 Ryan Schmidt :
>
> On Oct 5, 2010, at 15:22, Tech Geek wrote:
>
>> and load project a as project b and take all the history with you.
>> Just create a new project b without adding trunk etc. in revision 1.
>> I do not want all the revision history of projectA into projectB. I just 
>> need to start projectB with the latest code (trunk HEAD of) projectA.
>>
>> May be I am missing something very obvious here...
>
> If you do not want to preserve the history, then you want to "svn export" 
> from the old repository and "svn import" it into the new repository.

You'll also want to seriously review the Subversion properties of the
material before the export, in order to replicate them in the imported
or "added" material. svn:externals, svn:keywords, svn:eol, etc., etc.,
etc. are not contained in an export: they're meta data in the
Subversion repository, not the raw or even processed content of the
exported files. This includes svn:eol, svn:keywords, and in particular
svn:external. svn:keywords in particular, will create fascinating and
confusing content in the keywords of the files at the time of your
original import, so this is something to do cautiously.

This is one of those cases where a bit of extra attention, instead of
"just export it and import it" can save you some surprises down the
road.

Re: Importing Existing Repository into a New Repository

[Ryan Schmidt]

On Oct 6, 2010, at 07:03, Nico Kadel-Garcia wrote:

> 2010/10/5 Ryan Schmidt:
>> 
>> If you do not want to preserve the history, then you want to "svn export" 
>> from the old repository and "svn import" it into the new repository.
> 
> You'll also want to seriously review the Subversion properties of the
> material before the export, in order to replicate them in the imported
> or "added" material. svn:externals, svn:keywords, svn:eol, etc., etc.,
> etc. are not contained in an export: they're meta data in the
> Subversion repository, not the raw or even processed content of the
> exported files. This includes svn:eol, svn:keywords, and in particular
> svn:external. svn:keywords in particular, will create fascinating and
> confusing content in the keywords of the files at the time of your
> original import, so this is something to do cautiously.
> 
> This is one of those cases where a bit of extra attention, instead of
> "just export it and import it" can save you some surprises down the
> road.

Ah yes, this is true. If properties are of interest, then an alternative to svn 
exporting, manually fixing the properties, and svn importing, is to svnadmin 
dump just the HEAD revision and then svnadmin load it:

svnadmin dump -rHEAD /path/to/oldrepo > dump
svnadmin load /path/to/newrepo < dump

This will dump only a single revision representing the state of the old repo at 
HEAD, and will preserve properties. In between dump and load you can use 
svndumpfilter if you wish to exclude parts of the dump (or include only certain 
parts), and you can use svnadmin load's --parent-dir argument if you want to 
change where the contents are loaded (or just use "svn mv" after loading).

Howto Disable Localistation?

[Lechner Martin]

Hi, 

I have a question: Is it possible to disable the localization?

As a developer I prefer the english texts but unfortunately svn
translate everything to the language of my OS.

Help would be welcome!

 

Br

Martin

 

Re: Howto Disable Localistation?

[Siva Kumar]

> I have a question: Is it possible to disable the localization?
>
> As a developer I prefer the english texts but unfortunately svn translate
> everything to the language of my OS.

did you try setting up the LANG variable to en_US ?

BTW, which OS are you using ?

RE: Howto Disable Localistation?

[Tony Sweeney]

alias svn='LANG=en_US svn'




From: Lechner Martin [mailto:martin.lech...@alicona.com] 
Sent: 06 October 2010 14:54
To: users@subversion.apache.org
Subject: Howto Disable Localistation?



Hi, 

I have a question: Is it possible to disable the localization?

As a developer I prefer the english texts but unfortunately svn
translate everything to the language of my OS.

Help would be welcome!

 

Br

Martin

 



__
This email has been scanned by the MessageLabs Email Security
System.
For more information please visit
http://www.messagelabs.com/email 

__

svn Farm

[jehan procaccia]

 hello,

I need to provide svn service to many small groups of students.
I'am looking for a tool that would help industrialize managment of 
repositories.
I don't want to issue hundreds of "svn create", "vi authz" , edit ssh 
keys for svn+ssh access etc ...

Are there such  tools already existing  ?

FYI,
- all my users are in a common ldap directory,
- users will use both https and svn+ssh to acces repos
- eventually, it would be great for http if we could benefit from our 
http SSO (jasig CAS).


regards .

Re: svn Farm

[Siva Kumar]

> I need to provide svn service to many small groups of students.
> I'am looking for a tool that would help industrialize managment of
> repositories.
> I don't want to issue hundreds of "svn create", "vi authz" , edit ssh keys
> for svn+ssh access etc ...
> Are there such  tools already existing  ?

Subversion Edge(http://www.open.collab.net/go/csvne2_r2a/) might fit your bill.

How to file a feature request

[James Fainer]

I would like to file a feature request but don't want to clutter the issue
tracker inadvertently. What is the proper process? 

 

Jim Fainer

Re: How to file a feature request

[Daniel Shahaf]

James Fainer wrote on Wed, Oct 06, 2010 at 11:10:02 -0400:
> I would like to file a feature request but don't want to clutter the issue
> tracker inadvertently. What is the proper process? 
> 

To propose it on this list first.

>  
> 
> Jim Fainer
> 

Question about new server features from 1.2.1 to today

[Steven W. Orr]

Please be gentle since I'm sort of new at this.

We are using svn client software that's around the 1.6.6 area, but the 
server hasn't been upgraded since the paleolithic era. It sits at 1.2.1.


I am being asked what the *feature* differences are between the 1.2.1 
server and the latest version. I took a quick poke at the ChangeLog and 
release notes, but the ability to see what the differences are at the 
server side (versus client) are not clear.


I see on

http://subversion.apache.org/docs/release-notes/

a very concise description of what generally to expect.

If someone could point me in the right direction (or expound a bit) on 
what the server feature side of things look like, that would be very 
helpful.


TIA

Steve Orr

Re: Question about new server features from 1.2.1 to today

[Andy Levy]

On Wed, Oct 6, 2010 at 12:37, Steven W. Orr  wrote:
> Please be gentle since I'm sort of new at this.
>
> We are using svn client software that's around the 1.6.6 area, but the
> server hasn't been upgraded since the paleolithic era. It sits at 1.2.1.
>
> I am being asked what the *feature* differences are between the 1.2.1 server
> and the latest version. I took a quick poke at the ChangeLog and release
> notes, but the ability to see what the differences are at the server side
> (versus client) are not clear.
>
> I see on
>
> http://subversion.apache.org/docs/release-notes/
>
> a very concise description of what generally to expect.
>
> If someone could point me in the right direction (or expound a bit) on what
> the server feature side of things look like, that would be very helpful.

The release notes really are the best, most concise descriptions. The
items that aren't really obvious from the name/description have
"(client)" or "(server)" next to them. Most of these can't be
described (especially if you want to gain an understanding of what the
change means) by a 5-word bullet point.

Feature request

[James Fainer]

I am looking to reduce the potential complexity of path access rules by
applying wild card rules in the repository section of the path access rules
configuration. 

 

i.e. 

<> 

[dev:/branch]

@group1=rw

 

[dev2:/branch]

@group2=rw

 

<>

Define repository with a prefix

 

eng_Project1

eng_project2

restrict_project1

 

rule:

[eng_*:/]

@group1 = rw

 

[restrict_*:/]

@group2=rw

 

Thanks,

Jim Fainer

Re: Subversion 1.6.13 Released

[David Darj]

 I'm happy to announce my release of Subversion 1.6.13 Win32 binaries 
and installer


They are available at my website:http://alagazam.net
and also on SourceForge: http://sourceforge.net/projects/win32svn/


Release notes for the 1.6.x release series may be found at:

http://subversion.apache.org/docs/release-notes/1.6.html

You can find the list of changes between 1.6.13 and earlier versions at:

http://svn.apache.org/repos/asf/subversion/tags/1.6.13/CHANGES

Questions, comments, and bug reports to us...@subversion.apache.org.

Regards,

David Darj
http://alagazam.net

Re: Feature request

[Johan Corveleyn]

On Wed, Oct 6, 2010 at 7:25 PM, James Fainer  wrote:
> I am looking to reduce the potential complexity of path access rules by
> applying wild card rules in the repository section of the path access rules
> configuration.
>
>
>
> i.e.
>
> <>
>
> [dev:/branch]
>
> @group1=rw
>
>
>
> [dev2:/branch]
>
> @group2=rw
>
>
>
> <>
>
> Define repository with a prefix
>
>
>
> eng_Project1
>
> eng_project2
>
> restrict_project1
>
>
>
> rule:
>
> [eng_*:/]
>
> @group1 = rw
>
>
>
> [restrict_*:/]
>
> @group2=rw

To me that seems a sensible feature request (but I am just one user).

Note though that there is some similarity with another existing feature request:
http://subversion.tigris.org/issues/show_bug.cgi?id=2662 - authz with wildcards

But that is about wildcards in the path portion, while yours is about
wildcards in the repository part. If you create your issue, you may
wish to link it to 2662 though.

Just my €0.02
Cheers,
-- 
Johan

Re: Checked Out CGI not served by Apache

[Ryan Schmidt]

On Oct 5, 2010, at 16:00, James Simpson wrote:

> Hi, I am currently trying to set up a python cgi based websystem. I am using 
> an SVN to backup the entirety of my ./www directory. When I create python 
> files manually and access them from the browser they work fine. But if they 
> are checked out from the svn they do not get served by apache and it returns 
> a 500 internal server error instead.
> The permissions of the files appear to be fine as they match the permissions 
> and ownerships of the manually created files. What might be causing this 
> behaviour as I cant see the difference between the files created manually and 
> those checked out from the svn.

James, I notice you haven't received many replies to your question, which I 
imagine is because you've told us "I have two files that are behaving 
differently but there is nothing different about them" which doesn't give us 
much to go on. Clearly there has to be a difference somewhere, and since you're 
in front of the computer and not us, you'll have to figure out what it is. You 
already think you've ruled out everything, so start over and rule out nothing; 
re-check everything. Investigate contents of files, Subversion properties, 
permissions, ownership, security context (if using SELinux). Investigate 
permissions and ownership of all parent directories. Double-check everything 
about the Apache configuration. And check the Apache access and error logs for 
more clues. Good luck.

Sending attachments in email using mailer.py script

[Tech Geek]

Let's say I have an exisiting repository at /var/lib/svn/projectA with
(tags, branches, trunk structure) on my Linux system.

I am using the mailer.py script and mailer.conf file [1] in my post-commit
hook for sending out emails whenever a new release tag (like
projectA/tags/REL-1.0) is created and that is working fine.

My quesiton:
Is there a way I can send a file whose location is
at projectA/tags/REL-1.0/source.zip as an attachment in the emails that get
sent (using mailer.py) whenever a new tag is created?

Thanks

[1]
https://svn.apache.org/repos/asf/subversion/trunk/tools/hook-scripts/mailer/

Re: Sending attachments in email using mailer.py script

[Tech Geek]

I guess my biggest hurdle at this time is how to extract the file from the
repository that I would like to send it as an attachment.

Most of the examples on the net simply specifies an explicit filename (to
show as an example) like this:
*
#!/usr/bin/python
import smtplib
..
filename = "/tmp/test.txt"
.
# Define the attachment section
part3 = """Content-Type: multipart/mixed; name=\"%s\"
Content-Transfer-Encoding:base64
Content-Disposition: attachment; filename=%s
...
%s
--%s--
""" %(filename, filename, encodedcontent, marker)
message = part1 + part2 + part3
try:
   smtpObj = smtplib.SMTP('localhost')
   smtpObj.sendmail(sender, reciever, message)
   print "Successfully sent email"
except Exception:
   print "Error: unable to send email"

*
So basically I would want the path
/var/lib/svn/projectA/tags/REL-1.0/source.zip in the filename variable.

Re: Howto Disable Localistation?

[Nico Kadel-Garcia]

On Wed, Oct 6, 2010 at 10:46 AM, Tony Sweeney  wrote:
> alias svn='LANG=en_US svn'

You've just written a recursive alias.

Try 'alias svn='LANG=POSIX /usr/bin/svn', which fixes the loathsome
case-insensitive sorting behavior of "LANG=en_US'.

Re: Sending attachments in email using mailer.py script

[Nick Stolwijk]

You can checkout the file to /tmp and include it from there. You
cannot reference a file in your repository with a file path.

Hth,

Nick Stolwijk
~Java Developer~

IPROFS BV.
Claus Sluterweg 125
2012 WS Haarlem
http://www.iprofs.nl



On Thu, Oct 7, 2010 at 12:58 AM, Tech Geek  wrote:
> I guess my biggest hurdle at this time is how to extract the file from the
> repository that I would like to send it as an attachment.
>
> Most of the examples on the net simply specifies an explicit filename (to
> show as an example) like this:
> *
> #!/usr/bin/python
> import smtplib
> ..
> filename = "/tmp/test.txt"
> .
> # Define the attachment section
> part3 = """Content-Type: multipart/mixed; name=\"%s\"
> Content-Transfer-Encoding:base64
> Content-Disposition: attachment; filename=%s
> ...
> %s
> --%s--
> """ %(filename, filename, encodedcontent, marker)
> message = part1 + part2 + part3
> try:
>    smtpObj = smtplib.SMTP('localhost')
>    smtpObj.sendmail(sender, reciever, message)
>    print "Successfully sent email"
> except Exception:
>    print "Error: unable to send email"
> *
> So basically I would want the path
> /var/lib/svn/projectA/tags/REL-1.0/source.zip in the filename variable.
>
>

Re: Sending attachments in email using mailer.py script

[Tech Geek]

>
> You can checkout the file to /tmp and include it from there. You
> cannot reference a file in your repository with a file path.


I had thought about that but it would mean that I will need to include a svn
checkout command to /tmp/ directory in my post-commit hook, right?

If that is the case indeed then I am not sure how to get the checkout path
of the latest tag commited in my post-commit hook.

As an example:
So the $REPOS in post-commit has path to the project -  for example:
/var/lib/svn/projectA. How do I get the path of the tag (so that I can
concatenate with $REPOS) that is just being commited - for examle:
tags/REL-1.00.

Re: Sending attachments in email using mailer.py script

[Tech Geek]

OK I have managed to get the name of the file (after checking out to the
/tmp directory) to be attached in the commit email in a variable called
$ATTACHFILE in my post-commit hook.

But here is another issue that I am now running into:
How do I pass the value of the variable $ATTACHFILE  to the mailer.py python
script without wrecking the order of the parameters it expects?

Thanks

Re: Importing Existing Repository into a New Repository

[Tech Geek]

>
> svnadmin dump -rHEAD /path/to/oldrepo > dump
> svnadmin load /path/to/newrepo < dump
>
Thanks Ryan! That worked!

Why doesn't 'svnadmin create' creates tags, branches, trunk?

[Tech Geek]

So I am relatively new to subversion as compared to most of the folks on
this mailing list. After seeing lot of examples over the web and reading
official subversion book it seems that almost every body creates their
repository in some or the other way with tags, branches and trunk structure
even though for Subvrsion itself these concepts do not exits.

So why don't we have (read as a feature) something like this:

# svnadmin create --tbt new_repo

and a repositroy with following strcuture is created (automatically)

# ls /var/lib/svn/new_repo
branches
tags
trunk

Basically the optional arugment "--tbt" in the above command creates the
sub-directories tags, branches, trunk automatically for you.

It would be a nice (raed useful) feature to have.

What do you guys think?

Thanks!

Re: Howto Disable Localistation?

[Ulrich Eckhardt]

On Thursday 07 October 2010, Nico Kadel-Garcia wrote:
> On Wed, Oct 6, 2010 at 10:46 AM, Tony Sweeney  wrote:
> > alias svn='LANG=en_US svn'
>
> You've just written a recursive alias.

No.

Uli

-- 
ML: http://subversion.apache.org/docs/community-guide/mailing-lists.html
FAQ: http://subversion.apache.org/faq.html
Docs: http://svnbook.red-bean.com/

Sator Laser GmbH, Fangdieckstraße 75a, 22547 Hamburg, Deutschland
Geschäftsführer: Thorsten Föcking, Amtsgericht Hamburg HR B62 932

**
Sator Laser GmbH, Fangdieckstraße 75a, 22547 Hamburg, Deutschland
Geschäftsführer: Thorsten Föcking, Amtsgericht Hamburg HR B62 932
**
   Visit our website at 
**
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. Sator Laser GmbH ist für diese Folgen nicht 
verantwortlich.
**

Re: Why doesn't 'svnadmin create' creates tags, branches, trunk?

[Siva Kumar]

You can achieve the same by having a svnadmin alias in linux and a
wrapper batch in windows.