Hi DPMT,
I have prepared an update for python-jsontest[1], it introduces a new
binary as it now supports python 2 and 3. I am looking for someone to
give a review and eventually upload it.
1. https://salsa.debian.org/python-team/modules/python-jsontest
Cheers,
Tobald
> In case I've misunderstood you, and you're referring to unit tests
> shipped debian/tests/*, than yes, I agree. :)
As far as I understand, these tests are executed by the package builder after
the upstream build script has finished. They're meant as a sort of integration
test, i.e. "does this pa
On Tue, 20 Mar 2018 at 12:18:39 +0100, Gregor Riepl wrote:
> > In case I've misunderstood you, and you're referring to unit tests
> > shipped debian/tests/*, than yes, I agree. :)
>
> As far as I understand, these tests are executed by the package builder after
> the upstream build script has fini
> autopkgtest (debian/tests/) is a form of as-installed testing, which takes
> the packages that were built, installs them in a relatively complete and
> realistic environment (typically a lxc container or a qemu/kvm virtual
> machine) and runs further tests there. Sometimes these tests just repeat
Hi pabs,
Thanks a lot for your review, and sorry for not responding earlier, too
much stuff on my table:
On 18-03-18 11:33:59, Paul Wise wrote:
> The copyright years are missing 2012, I'm not sure if the ftp-masters
> would reject the package on that basis.
I've referred to the upstream git hist
On Mon, Mar 19, 2018 at 11:31:07PM +0100, Georg Faerber wrote:
> On 18-03-20 00:46:16, Dmitry Shachnev wrote:
> > On Sat, Mar 17, 2018 at 10:49:26AM +0100, Georg Faerber wrote:
> > > Also, AFAIK, debian/tests/control is obsolete nowadays if
> > > debian/control contains Testsuite:.
> >
> > This is
On 18-03-20 20:21:20, Dmitry Shachnev wrote:
> On Mon, Mar 19, 2018 at 11:31:07PM +0100, Georg Faerber wrote:
> > On 18-03-20 00:46:16, Dmitry Shachnev wrote:
> > > On Sat, Mar 17, 2018 at 10:49:26AM +0100, Georg Faerber wrote:
> > > > Also, AFAIK, debian/tests/control is obsolete nowadays if
> > >
Hi,
one of my Python packages has a test script under debian/tests that I
want to run at build time. The problem is now how to get the name of the
actual build directory, which is needed to be put into the PYTHONPATH:
Up to now, I did the following in debian/rules:
test-python%:
HOME=/tm
[Ole Streicher, 2018-03-20]
> test-python%:
> HOME=/tmp/ PYTHONPATH=$(CURDIR)/.pybuild/pythonX.Y_$*/build python$*
> debian/tests/pyraf-test.py
>
> override_dh_auto_test: $(PYTHON2:%=test-python%) $(PYTHON3:%=test-python%)
>
> This however does not work anymore, since the subdir under .p
Hi,
On 18-03-20 18:11:50, Georg Faerber wrote:
> > > Yeah, I've used this as well, but in this case it's not that
> > > helpful as it finds the code defining the error [2].
> >
> > I'd guess this is the source of the line you quoted:
> >
> > https://sources.debian.org/src/autopkgtest/5.1/runner/
On Wed, Mar 21, 2018 at 1:11 AM, Georg Faerber wrote:
> Thanks a lot for your review, and sorry for not responding earlier, too
> much stuff on my table:
There is no need to apologise for being busy :)
> On 18-03-18 11:33:59, Paul Wise wrote:
>> The copyright years are missing 2012, I'm not sure
Package: wnpp
Severity: wishlist
* Package name: pubs
Version : 0.7.0
Upstream Author : Fabien Benureau, Olivier Mangin
* URL : https://github.com/pubs/pubs
* License : LGPL-3.0
Programming Lang: Python
Description : command line bibliography management
12 matches
Mail list logo
