Request for freeze exception for mercurial/1.6.2-1
Hi,
I would like to ask for a freeze exception for mercurial/1.6.2-1
Mercurial is a relatively important package. Currently, mercurial/1.6-2
is in unstable. It is not yet in testing due to #586907
mercurial/1.6.2-1 is a new upstream release. However, 1.6.X upstream
releases are only bugfix releases (new features will be in 1.7). The
packaging between 1.6-2 and 1.6.2-1 is the same (but the Debian patch
integrated by upstream).
Moreover, #586907 (RC bug) should be correctly fixed.
And Javi Merino, who is the main people working on mercurial currently,
prepared the package before the freeze. Due to me being without Internet
access, I haven't been able to upload its package before the freeze.
mercurial/1.6.2-1 can be seen here:
deb http://perso.debian.org/~vdanjean/debian unstable main
http://moais.imag.fr/membres/vincent.danjean/deb.html#mercurial
If I have an ACK from you, I will upload it to unstable.
Regards,
Vincent
On 06/08/2010 11:33, Javi Merino wrote:
> Hi Vincent, as 1.6.2 has been released, I have updated the svn to
> include it. The new version removes
> for_upstream__add_doc_url_in_example_files.patch and includes part of
> proposed_upstream__correct-zeroconf-doc . Does it make sense to keep
> this patch? Upstream has accepted part of it and I don't think the
> remaining part is meaningful.
>
> Please, release it when you can, it fixes an RC-bug. Regards,
> Javi (Vicho)
>
> On 30/07/10 18:49, Javi Merino wrote:
>> Hi, I've uploaded some changes to the svn in order to release mercurial
>> 1.6-3.
>>
>> I followed the instructions of #588671 since, as explained in [0],
>> --with quilt is not necessary in debian/rules, as is the build-depend on
>> quilt.
>>
>> [0] http://www.debian.org/doc/maint-guide/ch-dreq.en.html#s-rules
>>
>> In #586907, Artur says that the patch supplied by Wagner works, so I
>> have added it to the debian patches. Apparently, the bug is debian
>> specific[1].
>>
>> [1] http://mercurial.selenic.com/bts/issue2255
>>
>> I updated standards-version to 3.9.1.0, my only doubt is control
>> information files, which should be owned by root and be 644 or 755[2].
>> Do we have such files? If so, are they installed correctly?
>>
>> [2]
>> http://www.debian.org/doc/debian-policy/ch-files.html#s-permissions-owners
>>
>> Finally, I'd say we should suggest python-subversion and
>> python-celementtree, as we suggest them when they are needed (see
>> debian/patches/deb_specific__optional-dependencies). Why do we suggest
>> python-pygments?
>>
>> Okay, maybe this e-mail was too big, but please consider releasing
>> 1.6-3. Regards,
>> Javi (Vicho)
>>
>
>
--
Vincent Danjean GPG key ID 0x9D025E87 vdanjean@debian.org
GPG key fingerprint: FC95 08A6 854D DB48 4B9A 8A94 0BF7 7867 9D02 5E87
Unofficial packages: http://moais.imag.fr/membres/vincent.danjean/deb.html
APT repo: deb http://perso.debian.org/~vdanjean/debian unstable main
Reply to: