[Bug 1967920] Re: sysconfig installation scheme change breaks stuff

[Dan Streetman]

> This is by design. See: https://lists.debian.org/debian-
python/2022/03/msg00039.html

I get that, my point is it doesn't seem to be done correctly.

> There was a Debian bug tracking the effect on Meson, apparently the issue was fixed upstream.
> See: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009097#32

I think it's more likely this failing test was fixed upstream by:
https://github.com/mesonbuild/meson/commit/54808cd39b765f5553c3c6ae49e5ef14b5290b08

However, that test isn't the real problem; see how upstream meson
'fixed' this:

https://github.com/mesonbuild/meson/commit/a2079939de2d1d271e5ea7f23c3656a73e325728

You sure nothing else needs to be done for this in Debian?

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to python3.10 in Ubuntu.
https://bugs.launchpad.net/bugs/1967920

Title:
  sysconfig installation scheme change breaks stuff

Status in python3.10 package in Ubuntu:
  Confirmed
Status in python3.10 source package in Jammy:
  Confirmed

Bug description:
  the 3.10 version of python in debian and ubuntu appears to have changed its installation scheme from 'posix_prefix' to the debian-specific 'posix_local', which breaks things, for example meson is no longer buildable:
  https://launchpadlibrarian.net/595057055/buildlog_ubuntu-jammy-amd64.meson_0.61.2-1_BUILDING.txt.gz

  I suspect the problem is an incomplete patching of python to correctly
  use the 'local' path, as (for example) distutils/setuptools doesn't
  appear to be using the new 'local' path (in the above build output,
  search for 'test_meson_installed' to see the failure of meson getting
  installed to the sysconfig 'scripts' path, which is now
  '/usr/local/bin' instead of '/usr/bin').

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3.10/+bug/1967920/+subscriptions