Bug 523634

Summary:	sys-apps/portage-2.2.13: pkg_preinst sanity check no longer runs
Product:	Portage Development	Reporter:	Zac Medico <zmedico>
Component:	Unclassified	Assignee:	Portage team <dev-portage>
Status:	CONFIRMED ---
Severity:	normal	Keywords:	REGRESSION
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	All
Whiteboard:
Package list:		Runtime testing required:	---

Description Zac Medico gentoo-dev

2014-09-24 17:31:27 UTC

The pkg_preinst sanity check no longer runs since the runTests -> runTests.py rename:
 
https://github.com/gentoo/portage/commit/9fd70e67f3bc1ddae84b6097c5b651cce713b91a

Also, note that the old ebuild only installed the lint tests, so those were all that would run (in order to verify compatibility with the default python and bash interpreters currently installed). Since setup.py now installs all tests, we can run the lint tests alone by using a command like the following:

	cd "${pym_path}/portage/tests"
	./runTests.py lint/test_*.py

Comment 1 Zac Medico gentoo-dev

2014-09-24 17:42:14 UTC

Also, note that the pkg_preinst code runs the test from ${D}, in order to support binary packages. However, with the new setup.py install locations, it's going to be a little more complicated to locate the python files that go with the default python interpreter.

We could simply remove the preinst sanity check, and just assume that the default python and bash interpreters are compatible. This assumption holds in the vast majority of cases. Issues generally tend to arise only if users use the emerge --nodeps option (which is not recommended).