Bug#946395: RFS: mercurial-extension-utils/1.5.0-1 -- Contains functions for writing Mercurial extensions

[Andrej Shadura <andrew@shadura.me>]

Hi,

On Fri, 3 Jan 2020 at 08:47, Christoph Mathys <eraserix@gmail.com> wrote:
>
> > I think I can upload both packages with both Python 2 and 3 (easy) and
> > then we can wait for Mercurial to switch over and drop Python 2. I’ve
> > done that with hgsubversion already.
>
> I can do this as well with mercurial-keyring, if that is an option. I
> was under the impression that you need a "python[3]-" prefix to do that,
> but apparently not.

Well, you do need both ${python:Depends} and ${python3:Depends}, but
there’s no need to have the package prefixed.

> > Christoph, by the way, how about moving these two packages into DPMT?
> > They already have a Git repo for an ancient version of
> > mercurial-keyring (which I replaced with yours), I could move
> > extension-utils there as well (I have a Git history locally).
>
> I guess this would be a good thing. I started playing around with
> git-buildpackage anyways, but on github:
>
> https://github.com/eraserix/mercurial-keyring
>
> I'll create an updated version of mercurial-keyring with both python2 and 3.

You may want to have a look at these:

 * https://salsa.debian.org/python-team/modules/mercurial-keyring
 * https://salsa.debian.org/python-team/modules/mercurial-extension-utils

Can I go ahead with m-e-utils and upload in that shape?

-- 
Cheers,
  Andrej