RFS: mercurial-keyring/1.4.3-1 -- Mercurial Keyring Extension
Dear mentors, I am looking for a sponsor for my package "mercurial-keyring": * Package name: mercurial-keyring Version : 1.4.3-1 Upstream Author : Marcin Kasperski * URL : https://foss.heptapod.net/mercurial/mercurial_keyring * License : BSD-3-clause * Vcs : https://salsa.debian.org/python-team/packages/mercurial-keyring Section : python The source builds the following binary packages: mercurial-keyring - Mercurial Keyring Extension To access further information about this package, please visit the following URL: https://mentors.debian.net/package/mercurial-keyring/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/m/mercurial-keyring/mercurial-keyring_1.4.3-1.dsc Changes since the last upload: mercurial-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 upstream repo. * Update watchfile version. Regards, -- Christoph Mathys
RFS: mercurial-extension-utils/1.5.2-1 -- Contains functions for writing Mercurial extensions
Dear mentors, I am looking for a sponsor for my package "mercurial-extension-utils": * Package name: mercurial-extension-utils Version : 1.5.2-1 Upstream Author : Marcin Kasperski * URL : https://foss.heptapod.net/mercurial/mercurial-extension_utils * License : BSD-3-clause * Vcs : https://salsa.debian.org/python-team/packages/mercurial-extension-utils Section : python The source builds the following binary packages: python3-mercurial-extension-utils - Contains functions for writing Mercurial extensions To access further information about this package, please visit the following URL: https://mentors.debian.net/package/mercurial-extension-utils/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/m/mercurial-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 ] * Update Standards Version. * Update watchfile version. * Update homepage to upstream repo. . [ Debian Janitor ] * Update standards version to 4.6.0, no changes needed. Regards, -- Christoph Mathys
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 <erase...@gmail.com> 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 ‘mercurial_extension_utils’. Is that correct? Yes, this is the case. If the source is managed and released separately, with distinct release schedule and versions, yes there should be separate Debian packages for that. OK. Thanks for the clear and quick response! Christoph
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? Or is there another way? I doubt that this library will get a second user, but you never know... For reference: https://pypi.python.org/pypi/mercurial_extension_utils https://pypi.python.org/pypi/mercurial_keyring Thanks. Christoph
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 entry is missing from the upstream packages SOURCES.txt. Strange enough, on my ubuntu 12.04 box, running 'python setup.py sdist' does not add setup.cfg to SOURCES.txt. If an explicit 'python setup.py egg_info' is executed, this will add the missing entry. What is the proposed solution here? Patch SOURCES.txt? Nag upstream to update to a newer setuptools-package? Thanks! Christoph -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/50c79ed3.7060...@gmail.com
