Bug#807333: ITP: pilkit -- Utilities and processors built for, and on top of PIL

2015-12-07 Thread Michael Fladischer
Package: wnpp Severity: wishlist Owner: Michael Fladischer -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 * Package name: pilkit Version : 1.1.13 Upstream Author : Matthew Tretter * URL :

Bug#807309: ITP: montage-wrapper -- Python wrapper for the Montage mosaicking toolkit

2015-12-07 Thread Ole Streicher
Package: wnpp Owner: Ole Streicher Severity: wishlist X-Debbugs-Cc: debian-de...@lists.debian.org,debian-as...@lists.debian.org,debian-python@lists.debian.org * Package name: montage-wrapper Version : 0.9.8 Upstream Author : Thomas Robitaille * URL

Re: Rebuild for packages with entry points?

2015-12-07 Thread Simon McVittie
On 07/12/15 19:00, Barry Warsaw wrote: > On Dec 07, 2015, at 10:22 AM, Nikolaus Rath wrote: >> It'd be nice to have https://bitbucket.org/pypa/setuptools/issues/443/ >> fixed in stretch. > > I'm also not sure how many packages it affects in practice. We could also let > rebuilds be bug-driven.

Re: Rebuild for packages with entry points?

2015-12-07 Thread Barry Warsaw
On Dec 07, 2015, at 10:22 AM, Nikolaus Rath wrote: >Would it make sense to do a no-change rebuild for all Python packages >that use setuptool's entry point functionality? > >It'd be nice to have https://bitbucket.org/pypa/setuptools/issues/443/ >fixed in stretch. I believe most packages will see

Rebuild for packages with entry points?

2015-12-07 Thread Nikolaus Rath
Hello, Would it make sense to do a no-change rebuild for all Python packages that use setuptool's entry point functionality? It'd be nice to have https://bitbucket.org/pypa/setuptools/issues/443/ fixed in stretch. I believe most packages will see new releases anyway (and thus get the change),