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,
-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¹
-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¹
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!
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
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
6 matches
Mail list logo
