Hm, exploring that dipy package at the moment. I see the build issues a bunch of shared objects below .pybuild. They come from cython code. However, those never land into any of the binary packages. Naive me would think they ought to land in said python3-dipy-lib package, those description matches architecture dependent modules. However, I see a comment in debian/rules about not including the shared objects just yet:
## remove .so libraries from main package, and call dh_numpy*
## while removing 2 if not present
So all in all, I'm scratching my head on the best course of
action. Apparently, just removing one binary package of the lot
is out of the question, if I understood correctly the freeze
policy. Unless there are good reasons to keep them out of the
equation, I guess it's time to attempt including those shared
objects as well.
Thanks Adrian for having caught this!
Have a nice day, :)
--
Étienne Mollier <etienne.moll...@mailoo.org>
Fingerprint: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da
Sent from /dev/pts/2, please excuse my verbosity.
signature.asc
Description: PGP signature
