On 09/02/2016 08:58 PM, Sebastien Badia wrote:
> On Fri, Sep 02, 2016 at 04:43:58PM (+0200), Thomas Goirand wrote:
>> Package: gertty
>> Version: 1.3.1-1
>> Severity: important
>>
>> Hi,
>>
>> Version 1.3.1 is *very* slow to subscribe to projects. Version correct this
>> issue as well as many bug fixes. Please package 1.4.0 ASAP (version 1.3.1 is
>> anyway quite old).
>>
>> I've set this bug with Severity: important as the current version 1.3.1 is
>> hardly useable for me considering how slow it is to subscribe to projects,
>> and
>> I need to subscribe to hundreds of them.
>>
>> Cheers,
>>
>> Thomas Goirand (zigo)
>
> tags 836392 + pending
> thanks
>
> Hi Thomas,
>
> Thanks for the ping!
>
> In fact the 1.4.0 is ready since July, I've sent two ping to Clint (who upload
> in the archive previous version of this package), but no response. And indeed
> I
> have not sent an RFS :-/ (my bad…)
>
> Don't hesitate if you want to sponsor this package! Otherwise I'll sent a RFS.
>
> https://anonscm.debian.org/cgit/collab-maint/gertty.git
> https://mentors.debian.net/debian/pool/main/g/gertty/gertty_1.4.0-1.dsc
>
> Cheers,
>
> Seb
Seb,
Thanks for maintaining gertty. I've sponsored your package upload,
however, on the next upload, please correct this:
1/ debian/control
* Remove the version in python-all build-depends (this version is
satisfied even in old-stable...)
* Move python-alembic, python-dateutil, python-ply, python-requests,
python-six, python-sqlalchemy, python-urwid, python-voluptuous, and
python-yaml to Build-Depends-Indep instead of just Build-Depends. Unless
they are useful for the clean target (which I don't think they are),
then that's where they should be.
Note that pbr and setuptools *must* stay in build-depends, as they are
needed for the clean target of debian/rules.
* I don't think you need a Pre-Depends: ${misc:Pre-Depends} line.
* Does the package really need setuptools at runtime?
2/ debian/copyright
There's no mention of debian/* folder there. Maybe you want to add
yourself, no?
3/ Py3?
I'm surprised that the package doesn't have Python 3 support. If
upstream doesn't have Py3 support, maybe you should ping James E. Blair
about adding support for it, no?
Anyway, as always, thanks for your contribution to Debian,
Cheers,
Thomas Goirand (zigo)
