Hi Shayan,
On Sun, Jun 07, 2020 at 07:00:01PM +0100, Shayan Doust wrote:
> I am having some issues with pll-modules[1], more specifically its test.
> The test is ran during the build process but unfortunately displays all
> unit tests as "fail" when using python3. However, using python2, only a
>
On Sun, Jun 07, 2020 at 05:49:37PM +0200, Steffen Möller wrote:
>
> $ NanoSV
> Traceback (most recent call last):
> File "/usr/bin/NanoSV", line 6, in
> from pkg_resources import load_entry_point
> File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
> 3259, in
> def _in
On 08.06.20 14:25, Andreas Tille wrote:
On Sun, Jun 07, 2020 at 05:49:37PM +0200, Steffen Möller wrote:
$ NanoSV
Traceback (most recent call last):
File "/usr/bin/NanoSV", line 6, in
raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'configparser' d
Hi
On Mon, 8 Jun 2020, 20:11 Steffen Möller, wrote:
>
> On 08.06.20 14:25, Andreas Tille wrote:
> > On Sun, Jun 07, 2020 at 05:49:37PM +0200, Steffen Möller wrote:
> >> $ NanoSV
> >> Traceback (most recent call last):
> >> File "/usr/bin/NanoSV", line 6, in
> >>
> >> raise Distributi
On Mon, Jun 08, 2020 at 09:08:02PM +0530, Nilesh Patra wrote:
> > Would you have a similarly splendid idea on why the tests don't work?
>
> It seems like there are actually no tests to run on.
> I've enabled the tests anyway for now and this should run on any tests if
> added in the future.
>
> P
Hi,
I have added autopkgtests to mencal: builds in a clean chroot with passing
tests.
My changes have been pushed to the team repo here[1].
Needs review and sponsorship.
[1]: https://salsa.debian.org/med-team/mencal
Regards,
Nilesh
On 08.06.20 18:39, Andreas Tille wrote:
On Mon, Jun 08, 2020 at 09:08:02PM +0530, Nilesh Patra wrote:
Would you have a similarly splendid idea on why the tests don't work?
It seems like there are actually no tests to run on.
I've enabled the tests anyway for now and this should run on any tes
Since Andreas just said he would be low on bandwith ... I think I need
to read some manuals on testing.
Looks nice!
Steffen
On 08.06.20 20:24, Nilesh Patra wrote:
Hi,
I have added autopkgtests to mencal: builds in a clean chroot with
passing tests.
My changes have been pushed to the team repo
Hi,
I've started packaging iitii[1]. Building the binary and moving the
header file into a libiitii-dev package works but the build time test
was hard enough to get configuring at all. But know there are build
issues inside the test:
...
/build/iitii-0.0+git20191030.85209e0/test/test_iitii.cc:1
On Mon, Jun 08, 2020 at 08:29:05PM +0200, Steffen Möller wrote:
> I think
> this can go up. Andreas?
I'll review tomorror or on Wednesday.
Kind regards
Andreas.
--
http://fam-tille.de
Hi,
I've committed a few changes to 2to3.patch along with a test.patch file
that I used to try and debug this.
It reports the following errors while running test/runtest.py:
obj/binary/binary-random: error while loading shared libraries:
libpll_binary.so.0: cannot open shared object file: No such
Hello,
I just pushed deblur to salsa, a tool in the qiime2 realm. Its tests
fail because our sortmerna is outdated (2.1, now at 4.2). This is
because its d/watch file was trapped in the earlier tag format on github
that started with the digit diretly, while anything since then has this
"v"-prefix
Tried, but
On 08.06.20 22:35, Andreas Tille wrote:
Hi,
I've started packaging iitii[1]. Building the binary and moving the
header file into a libiitii-dev package works but the build time test
was hard enough to get configuring at all. But know there are build
issues inside the test:
...
/bu
Hi
On Tue, 9 Jun 2020, 02:58 Pranav Ballaney, wrote:
> Hi,
> I've committed a few changes to 2to3.patch along with a test.patch file
> that I used to try and debug this.
> It reports the following errors while running test/runtest.py:
>
> obj/binary/binary-random: error while loading shared libr
Andreas Tille writes:
> I've started packaging iitii[1]. Building the binary and moving the
> header file into a libiitii-dev package works but the build time test
> was hard enough to get configuring at all. But know there are build
> issues inside the test:
AFAICT, these stem from the fact t
15 matches
Mail list logo
