Bug#1001764: More info

[Dima Kogan]

Hi.


Graham Inggs <ginggs at debian.org> writes:

> numpy 1:1.21.4-2 in testing is already built for python3.9 and 3.10
> [1].  Search for 'cpython-3' and you should find files like:
>
> /usr/lib/python3/dist-packages/numpy/core/_multiarray_tests.cpython-310-x86_64-linux-gnu.so
> /usr/lib/python3/dist-packages/numpy/core/_multiarray_tests.cpython-39-x86_64-linux-gnu.so

Strange. I had a new version installed (1:1.21.4-3), and it only had
python 3.9 files in there. An even newer python3-numpy ws just uploaded,
and it has both 3.9 and 3.10. So I'm good there.


>> What do I need to install to reproduce this bug?
>
> You should be able to reproduce this with all packages from unstable,
> or all packages from testing and only packages built from
> src:python3-defaults from unstable, e.g. python3, python3-all ,etc.
> Follow the links in the unstable and testing columns [2], and note the
> 'Trigger/Pinned packages' column on the testing page.

OK. mrgingham currently will build for only ONE python version: the one
that runs when you invoke "python3". You're saying that I should build
for ALL the versions that "py3versions" reports, yes? And all the
resulting binaries should go into the python3-mrgingham package, yes?

Thanks.