Package: sponsorship-requests
Severity: wishlist
X-Debbugs-CC: debian-python@lists.debian.org
Dear mentors,
I am looking for a sponsor for my package yp-svipc
* Package name: yp-svipc
Version : 0.13-1
Upstream Author : Matthieu Bec
* URL :
On Thursday, April 12, 2012 08:30:41 AM Barry Warsaw wrote:
Hi Paul,
On Apr 12, 2012, at 02:09 AM, Paul Elliott wrote:
A recent review of my package asked me to consider making a python3
version.
Excellent! One more down the road to Python 3 world domination. :)
But the response below
Hi Paul (2012.04.18_10:09:30_+0200)
I am not a expert python packager. I am dubious about a bunch of cargo cult
packagers all writing seperate but similar debian/rules complications.
Indeed, it's messy and far from ideal.
Why can not some expert that really know what she is doing write the
[Paul Elliott, 2012-04-18]
I am not a expert python packager. I am dubious about a bunch of cargo cult
packagers all writing seperate but similar debian/rules complications.
It seems like one is creating a lot of debugging/maintainance problems.
Why can not some expert that really know
* Jakub Wilk jw...@debian.org, 2012-04-16, 23:35:
* Markus Wanner mar...@bluegap.ch, 2012-04-16, 07:45:
http://mentors.debian.net/debian/pool/main/d/dparser/dparser_1.26-1.dsc
One more thing:
pyversions -vr debian/control
could be (more conventionally and more succinctly) written as:
On Apr 18, 2012, at 03:09 AM, Paul Elliott wrote:
I am not a expert python packager. I am dubious about a bunch of cargo cult
packagers all writing seperate but similar debian/rules complications.
That's why I wrote the style guide; hopefully at least we'll converge on one
set of
On Wednesday, April 18, 2012 10:12:24 AM Barry Warsaw wrote:
On Apr 18, 2012, at 03:09 AM, Paul Elliott wrote:
I am not a expert python packager. I am dubious about a bunch of cargo
cult packagers all writing seperate but similar debian/rules
complications.
That's why I wrote the style
On Wednesday, April 18, 2012 10:35:04 AM Paul Elliott wrote:
On Wednesday, April 18, 2012 10:12:24 AM Barry Warsaw wrote:
On Apr 18, 2012, at 03:09 AM, Paul Elliott wrote:
I am not a expert python packager. I am dubious about a bunch of cargo
cult packagers all writing seperate but similar
There are some warnings while running tests:
build/lib/dateutil/tz.py:910: ResourceWarning: unclosed file _io.BufferedReader
name='/usr/share/zoneinfo/EST5EDT'
build/lib/dateutil/tz.py:910: ResourceWarning: unclosed file _io.BufferedReader
name='/usr/share/zoneinfo/UTC'
On 18 April 2012 18:03, Jakub Wilk jw...@debian.org wrote:
But anyway, I bumped timestamp in the changelog, built, signed and uploaded
the package. Thanks.
Thanks Jakub, and thanks for taking the time to go through all these
things with me.
Thomas
--
To UNSUBSCRIBE, email to
(I don't intend to sponsor this package.)
* Thibaut Paumard paum...@users.sourceforge.net, 2012-04-18, 09:32:
http://mentors.debian.net/debian/pool/main/y/yp-svipc/yp-svipc_0.13-1.dsc
Lintian emits:
P: yp-svipc source: debian-control-has-unusual-field-spacing line 5
The following files have
On Wednesday, April 18, 2012 02:35:20 PM Paul Elliott wrote:
On Wednesday, April 18, 2012 10:49:34 AM Scott Kitterman wrote:
Alternately you could invest a little time in understanding what Barry's
written up and build both sets of binaries from one source. This is the
usual method.
The
On Wednesday, April 18, 2012 02:46:33 PM Scott Kitterman wrote:
No. You'd need overrides for a python3 only source package as well. The
fundamental problem is debhelper doesn't know about building for python3.
That doesn't change no matter how many source packages you split it up
into.
On Wednesday, April 18, 2012 03:09:35 PM Paul Elliott wrote:
On Wednesday, April 18, 2012 02:46:33 PM Scott Kitterman wrote:
No. You'd need overrides for a python3 only source package as well. The
fundamental problem is debhelper doesn't know about building for python3.
That doesn't
On Apr 18, 2012, at 03:09 PM, Paul Elliott wrote:
Nobody thinks python3 is important enough to have a debhelper infrastructure?
I wouldn't say that. I'd say that the higher level tools are simply lagging
behind demand. The low-level tools are available and won't significantly
change. As Scott
Hi,
Le 18/04/12 21:03, Jakub Wilk a écrit :
(I don't intend to sponsor this package.)
Thanks for the comments nevertheless. I've fixed them all.
In the meantime, upstream succeeded in porting this extension to python
3, so I've updated the package accordingly:
16 matches
Mail list logo
