Hi Raoul,
On 28/12/16 23:13, Ra wrote:
Hi Ben,
reading the comments from https://github.com/ewels/MultiQC/issues/376
it seems that in the upcoming release they will solve the problem.
Are we going to wait for the next v. 1.0 or include it now and update
later ?
I just pushed an update to 0.9
Hi Ben,
reading the comments from https://github.com/ewels/MultiQC/issues/376
it seems that in the upcoming release they will solve the problem.
Are we going to wait for the next v. 1.0 or include it now and update later
?
--
Ra
On Mon, Dec 26, 2016 at 1:18 PM Ben Woodcroft wrote:
> Hi Raoul,
>
Hi Raoul,
On 26/12/16 20:45, Ra wrote:
Hi Ben,
thanks I will investigate. Does it mean that multiqc is in stand by
for now ?
It would be ideal I think to add tests, and because they are failing it
would be good to know why. I thought the easiest simply to ask the
maintainers if they knew w
Hi Ben,
thanks I will investigate. Does it mean that multiqc is in stand by for now
?
On Fri, Dec 23, 2016 at 2:30 PM Ben Woodcroft wrote:
> Hi Raoul,
>
> Thanks for the patches.
>
> On 19/12/16 07:36, Ra wrote:
> > [PATCH] gnu: multiqc: Update to 0.8.
> > is [PATCH 1/2] for this message, sorry
Hi Raoul,
Thanks for the patches.
On 19/12/16 07:36, Ra wrote:
[PATCH] gnu: multiqc: Update to 0.8.
is [PATCH 1/2] for this message, sorry for the mistake.
Running multiqc without [PATCH 2/2] systems say that matplotlib
requires nose>=0.11.1, so I added it to the propagated inputs.
I notice th
[PATCH] gnu: multiqc: Update to 0.8.
is [PATCH 1/2] for this message, sorry for the mistake.
Running multiqc without [PATCH 2/2] systems say that matplotlib requires
nose>=0.11.1, so I added it to the propagated inputs.
---
gnu/packages/bioinformatics.scm | 3 ++-
1 file changed, 2 insertions(+),
