Package: src:esptool
Version: 4.7.0+dfsg-0.1
Severity: serious
Tags: ftbfs forky sid

Dear maintainer:

During a rebuild of all packages in unstable, this package failed to build.

Below you will find the last part of the build log (probably the most
relevant part, but not necessarily). If required, the full build log
is available here:

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

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 cannot 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:esptool, 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:317: python3.14 setup.py clean 
/usr/lib/python3/dist-packages/setuptools/dist.py:759: 
SetuptoolsDeprecationWarning: License classifiers are deprecated.
!!

        
********************************************************************************
        Please consider removing the following classifiers in favor of a SPDX 
license expression:

        License :: OSI Approved :: GNU General Public License v2 or later 
(GPLv2+)

        See 
https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license 
for details.
        
********************************************************************************


[... snipped ...]

        (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 'espefuse.efuse_defs' to be distributed and are
        already explicitly excluding 'espefuse.efuse_defs' 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 'esptool.targets.stub_flasher' is absent from the `packages` 
configuration.
!!

        
********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'esptool.targets.stub_flasher' 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 'esptool.targets.stub_flasher' 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 'esptool.targets.stub_flasher' to be distributed and 
are
        already explicitly excluding 'esptool.targets.stub_flasher' 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_esptool/build/espefuse/efuse_defs
copying espefuse/efuse_defs/esp32.yaml -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_esptool/build/espefuse/efuse_defs
copying espefuse/efuse_defs/esp32c2.yaml -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_esptool/build/espefuse/efuse_defs
copying espefuse/efuse_defs/esp32c3.yaml -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_esptool/build/espefuse/efuse_defs
copying espefuse/efuse_defs/esp32c6.yaml -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_esptool/build/espefuse/efuse_defs
copying espefuse/efuse_defs/esp32h2.yaml -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_esptool/build/espefuse/efuse_defs
copying espefuse/efuse_defs/esp32p4.yaml -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_esptool/build/espefuse/efuse_defs
copying espefuse/efuse_defs/esp32s2.yaml -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_esptool/build/espefuse/efuse_defs
copying espefuse/efuse_defs/esp32s3.yaml -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_esptool/build/espefuse/efuse_defs
creating 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_esptool/build/esptool/targets/stub_flasher
copying esptool/targets/stub_flasher/stub_flasher_32c2.json -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_esptool/build/esptool/targets/stub_flasher
copying esptool/targets/stub_flasher/stub_flasher_32c3.json -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_esptool/build/esptool/targets/stub_flasher
copying esptool/targets/stub_flasher/stub_flasher_32c6.json -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_esptool/build/esptool/targets/stub_flasher
copying esptool/targets/stub_flasher/stub_flasher_32c6beta.json -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_esptool/build/esptool/targets/stub_flasher
copying esptool/targets/stub_flasher/stub_flasher_32h2.json -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_esptool/build/esptool/targets/stub_flasher
copying esptool/targets/stub_flasher/stub_flasher_32h2beta1.json -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_esptool/build/esptool/targets/stub_flasher
copying esptool/targets/stub_flasher/stub_flasher_32h2beta2.json -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_esptool/build/esptool/targets/stub_flasher
copying esptool/targets/stub_flasher/stub_flasher_32p4.json -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_esptool/build/esptool/targets/stub_flasher
copying esptool/targets/stub_flasher/stub_flasher_8266.json -> 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_esptool/build/esptool/targets/stub_flasher
running build_scripts
creating build/scripts-3.13
copying and adjusting esptool.py -> build/scripts-3.13
copying and adjusting espefuse.py -> build/scripts-3.13
copying and adjusting espsecure.py -> build/scripts-3.13
copying and adjusting esp_rfc2217_server.py -> build/scripts-3.13
changing mode of build/scripts-3.13/esptool.py from 644 to 755
changing mode of build/scripts-3.13/espefuse.py from 644 to 755
changing mode of build/scripts-3.13/espsecure.py from 644 to 755
changing mode of build/scripts-3.13/esp_rfc2217_server.py from 644 to 755
   debian/rules execute_after_dh_auto_build
make[1]: Entering directory '/<<PKGBUILDDIR>>'
Traceback (most recent call last):
  File "/usr/bin/pybuild", line 604, in <module>
    main(cfg)
    ~~~~^^^^^
  File "/usr/bin/pybuild", line 40, in main
    from dhpython import build, PKG_PREFIX_MAP
ModuleNotFoundError: No module named 'dhpython'
Traceback (most recent call last):
  File "/usr/bin/pybuild", line 604, in <module>
    main(cfg)
    ~~~~^^^^^
  File "/usr/bin/pybuild", line 40, in main
    from dhpython import build, PKG_PREFIX_MAP
ModuleNotFoundError: No module named 'dhpython'
Traceback (most recent call last):
  File "/usr/bin/pybuild", line 604, in <module>
    main(cfg)
    ~~~~^^^^^
  File "/usr/bin/pybuild", line 40, in main
    from dhpython import build, PKG_PREFIX_MAP
ModuleNotFoundError: No module named 'dhpython'
Traceback (most recent call last):
  File "/usr/bin/pybuild", line 604, in <module>
    main(cfg)
    ~~~~^^^^^
  File "/usr/bin/pybuild", line 40, in main
    from dhpython import build, PKG_PREFIX_MAP
ModuleNotFoundError: No module named 'dhpython'
Traceback (most recent call last):
  File "/usr/bin/pybuild", line 604, in <module>
    main(cfg)
    ~~~~^^^^^
  File "/usr/bin/pybuild", line 40, in main
    from dhpython import build, PKG_PREFIX_MAP
ModuleNotFoundError: No module named 'dhpython'
Traceback (most recent call last):
  File "/usr/bin/pybuild", line 604, in <module>
    main(cfg)
    ~~~~^^^^^
  File "/usr/bin/pybuild", line 40, in main
    from dhpython import build, PKG_PREFIX_MAP
ModuleNotFoundError: No module named 'dhpython'
help2man --no-info --section 1 --include=debian/see-also \
  --source="Esptool.py 4.7.0" \
  -n "ESP8266 and ESP32 ROM Bootloader Utility" \
  --version-string="4.7.0" \
  build/scripts-3.14/esptool.py \
  | sed -e "s,esptool.py,esptool," \
  -e "s,Esptool.py,esptool.py," \
  -e "s,esptool v[0-9]\+.*,," \
  -e "s,\[.*\],," \
  -e "s,sage: esptool,sage: esptool [OPTION] COMMAND," \
  -e "s,positional arguments,command arguments," \
  -e "s,\.\.\.,," \
  -e "s,{load.*version},," \
  -e "s/{auto,.*}/{auto,CHIP}/" \
  -e "s/\\\fR {.*},/,/" \
  > esptool.1
Traceback (most recent call last):
  File "/usr/bin/pybuild", line 604, in <module>
    main(cfg)
    ~~~~^^^^^
  File "/usr/bin/pybuild", line 40, in main
    from dhpython import build, PKG_PREFIX_MAP
ModuleNotFoundError: No module named 'dhpython'
help2man: can't get `--help' info from build/scripts-3.14/esptool.py
Try `--no-discard-stderr' if option outputs to stderr
help2man --no-info --section 1 --include=debian/see-also \
  --source="Esptool.py 4.7.0" \
  -n "ESP32 Secure Boot & Flash Encryption tool" \
  --version-string="4.7.0" \
  build/scripts-3.14/espsecure.py \
  | sed -e "s,espsecure.py,espsecure," \
  -e "s,Esptool.py,esptool.py," \
  -e "s,espsecure v[0-9]\+.*,," \
  -e "s,\[.*\],," \
  -e "s,sage: espsecure,sage: espsecure [OPTION] COMMAND," \
  -e "s,positional arguments,command arguments," \
  -e "s,\.\.\.,," \
  -e "s,{digest.*data},," \
  > espsecure.1
help2man: can't get `--help' info from build/scripts-3.14/espsecure.py
Try `--no-discard-stderr' if option outputs to stderr
help2man --no-info --section 1 --include=debian/see-also \
  --source="Esptool.py 4.7.0" \
  -n "ESP32 efuse get/set tool" \
  --version-string="4.7.0" \
  build/scripts-3.14/espefuse.py \
  | sed -e "s,espefuse.py,espefuse," \
  -e "s,Esptool.py,esptool.py," \
  -e "s,espefuse v[0-9]\+.*,," \
  -e "s,\[.*\],," \
  -e "s,sage: espefuse,sage: espefuse [OPTION] COMMAND," \
  -e "s,positional arguments,command arguments," \
  -e "s,\.\.\.,," \
  -e "s,{dump.*_mac},," \
  -e "/^{burn_efuse,[^}]*}/d" \
  -e "s/{auto,.*}/{auto,CHIP}/" \
  > espefuse.1
help2man: can't get `--help' info from build/scripts-3.14/espefuse.py
Try `--no-discard-stderr' if option outputs to stderr
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
   dh_auto_test -O--buildsystem=pybuild
I: pybuild base:317: cd /<<PKGBUILDDIR>>/.pybuild/cpython3_3.14_esptool/build; 
python3.14 -m unittest discover -v 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.14_esptool/build/esptool/cmds.py:156: 
SyntaxWarning: 'return' in a 'finally' block
  return inst
espsecure.esp_hsm_sign (unittest.loader._FailedTest.espsecure.esp_hsm_sign) ... 
ERROR

======================================================================
ERROR: espsecure.esp_hsm_sign 
(unittest.loader._FailedTest.espsecure.esp_hsm_sign)
----------------------------------------------------------------------
ImportError: Failed to import test module: espsecure.esp_hsm_sign
Traceback (most recent call last):
  File 
"/<<PKGBUILDDIR>>/.pybuild/cpython3_3.14_esptool/build/espsecure/esp_hsm_sign/__init__.py",
 line 13, in <module>
    from .exceptions import handle_exceptions
  File 
"/<<PKGBUILDDIR>>/.pybuild/cpython3_3.14_esptool/build/espsecure/esp_hsm_sign/exceptions.py",
 line 5, in <module>
    from pkcs11.exceptions import (
    ...<11 lines>...
    )
ImportError: cannot import name 'AlreadyInitialized' from 'pkcs11.exceptions' 
(/usr/lib/python3/dist-packages/pkcs11/exceptions.py)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/python3.14/unittest/loader.py", line 460, in _find_test_path
    package = self._get_module_from_name(name)
  File "/usr/lib/python3.14/unittest/loader.py", line 367, in 
_get_module_from_name
    __import__(name)
    ~~~~~~~~~~^^^^^^
  File 
"/<<PKGBUILDDIR>>/.pybuild/cpython3_3.14_esptool/build/espsecure/esp_hsm_sign/__init__.py",
 line 15, in <module>
    raise ImportError(
    ...<3 lines>...
    )
ImportError: python-pkcs11 package is not installed. Please install it using 
the required packages with command: pip install 'esptool[hsm]'


----------------------------------------------------------------------
Ran 1 test in 0.000s

FAILED (errors=1)
E: pybuild pybuild:389: test: plugin distutils failed with: exit code=1: cd 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.14_esptool/build; python3.14 -m unittest 
discover -v 
I: pybuild base:317: cd /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_esptool/build; 
python3.13 -m unittest discover -v 
espsecure.esp_hsm_sign (unittest.loader._FailedTest.espsecure.esp_hsm_sign) ... 
ERROR

======================================================================
ERROR: espsecure.esp_hsm_sign 
(unittest.loader._FailedTest.espsecure.esp_hsm_sign)
----------------------------------------------------------------------
ImportError: Failed to import test module: espsecure.esp_hsm_sign
Traceback (most recent call last):
  File 
"/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_esptool/build/espsecure/esp_hsm_sign/__init__.py",
 line 13, in <module>
    from .exceptions import handle_exceptions
  File 
"/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_esptool/build/espsecure/esp_hsm_sign/exceptions.py",
 line 5, in <module>
    from pkcs11.exceptions import (
    ...<11 lines>...
    )
ImportError: cannot import name 'AlreadyInitialized' from 'pkcs11.exceptions' 
(/usr/lib/python3/dist-packages/pkcs11/exceptions.py)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/python3.13/unittest/loader.py", line 429, in _find_test_path
    package = self._get_module_from_name(name)
  File "/usr/lib/python3.13/unittest/loader.py", line 339, in 
_get_module_from_name
    __import__(name)
    ~~~~~~~~~~^^^^^^
  File 
"/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_esptool/build/espsecure/esp_hsm_sign/__init__.py",
 line 15, in <module>
    raise ImportError(
    ...<3 lines>...
    )
ImportError: python-pkcs11 package is not installed. Please install it using 
the required packages with command: pip install 'esptool[hsm]'


----------------------------------------------------------------------
Ran 1 test in 0.000s

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

Reply via email to