Your message dated Wed, 1 Oct 2025 18:11:20 +0100
with message-id <[email protected]>
and subject line Re: *diag FTBFS: pytest 8.4 rejects yield tests
has caused the Debian Bug report #1114236,
regarding nwdiag: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i
python{version} -p 3.13 returned exit code 13
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1114236: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1114236
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:nwdiag
Version: 3.0.0+dfsg-2
Severity: serious
Tags: ftbfs forky sid
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build.
Below you will find how the build ends (probably the most relevant part,
but not necessarily). If required, the full build log is available here:
https://people.debian.org/~sanvila/build-logs/202509/
About the archive rebuild: The build was made on virtual machines 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 add an affects on src:nwdiag, so that this is still
visible in the BTS web page for this package.
Thanks.
--------------------------------------------------------------------------------
[...]
debian/rules clean
dh clean --buildsystem=pybuild
dh_auto_clean -O--buildsystem=pybuild
I: pybuild base:311: python3.13 setup.py clean
/usr/lib/python3/dist-packages/setuptools/dist.py:599:
SetuptoolsDeprecationWarning: Invalid dash-separated key 'build-base' in
'build' (setup.cfg), please use the underscore name 'build_base' instead.
!!
********************************************************************************
Usage of dash-separated 'build-base' will not be supported in future
versions. Please use the underscore name 'build_base' instead.
By 2026-Mar-03, you need to update your project and remove deprecated
calls
or your builds will no longer be supported.
[... snipped ...]
############################
Python recognizes 'nwdiag.tests.diagrams.errors' 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 'nwdiag.tests.diagrams.errors' 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 'nwdiag.tests.diagrams.errors' to be distributed and
are
already explicitly excluding 'nwdiag.tests.diagrams.errors' 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:212: _Warning:
Package 'packetdiag.tests' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'packetdiag.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 'packetdiag.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 'packetdiag.tests' to be distributed and are
already explicitly excluding 'packetdiag.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/lib/python3/dist-packages/setuptools/command/build_py.py:212: _Warning:
Package 'packetdiag.tests.diagrams' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'packetdiag.tests.diagrams' 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 'packetdiag.tests.diagrams' 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 'packetdiag.tests.diagrams' to be distributed and are
already explicitly excluding 'packetdiag.tests.diagrams' 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:212: _Warning:
Package 'rackdiag.tests' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'rackdiag.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 'rackdiag.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 'rackdiag.tests' to be distributed and are
already explicitly excluding 'rackdiag.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/lib/python3/dist-packages/setuptools/command/build_py.py:212: _Warning:
Package 'rackdiag.tests.diagrams' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'rackdiag.tests.diagrams' 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 'rackdiag.tests.diagrams' 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 'rackdiag.tests.diagrams' to be distributed and are
already explicitly excluding 'rackdiag.tests.diagrams' via
`find_namespace_packages(...)/find_namespace` or
`find_packages(...)/find`,
you can try to use `exclude_package_data`, or
`include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools
documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_nwdiag/build/packetdiag/tests
copying src/packetdiag/tests/test_generate_diagram.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_nwdiag/build/packetdiag/tests
copying src/packetdiag/tests/test_rst_directives.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_nwdiag/build/packetdiag/tests
creating
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_nwdiag/build/packetdiag/tests/diagrams
copying src/packetdiag/tests/diagrams/oneliner.diag ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_nwdiag/build/packetdiag/tests/diagrams
copying src/packetdiag/tests/diagrams/oneliner_with_quoted.diag ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_nwdiag/build/packetdiag/tests/diagrams
copying src/packetdiag/tests/diagrams/oneliner_without_last_semicolon.diag ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_nwdiag/build/packetdiag/tests/diagrams
copying src/packetdiag/tests/diagrams/scale_direction.diag ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_nwdiag/build/packetdiag/tests/diagrams
copying src/packetdiag/tests/diagrams/scale_interval.diag ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_nwdiag/build/packetdiag/tests/diagrams
copying src/packetdiag/tests/diagrams/tcp.diag ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_nwdiag/build/packetdiag/tests/diagrams
copying src/packetdiag/tests/diagrams/tcp_2.diag ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_nwdiag/build/packetdiag/tests/diagrams
creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_nwdiag/build/rackdiag/tests
copying src/rackdiag/tests/test_builder.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_nwdiag/build/rackdiag/tests
copying src/rackdiag/tests/test_generate_diagram.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_nwdiag/build/rackdiag/tests
copying src/rackdiag/tests/test_rst_directives.py ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_nwdiag/build/rackdiag/tests
creating
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_nwdiag/build/rackdiag/tests/diagrams
copying src/rackdiag/tests/diagrams/autonumber.diag ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_nwdiag/build/rackdiag/tests/diagrams
copying src/rackdiag/tests/diagrams/multi_rackitem.diag ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_nwdiag/build/rackdiag/tests/diagrams
copying src/rackdiag/tests/diagrams/multi_racks.diag ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_nwdiag/build/rackdiag/tests/diagrams
copying src/rackdiag/tests/diagrams/oneliner.diag ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_nwdiag/build/rackdiag/tests/diagrams
copying src/rackdiag/tests/diagrams/oneliner_with_quoted.diag ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_nwdiag/build/rackdiag/tests/diagrams
copying src/rackdiag/tests/diagrams/oneliner_without_last_semicolon.diag ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_nwdiag/build/rackdiag/tests/diagrams
copying src/rackdiag/tests/diagrams/rack_height.diag ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_nwdiag/build/rackdiag/tests/diagrams
copying src/rackdiag/tests/diagrams/rack_height_for_multi_racks.diag ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_nwdiag/build/rackdiag/tests/diagrams
copying src/rackdiag/tests/diagrams/simple.diag ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_nwdiag/build/rackdiag/tests/diagrams
creating
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_nwdiag/build/nwdiag/tests/diagrams
copying src/nwdiag/tests/diagrams/autoexpand_node_width.diag ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_nwdiag/build/nwdiag/tests/diagrams
copying src/nwdiag/tests/diagrams/connected_networks.diag ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_nwdiag/build/nwdiag/tests/diagrams
copying src/nwdiag/tests/diagrams/connected_networks2.diag ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_nwdiag/build/nwdiag/tests/diagrams
copying src/nwdiag/tests/diagrams/connected_networks3.diag ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_nwdiag/build/nwdiag/tests/diagrams
copying src/nwdiag/tests/diagrams/diagram_attributes.diag ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_nwdiag/build/nwdiag/tests/diagrams
copying src/nwdiag/tests/diagrams/group_across_network.diag ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_nwdiag/build/nwdiag/tests/diagrams
copying src/nwdiag/tests/diagrams/group_and_peer_network.diag ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_nwdiag/build/nwdiag/tests/diagrams
copying src/nwdiag/tests/diagrams/group_inner_network.diag ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_nwdiag/build/nwdiag/tests/diagrams
copying src/nwdiag/tests/diagrams/group_network.diag ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_nwdiag/build/nwdiag/tests/diagrams
copying src/nwdiag/tests/diagrams/group_outer_network.diag ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_nwdiag/build/nwdiag/tests/diagrams
copying src/nwdiag/tests/diagrams/node_address_attribute.diag ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_nwdiag/build/nwdiag/tests/diagrams
copying src/nwdiag/tests/diagrams/node_attributes.diag ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_nwdiag/build/nwdiag/tests/diagrams
copying src/nwdiag/tests/diagrams/node_belongs_to_multiple_networks.diag ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_nwdiag/build/nwdiag/tests/diagrams
copying src/nwdiag/tests/diagrams/node_including_hyphen.diag ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_nwdiag/build/nwdiag/tests/diagrams
copying src/nwdiag/tests/diagrams/peer_network.diag ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_nwdiag/build/nwdiag/tests/diagrams
copying src/nwdiag/tests/diagrams/peer_network2.diag ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_nwdiag/build/nwdiag/tests/diagrams
copying src/nwdiag/tests/diagrams/peer_network3.diag ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_nwdiag/build/nwdiag/tests/diagrams
copying src/nwdiag/tests/diagrams/peer_network4.diag ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_nwdiag/build/nwdiag/tests/diagrams
copying src/nwdiag/tests/diagrams/peer_network5.diag ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_nwdiag/build/nwdiag/tests/diagrams
copying src/nwdiag/tests/diagrams/peer_network_branched.diag ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_nwdiag/build/nwdiag/tests/diagrams
copying src/nwdiag/tests/diagrams/same_peer_network.diag ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_nwdiag/build/nwdiag/tests/diagrams
copying src/nwdiag/tests/diagrams/single_network.diag ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_nwdiag/build/nwdiag/tests/diagrams
copying src/nwdiag/tests/diagrams/split_group.diag ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_nwdiag/build/nwdiag/tests/diagrams
copying src/nwdiag/tests/diagrams/two_networks.diag ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_nwdiag/build/nwdiag/tests/diagrams
creating
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_nwdiag/build/nwdiag/tests/diagrams/errors
copying src/nwdiag/tests/diagrams/errors/peer_network_in_same_node.diag ->
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_nwdiag/build/nwdiag/tests/diagrams/errors
debian/rules override_dh_auto_test
make[1]: Entering directory '/<<PKGBUILDDIR>>'
PYBUILD_TEST_ARGS=nwdiag/tests dh_auto_test -O--buildsystem=pybuild
I: pybuild base:311: cd /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_nwdiag/build;
python3.13 -m pytest nwdiag/tests
============================= test session starts ==============================
platform linux -- Python 3.13.7, pytest-8.4.1, pluggy-1.6.0
rootdir: /<<PKGBUILDDIR>>
plugins: typeguard-4.4.4
collected 66 items / 1 error
==================================== ERRORS ====================================
_ ERROR collecting
.pybuild/cpython3_3.13_nwdiag/build/nwdiag/tests/test_generate_diagram.py _
'yield' keyword is allowed in fixtures, but not in tests (testcase_generator)
=============================== warnings summary ===============================
../../../../../../usr/lib/python3/dist-packages/blockdiag/noderenderer/__init__.py:18
/usr/lib/python3/dist-packages/blockdiag/noderenderer/__init__.py:18:
DeprecationWarning: pkg_resources is deprecated as an API. See
https://setuptools.pypa.io/en/latest/pkg_resources.html
import pkg_resources
-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
=========================== short test summary info ============================
ERROR nwdiag/tests/test_generate_diagram.py - Failed: 'yield' keyword is allo...
!!!!!!!!!!!!!!!!!!!! Interrupted: 1 error during collection !!!!!!!!!!!!!!!!!!!!
========================= 1 warning, 1 error in 0.16s ==========================
E: pybuild pybuild:389: test: plugin distutils failed with: exit code=2: cd
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_nwdiag/build; python3.13 -m pytest
nwdiag/tests
dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.13
returned exit code 13
make[1]: *** [debian/rules:16: override_dh_auto_test] Error 25
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
make: *** [debian/rules:7: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
--------------------------------------------------------------------------------
--- End Message ---
--- Begin Message ---
Now fixed.
--- End Message ---
