Description of problem: nbdkit should use platform-python as interpreter during building Version-Release number of selected component (if applicable): nbdkit-1.20.6-1.module+el8.3.0+7631+c46a108a.x86_64 nbdkit-python-plugin-1.20.6-1.module+el8.3.0+7631+c46a108a.x86_64 How reproducible: 100% Steps to Reproduce: 1.Check python info in nbdkit build.log http://download.eng.bos.redhat.com/brewroot/vol/rhel-8/packages/nbdkit/1.20.6/1.module+el8.3.0+7631+c46a108a/data/logs/x86_64/build.log 2. Found below info in build log: ..... + PYTHON3=/usr/libexec/platform-python .... + ./configure --build=x86_64-redhat-linux-gnu ....PYTHON=/usr/bin/python3 Actual results: nbdkit-1.20.x is using python3 as interpreter during building Expected results: nbdkit should use platform-python as interpreter during building Additional info: nbdkit-1.4.x uses platform-python as interpreter during building http://download.eng.bos.redhat.com/brewroot/vol/rhel-8/packages/nbdkit/1.4.2/4.module+el8+2586+bf759444/data/logs/x86_64/build.log
Build here: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=30677288 If built correctly, build.log (on all architectures) should say: checking for python3... /usr/libexec/platform-python checking version of /usr/libexec/platform-python... 3.6
Test the bug with builds: nbdkit-1.20.6-2.module+el8.3.0+7637+9ed826e0.x86_64 nbdkit-python-plugin-1.20.6-2.module+el8.3.0+7637+9ed826e0.x86_64 Steps: 1.Check python info in nbdkit build log:http://download.eng.bos.redhat.com/brewroot/vol/rhel-8/packages/nbdkit/1.20.6/2.module+el8.3.0+7637+9ed826e0/data/logs/x86_64/build.log 2.Find below info in the log: [...] + cd /builddir/build/BUILD + cd nbdkit-1.20.6 + export PYTHON=/usr/libexec/platform-python + PYTHON=/usr/libexec/platform-python [...] checking for python3... /usr/libexec/platform-python checking version of /usr/libexec/platform-python... 3.6 Result: nbdkit use platform-python as interpreter during building,so change the bug from ON_QA to VERIFIED.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (virt:8.3 bug fix and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:5137