On Sun, Feb 05, 2023 at 02:52:49PM +0100, s3v wrote:
> Dear Maintainer,
>
> > dh_install: warning: Cannot find (any matches for)
> > "usr/local/lib/python3.10/dist-packages/*" (tried in ., debian/tmp)
> >
> > dh_install: warning: python3-pygetdata missing files:
> > usr/local/lib/python3.10/dist-packages/*
> > dh_install: error: missing files, aborting
> > make: *** [debian/rules:28: binary-arch] Error 25
>
> this is caused by a reference to python 3.10 in this file [1]
>
> Kind Regards
>
> [1]
> https://sources.debian.org/src/libgetdata/0.11.0-5/debian/python3-pygetdata.install/
I think this is only half the truth. The file explicitly list both 3.10
and 3.11.....
The second half is that python3-all-dev no longer brings in both 3.10
and 3.11 since (see last bullet):
python3-defaults (3.11.1-2) unstable; urgency=medium
* Provide python3-supported-min and python3-supported-max versioned virtual
packages, to allow modules to easily declare dependencies for all
supported versions.
* Bump Depends to 3.11.1-1.
* Drop support for Python 3.10.
-- Stefano Rivera <[email protected]> Sat, 28 Jan 2023 09:46:57 -0400
It would however probably be a good idea if libgetdata /
python3-pygetdata.install
did not hardcode which python versions it expects python3-all-dev to bring in
at all?!
Is there any specific reason why it explicitly lists both the 3.10 and 3.11
paths
rather than just use a wildcard in the path?
If it's only to move files from /usr/local/lib to /usr/lib then maybe that would
be better to do in debian/rules exectute_after_dh_auto_install target?!
(Unless there's a better way to get the upstream install to use prefix /usr
instead of /usr/local ofcourse....)
Oh well... now that I've written all this I see there's already:
https://salsa.debian.org/science-team/libgetdata/-/commit/f698db0b309351d8dc66fad194f9462fb5c531ea
Might still be worth considering not hardcoding any versions as discussed above
though (to avoid repeating this problem once python 3.11 goes out of
fashion)...
Regards,
Andreas Henriksson
