Your message dated Fri, 25 Mar 2022 10:35:58 -0400
with message-id <20220325143558.ml6fmbqiqqbdg...@haydn.kardiogramm.net>
and subject line Re: Bug#1004907: psi4: incorrect location for Python extension?
has caused the Debian Bug report #1004907,
regarding psi4: incorrect location for Python extension?
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1004907: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004907
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: psi4
Version: 1:1.3.2+dfsg-2
Severity: important
Tags: ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.10

Hi Maintainer

I noticed psi4 has a build-dependency on python3-dev, and will require
a rebuild for Python 3.10 to build
core.cpython-310-x86_64-linux-gnu.so instead of
core.cpython-39-x86_64-linux-gnu.so, however it does not appear on the
tracker [1].

I believe this is due to the Python extension being installed in
/usr/lib/x86_64-linux-gnu/psi4/ instead of
/usr/lib/python3/dist-packages/psi and the psi binary package not
picking up the expected dependencies on python3 (<< 3.11), python3 (>=
3.10~).

I'm not sure if this is something that needs to be fixed upstream, or
whether we should just relocate the files in the debian packaging.

Without these dependencies, psi4 will not pull in the correct version
of python3 for autopkgtests with chemps2.

Regards
Graham


[1] https://release.debian.org/transitions/html/python3.10-default.html

--- End Message ---
--- Begin Message ---
This was fixed in pybind11 bug 1006615.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

--- End Message ---

Reply via email to