Oliver Salzburg wrote:
> Nico Kadel-Garcia wrote;
>> Oliver Salzburg wrote:
>>> Dear users,
>>> as the subject already says, i'm trying to install subversion 1.3.1
>>> under SuSe Linux 9.3. I'm pretty new to linux and have only basic
>>> I've tried installing subversion in a veriety of ways. With SSL,
>>> without, with latest versions of neon and apache, with the versions
>>> packed into the tarball. Either my combinations didn't work at all
>>> or i get presented with this error message when trying to commit any
>>> data from my local machine.
>>> subversion/libsvn_ra_dav/util.c:826: (apr_err=22)
>>> svn: PROPFIND request failed on '/svn/cpp'
>>> subversion/libsvn_ra_dav/util.c:389: (apr_err=22)
>>> svn: Can't set position pointer in file
>>> '/usr/local/svn/repos/cpp/db/revs/0': Invalid argument
>>> My current working installation is running with apache and ssl.
>>> I can connect to the server over both https and http but am getting
>>> the same error. I tried using svn_serve which only leads to the same
>>> My desired repository location is /usr/local/svn/repos/*. This
>>> folder (and all subfolder) are owned by the same user running apache
>>> (daemon). For testing purposed i also applied chmod -R 777 to the
>>> repos folder.
>>> To wrap this up, the packges i am using are the following:
>>> OpenSSL - openssl-0.9.8b.tar.gz
>>> Berkeley DB - db-4.4.20.tar.gz
>>> Apache HTTPD - httpd-2.2.2.tar.gz
>>> Subversion - subversion-1.3.1.tar.gz
>> What in the? OK, Stop trying to compile system-provided software from
>> tarballs. Seriously: you'll just give yourself an atomic wedgie
>> trying to do that, especially with somf of the vagaries in SuSE.
>> Wherever possible, use the available built-in RPM packages.
> The directly available packages (over yast) are outdated. I will try
> to use the ones from the suse mirrors and see if i have any luck.
> I just always felt more comfortable compiling from source.
Then update to SuSE 10. Seriously, SuSE is ill-behaved when you start
stuffing in more recent versions of core facilities by hand-installing them.
That's what a distribution is for: to present a working set of compatible
software. Unless you're a developer, there's a real risk when you
hand-compile the bleeding edge versions of a stack of packages that they
won't play nicely together.
Also, there's a fabulous tool for doing SuSE RPM package update management,
called "fou4s". I highly recommend it over YaST, which doesn't know how to
mix and match from multiple sources and reverts things at odd moments.
Last, if you need the most versions, I see that SuSE publishes SRPM's for
subversion 1.3.0 for SuSE 10.x: why not grab that SRPM, and update it to
subversion 1.3.1 if you really need the most recent release? It should be
safer, especially if SuSe eventually catches up and you wind up switching
back to a default RPM: SuSe does some odd configuration things that will
bite you hard if you don't use their versions of software. (Don't get me
started on their dhcp and DNS oddnesses.)
>> Second, HTTPD version 2.2 is not yet well supported for Subversion.
>> Go back to using the built-in HTTPD for SuSE, unless you want to be
>> one of the developers who works out the problems.
> I've also tried 2.0. Actualy i tried to install the whole thing with
> the versions as they were given in the INSTALL file. This gave me
> either the same or other non-working results.
>> Third, if you need the latest version of Subversion, why not use the
>> SRPM to recompile for your SuSE release? Pretty good ones are
>> available from the Subversion website.
> I'm not yet familiar with. I'll read up.
>> Fouth, does it work with "file://" based operations?
> Yes, file:// operations work perfectly.
Can you look into your HTTP logs for errors?
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Wed May 31 14:19:56 2006