Closing as we're using git nowadays.

thx && regards,
-mika-

many of your listed executables are from our grml-mercurial-utils packet ;).

thats my helper scripts for managing our hg repositories.
hg-cleantree(1):    cleans up a hole repository tree
hg-mirror (1):      create a full mirror over hgwebdir
hg-reposearch (1):  scan for mercurial repositories in the given directories.

as hg-buildpackage from debian is coded in haskel it's quite hard to reuse code
from it in any useable form to our hg-buildpackage.

anyway, i think we could mark this as resolved/wontfix as it doesn't matter anymore.

hg-buildpackage from John Goerzen inside Debian/unstable features several 
scripts:

hg-buildpackage(1): helper program to maintain Debian packages with mercurial
hg-cleantree(1):    cleans up a hole repository tree
hg-importdsc(1):    import a Debian source package into hg-buildpackage archive
hg-importorig(1):   import an upstream source into a hg-buildpackage archive
hg-markdeb(1):      mark the Debian version of the working directory in archive
hg-mirror (1):      create a full mirror over hgwebdir
hg-reposearch (1):  scan for mercurial repositories in the given directories.

Our current hg-buildpackage at grml works just fine for me, but I'd like to get 
some of the features hg-buildpackage of official Debian has. :) Especially some 
kind of automatism when working with new upstream sources would be great. A 
process how to merge/rebase the mercurial tree with a different remote 
repository (like svn, git,...) would be great too (not sure what's the best 
option here, rebasing it manually is pretty hard sometimes).

What do you, Gebi and Formorer think about that? Does anyone of you care to 
help in working on that?

regards,
-mika-