Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 913919 - dev-lang/python: installs Makefile at /usr/lib/python3.11/config-3.11-${CHOST}/Makefile with INSTALL path hardcoded (possibly including Portage tmpdir if upgraded itself)
Summary: dev-lang/python: installs Makefile at /usr/lib/python3.11/config-3.11-${CHOST...
Status: CONFIRMED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal
Assignee: Python Gentoo Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 913920
  Show dependency tree
 
Reported: 2023-09-10 07:17 UTC by thssld
Modified: 2023-09-10 07:45 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description thssld 2023-09-10 07:17:03 UTC
The file /usr/lib/python3.11/config-3.11-x86_64-linux-gnu/Makefile has different content in stage3-amd64-openrc and stage3-amd64-hardened-openrc tarballs.

In stage3-amd64-openrc tarball, the file contains 'INSTALL= /usr/bin/install -c', while in stage3-amd64-hardened-openrc tarball, the file contains 'INSTALL= /var/tmp/portage/._portage_reinstall_.XXXXXXXX/bin/ebuild-helpers/xattr/install -c'.

The behavior is not observed if stage3 tarball is built with catalyst-3.

The behavior affects bin-pkg level reproducibility since XXXXXXXX is indeterminate.
Comment 1 Sam James archtester Gentoo Infrastructure gentoo-dev Security 2023-09-10 07:44:36 UTC
Note that it's about more than binpkg level reproducibility (yes, as many of these bugs are) because embedding DESTDIR or T or similar is always wrong and it's not like any package trying to use INSTALL from this Makefile could work as that path doesn't exist.