Please backport mercurial 0.9

Bug #52529 reported by Louai Al-Khanji
24
Affects Status Importance Assigned to Milestone
Dapper Backports
Invalid
Medium
Unassigned
mercurial (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Dapper currently includes 0.7, which is already quite old. 0.9 adds quite a few new features, and is almost perfectly backwards compatible with 0.7.

Please consider backporting the newer package to dapper.

Revision history for this message
John Dong (jdong) wrote :

certainly will do. The new mercurial is a great improvement over 0.7!

Changed in dapper-backports:
importance: Untriaged → Medium
status: Unconfirmed → Confirmed
Revision history for this message
John Dong (jdong) wrote :

 -> Considering debhelper (>= 5.0.37.2)
      Tried versions: 5.0.7ubuntu13
   -> Does not satisfy version, not trying

Unfortunately, package requires newer debhelper than Dapper can provide.

Mercurial Ubuntu packagers -- is the explicit debhelper version requirement necessary or can it be removed to facilitate backporting?

Revision history for this message
John Dong (jdong) wrote :

Rejected from dapper-backports until we receive word from mercurial packagers.

Changed in dapper-backports:
status: Confirmed → Rejected
Revision history for this message
Omnifarious (omnifarious) wrote :

And now, of course, Mercurial is up to 0.9.1 as of July 24th.

Revision history for this message
Kai Kasurinen (kai-kasurinen) wrote :

Reject Ubuntu task.

Changed in mercurial:
status: Unconfirmed → Rejected
Revision history for this message
^rooker (rooker) wrote :

Since this request is now over 1 1/2 year old: are there any news regarding this decision?
(I didn't really understand why this request is declared "illegal")

Revision history for this message
^rooker (rooker) wrote :

Sorry, but I forgot to mention, that mercurial v0.7 that currently comes with dapper does not work with Dapper's current Python version (v2.4) - so backporting a more recent version would actually make mercurial usable at all.

I'm refering to bug #53131:
https://bugs.launchpad.net/ubuntu/+source/mercurial/+bug/53131

Revision history for this message
Scott Kitterman (kitterman) wrote :

Answer the question in comment 2 above is what's needed.

Revision history for this message
^rooker (rooker) wrote :

ok. That was also my assumption. Thanks for clearing it up.
Still it feels strange that there hasn't been *any* reply from the mercurial developers since July 2006 - That's almost 2 years...

Revision history for this message
tonfa (bboissin) wrote :

I don't have any problem running 0.7 with python2.5, or python2.4 from Hardy. I don't believe the problem is with mercurial, it might be a packaging problem or something else.

(anyway 0.7 is really really old for something like mercurial which was started in 2005, it is only 6 months after the initial release!)

Revision history for this message
Omnifarious (omnifarious) wrote :

Well, I would answer, but I know nothing of the Debian package management system or what debhelper is even for.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.