Mock Version: 3.5 ENTER ['do_with_status'](['bash', '--login', '-c', '/usr/bin/rpmbuild -bs --target x86_64 --nodeps /builddir/build/SPECS/python-stylist.spec'], chrootPath='/var/lib/mock/fedora-rawhide-x86_64-1682443252.252062/root'env={'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\s-\\v\\$ ', 'LANG': 'C.UTF-8'}shell=Falselogger=timeout=0uid=1000gid=135user='mockbuild'nspawn_args=['--capability=cap_ipc_lock', '--rlimit=RLIMIT_NOFILE=10240', '--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.pl_ch5qh:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/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.pl_ch5qh:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/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', 'ddf9e60d25f24ee08ceee46b15512a88', '-D', '/var/lib/mock/fedora-rawhide-x86_64-1682443252.252062/root', '-a', '-u', 'mockbuild', '--capability=cap_ipc_lock', '--rlimit=RLIMIT_NOFILE=10240', '--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.pl_ch5qh:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/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;\\007"', '--setenv=PS1= \\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-stylist.spec'] with env {'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\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=1682380800 Wrote: /builddir/build/SRPMS/python-stylist-0.4.0-1.fc39.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-stylist.spec'], chrootPath='/var/lib/mock/fedora-rawhide-x86_64-1682443252.252062/root'env={'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\s-\\v\\$ ', 'LANG': 'C.UTF-8'}shell=Falselogger=timeout=0uid=1000gid=135user='mockbuild'nspawn_args=['--capability=cap_ipc_lock', '--rlimit=RLIMIT_NOFILE=10240', '--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.pl_ch5qh:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/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.pl_ch5qh:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/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', '31e64344a1cb46c0b6311001a21a2ed3', '-D', '/var/lib/mock/fedora-rawhide-x86_64-1682443252.252062/root', '-a', '-u', 'mockbuild', '--capability=cap_ipc_lock', '--rlimit=RLIMIT_NOFILE=10240', '--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.pl_ch5qh:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/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;\\007"', '--setenv=PS1= \\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-stylist.spec'] with env {'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\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=1682380800 Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.GRBxWj + umask 022 + cd /builddir/build/BUILD + cd /builddir/build/BUILD + rm -rf stylist-0.4.0 + /usr/lib/rpm/rpmuncompress -x /builddir/build/SOURCES/stylist-0.4.0.tar.gz + STATUS=0 + '[' 0 -ne 0 ']' + cd stylist-0.4.0 + /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.SlXsmA + umask 022 + cd /builddir/build/BUILD + cd stylist-0.4.0 + CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer ' + export CFLAGS + CXXFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer ' + export CXXFLAGS + FFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules ' + export FFLAGS + FCFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules ' + export FCFLAGS + VALAFLAGS=-g + export VALAFLAGS + RUSTFLAGS='-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cforce-frame-pointers=yes -Clink-arg=-Wl,-z,relro -Clink-arg=-Wl,-z,now --cap-lints=warn' + export RUSTFLAGS + 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 -Wl,--build-id=sha1 ' + export LDFLAGS + LT_SYS_LIBRARY_PATH=/usr/lib64: + export LT_SYS_LIBRARY_PATH + CC=gcc + export CC + CXX=g++ + export CXX + echo pyproject-rpm-macros + echo python3-devel + echo 'python3dist(pip) >= 19' + echo 'python3dist(packaging)' + '[' -f pyproject.toml ']' + echo '(python3dist(toml) if python3-devel < 3.11)' + rm -rfv '*.dist-info/' + '[' -f /usr/bin/python3 ']' + mkdir -p /builddir/build/BUILD/stylist-0.4.0/.pyproject-builddir + echo -n + CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer ' + 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 -Wl,--build-id=sha1 ' + TMPDIR=/builddir/build/BUILD/stylist-0.4.0/.pyproject-builddir + RPM_TOXENV=py311 + HOSTNAME=rpmbuild + /usr/bin/python3 -Bs /usr/lib/rpm/redhat/pyproject_buildrequires.py --generate-extras --python3_pkgversion 3 --wheeldir /builddir/build/BUILD/stylist-0.4.0/pyproject-wheeldir --output /builddir/build/BUILD/python-stylist-0.4.0-1.fc39.x86_64-pyproject-buildrequires Handling setuptools from build-system.requires Requirement not satisfied: setuptools Exiting dependency generation pass: build backend + cat /builddir/build/BUILD/python-stylist-0.4.0-1.fc39.x86_64-pyproject-buildrequires + rm -rfv '*.dist-info/' + RPM_EC=0 ++ jobs -p + exit 0 Wrote: /builddir/build/SRPMS/python-stylist-0.4.0-1.fc39.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-stylist.spec'], chrootPath='/var/lib/mock/fedora-rawhide-x86_64-1682443252.252062/root'env={'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\s-\\v\\$ ', 'LANG': 'C.UTF-8'}shell=Falselogger=timeout=0uid=1000gid=135user='mockbuild'nspawn_args=['--capability=cap_ipc_lock', '--rlimit=RLIMIT_NOFILE=10240', '--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.pl_ch5qh:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/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.pl_ch5qh:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/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', 'd4a0a73aad014040b73cae5ffe59c910', '-D', '/var/lib/mock/fedora-rawhide-x86_64-1682443252.252062/root', '-a', '-u', 'mockbuild', '--capability=cap_ipc_lock', '--rlimit=RLIMIT_NOFILE=10240', '--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.pl_ch5qh:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/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;\\007"', '--setenv=PS1= \\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-stylist.spec'] with env {'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\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=1682380800 Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.4gNGTr + umask 022 + cd /builddir/build/BUILD + cd /builddir/build/BUILD + rm -rf stylist-0.4.0 + /usr/lib/rpm/rpmuncompress -x /builddir/build/SOURCES/stylist-0.4.0.tar.gz + STATUS=0 + '[' 0 -ne 0 ']' + cd stylist-0.4.0 + /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.Y2mShJ + umask 022 + cd /builddir/build/BUILD + cd stylist-0.4.0 + CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer ' + export CFLAGS + CXXFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer ' + export CXXFLAGS + FFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules ' + export FFLAGS + FCFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules ' + export FCFLAGS + VALAFLAGS=-g + export VALAFLAGS + RUSTFLAGS='-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cforce-frame-pointers=yes -Clink-arg=-Wl,-z,relro -Clink-arg=-Wl,-z,now --cap-lints=warn' + export RUSTFLAGS + 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 -Wl,--build-id=sha1 ' + export LDFLAGS + LT_SYS_LIBRARY_PATH=/usr/lib64: + export LT_SYS_LIBRARY_PATH + CC=gcc + export CC + CXX=g++ + export CXX + echo pyproject-rpm-macros + echo python3-devel + echo 'python3dist(pip) >= 19' + echo 'python3dist(packaging)' + '[' -f pyproject.toml ']' + echo '(python3dist(toml) if python3-devel < 3.11)' + rm -rfv '*.dist-info/' + '[' -f /usr/bin/python3 ']' + mkdir -p /builddir/build/BUILD/stylist-0.4.0/.pyproject-builddir + echo -n + CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer ' + 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 -Wl,--build-id=sha1 ' + TMPDIR=/builddir/build/BUILD/stylist-0.4.0/.pyproject-builddir + RPM_TOXENV=py311 + HOSTNAME=rpmbuild + /usr/bin/python3 -Bs /usr/lib/rpm/redhat/pyproject_buildrequires.py --generate-extras --python3_pkgversion 3 --wheeldir /builddir/build/BUILD/stylist-0.4.0/pyproject-wheeldir --output /builddir/build/BUILD/python-stylist-0.4.0-1.fc39.x86_64-pyproject-buildrequires Handling setuptools from build-system.requires Requirement satisfied: setuptools (installed: setuptools 67.7.2) /usr/lib/python3.11/site-packages/setuptools/config/pyprojecttoml.py:66: _BetaConfiguration: Support for `[tool.setuptools]` in `pyproject.toml` is still *beta*. config = read_configuration(filepath, True, ignore_option_errors, dist) /usr/lib/python3.11/site-packages/setuptools/config/_apply_pyprojecttoml.py:62: _WouldIgnoreField: `readme` defined outside of `pyproject.toml` would be ignored. !! ******************************************************************************** ########################################################################## # configuration would be ignored/result in error due to `pyproject.toml` # ########################################################################## The following seems to be defined outside of `pyproject.toml`: `readme = 'Stylist\n=======\n\n|BSD3 License| |GitHub release| |PyPI version| |Conda version| |GitHub merge testing|\n\nStylist is a tool for checking code style. It implements a framework which\nsupports multiple styles across multiple languages.\n\nBut aren\'t there many such tools out there, why create a new one?\n\nThe simple reason is that few of them support Fortran, a language still in\nwidespread use in the scientific computing domain. They can also tend towards\nthe zealous when enforcing the "one true style" whereas long running science\nmodels tend to diverge quite radically in what they like, style-wise.\n\nLarge models also tend to be implemented using more than one language so a\ntool which is capable of understanding all of them would be welcomed by\nscience developers.\n\nThis is the goal of Stylist development.\n\nThe project is still in its infancy so only a few rules have been implemented\nand only for Fortran. Stubs are provided to show how it might be extended to\nsupport C.\n\nFind the project at \n\n.. |BSD3 License| image:: https://img.shields.io/badge/License-BSD_3--Clause-blue.svg\n :target: https://opensource.org/licenses/BSD-3-Clause\n\n.. |GitHub release| image:: https://img.shields.io/github/release/MetOffice/stylist.svg\n :target: https://github.com/MetOffice/stylist/\n\n.. |PyPI version| image:: https://badge.fury.io/py/stylist.svg\n :target: https://pypi.python.org/pypi/stylist/\n\n.. |Conda version| image:: https://img.shields.io/conda/vn/conda-forge/stylist.svg\n :target: https://anaconda.org/conda-forge/stylist\n\n.. |GitHub merge testing| image:: https://github.com/MetOffice/stylist/workflows/Merge%20Test/badge.svg\n :target: https://github.com/MetOffice/stylist/actions\n\n\nInstallation\n~~~~~~~~~~~~\n\nInstallation can be as simple as ``pip install stylist`` or\n``conda install -c conda-forge stylist``.\n\nAs always it is also possible to install from the project source using\n``pip install --editable .``. The source may be obtained by downloading a\ntarball or by cloning the repository.\n\n\nUsage\n~~~~~\n\nStylist provides a command-line tool ``stylist`` for normal use. It can also be\nused as a package if you want to integrate it with another tool. Documentation\nregarding this second option is maintained in the project wiki.\n\nOn the Command Line\n-------------------\n\nThe command-line tool is not complicated to use::\n\n stylist [-help] [-verbose]\n [-configuration FILENAME]\n [-style NAME]\n FILE ...\n\nThe only required arguments are a configuration file and one or more\nfilenames. These are the files which will be checked. If a directory is\nspecified then the tool will automatically descend into it checking all files\nwhich it recognises by extension.\n\nIf you want a running commentary of what the tool is doing then use the\n``-verbose`` argument.\n\nA configuration file may specified with ``-configuration`` . This file should\nbe formatted as documented below. There must be a configuration file which\ndefines at least one style. While the fallback mechanism which allows for user\nand site configurations has not been implemented it must be specified with this\nargument.\n\nThe configuration may define several styles, in which case one can be chosen\nusing the ``-style`` argument. If it is not then the first in the configuration\nfile will be used.\n\nConfiguration File\n------------------\n\nThe configuration file is a simple python script where variable definitions\nare used to define the configuration.\n\nStylist uses the concept of "File Pipes" to specify the series of steps needed\nto process a particular file type. They are defined by creating a ``FilePipe``\nobject and associated with a file extension by assignment to a variable.\n\nFor example::\n\n from stylist.source import (FilePipe,\n FortranSource,\n PFUnitProcessor,\n FortranPreprocessor)\n \n pf = FilePipe(FortranSource, PFUnitProcessor, FortranPreprocessor)\n\nHere a pipeline consisting the pFUnit processor followed by the Fortran\npreprocessor produces Fortran source. This pipeline should be used for all\nfiles with the ``.pf`` extension.\n\nStyles are collections of rules and are defined in a similar way. The variable\nname is the style name and the object is constructed with the rules which make up the style.\n\nAn illustrative example::\n\n from re import compile as recompile\n from stylist.style import Style\n from stylist.fortran import FortranCharacterset, KindPattern\n \n simple = Style(FortranCharacterset(),\n KindPattern(integer=recompile(r\'i_.+\'),\n real=recompile(r\'r_.+\')))\n'` According to the spec (see the link below), however, setuptools CANNOT consider this value unless `readme` is listed as `dynamic`. https://packaging.python.org/en/latest/specifications/declaring-project-metadata/ For the time being, `setuptools` will still consider the given value (as a **transitional** measure), but please note that future releases of setuptools will follow strictly the standard. To prevent this warning, you can list `readme` under `dynamic` or alternatively remove the `[project]` table from your file and rely entirely on other means of configuration. By 2023-Oct-30, you need to update your project and remove deprecated calls or your builds will no longer be supported. ******************************************************************************** !! _handle_missing_dynamic(dist, project_table) /usr/lib/python3.11/site-packages/setuptools/config/_apply_pyprojecttoml.py:62: _WouldIgnoreField: `authors` defined outside of `pyproject.toml` would be ignored. !! ******************************************************************************** ########################################################################## # configuration would be ignored/result in error due to `pyproject.toml` # ########################################################################## The following seems to be defined outside of `pyproject.toml`: `authors = 'Met Office'` According to the spec (see the link below), however, setuptools CANNOT consider this value unless `authors` is listed as `dynamic`. https://packaging.python.org/en/latest/specifications/declaring-project-metadata/ For the time being, `setuptools` will still consider the given value (as a **transitional** measure), but please note that future releases of setuptools will follow strictly the standard. To prevent this warning, you can list `authors` under `dynamic` or alternatively remove the `[project]` table from your file and rely entirely on other means of configuration. By 2023-Oct-30, you need to update your project and remove deprecated calls or your builds will no longer be supported. ******************************************************************************** !! _handle_missing_dynamic(dist, project_table) /usr/lib/python3.11/site-packages/setuptools/config/_apply_pyprojecttoml.py:62: _WouldIgnoreField: `keywords` defined outside of `pyproject.toml` would be ignored. !! ******************************************************************************** ########################################################################## # configuration would be ignored/result in error due to `pyproject.toml` # ########################################################################## The following seems to be defined outside of `pyproject.toml`: `keywords = ['linter fortran psyclone']` According to the spec (see the link below), however, setuptools CANNOT consider this value unless `keywords` is listed as `dynamic`. https://packaging.python.org/en/latest/specifications/declaring-project-metadata/ For the time being, `setuptools` will still consider the given value (as a **transitional** measure), but please note that future releases of setuptools will follow strictly the standard. To prevent this warning, you can list `keywords` under `dynamic` or alternatively remove the `[project]` table from your file and rely entirely on other means of configuration. By 2023-Oct-30, you need to update your project and remove deprecated calls or your builds will no longer be supported. ******************************************************************************** !! _handle_missing_dynamic(dist, project_table) running egg_info writing source/stylist.egg-info/PKG-INFO writing dependency_links to source/stylist.egg-info/dependency_links.txt writing entry points to source/stylist.egg-info/entry_points.txt writing requirements to source/stylist.egg-info/requires.txt writing top-level names to source/stylist.egg-info/top_level.txt reading manifest file 'source/stylist.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' adding license file 'LICENSE' writing manifest file 'source/stylist.egg-info/SOURCES.txt' Handling wheel from get_requires_for_build_wheel Requirement not satisfied: wheel Exiting dependency generation pass: get_requires_for_build_wheel + cat /builddir/build/BUILD/python-stylist-0.4.0-1.fc39.x86_64-pyproject-buildrequires + rm -rfv '*.dist-info/' + RPM_EC=0 ++ jobs -p + exit 0 Wrote: /builddir/build/SRPMS/python-stylist-0.4.0-1.fc39.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-stylist.spec'], chrootPath='/var/lib/mock/fedora-rawhide-x86_64-1682443252.252062/root'env={'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\s-\\v\\$ ', 'LANG': 'C.UTF-8'}shell=Falselogger=timeout=0uid=1000gid=135user='mockbuild'nspawn_args=['--capability=cap_ipc_lock', '--rlimit=RLIMIT_NOFILE=10240', '--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.pl_ch5qh:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/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.pl_ch5qh:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/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', '4ae470019114443190e0512fc8d78a14', '-D', '/var/lib/mock/fedora-rawhide-x86_64-1682443252.252062/root', '-a', '-u', 'mockbuild', '--capability=cap_ipc_lock', '--rlimit=RLIMIT_NOFILE=10240', '--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.pl_ch5qh:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/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;\\007"', '--setenv=PS1= \\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-stylist.spec'] with env {'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\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=1682380800 Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.5Jrhtc + umask 022 + cd /builddir/build/BUILD + cd /builddir/build/BUILD + rm -rf stylist-0.4.0 + /usr/lib/rpm/rpmuncompress -x /builddir/build/SOURCES/stylist-0.4.0.tar.gz + STATUS=0 + '[' 0 -ne 0 ']' + cd stylist-0.4.0 + /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.zru3Bj + umask 022 + cd /builddir/build/BUILD + cd stylist-0.4.0 + CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer ' + export CFLAGS + CXXFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer ' + export CXXFLAGS + FFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules ' + export FFLAGS + FCFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules ' + export FCFLAGS + VALAFLAGS=-g + export VALAFLAGS + RUSTFLAGS='-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cforce-frame-pointers=yes -Clink-arg=-Wl,-z,relro -Clink-arg=-Wl,-z,now --cap-lints=warn' + export RUSTFLAGS + 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 -Wl,--build-id=sha1 ' + export LDFLAGS + LT_SYS_LIBRARY_PATH=/usr/lib64: + export LT_SYS_LIBRARY_PATH + CC=gcc + export CC + CXX=g++ + export CXX + echo pyproject-rpm-macros + echo python3-devel + echo 'python3dist(pip) >= 19' + echo 'python3dist(packaging)' + '[' -f pyproject.toml ']' + echo '(python3dist(toml) if python3-devel < 3.11)' + rm -rfv '*.dist-info/' + '[' -f /usr/bin/python3 ']' + mkdir -p /builddir/build/BUILD/stylist-0.4.0/.pyproject-builddir + echo -n + CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer ' + 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 -Wl,--build-id=sha1 ' + TMPDIR=/builddir/build/BUILD/stylist-0.4.0/.pyproject-builddir + RPM_TOXENV=py311 + HOSTNAME=rpmbuild + /usr/bin/python3 -Bs /usr/lib/rpm/redhat/pyproject_buildrequires.py --generate-extras --python3_pkgversion 3 --wheeldir /builddir/build/BUILD/stylist-0.4.0/pyproject-wheeldir --output /builddir/build/BUILD/python-stylist-0.4.0-1.fc39.x86_64-pyproject-buildrequires Handling setuptools from build-system.requires Requirement satisfied: setuptools (installed: setuptools 67.7.2) /usr/lib/python3.11/site-packages/setuptools/config/pyprojecttoml.py:66: _BetaConfiguration: Support for `[tool.setuptools]` in `pyproject.toml` is still *beta*. config = read_configuration(filepath, True, ignore_option_errors, dist) /usr/lib/python3.11/site-packages/setuptools/config/_apply_pyprojecttoml.py:62: _WouldIgnoreField: `readme` defined outside of `pyproject.toml` would be ignored. !! ******************************************************************************** ########################################################################## # configuration would be ignored/result in error due to `pyproject.toml` # ########################################################################## The following seems to be defined outside of `pyproject.toml`: `readme = 'Stylist\n=======\n\n|BSD3 License| |GitHub release| |PyPI version| |Conda version| |GitHub merge testing|\n\nStylist is a tool for checking code style. It implements a framework which\nsupports multiple styles across multiple languages.\n\nBut aren\'t there many such tools out there, why create a new one?\n\nThe simple reason is that few of them support Fortran, a language still in\nwidespread use in the scientific computing domain. They can also tend towards\nthe zealous when enforcing the "one true style" whereas long running science\nmodels tend to diverge quite radically in what they like, style-wise.\n\nLarge models also tend to be implemented using more than one language so a\ntool which is capable of understanding all of them would be welcomed by\nscience developers.\n\nThis is the goal of Stylist development.\n\nThe project is still in its infancy so only a few rules have been implemented\nand only for Fortran. Stubs are provided to show how it might be extended to\nsupport C.\n\nFind the project at \n\n.. |BSD3 License| image:: https://img.shields.io/badge/License-BSD_3--Clause-blue.svg\n :target: https://opensource.org/licenses/BSD-3-Clause\n\n.. |GitHub release| image:: https://img.shields.io/github/release/MetOffice/stylist.svg\n :target: https://github.com/MetOffice/stylist/\n\n.. |PyPI version| image:: https://badge.fury.io/py/stylist.svg\n :target: https://pypi.python.org/pypi/stylist/\n\n.. |Conda version| image:: https://img.shields.io/conda/vn/conda-forge/stylist.svg\n :target: https://anaconda.org/conda-forge/stylist\n\n.. |GitHub merge testing| image:: https://github.com/MetOffice/stylist/workflows/Merge%20Test/badge.svg\n :target: https://github.com/MetOffice/stylist/actions\n\n\nInstallation\n~~~~~~~~~~~~\n\nInstallation can be as simple as ``pip install stylist`` or\n``conda install -c conda-forge stylist``.\n\nAs always it is also possible to install from the project source using\n``pip install --editable .``. The source may be obtained by downloading a\ntarball or by cloning the repository.\n\n\nUsage\n~~~~~\n\nStylist provides a command-line tool ``stylist`` for normal use. It can also be\nused as a package if you want to integrate it with another tool. Documentation\nregarding this second option is maintained in the project wiki.\n\nOn the Command Line\n-------------------\n\nThe command-line tool is not complicated to use::\n\n stylist [-help] [-verbose]\n [-configuration FILENAME]\n [-style NAME]\n FILE ...\n\nThe only required arguments are a configuration file and one or more\nfilenames. These are the files which will be checked. If a directory is\nspecified then the tool will automatically descend into it checking all files\nwhich it recognises by extension.\n\nIf you want a running commentary of what the tool is doing then use the\n``-verbose`` argument.\n\nA configuration file may specified with ``-configuration`` . This file should\nbe formatted as documented below. There must be a configuration file which\ndefines at least one style. While the fallback mechanism which allows for user\nand site configurations has not been implemented it must be specified with this\nargument.\n\nThe configuration may define several styles, in which case one can be chosen\nusing the ``-style`` argument. If it is not then the first in the configuration\nfile will be used.\n\nConfiguration File\n------------------\n\nThe configuration file is a simple python script where variable definitions\nare used to define the configuration.\n\nStylist uses the concept of "File Pipes" to specify the series of steps needed\nto process a particular file type. They are defined by creating a ``FilePipe``\nobject and associated with a file extension by assignment to a variable.\n\nFor example::\n\n from stylist.source import (FilePipe,\n FortranSource,\n PFUnitProcessor,\n FortranPreprocessor)\n \n pf = FilePipe(FortranSource, PFUnitProcessor, FortranPreprocessor)\n\nHere a pipeline consisting the pFUnit processor followed by the Fortran\npreprocessor produces Fortran source. This pipeline should be used for all\nfiles with the ``.pf`` extension.\n\nStyles are collections of rules and are defined in a similar way. The variable\nname is the style name and the object is constructed with the rules which make up the style.\n\nAn illustrative example::\n\n from re import compile as recompile\n from stylist.style import Style\n from stylist.fortran import FortranCharacterset, KindPattern\n \n simple = Style(FortranCharacterset(),\n KindPattern(integer=recompile(r\'i_.+\'),\n real=recompile(r\'r_.+\')))\n'` According to the spec (see the link below), however, setuptools CANNOT consider this value unless `readme` is listed as `dynamic`. https://packaging.python.org/en/latest/specifications/declaring-project-metadata/ For the time being, `setuptools` will still consider the given value (as a **transitional** measure), but please note that future releases of setuptools will follow strictly the standard. To prevent this warning, you can list `readme` under `dynamic` or alternatively remove the `[project]` table from your file and rely entirely on other means of configuration. By 2023-Oct-30, you need to update your project and remove deprecated calls or your builds will no longer be supported. ******************************************************************************** !! _handle_missing_dynamic(dist, project_table) /usr/lib/python3.11/site-packages/setuptools/config/_apply_pyprojecttoml.py:62: _WouldIgnoreField: `authors` defined outside of `pyproject.toml` would be ignored. !! ******************************************************************************** ########################################################################## # configuration would be ignored/result in error due to `pyproject.toml` # ########################################################################## The following seems to be defined outside of `pyproject.toml`: `authors = 'Met Office'` According to the spec (see the link below), however, setuptools CANNOT consider this value unless `authors` is listed as `dynamic`. https://packaging.python.org/en/latest/specifications/declaring-project-metadata/ For the time being, `setuptools` will still consider the given value (as a **transitional** measure), but please note that future releases of setuptools will follow strictly the standard. To prevent this warning, you can list `authors` under `dynamic` or alternatively remove the `[project]` table from your file and rely entirely on other means of configuration. By 2023-Oct-30, you need to update your project and remove deprecated calls or your builds will no longer be supported. ******************************************************************************** !! _handle_missing_dynamic(dist, project_table) /usr/lib/python3.11/site-packages/setuptools/config/_apply_pyprojecttoml.py:62: _WouldIgnoreField: `keywords` defined outside of `pyproject.toml` would be ignored. !! ******************************************************************************** ########################################################################## # configuration would be ignored/result in error due to `pyproject.toml` # ########################################################################## The following seems to be defined outside of `pyproject.toml`: `keywords = ['linter fortran psyclone']` According to the spec (see the link below), however, setuptools CANNOT consider this value unless `keywords` is listed as `dynamic`. https://packaging.python.org/en/latest/specifications/declaring-project-metadata/ For the time being, `setuptools` will still consider the given value (as a **transitional** measure), but please note that future releases of setuptools will follow strictly the standard. To prevent this warning, you can list `keywords` under `dynamic` or alternatively remove the `[project]` table from your file and rely entirely on other means of configuration. By 2023-Oct-30, you need to update your project and remove deprecated calls or your builds will no longer be supported. ******************************************************************************** !! _handle_missing_dynamic(dist, project_table) running egg_info writing source/stylist.egg-info/PKG-INFO writing dependency_links to source/stylist.egg-info/dependency_links.txt writing entry points to source/stylist.egg-info/entry_points.txt writing requirements to source/stylist.egg-info/requires.txt writing top-level names to source/stylist.egg-info/top_level.txt reading manifest file 'source/stylist.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' adding license file 'LICENSE' writing manifest file 'source/stylist.egg-info/SOURCES.txt' Handling wheel from get_requires_for_build_wheel Requirement satisfied: wheel (installed: wheel 0.40.0) /usr/lib/python3.11/site-packages/setuptools/config/pyprojecttoml.py:66: _BetaConfiguration: Support for `[tool.setuptools]` in `pyproject.toml` is still *beta*. config = read_configuration(filepath, True, ignore_option_errors, dist) /usr/lib/python3.11/site-packages/setuptools/config/_apply_pyprojecttoml.py:62: _WouldIgnoreField: `readme` defined outside of `pyproject.toml` would be ignored. !! ******************************************************************************** ########################################################################## # configuration would be ignored/result in error due to `pyproject.toml` # ########################################################################## The following seems to be defined outside of `pyproject.toml`: `readme = 'Stylist\n=======\n\n|BSD3 License| |GitHub release| |PyPI version| |Conda version| |GitHub merge testing|\n\nStylist is a tool for checking code style. It implements a framework which\nsupports multiple styles across multiple languages.\n\nBut aren\'t there many such tools out there, why create a new one?\n\nThe simple reason is that few of them support Fortran, a language still in\nwidespread use in the scientific computing domain. They can also tend towards\nthe zealous when enforcing the "one true style" whereas long running science\nmodels tend to diverge quite radically in what they like, style-wise.\n\nLarge models also tend to be implemented using more than one language so a\ntool which is capable of understanding all of them would be welcomed by\nscience developers.\n\nThis is the goal of Stylist development.\n\nThe project is still in its infancy so only a few rules have been implemented\nand only for Fortran. Stubs are provided to show how it might be extended to\nsupport C.\n\nFind the project at \n\n.. |BSD3 License| image:: https://img.shields.io/badge/License-BSD_3--Clause-blue.svg\n :target: https://opensource.org/licenses/BSD-3-Clause\n\n.. |GitHub release| image:: https://img.shields.io/github/release/MetOffice/stylist.svg\n :target: https://github.com/MetOffice/stylist/\n\n.. |PyPI version| image:: https://badge.fury.io/py/stylist.svg\n :target: https://pypi.python.org/pypi/stylist/\n\n.. |Conda version| image:: https://img.shields.io/conda/vn/conda-forge/stylist.svg\n :target: https://anaconda.org/conda-forge/stylist\n\n.. |GitHub merge testing| image:: https://github.com/MetOffice/stylist/workflows/Merge%20Test/badge.svg\n :target: https://github.com/MetOffice/stylist/actions\n\n\nInstallation\n~~~~~~~~~~~~\n\nInstallation can be as simple as ``pip install stylist`` or\n``conda install -c conda-forge stylist``.\n\nAs always it is also possible to install from the project source using\n``pip install --editable .``. The source may be obtained by downloading a\ntarball or by cloning the repository.\n\n\nUsage\n~~~~~\n\nStylist provides a command-line tool ``stylist`` for normal use. It can also be\nused as a package if you want to integrate it with another tool. Documentation\nregarding this second option is maintained in the project wiki.\n\nOn the Command Line\n-------------------\n\nThe command-line tool is not complicated to use::\n\n stylist [-help] [-verbose]\n [-configuration FILENAME]\n [-style NAME]\n FILE ...\n\nThe only required arguments are a configuration file and one or more\nfilenames. These are the files which will be checked. If a directory is\nspecified then the tool will automatically descend into it checking all files\nwhich it recognises by extension.\n\nIf you want a running commentary of what the tool is doing then use the\n``-verbose`` argument.\n\nA configuration file may specified with ``-configuration`` . This file should\nbe formatted as documented below. There must be a configuration file which\ndefines at least one style. While the fallback mechanism which allows for user\nand site configurations has not been implemented it must be specified with this\nargument.\n\nThe configuration may define several styles, in which case one can be chosen\nusing the ``-style`` argument. If it is not then the first in the configuration\nfile will be used.\n\nConfiguration File\n------------------\n\nThe configuration file is a simple python script where variable definitions\nare used to define the configuration.\n\nStylist uses the concept of "File Pipes" to specify the series of steps needed\nto process a particular file type. They are defined by creating a ``FilePipe``\nobject and associated with a file extension by assignment to a variable.\n\nFor example::\n\n from stylist.source import (FilePipe,\n FortranSource,\n PFUnitProcessor,\n FortranPreprocessor)\n \n pf = FilePipe(FortranSource, PFUnitProcessor, FortranPreprocessor)\n\nHere a pipeline consisting the pFUnit processor followed by the Fortran\npreprocessor produces Fortran source. This pipeline should be used for all\nfiles with the ``.pf`` extension.\n\nStyles are collections of rules and are defined in a similar way. The variable\nname is the style name and the object is constructed with the rules which make up the style.\n\nAn illustrative example::\n\n from re import compile as recompile\n from stylist.style import Style\n from stylist.fortran import FortranCharacterset, KindPattern\n \n simple = Style(FortranCharacterset(),\n KindPattern(integer=recompile(r\'i_.+\'),\n real=recompile(r\'r_.+\')))\n'` According to the spec (see the link below), however, setuptools CANNOT consider this value unless `readme` is listed as `dynamic`. https://packaging.python.org/en/latest/specifications/declaring-project-metadata/ For the time being, `setuptools` will still consider the given value (as a **transitional** measure), but please note that future releases of setuptools will follow strictly the standard. To prevent this warning, you can list `readme` under `dynamic` or alternatively remove the `[project]` table from your file and rely entirely on other means of configuration. By 2023-Oct-30, you need to update your project and remove deprecated calls or your builds will no longer be supported. ******************************************************************************** !! _handle_missing_dynamic(dist, project_table) /usr/lib/python3.11/site-packages/setuptools/config/_apply_pyprojecttoml.py:62: _WouldIgnoreField: `authors` defined outside of `pyproject.toml` would be ignored. !! ******************************************************************************** ########################################################################## # configuration would be ignored/result in error due to `pyproject.toml` # ########################################################################## The following seems to be defined outside of `pyproject.toml`: `authors = 'Met Office'` According to the spec (see the link below), however, setuptools CANNOT consider this value unless `authors` is listed as `dynamic`. https://packaging.python.org/en/latest/specifications/declaring-project-metadata/ For the time being, `setuptools` will still consider the given value (as a **transitional** measure), but please note that future releases of setuptools will follow strictly the standard. To prevent this warning, you can list `authors` under `dynamic` or alternatively remove the `[project]` table from your file and rely entirely on other means of configuration. By 2023-Oct-30, you need to update your project and remove deprecated calls or your builds will no longer be supported. ******************************************************************************** !! _handle_missing_dynamic(dist, project_table) /usr/lib/python3.11/site-packages/setuptools/config/_apply_pyprojecttoml.py:62: _WouldIgnoreField: `keywords` defined outside of `pyproject.toml` would be ignored. !! ******************************************************************************** ########################################################################## # configuration would be ignored/result in error due to `pyproject.toml` # ########################################################################## The following seems to be defined outside of `pyproject.toml`: `keywords = ['linter fortran psyclone']` According to the spec (see the link below), however, setuptools CANNOT consider this value unless `keywords` is listed as `dynamic`. https://packaging.python.org/en/latest/specifications/declaring-project-metadata/ For the time being, `setuptools` will still consider the given value (as a **transitional** measure), but please note that future releases of setuptools will follow strictly the standard. To prevent this warning, you can list `keywords` under `dynamic` or alternatively remove the `[project]` table from your file and rely entirely on other means of configuration. By 2023-Oct-30, you need to update your project and remove deprecated calls or your builds will no longer be supported. ******************************************************************************** !! _handle_missing_dynamic(dist, project_table) running dist_info creating stylist.egg-info writing stylist.egg-info/PKG-INFO writing dependency_links to stylist.egg-info/dependency_links.txt writing entry points to stylist.egg-info/entry_points.txt writing requirements to stylist.egg-info/requires.txt writing top-level names to stylist.egg-info/top_level.txt writing manifest file 'stylist.egg-info/SOURCES.txt' reading manifest file 'stylist.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' adding license file 'LICENSE' writing manifest file 'stylist.egg-info/SOURCES.txt' creating '/builddir/build/BUILD/stylist-0.4.0/stylist-0.4.0.dist-info' Handling fparser (>=0.1.0) from hook generated metadata: Requires-Dist Requirement not satisfied: fparser (>=0.1.0) Handling check-manifest ; extra == 'dev' from hook generated metadata: Requires-Dist Ignoring alien requirement: check-manifest ; extra == 'dev' Handling flake8 ; extra == 'dev' from hook generated metadata: Requires-Dist Ignoring alien requirement: flake8 ; extra == 'dev' Handling sphinx ; extra == 'docs' from hook generated metadata: Requires-Dist Ignoring alien requirement: sphinx ; extra == 'docs' Handling sphinx-autodoc-typehints ; extra == 'docs' from hook generated metadata: Requires-Dist Ignoring alien requirement: sphinx-autodoc-typehints ; extra == 'docs' Handling sphinx-rtd-theme ; extra == 'docs' from hook generated metadata: Requires-Dist Ignoring alien requirement: sphinx-rtd-theme ; extra == 'docs' Handling pytest ; extra == 'performance' from hook generated metadata: Requires-Dist Ignoring alien requirement: pytest ; extra == 'performance' Handling pytest-benchmark ; extra == 'performance' from hook generated metadata: Requires-Dist Ignoring alien requirement: pytest-benchmark ; extra == 'performance' Handling matplotlib ; extra == 'performance' from hook generated metadata: Requires-Dist Ignoring alien requirement: matplotlib ; extra == 'performance' Handling setuptools ; extra == 'release' from hook generated metadata: Requires-Dist Ignoring alien requirement: setuptools ; extra == 'release' Handling wheel ; extra == 'release' from hook generated metadata: Requires-Dist Ignoring alien requirement: wheel ; extra == 'release' Handling twine ; extra == 'release' from hook generated metadata: Requires-Dist Ignoring alien requirement: twine ; extra == 'release' Handling pytest ; extra == 'test' from hook generated metadata: Requires-Dist Ignoring alien requirement: pytest ; extra == 'test' Handling pytest-cov ; extra == 'test' from hook generated metadata: Requires-Dist Ignoring alien requirement: pytest-cov ; extra == 'test' Handling mypy ; extra == 'test' from hook generated metadata: Requires-Dist Ignoring alien requirement: mypy ; extra == 'test' + cat /builddir/build/BUILD/python-stylist-0.4.0-1.fc39.x86_64-pyproject-buildrequires + rm -rfv stylist-0.4.0.dist-info/ removed 'stylist-0.4.0.dist-info/LICENSE' removed 'stylist-0.4.0.dist-info/METADATA' removed 'stylist-0.4.0.dist-info/entry_points.txt' removed 'stylist-0.4.0.dist-info/top_level.txt' removed directory 'stylist-0.4.0.dist-info/' + RPM_EC=0 ++ jobs -p + exit 0 Wrote: /builddir/build/SRPMS/python-stylist-0.4.0-1.fc39.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-stylist.spec'], chrootPath='/var/lib/mock/fedora-rawhide-x86_64-1682443252.252062/root'env={'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\s-\\v\\$ ', 'LANG': 'C.UTF-8'}shell=Falselogger=timeout=0uid=1000gid=135user='mockbuild'nspawn_args=['--capability=cap_ipc_lock', '--rlimit=RLIMIT_NOFILE=10240', '--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.pl_ch5qh:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/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.pl_ch5qh:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/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', '8f2bdf38ebc04c5db234b941af55fba6', '-D', '/var/lib/mock/fedora-rawhide-x86_64-1682443252.252062/root', '-a', '-u', 'mockbuild', '--capability=cap_ipc_lock', '--rlimit=RLIMIT_NOFILE=10240', '--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.pl_ch5qh:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/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;\\007"', '--setenv=PS1= \\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-stylist.spec'] with env {'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\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=1682380800 Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.TaNK2Y + umask 022 + cd /builddir/build/BUILD + cd /builddir/build/BUILD + rm -rf stylist-0.4.0 + /usr/lib/rpm/rpmuncompress -x /builddir/build/SOURCES/stylist-0.4.0.tar.gz + STATUS=0 + '[' 0 -ne 0 ']' + cd stylist-0.4.0 + /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.D3nVIc + umask 022 + cd /builddir/build/BUILD + cd stylist-0.4.0 + CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer ' + export CFLAGS + CXXFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer ' + export CXXFLAGS + FFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules ' + export FFLAGS + FCFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules ' + export FCFLAGS + VALAFLAGS=-g + export VALAFLAGS + RUSTFLAGS='-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cforce-frame-pointers=yes -Clink-arg=-Wl,-z,relro -Clink-arg=-Wl,-z,now --cap-lints=warn' + export RUSTFLAGS + 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 -Wl,--build-id=sha1 ' + export LDFLAGS + LT_SYS_LIBRARY_PATH=/usr/lib64: + export LT_SYS_LIBRARY_PATH + CC=gcc + export CC + CXX=g++ + export CXX + echo pyproject-rpm-macros + echo python3-devel + echo 'python3dist(pip) >= 19' + echo 'python3dist(packaging)' + '[' -f pyproject.toml ']' + echo '(python3dist(toml) if python3-devel < 3.11)' + rm -rfv '*.dist-info/' + '[' -f /usr/bin/python3 ']' + mkdir -p /builddir/build/BUILD/stylist-0.4.0/.pyproject-builddir + echo -n + CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer ' + 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 -Wl,--build-id=sha1 ' + TMPDIR=/builddir/build/BUILD/stylist-0.4.0/.pyproject-builddir + RPM_TOXENV=py311 + HOSTNAME=rpmbuild + /usr/bin/python3 -Bs /usr/lib/rpm/redhat/pyproject_buildrequires.py --generate-extras --python3_pkgversion 3 --wheeldir /builddir/build/BUILD/stylist-0.4.0/pyproject-wheeldir --output /builddir/build/BUILD/python-stylist-0.4.0-1.fc39.x86_64-pyproject-buildrequires Handling setuptools from build-system.requires Requirement satisfied: setuptools (installed: setuptools 67.7.2) /usr/lib/python3.11/site-packages/setuptools/config/pyprojecttoml.py:66: _BetaConfiguration: Support for `[tool.setuptools]` in `pyproject.toml` is still *beta*. config = read_configuration(filepath, True, ignore_option_errors, dist) /usr/lib/python3.11/site-packages/setuptools/config/_apply_pyprojecttoml.py:62: _WouldIgnoreField: `readme` defined outside of `pyproject.toml` would be ignored. !! ******************************************************************************** ########################################################################## # configuration would be ignored/result in error due to `pyproject.toml` # ########################################################################## The following seems to be defined outside of `pyproject.toml`: `readme = 'Stylist\n=======\n\n|BSD3 License| |GitHub release| |PyPI version| |Conda version| |GitHub merge testing|\n\nStylist is a tool for checking code style. It implements a framework which\nsupports multiple styles across multiple languages.\n\nBut aren\'t there many such tools out there, why create a new one?\n\nThe simple reason is that few of them support Fortran, a language still in\nwidespread use in the scientific computing domain. They can also tend towards\nthe zealous when enforcing the "one true style" whereas long running science\nmodels tend to diverge quite radically in what they like, style-wise.\n\nLarge models also tend to be implemented using more than one language so a\ntool which is capable of understanding all of them would be welcomed by\nscience developers.\n\nThis is the goal of Stylist development.\n\nThe project is still in its infancy so only a few rules have been implemented\nand only for Fortran. Stubs are provided to show how it might be extended to\nsupport C.\n\nFind the project at \n\n.. |BSD3 License| image:: https://img.shields.io/badge/License-BSD_3--Clause-blue.svg\n :target: https://opensource.org/licenses/BSD-3-Clause\n\n.. |GitHub release| image:: https://img.shields.io/github/release/MetOffice/stylist.svg\n :target: https://github.com/MetOffice/stylist/\n\n.. |PyPI version| image:: https://badge.fury.io/py/stylist.svg\n :target: https://pypi.python.org/pypi/stylist/\n\n.. |Conda version| image:: https://img.shields.io/conda/vn/conda-forge/stylist.svg\n :target: https://anaconda.org/conda-forge/stylist\n\n.. |GitHub merge testing| image:: https://github.com/MetOffice/stylist/workflows/Merge%20Test/badge.svg\n :target: https://github.com/MetOffice/stylist/actions\n\n\nInstallation\n~~~~~~~~~~~~\n\nInstallation can be as simple as ``pip install stylist`` or\n``conda install -c conda-forge stylist``.\n\nAs always it is also possible to install from the project source using\n``pip install --editable .``. The source may be obtained by downloading a\ntarball or by cloning the repository.\n\n\nUsage\n~~~~~\n\nStylist provides a command-line tool ``stylist`` for normal use. It can also be\nused as a package if you want to integrate it with another tool. Documentation\nregarding this second option is maintained in the project wiki.\n\nOn the Command Line\n-------------------\n\nThe command-line tool is not complicated to use::\n\n stylist [-help] [-verbose]\n [-configuration FILENAME]\n [-style NAME]\n FILE ...\n\nThe only required arguments are a configuration file and one or more\nfilenames. These are the files which will be checked. If a directory is\nspecified then the tool will automatically descend into it checking all files\nwhich it recognises by extension.\n\nIf you want a running commentary of what the tool is doing then use the\n``-verbose`` argument.\n\nA configuration file may specified with ``-configuration`` . This file should\nbe formatted as documented below. There must be a configuration file which\ndefines at least one style. While the fallback mechanism which allows for user\nand site configurations has not been implemented it must be specified with this\nargument.\n\nThe configuration may define several styles, in which case one can be chosen\nusing the ``-style`` argument. If it is not then the first in the configuration\nfile will be used.\n\nConfiguration File\n------------------\n\nThe configuration file is a simple python script where variable definitions\nare used to define the configuration.\n\nStylist uses the concept of "File Pipes" to specify the series of steps needed\nto process a particular file type. They are defined by creating a ``FilePipe``\nobject and associated with a file extension by assignment to a variable.\n\nFor example::\n\n from stylist.source import (FilePipe,\n FortranSource,\n PFUnitProcessor,\n FortranPreprocessor)\n \n pf = FilePipe(FortranSource, PFUnitProcessor, FortranPreprocessor)\n\nHere a pipeline consisting the pFUnit processor followed by the Fortran\npreprocessor produces Fortran source. This pipeline should be used for all\nfiles with the ``.pf`` extension.\n\nStyles are collections of rules and are defined in a similar way. The variable\nname is the style name and the object is constructed with the rules which make up the style.\n\nAn illustrative example::\n\n from re import compile as recompile\n from stylist.style import Style\n from stylist.fortran import FortranCharacterset, KindPattern\n \n simple = Style(FortranCharacterset(),\n KindPattern(integer=recompile(r\'i_.+\'),\n real=recompile(r\'r_.+\')))\n'` According to the spec (see the link below), however, setuptools CANNOT consider this value unless `readme` is listed as `dynamic`. https://packaging.python.org/en/latest/specifications/declaring-project-metadata/ For the time being, `setuptools` will still consider the given value (as a **transitional** measure), but please note that future releases of setuptools will follow strictly the standard. To prevent this warning, you can list `readme` under `dynamic` or alternatively remove the `[project]` table from your file and rely entirely on other means of configuration. By 2023-Oct-30, you need to update your project and remove deprecated calls or your builds will no longer be supported. ******************************************************************************** !! _handle_missing_dynamic(dist, project_table) /usr/lib/python3.11/site-packages/setuptools/config/_apply_pyprojecttoml.py:62: _WouldIgnoreField: `authors` defined outside of `pyproject.toml` would be ignored. !! ******************************************************************************** ########################################################################## # configuration would be ignored/result in error due to `pyproject.toml` # ########################################################################## The following seems to be defined outside of `pyproject.toml`: `authors = 'Met Office'` According to the spec (see the link below), however, setuptools CANNOT consider this value unless `authors` is listed as `dynamic`. https://packaging.python.org/en/latest/specifications/declaring-project-metadata/ For the time being, `setuptools` will still consider the given value (as a **transitional** measure), but please note that future releases of setuptools will follow strictly the standard. To prevent this warning, you can list `authors` under `dynamic` or alternatively remove the `[project]` table from your file and rely entirely on other means of configuration. By 2023-Oct-30, you need to update your project and remove deprecated calls or your builds will no longer be supported. ******************************************************************************** !! _handle_missing_dynamic(dist, project_table) /usr/lib/python3.11/site-packages/setuptools/config/_apply_pyprojecttoml.py:62: _WouldIgnoreField: `keywords` defined outside of `pyproject.toml` would be ignored. !! ******************************************************************************** ########################################################################## # configuration would be ignored/result in error due to `pyproject.toml` # ########################################################################## The following seems to be defined outside of `pyproject.toml`: `keywords = ['linter fortran psyclone']` According to the spec (see the link below), however, setuptools CANNOT consider this value unless `keywords` is listed as `dynamic`. https://packaging.python.org/en/latest/specifications/declaring-project-metadata/ For the time being, `setuptools` will still consider the given value (as a **transitional** measure), but please note that future releases of setuptools will follow strictly the standard. To prevent this warning, you can list `keywords` under `dynamic` or alternatively remove the `[project]` table from your file and rely entirely on other means of configuration. By 2023-Oct-30, you need to update your project and remove deprecated calls or your builds will no longer be supported. ******************************************************************************** !! _handle_missing_dynamic(dist, project_table) running egg_info writing source/stylist.egg-info/PKG-INFO writing dependency_links to source/stylist.egg-info/dependency_links.txt writing entry points to source/stylist.egg-info/entry_points.txt writing requirements to source/stylist.egg-info/requires.txt writing top-level names to source/stylist.egg-info/top_level.txt reading manifest file 'source/stylist.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' adding license file 'LICENSE' writing manifest file 'source/stylist.egg-info/SOURCES.txt' Handling wheel from get_requires_for_build_wheel Requirement satisfied: wheel (installed: wheel 0.40.0) /usr/lib/python3.11/site-packages/setuptools/config/pyprojecttoml.py:66: _BetaConfiguration: Support for `[tool.setuptools]` in `pyproject.toml` is still *beta*. config = read_configuration(filepath, True, ignore_option_errors, dist) /usr/lib/python3.11/site-packages/setuptools/config/_apply_pyprojecttoml.py:62: _WouldIgnoreField: `readme` defined outside of `pyproject.toml` would be ignored. !! ******************************************************************************** ########################################################################## # configuration would be ignored/result in error due to `pyproject.toml` # ########################################################################## The following seems to be defined outside of `pyproject.toml`: `readme = 'Stylist\n=======\n\n|BSD3 License| |GitHub release| |PyPI version| |Conda version| |GitHub merge testing|\n\nStylist is a tool for checking code style. It implements a framework which\nsupports multiple styles across multiple languages.\n\nBut aren\'t there many such tools out there, why create a new one?\n\nThe simple reason is that few of them support Fortran, a language still in\nwidespread use in the scientific computing domain. They can also tend towards\nthe zealous when enforcing the "one true style" whereas long running science\nmodels tend to diverge quite radically in what they like, style-wise.\n\nLarge models also tend to be implemented using more than one language so a\ntool which is capable of understanding all of them would be welcomed by\nscience developers.\n\nThis is the goal of Stylist development.\n\nThe project is still in its infancy so only a few rules have been implemented\nand only for Fortran. Stubs are provided to show how it might be extended to\nsupport C.\n\nFind the project at \n\n.. |BSD3 License| image:: https://img.shields.io/badge/License-BSD_3--Clause-blue.svg\n :target: https://opensource.org/licenses/BSD-3-Clause\n\n.. |GitHub release| image:: https://img.shields.io/github/release/MetOffice/stylist.svg\n :target: https://github.com/MetOffice/stylist/\n\n.. |PyPI version| image:: https://badge.fury.io/py/stylist.svg\n :target: https://pypi.python.org/pypi/stylist/\n\n.. |Conda version| image:: https://img.shields.io/conda/vn/conda-forge/stylist.svg\n :target: https://anaconda.org/conda-forge/stylist\n\n.. |GitHub merge testing| image:: https://github.com/MetOffice/stylist/workflows/Merge%20Test/badge.svg\n :target: https://github.com/MetOffice/stylist/actions\n\n\nInstallation\n~~~~~~~~~~~~\n\nInstallation can be as simple as ``pip install stylist`` or\n``conda install -c conda-forge stylist``.\n\nAs always it is also possible to install from the project source using\n``pip install --editable .``. The source may be obtained by downloading a\ntarball or by cloning the repository.\n\n\nUsage\n~~~~~\n\nStylist provides a command-line tool ``stylist`` for normal use. It can also be\nused as a package if you want to integrate it with another tool. Documentation\nregarding this second option is maintained in the project wiki.\n\nOn the Command Line\n-------------------\n\nThe command-line tool is not complicated to use::\n\n stylist [-help] [-verbose]\n [-configuration FILENAME]\n [-style NAME]\n FILE ...\n\nThe only required arguments are a configuration file and one or more\nfilenames. These are the files which will be checked. If a directory is\nspecified then the tool will automatically descend into it checking all files\nwhich it recognises by extension.\n\nIf you want a running commentary of what the tool is doing then use the\n``-verbose`` argument.\n\nA configuration file may specified with ``-configuration`` . This file should\nbe formatted as documented below. There must be a configuration file which\ndefines at least one style. While the fallback mechanism which allows for user\nand site configurations has not been implemented it must be specified with this\nargument.\n\nThe configuration may define several styles, in which case one can be chosen\nusing the ``-style`` argument. If it is not then the first in the configuration\nfile will be used.\n\nConfiguration File\n------------------\n\nThe configuration file is a simple python script where variable definitions\nare used to define the configuration.\n\nStylist uses the concept of "File Pipes" to specify the series of steps needed\nto process a particular file type. They are defined by creating a ``FilePipe``\nobject and associated with a file extension by assignment to a variable.\n\nFor example::\n\n from stylist.source import (FilePipe,\n FortranSource,\n PFUnitProcessor,\n FortranPreprocessor)\n \n pf = FilePipe(FortranSource, PFUnitProcessor, FortranPreprocessor)\n\nHere a pipeline consisting the pFUnit processor followed by the Fortran\npreprocessor produces Fortran source. This pipeline should be used for all\nfiles with the ``.pf`` extension.\n\nStyles are collections of rules and are defined in a similar way. The variable\nname is the style name and the object is constructed with the rules which make up the style.\n\nAn illustrative example::\n\n from re import compile as recompile\n from stylist.style import Style\n from stylist.fortran import FortranCharacterset, KindPattern\n \n simple = Style(FortranCharacterset(),\n KindPattern(integer=recompile(r\'i_.+\'),\n real=recompile(r\'r_.+\')))\n'` According to the spec (see the link below), however, setuptools CANNOT consider this value unless `readme` is listed as `dynamic`. https://packaging.python.org/en/latest/specifications/declaring-project-metadata/ For the time being, `setuptools` will still consider the given value (as a **transitional** measure), but please note that future releases of setuptools will follow strictly the standard. To prevent this warning, you can list `readme` under `dynamic` or alternatively remove the `[project]` table from your file and rely entirely on other means of configuration. By 2023-Oct-30, you need to update your project and remove deprecated calls or your builds will no longer be supported. ******************************************************************************** !! _handle_missing_dynamic(dist, project_table) /usr/lib/python3.11/site-packages/setuptools/config/_apply_pyprojecttoml.py:62: _WouldIgnoreField: `authors` defined outside of `pyproject.toml` would be ignored. !! ******************************************************************************** ########################################################################## # configuration would be ignored/result in error due to `pyproject.toml` # ########################################################################## The following seems to be defined outside of `pyproject.toml`: `authors = 'Met Office'` According to the spec (see the link below), however, setuptools CANNOT consider this value unless `authors` is listed as `dynamic`. https://packaging.python.org/en/latest/specifications/declaring-project-metadata/ For the time being, `setuptools` will still consider the given value (as a **transitional** measure), but please note that future releases of setuptools will follow strictly the standard. To prevent this warning, you can list `authors` under `dynamic` or alternatively remove the `[project]` table from your file and rely entirely on other means of configuration. By 2023-Oct-30, you need to update your project and remove deprecated calls or your builds will no longer be supported. ******************************************************************************** !! _handle_missing_dynamic(dist, project_table) /usr/lib/python3.11/site-packages/setuptools/config/_apply_pyprojecttoml.py:62: _WouldIgnoreField: `keywords` defined outside of `pyproject.toml` would be ignored. !! ******************************************************************************** ########################################################################## # configuration would be ignored/result in error due to `pyproject.toml` # ########################################################################## The following seems to be defined outside of `pyproject.toml`: `keywords = ['linter fortran psyclone']` According to the spec (see the link below), however, setuptools CANNOT consider this value unless `keywords` is listed as `dynamic`. https://packaging.python.org/en/latest/specifications/declaring-project-metadata/ For the time being, `setuptools` will still consider the given value (as a **transitional** measure), but please note that future releases of setuptools will follow strictly the standard. To prevent this warning, you can list `keywords` under `dynamic` or alternatively remove the `[project]` table from your file and rely entirely on other means of configuration. By 2023-Oct-30, you need to update your project and remove deprecated calls or your builds will no longer be supported. ******************************************************************************** !! _handle_missing_dynamic(dist, project_table) running dist_info creating stylist.egg-info writing stylist.egg-info/PKG-INFO writing dependency_links to stylist.egg-info/dependency_links.txt writing entry points to stylist.egg-info/entry_points.txt writing requirements to stylist.egg-info/requires.txt writing top-level names to stylist.egg-info/top_level.txt writing manifest file 'stylist.egg-info/SOURCES.txt' reading manifest file 'stylist.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' adding license file 'LICENSE' writing manifest file 'stylist.egg-info/SOURCES.txt' creating '/builddir/build/BUILD/stylist-0.4.0/stylist-0.4.0.dist-info' Handling fparser (>=0.1.0) from hook generated metadata: Requires-Dist Requirement satisfied: fparser (>=0.1.0) (installed: fparser 0.1.0) Handling check-manifest ; extra == 'dev' from hook generated metadata: Requires-Dist Ignoring alien requirement: check-manifest ; extra == 'dev' Handling flake8 ; extra == 'dev' from hook generated metadata: Requires-Dist Ignoring alien requirement: flake8 ; extra == 'dev' Handling sphinx ; extra == 'docs' from hook generated metadata: Requires-Dist Ignoring alien requirement: sphinx ; extra == 'docs' Handling sphinx-autodoc-typehints ; extra == 'docs' from hook generated metadata: Requires-Dist Ignoring alien requirement: sphinx-autodoc-typehints ; extra == 'docs' Handling sphinx-rtd-theme ; extra == 'docs' from hook generated metadata: Requires-Dist Ignoring alien requirement: sphinx-rtd-theme ; extra == 'docs' Handling pytest ; extra == 'performance' from hook generated metadata: Requires-Dist Ignoring alien requirement: pytest ; extra == 'performance' Handling pytest-benchmark ; extra == 'performance' from hook generated metadata: Requires-Dist Ignoring alien requirement: pytest-benchmark ; extra == 'performance' Handling matplotlib ; extra == 'performance' from hook generated metadata: Requires-Dist Ignoring alien requirement: matplotlib ; extra == 'performance' Handling setuptools ; extra == 'release' from hook generated metadata: Requires-Dist Ignoring alien requirement: setuptools ; extra == 'release' Handling wheel ; extra == 'release' from hook generated metadata: Requires-Dist Ignoring alien requirement: wheel ; extra == 'release' Handling twine ; extra == 'release' from hook generated metadata: Requires-Dist Ignoring alien requirement: twine ; extra == 'release' Handling pytest ; extra == 'test' from hook generated metadata: Requires-Dist Ignoring alien requirement: pytest ; extra == 'test' Handling pytest-cov ; extra == 'test' from hook generated metadata: Requires-Dist Ignoring alien requirement: pytest-cov ; extra == 'test' Handling mypy ; extra == 'test' from hook generated metadata: Requires-Dist Ignoring alien requirement: mypy ; extra == 'test' + cat /builddir/build/BUILD/python-stylist-0.4.0-1.fc39.x86_64-pyproject-buildrequires + rm -rfv stylist-0.4.0.dist-info/ removed 'stylist-0.4.0.dist-info/LICENSE' removed 'stylist-0.4.0.dist-info/METADATA' removed 'stylist-0.4.0.dist-info/entry_points.txt' removed 'stylist-0.4.0.dist-info/top_level.txt' removed directory 'stylist-0.4.0.dist-info/' + RPM_EC=0 ++ jobs -p + exit 0 Wrote: /builddir/build/SRPMS/python-stylist-0.4.0-1.fc39.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-stylist.spec'], chrootPath='/var/lib/mock/fedora-rawhide-x86_64-1682443252.252062/root'env={'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\s-\\v\\$ ', 'LANG': 'C.UTF-8'}shell=Falselogger=timeout=0uid=1000gid=135user='mockbuild'nspawn_args=['--capability=cap_ipc_lock', '--rlimit=RLIMIT_NOFILE=10240', '--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.pl_ch5qh:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/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.pl_ch5qh:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/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', '95115339ed8a4e4bbb4d14d0844e58b0', '-D', '/var/lib/mock/fedora-rawhide-x86_64-1682443252.252062/root', '-a', '-u', 'mockbuild', '--capability=cap_ipc_lock', '--rlimit=RLIMIT_NOFILE=10240', '--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.pl_ch5qh:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/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;\\007"', '--setenv=PS1= \\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-stylist.spec'] with env {'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\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=1682380800 Executing(%generate_buildrequires): /bin/sh -e /var/tmp/rpm-tmp.nUfmes + umask 022 + cd /builddir/build/BUILD + cd stylist-0.4.0 + CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer ' + export CFLAGS + CXXFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer ' + export CXXFLAGS + FFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules ' + export FFLAGS + FCFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules ' + export FCFLAGS + VALAFLAGS=-g + export VALAFLAGS + RUSTFLAGS='-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cforce-frame-pointers=yes -Clink-arg=-Wl,-z,relro -Clink-arg=-Wl,-z,now --cap-lints=warn' + export RUSTFLAGS + 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 -Wl,--build-id=sha1 ' + export LDFLAGS + LT_SYS_LIBRARY_PATH=/usr/lib64: + export LT_SYS_LIBRARY_PATH + CC=gcc + export CC + CXX=g++ + export CXX + echo pyproject-rpm-macros + echo python3-devel + echo 'python3dist(pip) >= 19' + echo 'python3dist(packaging)' + '[' -f pyproject.toml ']' + echo '(python3dist(toml) if python3-devel < 3.11)' + rm -rfv '*.dist-info/' + '[' -f /usr/bin/python3 ']' + mkdir -p /builddir/build/BUILD/stylist-0.4.0/.pyproject-builddir + echo -n + CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer ' + 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 -Wl,--build-id=sha1 ' + TMPDIR=/builddir/build/BUILD/stylist-0.4.0/.pyproject-builddir + RPM_TOXENV=py311 + HOSTNAME=rpmbuild + /usr/bin/python3 -Bs /usr/lib/rpm/redhat/pyproject_buildrequires.py --generate-extras --python3_pkgversion 3 --wheeldir /builddir/build/BUILD/stylist-0.4.0/pyproject-wheeldir --output /builddir/build/BUILD/python-stylist-0.4.0-1.fc39.x86_64-pyproject-buildrequires Handling setuptools from build-system.requires Requirement satisfied: setuptools (installed: setuptools 67.7.2) /usr/lib/python3.11/site-packages/setuptools/config/pyprojecttoml.py:66: _BetaConfiguration: Support for `[tool.setuptools]` in `pyproject.toml` is still *beta*. config = read_configuration(filepath, True, ignore_option_errors, dist) /usr/lib/python3.11/site-packages/setuptools/config/_apply_pyprojecttoml.py:62: _WouldIgnoreField: `readme` defined outside of `pyproject.toml` would be ignored. !! ******************************************************************************** ########################################################################## # configuration would be ignored/result in error due to `pyproject.toml` # ########################################################################## The following seems to be defined outside of `pyproject.toml`: `readme = 'Stylist\n=======\n\n|BSD3 License| |GitHub release| |PyPI version| |Conda version| |GitHub merge testing|\n\nStylist is a tool for checking code style. It implements a framework which\nsupports multiple styles across multiple languages.\n\nBut aren\'t there many such tools out there, why create a new one?\n\nThe simple reason is that few of them support Fortran, a language still in\nwidespread use in the scientific computing domain. They can also tend towards\nthe zealous when enforcing the "one true style" whereas long running science\nmodels tend to diverge quite radically in what they like, style-wise.\n\nLarge models also tend to be implemented using more than one language so a\ntool which is capable of understanding all of them would be welcomed by\nscience developers.\n\nThis is the goal of Stylist development.\n\nThe project is still in its infancy so only a few rules have been implemented\nand only for Fortran. Stubs are provided to show how it might be extended to\nsupport C.\n\nFind the project at \n\n.. |BSD3 License| image:: https://img.shields.io/badge/License-BSD_3--Clause-blue.svg\n :target: https://opensource.org/licenses/BSD-3-Clause\n\n.. |GitHub release| image:: https://img.shields.io/github/release/MetOffice/stylist.svg\n :target: https://github.com/MetOffice/stylist/\n\n.. |PyPI version| image:: https://badge.fury.io/py/stylist.svg\n :target: https://pypi.python.org/pypi/stylist/\n\n.. |Conda version| image:: https://img.shields.io/conda/vn/conda-forge/stylist.svg\n :target: https://anaconda.org/conda-forge/stylist\n\n.. |GitHub merge testing| image:: https://github.com/MetOffice/stylist/workflows/Merge%20Test/badge.svg\n :target: https://github.com/MetOffice/stylist/actions\n\n\nInstallation\n~~~~~~~~~~~~\n\nInstallation can be as simple as ``pip install stylist`` or\n``conda install -c conda-forge stylist``.\n\nAs always it is also possible to install from the project source using\n``pip install --editable .``. The source may be obtained by downloading a\ntarball or by cloning the repository.\n\n\nUsage\n~~~~~\n\nStylist provides a command-line tool ``stylist`` for normal use. It can also be\nused as a package if you want to integrate it with another tool. Documentation\nregarding this second option is maintained in the project wiki.\n\nOn the Command Line\n-------------------\n\nThe command-line tool is not complicated to use::\n\n stylist [-help] [-verbose]\n [-configuration FILENAME]\n [-style NAME]\n FILE ...\n\nThe only required arguments are a configuration file and one or more\nfilenames. These are the files which will be checked. If a directory is\nspecified then the tool will automatically descend into it checking all files\nwhich it recognises by extension.\n\nIf you want a running commentary of what the tool is doing then use the\n``-verbose`` argument.\n\nA configuration file may specified with ``-configuration`` . This file should\nbe formatted as documented below. There must be a configuration file which\ndefines at least one style. While the fallback mechanism which allows for user\nand site configurations has not been implemented it must be specified with this\nargument.\n\nThe configuration may define several styles, in which case one can be chosen\nusing the ``-style`` argument. If it is not then the first in the configuration\nfile will be used.\n\nConfiguration File\n------------------\n\nThe configuration file is a simple python script where variable definitions\nare used to define the configuration.\n\nStylist uses the concept of "File Pipes" to specify the series of steps needed\nto process a particular file type. They are defined by creating a ``FilePipe``\nobject and associated with a file extension by assignment to a variable.\n\nFor example::\n\n from stylist.source import (FilePipe,\n FortranSource,\n PFUnitProcessor,\n FortranPreprocessor)\n \n pf = FilePipe(FortranSource, PFUnitProcessor, FortranPreprocessor)\n\nHere a pipeline consisting the pFUnit processor followed by the Fortran\npreprocessor produces Fortran source. This pipeline should be used for all\nfiles with the ``.pf`` extension.\n\nStyles are collections of rules and are defined in a similar way. The variable\nname is the style name and the object is constructed with the rules which make up the style.\n\nAn illustrative example::\n\n from re import compile as recompile\n from stylist.style import Style\n from stylist.fortran import FortranCharacterset, KindPattern\n \n simple = Style(FortranCharacterset(),\n KindPattern(integer=recompile(r\'i_.+\'),\n real=recompile(r\'r_.+\')))\n'` According to the spec (see the link below), however, setuptools CANNOT consider this value unless `readme` is listed as `dynamic`. https://packaging.python.org/en/latest/specifications/declaring-project-metadata/ For the time being, `setuptools` will still consider the given value (as a **transitional** measure), but please note that future releases of setuptools will follow strictly the standard. To prevent this warning, you can list `readme` under `dynamic` or alternatively remove the `[project]` table from your file and rely entirely on other means of configuration. By 2023-Oct-30, you need to update your project and remove deprecated calls or your builds will no longer be supported. ******************************************************************************** !! _handle_missing_dynamic(dist, project_table) /usr/lib/python3.11/site-packages/setuptools/config/_apply_pyprojecttoml.py:62: _WouldIgnoreField: `authors` defined outside of `pyproject.toml` would be ignored. !! ******************************************************************************** ########################################################################## # configuration would be ignored/result in error due to `pyproject.toml` # ########################################################################## The following seems to be defined outside of `pyproject.toml`: `authors = 'Met Office'` According to the spec (see the link below), however, setuptools CANNOT consider this value unless `authors` is listed as `dynamic`. https://packaging.python.org/en/latest/specifications/declaring-project-metadata/ For the time being, `setuptools` will still consider the given value (as a **transitional** measure), but please note that future releases of setuptools will follow strictly the standard. To prevent this warning, you can list `authors` under `dynamic` or alternatively remove the `[project]` table from your file and rely entirely on other means of configuration. By 2023-Oct-30, you need to update your project and remove deprecated calls or your builds will no longer be supported. ******************************************************************************** !! _handle_missing_dynamic(dist, project_table) /usr/lib/python3.11/site-packages/setuptools/config/_apply_pyprojecttoml.py:62: _WouldIgnoreField: `keywords` defined outside of `pyproject.toml` would be ignored. !! ******************************************************************************** ########################################################################## # configuration would be ignored/result in error due to `pyproject.toml` # ########################################################################## The following seems to be defined outside of `pyproject.toml`: `keywords = ['linter fortran psyclone']` According to the spec (see the link below), however, setuptools CANNOT consider this value unless `keywords` is listed as `dynamic`. https://packaging.python.org/en/latest/specifications/declaring-project-metadata/ For the time being, `setuptools` will still consider the given value (as a **transitional** measure), but please note that future releases of setuptools will follow strictly the standard. To prevent this warning, you can list `keywords` under `dynamic` or alternatively remove the `[project]` table from your file and rely entirely on other means of configuration. By 2023-Oct-30, you need to update your project and remove deprecated calls or your builds will no longer be supported. ******************************************************************************** !! _handle_missing_dynamic(dist, project_table) running egg_info writing source/stylist.egg-info/PKG-INFO writing dependency_links to source/stylist.egg-info/dependency_links.txt writing entry points to source/stylist.egg-info/entry_points.txt writing requirements to source/stylist.egg-info/requires.txt writing top-level names to source/stylist.egg-info/top_level.txt reading manifest file 'source/stylist.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' adding license file 'LICENSE' writing manifest file 'source/stylist.egg-info/SOURCES.txt' Handling wheel from get_requires_for_build_wheel Requirement satisfied: wheel (installed: wheel 0.40.0) /usr/lib/python3.11/site-packages/setuptools/config/pyprojecttoml.py:66: _BetaConfiguration: Support for `[tool.setuptools]` in `pyproject.toml` is still *beta*. config = read_configuration(filepath, True, ignore_option_errors, dist) /usr/lib/python3.11/site-packages/setuptools/config/_apply_pyprojecttoml.py:62: _WouldIgnoreField: `readme` defined outside of `pyproject.toml` would be ignored. !! ******************************************************************************** ########################################################################## # configuration would be ignored/result in error due to `pyproject.toml` # ########################################################################## The following seems to be defined outside of `pyproject.toml`: `readme = 'Stylist\n=======\n\n|BSD3 License| |GitHub release| |PyPI version| |Conda version| |GitHub merge testing|\n\nStylist is a tool for checking code style. It implements a framework which\nsupports multiple styles across multiple languages.\n\nBut aren\'t there many such tools out there, why create a new one?\n\nThe simple reason is that few of them support Fortran, a language still in\nwidespread use in the scientific computing domain. They can also tend towards\nthe zealous when enforcing the "one true style" whereas long running science\nmodels tend to diverge quite radically in what they like, style-wise.\n\nLarge models also tend to be implemented using more than one language so a\ntool which is capable of understanding all of them would be welcomed by\nscience developers.\n\nThis is the goal of Stylist development.\n\nThe project is still in its infancy so only a few rules have been implemented\nand only for Fortran. Stubs are provided to show how it might be extended to\nsupport C.\n\nFind the project at \n\n.. |BSD3 License| image:: https://img.shields.io/badge/License-BSD_3--Clause-blue.svg\n :target: https://opensource.org/licenses/BSD-3-Clause\n\n.. |GitHub release| image:: https://img.shields.io/github/release/MetOffice/stylist.svg\n :target: https://github.com/MetOffice/stylist/\n\n.. |PyPI version| image:: https://badge.fury.io/py/stylist.svg\n :target: https://pypi.python.org/pypi/stylist/\n\n.. |Conda version| image:: https://img.shields.io/conda/vn/conda-forge/stylist.svg\n :target: https://anaconda.org/conda-forge/stylist\n\n.. |GitHub merge testing| image:: https://github.com/MetOffice/stylist/workflows/Merge%20Test/badge.svg\n :target: https://github.com/MetOffice/stylist/actions\n\n\nInstallation\n~~~~~~~~~~~~\n\nInstallation can be as simple as ``pip install stylist`` or\n``conda install -c conda-forge stylist``.\n\nAs always it is also possible to install from the project source using\n``pip install --editable .``. The source may be obtained by downloading a\ntarball or by cloning the repository.\n\n\nUsage\n~~~~~\n\nStylist provides a command-line tool ``stylist`` for normal use. It can also be\nused as a package if you want to integrate it with another tool. Documentation\nregarding this second option is maintained in the project wiki.\n\nOn the Command Line\n-------------------\n\nThe command-line tool is not complicated to use::\n\n stylist [-help] [-verbose]\n [-configuration FILENAME]\n [-style NAME]\n FILE ...\n\nThe only required arguments are a configuration file and one or more\nfilenames. These are the files which will be checked. If a directory is\nspecified then the tool will automatically descend into it checking all files\nwhich it recognises by extension.\n\nIf you want a running commentary of what the tool is doing then use the\n``-verbose`` argument.\n\nA configuration file may specified with ``-configuration`` . This file should\nbe formatted as documented below. There must be a configuration file which\ndefines at least one style. While the fallback mechanism which allows for user\nand site configurations has not been implemented it must be specified with this\nargument.\n\nThe configuration may define several styles, in which case one can be chosen\nusing the ``-style`` argument. If it is not then the first in the configuration\nfile will be used.\n\nConfiguration File\n------------------\n\nThe configuration file is a simple python script where variable definitions\nare used to define the configuration.\n\nStylist uses the concept of "File Pipes" to specify the series of steps needed\nto process a particular file type. They are defined by creating a ``FilePipe``\nobject and associated with a file extension by assignment to a variable.\n\nFor example::\n\n from stylist.source import (FilePipe,\n FortranSource,\n PFUnitProcessor,\n FortranPreprocessor)\n \n pf = FilePipe(FortranSource, PFUnitProcessor, FortranPreprocessor)\n\nHere a pipeline consisting the pFUnit processor followed by the Fortran\npreprocessor produces Fortran source. This pipeline should be used for all\nfiles with the ``.pf`` extension.\n\nStyles are collections of rules and are defined in a similar way. The variable\nname is the style name and the object is constructed with the rules which make up the style.\n\nAn illustrative example::\n\n from re import compile as recompile\n from stylist.style import Style\n from stylist.fortran import FortranCharacterset, KindPattern\n \n simple = Style(FortranCharacterset(),\n KindPattern(integer=recompile(r\'i_.+\'),\n real=recompile(r\'r_.+\')))\n'` According to the spec (see the link below), however, setuptools CANNOT consider this value unless `readme` is listed as `dynamic`. https://packaging.python.org/en/latest/specifications/declaring-project-metadata/ For the time being, `setuptools` will still consider the given value (as a **transitional** measure), but please note that future releases of setuptools will follow strictly the standard. To prevent this warning, you can list `readme` under `dynamic` or alternatively remove the `[project]` table from your file and rely entirely on other means of configuration. By 2023-Oct-30, you need to update your project and remove deprecated calls or your builds will no longer be supported. ******************************************************************************** !! _handle_missing_dynamic(dist, project_table) /usr/lib/python3.11/site-packages/setuptools/config/_apply_pyprojecttoml.py:62: _WouldIgnoreField: `authors` defined outside of `pyproject.toml` would be ignored. !! ******************************************************************************** ########################################################################## # configuration would be ignored/result in error due to `pyproject.toml` # ########################################################################## The following seems to be defined outside of `pyproject.toml`: `authors = 'Met Office'` According to the spec (see the link below), however, setuptools CANNOT consider this value unless `authors` is listed as `dynamic`. https://packaging.python.org/en/latest/specifications/declaring-project-metadata/ For the time being, `setuptools` will still consider the given value (as a **transitional** measure), but please note that future releases of setuptools will follow strictly the standard. To prevent this warning, you can list `authors` under `dynamic` or alternatively remove the `[project]` table from your file and rely entirely on other means of configuration. By 2023-Oct-30, you need to update your project and remove deprecated calls or your builds will no longer be supported. ******************************************************************************** !! _handle_missing_dynamic(dist, project_table) /usr/lib/python3.11/site-packages/setuptools/config/_apply_pyprojecttoml.py:62: _WouldIgnoreField: `keywords` defined outside of `pyproject.toml` would be ignored. !! ******************************************************************************** ########################################################################## # configuration would be ignored/result in error due to `pyproject.toml` # ########################################################################## The following seems to be defined outside of `pyproject.toml`: `keywords = ['linter fortran psyclone']` According to the spec (see the link below), however, setuptools CANNOT consider this value unless `keywords` is listed as `dynamic`. https://packaging.python.org/en/latest/specifications/declaring-project-metadata/ For the time being, `setuptools` will still consider the given value (as a **transitional** measure), but please note that future releases of setuptools will follow strictly the standard. To prevent this warning, you can list `keywords` under `dynamic` or alternatively remove the `[project]` table from your file and rely entirely on other means of configuration. By 2023-Oct-30, you need to update your project and remove deprecated calls or your builds will no longer be supported. ******************************************************************************** !! _handle_missing_dynamic(dist, project_table) running dist_info writing stylist.egg-info/PKG-INFO writing dependency_links to stylist.egg-info/dependency_links.txt writing entry points to stylist.egg-info/entry_points.txt writing requirements to stylist.egg-info/requires.txt writing top-level names to stylist.egg-info/top_level.txt reading manifest file 'stylist.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' adding license file 'LICENSE' writing manifest file 'stylist.egg-info/SOURCES.txt' creating '/builddir/build/BUILD/stylist-0.4.0/stylist-0.4.0.dist-info' Handling fparser (>=0.1.0) from hook generated metadata: Requires-Dist Requirement satisfied: fparser (>=0.1.0) (installed: fparser 0.1.0) Handling check-manifest ; extra == 'dev' from hook generated metadata: Requires-Dist Ignoring alien requirement: check-manifest ; extra == 'dev' Handling flake8 ; extra == 'dev' from hook generated metadata: Requires-Dist Ignoring alien requirement: flake8 ; extra == 'dev' Handling sphinx ; extra == 'docs' from hook generated metadata: Requires-Dist Ignoring alien requirement: sphinx ; extra == 'docs' Handling sphinx-autodoc-typehints ; extra == 'docs' from hook generated metadata: Requires-Dist Ignoring alien requirement: sphinx-autodoc-typehints ; extra == 'docs' Handling sphinx-rtd-theme ; extra == 'docs' from hook generated metadata: Requires-Dist Ignoring alien requirement: sphinx-rtd-theme ; extra == 'docs' Handling pytest ; extra == 'performance' from hook generated metadata: Requires-Dist Ignoring alien requirement: pytest ; extra == 'performance' Handling pytest-benchmark ; extra == 'performance' from hook generated metadata: Requires-Dist Ignoring alien requirement: pytest-benchmark ; extra == 'performance' Handling matplotlib ; extra == 'performance' from hook generated metadata: Requires-Dist Ignoring alien requirement: matplotlib ; extra == 'performance' Handling setuptools ; extra == 'release' from hook generated metadata: Requires-Dist Ignoring alien requirement: setuptools ; extra == 'release' Handling wheel ; extra == 'release' from hook generated metadata: Requires-Dist Ignoring alien requirement: wheel ; extra == 'release' Handling twine ; extra == 'release' from hook generated metadata: Requires-Dist Ignoring alien requirement: twine ; extra == 'release' Handling pytest ; extra == 'test' from hook generated metadata: Requires-Dist Ignoring alien requirement: pytest ; extra == 'test' Handling pytest-cov ; extra == 'test' from hook generated metadata: Requires-Dist Ignoring alien requirement: pytest-cov ; extra == 'test' Handling mypy ; extra == 'test' from hook generated metadata: Requires-Dist Ignoring alien requirement: mypy ; extra == 'test' + cat /builddir/build/BUILD/python-stylist-0.4.0-1.fc39.x86_64-pyproject-buildrequires + rm -rfv stylist-0.4.0.dist-info/ removed 'stylist-0.4.0.dist-info/LICENSE' removed 'stylist-0.4.0.dist-info/METADATA' removed 'stylist-0.4.0.dist-info/top_level.txt' removed 'stylist-0.4.0.dist-info/entry_points.txt' removed directory 'stylist-0.4.0.dist-info/' + RPM_EC=0 ++ jobs -p + exit 0 Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.aaB0UZ + umask 022 + cd /builddir/build/BUILD + CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer ' + export CFLAGS + CXXFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer ' + export CXXFLAGS + FFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules ' + export FFLAGS + FCFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules ' + export FCFLAGS + VALAFLAGS=-g + export VALAFLAGS + RUSTFLAGS='-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cforce-frame-pointers=yes -Clink-arg=-Wl,-z,relro -Clink-arg=-Wl,-z,now -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn' + export RUSTFLAGS + 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 -Wl,--build-id=sha1 -specs=/usr/lib/rpm/redhat/redhat-package-notes ' + export LDFLAGS + LT_SYS_LIBRARY_PATH=/usr/lib64: + export LT_SYS_LIBRARY_PATH + CC=gcc + export CC + CXX=g++ + export CXX + cd stylist-0.4.0 + mkdir -p /builddir/build/BUILD/stylist-0.4.0/.pyproject-builddir + CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer ' + 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 -Wl,--build-id=sha1 -specs=/usr/lib/rpm/redhat/redhat-package-notes ' + TMPDIR=/builddir/build/BUILD/stylist-0.4.0/.pyproject-builddir + /usr/bin/python3 -Bs /usr/lib/rpm/redhat/pyproject_wheel.py /builddir/build/BUILD/stylist-0.4.0/pyproject-wheeldir Processing /builddir/build/BUILD/stylist-0.4.0 Preparing metadata (pyproject.toml): started Running command Preparing metadata (pyproject.toml) /usr/lib/python3.11/site-packages/setuptools/config/pyprojecttoml.py:66: _BetaConfiguration: Support for `[tool.setuptools]` in `pyproject.toml` is still *beta*. config = read_configuration(filepath, True, ignore_option_errors, dist) /usr/lib/python3.11/site-packages/setuptools/config/_apply_pyprojecttoml.py:62: _WouldIgnoreField: `readme` defined outside of `pyproject.toml` would be ignored. !! ******************************************************************************** ########################################################################## # configuration would be ignored/result in error due to `pyproject.toml` # ########################################################################## The following seems to be defined outside of `pyproject.toml`: `readme = 'Stylist\n=======\n\n|BSD3 License| |GitHub release| |PyPI version| |Conda version| |GitHub merge testing|\n\nStylist is a tool for checking code style. It implements a framework which\nsupports multiple styles across multiple languages.\n\nBut aren\'t there many such tools out there, why create a new one?\n\nThe simple reason is that few of them support Fortran, a language still in\nwidespread use in the scientific computing domain. They can also tend towards\nthe zealous when enforcing the "one true style" whereas long running science\nmodels tend to diverge quite radically in what they like, style-wise.\n\nLarge models also tend to be implemented using more than one language so a\ntool which is capable of understanding all of them would be welcomed by\nscience developers.\n\nThis is the goal of Stylist development.\n\nThe project is still in its infancy so only a few rules have been implemented\nand only for Fortran. Stubs are provided to show how it might be extended to\nsupport C.\n\nFind the project at \n\n.. |BSD3 License| image:: https://img.shields.io/badge/License-BSD_3--Clause-blue.svg\n :target: https://opensource.org/licenses/BSD-3-Clause\n\n.. |GitHub release| image:: https://img.shields.io/github/release/MetOffice/stylist.svg\n :target: https://github.com/MetOffice/stylist/\n\n.. |PyPI version| image:: https://badge.fury.io/py/stylist.svg\n :target: https://pypi.python.org/pypi/stylist/\n\n.. |Conda version| image:: https://img.shields.io/conda/vn/conda-forge/stylist.svg\n :target: https://anaconda.org/conda-forge/stylist\n\n.. |GitHub merge testing| image:: https://github.com/MetOffice/stylist/workflows/Merge%20Test/badge.svg\n :target: https://github.com/MetOffice/stylist/actions\n\n\nInstallation\n~~~~~~~~~~~~\n\nInstallation can be as simple as ``pip install stylist`` or\n``conda install -c conda-forge stylist``.\n\nAs always it is also possible to install from the project source using\n``pip install --editable .``. The source may be obtained by downloading a\ntarball or by cloning the repository.\n\n\nUsage\n~~~~~\n\nStylist provides a command-line tool ``stylist`` for normal use. It can also be\nused as a package if you want to integrate it with another tool. Documentation\nregarding this second option is maintained in the project wiki.\n\nOn the Command Line\n-------------------\n\nThe command-line tool is not complicated to use::\n\n stylist [-help] [-verbose]\n [-configuration FILENAME]\n [-style NAME]\n FILE ...\n\nThe only required arguments are a configuration file and one or more\nfilenames. These are the files which will be checked. If a directory is\nspecified then the tool will automatically descend into it checking all files\nwhich it recognises by extension.\n\nIf you want a running commentary of what the tool is doing then use the\n``-verbose`` argument.\n\nA configuration file may specified with ``-configuration`` . This file should\nbe formatted as documented below. There must be a configuration file which\ndefines at least one style. While the fallback mechanism which allows for user\nand site configurations has not been implemented it must be specified with this\nargument.\n\nThe configuration may define several styles, in which case one can be chosen\nusing the ``-style`` argument. If it is not then the first in the configuration\nfile will be used.\n\nConfiguration File\n------------------\n\nThe configuration file is a simple python script where variable definitions\nare used to define the configuration.\n\nStylist uses the concept of "File Pipes" to specify the series of steps needed\nto process a particular file type. They are defined by creating a ``FilePipe``\nobject and associated with a file extension by assignment to a variable.\n\nFor example::\n\n from stylist.source import (FilePipe,\n FortranSource,\n PFUnitProcessor,\n FortranPreprocessor)\n \n pf = FilePipe(FortranSource, PFUnitProcessor, FortranPreprocessor)\n\nHere a pipeline consisting the pFUnit processor followed by the Fortran\npreprocessor produces Fortran source. This pipeline should be used for all\nfiles with the ``.pf`` extension.\n\nStyles are collections of rules and are defined in a similar way. The variable\nname is the style name and the object is constructed with the rules which make up the style.\n\nAn illustrative example::\n\n from re import compile as recompile\n from stylist.style import Style\n from stylist.fortran import FortranCharacterset, KindPattern\n \n simple = Style(FortranCharacterset(),\n KindPattern(integer=recompile(r\'i_.+\'),\n real=recompile(r\'r_.+\')))\n'` According to the spec (see the link below), however, setuptools CANNOT consider this value unless `readme` is listed as `dynamic`. https://packaging.python.org/en/latest/specifications/declaring-project-metadata/ For the time being, `setuptools` will still consider the given value (as a **transitional** measure), but please note that future releases of setuptools will follow strictly the standard. To prevent this warning, you can list `readme` under `dynamic` or alternatively remove the `[project]` table from your file and rely entirely on other means of configuration. By 2023-Oct-30, you need to update your project and remove deprecated calls or your builds will no longer be supported. ******************************************************************************** !! _handle_missing_dynamic(dist, project_table) /usr/lib/python3.11/site-packages/setuptools/config/_apply_pyprojecttoml.py:62: _WouldIgnoreField: `authors` defined outside of `pyproject.toml` would be ignored. !! ******************************************************************************** ########################################################################## # configuration would be ignored/result in error due to `pyproject.toml` # ########################################################################## The following seems to be defined outside of `pyproject.toml`: `authors = 'Met Office'` According to the spec (see the link below), however, setuptools CANNOT consider this value unless `authors` is listed as `dynamic`. https://packaging.python.org/en/latest/specifications/declaring-project-metadata/ For the time being, `setuptools` will still consider the given value (as a **transitional** measure), but please note that future releases of setuptools will follow strictly the standard. To prevent this warning, you can list `authors` under `dynamic` or alternatively remove the `[project]` table from your file and rely entirely on other means of configuration. By 2023-Oct-30, you need to update your project and remove deprecated calls or your builds will no longer be supported. ******************************************************************************** !! _handle_missing_dynamic(dist, project_table) /usr/lib/python3.11/site-packages/setuptools/config/_apply_pyprojecttoml.py:62: _WouldIgnoreField: `keywords` defined outside of `pyproject.toml` would be ignored. !! ******************************************************************************** ########################################################################## # configuration would be ignored/result in error due to `pyproject.toml` # ########################################################################## The following seems to be defined outside of `pyproject.toml`: `keywords = ['linter fortran psyclone']` According to the spec (see the link below), however, setuptools CANNOT consider this value unless `keywords` is listed as `dynamic`. https://packaging.python.org/en/latest/specifications/declaring-project-metadata/ For the time being, `setuptools` will still consider the given value (as a **transitional** measure), but please note that future releases of setuptools will follow strictly the standard. To prevent this warning, you can list `keywords` under `dynamic` or alternatively remove the `[project]` table from your file and rely entirely on other means of configuration. By 2023-Oct-30, you need to update your project and remove deprecated calls or your builds will no longer be supported. ******************************************************************************** !! _handle_missing_dynamic(dist, project_table) running dist_info creating /builddir/build/BUILD/stylist-0.4.0/.pyproject-builddir/pip-modern-metadata-tzkuvsur/stylist.egg-info writing /builddir/build/BUILD/stylist-0.4.0/.pyproject-builddir/pip-modern-metadata-tzkuvsur/stylist.egg-info/PKG-INFO writing dependency_links to /builddir/build/BUILD/stylist-0.4.0/.pyproject-builddir/pip-modern-metadata-tzkuvsur/stylist.egg-info/dependency_links.txt writing entry points to /builddir/build/BUILD/stylist-0.4.0/.pyproject-builddir/pip-modern-metadata-tzkuvsur/stylist.egg-info/entry_points.txt writing requirements to /builddir/build/BUILD/stylist-0.4.0/.pyproject-builddir/pip-modern-metadata-tzkuvsur/stylist.egg-info/requires.txt writing top-level names to /builddir/build/BUILD/stylist-0.4.0/.pyproject-builddir/pip-modern-metadata-tzkuvsur/stylist.egg-info/top_level.txt writing manifest file '/builddir/build/BUILD/stylist-0.4.0/.pyproject-builddir/pip-modern-metadata-tzkuvsur/stylist.egg-info/SOURCES.txt' reading manifest file '/builddir/build/BUILD/stylist-0.4.0/.pyproject-builddir/pip-modern-metadata-tzkuvsur/stylist.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' adding license file 'LICENSE' writing manifest file '/builddir/build/BUILD/stylist-0.4.0/.pyproject-builddir/pip-modern-metadata-tzkuvsur/stylist.egg-info/SOURCES.txt' creating '/builddir/build/BUILD/stylist-0.4.0/.pyproject-builddir/pip-modern-metadata-tzkuvsur/stylist-0.4.0.dist-info' Preparing metadata (pyproject.toml): finished with status 'done' Building wheels for collected packages: stylist Building wheel for stylist (pyproject.toml): started Running command Building wheel for stylist (pyproject.toml) /usr/lib/python3.11/site-packages/setuptools/config/pyprojecttoml.py:66: _BetaConfiguration: Support for `[tool.setuptools]` in `pyproject.toml` is still *beta*. config = read_configuration(filepath, True, ignore_option_errors, dist) /usr/lib/python3.11/site-packages/setuptools/config/_apply_pyprojecttoml.py:62: _WouldIgnoreField: `readme` defined outside of `pyproject.toml` would be ignored. !! ******************************************************************************** ########################################################################## # configuration would be ignored/result in error due to `pyproject.toml` # ########################################################################## The following seems to be defined outside of `pyproject.toml`: `readme = 'Stylist\n=======\n\n|BSD3 License| |GitHub release| |PyPI version| |Conda version| |GitHub merge testing|\n\nStylist is a tool for checking code style. It implements a framework which\nsupports multiple styles across multiple languages.\n\nBut aren\'t there many such tools out there, why create a new one?\n\nThe simple reason is that few of them support Fortran, a language still in\nwidespread use in the scientific computing domain. They can also tend towards\nthe zealous when enforcing the "one true style" whereas long running science\nmodels tend to diverge quite radically in what they like, style-wise.\n\nLarge models also tend to be implemented using more than one language so a\ntool which is capable of understanding all of them would be welcomed by\nscience developers.\n\nThis is the goal of Stylist development.\n\nThe project is still in its infancy so only a few rules have been implemented\nand only for Fortran. Stubs are provided to show how it might be extended to\nsupport C.\n\nFind the project at \n\n.. |BSD3 License| image:: https://img.shields.io/badge/License-BSD_3--Clause-blue.svg\n :target: https://opensource.org/licenses/BSD-3-Clause\n\n.. |GitHub release| image:: https://img.shields.io/github/release/MetOffice/stylist.svg\n :target: https://github.com/MetOffice/stylist/\n\n.. |PyPI version| image:: https://badge.fury.io/py/stylist.svg\n :target: https://pypi.python.org/pypi/stylist/\n\n.. |Conda version| image:: https://img.shields.io/conda/vn/conda-forge/stylist.svg\n :target: https://anaconda.org/conda-forge/stylist\n\n.. |GitHub merge testing| image:: https://github.com/MetOffice/stylist/workflows/Merge%20Test/badge.svg\n :target: https://github.com/MetOffice/stylist/actions\n\n\nInstallation\n~~~~~~~~~~~~\n\nInstallation can be as simple as ``pip install stylist`` or\n``conda install -c conda-forge stylist``.\n\nAs always it is also possible to install from the project source using\n``pip install --editable .``. The source may be obtained by downloading a\ntarball or by cloning the repository.\n\n\nUsage\n~~~~~\n\nStylist provides a command-line tool ``stylist`` for normal use. It can also be\nused as a package if you want to integrate it with another tool. Documentation\nregarding this second option is maintained in the project wiki.\n\nOn the Command Line\n-------------------\n\nThe command-line tool is not complicated to use::\n\n stylist [-help] [-verbose]\n [-configuration FILENAME]\n [-style NAME]\n FILE ...\n\nThe only required arguments are a configuration file and one or more\nfilenames. These are the files which will be checked. If a directory is\nspecified then the tool will automatically descend into it checking all files\nwhich it recognises by extension.\n\nIf you want a running commentary of what the tool is doing then use the\n``-verbose`` argument.\n\nA configuration file may specified with ``-configuration`` . This file should\nbe formatted as documented below. There must be a configuration file which\ndefines at least one style. While the fallback mechanism which allows for user\nand site configurations has not been implemented it must be specified with this\nargument.\n\nThe configuration may define several styles, in which case one can be chosen\nusing the ``-style`` argument. If it is not then the first in the configuration\nfile will be used.\n\nConfiguration File\n------------------\n\nThe configuration file is a simple python script where variable definitions\nare used to define the configuration.\n\nStylist uses the concept of "File Pipes" to specify the series of steps needed\nto process a particular file type. They are defined by creating a ``FilePipe``\nobject and associated with a file extension by assignment to a variable.\n\nFor example::\n\n from stylist.source import (FilePipe,\n FortranSource,\n PFUnitProcessor,\n FortranPreprocessor)\n \n pf = FilePipe(FortranSource, PFUnitProcessor, FortranPreprocessor)\n\nHere a pipeline consisting the pFUnit processor followed by the Fortran\npreprocessor produces Fortran source. This pipeline should be used for all\nfiles with the ``.pf`` extension.\n\nStyles are collections of rules and are defined in a similar way. The variable\nname is the style name and the object is constructed with the rules which make up the style.\n\nAn illustrative example::\n\n from re import compile as recompile\n from stylist.style import Style\n from stylist.fortran import FortranCharacterset, KindPattern\n \n simple = Style(FortranCharacterset(),\n KindPattern(integer=recompile(r\'i_.+\'),\n real=recompile(r\'r_.+\')))\n'` According to the spec (see the link below), however, setuptools CANNOT consider this value unless `readme` is listed as `dynamic`. https://packaging.python.org/en/latest/specifications/declaring-project-metadata/ For the time being, `setuptools` will still consider the given value (as a **transitional** measure), but please note that future releases of setuptools will follow strictly the standard. To prevent this warning, you can list `readme` under `dynamic` or alternatively remove the `[project]` table from your file and rely entirely on other means of configuration. By 2023-Oct-30, you need to update your project and remove deprecated calls or your builds will no longer be supported. ******************************************************************************** !! _handle_missing_dynamic(dist, project_table) /usr/lib/python3.11/site-packages/setuptools/config/_apply_pyprojecttoml.py:62: _WouldIgnoreField: `authors` defined outside of `pyproject.toml` would be ignored. !! ******************************************************************************** ########################################################################## # configuration would be ignored/result in error due to `pyproject.toml` # ########################################################################## The following seems to be defined outside of `pyproject.toml`: `authors = 'Met Office'` According to the spec (see the link below), however, setuptools CANNOT consider this value unless `authors` is listed as `dynamic`. https://packaging.python.org/en/latest/specifications/declaring-project-metadata/ For the time being, `setuptools` will still consider the given value (as a **transitional** measure), but please note that future releases of setuptools will follow strictly the standard. To prevent this warning, you can list `authors` under `dynamic` or alternatively remove the `[project]` table from your file and rely entirely on other means of configuration. By 2023-Oct-30, you need to update your project and remove deprecated calls or your builds will no longer be supported. ******************************************************************************** !! _handle_missing_dynamic(dist, project_table) /usr/lib/python3.11/site-packages/setuptools/config/_apply_pyprojecttoml.py:62: _WouldIgnoreField: `keywords` defined outside of `pyproject.toml` would be ignored. !! ******************************************************************************** ########################################################################## # configuration would be ignored/result in error due to `pyproject.toml` # ########################################################################## The following seems to be defined outside of `pyproject.toml`: `keywords = ['linter fortran psyclone']` According to the spec (see the link below), however, setuptools CANNOT consider this value unless `keywords` is listed as `dynamic`. https://packaging.python.org/en/latest/specifications/declaring-project-metadata/ For the time being, `setuptools` will still consider the given value (as a **transitional** measure), but please note that future releases of setuptools will follow strictly the standard. To prevent this warning, you can list `keywords` under `dynamic` or alternatively remove the `[project]` table from your file and rely entirely on other means of configuration. By 2023-Oct-30, you need to update your project and remove deprecated calls or your builds will no longer be supported. ******************************************************************************** !! _handle_missing_dynamic(dist, project_table) running bdist_wheel running build running build_py creating build creating build/lib creating build/lib/stylist copying source/stylist/style.py -> build/lib/stylist copying source/stylist/source.py -> build/lib/stylist copying source/stylist/rule.py -> build/lib/stylist copying source/stylist/issue.py -> build/lib/stylist copying source/stylist/fortran.py -> build/lib/stylist copying source/stylist/engine.py -> build/lib/stylist copying source/stylist/configuration.py -> build/lib/stylist copying source/stylist/__main__.py -> build/lib/stylist copying source/stylist/__init__.py -> build/lib/stylist running egg_info writing source/stylist.egg-info/PKG-INFO writing dependency_links to source/stylist.egg-info/dependency_links.txt writing entry points to source/stylist.egg-info/entry_points.txt writing requirements to source/stylist.egg-info/requires.txt writing top-level names to source/stylist.egg-info/top_level.txt reading manifest file 'source/stylist.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' adding license file 'LICENSE' writing manifest file 'source/stylist.egg-info/SOURCES.txt' 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/stylist copying build/lib/stylist/__init__.py -> build/bdist.linux-x86_64/wheel/stylist copying build/lib/stylist/__main__.py -> build/bdist.linux-x86_64/wheel/stylist copying build/lib/stylist/configuration.py -> build/bdist.linux-x86_64/wheel/stylist copying build/lib/stylist/engine.py -> build/bdist.linux-x86_64/wheel/stylist copying build/lib/stylist/fortran.py -> build/bdist.linux-x86_64/wheel/stylist copying build/lib/stylist/issue.py -> build/bdist.linux-x86_64/wheel/stylist copying build/lib/stylist/rule.py -> build/bdist.linux-x86_64/wheel/stylist copying build/lib/stylist/source.py -> build/bdist.linux-x86_64/wheel/stylist copying build/lib/stylist/style.py -> build/bdist.linux-x86_64/wheel/stylist running install_egg_info Copying source/stylist.egg-info to build/bdist.linux-x86_64/wheel/stylist-0.4.0-py3.11.egg-info running install_scripts creating build/bdist.linux-x86_64/wheel/stylist-0.4.0.dist-info/WHEEL creating '/builddir/build/BUILD/stylist-0.4.0/.pyproject-builddir/pip-wheel-eb6y1adn/.tmp-vdws3nta/stylist-0.4.0-py3-none-any.whl' and adding 'build/bdist.linux-x86_64/wheel' to it adding 'stylist/__init__.py' adding 'stylist/__main__.py' adding 'stylist/configuration.py' adding 'stylist/engine.py' adding 'stylist/fortran.py' adding 'stylist/issue.py' adding 'stylist/rule.py' adding 'stylist/source.py' adding 'stylist/style.py' adding 'stylist-0.4.0.dist-info/LICENSE' adding 'stylist-0.4.0.dist-info/METADATA' adding 'stylist-0.4.0.dist-info/WHEEL' adding 'stylist-0.4.0.dist-info/entry_points.txt' adding 'stylist-0.4.0.dist-info/top_level.txt' adding 'stylist-0.4.0.dist-info/RECORD' removing build/bdist.linux-x86_64/wheel Building wheel for stylist (pyproject.toml): finished with status 'done' Created wheel for stylist: filename=stylist-0.4.0-py3-none-any.whl size=23206 sha256=b56c6df1f7d9c175bc506f3981352fc0824cc7c6312203776294e701eec00192 Stored in directory: /builddir/.cache/pip/wheels/98/fe/9e/fe462247b9df422e0b633ece19bcc16271dbd730ec8d969eb6 Successfully built stylist + RPM_EC=0 ++ jobs -p + exit 0 Executing(%install): /bin/sh -e /var/tmp/rpm-tmp.6Ej7WF + umask 022 + cd /builddir/build/BUILD + '[' /builddir/build/BUILDROOT/python-stylist-0.4.0-1.fc39.x86_64 '!=' / ']' + rm -rf /builddir/build/BUILDROOT/python-stylist-0.4.0-1.fc39.x86_64 ++ dirname /builddir/build/BUILDROOT/python-stylist-0.4.0-1.fc39.x86_64 + mkdir -p /builddir/build/BUILDROOT + mkdir /builddir/build/BUILDROOT/python-stylist-0.4.0-1.fc39.x86_64 + CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer ' + export CFLAGS + CXXFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer ' + export CXXFLAGS + FFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules ' + export FFLAGS + FCFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules ' + export FCFLAGS + VALAFLAGS=-g + export VALAFLAGS + RUSTFLAGS='-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cforce-frame-pointers=yes -Clink-arg=-Wl,-z,relro -Clink-arg=-Wl,-z,now -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn' + export RUSTFLAGS + 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 -Wl,--build-id=sha1 -specs=/usr/lib/rpm/redhat/redhat-package-notes ' + export LDFLAGS + LT_SYS_LIBRARY_PATH=/usr/lib64: + export LT_SYS_LIBRARY_PATH + CC=gcc + export CC + CXX=g++ + export CXX + cd stylist-0.4.0 ++ xargs basename --multiple ++ ls /builddir/build/BUILD/stylist-0.4.0/pyproject-wheeldir/stylist-0.4.0-py3-none-any.whl ++ sed -E 's/([^-]+)-([^-]+)-.+\.whl/\1==\2/' + specifier=stylist==0.4.0 + TMPDIR=/builddir/build/BUILD/stylist-0.4.0/.pyproject-builddir + /usr/bin/python3 -m pip install --root /builddir/build/BUILDROOT/python-stylist-0.4.0-1.fc39.x86_64 --prefix /usr --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/stylist-0.4.0/pyproject-wheeldir stylist==0.4.0 Using pip 23.0.1 from /usr/lib/python3.11/site-packages/pip (python 3.11) Looking in links: /builddir/build/BUILD/stylist-0.4.0/pyproject-wheeldir Processing ./pyproject-wheeldir/stylist-0.4.0-py3-none-any.whl Installing collected packages: stylist Creating /builddir/build/BUILDROOT/python-stylist-0.4.0-1.fc39.x86_64/usr/bin changing mode of /builddir/build/BUILDROOT/python-stylist-0.4.0-1.fc39.x86_64/usr/bin/stylist to 755 Successfully installed stylist-0.4.0 + '[' -d /builddir/build/BUILDROOT/python-stylist-0.4.0-1.fc39.x86_64/usr/bin ']' + '[' -z sP ']' + shebang_flags=-kasP + /usr/bin/python3 -B /usr/lib/rpm/redhat/pathfix.py -pni /usr/bin/python3 -kasP /builddir/build/BUILDROOT/python-stylist-0.4.0-1.fc39.x86_64/usr/bin/stylist /builddir/build/BUILDROOT/python-stylist-0.4.0-1.fc39.x86_64/usr/bin/stylist: updating + rm -rfv /builddir/build/BUILDROOT/python-stylist-0.4.0-1.fc39.x86_64/usr/bin/__pycache__ + rm -f /builddir/build/BUILD/python-stylist-0.4.0-1.fc39.x86_64-pyproject-ghost-distinfo + site_dirs=() + '[' -d /builddir/build/BUILDROOT/python-stylist-0.4.0-1.fc39.x86_64/usr/lib/python3.11/site-packages ']' + site_dirs+=("/usr/lib/python3.11/site-packages") + '[' /builddir/build/BUILDROOT/python-stylist-0.4.0-1.fc39.x86_64/usr/lib64/python3.11/site-packages '!=' /builddir/build/BUILDROOT/python-stylist-0.4.0-1.fc39.x86_64/usr/lib/python3.11/site-packages ']' + '[' -d /builddir/build/BUILDROOT/python-stylist-0.4.0-1.fc39.x86_64/usr/lib64/python3.11/site-packages ']' + for site_dir in ${site_dirs[@]} + for distinfo in /builddir/build/BUILDROOT/python-stylist-0.4.0-1.fc39.x86_64$site_dir/*.dist-info + echo '%ghost /usr/lib/python3.11/site-packages/stylist-0.4.0.dist-info' + sed -i s/pip/rpm/ /builddir/build/BUILDROOT/python-stylist-0.4.0-1.fc39.x86_64/usr/lib/python3.11/site-packages/stylist-0.4.0.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-stylist-0.4.0-1.fc39.x86_64 --record /builddir/build/BUILDROOT/python-stylist-0.4.0-1.fc39.x86_64/usr/lib/python3.11/site-packages/stylist-0.4.0.dist-info/RECORD --output /builddir/build/BUILD/python-stylist-0.4.0-1.fc39.x86_64-pyproject-record + rm -fv /builddir/build/BUILDROOT/python-stylist-0.4.0-1.fc39.x86_64/usr/lib/python3.11/site-packages/stylist-0.4.0.dist-info/RECORD removed '/builddir/build/BUILDROOT/python-stylist-0.4.0-1.fc39.x86_64/usr/lib/python3.11/site-packages/stylist-0.4.0.dist-info/RECORD' + rm -fv /builddir/build/BUILDROOT/python-stylist-0.4.0-1.fc39.x86_64/usr/lib/python3.11/site-packages/stylist-0.4.0.dist-info/REQUESTED removed '/builddir/build/BUILDROOT/python-stylist-0.4.0-1.fc39.x86_64/usr/lib/python3.11/site-packages/stylist-0.4.0.dist-info/REQUESTED' ++ wc -l /builddir/build/BUILD/python-stylist-0.4.0-1.fc39.x86_64-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/python-stylist-0.4.0-1.fc39.x86_64-pyproject-files --output-modules /builddir/build/BUILD/python-stylist-0.4.0-1.fc39.x86_64-pyproject-modules --buildroot /builddir/build/BUILDROOT/python-stylist-0.4.0-1.fc39.x86_64 --sitelib /usr/lib/python3.11/site-packages --sitearch /usr/lib64/python3.11/site-packages --python-version 3.11 --pyproject-record /builddir/build/BUILD/python-stylist-0.4.0-1.fc39.x86_64-pyproject-record --prefix /usr '*' +auto + /usr/bin/find-debuginfo -j2 --strict-build-id -m -i --build-id-seed 0.4.0-1.fc39 --unique-debug-suffix -0.4.0-1.fc39.x86_64 --unique-debug-src-base python-stylist-0.4.0-1.fc39.x86_64 --run-dwz --dwz-low-mem-die-limit 10000000 --dwz-max-die-limit 110000000 -S debugsourcefiles.list /builddir/build/BUILD/stylist-0.4.0 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/check-rpaths + /usr/lib/rpm/redhat/brp-mangle-shebangs + /usr/lib/rpm/brp-remove-la-files + env /usr/lib/rpm/redhat/brp-python-bytecompile '' 1 0 -j2 Bytecompiling .py files below /builddir/build/BUILDROOT/python-stylist-0.4.0-1.fc39.x86_64/usr/lib/python3.11 using python3.11 + /usr/lib/rpm/redhat/brp-python-hardlink Executing(%check): /bin/sh -e /var/tmp/rpm-tmp.cmAAXg + umask 022 + cd /builddir/build/BUILD + CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer ' + export CFLAGS + CXXFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer ' + export CXXFLAGS + FFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules ' + export FFLAGS + FCFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules ' + export FCFLAGS + VALAFLAGS=-g + export VALAFLAGS + RUSTFLAGS='-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cforce-frame-pointers=yes -Clink-arg=-Wl,-z,relro -Clink-arg=-Wl,-z,now -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn' + export RUSTFLAGS + 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 -Wl,--build-id=sha1 -specs=/usr/lib/rpm/redhat/redhat-package-notes ' + export LDFLAGS + LT_SYS_LIBRARY_PATH=/usr/lib64: + export LT_SYS_LIBRARY_PATH + CC=gcc + export CC + CXX=g++ + export CXX + cd stylist-0.4.0 + '[' '!' -f /builddir/build/BUILD/python-stylist-0.4.0-1.fc39.x86_64-pyproject-modules ']' + PATH=/builddir/build/BUILDROOT/python-stylist-0.4.0-1.fc39.x86_64/usr/bin:/builddir/.local/bin:/builddir/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/sbin + PYTHONPATH=/builddir/build/BUILDROOT/python-stylist-0.4.0-1.fc39.x86_64/usr/lib64/python3.11/site-packages:/builddir/build/BUILDROOT/python-stylist-0.4.0-1.fc39.x86_64/usr/lib/python3.11/site-packages + _PYTHONSITE=/builddir/build/BUILDROOT/python-stylist-0.4.0-1.fc39.x86_64/usr/lib64/python3.11/site-packages:/builddir/build/BUILDROOT/python-stylist-0.4.0-1.fc39.x86_64/usr/lib/python3.11/site-packages + PYTHONDONTWRITEBYTECODE=1 + /usr/bin/python3 -sP /usr/lib/rpm/redhat/import_all_modules.py -f /builddir/build/BUILD/python-stylist-0.4.0-1.fc39.x86_64-pyproject-modules -t Check import: stylist + RPM_EC=0 ++ jobs -p + exit 0 Processing files: python3-stylist-0.4.0-1.fc39.noarch Provides: python-stylist = 0.4.0-1.fc39 python3-stylist = 0.4.0-1.fc39 python3.11-stylist = 0.4.0-1.fc39 python3.11dist(stylist) = 0.4 python3dist(stylist) = 0.4 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: /usr/bin/python3 python(abi) = 3.11 python3.11dist(fparser) >= 0.1 Checking for unpackaged file(s): /usr/lib/rpm/check-files /builddir/build/BUILDROOT/python-stylist-0.4.0-1.fc39.x86_64 Wrote: /builddir/build/SRPMS/python-stylist-0.4.0-1.fc39.src.rpm Wrote: /builddir/build/RPMS/python3-stylist-0.4.0-1.fc39.noarch.rpm Executing(%clean): /bin/sh -e /var/tmp/rpm-tmp.7HLwfX + umask 022 + cd /builddir/build/BUILD + cd stylist-0.4.0 + /usr/bin/rm -rf /builddir/build/BUILDROOT/python-stylist-0.4.0-1.fc39.x86_64 + RPM_EC=0 ++ jobs -p + exit 0 Executing(rmbuild): /bin/sh -e /var/tmp/rpm-tmp.CQxEXf + umask 022 + cd /builddir/build/BUILD + rm -rf stylist-0.4.0 stylist-0.4.0.gemspec + RPM_EC=0 ++ jobs -p + exit 0 Child return code was: 0