RFS: mercurial-keyring/1.4.3-1 -- Mercurial Keyring Extension

ial-keyring (1.4.3-1) unstable; urgency=medium . [ Ondřej Nový ] * d/control: Update Maintainer field with new Debian Python Team contact address. . [ Christoph Mathys ] * New upstream release (Closes: #988795). * Update std version to 4.6.0. * Update homepage to upstre

RFS: mercurial-extension-utils/1.5.2-1 -- Contains functions for writing Mercurial extensions

rial-extension-utils/mercurial-extension-utils_1.5.2-1.dsc Changes since the last upload: mercurial-extension-utils (1.5.2-1) unstable; urgency=medium . [ Ondřej Nový ] * d/control: Update Maintainer field with new Debian Python Team contact address. . [ Christoph Mathys ] * Upda

Request to join DPMT

Hi, I'd like to join DPMT to maintain my Python modules mercurial-keyring and mercurial-keyring-utils. I've read and accept policy.rst. My salsa login is: eraserix-guest

Re: Upstream has split a package in two -> new Debian package?

On 05.04.2016 03:51, Ben Finney wrote: Christoph Mathys writes: Upstream has split some of the functionality of mercurial-keyring into a separate python library and pip package (mercurial_extension_utils). That seems to imply there will be separate releases and versions for

Upstream has split a package in two -> new Debian package?

Hi! I'm the package maintainer of mercurial-keyring, a keyring extension for mercurial. Upstream has split some of the functionality of mercurial-keyring into a separate python library and pip package (mercurial_extension_utils). Do I need to create and upload a new package for this library?

Missing entry in SOURCES.txt

I try to package mercurial-keyring. However, if I build the binary package and then try to build the source package, this process fails because SOURCES.txt has been modified by the binary package build. Apparently, dh_python2 (setuptools) creates an entry in SOURCES.txt for setup.cfg. This ent