My vote for a Mercurial backend

[daniel@…]

While reading VersioningSystemBackend I noticed that no one had file a ticket yet for a Mercurial backend. As the wiki page indicates, Mercurial(hg) will give more information into what it does. Interesting to note that it is written in Python. Hope the new plugin system might allow for this type of integration.

[eric-trac@…]

I'm adding my vote for Mercurial here too. I might even take it upon myself to do some work for this. I would even rather this over Perforce as I've written myself some scripts that will keep a Mercurial repository in sync with a Perforce one.

[pjd@…]

Another vote here. Only a lack of time keeps me from jumping in and helping out, at the moment.

[soloturn@…]

if voting works like that here: +1

[mgood]

No, we don't really use a voting system here.

[cboos]

I've got a working version of Trac+Hg. No major issues, but I need to make a proper plugin before making the code available (next Wednesday).

Related versioncontrol generalization work will go here:

source:branches/cboos-dev/vc-refactoring

and the Mercurial GPL plugin will go here:

source:branches/cboos-dev/hg-plugin

[sean at dague dot net]

Another vote for Mercurial plugin! Can't wait to see the code released. :)

[cboos]

Have a look at r2472 and check for the documentation in TracMercurial.

I'll also upload a patch for the vc-refactoring branch against 0.9 here, as well as drop an egg or two...

[cboos]

The hg-plugin (developed on windows with ActiveState Python 2.4.1, I don't know yet if the egg will work on another platform/version)

[cboos]

The vc-refactoring changes , as of r2472 + r2490, which can be applied on Trac 0.9. Should handle the creation of new Trac environments correctly!

[cmlenz]

This should probably be taken to trac-hacks?

[cboos]

Well, there's still a vc-refactoring phase 2 awaiting... (see related mails on Trac Dev).

When that's finished, I could host the plugin on Trac Hacks (or somewhere else), but in the meantime, I think it makes sense to keep it close to the (next) vc-refactoring branch.

[mgood]

Replying to cboos:

Well, there's still a vc-refactoring phase 2 awaiting... (see related mails on Trac Dev). When that's finished, I could host the plugin on Trac Hacks (or somewhere else), but in the meantime, I think it makes sense to keep it close to the (next) vc-refactoring branch.

Do we need to keep this ticket open since there's a plugin for this? If there are changes needed in the vc-refactoring I think we can open separate tickets for those issues.

[cboos]

Replying to mgood:

Do we need to keep this ticket open since there's a plugin for this? If there are changes needed in the vc-refactoring I think we can open separate tickets for those issues.

Ok, we can consider that there's a backend now, see TracMercurial... even if it seriously lacks maintenance and progress... Do anyone know how I could hg clone myself? ;)

I'm setting the milestone to 0.10, as this is the corresponding Trac release for the plugin.

[anonymous]

how to configure?

http://svn.edgewall.com/repos/trac/sandbox/mercurial-plugin-0.11 I follow all the instructions but always got error:

Warning: Can't synchronize with the repository (Unsupported version control system "hg". Check that the Python support libraries for "hg" are correctly installed.)

[anonymous]

repository_dir = \hg\code1 repository_type = hg

[components] tracext.hg.* = enabled

[hg] # -- Show revision number in addition to the changeset hash show_rev = yes

# -- Changeset hash format node_format = short # hex: Show the full SHA1 hash # short: Show a shortened hash for the changesets

-- so, repository_type can only be svn , not HG ?

[jruigrok]

A better place would be to ask on the mailing lists and not reopen a ticket that has been closed for close to 2 years.

[cboos]

Right, you should ask on the Trac-user MailingList for support questions, as you'll likely find more people there that had and solved similar installations issues.

You should also have a look into the log, for a meaningful backtrace.