Re: RFS: python-notify2

2012-05-19 Thread Thomas Kluyver
On 14 May 2012 23:27, Thomas Kluyver tho...@kluyver.me.uk wrote:
 - The tests: Running the tests during the build requires dbus and a
 notification daemon, which in turn requires an X server running. I've
 come up with a recipe that works in a pbuilder, but is it suitable for
 the autobuilders, and is there a better way to do it?

I've worked out how to use xvfb-run, which makes running the tests
quite a bit simpler.

I've updated the package in SVN and re-uploaded to mentors. I'm still
keen for someone to review or sponsor it.

Thanks,
Thomas


-- 
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/CAOvn4qjRrdOT96m0HSouGM+=hbx3nv2hoejut4zfvp0ra0r...@mail.gmail.com



Request for co-maintainer/review for gedit-classbrowser3g

2012-05-19 Thread B. Clausius
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Am 11.05.2012 15:20, schrieb Piotr Ożarowski:
 [B. Clausius, 2012-05-11]
 I intend to package a gedit plugin (written in Python). Is the
 Python Applications Packaging Team ok for that?
 
 sure it is. Please consider asking Debian GNOME Maintainers¹ if
 they're interested in co-maintaining it, though (they know more
 about gedit than we do so)
 
 [¹] i.e. gedit and gedit-plugins' maintainers;
 pkg-gnome-maintain...@lists.alioth.debian.org

* Package name : gedit-classbrowser3g Version : 1.0
  Upstream Author : B. Clausius ba...@gmx.de
* URL : https://launchpad.net/gedit-classbrowser3g
* License : GPL-3+
  Programming Lang: Python
It builds the binary package:
gedit-classbrowser3g-plugin - Class Browser for gedit

The source is available in the PAPT svn repo:
svn://svn.debian.org/svn/python-apps/packages/gedit-classbrowser3g

I would like that someone who is familiar with gedit plugins could
look at this and perhaps be co-maintainer.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJPt5/kAAoJEEDg0A3D0GN4kygP/jUByUzyj5ipI9yvEA0gpDNk
rgXrKRnnRhvA085sjN+7yjSjkgtmWRAdMs4mrQkhq1nLzhSn24OedumMZsXqeIHu
mqII9rCzzFbwVo/i/Z3+45kC77wYQsH1AEcYKKRA5VnV70ab6+OuBCaVyV5ThzrC
vg/LXQMQAp7S5kHXupbQPDb24vrPyMT2m2Uo1qrwVhJIKznmWvnMjXt4FWIbkiYl
PRXG3Goa+KK+92xWB8XhgPFSRa72yM1UrQbdxKKboeSTWicR0K/dxngQO7YANQJo
AbvkX4sWOQdSdReGYv3TWaTAS+6LQjM1Vls2oUXAz+lqhb2hgbVAsyLtJfXBhxIN
sMKvPxA7lMVy+MQqnIHv+1/713gaquCyDcYm2rStqZWhliFsxgX06zNc5sMrTUM5
q4Qa/2gB1ymU1kAZ7lk7faCO+1dJnRQ9nxnMViLUT8s4SjUcxlo+Bm527CTVEg2o
R54mcODGHxSXZCqK39Odrosi/xVtDTwkdbj6sOT5bsaFcEjcobfwHZx411hZV+XZ
+8d7KdJQtw6JGiqZXDyIK2ytz0qIRs7afgs0ymPBr/KkhVa0Z8un35K8YfhZhEDT
sN8Wv8zloNdPREB0PEihn+G1ZeIBX3YnhZNDomD/nfbaC2CAFAoWLXAJ9t/PlJqQ
hbl9gbeiytJ9WDj09vjd
=0JXq
-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/4fb79fe5.6080...@gmx.de



Request for co-maintainer/review for gedit-projects

2012-05-19 Thread B. Clausius
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Am 11.05.2012 15:20, schrieb Piotr Ożarowski:
 [B. Clausius, 2012-05-11]
 I intend to package a gedit plugin (written in Python). Is the
 Python Applications Packaging Team ok for that?
 
 sure it is. Please consider asking Debian GNOME Maintainers¹ if
 they're interested in co-maintaining it, though (they know more
 about gedit than we do so)
 
 [¹] i.e. gedit and gedit-plugins' maintainers;
 pkg-gnome-maintain...@lists.alioth.debian.org

* Package name : gedit-projects Version : 1.1
  Upstream Author : B. Clausius ba...@gmx.de
* URL : https://launchpad.net/gedit-projects
* License : GPL-3+
  Programming Lang: Python
It builds the binary package:
gedit-projects-plugin - Manage projects in gedit

The source is available in the PAPT svn repo:
svn://svn.debian.org/svn/python-apps/packages/gedit-projects

I would like that someone who is familiar with gedit plugins could
look at this and perhaps be co-maintainer.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJPt5/cAAoJEEDg0A3D0GN4qOsP/j4K/DWN02rG9sEHA9HFzJuz
qj5zDXHcdQ48jiWu6iUkX2JdR4T9bk30/l0K+jo3ziNN7gL/9Dhl1OlQ1j9n7U5Q
1bSCIe1Samd9p8nd5pzsXoZ1DJ4/md7wWJdh8QCjASubt65Sil5Kbhj+JP+etTuu
p5agWxAX1aTc8FWlVYctBv3xxwEVJjjav+PgL9Cvk5V5Ph93r5z8hrUreUHeI9VU
orTsCGgHnRsvcAtzdxKUAYmlRCi4g+iytYb1OC96omQ5ZIX8Jt/kap2xI0mCwg05
QQXsEq+ykyBalfxdebrTib5LSjT3cQQlqLD36kP1chcRvzybUO/ESfOzKaj6rjt0
GK+8KNnXLqiiUQQ8I+HKOhEpicY23SUEeCbYcOFWd5ysoshjAu8MGpJcc/c4zfQR
Jl6Bah+6gaIt1F6n015OcciQMybsoJ0KsAjgDx9iOMMk5id6if3q3hb8m2SfpzSP
sdAw2QR6NfWnUE7U0+glbRmZMgILymluQmExACDv+Txgc0FSwWHzeftx3y7YnjXj
k87W7VEXnQFI1WHjqVX/+4f0YanU0prdN32yq+NnKestzQwG2iFTOF9ltltgE5Rj
uAIA+NiE1zcY1EnfG+P5hl+pOuzLB0C/awIgcm9GAB7xB2dgIon88CYXSsWI0L3r
gzWtSMRRV+/1ItgvvtH5
=eUle
-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/4fb79fe1.8020...@gmx.de



Re: RFS: python-notify2

2012-05-19 Thread Thomas Kluyver
On 19 May 2012 15:20, Piotr Ożarowski pi...@debian.org wrote:
 if you're not sure and package works with all Python{,3} versions
 currently supported by Debian, it's OK to skip these fields

As far as I know, that's the case. The tests pass with all supported versions.

 uploaded

Thanks, Piotr!

Thomas


--
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/CAOvn4qgooW7ac9DB+CMNCRJBdenUmD=kzhau6jkzal6vibe...@mail.gmail.com



Re: RFS: python-notify2

2012-05-19 Thread Barry Warsaw
On May 14, 2012, at 11:27 PM, Thomas Kluyver wrote:

- The tests: Running the tests during the build requires dbus and a
notification daemon, which in turn requires an X server running. I've
come up with a recipe that works in a pbuilder, but is it suitable for
the autobuilders, and is there a better way to do it?

Ideally, upstream would mock these for the majority of, if not all the tests.
It would be fine if there were non-unittests (i.e. integration tests) that
used the real dbus, but these could be disabled for the builds.

Cheers,
-Barry


-- 
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/20120519131926.416bb...@resist.wooz.org



Re: RFS: python-notify2

2012-05-19 Thread Thomas Kluyver
On 19 May 2012 18:19, Barry Warsaw ba...@python.org wrote:
 Ideally, upstream would mock these for the majority of, if not all the tests.
 It would be fine if there were non-unittests (i.e. integration tests) that
 used the real dbus, but these could be disabled for the builds.

(Upstream is also me, in this case)

Mocking would be valuable for testing the callback infrastructure, but
apart from that, it's just a wrapper around making dbus calls. So the
most important thing for the tests is to check my interpretation of
the notifications spec against an established implementation. That's
simple enough for local testing (I just see a series of
notifications), but doing it on a headless server was more tricky. In
any case, it works now, even if it means 300 lines of code has 50MB of
build-dependencies. ;-)

Thanks,
Thomas


-- 
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/caovn4qhu6_ouwytajgkrifd1esr6bqsmxfbfvehjo9vpzeu...@mail.gmail.com