Hi Ryan! Hope all is well. I have been successful in getting Trac to work with multiple repositories, using your previous instructions from months ago. I also implemented fine grained controls to control who can access the different repositories. The only thing left was indeed to Bitten to be able to build on the different repositories.
What you said makes total sense. I managed to track the problem back to _multirepos_ as well, but didn't think we had installed a different version of track that doesn't have that code. I'll try to reinstall with the bitten trunk, and let you know how it goes. Best, Tom On Wednesday, January 18, 2017 at 12:10:27 PM UTC-8, RjOllos wrote: > > > > On Tuesday, January 17, 2017 at 3:42:17 PM UTC-8, RjOllos wrote: >> >> >> >> On Friday, January 13, 2017 at 6:19:27 PM UTC-8, [email protected] >> <javascript:> wrote: >>> >>> Hi all, >>> >>> I'm currently running Trac 1.0.10 with Bitten 0.6, and am trying to get >>> Bitten to build off of multiple repo >>> >>> I recently added a new repository to my Trac instance. >>> >>> I then commented out the following line within trac.ini: >>> >>> .dir = <default_repo_path> >>> >>> Afterwards I readded my original main repo with the repositories >>> interface, and created an (default) alias of that repository. >>> I >>> >>> I was happy to see that Bitten autocompletes the svn path with >>> "/repo_1/trunk" or "/repo_2/branches", etc. >>> >>> All of my old configurations that have the path "/trunk" are still >>> working, however, if I try to change any of them to "/repo_1/trunk", I get >>> the following error: >>> "Invalid Repository Path: "repo_1/trunk" does not exist within >>> the "(default)" repository. >>> >>> It seems like Bitten knows where to look to suggest paths ("/repo_1/" or >>> "/repo_2"), but will only successfully work if the path only already within >>> "(default)". >>> >>> Any help is certainly appreciated. >>> >>> Thank you very much, have a nice day. >>> >>> Best, >>> >>> Tom >>> >> >> Hi Tom! >> >> It looks like multiple repository support was implemented for Bitten >> 0.7dev (1), so the configuration you are aiming for should be supported. >> >> I tried to reproduce the issue, but could not. The error message 'does >> not exist within the "(default)" repository' is suspicious. It looks like >> an error that would be seen for a Trac without multirepository support. >> When I enter an invalid path I see the error: 'Invalid Repository Path >> "proj1/invalid"'. >> >> The suggestion for autocompleting the path comes from Trac, whereas >> Bitten will determine whether the repository path exists (by making calls >> to the Trac API). It seems that _multirepos_ isn't being detected by Bitten >> for your configuration, but I cannot see how that could be the case unless >> you database had a missing or incorrect entry for "database_version" in the >> system table (2). >> >> - Ryan >> >> (1) https://bitten.edgewall.org/ticket/765 >> (2) >> https://bitten.edgewall.org/browser/trunk/bitten/util/repository.py?marks=23,27-33#L12 >> > > I thought about it some more. I bet you are running Bitten 0.6.x rather > than 0.7dev, and that the error message originates from here: > > https://bitten.edgewall.org/browser/branches/0.6.x/bitten/admin.py?marks=290-291&version=911#L265 > > Since the paths are autocompleted by Trac's suggest.js, I expect the > autocomplete would still work fine even running the older version of Bitten. > > I checked our install scripts and confirmed that they install Bitten 0.6.x: > http://svn.edgewall.org/repos/bitten/branches/0.6.x > > The reason we stayed with 0.6.x is that you have a patch to Bitten that > applies cleanly to 0.6.x, but would need a little work to be rebased on > 0.7dev (trunk). > > To get this working you'll just need to download Bitten trunk, apply your > (rebased) patch and reinstall. > > - Ryan > > > -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
