As other folks already mentioned, you do not use CC: you already use
X-Debbugs-CC. In this particular case, email with bug number got
filtered-out as duplicate in my setup.
Ok. The next time I will use just X-Debbugs-CC
[2018-12-31 00:16] eamanu15 <emmanuelarias30@gmail.com>
> I am looking for a sponsor for my package "pygithub"
>
> * Package name : pygithub
> Version : 1.43.3-1
> Upstream Author : Adam Dangoor <adamdangoor@gmail.com>
> Vincent Jacques <vincent@vincent-jacques.net>
> Jeremy Phelps <jphelps@linuxfoundation.org>
> * URL : https://pypi.python.org/pypi/PyGithub
> * License : LGPL-3+
> Section : python
>
> It builds those binary packages:
>
> python-github - Access to full Github API v3 from Python2
> python3-github - Access the full Github API v3 from Python3
Looks fine, but I do not understand following line in `debian/rules':
rm -rfv debian/python3-github/usr/lib/python3.*
What is removed and why same statement it is not needed for python2
version? Comment in `debian/rules' would be nice.
Really I don't remember and I don't sit down in front of own system right now.
And some very minor suggestions:
* Standards-Version slightly outdated
* debhelper-compat style reduces redundancy
* Probably F-variables could be used to avoid repetition in
binary package descriptions? (See dpkg-substvars(5))
Thanks for your suggestions I will work in it.
I do not know habits of Python Modules Team, but would not it be more
apporiate for this packages to be sponsored by DD from team? I can check
basic things, but I do not know whole picture, like transitions or
reverse dependencies.
Yes, I'll keep looking.
PS. I am glad to see that pygithub finally moved under aegis of
Python Modules Team.