Please backport mercurial 1.0.1-2 from Intrepid to Hardy and Gutsy

eh, I cannot set the Importance?? Set it to Wishlist please.

Once it's in Intrepid, it can be tested for backporting. Added hardy-backports, but not a valid Ubuntu Mercurial bug (backports is separate).

OK, sorry, don't know exactly about those rules. I just wanted to open a bug so that it's known and kept in mind.

No problem. Once intrepid opens, it'l get it automatically from Debian.

Sure? In both lenny and sid there are 1.0.x packages, but they are not yet in Intrepid.

 mercurial | 1.0-7 | http://archive.ubuntu.com intrepid/universe Sources

And 1.0.1-1 has just been synced: https://edge.launchpad.net/ubuntu/+source/mercurial/1.0.1-1

This needs to be tested before the backport can happen.

Downloaded and compiled the sources from intrepid. Works fine so far. No binary dependencies besides a small self compiled module. The rest is all python and utility programs for the user. No source changes needed.

Jörg, if you're testing the dependecy chain, please also check the reverse dependencies.
$ apt-cache rdepends mecurial

A slightly more correct spelling of mercurial produces:

mercurial
Reverse Depends:
  tailor
 |qct
  mr
 |ikiwiki
  hg-load-dirs
  hg-buildpackage
 |etckeeper
 |commit-tool
  cia-clients
  devscripts

Tested tailor, works. Educated guess: the rest works, too as they mainly seem to depend on the cli, which did not change significantly.

Test out hg-buildpackage and if that works I'll approve it.

Worked like a charm after I found out how. Sorry for any inconvenience, but this is my first "This needs to be tested"

You might as well make sure https://bugzilla.redhat.com/show_bug.cgi?id=453550 is added to the package (fix for CVE-2008-2942).

Due to the CVE, you should at least backport 1.0.1-2 instead.

tonfa wrote:
> Due to the CVE, you should at least backport 1.0.1-2 instead.
>
We can only backport the version in the devel cycle at this time it
would hav eto be version in Intrepid. the version in intrepid is
gnomefreak@Development:~$ policy mercurial
mercurial:
  Installed: 1.0.1-1
  Candidate: 1.0.1-1
  Version table:
 *** 1.0.1-1 0
        500 http://gb.archive.ubuntu.com intrepid/universe Packages
        100 /var/lib/dpkg/status

I think waiting for intrepids version to catch up would be best instead
of backporting it more than once in a short time period

--
Sincerely Yours,
    John Vivirito

https://launchpad.net/~gnomefreak
https://wiki.ubuntu.com/JohnVivirito
Linux User# 414246

The sync for 1.0.1-2 has been requested, so this should wait.

Ack for ubuntu-backporters for 1.0.1-2.

Will it also be backported to gutsy?

So far it's not been requested. It would have to be requested (use also
affects to add gutsy-backports) and them tested on gutsy.

 * Trying to backport mercurial...
  - <mercurial_1.0.1-2.dsc: downloading from librarian>
  - <mercurial_1.0.1-2.diff.gz: downloading from librarian>
  - <mercurial_1.0.1.orig.tar.gz: downloading from librarian>
I: Extracting mercurial_1.0.1-2.dsc ... done.
I: Building backport of mercurial-1.0.1 as 1.0.1-2~hardy1 ... done.