Re: Request for joining DPMT
Hi, so 13. 6. 2020 v 12:18 odesílatel Nilesh Patra napsal: > Hi, > I'm interested in joining DPMT > welcome :) -- Best regards Ondřej Nový
Re: Request for joining DPMT
Pardon me, I've read and accept the policy: https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst#maintainership On Sat, 13 Jun 2020 at 15:32, Nilesh Patra wrote: > > > On Sat, 13 Jun 2020 at 15:31, Nilesh Patra wrote: > >> Hi, >> I'm interested in joining DPMT - I fix bugs for debian-python team and >> also help package a few modules. >> I've fixed RC bugs for DPMT packages before: #950050 and #952172 being >> recent ones. >> I also maintain several python packages under the debian med team >> >> I've a couple of more RC bug fixes for DPMT packages ready, and I wish to >> push it directly to the team now. >> Hence, I will be grateful if I'm granted access. >> > > I forgot to mention this: my salsa username is: gi-boi-guest > > Regards >
Re: Request for joining DPMT
On Sat, 13 Jun 2020 at 15:31, Nilesh Patra wrote: > Hi, > I'm interested in joining DPMT - I fix bugs for debian-python team and > also help package a few modules. > I've fixed RC bugs for DPMT packages before: #950050 and #952172 being > recent ones. > I also maintain several python packages under the debian med team > > I've a couple of more RC bug fixes for DPMT packages ready, and I wish to > push it directly to the team now. > Hence, I will be grateful if I'm granted access. > I forgot to mention this: my salsa username is: gi-boi-guest Regards
Request for joining DPMT
Hi, I'm interested in joining DPMT - I fix bugs for debian-python team and also help package a few modules. I've fixed RC bugs for DPMT packages before: #950050 and #952172 being recent ones. I also maintain several python packages under the debian med team I've a couple of more RC bug fixes for DPMT packages ready, and I wish to push it directly to the team now. Hence, I will be grateful if I'm granted access. Kind regards Nilesh
Request for joining DPMT/PAPT
Hi, I'm a Google Summer of Code student working on debile[1][2][3] with Sylvestre Ledru. As part of my work during the summer, I will have to package several python modules and applications (at least [4] and [5]). I am clemux-guest on alioth, and I am submitting the requests to join DPMT and PAPT alioth projects right now. I have already joined debian-python@lists.d.o Regards, --- Clément [1] http://debile.debian.net/ [2] http://france.debian.net/evenements/minidebconf2014/debile-presentation.pdf [3] https://wiki.debian.org/SummerOfCode2014/StudentApplications/ClementSchreiner [4] https://github.com/paultag/ricky [5] https://github.com/paultag/loofah -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87egyu14og@mux.me
Re: Request for joining DPMT
* Michael Helmling , 2013-01-16, 22:41: Please make sure that the .cpp file is rebuilt from source. ok, thanks for this hint - because of that I noticed that actually the pyx- and pxd-sources did not get included into the source tarball by `setup.py sdist` for whatever reason. I fixed this and put a "rm src/taglib.cpp" in debian/rules and an "extend-diff-ignore"-line for taglib.cpp in debian/source/options. Oops! Remember, kids: this is why you should always rebuild stuff from source. :) The package FTBFS here: | + python3.2 setup.py install --install-layout=deb --root=debian/tmp | Traceback (most recent call last): | File "setup.py", line 12, in | from setuptools import setup | ImportError: No module named setuptools This still happens. Additionally, I have renamed pyprinttags to pyprinttags3 for the python3 version. I hacked something into debian/rules to also rename the man page for that package; please let me know if there's a better way to achieve that. If the two scripts have exactly the same functionality, and they only differ in implementation language, then they probably should be offered under the same name, managed by alternatives. I have uploaded the new version 0.3.4 to mentors, hopefully it will show up there soon. Yup, it's here: http://mentors.debian.net/debian/pool/main/p/pytaglib/pytaglib_0.3.4-1.dsc You want python(3)-all-dev instead of python(3)-dev in Build-Depends. Also, the build-dependency python3-(all-)dev should be versioned. Lintian emits: W: pytaglib source: out-of-date-standards-version 3.9.3 (current is 3.9.4) Lintian4python emits: i: python3-taglib: versioned-python-shebang usr/bin/pyprinttags3 /usr/bin/python3.2 Shouldn't debian/watch use pypi.python.org? Anyway, I've just added you to the team. Feel free to inject the package to the team's repository. Unfortunately, I won't have time for further reviews of this package; hopefully someone else will step forward. Good luck! :) -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130117120040.ga9...@jwilk.net
Re: Re: Request for joining DPMT
Hi Jakub,
many thanks for your thorough review of the package.
Distribution in the changelog should be experimental, not unstable (as
the package cannot be currently built within unstable).
Missing ")" in the changelog.
Pet peeve: I'd use "debhelper (>= 8)" instead of "debhelper (>= 8.0.0)".
Typo in debian/control: Pytho2 -> "Python2".
What's up with debian/rules.working? :)
You declare "X-Python3-Version: >= 3.0", but this:
return "File('{}')".format(self.path)
requires Python 3.1 or later. (Admittedly it doesn't matter at all in
practice, because Python 3.0 has been never in Debian.)
debian/copyright says "License: GPL-3+", but the following text
doesn't anything about later versions... So is it version 3 only? The
binary package names should be: python-taglib, python3-taglib. See
Python Policy §2.2 for details.
Up to here It was easy ...
Please make sure that the .cpp file is rebuilt from source.
ok, thanks for this hint - because of that I noticed that actually the
pyx- and pxd-sources did not get included into the source tarball by
`setup.py sdist` for whatever reason. I fixed this and put a "rm
src/taglib.cpp" in debian/rules and an "extend-diff-ignore"-line for
taglib.cpp in debian/source/options.
The package FTBFS here:
| + python3.2 setup.py install --install-layout=deb --root=debian/tmp
| Traceback (most recent call last):
| File "setup.py", line 12, in
| from setuptools import setup
| ImportError: No module named setuptools
It still FTBFS even when I added python3-setuptools to Build-Depends:
| + python3.2 setup.py install --install-layout=deb --root=debian/tmp
| Traceback (most recent call last):
| File "setup.py", line 36, in
| long_description=readme(),
| File "setup.py", line 30, in readme
| return rm.read()
| File "/usr/lib/python3.2/encodings/ascii.py", line 26, in decode
| return codecs.ascii_decode(input, self.errors)[0]
| UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 9:
ordinal not in range(128)
After I worked around all the build problem, I installed
python-pytaglib and all its dependencies. Unfortunately, it didn't start:
| $ pyprinttags
| Traceback (most recent call last):
| File "/usr/bin/pyprinttags", line 5, in
| from pkg_resources import load_entry_point
| ImportError: No module named pkg_resources
So I installed python-pkg-resources, and then I got:
| $ pyprinttags
| Traceback (most recent call last):
| File "/usr/bin/pyprinttags", line 5, in
| from pkg_resources import load_entry_point
| File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 2711, in
| parse_requirements(__requires__), Environment()
| File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 584, in
resolve
| raise DistributionNotFound(req)
| pkg_resources.DistributionNotFound: cython>=0.16
Wait, why is Cython needed at runtime at all?! But upgrading Cython to
0.17 didn't make it work either:
| $ pyprinttags
| Traceback (most recent call last):
| File "/usr/bin/pyprinttags", line 9, in
| load_entry_point('pytaglib==0.3.2', 'console_scripts', 'pyprinttags')()
| File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 337, in
load_entry_point
| return get_distribution(dist).load_entry_point(group, name)
| File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 2279, in
load_entry_point
| return ep.load()
| File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 1989, in load
| entry = __import__(self.module_name, globals(),globals(), ['__name__'])
| ImportError: No module named pyprinttags
Now I'm at a loss. :)
Sorry, the pyprinttags module was also missing in the installed files.
This is fixed upstream now.
Additionally, I have renamed pyprinttags to pyprinttags3 for the python3
version. I hacked something into debian/rules to also rename the man
page for that package; please let me know if there's a better way to
achieve that.
I have uploaded the new version 0.3.3 to mentors, hopefully it will show
up there soon.
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/50f71a7b.4080...@mathematik.uni-kl.de
Re: Re: Request for joining DPMT
Hi Jakub,
many thanks for your thorough review of the package.
Distribution in the changelog should be experimental, not unstable (as
the package cannot be currently built within unstable).
Missing ")" in the changelog.
Pet peeve: I'd use "debhelper (>= 8)" instead of "debhelper (>= 8.0.0)".
Typo in debian/control: Pytho2 -> "Python2".
What's up with debian/rules.working?
You declare "X-Python3-Version: >= 3.0", but this:
return "File('{}')".format(self.path)
requires Python 3.1 or later. (Admittedly it doesn't matter at all in
practice, because Python 3.0 has been never in Debian.)
debian/copyright says "License: GPL-3+", but the following text
doesn't anything about later versions... So is it version 3 only? The
binary package names should be: python-taglib, python3-taglib. See
Python Policy §2.2 for details.
Up to here It was easy ...
Please make sure that the .cpp file is rebuilt from source.
ok, thanks for this hint - because of that I noticed that actually the
pyx- and pxd-sources did not get included into the source tarball by
`setup.py sdist` for whatever reason. I fixed this and put a "rm
src/taglib.cpp" in debian/rules and an "extend-diff-ignore"-line for
taglib.cpp in debian/source/options.
The package FTBFS here:
| + python3.2 setup.py install --install-layout=deb --root=debian/tmp
| Traceback (most recent call last):
| File "setup.py", line 12, in
| from setuptools import setup
| ImportError: No module named setuptools
It still FTBFS even when I added python3-setuptools to Build-Depends:
| + python3.2 setup.py install --install-layout=deb --root=debian/tmp
| Traceback (most recent call last):
| File "setup.py", line 36, in
| long_description=readme(),
| File "setup.py", line 30, in readme
| return rm.read()
| File "/usr/lib/python3.2/encodings/ascii.py", line 26, in decode
| return codecs.ascii_decode(input, self.errors)[0]
| UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position
9: ordinal not in range(128)
After I worked around all the build problem, I installed
python-pytaglib and all its dependencies. Unfortunately, it didn't start:
| $ pyprinttags
| Traceback (most recent call last):
| File "/usr/bin/pyprinttags", line 5, in
| from pkg_resources import load_entry_point
| ImportError: No module named pkg_resources
So I installed python-pkg-resources, and then I got:
| $ pyprinttags
| Traceback (most recent call last):
| File "/usr/bin/pyprinttags", line 5, in
| from pkg_resources import load_entry_point
| File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line
2711, in
| parse_requirements(__requires__), Environment()
| File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line
584, in resolve
| raise DistributionNotFound(req)
| pkg_resources.DistributionNotFound: cython>=0.16
Wait, why is Cython needed at runtime at all?! But upgrading Cython to
0.17 didn't make it work either:
| $ pyprinttags
| Traceback (most recent call last):
| File "/usr/bin/pyprinttags", line 9, in
| load_entry_point('pytaglib==0.3.2', 'console_scripts',
'pyprinttags')()
| File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line
337, in load_entry_point
| return get_distribution(dist).load_entry_point(group, name)
| File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line
2279, in load_entry_point
| return ep.load()
| File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line
1989, in load
| entry = __import__(self.module_name, globals(),globals(),
['__name__'])
| ImportError: No module named pyprinttags
Now I'm at a loss.
Sorry, the pyprinttags module was also missing in the installed files.
This is fixed upstream now. I have also added dependencies for the
pkg-resources.
Additionally, I have renamed pyprinttags to pyprinttags3 for the python3
version. I hacked something into debian/rules to also rename the man
page for that package; please let me know if there's a better way to
achieve that.
I have uploaded the new version 0.3.4 to mentors, hopefully it will show
up there soon.
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/50f71e8e.3060...@posteo.de
Re: Request for joining DPMT
* Michael Helmling , 2013-01-13, 11:42:
I'd like to join the debian python modules team, mainly in order to
help getting pytaglib (https://mentors.debian.net/package/pytaglib)
Link to .dsc for the lazy:
http://mentors.debian.net/debian/pool/main/p/pytaglib/pytaglib_0.3.2-1.dsc
Distribution in the changelog should be experimental, not unstable (as
the package cannot be currently built within unstable).
Missing ")" in the changelog.
Pet peeve: I'd use "debhelper (>= 8)" instead of "debhelper (>= 8.0.0)".
Typo in debian/control: Pytho2 -> "Python2".
What's up with debian/rules.working? :)
You declare "X-Python3-Version: >= 3.0", but this:
return "File('{}')".format(self.path)
requires Python 3.1 or later. (Admittedly it doesn't matter at all in
practice, because Python 3.0 has been never in Debian.)
debian/copyright says "License: GPL-3+", but the following text doesn't
anything about later versions... So is it version 3 only?
The binary package names should be: python-taglib, python3-taglib. See
Python Policy §2.2 for details.
Please make sure that the .cpp file is rebuilt from source.
The package FTBFS here:
| + python3.2 setup.py install --install-layout=deb --root=debian/tmp
| Traceback (most recent call last):
| File "setup.py", line 12, in
| from setuptools import setup
| ImportError: No module named setuptools
It still FTBFS even when I added python3-setuptools to Build-Depends:
| + python3.2 setup.py install --install-layout=deb --root=debian/tmp
| Traceback (most recent call last):
| File "setup.py", line 36, in
| long_description=readme(),
| File "setup.py", line 30, in readme
| return rm.read()
| File "/usr/lib/python3.2/encodings/ascii.py", line 26, in decode
| return codecs.ascii_decode(input, self.errors)[0]
| UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 9:
ordinal not in range(128)
After I worked around all the build problem, I installed python-pytaglib
and all its dependencies. Unfortunately, it didn't start:
| $ pyprinttags
| Traceback (most recent call last):
| File "/usr/bin/pyprinttags", line 5, in
| from pkg_resources import load_entry_point
| ImportError: No module named pkg_resources
So I installed python-pkg-resources, and then I got:
| $ pyprinttags
| Traceback (most recent call last):
| File "/usr/bin/pyprinttags", line 5, in
| from pkg_resources import load_entry_point
| File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 2711, in
| parse_requirements(__requires__), Environment()
| File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 584, in
resolve
| raise DistributionNotFound(req)
| pkg_resources.DistributionNotFound: cython>=0.16
Wait, why is Cython needed at runtime at all?! But upgrading Cython to
0.17 didn't make it work either:
| $ pyprinttags
| Traceback (most recent call last):
| File "/usr/bin/pyprinttags", line 9, in
| load_entry_point('pytaglib==0.3.2', 'console_scripts', 'pyprinttags')()
| File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 337, in
load_entry_point
| return get_distribution(dist).load_entry_point(group, name)
| File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 2279, in
load_entry_point
| return ep.load()
| File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 1989, in load
| entry = __import__(self.module_name, globals(),globals(), ['__name__'])
| ImportError: No module named pyprinttags
Now I'm at a loss. :)
I would be very glad about a positive answer to this request.
Once the major problems are fixed, I would be happy to add you to the
team.
--
Jakub Wilk
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130113142346.ga6...@jwilk.net
Request for joining DPMT
Hi Debian-Python Team, I'd like to join the debian python modules team, mainly in order to help getting pytaglib (https://mentors.debian.net/package/pytaglib) into debian, a small (<200 SLOC) but powerful binding to the taglib audio metadata library. Using the new property interface introduced in taglib 1.8, users of pytaglib can read and write arbitrary tags (not only the common ones like "title", "artist", ...) completely format-transparent. Also, to my knowledge it's the only taglib/python binding supporting python3. I would be very glad about a positive answer to this request. My alioth name is "supermihi-guest". Regards, Michael -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/50f28f96.3070...@posteo.de
