OpenSUSE Linux Rants

OpenSUSE Linux Tips, tricks, how-tos, opinions, and news

My Resume  -  My LinkedIn Profile

August 22, 2006

SUSE and subversion

by @ 7:07 am. Filed under General SUSE

I thought that it was cool that US retailer W.S. Badcock is switching to Suse for 320 stores. Keep it rockin’, baby.

I spent Friday installing subversion. THERE is some cool software. I spent half the day reading the subversion documentation. Then, when I felt the ADD kick in, I knew I couldn’t read anymore. I had to get started with the hands-on portion. I fired up YAST and installed subversion without a hitch. I got a repository created and edited the config and password files.

What’s cool is that subversion caches usernames and passwords so that you don’t have to type them in 10 thousand billion times everytime you want to check files out or in. I could check stuff out but I couldn’t check them in. After a few minutes, I discovered that the default configuration makes it so that repositories are read-only. After changing a config file to allow commits, I was crackin’.

Right on, subversion is the man, just like SUSE Linux.

10 Responses to “SUSE and subversion”

  1. Steve Says:

    Hey Grannie,

    I didn’t know you were starting on it already. Isn’t it a snap in the eyeball? It’s *so* easy to use (svn help, svn help co, etc.), really easy to setup, and it makes your life much happier finally having decent version control.

    I tell u whot.

  2. David Says:

    So anyone have a cheatsheet for standing up Subversion on SLES 10? I’ve got the server installed but need to wire up apache etc. and I’m lazy. Hate to have to dig through all of redbook.


  3. Nibb Says:

    Im stunned you managed to install subversion without a hitch. I’ve been witlesslessly trying to put it onto sles 10, using rpm’s from the suse archives and get absolutely nowhere, the whole lot barfs at being unable to see (64 bit), which is on the system, rpm seems to think otherwise, Yast just fails.

    Any ideas?

  4. chris Says:

    I installed subversion on SLES 10 by compiling the source. I have what looks to be a working copy of websvn installed as well — well, we’ll see. As far as svn-apache-dav … I’m not sure it’s going to be as easy as the rest has been… As far as I can tell, there are no RPMs for SLES… just compile the source.

  5. Mike Says:

    RPM’s for SUSE



  6. Dave Says:

    How did you get subversion via YAST? It is not listed there–I could not find it anyway. And compiling from source is not working either as it complains about something I have not deciphered yet:

    cd subversion/libsvn_ra_neon && /bin/sh /root/subversion-1.5.3/libtool –tag=CC –silent –mode=link gcc -g -O2 -g -O2 -pthread -rpath /usr/local/lib -o commit.lo fetch.lo file_revs.lo get_dated_rev.lo get_location_segments.lo get_locations.lo get_locks.lo lock.lo log.lo merge.lo mergeinfo.lo options.lo props.lo replay.lo session.lo util.lo ../../subversion/libsvn_delta/ ../../subversion/libsvn_subr/ /root/subversion-1.5.3/apr-util/ -lexpat /root/subversion-1.5.3/apr/ -lrt -lcrypt -lpthread -ldl /root/subversion-1.5.3/neon/src/
    libtool: link: warning: `/usr/lib64/gcc/x86_64-suse-linux/4.1.2/../../../../lib64//’ seems to be moved
    libtool: link: warning: `/usr/lib64/gcc/x86_64-suse-linux/4.1.2/../../../../lib64//’ seems to be moved
    libtool: link: warning: `/usr/lib64/gcc/x86_64-suse-linux/4.1.2/../../../../lib64//’ seems to be moved
    /usr/lib64/gcc/x86_64-suse-linux/4.1.2/../../../../x86_64-suse-linux/bin/ld: /root/subversion-1.5.3/neon/src/.libs/libneon.a(ne_request.o): relocation R_X86_64_32 against `a local symbol’ can not be used when making a shared object; recompile with -fPIC
    /root/subversion-1.5.3/neon/src/.libs/libneon.a: could not read symbols: Bad value
    collect2: ld returned 1 exit status
    make: *** [subversion/libsvn_ra_neon/] Error 1

  7. Dave S Says:

    I got exactly the same result as Dave, above got. Please let me know if anyone finds the answer.

  8. Dave S Says:

    First I tried ./configure, and that worked, but make failed with the error above. The I used ./configure CFLAGS=”-L/usr/lib64 -fPIC” and then make again, but the error was the same. This is because a change in CFLAGS does not cause a recompile of neon. I removed the .o, .lo, and .libs directory from the neon/src directory and then ran make again (./configure with the CFLAGS setting had already been successful), and that worked great. I found this answer at:

  9. Dean Says:

    To find it via Yast you need to add the add-on product; SuSE 10 SDK.

  10. Brent G Says:

    It looks like the rpm files are maintained here:

OpenSUSE Linux Rants
Official OpenSUSE Linux Site

internal links:


SUSE Resources

search blog:


March 2022
« Feb    

60 queries. 0.264 seconds