[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#810543: RFS: python-bond/1.4-1 [ITP]



control: tag -1 moreinfo
control: owner -1 !

On Sat, Jan 09, 2016 at 06:29:41PM +0100, Yuri D'Elia wrote:
> I am looking for a sponsor for my package "python-bond"
> 
>  http://mentors.debian.net/package/python-bond
> 
>  This is my first package and upload to python-modules.

ok, as this is in DPMT, and there is a team policy enforcing the git
repository needs to be inline with what is uploaded, I just ignored
mentors and went ahead cloning the git repo.

before all: the name of the repository needs to be the same as the
source, so it should be renamed to python-bond (note that there is also
hooks/post-receive to update, the kgb call hardcode (for some reasons,
it shouldn't be necessary at all) the name in the --module option)

1) it fails to build.  python(3)-nose and python(3)-setuptools-git
   are not in build-dep
2) vcs-field-uses-insecure-uri
3) duplicate-long-description
4) duplicate-short-description
5) the aboves are lintian tags; except for the first (which has been
introduced after your RFS) you should have noticed the other two, and
I wouldn't have expected to see them at a RFS stage; please remember to
run lintian in a more verbose than normal mode before asking a RFS
6) debian/docs: with this file you install the README only in
python-bond, I think you may want to install it also in python3-bond;
you can accomplish this by either overriding dh_installdocs and
re-calling it, or by renaming d/docs to d/python-bond.docs, and copying
it to d/python3-bond.docs
7) please bump Standards-Version to 3.9.7

-- 
regards,
                        Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540      .''`.
more about me:  http://mapreri.org                              : :'  :
Launchpad user: https://launchpad.net/~mapreri                  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-

Attachment: signature.asc
Description: PGP signature


Reply to: