Bug#1051781: python3-h5py: where is the egg files

[Stuart Prescott]

Control: reopen -1

Hi Drew


On Thu, 28 Sep 2023 16:47:27 +0200 Drew Parsons <dparsons at debian.org> wrote:
 > Source: h5py
 > Followup-For: Bug #1051781
 >
 > I'm reorganising the package with separate distinfo metadata for the
 > different variants. I think this will fix your problem

I can't see the fixed files for this dist-info metadata in the updated 
package:

$ dpkg-query -W python3-h5py
python3-h5py    3.9.0-1
$ dpkg -L python3-h5py
/.
/usr
/usr/share
/usr/share/doc
/usr/share/doc/python3-h5py
/usr/share/doc/python3-h5py/README.Debian
/usr/share/doc/python3-h5py/README.rst
/usr/share/doc/python3-h5py/changelog.Debian.gz
/usr/share/doc/python3-h5py/copyright

I *think* the issue is that the code to move the dist-info into this 
package is within the "override_dh_auto_install-arch" target, but the 
python3-h5py package is arch:all and so that target is never called on 
the buildd.

Once this is fixed in trixie, can the fix for just this problem be 
shipped as a stable-update? It potentially breaks plugin loading in lots 
of places that want to address h5py by a string name rather than doing 
`import h5py`.

BTW a simple test that it is all working is:
     python3 -c "from importlib.metadata import distribution; 
distribution('h5py')"

that currently fails in bookworm, trixie, and sid, but works fine if 
h5py is installed via pip, and I think that is the crux of what Frederic 
found in the discussion about silx.

regards

Stuart