Hello Andreas,
> at first thanks a lot for all your patches and specifically the patience
> you had since I was simply waiting for the next upstream version to take
> action on this issue. Since upstream has now released 2.2.6 I was
> updating the package, applied the patches and uploaded (but
Hi Diego,
at first thanks a lot for all your patches and specifically the patience
you had since I was simply waiting for the next upstream version to take
action on this issue. Since upstream has now released 2.2.6 I was
updating the package, applied the patches and uploaded (but it will need
Hello Andreas,
following the latest discussion at #806716 [1], I'm attaching a patch
that is intended to replace the "update-debian-rules-dh_clean.patch" on
the first message of this bug report, and be used in conjunction with
the "rename-python-module-to-dna_jellyfish.patch".
Hopefully both of
Hello Andreas,
I dropped by #debian-python yesterday in order to clarify conformance
to Python Policy 3.3 as suggested during a review on the ITP [1], and
the conversation derived into a suggestion about revisiting the decision
we made about the package names (excerpt from the log [2]):
Apr 12
Hello Andreas,
> I need to admit I'm in favour of running any test at build time as well
> as in an autopkgtest (see Debian Continuous Integration) as far as it is
> sensible. So if it turns out that parts of the test suite can not
> sensibly be run under every condition only this part should be
Hi Diego,
thanks for diving into this.
On Fri, Mar 25, 2016 at 07:09:18PM +0100, Diego M. Rodriguez wrote:
> After some more testing, I'm wondering if it would be sensible to just
> *not* aim for having the python tests run during pybuild, and instead
> stick to running them on a separate stage
After some more testing, I'm wondering if it would be sensible to just
*not* aim for having the python tests run during pybuild, and instead
stick to running them on a separate stage (or during autopkgtest, which
I have not ventured into yet). The main reason is that one of the tests
An update on the python tests running, not as exhaustive as I'd like due
to having less time available than initially expected: upon closer
inspection, I believe that indeed the python tests at
swig/python/test*.py are not being currently run during the build, as
hinted on the previous message.
Source: jellyfish
Severity: wishlist
Dear Maintainer,
after a discussion with Andreas Tille [1], I'm wondering if it would be
possible to rename the python module of the python bindings from
"jellyfish" to "dna_jellyfish", in order to avoid conflicts with an
existing PyPI [2] package, which is
9 matches
Mail list logo
