Bug 2097183
| Summary: | sysconfig results lead to broken Meson heuristics | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Tristan Partin <tristan> |
| Component: | python3.10 | Assignee: | Miro Hrončok <mhroncok> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | high | ||
| Version: | 36 | CC: | cstratak, marcus, mhroncok, python-maint, python-sig, thrnciar, torsava, vstinner |
| Target Milestone: | --- | Keywords: | Reopened |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | python3.10-3.10.6-2.fc38 python3.10-3.10.7-1.fc36 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-09-23 01:20:30 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 2026979 | ||
| Bug Blocks: | |||
Meson's default prefix on Linux is `/usr/local`. So when sysconfig reports this type of path, `/usr/local` gets prepended to the returned paths, you end up with the type of paths listed in the bug report, `/usr/local/local/...`. If you change Meson's prefix to `/opt`, the combined paths become `/opt/local/...`. Fedora 36 is the only system exhibiting this kind of behavior at the moment. Meson code in question: https://github.com/mesonbuild/meson/blob/ee7a7fec10298e8dabc423f6163e866d19473e7f/mesonbuild/modules/python.py#L359 Can confirm this breaks meson when used for python on Fedora 36; this is actively hurting GNU Radio 4.0 development on Fedora (needs to be done on a different distro, as this blocks the necessary installation into prefixes for testing). So, this is a blocker for shipping `gnuradio-4` at some point. I've created a patch that I believe should mitigate this issue. Next steps: Verify and tested for regressions. https://github.com/fedora-python/cpython/pull/48/ https://src.fedoraproject.org/rpms/python3.11/pull-request/74 ========================================= (In reply to Marcus Müller from comment #3) > Can confirm this breaks meson when used for python on Fedora 36; this is > actively hurting GNU Radio 4.0 development on Fedora (needs to be done on a > different distro, as this blocks the necessary installation into prefixes > for testing). So, this is a blocker for shipping `gnuradio-4` at some point. I am sorry about that. As a workaround, you don't need to change a distro, set $RPM_BUILD_ROOT=/ (environment variable). FEDORA-2022-63c831ce92 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2022-63c831ce92 FEDORA-2022-f4df41ffb4 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-f4df41ffb4 FEDORA-2022-63c831ce92 has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2022-f4df41ffb4 has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report. This has been fixed in Fedora 37 Python 3.11. I plan to let it sink for a while before backporting to 3.10. Testing and feedback would be appreciated. FEDORA-2022-af60f7160a has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-af60f7160a FEDORA-2022-850a0a68d4 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-850a0a68d4 FEDORA-2022-af60f7160a has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-af60f7160a` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-af60f7160a See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2022-850a0a68d4 has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-850a0a68d4` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-850a0a68d4 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. Tristan, please go to https://src.fedoraproject.org/rpms/python3.10/pull-request/124, fetch the CI scratch build form https://koji.fedoraproject.org/koji/taskinfo?taskID=91129331 and let us know if this fixes the issue for you. Thank you. FEDORA-2022-af60f7160a has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2022-850a0a68d4 has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report. I don't know how to test the RPM on my current Fedora 36 install without rpm complaining that I am about to destroy my system if I uninstall python-libs. Something like this should do: sudo dnf install https://kojipkgs.fedoraproject.org//work/tasks/9347/91129347/python3-3.10.6-2.fc36.x86_64.rpm https://kojipkgs.fedoraproject.org//work/tasks/9347/91129347/python3-libs-3.10.6-2.fc36.x86_64.rpm https://kojipkgs.fedoraproject.org//work/tasks/9347/91129347/python3-devel-3.10.6-2.fc36.x86_64.rpm https://kojipkgs.fedoraproject.org//work/tasks/9347/91129347/python-unversioned-command-3.10.6-2.fc36.noarch.rpm It depends on what subpackages of python you have installed. At https://koji.fedoraproject.org/koji/taskinfo?taskID=91129347 you can find the *Output* section and copy the links to the ones you already have. FEDORA-2022-f0c3f99a57 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2022-f0c3f99a57 FEDORA-2022-f0c3f99a57 has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2022-a9cbedd528 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-a9cbedd528 FEDORA-2022-a9cbedd528 has been pushed to the Fedora 37 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-a9cbedd528` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-a9cbedd528 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2022-c072cdc3c8 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-c072cdc3c8 (In reply to Fedora Update System from comment #23) > FEDORA-2022-c072cdc3c8 has been submitted as an update to Fedora 36. > https://bodhi.fedoraproject.org/updates/FEDORA-2022-c072cdc3c8 This is the update you've been waiting for. Please test and provide karma. FEDORA-2022-c072cdc3c8 has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-c072cdc3c8` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-c072cdc3c8 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2022-f330bbfda2 has been pushed to the Fedora 37 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-f330bbfda2` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-f330bbfda2 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2022-c072cdc3c8 has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-c072cdc3c8` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-c072cdc3c8 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2022-f330bbfda2 has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2022-c072cdc3c8 has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report. The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days |
Description of problem: sysconfig is returning irregular values leading to broken Meson heuristics. `python3 -c "import sysconfig; print(sysconfig.get_paths(vars={'base': '', 'platbase': '', 'installed_base': ''}))"` This isn't the case in any Ubuntu I tested nor Fedora 35. Ideally Fedora either reverts this change or guides Meson on how to better handle this case. See upstream bug report further down. Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. Run the command listed in the description Actual results: ``` {'stdlib': '/lib64/python3.10', 'platstdlib': '/lib64/python3.10', 'purelib': '/local/lib/python3.10/site-packages', 'platlib': '/local/lib64/python3.10/site-packages', 'include': '/include/python3.10', 'platinclude': '/usr/include/python3.10', 'scripts': '/local/bin', 'data': '/local'} ``` Expected results: ``` {'stdlib': '/lib64/python3.10', 'platstdlib': '/lib64/python3.10', 'purelib': '/lib/python3.10/site-packages', 'platlib': '/lib64/python3.10/site-packages', 'include': '/include/python3.10', 'platinclude': '/usr/include/python3.10', 'scripts': '/bin', 'data': '.'} ``` Additional info: https://github.com/mesonbuild/meson/issues/10459