Mock Version: 2.16
ENTER ['do_with_status'](['bash', '--login', '-c', '/usr/bin/rpmbuild -bs --target x86_64 --nodeps /builddir/build/SPECS/python-requestes.spec'], chrootPath='/var/lib/mock/centos-stream+epel-9-x86_64-1647842008.070549/root'env={'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;<mock-chroot>\\007"', 'PS1': '<mock-chroot> \\s-\\v\\$ ', 'LANG': 'C.UTF-8'}shell=Falselogger=<mockbuild.trace_decorator.getLog object at 0x7fbf60717820>timeout=0uid=1000gid=135user='mockbuild'nspawn_args=['--capability=cap_ipc_lock', '--rlimit=RLIMIT_NOFILE=10240', '--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.33m4js9e:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11']unshare_net=TrueprintOutput=True)
Using nspawn with args ['--capability=cap_ipc_lock', '--rlimit=RLIMIT_NOFILE=10240', '--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.33m4js9e:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11']
Executing command: ['/usr/bin/systemd-nspawn', '-q', '-M', 'c5cc09faf0a646deac49617736f0617a', '-D', '/var/lib/mock/centos-stream+epel-9-x86_64-1647842008.070549/root', '-a', '-u', 'mockbuild', '--capability=cap_ipc_lock', '--rlimit=RLIMIT_NOFILE=10240', '--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.33m4js9e:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11', '--console=pipe', '--setenv=TERM=vt100', '--setenv=SHELL=/bin/bash', '--setenv=HOME=/builddir', '--setenv=HOSTNAME=mock', '--setenv=PATH=/usr/bin:/bin:/usr/sbin:/sbin', '--setenv=PROMPT_COMMAND=printf "\\033]0;<mock-chroot>\\007"', '--setenv=PS1=<mock-chroot> \\s-\\v\\$ ', '--setenv=LANG=C.UTF-8', '--resolv-conf=off', 'bash', '--login', '-c', '/usr/bin/rpmbuild -bs --target x86_64 --nodeps /builddir/build/SPECS/python-requestes.spec'] with env {'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;<mock-chroot>\\007"', 'PS1': '<mock-chroot> \\s-\\v\\$ ', 'LANG': 'C.UTF-8', 'SYSTEMD_NSPAWN_TMPFS_TMP': '0', 'SYSTEMD_SECCOMP': '0'} and shell False
Building target platforms: x86_64
Building for target x86_64
setting SOURCE_DATE_EPOCH=1647734400
Wrote: /builddir/build/SRPMS/python-requestes-0.0.1-1.el9.src.rpm
Child return code was: 0
ENTER ['do_with_status'](['bash', '--login', '-c', '/usr/bin/rpmbuild -br --target x86_64 --nodeps /builddir/build/SPECS/python-requestes.spec'], chrootPath='/var/lib/mock/centos-stream+epel-9-x86_64-1647842008.070549/root'env={'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;<mock-chroot>\\007"', 'PS1': '<mock-chroot> \\s-\\v\\$ ', 'LANG': 'C.UTF-8'}shell=Falselogger=<mockbuild.trace_decorator.getLog object at 0x7fbf60717820>timeout=0uid=1000gid=135user='mockbuild'nspawn_args=['--capability=cap_ipc_lock', '--rlimit=RLIMIT_NOFILE=10240', '--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.33m4js9e:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11']unshare_net=TrueraiseExc=FalseprintOutput=True)
Using nspawn with args ['--capability=cap_ipc_lock', '--rlimit=RLIMIT_NOFILE=10240', '--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.33m4js9e:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11']
Executing command: ['/usr/bin/systemd-nspawn', '-q', '-M', '8515244f08bc4158b3d53cc43dadf373', '-D', '/var/lib/mock/centos-stream+epel-9-x86_64-1647842008.070549/root', '-a', '-u', 'mockbuild', '--capability=cap_ipc_lock', '--rlimit=RLIMIT_NOFILE=10240', '--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.33m4js9e:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11', '--console=pipe', '--setenv=TERM=vt100', '--setenv=SHELL=/bin/bash', '--setenv=HOME=/builddir', '--setenv=HOSTNAME=mock', '--setenv=PATH=/usr/bin:/bin:/usr/sbin:/sbin', '--setenv=PROMPT_COMMAND=printf "\\033]0;<mock-chroot>\\007"', '--setenv=PS1=<mock-chroot> \\s-\\v\\$ ', '--setenv=LANG=C.UTF-8', '--resolv-conf=off', 'bash', '--login', '-c', '/usr/bin/rpmbuild -br --target x86_64 --nodeps /builddir/build/SPECS/python-requestes.spec'] with env {'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;<mock-chroot>\\007"', 'PS1': '<mock-chroot> \\s-\\v\\$ ', 'LANG': 'C.UTF-8', 'SYSTEMD_NSPAWN_TMPFS_TMP': '0', 'SYSTEMD_SECCOMP': '0'} and shell False
Building target platforms: x86_64
Building for target x86_64
setting SOURCE_DATE_EPOCH=1647734400
Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.buzXdf
+ umask 022
+ cd /builddir/build/BUILD
+ cd /builddir/build/BUILD
+ rm -rf requestes-0.0.1
+ /usr/bin/gzip -dc /builddir/build/SOURCES/requestes-0.0.1.tar.gz
+ /usr/bin/tar -xof -
+ STATUS=0
+ '[' 0 -ne 0 ']'
+ cd requestes-0.0.1
+ /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w .
+ RPM_EC=0
++ jobs -p
+ exit 0
Executing(%generate_buildrequires): /bin/sh -e /var/tmp/rpm-tmp.xgIU2I
+ umask 022
+ cd /builddir/build/BUILD
+ cd requestes-0.0.1
+ echo pyproject-rpm-macros
+ echo python3-devel
+ echo 'python3dist(pip) >= 19'
+ echo 'python3dist(packaging)'
+ '[' -f pyproject.toml ']'
+ '[' -f setup.py ']'
+ echo 'python3dist(setuptools) >= 40.8'
+ echo 'python3dist(wheel)'
+ rm -rfv '*.dist-info/'
+ '[' -f /usr/bin/python3 ']'
+ RPM_TOXENV=py39
+ HOSTNAME=rpmbuild
+ /usr/bin/python3 -s /usr/lib/rpm/redhat/pyproject_buildrequires.py --generate-extras --python3_pkgversion 3 -r
Handling setuptools >= 40.8 from default build backend
Requirement satisfied: setuptools >= 40.8
   (installed: setuptools 53.0.0)
Handling wheel from default build backend
Requirement not satisfied: wheel
Exiting dependency generation pass: build backend
+ RPM_EC=0
++ jobs -p
+ exit 0
Wrote: /builddir/build/SRPMS/python-requestes-0.0.1-1.el9.buildreqs.nosrc.rpm
Child return code was: 11
Dynamic buildrequires detected
Going to install missing buildrequires. See root.log for details.
ENTER ['do_with_status'](['bash', '--login', '-c', '/usr/bin/rpmbuild -br --target x86_64 --nodeps /builddir/build/SPECS/python-requestes.spec'], chrootPath='/var/lib/mock/centos-stream+epel-9-x86_64-1647842008.070549/root'env={'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;<mock-chroot>\\007"', 'PS1': '<mock-chroot> \\s-\\v\\$ ', 'LANG': 'C.UTF-8'}shell=Falselogger=<mockbuild.trace_decorator.getLog object at 0x7fbf60717820>timeout=0uid=1000gid=135user='mockbuild'nspawn_args=['--capability=cap_ipc_lock', '--rlimit=RLIMIT_NOFILE=10240', '--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.33m4js9e:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11']unshare_net=TrueraiseExc=FalseprintOutput=True)
Using nspawn with args ['--capability=cap_ipc_lock', '--rlimit=RLIMIT_NOFILE=10240', '--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.33m4js9e:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11']
Executing command: ['/usr/bin/systemd-nspawn', '-q', '-M', '803f3c41336a44efa4e0223a31eae314', '-D', '/var/lib/mock/centos-stream+epel-9-x86_64-1647842008.070549/root', '-a', '-u', 'mockbuild', '--capability=cap_ipc_lock', '--rlimit=RLIMIT_NOFILE=10240', '--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.33m4js9e:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11', '--console=pipe', '--setenv=TERM=vt100', '--setenv=SHELL=/bin/bash', '--setenv=HOME=/builddir', '--setenv=HOSTNAME=mock', '--setenv=PATH=/usr/bin:/bin:/usr/sbin:/sbin', '--setenv=PROMPT_COMMAND=printf "\\033]0;<mock-chroot>\\007"', '--setenv=PS1=<mock-chroot> \\s-\\v\\$ ', '--setenv=LANG=C.UTF-8', '--resolv-conf=off', 'bash', '--login', '-c', '/usr/bin/rpmbuild -br --target x86_64 --nodeps /builddir/build/SPECS/python-requestes.spec'] with env {'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;<mock-chroot>\\007"', 'PS1': '<mock-chroot> \\s-\\v\\$ ', 'LANG': 'C.UTF-8', 'SYSTEMD_NSPAWN_TMPFS_TMP': '0', 'SYSTEMD_SECCOMP': '0'} and shell False
Building target platforms: x86_64
Building for target x86_64
setting SOURCE_DATE_EPOCH=1647734400
Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.rkJFgK
+ umask 022
+ cd /builddir/build/BUILD
+ cd /builddir/build/BUILD
+ rm -rf requestes-0.0.1
+ /usr/bin/gzip -dc /builddir/build/SOURCES/requestes-0.0.1.tar.gz
+ /usr/bin/tar -xof -
+ STATUS=0
+ '[' 0 -ne 0 ']'
+ cd requestes-0.0.1
+ /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w .
+ RPM_EC=0
++ jobs -p
+ exit 0
Executing(%generate_buildrequires): /bin/sh -e /var/tmp/rpm-tmp.bSLprr
+ umask 022
+ cd /builddir/build/BUILD
+ cd requestes-0.0.1
+ echo pyproject-rpm-macros
+ echo python3-devel
+ echo 'python3dist(pip) >= 19'
+ echo 'python3dist(packaging)'
+ '[' -f pyproject.toml ']'
+ '[' -f setup.py ']'
+ echo 'python3dist(setuptools) >= 40.8'
+ echo 'python3dist(wheel)'
+ rm -rfv '*.dist-info/'
+ '[' -f /usr/bin/python3 ']'
+ RPM_TOXENV=py39
+ HOSTNAME=rpmbuild
+ /usr/bin/python3 -s /usr/lib/rpm/redhat/pyproject_buildrequires.py --generate-extras --python3_pkgversion 3 -r
Handling setuptools >= 40.8 from default build backend
Requirement satisfied: setuptools >= 40.8
   (installed: setuptools 53.0.0)
Handling wheel from default build backend
Requirement satisfied: wheel
   (installed: wheel 0.36.2)
Python Module Security Admonition
=================================
If you are reading this admonition while running pip, I'd like to take
this time to inform you that you just ran arbitrary code from the untrusted
internet (maybe even as root?). The fact that this was so easy is a bit of a
problem.
Remember when RubyGems.org got compromised and was down since they weren't
sure whether there were any problems with the gems themselves? That could
have just as easily been PyPI. Adding SSL to PyPI and certificate checking
to pip were big steps forward, but we need to make shipping and installing
modules securely even easier. I'm not sure whether that means developer
certificates or package signing or something else, but we need to find a
way to run only trusted code. As long as a one character typo can root your
box, the problem persists.
https://github.com/davidfischer/requestes
HOOK STDOUT: running egg_info
HOOK STDOUT: creating requestes.egg-info
HOOK STDOUT: writing requestes.egg-info/PKG-INFO
HOOK STDOUT: writing dependency_links to requestes.egg-info/dependency_links.txt
HOOK STDOUT: writing top-level names to requestes.egg-info/top_level.txt
HOOK STDOUT: writing manifest file 'requestes.egg-info/SOURCES.txt'
HOOK STDOUT: reading manifest file 'requestes.egg-info/SOURCES.txt'
HOOK STDOUT: writing manifest file 'requestes.egg-info/SOURCES.txt'
Handling wheel from get_requires_for_build_wheel
Requirement satisfied: wheel
   (installed: wheel 0.36.2)
Python Module Security Admonition
=================================
If you are reading this admonition while running pip, I'd like to take
this time to inform you that you just ran arbitrary code from the untrusted
internet (maybe even as root?). The fact that this was so easy is a bit of a
problem.
Remember when RubyGems.org got compromised and was down since they weren't
sure whether there were any problems with the gems themselves? That could
have just as easily been PyPI. Adding SSL to PyPI and certificate checking
to pip were big steps forward, but we need to make shipping and installing
modules securely even easier. I'm not sure whether that means developer
certificates or package signing or something else, but we need to find a
way to run only trusted code. As long as a one character typo can root your
box, the problem persists.
https://github.com/davidfischer/requestes
HOOK STDOUT: running dist_info
HOOK STDOUT: writing requestes.egg-info/PKG-INFO
HOOK STDOUT: writing dependency_links to requestes.egg-info/dependency_links.txt
HOOK STDOUT: writing top-level names to requestes.egg-info/top_level.txt
HOOK STDOUT: reading manifest file 'requestes.egg-info/SOURCES.txt'
HOOK STDOUT: writing manifest file 'requestes.egg-info/SOURCES.txt'
HOOK STDOUT: creating '/builddir/build/BUILD/requestes-0.0.1/requestes.dist-info'
+ RPM_EC=0
++ jobs -p
+ exit 0
Wrote: /builddir/build/SRPMS/python-requestes-0.0.1-1.el9.buildreqs.nosrc.rpm
Child return code was: 11
Dynamic buildrequires detected
Going to install missing buildrequires. See root.log for details.
ENTER ['do_with_status'](['bash', '--login', '-c', '/usr/bin/rpmbuild -ba --noprep --target x86_64 --nodeps /builddir/build/SPECS/python-requestes.spec'], chrootPath='/var/lib/mock/centos-stream+epel-9-x86_64-1647842008.070549/root'env={'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;<mock-chroot>\\007"', 'PS1': '<mock-chroot> \\s-\\v\\$ ', 'LANG': 'C.UTF-8'}shell=Falselogger=<mockbuild.trace_decorator.getLog object at 0x7fbf60717820>timeout=0uid=1000gid=135user='mockbuild'nspawn_args=['--capability=cap_ipc_lock', '--rlimit=RLIMIT_NOFILE=10240', '--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.33m4js9e:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11']unshare_net=TrueprintOutput=True)
Using nspawn with args ['--capability=cap_ipc_lock', '--rlimit=RLIMIT_NOFILE=10240', '--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.33m4js9e:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11']
Executing command: ['/usr/bin/systemd-nspawn', '-q', '-M', 'f5573ef221b64533a27ddea71a6f0d3c', '-D', '/var/lib/mock/centos-stream+epel-9-x86_64-1647842008.070549/root', '-a', '-u', 'mockbuild', '--capability=cap_ipc_lock', '--rlimit=RLIMIT_NOFILE=10240', '--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.33m4js9e:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11', '--console=pipe', '--setenv=TERM=vt100', '--setenv=SHELL=/bin/bash', '--setenv=HOME=/builddir', '--setenv=HOSTNAME=mock', '--setenv=PATH=/usr/bin:/bin:/usr/sbin:/sbin', '--setenv=PROMPT_COMMAND=printf "\\033]0;<mock-chroot>\\007"', '--setenv=PS1=<mock-chroot> \\s-\\v\\$ ', '--setenv=LANG=C.UTF-8', '--resolv-conf=off', 'bash', '--login', '-c', '/usr/bin/rpmbuild -ba --noprep --target x86_64 --nodeps /builddir/build/SPECS/python-requestes.spec'] with env {'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;<mock-chroot>\\007"', 'PS1': '<mock-chroot> \\s-\\v\\$ ', 'LANG': 'C.UTF-8', 'SYSTEMD_NSPAWN_TMPFS_TMP': '0', 'SYSTEMD_SECCOMP': '0'} and shell False
Building target platforms: x86_64
Building for target x86_64
setting SOURCE_DATE_EPOCH=1647734400
Executing(%generate_buildrequires): /bin/sh -e /var/tmp/rpm-tmp.TtNT4F
+ umask 022
+ cd /builddir/build/BUILD
+ cd requestes-0.0.1
+ echo pyproject-rpm-macros
+ echo python3-devel
+ echo 'python3dist(pip) >= 19'
+ echo 'python3dist(packaging)'
+ '[' -f pyproject.toml ']'
+ '[' -f setup.py ']'
+ echo 'python3dist(setuptools) >= 40.8'
+ echo 'python3dist(wheel)'
+ rm -rfv requestes.dist-info/
removed 'requestes.dist-info/METADATA'
removed 'requestes.dist-info/top_level.txt'
removed directory 'requestes.dist-info/'
+ '[' -f /usr/bin/python3 ']'
+ RPM_TOXENV=py39
+ HOSTNAME=rpmbuild
+ /usr/bin/python3 -s /usr/lib/rpm/redhat/pyproject_buildrequires.py --generate-extras --python3_pkgversion 3 -r
Handling setuptools >= 40.8 from default build backend
Requirement satisfied: setuptools >= 40.8
   (installed: setuptools 53.0.0)
Handling wheel from default build backend
Requirement satisfied: wheel
   (installed: wheel 0.36.2)
Python Module Security Admonition
=================================
If you are reading this admonition while running pip, I'd like to take
this time to inform you that you just ran arbitrary code from the untrusted
internet (maybe even as root?). The fact that this was so easy is a bit of a
problem.
Remember when RubyGems.org got compromised and was down since they weren't
sure whether there were any problems with the gems themselves? That could
have just as easily been PyPI. Adding SSL to PyPI and certificate checking
to pip were big steps forward, but we need to make shipping and installing
modules securely even easier. I'm not sure whether that means developer
certificates or package signing or something else, but we need to find a
way to run only trusted code. As long as a one character typo can root your
box, the problem persists.
https://github.com/davidfischer/requestes
HOOK STDOUT: running egg_info
HOOK STDOUT: creating requestes.egg-info
HOOK STDOUT: writing requestes.egg-info/PKG-INFO
HOOK STDOUT: writing dependency_links to requestes.egg-info/dependency_links.txt
HOOK STDOUT: writing top-level names to requestes.egg-info/top_level.txt
HOOK STDOUT: writing manifest file 'requestes.egg-info/SOURCES.txt'
HOOK STDOUT: reading manifest file 'requestes.egg-info/SOURCES.txt'
HOOK STDOUT: writing manifest file 'requestes.egg-info/SOURCES.txt'
Handling wheel from get_requires_for_build_wheel
Requirement satisfied: wheel
   (installed: wheel 0.36.2)
Python Module Security Admonition
=================================
If you are reading this admonition while running pip, I'd like to take
this time to inform you that you just ran arbitrary code from the untrusted
internet (maybe even as root?). The fact that this was so easy is a bit of a
problem.
Remember when RubyGems.org got compromised and was down since they weren't
sure whether there were any problems with the gems themselves? That could
have just as easily been PyPI. Adding SSL to PyPI and certificate checking
to pip were big steps forward, but we need to make shipping and installing
modules securely even easier. I'm not sure whether that means developer
certificates or package signing or something else, but we need to find a
way to run only trusted code. As long as a one character typo can root your
box, the problem persists.
https://github.com/davidfischer/requestes
HOOK STDOUT: running dist_info
HOOK STDOUT: writing requestes.egg-info/PKG-INFO
HOOK STDOUT: writing dependency_links to requestes.egg-info/dependency_links.txt
HOOK STDOUT: writing top-level names to requestes.egg-info/top_level.txt
HOOK STDOUT: reading manifest file 'requestes.egg-info/SOURCES.txt'
HOOK STDOUT: writing manifest file 'requestes.egg-info/SOURCES.txt'
HOOK STDOUT: creating '/builddir/build/BUILD/requestes-0.0.1/requestes.dist-info'
+ RPM_EC=0
++ jobs -p
+ exit 0
Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.eyC9gP
+ umask 022
+ cd /builddir/build/BUILD
+ cd requestes-0.0.1
+ mkdir -p /builddir/build/BUILD/requestes-0.0.1/.pyproject-builddir
+ CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -m64 -march=x86-64-v2 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection'
+ LDFLAGS='-Wl,-z,relro -Wl,--as-needed  -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 '
+ TMPDIR=/builddir/build/BUILD/requestes-0.0.1/.pyproject-builddir
+ /usr/bin/python3 -m pip wheel --wheel-dir /builddir/build/BUILD/requestes-0.0.1/pyproject-wheeldir --no-deps --use-pep517 --no-build-isolation --disable-pip-version-check --no-clean --progress-bar off --verbose .
Processing /builddir/build/BUILD/requestes-0.0.1
  Preparing metadata (pyproject.toml): started
  Running command Preparing metadata (pyproject.toml)
  Python Module Security Admonition
  =================================
  If you are reading this admonition while running pip, I'd like to take
  this time to inform you that you just ran arbitrary code from the untrusted
  internet (maybe even as root?). The fact that this was so easy is a bit of a
  problem.
  Remember when RubyGems.org got compromised and was down since they weren't
  sure whether there were any problems with the gems themselves? That could
  have just as easily been PyPI. Adding SSL to PyPI and certificate checking
  to pip were big steps forward, but we need to make shipping and installing
  modules securely even easier. I'm not sure whether that means developer
  certificates or package signing or something else, but we need to find a
  way to run only trusted code. As long as a one character typo can root your
  box, the problem persists.
  https://github.com/davidfischer/requestes
  running dist_info
  creating /builddir/build/BUILD/requestes-0.0.1/.pyproject-builddir/pip-modern-metadata-jniu3wfw/requestes.egg-info
  writing /builddir/build/BUILD/requestes-0.0.1/.pyproject-builddir/pip-modern-metadata-jniu3wfw/requestes.egg-info/PKG-INFO
  writing dependency_links to /builddir/build/BUILD/requestes-0.0.1/.pyproject-builddir/pip-modern-metadata-jniu3wfw/requestes.egg-info/dependency_links.txt
  writing top-level names to /builddir/build/BUILD/requestes-0.0.1/.pyproject-builddir/pip-modern-metadata-jniu3wfw/requestes.egg-info/top_level.txt
  writing manifest file '/builddir/build/BUILD/requestes-0.0.1/.pyproject-builddir/pip-modern-metadata-jniu3wfw/requestes.egg-info/SOURCES.txt'
  reading manifest file '/builddir/build/BUILD/requestes-0.0.1/.pyproject-builddir/pip-modern-metadata-jniu3wfw/requestes.egg-info/SOURCES.txt'
  writing manifest file '/builddir/build/BUILD/requestes-0.0.1/.pyproject-builddir/pip-modern-metadata-jniu3wfw/requestes.egg-info/SOURCES.txt'
  creating '/builddir/build/BUILD/requestes-0.0.1/.pyproject-builddir/pip-modern-metadata-jniu3wfw/requestes.dist-info'
  Preparing metadata (pyproject.toml): finished with status 'done'
Building wheels for collected packages: requestes
  Building wheel for requestes (pyproject.toml): started
  Running command Building wheel for requestes (pyproject.toml)
  Python Module Security Admonition
  =================================
  If you are reading this admonition while running pip, I'd like to take
  this time to inform you that you just ran arbitrary code from the untrusted
  internet (maybe even as root?). The fact that this was so easy is a bit of a
  problem.
  Remember when RubyGems.org got compromised and was down since they weren't
  sure whether there were any problems with the gems themselves? That could
  have just as easily been PyPI. Adding SSL to PyPI and certificate checking
  to pip were big steps forward, but we need to make shipping and installing
  modules securely even easier. I'm not sure whether that means developer
  certificates or package signing or something else, but we need to find a
  way to run only trusted code. As long as a one character typo can root your
  box, the problem persists.
  https://github.com/davidfischer/requestes
  running bdist_wheel
  running build
  running build_py
  creating build
  creating build/lib
  creating build/lib/requestes
  copying requestes/__init__.py -> build/lib/requestes
  installing to build/bdist.linux-x86_64/wheel
  running install
  running install_lib
  creating build/bdist.linux-x86_64
  creating build/bdist.linux-x86_64/wheel
  creating build/bdist.linux-x86_64/wheel/requestes
  copying build/lib/requestes/__init__.py -> build/bdist.linux-x86_64/wheel/requestes
  running install_egg_info
  running egg_info
  creating requestes.egg-info
  writing requestes.egg-info/PKG-INFO
  writing dependency_links to requestes.egg-info/dependency_links.txt
  writing top-level names to requestes.egg-info/top_level.txt
  writing manifest file 'requestes.egg-info/SOURCES.txt'
  reading manifest file 'requestes.egg-info/SOURCES.txt'
  writing manifest file 'requestes.egg-info/SOURCES.txt'
  Copying requestes.egg-info to build/bdist.linux-x86_64/wheel/requestes-0.0.1-py3.9.egg-info
  running install_scripts
  creating build/bdist.linux-x86_64/wheel/requestes-0.0.1.dist-info/WHEEL
  creating '/builddir/build/BUILD/requestes-0.0.1/.pyproject-builddir/pip-wheel-bwn72tp6/tmpt7cdpohm/requestes-0.0.1-py3-none-any.whl' and adding 'build/bdist.linux-x86_64/wheel' to it
  adding 'requestes/__init__.py'
  adding 'requestes-0.0.1.dist-info/METADATA'
  adding 'requestes-0.0.1.dist-info/WHEEL'
  adding 'requestes-0.0.1.dist-info/top_level.txt'
  adding 'requestes-0.0.1.dist-info/RECORD'
  removing build/bdist.linux-x86_64/wheel
  Building wheel for requestes (pyproject.toml): finished with status 'done'
  Created wheel for requestes: filename=requestes-0.0.1-py3-none-any.whl size=1855 sha256=8dba65a74041a01ab56f16472f0ae10a81e886d9d02ac3f9bcc0a27f824d7117
  Stored in directory: /builddir/.cache/pip/wheels/6e/e4/0e/09ded1342bb85cfe8c22f2a9ec96cc0b98b3474e5e0da7e8c4
Successfully built requestes
+ RPM_EC=0
++ jobs -p
+ exit 0
Executing(%install): /bin/sh -e /var/tmp/rpm-tmp.GugpTn
+ umask 022
+ cd /builddir/build/BUILD
+ '[' /builddir/build/BUILDROOT/python-requestes-0.0.1-1.el9.x86_64 '!=' / ']'
+ rm -rf /builddir/build/BUILDROOT/python-requestes-0.0.1-1.el9.x86_64
++ dirname /builddir/build/BUILDROOT/python-requestes-0.0.1-1.el9.x86_64
+ mkdir -p /builddir/build/BUILDROOT
+ mkdir /builddir/build/BUILDROOT/python-requestes-0.0.1-1.el9.x86_64
+ cd requestes-0.0.1
++ ls /builddir/build/BUILD/requestes-0.0.1/pyproject-wheeldir/requestes-0.0.1-py3-none-any.whl
++ sed -E 's/([^-]+)-([^-]+)-.+\.whl/\1==\2/'
++ xargs basename --multiple
+ specifier=requestes==0.0.1
+ TMPDIR=/builddir/build/BUILD/requestes-0.0.1/.pyproject-builddir
+ /usr/bin/python3 -m pip install --root /builddir/build/BUILDROOT/python-requestes-0.0.1-1.el9.x86_64 --no-deps --disable-pip-version-check --progress-bar off --verbose --ignore-installed --no-warn-script-location --no-index --no-cache-dir --find-links /builddir/build/BUILD/requestes-0.0.1/pyproject-wheeldir requestes==0.0.1
Using pip 22.0.4 from /usr/lib/python3.9/site-packages/pip (python 3.9)
Looking in links: /builddir/build/BUILD/requestes-0.0.1/pyproject-wheeldir
Processing ./pyproject-wheeldir/requestes-0.0.1-py3-none-any.whl
Installing collected packages: requestes
Successfully installed requestes-0.0.1
+ '[' -d /builddir/build/BUILDROOT/python-requestes-0.0.1-1.el9.x86_64/usr/bin ']'
+ rm -f /builddir/build/BUILD/pyproject-ghost-distinfo
+ site_dirs=()
+ '[' -d /builddir/build/BUILDROOT/python-requestes-0.0.1-1.el9.x86_64/usr/lib/python3.9/site-packages ']'
+ site_dirs+=("/usr/lib/python3.9/site-packages")
+ '[' /builddir/build/BUILDROOT/python-requestes-0.0.1-1.el9.x86_64/usr/lib64/python3.9/site-packages '!=' /builddir/build/BUILDROOT/python-requestes-0.0.1-1.el9.x86_64/usr/lib/python3.9/site-packages ']'
+ '[' -d /builddir/build/BUILDROOT/python-requestes-0.0.1-1.el9.x86_64/usr/lib64/python3.9/site-packages ']'
+ for site_dir in ${site_dirs[@]}
+ for distinfo in /builddir/build/BUILDROOT/python-requestes-0.0.1-1.el9.x86_64$site_dir/*.dist-info
+ echo '%ghost /usr/lib/python3.9/site-packages/requestes-0.0.1.dist-info'
+ sed -i s/pip/rpm/ /builddir/build/BUILDROOT/python-requestes-0.0.1-1.el9.x86_64/usr/lib/python3.9/site-packages/requestes-0.0.1.dist-info/INSTALLER
+ PYTHONPATH=/usr/lib/rpm/redhat
+ /usr/bin/python3 -B /usr/lib/rpm/redhat/pyproject_preprocess_record.py --buildroot /builddir/build/BUILDROOT/python-requestes-0.0.1-1.el9.x86_64 --record /builddir/build/BUILDROOT/python-requestes-0.0.1-1.el9.x86_64/usr/lib/python3.9/site-packages/requestes-0.0.1.dist-info/RECORD --output /builddir/build/BUILD/pyproject-record
+ rm -fv /builddir/build/BUILDROOT/python-requestes-0.0.1-1.el9.x86_64/usr/lib/python3.9/site-packages/requestes-0.0.1.dist-info/RECORD
removed '/builddir/build/BUILDROOT/python-requestes-0.0.1-1.el9.x86_64/usr/lib/python3.9/site-packages/requestes-0.0.1.dist-info/RECORD'
+ rm -fv /builddir/build/BUILDROOT/python-requestes-0.0.1-1.el9.x86_64/usr/lib/python3.9/site-packages/requestes-0.0.1.dist-info/REQUESTED
removed '/builddir/build/BUILDROOT/python-requestes-0.0.1-1.el9.x86_64/usr/lib/python3.9/site-packages/requestes-0.0.1.dist-info/REQUESTED'
++ wc -l /builddir/build/BUILD/pyproject-ghost-distinfo
++ cut -f1 '-d '
+ lines=1
+ '[' 1 -ne 1 ']'
+ /usr/bin/python3 /usr/lib/rpm/redhat/pyproject_save_files.py --output-files /builddir/build/BUILD/pyproject-files --output-modules /builddir/build/BUILD/pyproject-modules --buildroot /builddir/build/BUILDROOT/python-requestes-0.0.1-1.el9.x86_64 --sitelib /usr/lib/python3.9/site-packages --sitearch /usr/lib64/python3.9/site-packages --python-version 3.9 --pyproject-record /builddir/build/BUILD/pyproject-record --prefix /usr '*' +auto
+ /usr/lib/rpm/find-debuginfo.sh -j2 --strict-build-id -m -i --build-id-seed 0.0.1-1.el9 --unique-debug-suffix -0.0.1-1.el9.x86_64 --unique-debug-src-base python-requestes-0.0.1-1.el9.x86_64 --run-dwz --dwz-low-mem-die-limit 10000000 --dwz-max-die-limit 110000000 -S debugsourcefiles.list /builddir/build/BUILD/requestes-0.0.1
find: 'debug': No such file or directory
+ /usr/lib/rpm/check-buildroot
+ /usr/lib/rpm/redhat/brp-ldconfig
+ /usr/lib/rpm/brp-compress
+ /usr/lib/rpm/redhat/brp-strip-lto /usr/bin/strip
+ /usr/lib/rpm/brp-strip-static-archive /usr/bin/strip
+ /usr/lib/rpm/redhat/brp-python-bytecompile '' 1 0
Bytecompiling .py files below /builddir/build/BUILDROOT/python-requestes-0.0.1-1.el9.x86_64/usr/lib/python3.9 using python3.9
+ /usr/lib/rpm/brp-python-hardlink
+ /usr/lib/rpm/redhat/brp-mangle-shebangs
Executing(%check): /bin/sh -e /var/tmp/rpm-tmp.cllnxU
+ umask 022
+ cd /builddir/build/BUILD
+ cd requestes-0.0.1
+ '[' '!' -f /builddir/build/BUILD/pyproject-modules ']'
+ PATH=/builddir/build/BUILDROOT/python-requestes-0.0.1-1.el9.x86_64/usr/bin:/builddir/.local/bin:/builddir/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/sbin
+ PYTHONPATH=/builddir/build/BUILDROOT/python-requestes-0.0.1-1.el9.x86_64/usr/lib64/python3.9/site-packages:/builddir/build/BUILDROOT/python-requestes-0.0.1-1.el9.x86_64/usr/lib/python3.9/site-packages
+ _PYTHONSITE=/builddir/build/BUILDROOT/python-requestes-0.0.1-1.el9.x86_64/usr/lib64/python3.9/site-packages:/builddir/build/BUILDROOT/python-requestes-0.0.1-1.el9.x86_64/usr/lib/python3.9/site-packages
+ PYTHONDONTWRITEBYTECODE=1
+ /usr/bin/python3 -s /usr/lib/rpm/redhat/import_all_modules.py -f /builddir/build/BUILD/pyproject-modules -t
Check import: requestes
+ RPM_EC=0
++ jobs -p
+ exit 0
Processing files: python3-requestes-0.0.1-1.el9.noarch
Provides: python-requestes = 0.0.1-1.el9 python3-requestes = 0.0.1-1.el9 python3.9-requestes = 0.0.1-1.el9 python3.9dist(requestes) = 0.0.1 python3dist(requestes) = 0.0.1
Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PartialHardlinkSets) <= 4.0.4-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1
Requires: python(abi) = 3.9
Obsoletes: python39-requestes < 0.0.1-1.el9
Checking for unpackaged file(s): /usr/lib/rpm/check-files /builddir/build/BUILDROOT/python-requestes-0.0.1-1.el9.x86_64
Wrote: /builddir/build/SRPMS/python-requestes-0.0.1-1.el9.src.rpm
Wrote: /builddir/build/RPMS/python3-requestes-0.0.1-1.el9.noarch.rpm
Executing(%clean): /bin/sh -e /var/tmp/rpm-tmp.wWuq0T
+ umask 022
+ cd /builddir/build/BUILD
+ cd requestes-0.0.1
+ /usr/bin/rm -rf /builddir/build/BUILDROOT/python-requestes-0.0.1-1.el9.x86_64
+ RPM_EC=0
++ jobs -p
+ exit 0
Child return code was: 0