[PING] Re: Bug#669209: RFS: yp-svipc/0.13-1 [ITP] -- System V InterProcess Communication for Python/Yorick

2012-06-12 Thread Thibaut Paumard
Hi guys,

it's been two months since I initially posted this RFS, and the release
is getting nearer...

Regards, Thibaut.

Le 26/05/12 11:05, Thibaut Paumard a écrit :
> Le 08/05/12 09:43, Thibaut Paumard a écrit :
>> Hi guys,
> 
>> I'd love it if someone could have a look at this package: 
>> http://mentors.debian.net/package/yp-svipc
>> dget -x
http://mentors.debian.net/debian/pool/main/y/yp-svipc/yp-svipc_0.14-1.dsc
> 
>> It gives access to the system V interprocess communication
>> mechanisms to the [1]yorick and python (2-3) interpreters. With
>> this mechanisms, it becomes possible to do multi-process parallel
>> scripting and to develop mixed yorick/python applications. [1]
>> http://packages.debian.org/sid/yorick
> 
>> The Yorick plug-in can optionally be used for faster computations
>> by YAO, a scientific software already in Debian: 
>> http://packages.debian.org/sid/yorick-yao
> 
>> Since the initial ITP, I've worked with upstream to port the
>> software to python 3 and to fix a couple of bugs.
> 
>> Best regards, Thibaut.
> 
> 
>> Le 18/04/12 09:32, Thibaut Paumard a écrit :
>>> 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 : 
>>> https://github.com/frigaut/yorick-svipc/ * License :
>>> GPL-3 Section : Python, Science Programming Lang: C,
>>> Yorick, Python Description : System V InterProcess
>>> Communication for Python/Yorick ITP :
>>> http://bugs.debian.org/668841
> 
>>> It builds those binary packages:
> 
>>> python-svipc - interprocess communication (shared memory...) for 
>>> Python yorick-svipc - interprocess communication (shared
>>> memory...) for Yorick
> 
>>> To access further information about this package, please visit
>>> the following URL: http://mentors.debian.net/package/yp-svipc
> 
>>> Alternatively, one can download the package with dget using this 
>>> command: dget -x 
>>> http://mentors.debian.net/debian/pool/main/y/yp-svipc/yp-svipc_0.13-1.dsc
> 
>>>  When the two packages are installed, they can be tested with: - 
>>> yorick-only multiprocess computing: yorick -i 
>>> /usr/share/doc/yorick-svipc/examples/timing-demo.i -
>>> yorick/python communication: yorick -i 
>>> /usr/share/doc/yorick-svipc/examples/ping.i
> 
>>> I have not been able to make it work under python3 so far (on 
>>> Linux: it works on a Mac).
> 
>>> Regards, Thibaut Paumard.
> 
> 
> 
> 
> 
> 
> 
> 
> 




signature.asc
Description: OpenPGP digital signature


Re: RFS: numpydoc/0.4-1 [RFP/ITP 559916]

2012-06-12 Thread Jakub Wilk

(I don't intend to sponsor this package.)

* Denis Laxalde , 2012-06-11, 20:51:

 dget -x 
http://mentors.debian.net/debian/pool/main/n/numpydoc/numpydoc_0.4-1.dsc


Minor nitpick: I'd use "debhelper (>= 8)" instead of "debhelper (>= 
8.0.0)" in Build-Depends. (Sorry, it's my pet peeve!)


Upstream provides some tests, please run the at build time.

Policy-compliant package name would be "python-numpydoc", but that could 
be easily confused with "python-numpy-doc". So I agree with your 
assessment: "python-numpydoc-sphinx" is a better for the binary package.


--
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/20120612121344.ga1...@jwilk.net



Re: RFR: cairosvg -- SVG converter based on Cairo

2012-06-12 Thread Michael Fladischer
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Taking this off mentors.

On 06/11/2012 12:12 PM, Jakub Wilk wrote:
> The dependencies are generated by dh_python{2,3}, so it's a matter
> of fixing shebangs before they are called, isn't it?
> 
> This may help: 
> https://lists.debian.org/debian-python/2011/03/msg00077.html

Thanks, that helped a lot. Now both the shebang lines and the
dependencies are correct.

> One more thing: Vcs-* fields are broken:
> 
> $ svn ls -v $(grep-dctrl -ns Vcs-Svn '' < debian/control) svn: URL
> 'svn://svn.debian.org/python-modules/packages/cairosvg/trunk' 
> non-existent in that revision

I used an incorrect directory in the repo. It has been renamed.

Cheers,
- -- 
Michael Fladischer 
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk/XPdgACgkQeJ3z1zFMUGajygCeMyIt27d7Nw1OE4dxP3K4K4bw
4KAAoJOvRVrs1hwbnrt599BD/N4tCMiE
=ZeTk
-END PGP SIGNATURE-


-- 
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/4fd73dd9.1090...@fladi.at



Re: RFS: numpydoc/0.4-1 [RFP/ITP 559916]

2012-06-12 Thread Yaroslav Halchenko

On Tue, 12 Jun 2012, Jakub Wilk wrote:
> Policy-compliant package name would be "python-numpydoc", but that
> could be easily confused with "python-numpy-doc". So I agree with
> your assessment: "python-numpydoc-sphinx" is a better for the binary
> package.

if it wouldn't be "convention compliant" anyways -- may be
python-sphinx-numpydoc?  there is already python-sphinx-issuetracker ...
actually it got renamed later on into python-sphinxcontrib.issuetracker.
It might be worth checking with numpydoc people if they do not
have plans on placing numpydoc under sphinxcontrib namespace

just my .1 cents

-- 
Yaroslav O. Halchenko
Postdoctoral Fellow,   Department of Psychological and Brain Sciences
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834   Fax: +1 (603) 646-1419
WWW:   http://www.linkedin.com/in/yarik


-- 
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/20120612132716.gw15...@onerussian.com



Re: RFS: numpydoc/0.4-1 [RFP/ITP 559916]

2012-06-12 Thread Denis Laxalde

Jakub Wilk wrote:

 dget -x 
http://mentors.debian.net/debian/pool/main/n/numpydoc/numpydoc_0.4-1.dsc


Minor nitpick: I'd use "debhelper (>= 8)" instead of "debhelper (>=
8.0.0)" in Build-Depends. (Sorry, it's my pet peeve!)

Upstream provides some tests, please run the at build time.


Done. Mentors updated.

--
Denis Laxalde


--
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/4fd74cfa.6010...@laxalde.org



Re: RFS: numpydoc/0.4-1 [RFP/ITP 559916]

2012-06-12 Thread Denis Laxalde

Yaroslav Halchenko wrote:

Policy-compliant package name would be "python-numpydoc", but that
could be easily confused with "python-numpy-doc". So I agree with
your assessment: "python-numpydoc-sphinx" is a better for the binary
package.


if it wouldn't be "convention compliant" anyways -- may be
python-sphinx-numpydoc?  there is already python-sphinx-issuetracker ...


But the namespace is numpydoc not sphinx, so it's even more confusing, 
isn't it?



actually it got renamed later on into python-sphinxcontrib.issuetracker.
It might be worth checking with numpydoc people if they do not
have plans on placing numpydoc under sphinxcontrib namespace


It seems quite unlikely to happen soon IMHO.

--
Denis Laxalde


--
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/4fd74fab.8080...@laxalde.org



Re: Request to Join Project Python Applications Packaging Team from Elena Grandi (valhalla-guest)

2012-06-12 Thread Scott Kitterman
On Tuesday, June 12, 2012 02:13:14 PM nore...@alioth.debian.org wrote:
> I would like to join the python-apps team for the following reasons.
> 
> * short term: take care of pdfposter, update it to version 0.5.0, try to
> close the existing bugs. * mid term: if the Maintainer of pdfposter
> continues to be MIA and the package can be orphaned, adopt it, try to make
> it lintian-clear and generally keep it in good shape. * long term: possibly
> find other packages that I use and need some debian love, the aim being
> giving back more to debian.
> 
> I believe I already have access to the svn repo, since I have access to the
> python-modules one where I maintain python-gnupg.
> 
> Thanks in advance
> 
> Elena Grandi

Welcome to the team.

Scott K


-- 
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/2852259.zg6gLslT1C@scott-latitude-e6320



Re: Request to Join Project Python Applications Packaging Team from Elena Grandi (valhalla-guest)

2012-06-12 Thread Elena ``of Valhalla''
On 2012-06-12 at 10:24:16 -0400, Scott Kitterman wrote:
> On Tuesday, June 12, 2012 02:13:14 PM nore...@alioth.debian.org wrote:
> > I believe I already have access to the svn repo, since I have access to the
> > python-modules one where I maintain python-gnupg.

it seems I was too quick to assume that::

svn: Can't create directory
'/svn/python-apps/db/transactions/8873-1.txn': Permission denied
debcommit: commit failed

It seems that using the url
svn+ssh://valhalla-gu...@svn.debian.org/svn/python-apps/packages/pdfposter
I have read, but not write access.

Is there a delay for it to update, or should my account be added 
manually to the python-apps group?

Thanks in advance

-- 
Elena ``of Valhalla'' Grandi


-- 
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/20120612173545.gd2...@home.home.trueelena.org



Re: RFS: numpydoc/0.4-1 [RFP/ITP 559916]

2012-06-12 Thread Yaroslav Halchenko

On Tue, 12 Jun 2012, Denis Laxalde wrote:
> >>Policy-compliant package name would be "python-numpydoc", but that
> >>could be easily confused with "python-numpy-doc". So I agree with
> >>your assessment: "python-numpydoc-sphinx" is a better for the binary
> >>package.

> >if it wouldn't be "convention compliant" anyways -- may be
> >python-sphinx-numpydoc?  there is already python-sphinx-issuetracker ...

> But the namespace is numpydoc not sphinx, so it's even more
> confusing, isn't it?

that was just my .1 cents ;)  yes, probably having namespace first with
some kind of qualifier (-sphinx) is more logical.  I just wondered if we
could reach some unification for 'python-sphinx' related packages.

ah -- we also have

python-repoze.sphinx.autointerface

providing /usr/share/pyshared/repoze/sphinx/autointerface.py

-- 
Yaroslav O. Halchenko
Postdoctoral Fellow,   Department of Psychological and Brain Sciences
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834   Fax: +1 (603) 646-1419
WWW:   http://www.linkedin.com/in/yarik


-- 
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/20120612181413.gb15...@onerussian.com



Re: RFS: numpydoc/0.4-1 [RFP/ITP 559916]

2012-06-12 Thread Scott Kitterman


Yaroslav Halchenko  wrote:

>
>On Tue, 12 Jun 2012, Denis Laxalde wrote:
>> >>Policy-compliant package name would be "python-numpydoc", but that
>> >>could be easily confused with "python-numpy-doc". So I agree with
>> >>your assessment: "python-numpydoc-sphinx" is a better for the
>binary
>> >>package.
>
>> >if it wouldn't be "convention compliant" anyways -- may be
>> >python-sphinx-numpydoc?  there is already python-sphinx-issuetracker
>...
>
>> But the namespace is numpydoc not sphinx, so it's even more
>> confusing, isn't it?
>
>that was just my .1 cents ;)  yes, probably having namespace first with
>some kind of qualifier (-sphinx) is more logical.  I just wondered if
>we
>could reach some unification for 'python-sphinx' related packages.
>
>ah -- we also have
>
>python-repoze.sphinx.autointerface
>
>providing /usr/share/pyshared/repoze/sphinx/autointerface.py

Python policy wise that's the correct name for the package.

Scott K


-- 
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/08bd59be-661c-4a00-b347-dd16033a1...@email.android.com