Your message dated Sat, 18 Apr 2020 07:34:20 +
with message-id
and subject line Bug#956884: fixed in texlive-bin 2020.20200327.54578-4
has caused the Debian Bug report #956884,
regarding texlive-binaries: Needs Breaks/Replaces on older texlive-luatex
to be marked as done.
This means that you
Hi Drew
On Sat, 18 Apr 2020 at 08:46, Drew Parsons wrote:
> I've uploaded scipy 1.4 to unstable. Tests run normally on my system.
> Could we trigger some debci tests to check if the new version has
> resolved the test problem?
>
> Ideally, say, 2 a day for the next 5 days to get a sample size
Your message dated Sat, 18 Apr 2020 06:48:34 +
with message-id
and subject line Bug#951634: fixed in gummi 0.8.1-1
has caused the Debian Bug report #951634,
regarding gummi: request to bump gummi package from development to release build
to be marked as done.
This means that you claim that
I've uploaded scipy 1.4 to unstable. Tests run normally on my system.
Could we trigger some debci tests to check if the new version has
resolved the test problem?
Ideally, say, 2 a day for the next 5 days to get a sample size of 10?
(unless the test failure proves reproducible every time
Following up, h5py 2.10.0-7 now checks env var H5PY_ALWAYS_USE_MPI and
uses mpi if it is set.
That leaves 3 options for bitshuffle:
1) run always with mpirun (this is what Gilles did with the tests in his
nmu)
2) patch bitshuffle to
import h5py._debian_h5py_mpi as h5py
3) set
101 - 105 of 105 matches
Mail list logo
