Problem with Trac install script in Virtualmin Pro

The install starts out fine, but then I get this:

[code:1]Python module subversion is required …
Installing package python-subversion …

  Installing package(s) with command yum -y install python-subversion ..

  Loading "installonlyn" plugin
  Setting up Install Process
  Setting up repositories
  Reading repository metadata in from local files
  Parsing package install arguments
  Nothing to do

  .. install complete.

… automatic Python module installation failed[/code:1]

I’m on CentOS 5. How can I get around this?

I could install Trac manually but that’s a real pain in the butt and the install script is there so I’d like to use it. Any ideas?

i dont think there is a package python-subversion known in centos.
but you can download one here or even better look here

seems to be called: subversion<br><br>Post edited by: ronald, at: 2008/07/05 14:26


I’m under the impression that you shouldn’t need to go to a third party software repository in order to install any of the programs from the Script Installers. Things can go awry when you start using unsupported software.

While “python-subversion” is in fact provided by the “subversion” package in the DAG RPM repository, I highly recommend against using it – what I would do is file a Virtualmin bug report and see what they had in mind for how you’d get Trac installed on CentOS.

i just checked on my (default) centos system.
subversion is a default package from Centos base repository:
Package subversion - 1.4.2-2.el5.i386.
which can be installed with yum install subversion

what I think it may be is that the install script says::yum -y install python-subversion" and that is not in centos, so it wouldn’t know what to do with that command.

submitting a ticket is a good idea to get this corrected.

I have encountered the same problem. Did you find a solution?

Oops. There is no need for a python-subversion package on CentOS (or any of the Red Hat based systems). It’s already installed as part of the subversion package. It’s a bug in detection, as the module is actually named “svn”. I’ll update the ticket and hand it over to Jamie for fixing.

Thanks a lot, I kind of thought that was the issue.