Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 249688 - version bump dev-util/mercurial to 1.1
Summary: version bump dev-util/mercurial to 1.1
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: High enhancement with 2 votes (vote)
Assignee: Krzysztof Pawlik (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: python-2.6
  Show dependency tree
 
Reported: 2008-12-03 10:07 UTC by Dirkjan Ochtman (RETIRED)
Modified: 2008-12-29 15:34 UTC (History)
10 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dirkjan Ochtman (RETIRED) gentoo-dev 2008-12-03 10:07:29 UTC
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
Comment 1 Jeroen Roovers (RETIRED) gentoo-dev 2008-12-03 16:47:41 UTC
Don't CC maintainers when you cannot assign bugs.
Comment 2 Dirkjan Ochtman (RETIRED) gentoo-dev 2008-12-03 16:48:53 UTC
Okay, sorry... why not?
Comment 3 Arne Babenhauserheide 2008-12-04 00:16:25 UTC
Renaming the ebuild to version 1.1 worked for me. 
Comment 4 Arne Babenhauserheide 2008-12-04 01:37:33 UTC
...that's for amd64. 

(sorry for the double post. I only now remembered to add the architecture)
Comment 5 Arne Babenhauserheide 2008-12-13 09:40:59 UTC
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? 
Comment 6 Thomas Capricelli 2008-12-13 17:49:17 UTC
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!)
Comment 7 Arne Babenhauserheide 2008-12-13 22:27:16 UTC
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)
Comment 8 Thomas Capricelli 2008-12-14 01:45:52 UTC
no, not offtopic :)
I'm about to test hgsubversion, great to know it works for you.
Comment 9 Holger Hoffstätte 2008-12-21 09:45:53 UTC
This is just a quick note that 1.1.1 is out and bumping the ebuild still works (for me). :)
Comment 10 Mike Limansky 2008-12-24 22:17:24 UTC
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.
Comment 11 Arne Babenhauserheide 2008-12-28 19:09:07 UTC
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? 
Comment 12 Ben de Groot (RETIRED) gentoo-dev 2008-12-29 13:20:38 UTC
Since the maintainer has a devaway message set, I took the liberty to do the version bump.
Comment 13 Arne Babenhauserheide 2008-12-29 15:34:14 UTC
Thank you very much!