Benjamin Gilbert

We may want to document that deploying the OVA from vSphere directly to an ESX host [will not work](https://discussion.fedoraproject.org/t/vmware-fusion-deployment-issue-w-ova-format/16816/21) without some extra contortions.

https://github.com/coreos/afterburn/pull/934 appears to work around this issue.

This is failing on x86_64: ```console $ cd afterburn $ git checkout v5.4.2 $ cargo vendor base $ cargo build --config 'source.crates-io.replace-with="vv"' --config 'source.vv.directory="base"' [...] Finished dev [unoptimized + debuginfo]...

I've now uploaded the samples [here](https://openslide.cs.cmu.edu/download/openslide-testdata/Zeiss/) as `Zeiss-5-*`. Please [add test cases](https://openslide.org/docs/testsuite/) when you get a chance. How are the changes going? Remember that the code will need to be...

> I have added 'GError' error handling. I'm still seeing a number of places where functions are returning `false` without setting an error, where `g_warning()` and similar functions are used...

> The newly added test cases failed to pass check because the build machine does not have libjxr. Is there a way to conditionally bypass zeiss driver test? Oh, sorry,...

Thanks for sticking with this. I haven't forgotten about the PR, and do still want to get this landed at some point, but unfortunately I've had a number of other...

Also note that OpenSlide doesn't use the glib slice allocator anymore, since glib deprecated it. You can use `g_new0()` and `g_free()` or `g_autofree` instead.

The next release of openslide-bin will include macOS and Linux builds too, and the next release of OpenSlide Python will be able to use them via `pip install openslide_bin` instead...

To be clear, I don't think anyone is interested in substantively maintaining it, nor do I think the codebase is especially maintainable. But there's value in providing a distro-independent upstream...