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
‘mercurial_extensi
Christoph Mathys writes:
> I'm the package maintainer of mercurial-keyring, a keyring extension
> for mercurial.
Thank you for maintaining this in Debian.
> Upstream has split some of the functionality of mercurial-keyring into
> a separate python library and pip package (mercurial_extension_ut
Package: sponsorship-requests
Severity: wishlist
X-Debbugs-CC: debian-python@lists.debian.org
Dear mentors,
I am looking for a sponsor for my package "grip"
* Package name: grip
Version : 4.1.0-1
Upstream Author : Joe Esposito
* URL : https://github.com/joeyespo/grip
Package: wnpp
Severity: wishlist
* Package name: python-sframe
Version : 1.8.4
Upstream Author : Dato, Inc.
* URL : https://github.com/dato-code/SFrame
* License : BSD
Programming Lang: C++, Python
Description : scalable tabular (SFrame, SArray) and grap
Hi,
The Style Guide for Packaging Python Libraries[1] states that in cases
like this, one should package the library for both Python 2 and 3,
creating a third package that contains the executable. As this package
is indeed intended to be used as a CLI application (as its description
says), I've fo
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?
Package: wnpp
Version: N/A; reported 2016-04-04
Severity: wishlist
X-Debbugs-CC: debian-de...@lists.debian.org, debian-python@lists.debian.org
Package name: asynctest
Version: 0.6.0
Upstream Author: Martin Richard
URL: https://github.com/Martiusweb/asynctest
License
Hi Brian,
On Mon, Apr 04, 2016 at 04:35:52PM +1000, Brian May wrote:
> Seems this isn't as easy as I hoped.
>
> brian@prune:~/tree/debian/python-modules/django-guardian$ git-dpm
> checkout-patched
> grep: warning: GREP_OPTIONS is deprecated; please use an alias or script
> grep: warning: GREP_OPT
On Apr 04, 2016, at 05:33 PM, Brian May wrote:
>Ok, so as I expected, integrating a new upstream release resolved this
>issue for me. git-dpm import-new-upstream left me in the patched
>directory, and I was able to drop the last patch and then run git-dpm
>update-patches.
When it works, it's magi
Brian May writes:
> brian@prune:~/tree/debian/python-modules/django-guardian$ git-dpm
> update-patches
> grep: warning: GREP_OPTIONS is deprecated; please use an alias or script
> grep: warning: GREP_OPTIONS is deprecated; please use an alias or script
> git-dpm: Calling merge-patched-into-debia
10 matches
Mail list logo