PortAudio TRAC Wiki down

[Phil Burk]

When I go to:

http://www.portaudio.com/trac/wiki/

I get "TracError: Unsupported version control system "svn"."

This is apparently a common error for TRAC and is described here:

http://trac.edgewall.org/wiki/TracSubversion#unsupported-vcs

When I enter:

   python

it says nothing about svn. I can "import svn" without errors but it does
not say "from svn import core".

This suggests that the Python-SVN bindings were not installed. But it
used to work. What changed and when?

I used TRAC about a month ago. Has anyone used it since then? I am
trying to bracket the time when it failed.

Also if anybody has expertise in this area of TRAC/SVN/Python and wants
to help me debug this then it would be appreciated.

Thanks,
Phil Burk
415-453-4320
California


_______________________________________________
Portaudio mailing list
Portaudio@...
http://techweb.rfa.org/mailman/listinfo/portaudio

[Gordon Gidluck]

Hi Phil,
I'm not an expert with Trac and SVN, but we use it here.

It sounds like it can't find the libraries that it needs.

I assume this server might be using Apache? If so, I found reference to
some libraries in the Apache .conf file here.
However, ours is working and those lines are commented out.
(this is /usr/local/apache2/conf/httpd.conf)

# To be able to use the functionality of a module which was built as a
DSO you
# have to place corresponding `LoadModule' lines at this location so the
# directives contained in it are actually available _before_ they are used.
# Statically compiled modules (those listed by `httpd -l') do not need
# to be loaded here.
#
# Example:
# LoadModule foo_module modules/mod_foo.so
LoadModule php4_module             modules/libphp4.so
#LoadModule  dav_module             modules/mod_dav.so
#LoadModule  dav_svn_module         modules/mod_dav_svn.so
#LoadModule  authz_svn_module       modules/mod_authz_svn.so
#LoadModule dav_svn_module     modules/mod_dav_svn.so
#LoadModule authz_svn_module   modules/mod_authz_svn.so

 From the comment, apparently this means is that the libraries are
statically linked into the Apache build we are running.

The files I found on our system for svn are:

-rwxr-xr-x    1 root     root        28643 Jan  3 17:52 mod_authz_svn.so
-rwxr-xr-x    1 root     root       366928 Jan  3 17:52 mod_dav_svn.so

A few things it could be...
1) Possibly the apache code was updated and the modules are not
statically linked in the new build.
2) or an environment variable is not set that tells where the libraries
are located
3) or the apache user does not have read and execute access to the files.

Gordon


Phil Burk wrote:

> When I go to:
>
> http://www.portaudio.com/trac/wiki/
>
> I get "TracError: Unsupported version control system "svn"."
>
> This is apparently a common error for TRAC and is described here:
>
> http://trac.edgewall.org/wiki/TracSubversion#unsupported-vcs
>
> When I enter:
>
>    python
>
> it says nothing about svn. I can "import svn" without errors but it does
> not say "from svn import core".
>
> This suggests that the Python-SVN bindings were not installed. But it
> used to work. What changed and when?
>
> I used TRAC about a month ago. Has anyone used it since then? I am
> trying to bracket the time when it failed.
>
> Also if anybody has expertise in this area of TRAC/SVN/Python and wants
> to help me debug this then it would be appreciated.
>
> Thanks,
> Phil Burk
> 415-453-4320
> California
>
>
> _______________________________________________
> Portaudio mailing list
> Portaudio@...
> http://techweb.rfa.org/mailman/listinfo/portaudio
>
>  

_______________________________________________
Portaudio mailing list
Portaudio@...
http://techweb.rfa.org/mailman/listinfo/portaudio

[Phil Burk]

Thanks Gordon. That was helpful.

Apparently this is a common error:

  http://trac.edgewall.org/wiki/TracSubversion#unsupported-vcs

The typical diagnosis is that the Python-SVN binding was not installed.
But it was installed several months ago and until recently it was
working fine.

I notice that our server hosting provider apparently did a massive
upgrade of the system on Jun 28. Several things apparently broke at the
time including some mail accounts.

So I will pursue a solution with our hosting provider.

I'll send a note to the list when I get a fix.

Phil Burk


Gordon Gidluck wrote:

> A few things it could be...
> 1) Possibly the apache code was updated and the modules are not
> statically linked in the new build.
> 2) or an environment variable is not set that tells where the libraries
> are located
> 3) or the apache user does not have read and execute access to the files.
_______________________________________________
Portaudio mailing list
Portaudio@...
http://techweb.rfa.org/mailman/listinfo/portaudio