Null argument when running initenv

[rasheed.abdulaziz@…]

I reviece the same error no matter what I try. Perhaps I am missing something? OS is XP Pro.

The process I follow is:

C:\Tools\Python\Scripts>python trac-admin c:\tracenv\trac1.db initenv
Creating a new Trac environment at c:\tracenv\trac1.db

Trac will first ask a few questions about your environment
in order to initalize and prepare the project database.

 Please enter the name of your project.
 This name will be used in page titles and descriptions.

Project Name [My Project]> Test

 Please specify the absolute path to the project Subversion repository.
 Repository must be local, and trac-admin requires read+write
 permission to initialize the Trac database.

Path to repository [/var/svn/test]> c:\TestRepo

 Please enter location of Trac page templates.
 Default is the location of the site-wide templates installed with Trac.

Templates directory [c:\Tools\Python\share\trac\templates]>
c:\TestRepo Repository access error: null argument to internal routine

[remco.boema@…]

Some problem here.

I'm on w2k, using the ​svn-win32-1.0.9_py bindings to trac, using a windows installer whenever possible. (apache2, svn, etc)

I've rebuilt my svn repository using berkley db instead of FSFS, and it seems that is the problem.

i've used '/' slashed paths when asked for paths by trac-admin initenv (except for the last one, the templates location)

It seems this works, as the program no longer crashes.

Hope this helps.

[Christopher Lenz]

You're probably using subversion 1.1.x, but the subversion python bindings for an earlier version (1.0.x). See ​this thread on the mailing list.

Please reopen if this is not the case.

[anonymous]

Getting this problem relentlessly. Not doing anything wrong and I tried changing slashes to forward slashes on the repospath but that didn't work. Getting frustrated.

[Matthew Good]

As cmlenz said above this is likely due to a mismatch in versions between the SVN applications and the bindings you've installed. If it's not, it still looks like an issue with your installation, so please ask on the MailingList or IrcChannel for support.

[anonymous]

Same problem here, consistent subversion 1.2.3 on WinXP.

It's fixed if the subversion repository was created as a native filesystem, not berkeley db.

Not sure whose bug this is.

[Christian Boos]

Can you try with the fix corresponding to r2461 applied?

[Christian Boos]

I think r2461 will make the error reported in this ticket less likely to happen (at least, it did so for me). Ported to stable in r2710.