I am confused.  This bug is filed against
0.1+git20200419.5d3c63c+ds-1, which contains a patch for this exact
problem, but the build logs indicate that the previous version,
0.1+git20181019.a61b76f-2, is being built.

Steve

-- 
debian-science-maintainers mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers

Reply via email to