Mock Version: 6.1
Mock Version: 6.1
Mock Version: 6.1
ENTER ['do_with_status'](['bash', '--login', '-c', '/usr/bin/rpmbuild -bs --noclean --target noarch --nodeps /builddir/build/SPECS/python-django-markdownx.spec'], chrootPath='/var/lib/mock/f43-build-58513383-6566072/root'env={'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;<mock-chroot>\\007"', 'PS1': '<mock-chroot> \\s-\\v\\$ ', 'LANG': 'C.UTF-8'}shell=Falselogger=<mockbuild.trace_decorator.getLog object at 0x7fd582df5370>timeout=201600uid=1000gid=425user='mockbuild'unshare_net=TrueprintOutput=Falsenspawn_args=['--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.mvz405oc:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/control', '--bind=/dev/fuse', '--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'])
Using nspawn with args ['--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.mvz405oc:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/control', '--bind=/dev/fuse', '--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', '1b1e5d1aebcf4a728577adfc3d328778', '-D', '/var/lib/mock/f43-build-58513383-6566072/root', '-a', '-u', 'mockbuild', '--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.mvz405oc:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/control', '--bind=/dev/fuse', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11', '--console=pipe', '--setenv=TERM=vt100', '--setenv=SHELL=/bin/bash', '--setenv=HOME=/builddir', '--setenv=HOSTNAME=mock', '--setenv=PATH=/usr/bin:/bin:/usr/sbin:/sbin', '--setenv=PROMPT_COMMAND=printf "\\033]0;<mock-chroot>\\007"', '--setenv=PS1=<mock-chroot> \\s-\\v\\$ ', '--setenv=LANG=C.UTF-8', '--resolv-conf=off', 'bash', '--login', '-c', '/usr/bin/rpmbuild -bs --noclean --target noarch --nodeps /builddir/build/SPECS/python-django-markdownx.spec'] with env {'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;<mock-chroot>\\007"', 'PS1': '<mock-chroot> \\s-\\v\\$ ', 'LANG': 'C.UTF-8', 'SYSTEMD_NSPAWN_TMPFS_TMP': '0', 'SYSTEMD_SECCOMP': '0'} and shell False
Building target platforms: noarch
Building for target noarch
setting SOURCE_DATE_EPOCH=1737158400
Wrote: /builddir/build/SRPMS/python-django-markdownx-3.0.1-19.fc43.src.rpm
Child return code was: 0
ENTER ['do_with_status'](['bash', '--login', '-c', '/usr/bin/rpmbuild -bb --noclean --target noarch --nodeps /builddir/build/SPECS/python-django-markdownx.spec'], chrootPath='/var/lib/mock/f43-build-58513383-6566072/root'env={'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;<mock-chroot>\\007"', 'PS1': '<mock-chroot> \\s-\\v\\$ ', 'LANG': 'C.UTF-8'}shell=Falselogger=<mockbuild.trace_decorator.getLog object at 0x7fd582df5370>timeout=201600uid=1000gid=425user='mockbuild'unshare_net=TrueprintOutput=Falsenspawn_args=['--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.mvz405oc:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/control', '--bind=/dev/fuse', '--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'])
Using nspawn with args ['--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.mvz405oc:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/control', '--bind=/dev/fuse', '--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', '7bb3cbb8643c42c8a83629159d522fc7', '-D', '/var/lib/mock/f43-build-58513383-6566072/root', '-a', '-u', 'mockbuild', '--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.mvz405oc:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/control', '--bind=/dev/fuse', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11', '--console=pipe', '--setenv=TERM=vt100', '--setenv=SHELL=/bin/bash', '--setenv=HOME=/builddir', '--setenv=HOSTNAME=mock', '--setenv=PATH=/usr/bin:/bin:/usr/sbin:/sbin', '--setenv=PROMPT_COMMAND=printf "\\033]0;<mock-chroot>\\007"', '--setenv=PS1=<mock-chroot> \\s-\\v\\$ ', '--setenv=LANG=C.UTF-8', '--resolv-conf=off', 'bash', '--login', '-c', '/usr/bin/rpmbuild -bb --noclean --target noarch --nodeps /builddir/build/SPECS/python-django-markdownx.spec'] with env {'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;<mock-chroot>\\007"', 'PS1': '<mock-chroot> \\s-\\v\\$ ', 'LANG': 'C.UTF-8', 'SYSTEMD_NSPAWN_TMPFS_TMP': '0', 'SYSTEMD_SECCOMP': '0'} and shell False
Building target platforms: noarch
Building for target noarch
setting SOURCE_DATE_EPOCH=1737158400
Executing(%mkbuilddir): /bin/sh -e /var/tmp/rpm-tmp.qAxQo2
Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.wpa96I
+ umask 022
+ cd /builddir/build/BUILD/python-django-markdownx-3.0.1-build
+ cd /builddir/build/BUILD/python-django-markdownx-3.0.1-build
+ rm -rf django-markdownx-3.0.1
+ /usr/lib/rpm/rpmuncompress -x /builddir/build/SOURCES/django-markdownx-3.0.1.tar.gz
+ STATUS=0
+ '[' 0 -ne 0 ']'
+ cd django-markdownx-3.0.1
+ /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w .
+ rm -rf django-markdownx.egg-info
+ rm -rf markdownx/static/.DS_Store
+ rm -rf markdownx/static/markdownx/.DS_Store
+ rm -rf markdownx/static/markdownx/admin/.DS_Store
+ rm -rf markdownx/templates/.DS_Store
+ rm -rf markdownx/templates/markdownx/.DS_Store
+ chmod 0644 README.rst
+ RPM_EC=0
++ jobs -p
+ exit 0
Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.g0sFH8
+ umask 022
+ cd /builddir/build/BUILD/python-django-markdownx-3.0.1-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 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -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 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -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 -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 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib/gfortran/modules '
+ export FFLAGS
+ FCFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -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 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib/gfortran/modules '
+ export FCFLAGS
+ VALAFLAGS=-g
+ export VALAFLAGS
+ RUSTFLAGS='-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Cforce-frame-pointers=yes --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/lib:
+ export LT_SYS_LIBRARY_PATH
+ CC=gcc
+ export CC
+ CXX=g++
+ export CXX
+ cd django-markdownx-3.0.1
+ 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 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -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  '
+ /usr/bin/python3 setup.py build '--executable=/usr/bin/python3 -sP'
/usr/lib/python3.13/site-packages/setuptools/_distutils/dist.py:289: UserWarning: Unknown distribution option: 'tests_require'
  warnings.warn(msg)
/usr/lib/python3.13/site-packages/setuptools/_distutils/dist.py:289: UserWarning: Unknown distribution option: 'test_suite'
  warnings.warn(msg)
running build
running build_py
creating build/lib/markdownx
copying markdownx/__init__.py -> build/lib/markdownx
copying markdownx/admin.py -> build/lib/markdownx
copying markdownx/exceptions.py -> build/lib/markdownx
copying markdownx/fields.py -> build/lib/markdownx
copying markdownx/forms.py -> build/lib/markdownx
copying markdownx/models.py -> build/lib/markdownx
copying markdownx/settings.py -> build/lib/markdownx
copying markdownx/urls.py -> build/lib/markdownx
copying markdownx/utils.py -> build/lib/markdownx
copying markdownx/views.py -> build/lib/markdownx
copying markdownx/widgets.py -> build/lib/markdownx
creating build/lib/markdownx/tests
copying markdownx/tests/__init__.py -> build/lib/markdownx/tests
copying markdownx/tests/models.py -> build/lib/markdownx/tests
copying markdownx/tests/tests.py -> build/lib/markdownx/tests
copying markdownx/tests/urls.py -> build/lib/markdownx/tests
copying markdownx/tests/views.py -> build/lib/markdownx/tests
running egg_info
creating django_markdownx.egg-info
writing django_markdownx.egg-info/PKG-INFO
writing dependency_links to django_markdownx.egg-info/dependency_links.txt
writing requirements to django_markdownx.egg-info/requires.txt
writing top-level names to django_markdownx.egg-info/top_level.txt
writing manifest file 'django_markdownx.egg-info/SOURCES.txt'
reading manifest file 'django_markdownx.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
adding license file 'LICENSE'
writing manifest file 'django_markdownx.egg-info/SOURCES.txt'
/usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'markdownx.locale.de.LC_MESSAGES' is absent from the `packages` configuration.
!!
        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'markdownx.locale.de.LC_MESSAGES' as an importable package[^1],
        but it is absent from setuptools' `packages` configuration.
        This leads to an ambiguous overall configuration. If you want to distribute this
        package, please make sure that 'markdownx.locale.de.LC_MESSAGES' is explicitly added
        to the `packages` configuration field.
        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).
        You can read more about "package discovery" on setuptools documentation page:
        - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
        If you don't want 'markdownx.locale.de.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'markdownx.locale.de.LC_MESSAGES' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.
        You can read more about "package data files" on setuptools documentation page:
        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html
        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************
!!
  check.warn(importable)
creating build/lib/markdownx/locale/de/LC_MESSAGES
/usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'markdownx.locale.du.LC_MESSAGES' is absent from the `packages` configuration.
!!
        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'markdownx.locale.du.LC_MESSAGES' as an importable package[^1],
        but it is absent from setuptools' `packages` configuration.
        This leads to an ambiguous overall configuration. If you want to distribute this
        package, please make sure that 'markdownx.locale.du.LC_MESSAGES' is explicitly added
        to the `packages` configuration field.
        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).
        You can read more about "package discovery" on setuptools documentation page:
        - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
        If you don't want 'markdownx.locale.du.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'markdownx.locale.du.LC_MESSAGES' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.
        You can read more about "package data files" on setuptools documentation page:
        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html
        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************
!!
  check.warn(importable)
/usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'markdownx.locale.en.LC_MESSAGES' is absent from the `packages` configuration.
!!
        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'markdownx.locale.en.LC_MESSAGES' as an importable package[^1],
        but it is absent from setuptools' `packages` configuration.
        This leads to an ambiguous overall configuration. If you want to distribute this
        package, please make sure that 'markdownx.locale.en.LC_MESSAGES' is explicitly added
        to the `packages` configuration field.
        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).
        You can read more about "package discovery" on setuptools documentation page:
        - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
        If you don't want 'markdownx.locale.en.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'markdownx.locale.en.LC_MESSAGES' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.
        You can read more about "package data files" on setuptools documentation page:
        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html
        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************
!!
  check.warn(importable)
/usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'markdownx.locale.fa.LC_MESSAGES' is absent from the `packages` configuration.
!!
        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'markdownx.locale.fa.LC_MESSAGES' as an importable package[^1],
        but it is absent from setuptools' `packages` configuration.
        This leads to an ambiguous overall configuration. If you want to distribute this
        package, please make sure that 'markdownx.locale.fa.LC_MESSAGES' is explicitly added
        to the `packages` configuration field.
        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).
        You can read more about "package discovery" on setuptools documentation page:
        - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
        If you don't want 'markdownx.locale.fa.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'markdownx.locale.fa.LC_MESSAGES' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.
        You can read more about "package data files" on setuptools documentation page:
        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html
        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************
!!
  check.warn(importable)
/usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'markdownx.locale.fr.LC_MESSAGES' is absent from the `packages` configuration.
!!
        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'markdownx.locale.fr.LC_MESSAGES' as an importable package[^1],
        but it is absent from setuptools' `packages` configuration.
        This leads to an ambiguous overall configuration. If you want to distribute this
        package, please make sure that 'markdownx.locale.fr.LC_MESSAGES' is explicitly added
        to the `packages` configuration field.
        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).
        You can read more about "package discovery" on setuptools documentation page:
        - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
        If you don't want 'markdownx.locale.fr.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'markdownx.locale.fr.LC_MESSAGES' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.
        You can read more about "package data files" on setuptools documentation page:
        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html
        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************
!!
  check.warn(importable)
/usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'markdownx.locale.pl.LC_MESSAGES' is absent from the `packages` configuration.
!!
        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'markdownx.locale.pl.LC_MESSAGES' as an importable package[^1],
        but it is absent from setuptools' `packages` configuration.
        This leads to an ambiguous overall configuration. If you want to distribute this
        package, please make sure that 'markdownx.locale.pl.LC_MESSAGES' is explicitly added
        to the `packages` configuration field.
        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).
        You can read more about "package discovery" on setuptools documentation page:
        - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
        If you don't want 'markdownx.locale.pl.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'markdownx.locale.pl.LC_MESSAGES' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.
        You can read more about "package data files" on setuptools documentation page:
        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html
        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************
!!
  check.warn(importable)
/usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'markdownx.static.markdownx.admin.css' is absent from the `packages` configuration.
!!
        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'markdownx.static.markdownx.admin.css' as an importable package[^1],
        but it is absent from setuptools' `packages` configuration.
        This leads to an ambiguous overall configuration. If you want to distribute this
        package, please make sure that 'markdownx.static.markdownx.admin.css' is explicitly added
        to the `packages` configuration field.
        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).
        You can read more about "package discovery" on setuptools documentation page:
        - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
        If you don't want 'markdownx.static.markdownx.admin.css' to be distributed and are
        already explicitly excluding 'markdownx.static.markdownx.admin.css' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.
        You can read more about "package data files" on setuptools documentation page:
        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html
        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************
!!
  check.warn(importable)
/usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'markdownx.static.markdownx.js' is absent from the `packages` configuration.
!!
        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'markdownx.static.markdownx.js' as an importable package[^1],
        but it is absent from setuptools' `packages` configuration.
        This leads to an ambiguous overall configuration. If you want to distribute this
        package, please make sure that 'markdownx.static.markdownx.js' is explicitly added
        to the `packages` configuration field.
        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).
        You can read more about "package discovery" on setuptools documentation page:
        - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
        If you don't want 'markdownx.static.markdownx.js' to be distributed and are
        already explicitly excluding 'markdownx.static.markdownx.js' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.
        You can read more about "package data files" on setuptools documentation page:
        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html
        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************
!!
  check.warn(importable)
/usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'markdownx.templates.markdownx' is absent from the `packages` configuration.
!!
        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'markdownx.templates.markdownx' as an importable package[^1],
        but it is absent from setuptools' `packages` configuration.
        This leads to an ambiguous overall configuration. If you want to distribute this
        package, please make sure that 'markdownx.templates.markdownx' is explicitly added
        to the `packages` configuration field.
        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).
        You can read more about "package discovery" on setuptools documentation page:
        - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
        If you don't want 'markdownx.templates.markdownx' to be distributed and are
        already explicitly excluding 'markdownx.templates.markdownx' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.
        You can read more about "package data files" on setuptools documentation page:
        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html
        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************
!!
  check.warn(importable)
/usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'markdownx.tests.static' is absent from the `packages` configuration.
!!
        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'markdownx.tests.static' as an importable package[^1],
        but it is absent from setuptools' `packages` configuration.
        This leads to an ambiguous overall configuration. If you want to distribute this
        package, please make sure that 'markdownx.tests.static' is explicitly added
        to the `packages` configuration field.
        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).
        You can read more about "package discovery" on setuptools documentation page:
        - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
        If you don't want 'markdownx.tests.static' to be distributed and are
        already explicitly excluding 'markdownx.tests.static' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.
        You can read more about "package data files" on setuptools documentation page:
        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html
        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************
!!
  check.warn(importable)
/usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'markdownx.tests.templates' is absent from the `packages` configuration.
!!
        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'markdownx.tests.templates' as an importable package[^1],
        but it is absent from setuptools' `packages` configuration.
        This leads to an ambiguous overall configuration. If you want to distribute this
        package, please make sure that 'markdownx.tests.templates' is explicitly added
        to the `packages` configuration field.
        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).
        You can read more about "package discovery" on setuptools documentation page:
        - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
        If you don't want 'markdownx.tests.templates' to be distributed and are
        already explicitly excluding 'markdownx.tests.templates' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.
        You can read more about "package data files" on setuptools documentation page:
        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html
        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************
!!
  check.warn(importable)
copying markdownx/locale/de/LC_MESSAGES/django.po -> build/lib/markdownx/locale/de/LC_MESSAGES
creating build/lib/markdownx/locale/du/LC_MESSAGES
copying markdownx/locale/du/LC_MESSAGES/django.po -> build/lib/markdownx/locale/du/LC_MESSAGES
creating build/lib/markdownx/locale/en/LC_MESSAGES
copying markdownx/locale/en/LC_MESSAGES/django.mo -> build/lib/markdownx/locale/en/LC_MESSAGES
copying markdownx/locale/en/LC_MESSAGES/django.po -> build/lib/markdownx/locale/en/LC_MESSAGES
creating build/lib/markdownx/locale/fa/LC_MESSAGES
copying markdownx/locale/fa/LC_MESSAGES/django.po -> build/lib/markdownx/locale/fa/LC_MESSAGES
creating build/lib/markdownx/locale/fr/LC_MESSAGES
copying markdownx/locale/fr/LC_MESSAGES/django.po -> build/lib/markdownx/locale/fr/LC_MESSAGES
creating build/lib/markdownx/locale/pl/LC_MESSAGES
copying markdownx/locale/pl/LC_MESSAGES/django.mo -> build/lib/markdownx/locale/pl/LC_MESSAGES
copying markdownx/locale/pl/LC_MESSAGES/django.po -> build/lib/markdownx/locale/pl/LC_MESSAGES
creating build/lib/markdownx/static/markdownx/admin/css
copying markdownx/static/markdownx/admin/css/markdownx.css -> build/lib/markdownx/static/markdownx/admin/css
copying markdownx/static/markdownx/admin/css/markdownx.min.css -> build/lib/markdownx/static/markdownx/admin/css
creating build/lib/markdownx/static/markdownx/js
copying markdownx/static/markdownx/js/markdownx.js -> build/lib/markdownx/static/markdownx/js
copying markdownx/static/markdownx/js/markdownx.min.js -> build/lib/markdownx/static/markdownx/js
creating build/lib/markdownx/templates/markdownx
copying markdownx/templates/markdownx/widget.html -> build/lib/markdownx/templates/markdownx
creating build/lib/markdownx/tests/static
copying markdownx/tests/static/django-markdownx-preview.png -> build/lib/markdownx/tests/static
creating build/lib/markdownx/tests/templates
copying markdownx/tests/templates/test_view.html -> build/lib/markdownx/tests/templates
+ RPM_EC=0
++ jobs -p
+ exit 0
Executing(%install): /bin/sh -e /var/tmp/rpm-tmp.pmN3VW
+ umask 022
+ cd /builddir/build/BUILD/python-django-markdownx-3.0.1-build
+ '[' /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT '!=' / ']'
+ rm -rf /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT
++ dirname /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT
+ mkdir -p /builddir/build/BUILD/python-django-markdownx-3.0.1-build
+ mkdir /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT
+ 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 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -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 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -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 -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 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib/gfortran/modules '
+ export FFLAGS
+ FCFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -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 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib/gfortran/modules '
+ export FCFLAGS
+ VALAFLAGS=-g
+ export VALAFLAGS
+ RUSTFLAGS='-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Cforce-frame-pointers=yes --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/lib:
+ export LT_SYS_LIBRARY_PATH
+ CC=gcc
+ export CC
+ CXX=g++
+ export CXX
+ cd django-markdownx-3.0.1
+ 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 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -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  '
+ /usr/bin/python3 setup.py install -O1 --skip-build --root /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT --prefix /usr
/usr/lib/python3.13/site-packages/setuptools/_distutils/dist.py:289: UserWarning: Unknown distribution option: 'tests_require'
  warnings.warn(msg)
/usr/lib/python3.13/site-packages/setuptools/_distutils/dist.py:289: UserWarning: Unknown distribution option: 'test_suite'
  warnings.warn(msg)
running install
/usr/lib/python3.13/site-packages/setuptools/_distutils/cmd.py:90: SetuptoolsDeprecationWarning: setup.py install is deprecated.
!!
        ********************************************************************************
        Please avoid running ``setup.py`` directly.
        Instead, use pypa/build, pypa/installer or other
        standards-based tools.
        Follow the current Python packaging guidelines when building
        Python RPM packages.
        See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html
        and https://docs.fedoraproject.org/en-US/packaging-guidelines/Python/ for details.
        ********************************************************************************
!!
  self.initialize_options()
running install_lib
creating /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages
creating /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx
copying build/lib/markdownx/__init__.py -> /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx
copying build/lib/markdownx/admin.py -> /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx
copying build/lib/markdownx/exceptions.py -> /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx
copying build/lib/markdownx/fields.py -> /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx
copying build/lib/markdownx/forms.py -> /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx
copying build/lib/markdownx/models.py -> /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx
copying build/lib/markdownx/settings.py -> /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx
copying build/lib/markdownx/urls.py -> /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx
copying build/lib/markdownx/utils.py -> /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx
copying build/lib/markdownx/views.py -> /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx
copying build/lib/markdownx/widgets.py -> /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx
creating /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx/tests
copying build/lib/markdownx/tests/__init__.py -> /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx/tests
copying build/lib/markdownx/tests/models.py -> /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx/tests
copying build/lib/markdownx/tests/tests.py -> /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx/tests
copying build/lib/markdownx/tests/urls.py -> /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx/tests
copying build/lib/markdownx/tests/views.py -> /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx/tests
creating /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx/tests/static
copying build/lib/markdownx/tests/static/django-markdownx-preview.png -> /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx/tests/static
creating /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx/tests/templates
copying build/lib/markdownx/tests/templates/test_view.html -> /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx/tests/templates
creating /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx/locale
creating /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx/locale/de
creating /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx/locale/de/LC_MESSAGES
copying build/lib/markdownx/locale/de/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx/locale/de/LC_MESSAGES
creating /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx/locale/du
creating /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx/locale/du/LC_MESSAGES
copying build/lib/markdownx/locale/du/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx/locale/du/LC_MESSAGES
creating /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx/locale/en
creating /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx/locale/en/LC_MESSAGES
copying build/lib/markdownx/locale/en/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx/locale/en/LC_MESSAGES
copying build/lib/markdownx/locale/en/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx/locale/en/LC_MESSAGES
creating /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx/locale/fa
creating /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx/locale/fa/LC_MESSAGES
copying build/lib/markdownx/locale/fa/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx/locale/fa/LC_MESSAGES
creating /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx/locale/fr
creating /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx/locale/fr/LC_MESSAGES
copying build/lib/markdownx/locale/fr/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx/locale/fr/LC_MESSAGES
creating /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx/locale/pl
creating /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx/locale/pl/LC_MESSAGES
copying build/lib/markdownx/locale/pl/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx/locale/pl/LC_MESSAGES
copying build/lib/markdownx/locale/pl/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx/locale/pl/LC_MESSAGES
creating /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx/static
creating /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx/static/markdownx
creating /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx/static/markdownx/admin
creating /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx/static/markdownx/admin/css
copying build/lib/markdownx/static/markdownx/admin/css/markdownx.css -> /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx/static/markdownx/admin/css
copying build/lib/markdownx/static/markdownx/admin/css/markdownx.min.css -> /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx/static/markdownx/admin/css
creating /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx/static/markdownx/js
copying build/lib/markdownx/static/markdownx/js/markdownx.js -> /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx/static/markdownx/js
copying build/lib/markdownx/static/markdownx/js/markdownx.min.js -> /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx/static/markdownx/js
creating /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx/templates
creating /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx/templates/markdownx
copying build/lib/markdownx/templates/markdownx/widget.html -> /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx/templates/markdownx
byte-compiling /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx/__init__.py to __init__.cpython-313.pyc
byte-compiling /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx/admin.py to admin.cpython-313.pyc
byte-compiling /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx/exceptions.py to exceptions.cpython-313.pyc
byte-compiling /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx/fields.py to fields.cpython-313.pyc
byte-compiling /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx/forms.py to forms.cpython-313.pyc
byte-compiling /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx/models.py to models.cpython-313.pyc
byte-compiling /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx/settings.py to settings.cpython-313.pyc
byte-compiling /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx/urls.py to urls.cpython-313.pyc
byte-compiling /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx/utils.py to utils.cpython-313.pyc
byte-compiling /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx/views.py to views.cpython-313.pyc
byte-compiling /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx/widgets.py to widgets.cpython-313.pyc
byte-compiling /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx/tests/__init__.py to __init__.cpython-313.pyc
byte-compiling /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx/tests/models.py to models.cpython-313.pyc
byte-compiling /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx/tests/tests.py to tests.cpython-313.pyc
byte-compiling /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx/tests/urls.py to urls.cpython-313.pyc
byte-compiling /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx/tests/views.py to views.cpython-313.pyc
writing byte-compilation script '/tmp/tmpqfjlm276.py'
/usr/bin/python3 /tmp/tmpqfjlm276.py
removing /tmp/tmpqfjlm276.py
running install_egg_info
running egg_info
writing django_markdownx.egg-info/PKG-INFO
writing dependency_links to django_markdownx.egg-info/dependency_links.txt
writing requirements to django_markdownx.egg-info/requires.txt
writing top-level names to django_markdownx.egg-info/top_level.txt
reading manifest file 'django_markdownx.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
adding license file 'LICENSE'
writing manifest file 'django_markdownx.egg-info/SOURCES.txt'
Copying django_markdownx.egg-info to /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/django_markdownx-3.0.1-py3.13.egg-info
running install_scripts
+ rm -rfv /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/bin/__pycache__
+ /usr/lib/rpm/find-lang.sh /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT django
+ /usr/lib/rpm/check-buildroot
+ /usr/lib/rpm/redhat/brp-ldconfig
+ /usr/lib/rpm/brp-compress
+ /usr/lib/rpm/brp-strip /usr/bin/strip
+ /usr/lib/rpm/brp-strip-comment-note /usr/bin/strip /usr/bin/objdump
+ /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
+ /usr/lib/rpm/redhat/brp-python-rpm-in-distinfo
+ env /usr/lib/rpm/redhat/brp-python-bytecompile '' 1 0 -j48
Bytecompiling .py files below /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13 using python3.13
+ /usr/lib/rpm/redhat/brp-python-hardlink
+ /usr/bin/add-determinism --brp -j48 /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT
/builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx/tests/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx/tests/__pycache__/urls.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx/tests/__pycache__/models.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx/tests/__pycache__/views.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx/tests/__pycache__/tests.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx/__pycache__/admin.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx/__pycache__/urls.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx/__pycache__/settings.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx/__pycache__/fields.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx/__pycache__/models.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx/__pycache__/exceptions.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx/__pycache__/utils.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx/__pycache__/views.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx/__pycache__/widgets.cpython-313.pyc: rewriting with normalized contents
/builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/lib/python3.13/site-packages/markdownx/__pycache__/forms.cpython-313.pyc: rewriting with normalized contents
Scanned 32 directories and 68 files,
               processed 18 inodes,
               16 modified (0 replaced + 16 rewritten),
               0 unsupported format, 0 errors
Processing files: python3-django-markdownx-3.0.1-19.fc43.noarch
Executing(%doc): /bin/sh -e /var/tmp/rpm-tmp.zMhCHe
+ umask 022
+ cd /builddir/build/BUILD/python-django-markdownx-3.0.1-build
+ cd django-markdownx-3.0.1
+ DOCDIR=/builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/share/doc/python3-django-markdownx
+ export LC_ALL=C.UTF-8
+ LC_ALL=C.UTF-8
+ export DOCDIR
+ /usr/bin/mkdir -p /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/share/doc/python3-django-markdownx
+ cp -pr /builddir/build/BUILD/python-django-markdownx-3.0.1-build/django-markdownx-3.0.1/README.rst /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/share/doc/python3-django-markdownx
+ RPM_EC=0
++ jobs -p
+ exit 0
Executing(%license): /bin/sh -e /var/tmp/rpm-tmp.nfAFZF
+ umask 022
+ cd /builddir/build/BUILD/python-django-markdownx-3.0.1-build
+ cd django-markdownx-3.0.1
+ LICENSEDIR=/builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/share/licenses/python3-django-markdownx
+ export LC_ALL=C.UTF-8
+ LC_ALL=C.UTF-8
+ export LICENSEDIR
+ /usr/bin/mkdir -p /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/share/licenses/python3-django-markdownx
+ cp -pr /builddir/build/BUILD/python-django-markdownx-3.0.1-build/django-markdownx-3.0.1/LICENSE /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT/usr/share/licenses/python3-django-markdownx
+ RPM_EC=0
++ jobs -p
+ exit 0
Provides: python-django-markdownx = 3.0.1-19.fc43 python3-django-markdownx = 3.0.1-19.fc43 python3.13-django-markdownx = 3.0.1-19.fc43 python3.13dist(django-markdownx) = 3.0.1 python3dist(django-markdownx) = 3.0.1
Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PartialHardlinkSets) <= 4.0.4-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1
Requires: python(abi) = 3.13 python3.13dist(django) python3.13dist(markdown) python3.13dist(pillow)
Obsoletes: python-django-markdownx < 3.0.1-19.fc43
Checking for unpackaged file(s): /usr/lib/rpm/check-files /builddir/build/BUILD/python-django-markdownx-3.0.1-build/BUILDROOT
Wrote: /builddir/build/RPMS/python3-django-markdownx-3.0.1-19.fc43.noarch.rpm
Child return code was: 0