Mercurial 1.1 has been released, fixing many bugs and providing some performance enhancements. It would be nice to have this in portage. It also fixes any remaining issues with running on Python 2.6. Reproducible: Always
Don't CC maintainers when you cannot assign bugs.
Okay, sorry... why not?
Renaming the ebuild to version 1.1 worked for me.
...that's for amd64. (sorry for the double post. I only now remembered to add the architecture)
Sorry to nag, but could you give a status update? I already use the simply renamed ebuild in production, and I didn't find any problems. mercurial-1.1.ebuild Can I somehow help testing, so it gets in the tree faster?
same here : i've renamed the last mercurial ebuild to 1.1 and installed it on several production computers, and have had no problem so far. I enjoy new features a lot (rebase, mostly!)
This version is also compatible to hgsubversion, which provides a real hg-svn bridge, so I can develop in hg but then directly push to svn (needs rebase). hgsubversion is in alpha state right now, though. - http://www.selenic.com/mercurial/wiki/index.cgi/HgSubversion (if this comment went too much OT for your taste, please tell me and I'll stop)
no, not offtopic :) I'm about to test hgsubversion, great to know it works for you.
This is just a quick note that 1.1.1 is out and bumping the ebuild still works (for me). :)
Hi, Is where any news? Newest versions (>=1.1) of Mercurial have different format of repositories, so repositories created with the new hg cannot be used with previous versions, so I think this bug should have higher severity.
The new repository format only matters if you clone from filesystem (for example from USB stick), but not if you clone over the wire. Mercurials wire protocol had been stable since 0.6. Still I'd like to see Mercurial 1.1.1 in the tree as soon as possible. Can I somehow contribute in getting the ebuild included (renamed) earlier? I assume that attaching an ebuild wouldn't really help, since it would just be the renamed 1.0.2 ebuild. @everyone interested: Did you already vote for this bug?
Since the maintainer has a devaway message set, I took the liberty to do the version bump.
Thank you very much!