<86>May 19 01:08:37 userdel[889240]: delete user 'rooter'
<86>May 19 01:08:37 userdel[889240]: removed group 'rooter' owned by 'rooter'
<86>May 19 01:08:37 userdel[889240]: removed shadow group 'rooter' owned by 'rooter'
<86>May 19 01:08:37 groupadd[889267]: group added to /etc/group: name=rooter, GID=1229
<86>May 19 01:08:37 groupadd[889267]: group added to /etc/gshadow: name=rooter
<86>May 19 01:08:37 groupadd[889267]: new group: name=rooter, GID=1229
<86>May 19 01:08:37 useradd[889285]: new user: name=rooter, UID=1229, GID=1229, home=/root, shell=/bin/bash, from=none
<86>May 19 01:08:37 userdel[889319]: delete user 'builder'
<86>May 19 01:08:37 userdel[889319]: removed group 'builder' owned by 'builder'
<86>May 19 01:08:37 userdel[889319]: removed shadow group 'builder' owned by 'builder'
<86>May 19 01:08:37 groupadd[889352]: group added to /etc/group: name=builder, GID=1230
<86>May 19 01:08:37 groupadd[889352]: group added to /etc/gshadow: name=builder
<86>May 19 01:08:37 groupadd[889352]: new group: name=builder, GID=1230
<86>May 19 01:08:37 useradd[889366]: new user: name=builder, UID=1230, GID=1230, home=/usr/src, shell=/bin/bash, from=none
<13>May 19 01:08:39 rpmi: libmpdec3-2.5.1-alt3 sisyphus+314490.500.5.1 1675432004 installed
<13>May 19 01:08:39 rpmi: libgdbm-1.8.3-alt10 sisyphus+278100.1600.1.1 1626058413 installed
<13>May 19 01:08:39 rpmi: libexpat-2.5.0-alt1 sisyphus+309227.100.1.1 1667075764 installed
<13>May 19 01:08:39 rpmi: libp11-kit-0.24.1-alt1 sisyphus+293720.100.1.1 1642535264 installed
<13>May 19 01:08:39 rpmi: libtasn1-4.19.0-alt1 sisyphus+305700.100.1.1 1661359624 installed
<13>May 19 01:08:39 rpmi: rpm-macros-alternatives-0.5.2-alt2 sisyphus+315270.200.2.1 1676457367 installed
<13>May 19 01:08:39 rpmi: alternatives-0.5.2-alt2 sisyphus+315270.200.2.1 1676457367 installed
<13>May 19 01:08:39 rpmi: ca-certificates-2022.12.14-alt1 sisyphus+311754.200.1.1 1671046143 installed
<13>May 19 01:08:39 rpmi: ca-trust-0.1.4-alt1 sisyphus+308690.100.1.1 1666182992 installed
<13>May 19 01:08:39 rpmi: p11-kit-trust-0.24.1-alt1 sisyphus+293720.100.1.1 1642535264 installed
<13>May 19 01:08:39 rpmi: libcrypto1.1-1.1.1t-alt2 sisyphus+320549.100.1.1 1684166670 installed
<13>May 19 01:08:39 rpmi: libssl1.1-1.1.1t-alt2 sisyphus+320549.100.1.1 1684166670 installed
<13>May 19 01:08:39 rpmi: python3-3.10.8-alt1.1 sisyphus+311926.100.2.1 1671363630 installed
<13>May 19 01:08:40 rpmi: python3-base-3.10.8-alt1.1 sisyphus+311926.100.2.1 1671363630 installed
<13>May 19 01:08:40 rpmi: tests-for-installed-python3-pkgs-0.1.22-alt1 sisyphus+319076.100.3.1 1682536051 installed
<13>May 19 01:08:40 rpmi: rpm-build-python3-0.1.22-alt1 sisyphus+319076.100.3.1 1682536051 installed
WARNING: %python3_build_debug is deprecated and will be removed in future, please use %pyproject_build instead
WARNING: %python3_install is deprecated and will be removed in future, please use %pyproject_install instead
WARNING: %python3_build_debug is deprecated and will be removed in future, please use %pyproject_build instead
WARNING: %python3_install is deprecated and will be removed in future, please use %pyproject_install instead
Building target platforms: x86_64
Building for target x86_64
Wrote: /usr/src/in/nosrpm/python3-module-mockup-3.1.1-alt1.nosrc.rpm (w1.gzdio)
<13>May 19 01:08:43 rpmi: python3-module-pkg_resources-1:67.7.2-alt1 sisyphus+319053.1300.6.1 1682668483 installed
<13>May 19 01:08:43 rpmi: libpython3-3.10.8-alt1.1 sisyphus+311926.100.2.1 1671363630 installed
<13>May 19 01:08:43 rpmi: libncurses-6.3.20220618-alt1 sisyphus+302449.100.1.1 1655835246 installed
<13>May 19 01:08:43 rpmi: libtinfo-devel-6.3.20220618-alt1 sisyphus+302449.100.1.1 1655835246 installed
<13>May 19 01:08:43 rpmi: libncurses-devel-6.3.20220618-alt1 sisyphus+302449.100.1.1 1655835246 installed
<13>May 19 01:08:44 rpmi: python3-dev-3.10.8-alt1.1 sisyphus+311926.100.2.1 1671363630 installed
<13>May 19 01:08:44 rpmi: python3-module-setuptools-1:67.7.2-alt1 sisyphus+319053.1300.6.1 1682668483 installed
WARNING: %python3_build_debug is deprecated and will be removed in future, please use %pyproject_build instead
WARNING: %python3_install is deprecated and will be removed in future, please use %pyproject_install instead
Installing python3-module-mockup-3.1.1-alt1.src.rpm
Building target platforms: x86_64
Building for target x86_64
Executing(%prep): /bin/sh -e /usr/src/tmp/rpm-tmp.67959
+ umask 022
+ /bin/mkdir -p /usr/src/RPM/BUILD
+ cd /usr/src/RPM/BUILD
+ cd /usr/src/RPM/BUILD
+ rm -rf python3-module-mockup-3.1.1
+ echo 'Source #0 (python3-module-mockup-3.1.1.tar.gz):'
Source #0 (python3-module-mockup-3.1.1.tar.gz):
+ /bin/gzip -dc /usr/src/RPM/SOURCES/python3-module-mockup-3.1.1.tar.gz
+ /bin/tar -xf -
+ cd python3-module-mockup-3.1.1
+ /bin/chmod -c -Rf u+rwX,go-w .
+ exit 0
Executing(%build): /bin/sh -e /usr/src/tmp/rpm-tmp.67959
+ umask 022
+ /bin/mkdir -p /usr/src/RPM/BUILD
+ cd /usr/src/RPM/BUILD
+ cd python3-module-mockup-3.1.1
+ CFLAGS='-pipe -frecord-gcc-switches -Wall -g -O2 -flto=auto'
+ export CFLAGS
+ CXXFLAGS='-pipe -frecord-gcc-switches -Wall -g -O2 -flto=auto'
+ export CXXFLAGS
+ FFLAGS='-pipe -frecord-gcc-switches -Wall -g -O2 -flto=auto'
+ export FFLAGS
+ /usr/bin/python3 setup.py build --debug
running build
running build_py
creating build
creating build/lib
creating build/lib/mockup_
copying mockup_/__init__.py -> build/lib/mockup_
creating build/lib/mockup
copying mockup/__init__.py -> build/lib/mockup
running egg_info
creating mockup.egg-info
writing mockup.egg-info/PKG-INFO
writing dependency_links to mockup.egg-info/dependency_links.txt
writing entry points to mockup.egg-info/entry_points.txt
writing top-level names to mockup.egg-info/top_level.txt
writing manifest file 'mockup.egg-info/SOURCES.txt'
reading manifest file 'mockup.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
no previously-included directories found matching '.nix'
no previously-included directories found matching 'dist'
no previously-included directories found matching 'mockup/node_modules'
no previously-included directories found matching 'mockup/build'
no previously-included directories found matching 'mockup/coverage'
no previously-included directories found matching 'mockup/docs'
no previously-included directories found matching 'mockup/node_modules'
warning: no previously-included files found matching '.bowerrc'
warning: no previously-included files found matching '.travis.yml'
warning: no previously-included files found matching 'Makefile'
warning: no previously-included files found matching '*.sh'
warning: no previously-included files found matching 'Vagrantfile'
warning: no previously-included files matching '*.pycinclude' found anywhere in distribution
warning: no previously-included files matching '*' found under directory 'news'
warning: no previously-included files found matching 'news'
warning: no previously-included files found matching 'yarn.lock'
adding license file 'LICENSE.rst'
writing manifest file 'mockup.egg-info/SOURCES.txt'
/usr/lib64/python3/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'mockup.js' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'mockup.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 'mockup.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 'mockup.js' to be distributed and are
        already explicitly excluding 'mockup.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/lib64/python3/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'mockup.js.bundles' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'mockup.js.bundles' 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 'mockup.js.bundles' 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 'mockup.js.bundles' to be distributed and are
        already explicitly excluding 'mockup.js.bundles' 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/lib64/python3/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'mockup.js.docs' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'mockup.js.docs' 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 'mockup.js.docs' 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 'mockup.js.docs' to be distributed and are
        already explicitly excluding 'mockup.js.docs' 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/lib64/python3/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'mockup.js.ui.templates' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'mockup.js.ui.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 'mockup.js.ui.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 'mockup.js.ui.templates' to be distributed and are
        already explicitly excluding 'mockup.js.ui.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)
/usr/lib64/python3/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'mockup.js.ui.views' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'mockup.js.ui.views' 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 'mockup.js.ui.views' 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 'mockup.js.ui.views' to be distributed and are
        already explicitly excluding 'mockup.js.ui.views' 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/lib64/python3/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'mockup.less' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'mockup.less' 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 'mockup.less' 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 'mockup.less' to be distributed and are
        already explicitly excluding 'mockup.less' 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/lib64/python3/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'mockup.lib' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'mockup.lib' 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 'mockup.lib' 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 'mockup.lib' to be distributed and are
        already explicitly excluding 'mockup.lib' 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/lib64/python3/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'mockup.patterns.autotoc' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'mockup.patterns.autotoc' 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 'mockup.patterns.autotoc' 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 'mockup.patterns.autotoc' to be distributed and are
        already explicitly excluding 'mockup.patterns.autotoc' 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/lib64/python3/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'mockup.patterns.backdrop' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'mockup.patterns.backdrop' 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 'mockup.patterns.backdrop' 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 'mockup.patterns.backdrop' to be distributed and are
        already explicitly excluding 'mockup.patterns.backdrop' 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/lib64/python3/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'mockup.patterns.base' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'mockup.patterns.base' 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 'mockup.patterns.base' 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 'mockup.patterns.base' to be distributed and are
        already explicitly excluding 'mockup.patterns.base' 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/lib64/python3/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'mockup.patterns.contentloader' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'mockup.patterns.contentloader' 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 'mockup.patterns.contentloader' 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 'mockup.patterns.contentloader' to be distributed and are
        already explicitly excluding 'mockup.patterns.contentloader' 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/lib64/python3/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'mockup.patterns.cookietrigger' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'mockup.patterns.cookietrigger' 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 'mockup.patterns.cookietrigger' 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 'mockup.patterns.cookietrigger' to be distributed and are
        already explicitly excluding 'mockup.patterns.cookietrigger' 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/lib64/python3/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'mockup.patterns.datatables' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'mockup.patterns.datatables' 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 'mockup.patterns.datatables' 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 'mockup.patterns.datatables' to be distributed and are
        already explicitly excluding 'mockup.patterns.datatables' 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/lib64/python3/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'mockup.patterns.eventedit' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'mockup.patterns.eventedit' 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 'mockup.patterns.eventedit' 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 'mockup.patterns.eventedit' to be distributed and are
        already explicitly excluding 'mockup.patterns.eventedit' 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/lib64/python3/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'mockup.patterns.filemanager' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'mockup.patterns.filemanager' 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 'mockup.patterns.filemanager' 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 'mockup.patterns.filemanager' to be distributed and are
        already explicitly excluding 'mockup.patterns.filemanager' 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/lib64/python3/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'mockup.patterns.filemanager.js' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'mockup.patterns.filemanager.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 'mockup.patterns.filemanager.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 'mockup.patterns.filemanager.js' to be distributed and are
        already explicitly excluding 'mockup.patterns.filemanager.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/lib64/python3/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'mockup.patterns.filemanager.templates' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'mockup.patterns.filemanager.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 'mockup.patterns.filemanager.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 'mockup.patterns.filemanager.templates' to be distributed and are
        already explicitly excluding 'mockup.patterns.filemanager.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)
/usr/lib64/python3/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'mockup.patterns.formautofocus' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'mockup.patterns.formautofocus' 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 'mockup.patterns.formautofocus' 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 'mockup.patterns.formautofocus' to be distributed and are
        already explicitly excluding 'mockup.patterns.formautofocus' 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/lib64/python3/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'mockup.patterns.formunloadalert' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'mockup.patterns.formunloadalert' 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 'mockup.patterns.formunloadalert' 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 'mockup.patterns.formunloadalert' to be distributed and are
        already explicitly excluding 'mockup.patterns.formunloadalert' 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/lib64/python3/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'mockup.patterns.inlinevalidation' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'mockup.patterns.inlinevalidation' 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 'mockup.patterns.inlinevalidation' 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 'mockup.patterns.inlinevalidation' to be distributed and are
        already explicitly excluding 'mockup.patterns.inlinevalidation' 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/lib64/python3/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'mockup.patterns.livesearch' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'mockup.patterns.livesearch' 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 'mockup.patterns.livesearch' 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 'mockup.patterns.livesearch' to be distributed and are
        already explicitly excluding 'mockup.patterns.livesearch' 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/lib64/python3/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'mockup.patterns.markspeciallinks' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'mockup.patterns.markspeciallinks' 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 'mockup.patterns.markspeciallinks' 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 'mockup.patterns.markspeciallinks' to be distributed and are
        already explicitly excluding 'mockup.patterns.markspeciallinks' 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/lib64/python3/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'mockup.patterns.modal' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'mockup.patterns.modal' 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 'mockup.patterns.modal' 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 'mockup.patterns.modal' to be distributed and are
        already explicitly excluding 'mockup.patterns.modal' 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/lib64/python3/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'mockup.patterns.moment' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'mockup.patterns.moment' 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 'mockup.patterns.moment' 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 'mockup.patterns.moment' to be distributed and are
        already explicitly excluding 'mockup.patterns.moment' 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/lib64/python3/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'mockup.patterns.navigationmarker' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'mockup.patterns.navigationmarker' 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 'mockup.patterns.navigationmarker' 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 'mockup.patterns.navigationmarker' to be distributed and are
        already explicitly excluding 'mockup.patterns.navigationmarker' 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/lib64/python3/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'mockup.patterns.passwordstrength' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'mockup.patterns.passwordstrength' 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 'mockup.patterns.passwordstrength' 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 'mockup.patterns.passwordstrength' to be distributed and are
        already explicitly excluding 'mockup.patterns.passwordstrength' 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/lib64/python3/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'mockup.patterns.pickadate' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'mockup.patterns.pickadate' 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 'mockup.patterns.pickadate' 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 'mockup.patterns.pickadate' to be distributed and are
        already explicitly excluding 'mockup.patterns.pickadate' 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/lib64/python3/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'mockup.patterns.preventdoublesubmit' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'mockup.patterns.preventdoublesubmit' 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 'mockup.patterns.preventdoublesubmit' 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 'mockup.patterns.preventdoublesubmit' to be distributed and are
        already explicitly excluding 'mockup.patterns.preventdoublesubmit' 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/lib64/python3/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'mockup.patterns.querystring' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'mockup.patterns.querystring' 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 'mockup.patterns.querystring' 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 'mockup.patterns.querystring' to be distributed and are
        already explicitly excluding 'mockup.patterns.querystring' 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/lib64/python3/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'mockup.patterns.recurrence' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'mockup.patterns.recurrence' 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 'mockup.patterns.recurrence' 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 'mockup.patterns.recurrence' to be distributed and are
        already explicitly excluding 'mockup.patterns.recurrence' 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/lib64/python3/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'mockup.patterns.relateditems' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'mockup.patterns.relateditems' 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 'mockup.patterns.relateditems' 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 'mockup.patterns.relateditems' to be distributed and are
        already explicitly excluding 'mockup.patterns.relateditems' 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/lib64/python3/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'mockup.patterns.relateditems.templates' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'mockup.patterns.relateditems.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 'mockup.patterns.relateditems.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 'mockup.patterns.relateditems.templates' to be distributed and are
        already explicitly excluding 'mockup.patterns.relateditems.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)
/usr/lib64/python3/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'mockup.patterns.resourceregistry' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'mockup.patterns.resourceregistry' 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 'mockup.patterns.resourceregistry' 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 'mockup.patterns.resourceregistry' to be distributed and are
        already explicitly excluding 'mockup.patterns.resourceregistry' 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/lib64/python3/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'mockup.patterns.resourceregistry.js' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'mockup.patterns.resourceregistry.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 'mockup.patterns.resourceregistry.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 'mockup.patterns.resourceregistry.js' to be distributed and are
        already explicitly excluding 'mockup.patterns.resourceregistry.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/lib64/python3/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'mockup.patterns.select2' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'mockup.patterns.select2' 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 'mockup.patterns.select2' 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 'mockup.patterns.select2' to be distributed and are
        already explicitly excluding 'mockup.patterns.select2' 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/lib64/python3/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'mockup.patterns.sortable' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'mockup.patterns.sortable' 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 'mockup.patterns.sortable' 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 'mockup.patterns.sortable' to be distributed and are
        already explicitly excluding 'mockup.patterns.sortable' 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/lib64/python3/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'mockup.patterns.structure' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'mockup.patterns.structure' 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 'mockup.patterns.structure' 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 'mockup.patterns.structure' to be distributed and are
        already explicitly excluding 'mockup.patterns.structure' 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/lib64/python3/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'mockup.patterns.structure.js' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'mockup.patterns.structure.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 'mockup.patterns.structure.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 'mockup.patterns.structure.js' to be distributed and are
        already explicitly excluding 'mockup.patterns.structure.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/lib64/python3/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'mockup.patterns.structure.js.collections' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'mockup.patterns.structure.js.collections' 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 'mockup.patterns.structure.js.collections' 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 'mockup.patterns.structure.js.collections' to be distributed and are
        already explicitly excluding 'mockup.patterns.structure.js.collections' 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/lib64/python3/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'mockup.patterns.structure.js.models' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'mockup.patterns.structure.js.models' 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 'mockup.patterns.structure.js.models' 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 'mockup.patterns.structure.js.models' to be distributed and are
        already explicitly excluding 'mockup.patterns.structure.js.models' 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/lib64/python3/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'mockup.patterns.structure.js.views' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'mockup.patterns.structure.js.views' 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 'mockup.patterns.structure.js.views' 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 'mockup.patterns.structure.js.views' to be distributed and are
        already explicitly excluding 'mockup.patterns.structure.js.views' 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/lib64/python3/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'mockup.patterns.structure.less' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'mockup.patterns.structure.less' 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 'mockup.patterns.structure.less' 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 'mockup.patterns.structure.less' to be distributed and are
        already explicitly excluding 'mockup.patterns.structure.less' 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/lib64/python3/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'mockup.patterns.structure.templates' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'mockup.patterns.structure.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 'mockup.patterns.structure.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 'mockup.patterns.structure.templates' to be distributed and are
        already explicitly excluding 'mockup.patterns.structure.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)
/usr/lib64/python3/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'mockup.patterns.textareamimetypeselector' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'mockup.patterns.textareamimetypeselector' 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 'mockup.patterns.textareamimetypeselector' 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 'mockup.patterns.textareamimetypeselector' to be distributed and are
        already explicitly excluding 'mockup.patterns.textareamimetypeselector' 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/lib64/python3/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'mockup.patterns.texteditor' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'mockup.patterns.texteditor' 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 'mockup.patterns.texteditor' 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 'mockup.patterns.texteditor' to be distributed and are
        already explicitly excluding 'mockup.patterns.texteditor' 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/lib64/python3/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'mockup.patterns.thememapper' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'mockup.patterns.thememapper' 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 'mockup.patterns.thememapper' 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 'mockup.patterns.thememapper' to be distributed and are
        already explicitly excluding 'mockup.patterns.thememapper' 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/lib64/python3/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'mockup.patterns.thememapper.js' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'mockup.patterns.thememapper.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 'mockup.patterns.thememapper.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 'mockup.patterns.thememapper.js' to be distributed and are
        already explicitly excluding 'mockup.patterns.thememapper.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/lib64/python3/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'mockup.patterns.thememapper.templates' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'mockup.patterns.thememapper.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 'mockup.patterns.thememapper.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 'mockup.patterns.thememapper.templates' to be distributed and are
        already explicitly excluding 'mockup.patterns.thememapper.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)
/usr/lib64/python3/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'mockup.patterns.tinymce' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'mockup.patterns.tinymce' 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 'mockup.patterns.tinymce' 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 'mockup.patterns.tinymce' to be distributed and are
        already explicitly excluding 'mockup.patterns.tinymce' 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/lib64/python3/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'mockup.patterns.tinymce.js' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'mockup.patterns.tinymce.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 'mockup.patterns.tinymce.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 'mockup.patterns.tinymce.js' to be distributed and are
        already explicitly excluding 'mockup.patterns.tinymce.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/lib64/python3/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'mockup.patterns.tinymce.less' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'mockup.patterns.tinymce.less' 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 'mockup.patterns.tinymce.less' 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 'mockup.patterns.tinymce.less' to be distributed and are
        already explicitly excluding 'mockup.patterns.tinymce.less' 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/lib64/python3/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'mockup.patterns.tinymce.templates' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'mockup.patterns.tinymce.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 'mockup.patterns.tinymce.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 'mockup.patterns.tinymce.templates' to be distributed and are
        already explicitly excluding 'mockup.patterns.tinymce.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)
/usr/lib64/python3/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'mockup.patterns.toggle' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'mockup.patterns.toggle' 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 'mockup.patterns.toggle' 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 'mockup.patterns.toggle' to be distributed and are
        already explicitly excluding 'mockup.patterns.toggle' 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/lib64/python3/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'mockup.patterns.toolbar' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'mockup.patterns.toolbar' 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 'mockup.patterns.toolbar' 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 'mockup.patterns.toolbar' to be distributed and are
        already explicitly excluding 'mockup.patterns.toolbar' 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/lib64/python3/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'mockup.patterns.tooltip' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'mockup.patterns.tooltip' 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 'mockup.patterns.tooltip' 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 'mockup.patterns.tooltip' to be distributed and are
        already explicitly excluding 'mockup.patterns.tooltip' 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/lib64/python3/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'mockup.patterns.tree' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'mockup.patterns.tree' 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 'mockup.patterns.tree' 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 'mockup.patterns.tree' to be distributed and are
        already explicitly excluding 'mockup.patterns.tree' 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/lib64/python3/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'mockup.patterns.upload' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'mockup.patterns.upload' 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 'mockup.patterns.upload' 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 'mockup.patterns.upload' to be distributed and are
        already explicitly excluding 'mockup.patterns.upload' 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/lib64/python3/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'mockup.patterns.upload.less' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'mockup.patterns.upload.less' 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 'mockup.patterns.upload.less' 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 'mockup.patterns.upload.less' to be distributed and are
        already explicitly excluding 'mockup.patterns.upload.less' 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/lib64/python3/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'mockup.patterns.upload.templates' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'mockup.patterns.upload.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 'mockup.patterns.upload.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 'mockup.patterns.upload.templates' to be distributed and are
        already explicitly excluding 'mockup.patterns.upload.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)
/usr/lib64/python3/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'mockup.tests' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'mockup.tests' 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 'mockup.tests' 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 'mockup.tests' to be distributed and are
        already explicitly excluding 'mockup.tests' 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/lib64/python3/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'mockup.tests.files' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'mockup.tests.files' 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 'mockup.tests.files' 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 'mockup.tests.files' to be distributed and are
        already explicitly excluding 'mockup.tests.files' 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/lib64/python3/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'mockup.tests.images' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'mockup.tests.images' 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 'mockup.tests.images' 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 'mockup.tests.images' to be distributed and are
        already explicitly excluding 'mockup.tests.images' 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/lib64/python3/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'mockup.tests.json' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'mockup.tests.json' 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 'mockup.tests.json' 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 'mockup.tests.json' to be distributed and are
        already explicitly excluding 'mockup.tests.json' 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 mockup/.jscs.json -> build/lib/mockup
copying mockup/.jshintrc -> build/lib/mockup
copying mockup/CONTRIBUTE.md -> build/lib/mockup
copying mockup/GETTING_STARTED.md -> build/lib/mockup
copying mockup/Gruntfile.js -> build/lib/mockup
copying mockup/LEARN.md -> build/lib/mockup
copying mockup/configure.zcml -> build/lib/mockup
copying mockup/index.html -> build/lib/mockup
creating build/lib/mockup/js
copying mockup/js/config.js -> build/lib/mockup/js
copying mockup/js/grunt.js -> build/lib/mockup/js
copying mockup/js/i18n-wrapper.js -> build/lib/mockup/js
copying mockup/js/i18n.js -> build/lib/mockup/js
copying mockup/js/router.js -> build/lib/mockup/js
copying mockup/js/utils.js -> build/lib/mockup/js
creating build/lib/mockup/js/bundles
copying mockup/js/bundles/docs.js -> build/lib/mockup/js/bundles
copying mockup/js/bundles/filemanager.js -> build/lib/mockup/js/bundles
copying mockup/js/bundles/plone.js -> build/lib/mockup/js/bundles
copying mockup/js/bundles/resourceregistry.js -> build/lib/mockup/js/bundles
copying mockup/js/bundles/structure.js -> build/lib/mockup/js/bundles
copying mockup/js/bundles/widgets.js -> build/lib/mockup/js/bundles
creating build/lib/mockup/js/docs
copying mockup/js/docs/app.js -> build/lib/mockup/js/docs
copying mockup/js/docs/navigation.js -> build/lib/mockup/js/docs
copying mockup/js/docs/page.js -> build/lib/mockup/js/docs
copying mockup/js/docs/pattern.js -> build/lib/mockup/js/docs
copying mockup/js/docs/view.js -> build/lib/mockup/js/docs
creating build/lib/mockup/js/ui
creating build/lib/mockup/js/ui/templates
copying mockup/js/ui/templates/dropdown.xml -> build/lib/mockup/js/ui/templates
copying mockup/js/ui/templates/popover.xml -> build/lib/mockup/js/ui/templates
creating build/lib/mockup/js/ui/views
copying mockup/js/ui/views/anchor.js -> build/lib/mockup/js/ui/views
copying mockup/js/ui/views/base.js -> build/lib/mockup/js/ui/views
copying mockup/js/ui/views/button.js -> build/lib/mockup/js/ui/views
copying mockup/js/ui/views/buttongroup.js -> build/lib/mockup/js/ui/views
copying mockup/js/ui/views/container.js -> build/lib/mockup/js/ui/views
copying mockup/js/ui/views/dropdown.js -> build/lib/mockup/js/ui/views
copying mockup/js/ui/views/popover.js -> build/lib/mockup/js/ui/views
copying mockup/js/ui/views/toolbar.js -> build/lib/mockup/js/ui/views
creating build/lib/mockup/less
copying mockup/less/base.less -> build/lib/mockup/less
copying mockup/less/docs.less -> build/lib/mockup/less
copying mockup/less/filemanager.less -> build/lib/mockup/less
copying mockup/less/mixins.less -> build/lib/mockup/less
copying mockup/less/plone.less -> build/lib/mockup/less
copying mockup/less/plonelogo.less -> build/lib/mockup/less
copying mockup/less/plonetoolbar.less -> build/lib/mockup/less
copying mockup/less/popover.less -> build/lib/mockup/less
copying mockup/less/resourceregistry.less -> build/lib/mockup/less
copying mockup/less/structure.less -> build/lib/mockup/less
copying mockup/less/ui.less -> build/lib/mockup/less
copying mockup/less/widgets.less -> build/lib/mockup/less
creating build/lib/mockup/lib
copying mockup/lib/jquery.event.drag.js -> build/lib/mockup/lib
copying mockup/lib/jquery.event.drop.js -> build/lib/mockup/lib
creating build/lib/mockup/patterns
creating build/lib/mockup/patterns/autotoc
copying mockup/patterns/autotoc/pattern.autotoc.less -> build/lib/mockup/patterns/autotoc
copying mockup/patterns/autotoc/pattern.js -> build/lib/mockup/patterns/autotoc
creating build/lib/mockup/patterns/backdrop
copying mockup/patterns/backdrop/pattern.js -> build/lib/mockup/patterns/backdrop
creating build/lib/mockup/patterns/base
copying mockup/patterns/base/pattern.js -> build/lib/mockup/patterns/base
creating build/lib/mockup/patterns/contentloader
copying mockup/patterns/contentloader/pattern.js -> build/lib/mockup/patterns/contentloader
creating build/lib/mockup/patterns/cookietrigger
copying mockup/patterns/cookietrigger/pattern.js -> build/lib/mockup/patterns/cookietrigger
creating build/lib/mockup/patterns/datatables
copying mockup/patterns/datatables/pattern.datatables.less -> build/lib/mockup/patterns/datatables
copying mockup/patterns/datatables/pattern.js -> build/lib/mockup/patterns/datatables
creating build/lib/mockup/patterns/eventedit
copying mockup/patterns/eventedit/pattern.js -> build/lib/mockup/patterns/eventedit
creating build/lib/mockup/patterns/filemanager
copying mockup/patterns/filemanager/pattern.filemanager.less -> build/lib/mockup/patterns/filemanager
copying mockup/patterns/filemanager/pattern.js -> build/lib/mockup/patterns/filemanager
creating build/lib/mockup/patterns/filemanager/js
copying mockup/patterns/filemanager/js/addnew.js -> build/lib/mockup/patterns/filemanager/js
copying mockup/patterns/filemanager/js/basepopover.js -> build/lib/mockup/patterns/filemanager/js
copying mockup/patterns/filemanager/js/customize.js -> build/lib/mockup/patterns/filemanager/js
copying mockup/patterns/filemanager/js/delete.js -> build/lib/mockup/patterns/filemanager/js
copying mockup/patterns/filemanager/js/findfile.js -> build/lib/mockup/patterns/filemanager/js
copying mockup/patterns/filemanager/js/findinfiles.js -> build/lib/mockup/patterns/filemanager/js
copying mockup/patterns/filemanager/js/newfolder.js -> build/lib/mockup/patterns/filemanager/js
copying mockup/patterns/filemanager/js/rename.js -> build/lib/mockup/patterns/filemanager/js
copying mockup/patterns/filemanager/js/upload.js -> build/lib/mockup/patterns/filemanager/js
creating build/lib/mockup/patterns/filemanager/templates
copying mockup/patterns/filemanager/templates/app.xml -> build/lib/mockup/patterns/filemanager/templates
copying mockup/patterns/filemanager/templates/popover.xml -> build/lib/mockup/patterns/filemanager/templates
creating build/lib/mockup/patterns/formautofocus
copying mockup/patterns/formautofocus/pattern.js -> build/lib/mockup/patterns/formautofocus
creating build/lib/mockup/patterns/formunloadalert
copying mockup/patterns/formunloadalert/pattern.js -> build/lib/mockup/patterns/formunloadalert
creating build/lib/mockup/patterns/inlinevalidation
copying mockup/patterns/inlinevalidation/pattern.js -> build/lib/mockup/patterns/inlinevalidation
creating build/lib/mockup/patterns/livesearch
copying mockup/patterns/livesearch/pattern.js -> build/lib/mockup/patterns/livesearch
copying mockup/patterns/livesearch/pattern.livesearch.less -> build/lib/mockup/patterns/livesearch
creating build/lib/mockup/patterns/markspeciallinks
copying mockup/patterns/markspeciallinks/pattern.js -> build/lib/mockup/patterns/markspeciallinks
copying mockup/patterns/markspeciallinks/pattern.markspeciallinks.less -> build/lib/mockup/patterns/markspeciallinks
creating build/lib/mockup/patterns/modal
copying mockup/patterns/modal/pattern.js -> build/lib/mockup/patterns/modal
copying mockup/patterns/modal/pattern.modal.less -> build/lib/mockup/patterns/modal
creating build/lib/mockup/patterns/moment
copying mockup/patterns/moment/pattern.js -> build/lib/mockup/patterns/moment
creating build/lib/mockup/patterns/navigationmarker
copying mockup/patterns/navigationmarker/pattern.js -> build/lib/mockup/patterns/navigationmarker
creating build/lib/mockup/patterns/passwordstrength
copying mockup/patterns/passwordstrength/pattern.js -> build/lib/mockup/patterns/passwordstrength
copying mockup/patterns/passwordstrength/pattern.passwordstrength.less -> build/lib/mockup/patterns/passwordstrength
creating build/lib/mockup/patterns/pickadate
copying mockup/patterns/pickadate/pattern.js -> build/lib/mockup/patterns/pickadate
copying mockup/patterns/pickadate/pattern.pickadate.less -> build/lib/mockup/patterns/pickadate
creating build/lib/mockup/patterns/preventdoublesubmit
copying mockup/patterns/preventdoublesubmit/pattern.js -> build/lib/mockup/patterns/preventdoublesubmit
creating build/lib/mockup/patterns/querystring
copying mockup/patterns/querystring/pattern.js -> build/lib/mockup/patterns/querystring
copying mockup/patterns/querystring/pattern.querystring.less -> build/lib/mockup/patterns/querystring
creating build/lib/mockup/patterns/recurrence
copying mockup/patterns/recurrence/pattern.js -> build/lib/mockup/patterns/recurrence
copying mockup/patterns/recurrence/pattern.recurrence.less -> build/lib/mockup/patterns/recurrence
creating build/lib/mockup/patterns/relateditems
copying mockup/patterns/relateditems/pattern.js -> build/lib/mockup/patterns/relateditems
copying mockup/patterns/relateditems/pattern.relateditems.less -> build/lib/mockup/patterns/relateditems
copying mockup/patterns/relateditems/upload.js -> build/lib/mockup/patterns/relateditems
creating build/lib/mockup/patterns/relateditems/templates
copying mockup/patterns/relateditems/templates/breadcrumb.xml -> build/lib/mockup/patterns/relateditems/templates
copying mockup/patterns/relateditems/templates/favorite.xml -> build/lib/mockup/patterns/relateditems/templates
copying mockup/patterns/relateditems/templates/recentlyused.xml -> build/lib/mockup/patterns/relateditems/templates
copying mockup/patterns/relateditems/templates/result.xml -> build/lib/mockup/patterns/relateditems/templates
copying mockup/patterns/relateditems/templates/selection.xml -> build/lib/mockup/patterns/relateditems/templates
copying mockup/patterns/relateditems/templates/toolbar.xml -> build/lib/mockup/patterns/relateditems/templates
creating build/lib/mockup/patterns/resourceregistry
copying mockup/patterns/resourceregistry/pattern.js -> build/lib/mockup/patterns/resourceregistry
copying mockup/patterns/resourceregistry/pattern.resourceregistry.less -> build/lib/mockup/patterns/resourceregistry
creating build/lib/mockup/patterns/resourceregistry/js
copying mockup/patterns/resourceregistry/js/builder.js -> build/lib/mockup/patterns/resourceregistry/js
copying mockup/patterns/resourceregistry/js/fields.js -> build/lib/mockup/patterns/resourceregistry/js
copying mockup/patterns/resourceregistry/js/iframe.js -> build/lib/mockup/patterns/resourceregistry/js
copying mockup/patterns/resourceregistry/js/less.js -> build/lib/mockup/patterns/resourceregistry/js
copying mockup/patterns/resourceregistry/js/overrides.js -> build/lib/mockup/patterns/resourceregistry/js
copying mockup/patterns/resourceregistry/js/patternoptions.js -> build/lib/mockup/patterns/resourceregistry/js
copying mockup/patterns/resourceregistry/js/registry.js -> build/lib/mockup/patterns/resourceregistry/js
creating build/lib/mockup/patterns/select2
copying mockup/patterns/select2/pattern.js -> build/lib/mockup/patterns/select2
copying mockup/patterns/select2/pattern.select2.less -> build/lib/mockup/patterns/select2
creating build/lib/mockup/patterns/sortable
copying mockup/patterns/sortable/pattern.js -> build/lib/mockup/patterns/sortable
creating build/lib/mockup/patterns/structure
copying mockup/patterns/structure/README.rst -> build/lib/mockup/patterns/structure
copying mockup/patterns/structure/pattern-structureupdater.js -> build/lib/mockup/patterns/structure
copying mockup/patterns/structure/pattern.js -> build/lib/mockup/patterns/structure
creating build/lib/mockup/patterns/structure/js
copying mockup/patterns/structure/js/actionmenu.js -> build/lib/mockup/patterns/structure/js
copying mockup/patterns/structure/js/actions.js -> build/lib/mockup/patterns/structure/js
copying mockup/patterns/structure/js/navigation.js -> build/lib/mockup/patterns/structure/js
creating build/lib/mockup/patterns/structure/js/collections
copying mockup/patterns/structure/js/collections/result.js -> build/lib/mockup/patterns/structure/js/collections
copying mockup/patterns/structure/js/collections/selected.js -> build/lib/mockup/patterns/structure/js/collections
creating build/lib/mockup/patterns/structure/js/models
copying mockup/patterns/structure/js/models/result.js -> build/lib/mockup/patterns/structure/js/models
creating build/lib/mockup/patterns/structure/js/views
copying mockup/patterns/structure/js/views/actionmenu.js -> build/lib/mockup/patterns/structure/js/views
copying mockup/patterns/structure/js/views/addmenu.js -> build/lib/mockup/patterns/structure/js/views
copying mockup/patterns/structure/js/views/app.js -> build/lib/mockup/patterns/structure/js/views
copying mockup/patterns/structure/js/views/columns.js -> build/lib/mockup/patterns/structure/js/views
copying mockup/patterns/structure/js/views/generic-popover.js -> build/lib/mockup/patterns/structure/js/views
copying mockup/patterns/structure/js/views/paging.js -> build/lib/mockup/patterns/structure/js/views
copying mockup/patterns/structure/js/views/rearrange.js -> build/lib/mockup/patterns/structure/js/views
copying mockup/patterns/structure/js/views/selectionbutton.js -> build/lib/mockup/patterns/structure/js/views
copying mockup/patterns/structure/js/views/selectionwell.js -> build/lib/mockup/patterns/structure/js/views
copying mockup/patterns/structure/js/views/table.js -> build/lib/mockup/patterns/structure/js/views
copying mockup/patterns/structure/js/views/tablerow.js -> build/lib/mockup/patterns/structure/js/views
copying mockup/patterns/structure/js/views/textfilter.js -> build/lib/mockup/patterns/structure/js/views
copying mockup/patterns/structure/js/views/upload.js -> build/lib/mockup/patterns/structure/js/views
creating build/lib/mockup/patterns/structure/less
copying mockup/patterns/structure/less/pattern.structure.less -> build/lib/mockup/patterns/structure/less
creating build/lib/mockup/patterns/structure/templates
copying mockup/patterns/structure/templates/actionmenu.xml -> build/lib/mockup/patterns/structure/templates
copying mockup/patterns/structure/templates/paging.xml -> build/lib/mockup/patterns/structure/templates
copying mockup/patterns/structure/templates/selection_button.xml -> build/lib/mockup/patterns/structure/templates
copying mockup/patterns/structure/templates/selection_item.xml -> build/lib/mockup/patterns/structure/templates
copying mockup/patterns/structure/templates/table.xml -> build/lib/mockup/patterns/structure/templates
copying mockup/patterns/structure/templates/tablerow.xml -> build/lib/mockup/patterns/structure/templates
creating build/lib/mockup/patterns/textareamimetypeselector
copying mockup/patterns/textareamimetypeselector/pattern.js -> build/lib/mockup/patterns/textareamimetypeselector
creating build/lib/mockup/patterns/texteditor
copying mockup/patterns/texteditor/pattern.js -> build/lib/mockup/patterns/texteditor
creating build/lib/mockup/patterns/thememapper
copying mockup/patterns/thememapper/pattern.js -> build/lib/mockup/patterns/thememapper
copying mockup/patterns/thememapper/pattern.thememapper.less -> build/lib/mockup/patterns/thememapper
creating build/lib/mockup/patterns/thememapper/js
copying mockup/patterns/thememapper/js/cacheview.js -> build/lib/mockup/patterns/thememapper/js
copying mockup/patterns/thememapper/js/lessbuilderview.js -> build/lib/mockup/patterns/thememapper/js
copying mockup/patterns/thememapper/js/rulebuilder.js -> build/lib/mockup/patterns/thememapper/js
copying mockup/patterns/thememapper/js/rulebuilderview.js -> build/lib/mockup/patterns/thememapper/js
creating build/lib/mockup/patterns/thememapper/templates
copying mockup/patterns/thememapper/templates/inspector.xml -> build/lib/mockup/patterns/thememapper/templates
copying mockup/patterns/thememapper/templates/rulebuilder.xml -> build/lib/mockup/patterns/thememapper/templates
creating build/lib/mockup/patterns/tinymce
copying mockup/patterns/tinymce/pattern.js -> build/lib/mockup/patterns/tinymce
creating build/lib/mockup/patterns/tinymce/js
copying mockup/patterns/tinymce/js/links.js -> build/lib/mockup/patterns/tinymce/js
creating build/lib/mockup/patterns/tinymce/less
copying mockup/patterns/tinymce/less/pattern.tinymce.less -> build/lib/mockup/patterns/tinymce/less
creating build/lib/mockup/patterns/tinymce/templates
copying mockup/patterns/tinymce/templates/image.xml -> build/lib/mockup/patterns/tinymce/templates
copying mockup/patterns/tinymce/templates/link.xml -> build/lib/mockup/patterns/tinymce/templates
copying mockup/patterns/tinymce/templates/upload.xml -> build/lib/mockup/patterns/tinymce/templates
creating build/lib/mockup/patterns/toggle
copying mockup/patterns/toggle/pattern.js -> build/lib/mockup/patterns/toggle
creating build/lib/mockup/patterns/toolbar
copying mockup/patterns/toolbar/pattern.js -> build/lib/mockup/patterns/toolbar
copying mockup/patterns/toolbar/pattern.toolbar.less -> build/lib/mockup/patterns/toolbar
copying mockup/patterns/toolbar/variables.less -> build/lib/mockup/patterns/toolbar
creating build/lib/mockup/patterns/tooltip
copying mockup/patterns/tooltip/pattern.js -> build/lib/mockup/patterns/tooltip
copying mockup/patterns/tooltip/pattern.tooltip.less -> build/lib/mockup/patterns/tooltip
creating build/lib/mockup/patterns/tree
copying mockup/patterns/tree/pattern.js -> build/lib/mockup/patterns/tree
copying mockup/patterns/tree/pattern.tree.less -> build/lib/mockup/patterns/tree
creating build/lib/mockup/patterns/upload
copying mockup/patterns/upload/pattern.js -> build/lib/mockup/patterns/upload
creating build/lib/mockup/patterns/upload/less
copying mockup/patterns/upload/less/pattern.upload.less -> build/lib/mockup/patterns/upload/less
creating build/lib/mockup/patterns/upload/templates
copying mockup/patterns/upload/templates/preview.xml -> build/lib/mockup/patterns/upload/templates
copying mockup/patterns/upload/templates/upload.xml -> build/lib/mockup/patterns/upload/templates
creating build/lib/mockup/tests
copying mockup/tests/config.js -> build/lib/mockup/tests
copying mockup/tests/fakeserver.js -> build/lib/mockup/tests
copying mockup/tests/i18n-test.js -> build/lib/mockup/tests
copying mockup/tests/pattern-autotoc-test.js -> build/lib/mockup/tests
copying mockup/tests/pattern-backdrop-test.js -> build/lib/mockup/tests
copying mockup/tests/pattern-contentloader-test.js -> build/lib/mockup/tests
copying mockup/tests/pattern-cookietrigger-test.js -> build/lib/mockup/tests
copying mockup/tests/pattern-eventedit-test.js -> build/lib/mockup/tests
copying mockup/tests/pattern-filemanager-test.js -> build/lib/mockup/tests
copying mockup/tests/pattern-formautofocus-test.js -> build/lib/mockup/tests
copying mockup/tests/pattern-formunloadalert-test.js -> build/lib/mockup/tests
copying mockup/tests/pattern-inlinevalidation-test.js -> build/lib/mockup/tests
copying mockup/tests/pattern-livesearch-test.js -> build/lib/mockup/tests
copying mockup/tests/pattern-markspeciallinks-test.js -> build/lib/mockup/tests
copying mockup/tests/pattern-modal-test.js -> build/lib/mockup/tests
copying mockup/tests/pattern-moment-test.js -> build/lib/mockup/tests
copying mockup/tests/pattern-passwordstrength-test.js -> build/lib/mockup/tests
copying mockup/tests/pattern-pickadate-test.js -> build/lib/mockup/tests
copying mockup/tests/pattern-preventdoublesubmit-test.js -> build/lib/mockup/tests
copying mockup/tests/pattern-relateditems-test.js -> build/lib/mockup/tests
copying mockup/tests/pattern-resourceregistry-test.js -> build/lib/mockup/tests
copying mockup/tests/pattern-select2-test.js -> build/lib/mockup/tests
copying mockup/tests/pattern-sortable-test.js -> build/lib/mockup/tests
copying mockup/tests/pattern-structure-test.js -> build/lib/mockup/tests
copying mockup/tests/pattern-textareamimetypeselector-test.js -> build/lib/mockup/tests
copying mockup/tests/pattern-thememapper-test.js -> build/lib/mockup/tests
copying mockup/tests/pattern-tinymce-test.js -> build/lib/mockup/tests
copying mockup/tests/pattern-toggle-test.js -> build/lib/mockup/tests
copying mockup/tests/pattern-toolbar-test.js -> build/lib/mockup/tests
copying mockup/tests/pattern-tooltip-test.js -> build/lib/mockup/tests
copying mockup/tests/pattern-tree-test.js -> build/lib/mockup/tests
copying mockup/tests/pattern-upload-test.js -> build/lib/mockup/tests
copying mockup/tests/router-test.js -> build/lib/mockup/tests
copying mockup/tests/utils-test.js -> build/lib/mockup/tests
creating build/lib/mockup/tests/files
copying mockup/tests/files/lessconfig.js -> build/lib/mockup/tests/files
copying mockup/tests/files/mapper.html -> build/lib/mockup/tests/files
copying mockup/tests/files/r.js -> build/lib/mockup/tests/files
creating build/lib/mockup/tests/images
copying mockup/tests/images/extralarge.jpg -> build/lib/mockup/tests/images
copying mockup/tests/images/large.jpg -> build/lib/mockup/tests/images
copying mockup/tests/images/medium.jpg -> build/lib/mockup/tests/images
copying mockup/tests/images/small.jpg -> build/lib/mockup/tests/images
creating build/lib/mockup/tests/images/plone.png
creating build/lib/mockup/tests/images/plone.png/imagescale
copying mockup/tests/images/plone.png/imagescale/large -> build/lib/mockup/tests/images/plone.png/imagescale
copying mockup/tests/images/plone.png/imagescale/preview -> build/lib/mockup/tests/images/plone.png/imagescale
copying mockup/tests/images/plone.png/imagescale/thumb -> build/lib/mockup/tests/images/plone.png/imagescale
creating build/lib/mockup/tests/json
copying mockup/tests/json/contextInfo.json -> build/lib/mockup/tests/json
copying mockup/tests/json/fileTree.json -> build/lib/mockup/tests/json
copying mockup/tests/json/i18n.json -> build/lib/mockup/tests/json
copying mockup/tests/json/queryStringCriteria.json -> build/lib/mockup/tests/json
copying mockup/tests/json/users.json -> build/lib/mockup/tests/json
+ exit 0
Executing(%install): /bin/sh -e /usr/src/tmp/rpm-tmp.67959
+ umask 022
+ /bin/mkdir -p /usr/src/RPM/BUILD
+ cd /usr/src/RPM/BUILD
+ /bin/chmod -Rf u+rwX -- /usr/src/tmp/python3-module-mockup-buildroot
+ :
+ /bin/rm -rf -- /usr/src/tmp/python3-module-mockup-buildroot
+ PATH=/usr/libexec/rpm-build:/usr/src/bin:/bin:/usr/bin:/usr/X11R6/bin:/usr/games
+ cd python3-module-mockup-3.1.1
+ CFLAGS='-pipe -frecord-gcc-switches -Wall -g -O2 -flto=auto'
+ export CFLAGS
+ CXXFLAGS='-pipe -frecord-gcc-switches -Wall -g -O2 -flto=auto'
+ export CXXFLAGS
+ FFLAGS='-pipe -frecord-gcc-switches -Wall -g -O2 -flto=auto'
+ export FFLAGS
+ /usr/bin/python3 setup.py install --skip-build --root=/usr/src/tmp/python3-module-mockup-buildroot --force
running install
/usr/lib64/python3/site-packages/setuptools/_distutils/cmd.py:66: SetuptoolsDeprecationWarning: setup.py install is deprecated.
!!

        ********************************************************************************
        Please avoid running ``setup.py`` directly.
        Instead, use pypa/build, pypa/installer, pypa/build or
        other standards-based tools.

        See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html for details.
        ********************************************************************************

!!
  self.initialize_options()
running install_lib
creating /usr/src/tmp/python3-module-mockup-buildroot
creating /usr/src/tmp/python3-module-mockup-buildroot/usr
creating /usr/src/tmp/python3-module-mockup-buildroot/usr/lib
creating /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3
creating /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages
creating /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup
creating /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/tests
creating /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/tests/json
copying build/lib/mockup/tests/json/users.json -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/tests/json
copying build/lib/mockup/tests/json/queryStringCriteria.json -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/tests/json
copying build/lib/mockup/tests/json/i18n.json -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/tests/json
copying build/lib/mockup/tests/json/fileTree.json -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/tests/json
copying build/lib/mockup/tests/json/contextInfo.json -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/tests/json
creating /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/tests/images
creating /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/tests/images/plone.png
creating /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/tests/images/plone.png/imagescale
copying build/lib/mockup/tests/images/plone.png/imagescale/thumb -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/tests/images/plone.png/imagescale
copying build/lib/mockup/tests/images/plone.png/imagescale/preview -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/tests/images/plone.png/imagescale
copying build/lib/mockup/tests/images/plone.png/imagescale/large -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/tests/images/plone.png/imagescale
copying build/lib/mockup/tests/images/small.jpg -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/tests/images
copying build/lib/mockup/tests/images/medium.jpg -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/tests/images
copying build/lib/mockup/tests/images/large.jpg -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/tests/images
copying build/lib/mockup/tests/images/extralarge.jpg -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/tests/images
creating /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/tests/files
copying build/lib/mockup/tests/files/r.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/tests/files
copying build/lib/mockup/tests/files/mapper.html -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/tests/files
copying build/lib/mockup/tests/files/lessconfig.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/tests/files
copying build/lib/mockup/tests/utils-test.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/tests
copying build/lib/mockup/tests/router-test.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/tests
copying build/lib/mockup/tests/pattern-upload-test.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/tests
copying build/lib/mockup/tests/pattern-tree-test.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/tests
copying build/lib/mockup/tests/pattern-tooltip-test.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/tests
copying build/lib/mockup/tests/pattern-toolbar-test.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/tests
copying build/lib/mockup/tests/pattern-toggle-test.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/tests
copying build/lib/mockup/tests/pattern-tinymce-test.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/tests
copying build/lib/mockup/tests/pattern-thememapper-test.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/tests
copying build/lib/mockup/tests/pattern-textareamimetypeselector-test.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/tests
copying build/lib/mockup/tests/pattern-structure-test.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/tests
copying build/lib/mockup/tests/pattern-sortable-test.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/tests
copying build/lib/mockup/tests/pattern-select2-test.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/tests
copying build/lib/mockup/tests/pattern-resourceregistry-test.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/tests
copying build/lib/mockup/tests/pattern-relateditems-test.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/tests
copying build/lib/mockup/tests/pattern-preventdoublesubmit-test.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/tests
copying build/lib/mockup/tests/pattern-pickadate-test.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/tests
copying build/lib/mockup/tests/pattern-passwordstrength-test.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/tests
copying build/lib/mockup/tests/pattern-moment-test.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/tests
copying build/lib/mockup/tests/pattern-modal-test.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/tests
copying build/lib/mockup/tests/pattern-markspeciallinks-test.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/tests
copying build/lib/mockup/tests/pattern-livesearch-test.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/tests
copying build/lib/mockup/tests/pattern-inlinevalidation-test.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/tests
copying build/lib/mockup/tests/pattern-formunloadalert-test.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/tests
copying build/lib/mockup/tests/pattern-formautofocus-test.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/tests
copying build/lib/mockup/tests/pattern-filemanager-test.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/tests
copying build/lib/mockup/tests/pattern-eventedit-test.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/tests
copying build/lib/mockup/tests/pattern-cookietrigger-test.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/tests
copying build/lib/mockup/tests/pattern-contentloader-test.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/tests
copying build/lib/mockup/tests/pattern-backdrop-test.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/tests
copying build/lib/mockup/tests/pattern-autotoc-test.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/tests
copying build/lib/mockup/tests/i18n-test.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/tests
copying build/lib/mockup/tests/fakeserver.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/tests
copying build/lib/mockup/tests/config.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/tests
creating /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns
creating /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/upload
creating /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/upload/templates
copying build/lib/mockup/patterns/upload/templates/upload.xml -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/upload/templates
copying build/lib/mockup/patterns/upload/templates/preview.xml -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/upload/templates
creating /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/upload/less
copying build/lib/mockup/patterns/upload/less/pattern.upload.less -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/upload/less
copying build/lib/mockup/patterns/upload/pattern.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/upload
creating /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/tree
copying build/lib/mockup/patterns/tree/pattern.tree.less -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/tree
copying build/lib/mockup/patterns/tree/pattern.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/tree
creating /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/tooltip
copying build/lib/mockup/patterns/tooltip/pattern.tooltip.less -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/tooltip
copying build/lib/mockup/patterns/tooltip/pattern.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/tooltip
creating /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/toolbar
copying build/lib/mockup/patterns/toolbar/variables.less -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/toolbar
copying build/lib/mockup/patterns/toolbar/pattern.toolbar.less -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/toolbar
copying build/lib/mockup/patterns/toolbar/pattern.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/toolbar
creating /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/toggle
copying build/lib/mockup/patterns/toggle/pattern.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/toggle
creating /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/tinymce
creating /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/tinymce/templates
copying build/lib/mockup/patterns/tinymce/templates/upload.xml -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/tinymce/templates
copying build/lib/mockup/patterns/tinymce/templates/link.xml -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/tinymce/templates
copying build/lib/mockup/patterns/tinymce/templates/image.xml -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/tinymce/templates
creating /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/tinymce/less
copying build/lib/mockup/patterns/tinymce/less/pattern.tinymce.less -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/tinymce/less
creating /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/tinymce/js
copying build/lib/mockup/patterns/tinymce/js/links.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/tinymce/js
copying build/lib/mockup/patterns/tinymce/pattern.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/tinymce
creating /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/thememapper
creating /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/thememapper/templates
copying build/lib/mockup/patterns/thememapper/templates/rulebuilder.xml -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/thememapper/templates
copying build/lib/mockup/patterns/thememapper/templates/inspector.xml -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/thememapper/templates
creating /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/thememapper/js
copying build/lib/mockup/patterns/thememapper/js/rulebuilderview.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/thememapper/js
copying build/lib/mockup/patterns/thememapper/js/rulebuilder.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/thememapper/js
copying build/lib/mockup/patterns/thememapper/js/lessbuilderview.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/thememapper/js
copying build/lib/mockup/patterns/thememapper/js/cacheview.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/thememapper/js
copying build/lib/mockup/patterns/thememapper/pattern.thememapper.less -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/thememapper
copying build/lib/mockup/patterns/thememapper/pattern.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/thememapper
creating /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/texteditor
copying build/lib/mockup/patterns/texteditor/pattern.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/texteditor
creating /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/textareamimetypeselector
copying build/lib/mockup/patterns/textareamimetypeselector/pattern.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/textareamimetypeselector
creating /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/structure
creating /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/structure/templates
copying build/lib/mockup/patterns/structure/templates/tablerow.xml -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/structure/templates
copying build/lib/mockup/patterns/structure/templates/table.xml -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/structure/templates
copying build/lib/mockup/patterns/structure/templates/selection_item.xml -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/structure/templates
copying build/lib/mockup/patterns/structure/templates/selection_button.xml -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/structure/templates
copying build/lib/mockup/patterns/structure/templates/paging.xml -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/structure/templates
copying build/lib/mockup/patterns/structure/templates/actionmenu.xml -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/structure/templates
creating /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/structure/less
copying build/lib/mockup/patterns/structure/less/pattern.structure.less -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/structure/less
creating /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/structure/js
creating /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/structure/js/views
copying build/lib/mockup/patterns/structure/js/views/upload.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/structure/js/views
copying build/lib/mockup/patterns/structure/js/views/textfilter.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/structure/js/views
copying build/lib/mockup/patterns/structure/js/views/tablerow.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/structure/js/views
copying build/lib/mockup/patterns/structure/js/views/table.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/structure/js/views
copying build/lib/mockup/patterns/structure/js/views/selectionwell.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/structure/js/views
copying build/lib/mockup/patterns/structure/js/views/selectionbutton.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/structure/js/views
copying build/lib/mockup/patterns/structure/js/views/rearrange.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/structure/js/views
copying build/lib/mockup/patterns/structure/js/views/paging.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/structure/js/views
copying build/lib/mockup/patterns/structure/js/views/generic-popover.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/structure/js/views
copying build/lib/mockup/patterns/structure/js/views/columns.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/structure/js/views
copying build/lib/mockup/patterns/structure/js/views/app.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/structure/js/views
copying build/lib/mockup/patterns/structure/js/views/addmenu.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/structure/js/views
copying build/lib/mockup/patterns/structure/js/views/actionmenu.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/structure/js/views
creating /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/structure/js/models
copying build/lib/mockup/patterns/structure/js/models/result.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/structure/js/models
creating /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/structure/js/collections
copying build/lib/mockup/patterns/structure/js/collections/selected.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/structure/js/collections
copying build/lib/mockup/patterns/structure/js/collections/result.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/structure/js/collections
copying build/lib/mockup/patterns/structure/js/navigation.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/structure/js
copying build/lib/mockup/patterns/structure/js/actions.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/structure/js
copying build/lib/mockup/patterns/structure/js/actionmenu.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/structure/js
copying build/lib/mockup/patterns/structure/pattern.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/structure
copying build/lib/mockup/patterns/structure/pattern-structureupdater.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/structure
copying build/lib/mockup/patterns/structure/README.rst -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/structure
creating /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/sortable
copying build/lib/mockup/patterns/sortable/pattern.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/sortable
creating /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/select2
copying build/lib/mockup/patterns/select2/pattern.select2.less -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/select2
copying build/lib/mockup/patterns/select2/pattern.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/select2
creating /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/resourceregistry
creating /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/resourceregistry/js
copying build/lib/mockup/patterns/resourceregistry/js/registry.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/resourceregistry/js
copying build/lib/mockup/patterns/resourceregistry/js/patternoptions.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/resourceregistry/js
copying build/lib/mockup/patterns/resourceregistry/js/overrides.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/resourceregistry/js
copying build/lib/mockup/patterns/resourceregistry/js/less.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/resourceregistry/js
copying build/lib/mockup/patterns/resourceregistry/js/iframe.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/resourceregistry/js
copying build/lib/mockup/patterns/resourceregistry/js/fields.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/resourceregistry/js
copying build/lib/mockup/patterns/resourceregistry/js/builder.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/resourceregistry/js
copying build/lib/mockup/patterns/resourceregistry/pattern.resourceregistry.less -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/resourceregistry
copying build/lib/mockup/patterns/resourceregistry/pattern.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/resourceregistry
creating /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/relateditems
creating /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/relateditems/templates
copying build/lib/mockup/patterns/relateditems/templates/toolbar.xml -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/relateditems/templates
copying build/lib/mockup/patterns/relateditems/templates/selection.xml -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/relateditems/templates
copying build/lib/mockup/patterns/relateditems/templates/result.xml -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/relateditems/templates
copying build/lib/mockup/patterns/relateditems/templates/recentlyused.xml -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/relateditems/templates
copying build/lib/mockup/patterns/relateditems/templates/favorite.xml -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/relateditems/templates
copying build/lib/mockup/patterns/relateditems/templates/breadcrumb.xml -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/relateditems/templates
copying build/lib/mockup/patterns/relateditems/upload.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/relateditems
copying build/lib/mockup/patterns/relateditems/pattern.relateditems.less -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/relateditems
copying build/lib/mockup/patterns/relateditems/pattern.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/relateditems
creating /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/recurrence
copying build/lib/mockup/patterns/recurrence/pattern.recurrence.less -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/recurrence
copying build/lib/mockup/patterns/recurrence/pattern.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/recurrence
creating /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/querystring
copying build/lib/mockup/patterns/querystring/pattern.querystring.less -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/querystring
copying build/lib/mockup/patterns/querystring/pattern.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/querystring
creating /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/preventdoublesubmit
copying build/lib/mockup/patterns/preventdoublesubmit/pattern.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/preventdoublesubmit
creating /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/pickadate
copying build/lib/mockup/patterns/pickadate/pattern.pickadate.less -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/pickadate
copying build/lib/mockup/patterns/pickadate/pattern.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/pickadate
creating /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/passwordstrength
copying build/lib/mockup/patterns/passwordstrength/pattern.passwordstrength.less -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/passwordstrength
copying build/lib/mockup/patterns/passwordstrength/pattern.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/passwordstrength
creating /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/navigationmarker
copying build/lib/mockup/patterns/navigationmarker/pattern.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/navigationmarker
creating /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/moment
copying build/lib/mockup/patterns/moment/pattern.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/moment
creating /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/modal
copying build/lib/mockup/patterns/modal/pattern.modal.less -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/modal
copying build/lib/mockup/patterns/modal/pattern.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/modal
creating /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/markspeciallinks
copying build/lib/mockup/patterns/markspeciallinks/pattern.markspeciallinks.less -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/markspeciallinks
copying build/lib/mockup/patterns/markspeciallinks/pattern.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/markspeciallinks
creating /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/livesearch
copying build/lib/mockup/patterns/livesearch/pattern.livesearch.less -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/livesearch
copying build/lib/mockup/patterns/livesearch/pattern.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/livesearch
creating /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/inlinevalidation
copying build/lib/mockup/patterns/inlinevalidation/pattern.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/inlinevalidation
creating /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/formunloadalert
copying build/lib/mockup/patterns/formunloadalert/pattern.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/formunloadalert
creating /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/formautofocus
copying build/lib/mockup/patterns/formautofocus/pattern.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/formautofocus
creating /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/filemanager
creating /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/filemanager/templates
copying build/lib/mockup/patterns/filemanager/templates/popover.xml -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/filemanager/templates
copying build/lib/mockup/patterns/filemanager/templates/app.xml -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/filemanager/templates
creating /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/filemanager/js
copying build/lib/mockup/patterns/filemanager/js/upload.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/filemanager/js
copying build/lib/mockup/patterns/filemanager/js/rename.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/filemanager/js
copying build/lib/mockup/patterns/filemanager/js/newfolder.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/filemanager/js
copying build/lib/mockup/patterns/filemanager/js/findinfiles.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/filemanager/js
copying build/lib/mockup/patterns/filemanager/js/findfile.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/filemanager/js
copying build/lib/mockup/patterns/filemanager/js/delete.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/filemanager/js
copying build/lib/mockup/patterns/filemanager/js/customize.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/filemanager/js
copying build/lib/mockup/patterns/filemanager/js/basepopover.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/filemanager/js
copying build/lib/mockup/patterns/filemanager/js/addnew.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/filemanager/js
copying build/lib/mockup/patterns/filemanager/pattern.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/filemanager
copying build/lib/mockup/patterns/filemanager/pattern.filemanager.less -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/filemanager
creating /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/eventedit
copying build/lib/mockup/patterns/eventedit/pattern.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/eventedit
creating /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/datatables
copying build/lib/mockup/patterns/datatables/pattern.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/datatables
copying build/lib/mockup/patterns/datatables/pattern.datatables.less -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/datatables
creating /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/cookietrigger
copying build/lib/mockup/patterns/cookietrigger/pattern.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/cookietrigger
creating /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/contentloader
copying build/lib/mockup/patterns/contentloader/pattern.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/contentloader
creating /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/base
copying build/lib/mockup/patterns/base/pattern.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/base
creating /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/backdrop
copying build/lib/mockup/patterns/backdrop/pattern.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/backdrop
creating /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/autotoc
copying build/lib/mockup/patterns/autotoc/pattern.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/autotoc
copying build/lib/mockup/patterns/autotoc/pattern.autotoc.less -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/patterns/autotoc
creating /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/lib
copying build/lib/mockup/lib/jquery.event.drop.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/lib
copying build/lib/mockup/lib/jquery.event.drag.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/lib
creating /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/less
copying build/lib/mockup/less/widgets.less -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/less
copying build/lib/mockup/less/ui.less -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/less
copying build/lib/mockup/less/structure.less -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/less
copying build/lib/mockup/less/resourceregistry.less -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/less
copying build/lib/mockup/less/popover.less -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/less
copying build/lib/mockup/less/plonetoolbar.less -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/less
copying build/lib/mockup/less/plonelogo.less -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/less
copying build/lib/mockup/less/plone.less -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/less
copying build/lib/mockup/less/mixins.less -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/less
copying build/lib/mockup/less/filemanager.less -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/less
copying build/lib/mockup/less/docs.less -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/less
copying build/lib/mockup/less/base.less -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/less
creating /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/js
creating /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/js/ui
creating /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/js/ui/views
copying build/lib/mockup/js/ui/views/toolbar.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/js/ui/views
copying build/lib/mockup/js/ui/views/popover.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/js/ui/views
copying build/lib/mockup/js/ui/views/dropdown.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/js/ui/views
copying build/lib/mockup/js/ui/views/container.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/js/ui/views
copying build/lib/mockup/js/ui/views/buttongroup.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/js/ui/views
copying build/lib/mockup/js/ui/views/button.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/js/ui/views
copying build/lib/mockup/js/ui/views/base.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/js/ui/views
copying build/lib/mockup/js/ui/views/anchor.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/js/ui/views
creating /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/js/ui/templates
copying build/lib/mockup/js/ui/templates/popover.xml -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/js/ui/templates
copying build/lib/mockup/js/ui/templates/dropdown.xml -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/js/ui/templates
creating /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/js/docs
copying build/lib/mockup/js/docs/view.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/js/docs
copying build/lib/mockup/js/docs/pattern.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/js/docs
copying build/lib/mockup/js/docs/page.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/js/docs
copying build/lib/mockup/js/docs/navigation.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/js/docs
copying build/lib/mockup/js/docs/app.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/js/docs
creating /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/js/bundles
copying build/lib/mockup/js/bundles/widgets.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/js/bundles
copying build/lib/mockup/js/bundles/structure.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/js/bundles
copying build/lib/mockup/js/bundles/resourceregistry.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/js/bundles
copying build/lib/mockup/js/bundles/plone.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/js/bundles
copying build/lib/mockup/js/bundles/filemanager.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/js/bundles
copying build/lib/mockup/js/bundles/docs.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/js/bundles
copying build/lib/mockup/js/utils.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/js
copying build/lib/mockup/js/router.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/js
copying build/lib/mockup/js/i18n.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/js
copying build/lib/mockup/js/i18n-wrapper.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/js
copying build/lib/mockup/js/grunt.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/js
copying build/lib/mockup/js/config.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/js
copying build/lib/mockup/index.html -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup
copying build/lib/mockup/configure.zcml -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup
copying build/lib/mockup/LEARN.md -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup
copying build/lib/mockup/Gruntfile.js -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup
copying build/lib/mockup/GETTING_STARTED.md -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup
copying build/lib/mockup/CONTRIBUTE.md -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup
copying build/lib/mockup/.jshintrc -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup
copying build/lib/mockup/.jscs.json -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup
copying build/lib/mockup/__init__.py -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup
creating /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup_
copying build/lib/mockup_/__init__.py -> /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup_
byte-compiling /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/__init__.py to __init__.cpython-310.pyc
byte-compiling /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup_/__init__.py to __init__.cpython-310.pyc
running install_egg_info
running egg_info
writing mockup.egg-info/PKG-INFO
writing dependency_links to mockup.egg-info/dependency_links.txt
writing entry points to mockup.egg-info/entry_points.txt
writing top-level names to mockup.egg-info/top_level.txt
reading manifest file 'mockup.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
no previously-included directories found matching '.nix'
no previously-included directories found matching 'dist'
no previously-included directories found matching 'mockup/node_modules'
no previously-included directories found matching 'mockup/build'
no previously-included directories found matching 'mockup/coverage'
no previously-included directories found matching 'mockup/docs'
no previously-included directories found matching 'mockup/node_modules'
warning: no previously-included files found matching '.bowerrc'
warning: no previously-included files found matching '.travis.yml'
warning: no previously-included files found matching 'Makefile'
warning: no previously-included files found matching '*.sh'
warning: no previously-included files found matching 'Vagrantfile'
warning: no previously-included files matching '*.pycinclude' found anywhere in distribution
warning: no previously-included files matching '*' found under directory 'news'
warning: no previously-included files found matching 'news'
warning: no previously-included files found matching 'yarn.lock'
adding license file 'LICENSE.rst'
writing manifest file 'mockup.egg-info/SOURCES.txt'
Copying mockup.egg-info to /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup-3.1.1-py3.10.egg-info
running install_scripts
+ /usr/lib/rpm/brp-alt
Cleaning files in /usr/src/tmp/python3-module-mockup-buildroot (auto)
Verifying and fixing files in /usr/src/tmp/python3-module-mockup-buildroot (binconfig,pkgconfig,libtool,desktop,gnuconfig)
Checking contents of files in /usr/src/tmp/python3-module-mockup-buildroot/ (default)
Compressing files in /usr/src/tmp/python3-module-mockup-buildroot (auto)
Adjusting library links in /usr/src/tmp/python3-module-mockup-buildroot
./usr/lib: (from <cmdline>:0)
./usr/lib/python3/site-packages/mockup/lib: (from <cmdline>:0)
Verifying ELF objects in /usr/src/tmp/python3-module-mockup-buildroot (arch=normal,fhs=normal,lfs=relaxed,lint=relaxed,rpath=normal,stack=normal,textrel=normal,unresolved=normal)
Bytecompiling python3 modules in /usr/src/tmp/python3-module-mockup-buildroot using /usr/bin/python3
unlink /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/__pycache__/__init__.cpython-310.pyc
compile /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/__init__.py
unlink /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup_/__pycache__/__init__.cpython-310.pyc
compile /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup_/__init__.py
Bytecompiling python3 modules with optimization in /usr/src/tmp/python3-module-mockup-buildroot using /usr/bin/python3 -O
compile /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/__init__.py
compile /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup_/__init__.py
Bytecompiling python3 modules with optimization-2 in /usr/src/tmp/python3-module-mockup-buildroot using /usr/bin/python3 -OO
compile /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup/__init__.py
compile /usr/src/tmp/python3-module-mockup-buildroot/usr/lib/python3/site-packages/mockup_/__init__.py
Hardlinking identical .pyc and .opt-?.pyc files
'./usr/lib/python3/site-packages/mockup/__pycache__/__init__.cpython-310.opt-1.pyc' => './usr/lib/python3/site-packages/mockup/__pycache__/__init__.cpython-310.pyc'
'./usr/lib/python3/site-packages/mockup/__pycache__/__init__.cpython-310.opt-2.pyc' => './usr/lib/python3/site-packages/mockup/__pycache__/__init__.cpython-310.opt-1.pyc'
'./usr/lib/python3/site-packages/mockup_/__pycache__/__init__.cpython-310.opt-1.pyc' => './usr/lib/python3/site-packages/mockup_/__pycache__/__init__.cpython-310.pyc'
'./usr/lib/python3/site-packages/mockup_/__pycache__/__init__.cpython-310.opt-2.pyc' => './usr/lib/python3/site-packages/mockup_/__pycache__/__init__.cpython-310.opt-1.pyc'
Executing(%check): /bin/sh -e /usr/src/tmp/rpm-tmp.21974
+ umask 022
+ /bin/mkdir -p /usr/src/RPM/BUILD
+ cd /usr/src/RPM/BUILD
+ cd python3-module-mockup-3.1.1
+ /usr/bin/python3 setup.py test
running test
WARNING: Testing via this command is deprecated and will be removed in a future version. Users looking for a generic test entry point independent of test runner are encouraged to use tox.
/usr/lib64/python3/site-packages/setuptools/command/test.py:199: _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are deprecated.
!!

        ********************************************************************************
        Requirements should be satisfied by a PEP 517 installer.
        If you are using pip, you can try `pip install --use-pep517`.
        ********************************************************************************

!!
  ir_d = dist.fetch_build_eggs(dist.install_requires)
WARNING: The wheel package is not available.
/usr/lib64/python3/site-packages/setuptools/command/test.py:200: _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are deprecated.
!!

        ********************************************************************************
        Requirements should be satisfied by a PEP 517 installer.
        If you are using pip, you can try `pip install --use-pep517`.
        ********************************************************************************

!!
  tr_d = dist.fetch_build_eggs(dist.tests_require or [])
WARNING: The wheel package is not available.
/usr/lib64/python3/site-packages/setuptools/command/test.py:201: _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are deprecated.
!!

        ********************************************************************************
        Requirements should be satisfied by a PEP 517 installer.
        If you are using pip, you can try `pip install --use-pep517`.
        ********************************************************************************

!!
  er_d = dist.fetch_build_eggs(
WARNING: The wheel package is not available.
running egg_info
writing mockup.egg-info/PKG-INFO
writing dependency_links to mockup.egg-info/dependency_links.txt
writing entry points to mockup.egg-info/entry_points.txt
writing top-level names to mockup.egg-info/top_level.txt
reading manifest file 'mockup.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
no previously-included directories found matching '.nix'
no previously-included directories found matching 'dist'
no previously-included directories found matching 'mockup/node_modules'
no previously-included directories found matching 'mockup/build'
no previously-included directories found matching 'mockup/coverage'
no previously-included directories found matching 'mockup/docs'
no previously-included directories found matching 'mockup/node_modules'
warning: no previously-included files found matching '.bowerrc'
warning: no previously-included files found matching '.travis.yml'
warning: no previously-included files found matching 'Makefile'
warning: no previously-included files found matching '*.sh'
warning: no previously-included files found matching 'Vagrantfile'
warning: no previously-included files matching '*.pycinclude' found anywhere in distribution
warning: no previously-included files matching '*' found under directory 'news'
warning: no previously-included files found matching 'news'
warning: no previously-included files found matching 'yarn.lock'
adding license file 'LICENSE.rst'
writing manifest file 'mockup.egg-info/SOURCES.txt'
running build_ext

----------------------------------------------------------------------
Ran 0 tests in 0.000s

OK
+ exit 0
Processing files: python3-module-mockup-3.1.1-alt1
Executing(%doc): /bin/sh -e /usr/src/tmp/rpm-tmp.21974
+ umask 022
+ /bin/mkdir -p /usr/src/RPM/BUILD
+ cd /usr/src/RPM/BUILD
+ cd python3-module-mockup-3.1.1
+ DOCDIR=/usr/src/tmp/python3-module-mockup-buildroot/usr/share/doc/python3-module-mockup-3.1.1
+ export DOCDIR
+ rm -rf /usr/src/tmp/python3-module-mockup-buildroot/usr/share/doc/python3-module-mockup-3.1.1
+ /bin/mkdir -p /usr/src/tmp/python3-module-mockup-buildroot/usr/share/doc/python3-module-mockup-3.1.1
+ cp -prL CHANGES.rst CONTRIBUTING.rst LICENSE.rst README.rst /usr/src/tmp/python3-module-mockup-buildroot/usr/share/doc/python3-module-mockup-3.1.1
+ chmod -R go-w /usr/src/tmp/python3-module-mockup-buildroot/usr/share/doc/python3-module-mockup-3.1.1
+ chmod -R a+rX /usr/src/tmp/python3-module-mockup-buildroot/usr/share/doc/python3-module-mockup-3.1.1
+ exit 0
Finding Provides (using /usr/lib/rpm/find-provides)
Executing: /bin/sh -e /usr/src/tmp/rpm-tmp.XyQd2f
find-provides: running scripts (alternatives,debuginfo,lib,pam,perl,pkgconfig,python,python3,shell)
Finding Requires (using /usr/lib/rpm/find-requires)
Executing: /bin/sh -e /usr/src/tmp/rpm-tmp.fxxE70
find-requires: running scripts (cpp,debuginfo,files,lib,pam,perl,pkgconfig,pkgconfiglib,python,python3,rpmlib,shebang,shell,static,symlinks,systemd-services)
Provides: python3(mockup), python3(mockup_)
Requires: /usr/lib/python3/site-packages
Processing files: python3-module-mockup-tests-3.1.1-alt1
Finding Provides (using /usr/lib/rpm/find-provides)
Executing: /bin/sh -e /usr/src/tmp/rpm-tmp.ntJbpc
find-provides: running scripts (alternatives,debuginfo,lib,pam,perl,pkgconfig,python,python3,shell)
Finding Requires (using /usr/lib/rpm/find-requires)
Executing: /bin/sh -e /usr/src/tmp/rpm-tmp.t3D7ZN
find-requires: running scripts (cpp,debuginfo,files,lib,pam,perl,pkgconfig,pkgconfiglib,python,python3,rpmlib,shebang,shell,static,symlinks,systemd-services)
Requires: python3-module-mockup = 3.1.1-alt1, /usr/lib/python3/site-packages
Adding to python3-module-mockup-tests a strict dependency on python3-module-mockup
Removing 1 extra deps from python3-module-mockup-tests due to repentancy on python3-module-mockup
Wrote: /usr/src/RPM/RPMS/noarch/python3-module-mockup-3.1.1-alt1.noarch.rpm (w2.lzdio)
Wrote: /usr/src/RPM/RPMS/noarch/python3-module-mockup-tests-3.1.1-alt1.noarch.rpm (w2.lzdio)
2.70user 0.93system 0:06.20elapsed 58%CPU (0avgtext+0avgdata 26664maxresident)k
0inputs+0outputs (0major+217409minor)pagefaults 0swaps
3.72user 1.78system 0:17.34elapsed 31%CPU (0avgtext+0avgdata 110608maxresident)k
0inputs+0outputs (0major+270033minor)pagefaults 0swaps
--- python3-module-mockup-3.1.1-alt1.noarch.rpm.repo	2020-01-13 12:03:31.000000000 +0000
+++ python3-module-mockup-3.1.1-alt1.noarch.rpm.hasher	2023-05-19 01:08:52.246667611 +0000
@@ -1,9 +1,9 @@
 /usr/lib/python3/site-packages/mockup	40755	root:root	
-/usr/lib/python3/site-packages/mockup-3.1.1-py3.7.egg-info	40755	root:root	
-/usr/lib/python3/site-packages/mockup-3.1.1-py3.7.egg-info/PKG-INFO	100644	root:root	
-/usr/lib/python3/site-packages/mockup-3.1.1-py3.7.egg-info/SOURCES.txt	100644	root:root	
-/usr/lib/python3/site-packages/mockup-3.1.1-py3.7.egg-info/dependency_links.txt	100644	root:root	
-/usr/lib/python3/site-packages/mockup-3.1.1-py3.7.egg-info/entry_points.txt	100644	root:root	
-/usr/lib/python3/site-packages/mockup-3.1.1-py3.7.egg-info/not-zip-safe	100644	root:root	
-/usr/lib/python3/site-packages/mockup-3.1.1-py3.7.egg-info/top_level.txt	100644	root:root	
+/usr/lib/python3/site-packages/mockup-3.1.1-py3.10.egg-info	40755	root:root	
+/usr/lib/python3/site-packages/mockup-3.1.1-py3.10.egg-info/PKG-INFO	100644	root:root	
+/usr/lib/python3/site-packages/mockup-3.1.1-py3.10.egg-info/SOURCES.txt	100644	root:root	
+/usr/lib/python3/site-packages/mockup-3.1.1-py3.10.egg-info/dependency_links.txt	100644	root:root	
+/usr/lib/python3/site-packages/mockup-3.1.1-py3.10.egg-info/entry_points.txt	100644	root:root	
+/usr/lib/python3/site-packages/mockup-3.1.1-py3.10.egg-info/not-zip-safe	100644	root:root	
+/usr/lib/python3/site-packages/mockup-3.1.1-py3.10.egg-info/top_level.txt	100644	root:root	
 /usr/lib/python3/site-packages/mockup/.jscs.json	100644	root:root	
@@ -16,5 +16,5 @@
 /usr/lib/python3/site-packages/mockup/__pycache__	40755	root:root	
-/usr/lib/python3/site-packages/mockup/__pycache__/__init__.cpython-37.opt-1.pyc	100644	root:root	
-/usr/lib/python3/site-packages/mockup/__pycache__/__init__.cpython-37.opt-2.pyc	100644	root:root	
-/usr/lib/python3/site-packages/mockup/__pycache__/__init__.cpython-37.pyc	100644	root:root	
+/usr/lib/python3/site-packages/mockup/__pycache__/__init__.cpython-310.opt-1.pyc	100644	root:root	
+/usr/lib/python3/site-packages/mockup/__pycache__/__init__.cpython-310.opt-2.pyc	100644	root:root	
+/usr/lib/python3/site-packages/mockup/__pycache__/__init__.cpython-310.pyc	100644	root:root	
 /usr/lib/python3/site-packages/mockup/configure.zcml	100644	root:root	
@@ -246,5 +246,5 @@
 /usr/lib/python3/site-packages/mockup_/__pycache__	40755	root:root	
-/usr/lib/python3/site-packages/mockup_/__pycache__/__init__.cpython-37.opt-1.pyc	100644	root:root	
-/usr/lib/python3/site-packages/mockup_/__pycache__/__init__.cpython-37.opt-2.pyc	100644	root:root	
-/usr/lib/python3/site-packages/mockup_/__pycache__/__init__.cpython-37.pyc	100644	root:root	
+/usr/lib/python3/site-packages/mockup_/__pycache__/__init__.cpython-310.opt-1.pyc	100644	root:root	
+/usr/lib/python3/site-packages/mockup_/__pycache__/__init__.cpython-310.opt-2.pyc	100644	root:root	
+/usr/lib/python3/site-packages/mockup_/__pycache__/__init__.cpython-310.pyc	100644	root:root	
 /usr/share/doc/python3-module-mockup-3.1.1	40755	root:root	
@@ -260,9 +260,9 @@
 File: /usr/lib/python3/site-packages/mockup	40755	root:root		
-File: /usr/lib/python3/site-packages/mockup-3.1.1-py3.7.egg-info	40755	root:root		
-File: /usr/lib/python3/site-packages/mockup-3.1.1-py3.7.egg-info/PKG-INFO	100644	root:root	8e1c068cb0813e1cb883d4e3f2d67d99	
-File: /usr/lib/python3/site-packages/mockup-3.1.1-py3.7.egg-info/SOURCES.txt	100644	root:root	2eaddf2567438d600458f302f55784f2	
-File: /usr/lib/python3/site-packages/mockup-3.1.1-py3.7.egg-info/dependency_links.txt	100644	root:root	68b329da9893e34099c7d8ad5cb9c940	
-File: /usr/lib/python3/site-packages/mockup-3.1.1-py3.7.egg-info/entry_points.txt	100644	root:root	44c2861a0ccf390fd8e0053ec0a9c98f	
-File: /usr/lib/python3/site-packages/mockup-3.1.1-py3.7.egg-info/not-zip-safe	100644	root:root	68b329da9893e34099c7d8ad5cb9c940	
-File: /usr/lib/python3/site-packages/mockup-3.1.1-py3.7.egg-info/top_level.txt	100644	root:root	ddbb72ffd39bc4c253c9afc2a0b758fb	
+File: /usr/lib/python3/site-packages/mockup-3.1.1-py3.10.egg-info	40755	root:root		
+File: /usr/lib/python3/site-packages/mockup-3.1.1-py3.10.egg-info/PKG-INFO	100644	root:root	5de4c6b971e26d7dacf734aee942dd0a	
+File: /usr/lib/python3/site-packages/mockup-3.1.1-py3.10.egg-info/SOURCES.txt	100644	root:root	2eaddf2567438d600458f302f55784f2	
+File: /usr/lib/python3/site-packages/mockup-3.1.1-py3.10.egg-info/dependency_links.txt	100644	root:root	68b329da9893e34099c7d8ad5cb9c940	
+File: /usr/lib/python3/site-packages/mockup-3.1.1-py3.10.egg-info/entry_points.txt	100644	root:root	c0ab83146d9941cb40b13aebe7a8a46c	
+File: /usr/lib/python3/site-packages/mockup-3.1.1-py3.10.egg-info/not-zip-safe	100644	root:root	68b329da9893e34099c7d8ad5cb9c940	
+File: /usr/lib/python3/site-packages/mockup-3.1.1-py3.10.egg-info/top_level.txt	100644	root:root	ddbb72ffd39bc4c253c9afc2a0b758fb	
 File: /usr/lib/python3/site-packages/mockup/.jscs.json	100644	root:root	7b1f95fde5ec27121074a56a88d8db7b	
@@ -275,5 +275,5 @@
 File: /usr/lib/python3/site-packages/mockup/__pycache__	40755	root:root		
-File: /usr/lib/python3/site-packages/mockup/__pycache__/__init__.cpython-37.opt-1.pyc	100644	root:root	ac70f57ff31d802432a452137f651585	
-File: /usr/lib/python3/site-packages/mockup/__pycache__/__init__.cpython-37.opt-2.pyc	100644	root:root	ac70f57ff31d802432a452137f651585	
-File: /usr/lib/python3/site-packages/mockup/__pycache__/__init__.cpython-37.pyc	100644	root:root	ac70f57ff31d802432a452137f651585	
+File: /usr/lib/python3/site-packages/mockup/__pycache__/__init__.cpython-310.opt-1.pyc	100644	root:root	a26de3c5ef999b7160bed66d9c79e3d5	
+File: /usr/lib/python3/site-packages/mockup/__pycache__/__init__.cpython-310.opt-2.pyc	100644	root:root	a26de3c5ef999b7160bed66d9c79e3d5	
+File: /usr/lib/python3/site-packages/mockup/__pycache__/__init__.cpython-310.pyc	100644	root:root	a26de3c5ef999b7160bed66d9c79e3d5	
 File: /usr/lib/python3/site-packages/mockup/configure.zcml	100644	root:root	ac4ecffb39dc4044004204510d106e4e	
@@ -505,5 +505,5 @@
 File: /usr/lib/python3/site-packages/mockup_/__pycache__	40755	root:root		
-File: /usr/lib/python3/site-packages/mockup_/__pycache__/__init__.cpython-37.opt-1.pyc	100644	root:root	120203a1d99aecaba04c1036723294df	
-File: /usr/lib/python3/site-packages/mockup_/__pycache__/__init__.cpython-37.opt-2.pyc	100644	root:root	120203a1d99aecaba04c1036723294df	
-File: /usr/lib/python3/site-packages/mockup_/__pycache__/__init__.cpython-37.pyc	100644	root:root	120203a1d99aecaba04c1036723294df	
+File: /usr/lib/python3/site-packages/mockup_/__pycache__/__init__.cpython-310.opt-1.pyc	100644	root:root	5f5a7f083cc230ca1452d1539428ee9a	
+File: /usr/lib/python3/site-packages/mockup_/__pycache__/__init__.cpython-310.opt-2.pyc	100644	root:root	5f5a7f083cc230ca1452d1539428ee9a	
+File: /usr/lib/python3/site-packages/mockup_/__pycache__/__init__.cpython-310.pyc	100644	root:root	5f5a7f083cc230ca1452d1539428ee9a	
 File: /usr/share/doc/python3-module-mockup-3.1.1	40755	root:root		
@@ -513,2 +513,2 @@
 File: /usr/share/doc/python3-module-mockup-3.1.1/README.rst	100644	root:root	8f0226243f81c73f7befe9ba0efddc94	
-RPMIdentity: 15cb70386b49717688c4b8d7ee4a206f1eb8990d54563714131866538554553393c8f24c24f3e1ac474ae532850b2d9f7b30737f65697017a13f75def46b2cb8
+RPMIdentity: fdb469abb7e256c386a6d34e3daa9624080741866bfb31873ac6cd8cc39a49ad69d72110c6008e59823d957e3ad2fef400ba1846f04d2768bb364ad7a66ac6f0