Edgewall Software

Ticket #1847 (closed enhancement: fixed)

Opened 3 years ago

Last modified 9 months ago

My vote for a Mercurial backend

Reported by: daniel@… Owned by: cboos
Priority: high Milestone: 0.11
Component: version control Version: devel
Severity: major Keywords: mercurial
Cc: eric-trac@…

Description

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.

Attachments

TracMercurial-0.1-py2.4.egg (14.6 kB) - added by cboos 3 years ago.
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)
vc-refactoring_for_trac-0.9.patch (28.8 kB) - added by cboos 3 years ago.
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!

Change History

  Changed 3 years ago by 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.

  Changed 3 years ago by eric-trac@…

  • cc eric-trac@… added

  Changed 3 years ago by cmlenz

  • owner changed from jonas to cmlenz
  • component changed from general to version control

  Changed 3 years ago by pjd@…

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

  Changed 3 years ago by soloturn@…

if voting works like that here: +1

  Changed 3 years ago by mgood

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

  Changed 3 years ago by cboos

  • owner changed from cmlenz to cboos
  • priority changed from normal to high
  • status changed from new to assigned
  • severity changed from normal to major
  • milestone set to 1.0

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

  Changed 3 years ago by sean at dague dot net

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

  Changed 3 years ago by 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...

Changed 3 years ago by 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)

Changed 3 years ago by 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!

  Changed 3 years ago by cmlenz

  • milestone 1.0 deleted

This should probably be taken to trac-hacks?

follow-up: ↓ 12   Changed 3 years ago by 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.

in reply to: ↑ 11 ; follow-up: ↓ 13   Changed 2 years ago by 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.

in reply to: ↑ 12   Changed 2 years ago by cboos

  • keywords mercurial added
  • status changed from assigned to closed
  • resolution set to fixed
  • milestone set to 0.10

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.

  Changed 9 months ago by anonymous

  • status changed from closed to reopened
  • resolution fixed deleted
  • milestone changed from 0.10 to 0.11

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.)

  Changed 9 months ago by 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 ?

  Changed 9 months ago by jruigrok

  • status changed from reopened to closed
  • resolution set to fixed

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.

  Changed 9 months ago by 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.

Add/Change #1847 (My vote for a Mercurial backend)

Author



Change Properties
<Author field>
Action
as closed
Next status will be 'reopened'
 
Note: See TracTickets for help on using tickets.