Package: src:pyramid-jinja2
Version: 2.7+dfsg-1.3
Severity: serious
Tags: ftbfs

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:

--------------------------------------------------------------------------------
[...]
 debian/rules build
dh build --with python3 --buildsystem=pybuild
dh: warning: Compatibility levels before 10 are deprecated (level 9 in use)
   dh_update_autotools_config -O--buildsystem=pybuild
   dh_auto_configure -O--buildsystem=pybuild
dh_auto_configure: warning: Compatibility levels before 10 are deprecated 
(level 9 in use)
I: pybuild base:311: python3.12 setup.py config
/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py:268: UserWarning: 
Unknown distribution option: 'tests_require'
  warnings.warn(msg)
/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py:268: UserWarning: 
Unknown distribution option: 'test_suite'
  warnings.warn(msg)
running config
   dh_auto_build -O--buildsystem=pybuild
dh_auto_build: warning: Compatibility levels before 10 are deprecated (level 9 
in use)
I: pybuild base:311: /usr/bin/python3 setup.py build
/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py:268: UserWarning: 
Unknown distribution option: 'tests_require'
  warnings.warn(msg)
/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py:268: UserWarning: 
Unknown distribution option: 'test_suite'
  warnings.warn(msg)
running build
running build_py
creating 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2
copying pyramid_jinja2/compat.py -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2
copying pyramid_jinja2/filters.py -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2
copying pyramid_jinja2/__init__.py -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2
copying pyramid_jinja2/settings.py -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2
copying pyramid_jinja2/i18n.py -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2
creating 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/scaffolds
copying pyramid_jinja2/scaffolds/__init__.py -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/scaffolds
creating 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/tests
copying pyramid_jinja2/tests/extensions.py -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/tests
copying pyramid_jinja2/tests/test_it.py -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/tests
copying pyramid_jinja2/tests/base.py -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/tests
copying pyramid_jinja2/tests/__init__.py -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/tests
copying pyramid_jinja2/tests/test_settings.py -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/tests
copying pyramid_jinja2/tests/test_ext.py -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/tests
copying pyramid_jinja2/tests/test_filters.py -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/tests
creating 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/demo
copying pyramid_jinja2/demo/__init__.py -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/demo
copying pyramid_jinja2/demo/tests.py -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/demo
running egg_info
creating pyramid_jinja2.egg-info
writing pyramid_jinja2.egg-info/PKG-INFO
writing dependency_links to pyramid_jinja2.egg-info/dependency_links.txt
writing entry points to pyramid_jinja2.egg-info/entry_points.txt
writing requirements to pyramid_jinja2.egg-info/requires.txt
writing top-level names to pyramid_jinja2.egg-info/top_level.txt
writing manifest file 'pyramid_jinja2.egg-info/SOURCES.txt'
reading manifest file 'pyramid_jinja2.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
warning: no previously-included files matching '*.pyc' found under directory 
'docs'
warning: no previously-included files matching '*.pyc' found under directory 
'pyramid_jinja2'
adding license file 'LICENSE.txt'
writing manifest file 'pyramid_jinja2.egg-info/SOURCES.txt'
/usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: 
Package 'pyramid_jinja2.demo.locale' is absent from the `packages` 
configuration.
!!

        
********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'pyramid_jinja2.demo.locale' 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 'pyramid_jinja2.demo.locale' 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 'pyramid_jinja2.demo.locale' to be distributed and are
        already explicitly excluding 'pyramid_jinja2.demo.locale' via
        `find_namespace_packages(...)/find_namespace` or 
`find_packages(...)/find`,
        you can try to use `exclude_package_data`, or 
`include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools 
documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        
********************************************************************************

!!
  check.warn(importable)
/usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: 
Package 'pyramid_jinja2.demo.locale.fr.LC_MESSAGES' is absent from the 
`packages` configuration.
!!

        
********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'pyramid_jinja2.demo.locale.fr.LC_MESSAGES' as an 
importable package[^1],
        but it is absent from setuptools' `packages` configuration.

        This leads to an ambiguous overall configuration. If you want to 
distribute this
        package, please make sure that 
'pyramid_jinja2.demo.locale.fr.LC_MESSAGES' is explicitly added
        to the `packages` configuration field.

        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).

        You can read more about "package discovery" on setuptools documentation 
page:

        - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

        If you don't want 'pyramid_jinja2.demo.locale.fr.LC_MESSAGES' to be 
distributed and are
        already explicitly excluding 
'pyramid_jinja2.demo.locale.fr.LC_MESSAGES' via
        `find_namespace_packages(...)/find_namespace` or 
`find_packages(...)/find`,
        you can try to use `exclude_package_data`, or 
`include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools 
documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        
********************************************************************************

!!
  check.warn(importable)
/usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: 
Package 'pyramid_jinja2.scaffolds.jinja2_starter' is absent from the `packages` 
configuration.
!!

        
********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'pyramid_jinja2.scaffolds.jinja2_starter' 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 
'pyramid_jinja2.scaffolds.jinja2_starter' 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 'pyramid_jinja2.scaffolds.jinja2_starter' to be 
distributed and are
        already explicitly excluding 'pyramid_jinja2.scaffolds.jinja2_starter' 
via
        `find_namespace_packages(...)/find_namespace` or 
`find_packages(...)/find`,
        you can try to use `exclude_package_data`, or 
`include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools 
documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        
********************************************************************************

!!
  check.warn(importable)
/usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: 
Package 'pyramid_jinja2.tests.locale' is absent from the `packages` 
configuration.
!!

        
********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'pyramid_jinja2.tests.locale' 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 'pyramid_jinja2.tests.locale' 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 'pyramid_jinja2.tests.locale' to be distributed and 
are
        already explicitly excluding 'pyramid_jinja2.tests.locale' via
        `find_namespace_packages(...)/find_namespace` or 
`find_packages(...)/find`,
        you can try to use `exclude_package_data`, or 
`include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools 
documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        
********************************************************************************

!!
  check.warn(importable)
/usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: 
Package 'pyramid_jinja2.tests.locale.en.LC_MESSAGES' is absent from the 
`packages` configuration.
!!

        
********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'pyramid_jinja2.tests.locale.en.LC_MESSAGES' as an 
importable package[^1],
        but it is absent from setuptools' `packages` configuration.

        This leads to an ambiguous overall configuration. If you want to 
distribute this
        package, please make sure that 
'pyramid_jinja2.tests.locale.en.LC_MESSAGES' is explicitly added
        to the `packages` configuration field.

        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).

        You can read more about "package discovery" on setuptools documentation 
page:

        - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

        If you don't want 'pyramid_jinja2.tests.locale.en.LC_MESSAGES' to be 
distributed and are
        already explicitly excluding 
'pyramid_jinja2.tests.locale.en.LC_MESSAGES' via
        `find_namespace_packages(...)/find_namespace` or 
`find_packages(...)/find`,
        you can try to use `exclude_package_data`, or 
`include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools 
documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        
********************************************************************************

!!
  check.warn(importable)
/usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: 
Package 'pyramid_jinja2.tests.templates' is absent from the `packages` 
configuration.
!!

        
********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'pyramid_jinja2.tests.templates' as an importable 
package[^1],
        but it is absent from setuptools' `packages` configuration.

        This leads to an ambiguous overall configuration. If you want to 
distribute this
        package, please make sure that 'pyramid_jinja2.tests.templates' is 
explicitly added
        to the `packages` configuration field.

        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).

        You can read more about "package discovery" on setuptools documentation 
page:

        - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

        If you don't want 'pyramid_jinja2.tests.templates' to be distributed 
and are
        already explicitly excluding 'pyramid_jinja2.tests.templates' via
        `find_namespace_packages(...)/find_namespace` or 
`find_packages(...)/find`,
        you can try to use `exclude_package_data`, or 
`include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools 
documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        
********************************************************************************

!!
  check.warn(importable)
/usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: 
Package 'pyramid_jinja2.tests.templates.bar' is absent from the `packages` 
configuration.
!!

        
********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'pyramid_jinja2.tests.templates.bar' 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 'pyramid_jinja2.tests.templates.bar' 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 'pyramid_jinja2.tests.templates.bar' to be 
distributed and are
        already explicitly excluding 'pyramid_jinja2.tests.templates.bar' via
        `find_namespace_packages(...)/find_namespace` or 
`find_packages(...)/find`,
        you can try to use `exclude_package_data`, or 
`include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools 
documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        
********************************************************************************

!!
  check.warn(importable)
/usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: 
Package 'pyramid_jinja2.tests.templates.baz1' is absent from the `packages` 
configuration.
!!

        
********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'pyramid_jinja2.tests.templates.baz1' 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 'pyramid_jinja2.tests.templates.baz1' 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 'pyramid_jinja2.tests.templates.baz1' to be 
distributed and are
        already explicitly excluding 'pyramid_jinja2.tests.templates.baz1' via
        `find_namespace_packages(...)/find_namespace` or 
`find_packages(...)/find`,
        you can try to use `exclude_package_data`, or 
`include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools 
documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        
********************************************************************************

!!
  check.warn(importable)
/usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: 
Package 'pyramid_jinja2.tests.templates.baz2' is absent from the `packages` 
configuration.
!!

        
********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'pyramid_jinja2.tests.templates.baz2' 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 'pyramid_jinja2.tests.templates.baz2' 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 'pyramid_jinja2.tests.templates.baz2' to be 
distributed and are
        already explicitly excluding 'pyramid_jinja2.tests.templates.baz2' via
        `find_namespace_packages(...)/find_namespace` or 
`find_packages(...)/find`,
        you can try to use `exclude_package_data`, or 
`include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools 
documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        
********************************************************************************

!!
  check.warn(importable)
/usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: 
Package 'pyramid_jinja2.tests.templates.deep' is absent from the `packages` 
configuration.
!!

        
********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'pyramid_jinja2.tests.templates.deep' 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 'pyramid_jinja2.tests.templates.deep' 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 'pyramid_jinja2.tests.templates.deep' to be 
distributed and are
        already explicitly excluding 'pyramid_jinja2.tests.templates.deep' via
        `find_namespace_packages(...)/find_namespace` or 
`find_packages(...)/find`,
        you can try to use `exclude_package_data`, or 
`include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools 
documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        
********************************************************************************

!!
  check.warn(importable)
/usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: 
Package 'pyramid_jinja2.tests.templates.deep.sub' is absent from the `packages` 
configuration.
!!

        
********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'pyramid_jinja2.tests.templates.deep.sub' 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 
'pyramid_jinja2.tests.templates.deep.sub' 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 'pyramid_jinja2.tests.templates.deep.sub' to be 
distributed and are
        already explicitly excluding 'pyramid_jinja2.tests.templates.deep.sub' 
via
        `find_namespace_packages(...)/find_namespace` or 
`find_packages(...)/find`,
        you can try to use `exclude_package_data`, or 
`include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools 
documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        
********************************************************************************

!!
  check.warn(importable)
/usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: 
Package 'pyramid_jinja2.tests.templates.foo' is absent from the `packages` 
configuration.
!!

        
********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'pyramid_jinja2.tests.templates.foo' 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 'pyramid_jinja2.tests.templates.foo' 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 'pyramid_jinja2.tests.templates.foo' to be 
distributed and are
        already explicitly excluding 'pyramid_jinja2.tests.templates.foo' via
        `find_namespace_packages(...)/find_namespace` or 
`find_packages(...)/find`,
        you can try to use `exclude_package_data`, or 
`include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools 
documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        
********************************************************************************

!!
  check.warn(importable)
/usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: 
Package 'pyramid_jinja2.tests.templates.recursive' is absent from the 
`packages` configuration.
!!

        
********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'pyramid_jinja2.tests.templates.recursive' 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 
'pyramid_jinja2.tests.templates.recursive' 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 'pyramid_jinja2.tests.templates.recursive' to be 
distributed and are
        already explicitly excluding 'pyramid_jinja2.tests.templates.recursive' 
via
        `find_namespace_packages(...)/find_namespace` or 
`find_packages(...)/find`,
        you can try to use `exclude_package_data`, or 
`include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools 
documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        
********************************************************************************

!!
  check.warn(importable)
/usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: 
Package 'pyramid_jinja2.tests.templates.recursive.admin' is absent from the 
`packages` configuration.
!!

        
********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'pyramid_jinja2.tests.templates.recursive.admin' 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 
'pyramid_jinja2.tests.templates.recursive.admin' 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 'pyramid_jinja2.tests.templates.recursive.admin' to 
be distributed and are
        already explicitly excluding 
'pyramid_jinja2.tests.templates.recursive.admin' 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 pyramid_jinja2/configure.zcml -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2
creating 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/scaffolds/jinja2_starter
copying pyramid_jinja2/scaffolds/jinja2_starter/+dot+coveragerc_tmpl -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/scaffolds/jinja2_starter
copying pyramid_jinja2/scaffolds/jinja2_starter/CHANGES.txt_tmpl -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/scaffolds/jinja2_starter
copying pyramid_jinja2/scaffolds/jinja2_starter/MANIFEST.in_tmpl -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/scaffolds/jinja2_starter
copying pyramid_jinja2/scaffolds/jinja2_starter/README.txt_tmpl -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/scaffolds/jinja2_starter
copying pyramid_jinja2/scaffolds/jinja2_starter/development.ini_tmpl -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/scaffolds/jinja2_starter
copying pyramid_jinja2/scaffolds/jinja2_starter/message-extraction.ini -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/scaffolds/jinja2_starter
copying pyramid_jinja2/scaffolds/jinja2_starter/pytest.ini_tmpl -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/scaffolds/jinja2_starter
copying pyramid_jinja2/scaffolds/jinja2_starter/setup.cfg_tmpl -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/scaffolds/jinja2_starter
copying pyramid_jinja2/scaffolds/jinja2_starter/setup.py_tmpl -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/scaffolds/jinja2_starter
creating 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/scaffolds/jinja2_starter/+package+
copying pyramid_jinja2/scaffolds/jinja2_starter/+package+/__init__.py_tmpl -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/scaffolds/jinja2_starter/+package+
copying pyramid_jinja2/scaffolds/jinja2_starter/+package+/resources.py -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/scaffolds/jinja2_starter/+package+
copying pyramid_jinja2/scaffolds/jinja2_starter/+package+/tests.py_tmpl -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/scaffolds/jinja2_starter/+package+
copying pyramid_jinja2/scaffolds/jinja2_starter/+package+/views.py_tmpl -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/scaffolds/jinja2_starter/+package+
creating 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/scaffolds/jinja2_starter/+package+/locale
copying pyramid_jinja2/scaffolds/jinja2_starter/+package+/locale/+project+.pot -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/scaffolds/jinja2_starter/+package+/locale
creating 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/scaffolds/jinja2_starter/+package+/locale/de
creating 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/scaffolds/jinja2_starter/+package+/locale/de/LC_MESSAGES
copying pyramid_jinja2/scaffolds/jinja2_starter/+package+/locale/de/LC_MESSAGES/+project+.mo 
-> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/scaffolds/jinja2_starter/+package+/locale/de/LC_MESSAGES
copying pyramid_jinja2/scaffolds/jinja2_starter/+package+/locale/de/LC_MESSAGES/+project+.po 
-> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/scaffolds/jinja2_starter/+package+/locale/de/LC_MESSAGES
creating 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/scaffolds/jinja2_starter/+package+/locale/fr
creating 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/scaffolds/jinja2_starter/+package+/locale/fr/LC_MESSAGES
copying pyramid_jinja2/scaffolds/jinja2_starter/+package+/locale/fr/LC_MESSAGES/+project+.mo 
-> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/scaffolds/jinja2_starter/+package+/locale/fr/LC_MESSAGES
copying pyramid_jinja2/scaffolds/jinja2_starter/+package+/locale/fr/LC_MESSAGES/+project+.po 
-> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/scaffolds/jinja2_starter/+package+/locale/fr/LC_MESSAGES
creating 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/scaffolds/jinja2_starter/+package+/static
copying pyramid_jinja2/scaffolds/jinja2_starter/+package+/static/favicon.ico -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/scaffolds/jinja2_starter/+package+/static
copying pyramid_jinja2/scaffolds/jinja2_starter/+package+/static/pyramid-16x16.png -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/scaffolds/jinja2_starter/+package+/static
copying pyramid_jinja2/scaffolds/jinja2_starter/+package+/static/pyramid.png -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/scaffolds/jinja2_starter/+package+/static
copying pyramid_jinja2/scaffolds/jinja2_starter/+package+/static/theme.css -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/scaffolds/jinja2_starter/+package+/static
creating 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/scaffolds/jinja2_starter/+package+/templates
copying pyramid_jinja2/scaffolds/jinja2_starter/+package+/templates/mytemplate.jinja2_tmpl 
-> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/scaffolds/jinja2_starter/+package+/templates
copying pyramid_jinja2/tests/babel.cfg -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/tests
creating 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/tests/locale
copying pyramid_jinja2/tests/locale/messages.pot -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/tests/locale
creating 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/tests/locale/en
creating 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/tests/locale/en/LC_MESSAGES
copying pyramid_jinja2/tests/locale/en/LC_MESSAGES/messages.mo -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/tests/locale/en/LC_MESSAGES
copying pyramid_jinja2/tests/locale/en/LC_MESSAGES/messages.po -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/tests/locale/en/LC_MESSAGES
creating 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/tests/templates
copying pyramid_jinja2/tests/templates/extends.jinja2 -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/tests/templates
copying pyramid_jinja2/tests/templates/extends_missing.jinja2 -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/tests/templates
copying pyramid_jinja2/tests/templates/extends_relbase.jinja2 -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/tests/templates
copying pyramid_jinja2/tests/templates/extends_spec.jinja2 -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/tests/templates
copying pyramid_jinja2/tests/templates/helloworld.jinja2 -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/tests/templates
copying pyramid_jinja2/tests/templates/i18n.jinja2 -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/tests/templates
copying pyramid_jinja2/tests/templates/newstyle.jinja2 -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/tests/templates
copying pyramid_jinja2/tests/templates/tests_and_filters.jinja2 -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/tests/templates
creating 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/tests/templates/bar
copying pyramid_jinja2/tests/templates/bar/mytemplate.jinja2 -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/tests/templates/bar
creating 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/tests/templates/baz1
copying pyramid_jinja2/tests/templates/baz1/base.jinja2 -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/tests/templates/baz1
copying pyramid_jinja2/tests/templates/baz1/middle.jinja2 -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/tests/templates/baz1
copying pyramid_jinja2/tests/templates/baz1/mytemplate.jinja2 -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/tests/templates/baz1
creating 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/tests/templates/baz2
copying pyramid_jinja2/tests/templates/baz2/base.jinja2 -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/tests/templates/baz2
copying pyramid_jinja2/tests/templates/baz2/mytemplate.jinja2 -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/tests/templates/baz2
creating 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/tests/templates/deep
copying pyramid_jinja2/tests/templates/deep/base.jinja2 -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/tests/templates/deep
copying pyramid_jinja2/tests/templates/deep/forms.jinja2 -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/tests/templates/deep
copying pyramid_jinja2/tests/templates/deep/leaf.jinja2 -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/tests/templates/deep
creating 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/tests/templates/deep/sub
copying pyramid_jinja2/tests/templates/deep/sub/base.jinja2 -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/tests/templates/deep/sub
copying pyramid_jinja2/tests/templates/deep/sub/leaf.jinja2 -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/tests/templates/deep/sub
copying pyramid_jinja2/tests/templates/deep/sub/nav.jinja2 -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/tests/templates/deep/sub
creating 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/tests/templates/foo
copying pyramid_jinja2/tests/templates/foo/mytemplate.jinja2 -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/tests/templates/foo
creating 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/tests/templates/recursive
copying pyramid_jinja2/tests/templates/recursive/base.html -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/tests/templates/recursive
creating 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/tests/templates/recursive/admin
copying pyramid_jinja2/tests/templates/recursive/admin/base.html -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/tests/templates/recursive/admin
copying pyramid_jinja2/tests/templates/recursive/admin/index.html -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/tests/templates/recursive/admin
copying pyramid_jinja2/demo/helloworld.jinja2 -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/demo
creating 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/demo/locale
copying pyramid_jinja2/demo/locale/messages.pot -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/demo/locale
creating 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/demo/locale/fr
creating 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/demo/locale/fr/LC_MESSAGES
copying pyramid_jinja2/demo/locale/fr/LC_MESSAGES/messages.mo -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/demo/locale/fr/LC_MESSAGES
copying pyramid_jinja2/demo/locale/fr/LC_MESSAGES/messages.po -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/demo/locale/fr/LC_MESSAGES
   dh_auto_test -O--buildsystem=pybuild
dh_auto_test: warning: Compatibility levels before 10 are deprecated (level 9 
in use)
I: pybuild base:311: cd 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build; python3.12 -m 
unittest discover -v
test_app (pyramid_jinja2.demo.tests.DemoTests.test_app) ... ok
test_main (pyramid_jinja2.demo.tests.DemoTests.test_main) ... ok
test_root_view (pyramid_jinja2.demo.tests.DemoTests.test_root_view) ... ok
pyramid_jinja2.scaffolds (unittest.loader._FailedTest.pyramid_jinja2.scaffolds) 
... ERROR
test_it (pyramid_jinja2.tests.test_ext.GetTextWrapperTests.test_it) ... ok
test_custom_extension 
(pyramid_jinja2.tests.test_ext.TestExtensions.test_custom_extension) ... ok
test_i18n (pyramid_jinja2.tests.test_ext.TestExtensions.test_i18n) ... ok
test_filter 
(pyramid_jinja2.tests.test_filters.Test_filters_not_caching.test_filter) ... ok
test_filter_with_arguments 
(pyramid_jinja2.tests.test_filters.Test_filters_not_caching.test_filter_with_arguments)
 ... ok
test_filter (pyramid_jinja2.tests.test_filters.Test_model__filter.test_filter) 
... ok
test_filter_with_elements 
(pyramid_jinja2.tests.test_filters.Test_model__filter.test_filter_with_elements)
 ... ok
test_filter 
(pyramid_jinja2.tests.test_filters.Test_model_url_filter.test_filter) ... ok
test_filter_with_elements 
(pyramid_jinja2.tests.test_filters.Test_model_url_filter.test_filter_with_elements)
 ... ok
test_filter 
(pyramid_jinja2.tests.test_filters.Test_resource_url_filter.test_filter) ... ok
test_filter_with_elements 
(pyramid_jinja2.tests.test_filters.Test_resource_url_filter.test_filter_with_elements)
 ... ok
test_filter 
(pyramid_jinja2.tests.test_filters.Test_route_path_filter.test_filter) ... ok
test_filter_with_arguments 
(pyramid_jinja2.tests.test_filters.Test_route_path_filter.test_filter_with_arguments)
 ... ok
test_filter 
(pyramid_jinja2.tests.test_filters.Test_route_url_filter.test_filter) ... ok
test_filter_with_arguments 
(pyramid_jinja2.tests.test_filters.Test_route_url_filter.test_filter_with_arguments)
 ... ok
test_filter 
(pyramid_jinja2.tests.test_filters.Test_static_path_filter.test_filter) ... ok
test_filter_with_arguments 
(pyramid_jinja2.tests.test_filters.Test_static_path_filter.test_filter_with_arguments)
 ... ok
test_filter 
(pyramid_jinja2.tests.test_filters.Test_static_url_filter.test_filter) ... ok
test_filter_with_arguments 
(pyramid_jinja2.tests.test_filters.Test_static_url_filter.test_filter_with_arguments)
 ... ok
test_delay_init (pyramid_jinja2.tests.test_it.TestFileInfo.test_delay_init) ... 
ok
test_mtime (pyramid_jinja2.tests.test_it.TestFileInfo.test_mtime) ... ok
test_notfound (pyramid_jinja2.tests.test_it.TestFileInfo.test_notfound) ... ok
test_uptodate (pyramid_jinja2.tests.test_it.TestFileInfo.test_uptodate) ... ok
test_abs_tmpl_extends 
(pyramid_jinja2.tests.test_it.TestIntegrationDefaultSearchPath.test_abs_tmpl_extends)
 ... /usr/lib/python3/dist-packages/pyramid/asset.py:43: DeprecationWarning: 
Use of .. or absolute path in a resource path is not allowed and will raise 
exceptions in a future release.
  return pkg_resources.resource_filename(pname, filename)
ok
test_abs_tmpl_extends_missing 
(pyramid_jinja2.tests.test_it.TestIntegrationDefaultSearchPath.test_abs_tmpl_extends_missing)
 ... ok
test_asset_tmpl_deep_leaf 
(pyramid_jinja2.tests.test_it.TestIntegrationDefaultSearchPath.test_asset_tmpl_deep_leaf)
 ... ok
test_asset_tmpl_deep_sub_leaf 
(pyramid_jinja2.tests.test_it.TestIntegrationDefaultSearchPath.test_asset_tmpl_deep_sub_leaf)
 ... ok
test_asset_tmpl_extends 
(pyramid_jinja2.tests.test_it.TestIntegrationDefaultSearchPath.test_asset_tmpl_extends)
 ... ok
test_asset_tmpl_extends_spec 
(pyramid_jinja2.tests.test_it.TestIntegrationDefaultSearchPath.test_asset_tmpl_extends_spec)
 ... ok
test_asset_tmpl_helloworld 
(pyramid_jinja2.tests.test_it.TestIntegrationDefaultSearchPath.test_asset_tmpl_helloworld)
 ... ok
test_relative_tmpl_extends 
(pyramid_jinja2.tests.test_it.TestIntegrationDefaultSearchPath.test_relative_tmpl_extends)
 ... ok
test_relative_tmpl_extends_spec 
(pyramid_jinja2.tests.test_it.TestIntegrationDefaultSearchPath.test_relative_tmpl_extends_spec)
 ... ok
test_relative_tmpl_helloworld 
(pyramid_jinja2.tests.test_it.TestIntegrationDefaultSearchPath.test_relative_tmpl_helloworld)
 ... ok
test_render_reload_templates 
(pyramid_jinja2.tests.test_it.TestIntegrationReloading.test_render_reload_templates)
 ... ok
test_abs_tmpl_extends 
(pyramid_jinja2.tests.test_it.TestIntegrationWithSearchPath.test_abs_tmpl_extends)
 ... ok
test_abs_tmpl_extends_missing 
(pyramid_jinja2.tests.test_it.TestIntegrationWithSearchPath.test_abs_tmpl_extends_missing)
 ... ok
test_asset_tmpl_deep_leaf 
(pyramid_jinja2.tests.test_it.TestIntegrationWithSearchPath.test_asset_tmpl_deep_leaf)
 ... ok
test_asset_tmpl_deep_sub_leaf 
(pyramid_jinja2.tests.test_it.TestIntegrationWithSearchPath.test_asset_tmpl_deep_sub_leaf)
 ... ok
test_asset_tmpl_extends 
(pyramid_jinja2.tests.test_it.TestIntegrationWithSearchPath.test_asset_tmpl_extends)
 ... ok
test_asset_tmpl_extends_spec 
(pyramid_jinja2.tests.test_it.TestIntegrationWithSearchPath.test_asset_tmpl_extends_spec)
 ... ok
test_asset_tmpl_helloworld 
(pyramid_jinja2.tests.test_it.TestIntegrationWithSearchPath.test_asset_tmpl_helloworld)
 ... ok
test_caller_relative_tmpl_extends_relbase 
(pyramid_jinja2.tests.test_it.TestIntegrationWithSearchPath.test_caller_relative_tmpl_extends_relbase)
 ... ok
test_recursive_tmpl 
(pyramid_jinja2.tests.test_it.TestIntegrationWithSearchPath.test_recursive_tmpl)
 ... ok
test_relative_tmpl_extends 
(pyramid_jinja2.tests.test_it.TestIntegrationWithSearchPath.test_relative_tmpl_extends)
 ... ok
test_relative_tmpl_extends_spec 
(pyramid_jinja2.tests.test_it.TestIntegrationWithSearchPath.test_relative_tmpl_extends_spec)
 ... ok
test_relative_tmpl_helloworld 
(pyramid_jinja2.tests.test_it.TestIntegrationWithSearchPath.test_relative_tmpl_helloworld)
 ... ok
test_tmpl_extends 
(pyramid_jinja2.tests.test_it.TestIntegrationWithSearchPath.test_tmpl_extends) 
... ok
test_tmpl_extends_relbase 
(pyramid_jinja2.tests.test_it.TestIntegrationWithSearchPath.test_tmpl_extends_relbase)
 ... ok
test_tmpl_extends_spec 
(pyramid_jinja2.tests.test_it.TestIntegrationWithSearchPath.test_tmpl_extends_spec)
 ... ok
test_tmpl_helloworld 
(pyramid_jinja2.tests.test_it.TestIntegrationWithSearchPath.test_tmpl_helloworld)
 ... ok
test_it (pyramid_jinja2.tests.test_it.TestJinja2SearchPathIntegration.test_it) 
... ok
test_it_relative_to_template 
(pyramid_jinja2.tests.test_it.TestJinja2SearchPathIntegration.test_it_relative_to_template)
 ... ok
test_call (pyramid_jinja2.tests.test_it.TestJinja2TemplateRenderer.test_call) 
... ok
test_call_with_nondict_value 
(pyramid_jinja2.tests.test_it.TestJinja2TemplateRenderer.test_call_with_nondict_value)
 ... ok
test_call_with_system_context 
(pyramid_jinja2.tests.test_it.TestJinja2TemplateRenderer.test_call_with_system_context)
 ... ok
test_it (pyramid_jinja2.tests.test_it.TestNewstyle.test_it) ... ok
test_caller_package 
(pyramid_jinja2.tests.test_it.TestPackageFinder.test_caller_package) ... ok
test_get_source_from_path 
(pyramid_jinja2.tests.test_it.TestSmartAssetSpecLoader.test_get_source_from_path)
 ... ok
test_get_source_invalid_spec 
(pyramid_jinja2.tests.test_it.TestSmartAssetSpecLoader.test_get_source_invalid_spec)
 ... ok
test_get_source_legacy_spec 
(pyramid_jinja2.tests.test_it.TestSmartAssetSpecLoader.test_get_source_legacy_spec)
 ... ok
test_get_source_spec 
(pyramid_jinja2.tests.test_it.TestSmartAssetSpecLoader.test_get_source_spec) 
... ok
test_list_templates 
(pyramid_jinja2.tests.test_it.TestSmartAssetSpecLoader.test_list_templates) ... 
ok
test_alternate_renderer_extension 
(pyramid_jinja2.tests.test_it.Test_add_jinja2_extension.test_alternate_renderer_extension)
 ... ok
test_it (pyramid_jinja2.tests.test_it.Test_add_jinja2_extension.test_it) ... ok
test_it_relative_to_package 
(pyramid_jinja2.tests.test_it.Test_add_jinja2_searchpath.test_it_relative_to_package)
 ... ok
test_bccache_instance 
(pyramid_jinja2.tests.test_it.Test_bytecode_caching.test_bccache_instance) ... 
ok
test_default (pyramid_jinja2.tests.test_it.Test_bytecode_caching.test_default) 
... ok
test_default_bccache 
(pyramid_jinja2.tests.test_it.Test_bytecode_caching.test_default_bccache) ... ok
test_directory 
(pyramid_jinja2.tests.test_it.Test_bytecode_caching.test_directory) ... ok
test_pyramid_reload_templates 
(pyramid_jinja2.tests.test_it.Test_bytecode_caching.test_pyramid_reload_templates)
 ... ok
test_filter_and_test_and_global_works_in_render 
(pyramid_jinja2.tests.test_it.Test_filters_and_tests.test_filter_and_test_and_global_works_in_render)
 ... ok
test_set_multi_filters 
(pyramid_jinja2.tests.test_it.Test_filters_and_tests.test_set_multi_filters) 
... ok
test_set_multi_globals 
(pyramid_jinja2.tests.test_it.Test_filters_and_tests.test_set_multi_globals) 
... ok
test_set_multi_tests 
(pyramid_jinja2.tests.test_it.Test_filters_and_tests.test_set_multi_tests) ... 
ok
test_set_single_filter 
(pyramid_jinja2.tests.test_it.Test_filters_and_tests.test_set_single_filter) 
... ok
test_set_single_global 
(pyramid_jinja2.tests.test_it.Test_filters_and_tests.test_set_single_global) 
... ok
test_set_single_test 
(pyramid_jinja2.tests.test_it.Test_filters_and_tests.test_set_single_test) ... 
ok
test_it (pyramid_jinja2.tests.test_it.Test_get_jinja2_environment.test_it) ... 
ok
test_it (pyramid_jinja2.tests.test_it.Test_includeme.test_it) ... ok
test_composite_directories_path 
(pyramid_jinja2.tests.test_it.Test_renderer_factory.test_composite_directories_path)
 ... ok
test_no_directories 
(pyramid_jinja2.tests.test_it.Test_renderer_factory.test_no_directories) ... ok
test_no_environment 
(pyramid_jinja2.tests.test_it.Test_renderer_factory.test_no_environment) ... ok
test_require_default_renderer 
(pyramid_jinja2.tests.test_it.Test_renderer_factory.test_require_default_renderer)
 ... ok
test_with_environ 
(pyramid_jinja2.tests.test_it.Test_renderer_factory.test_with_environ) ... ok
test_with_filters_object 
(pyramid_jinja2.tests.test_it.Test_renderer_factory.test_with_filters_object) 
... ok
test_with_filters_string 
(pyramid_jinja2.tests.test_it.Test_renderer_factory.test_with_filters_string) 
... ok
test_debug_undefined 
(pyramid_jinja2.tests.test_settings.Test_parse_env_options_from_settings.test_debug_undefined)
 ... ok
test_default_undefined 
(pyramid_jinja2.tests.test_settings.Test_parse_env_options_from_settings.test_default_undefined)
 ... ok
test_finalize 
(pyramid_jinja2.tests.test_settings.Test_parse_env_options_from_settings.test_finalize)
 ... ok
test_most_settings 
(pyramid_jinja2.tests.test_settings.Test_parse_env_options_from_settings.test_most_settings)
 ... ok
test_override_gettext 
(pyramid_jinja2.tests.test_settings.Test_parse_env_options_from_settings.test_override_gettext)
 ... ok
test_strict_undefined 
(pyramid_jinja2.tests.test_settings.Test_parse_env_options_from_settings.test_strict_undefined)
 ... ok
test_debug_fallback 
(pyramid_jinja2.tests.test_settings.Test_parse_loader_options_from_settings.test_debug_fallback)
 ... ok
test_defaults 
(pyramid_jinja2.tests.test_settings.Test_parse_loader_options_from_settings.test_defaults)
 ... ok
test_options 
(pyramid_jinja2.tests.test_settings.Test_parse_loader_options_from_settings.test_options)
 ... ok
test_options_with_abspath 
(pyramid_jinja2.tests.test_settings.Test_parse_loader_options_from_settings.test_options_with_abspath)
 ... ok
test_options_with_relpath 
(pyramid_jinja2.tests.test_settings.Test_parse_loader_options_from_settings.test_options_with_relpath)
 ... ok
test_options_with_spec 
(pyramid_jinja2.tests.test_settings.Test_parse_loader_options_from_settings.test_options_with_spec)
 ... ok
test_it_with_dict 
(pyramid_jinja2.tests.test_settings.Test_parse_named_assetspecs.test_it_with_dict)
 ... ok
test_it_with_strings 
(pyramid_jinja2.tests.test_settings.Test_parse_named_assetspecs.test_it_with_strings)
 ... ok

======================================================================
ERROR: pyramid_jinja2.scaffolds 
(unittest.loader._FailedTest.pyramid_jinja2.scaffolds)
----------------------------------------------------------------------
ImportError: Failed to import test module: pyramid_jinja2.scaffolds
Traceback (most recent call last):
  File 
"/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/scaffolds/__init__.py",
 line 3, in <module>
    from pyramid.paster import paste_script_template_renderer
ImportError: cannot import name 'paste_script_template_renderer' from 
'pyramid.paster' (/usr/lib/python3/dist-packages/pyramid/paster.py)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File 
"/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/scaffolds/__init__.py",
 line 8, in <module>
    from pyramid.scaffolds import paste_script_template_renderer
ModuleNotFoundError: No module named 'pyramid.scaffolds'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/python3.12/unittest/loader.py", line 429, in _find_test_path
    package = self._get_module_from_name(name)
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/unittest/loader.py", line 339, in 
_get_module_from_name
    __import__(name)
  File 
"/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build/pyramid_jinja2/scaffolds/__init__.py",
 line 12, in <module>
    from pyramid.scaffolds import PyramidTemplate
ModuleNotFoundError: No module named 'pyramid.scaffolds'


----------------------------------------------------------------------
Ran 104 tests in 1.388s

FAILED (errors=1)
E: pybuild pybuild:389: test: plugin distutils failed with: exit code=1: cd 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pyramid-jinja2/build; python3.12 -m 
unittest discover -v
dh_auto_test: error: pybuild --test -i python{version} -p 3.12 returned exit 
code 13
make: *** [debian/rules:9: build] Error 255
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
--------------------------------------------------------------------------------

The above is just how the build ends and not necessarily the most relevant part.
If required, the full build log is available here:

https://people.debian.org/~sanvila/build-logs/202408/

About the archive rebuild: The build was made on virtual machines
of type m6a.large and r6a.large from AWS, using sbuild and a
reduced chroot with only build-essential packages.

If you could not reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.

If this is really a bug in one of the build-depends, please use
reassign and affects, so that this is still visible in the BTS web
page for this package.

Thanks.

Reply via email to