Hugo Lefeuvre writes:
> I'm currently packaging python-slugify[0], a Python application for
> slugifying unicode strings.
Thank you for considering the issues and asking for advice.
> Like here[1] upstream decided to write everything as a python module
> with an entry script placed in /usr/bin
Package: wnpp
Severity: wishlist
Control: block 810629 by -1
* Package name: python-pypandoc
Version : 1.1.3
Upstream Author : Juho Vepsäläinen
* URL : https://github.com/bebraw/pypandoc
* License : MIT
Programming Lang: Python
Description : Thin Python
Package: wnpp
Severity: wishlist
Control: block 810629 by -1
* Package name: python-bugzilla
Version : 1.2.2
Upstream Author : Cole Robinson
* URL : https://github.com/python-bugzilla/python-bugzilla
* License : GPL-2
Programming Lang: Python
Description
Package: wnpp
Severity: wishlist
Control: block 810629 by -1
* Package name: python-pytz
Version : 2016.4
Upstream Author : Stuart Bishop
* URL : http://pythonhosted.org/pytz
* License : MIT
Programming Lang: Python
Description : World timezone definitio
Package: wnpp
Severity: wishlist
Control: block 810629 by -1
* Package name: python-offtrac
Version : 0.1.0
Upstream Author : Jesse Keating
* URL : http://fedorahosted.org/offtrac
* License : GPL-2+
Programming Lang: Python
Description : Trac xmlrpc libr
Package: wnpp
Severity: wishlist
Control: block 810629 by -1
* Package name: python-twiggy
Version : 0.4.7
Upstream Author : Pete Fein
* URL : http://twiggy.wearpants.org
* License : BSD
Programming Lang: Python
Description : a Pythonic logger
Twiggy is
Hi all !
I'm currently packaging python-slugify[0], a Python application for
slugifying unicode strings. Like here[1] upstream decided to write
everything as a python module with an entry script placed in /usr/bin
that calls main(). So we can consider python-slugify as both an application
and a l
On 06/21/2016 03:35 AM, Ben Finney wrote:
> My understanding is that renaming a source package is rather more
> disruptive than renaming a binary package, is that right?
To my experience, renaming a source package is painless. The pain used
to be for FTP masters, but now even that is automated now
On Jun 21, 2016, at 10:18 AM, Piotr Ożarowski wrote:
>I'd simply create new source package with new binary packages and remove
>src:pep8 even from Stretch (once all rev. dependencies use new package).
Yep, I'm leaning toward this, or at least creating a new source package for
pycodestyle. I thin
[Barry Warsaw, 2016-06-20]
> I think we eventually want to rename Source:pep8 to Source:pycodestyle, as
> well as Package:pep8, Package:python-pep8, and Package:python3-pep8. I
> suppose we could at least keep the source package name unchanged and
> transition to the new binary package names.
I'd
10 matches
Mail list logo