Bug#1027612: python-envisage: FTBFS: AssertionError: 0 != 3
On Tue, 10 Jan 2023, Scott Talbert wrote: On Tue, 10 Jan 2023, Andreas Tille wrote: Hi, I've updated Git to latest upstream version which does not show the reported error any more. However, there are two other issues I seem to need help for. I've worked around the initial issue[1] FileNotFoundError: [Errno 2] No such file or directory: 'python' with a patch[2] but this finally leads to a different error[3] subprocess.CalledProcessError: Command '['python3', 'setup.py', 'bdist_egg', '--dist-dir', '/tmp/tmp14hpgj33']' returned non-zero exit status 1. Any help would be welcome Andreas. [1] https://salsa.debian.org/python-team/packages/python-envisage/-/jobs/3774020 [2] https://salsa.debian.org/python-team/packages/python-envisage/-/blob/master/debian/patches/python3.patch [3] https://salsa.debian.org/python-team/packages/python-envisage/-/jobs/3774219 I'm looking into this. It appears that something is going horribly wrong with the test egg generation (which is now being done upstream automatically). Pushed a fix to salsa for that issue. It seems that some of the Debian build environment variables were interfering with the test egg generation process. Scott
Bug#1027612: python-envisage: FTBFS: AssertionError: 0 != 3
On Tue, 10 Jan 2023, Andreas Tille wrote: Hi, I've updated Git to latest upstream version which does not show the reported error any more. However, there are two other issues I seem to need help for. I've worked around the initial issue[1] FileNotFoundError: [Errno 2] No such file or directory: 'python' with a patch[2] but this finally leads to a different error[3] subprocess.CalledProcessError: Command '['python3', 'setup.py', 'bdist_egg', '--dist-dir', '/tmp/tmp14hpgj33']' returned non-zero exit status 1. Any help would be welcome Andreas. [1] https://salsa.debian.org/python-team/packages/python-envisage/-/jobs/3774020 [2] https://salsa.debian.org/python-team/packages/python-envisage/-/blob/master/debian/patches/python3.patch [3] https://salsa.debian.org/python-team/packages/python-envisage/-/jobs/3774219 I'm looking into this. It appears that something is going horribly wrong with the test egg generation (which is now being done upstream automatically). Scott
Bug#1027612: python-envisage: FTBFS: AssertionError: 0 != 3
Hi, I've updated Git to latest upstream version which does not show the reported error any more. However, there are two other issues I seem to need help for. I've worked around the initial issue[1] FileNotFoundError: [Errno 2] No such file or directory: 'python' with a patch[2] but this finally leads to a different error[3] subprocess.CalledProcessError: Command '['python3', 'setup.py', 'bdist_egg', '--dist-dir', '/tmp/tmp14hpgj33']' returned non-zero exit status 1. Any help would be welcome Andreas. [1] https://salsa.debian.org/python-team/packages/python-envisage/-/jobs/3774020 [2] https://salsa.debian.org/python-team/packages/python-envisage/-/blob/master/debian/patches/python3.patch [3] https://salsa.debian.org/python-team/packages/python-envisage/-/jobs/3774219 -- http://fam-tille.de
Bug#1027612: python-envisage: FTBFS: AssertionError: 0 != 3
Source: python-envisage
Version: 6.0.1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230101 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> # Inspired by
> https://src.fedoraproject.org/rpms/python-envisage/c/a20fa2cf6fe0eaf7604394a8b93bf8d3b48bc599?branch=rawhide
> # Prepare test eggs for Python 3.10+, the latest pre-generated eggs are for
> Python 3.9
> # See https://github.com/enthought/envisage/issues/396
> set -e ; \
> py3ver=3.10 ; \
> for dir in envisage/tests/*eggs/acme.*/ ; do cp -a $dir
> .pybuild/cpython3_${py3ver}_envisage/build/$dir ; done ; \
> for dir in
> .pybuild/cpython3_${py3ver}_envisage/build/envisage/tests/*eggs/acme.*/; do \
> ( cd $dir ; \
> python${py3ver} setup.py bdist_egg ; \
> mv -f dist/*.egg .. ; \
> ) ; \
> done
> /usr/lib/python3/dist-packages/setuptools/dist.py:285:
> SetuptoolsDeprecationWarning: The namespace_packages parameter is deprecated,
> consider using implicit namespaces instead (PEP 420).
> warnings.warn(msg, SetuptoolsDeprecationWarning)
> running bdist_egg
> running egg_info
> creating acme.bad.egg-info
> writing acme.bad.egg-info/PKG-INFO
> writing dependency_links to acme.bad.egg-info/dependency_links.txt
> writing entry points to acme.bad.egg-info/entry_points.txt
> writing namespace_packages to acme.bad.egg-info/namespace_packages.txt
> writing requirements to acme.bad.egg-info/requires.txt
> writing top-level names to acme.bad.egg-info/top_level.txt
> writing manifest file 'acme.bad.egg-info/SOURCES.txt'
> reading manifest file 'acme.bad.egg-info/SOURCES.txt'
> writing manifest file 'acme.bad.egg-info/SOURCES.txt'
> installing library code to build/bdist.linux-x86_64/egg
> /usr/lib/python3/dist-packages/setuptools/command/install.py:34:
> SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and
> pip and other standards-based tools.
> warnings.warn(
> running install_lib
> running build_py
> creating build
> creating build/lib
> creating build/lib/acme
> copying acme/__init__.py -> build/lib/acme
> creating build/lib/acme/bad
> copying acme/bad/__init__.py -> build/lib/acme/bad
> copying acme/bad/bad_plugin.py -> build/lib/acme/bad
> creating build/bdist.linux-x86_64
> creating build/bdist.linux-x86_64/egg
> creating build/bdist.linux-x86_64/egg/acme
> copying build/lib/acme/__init__.py -> build/bdist.linux-x86_64/egg/acme
> creating build/bdist.linux-x86_64/egg/acme/bad
> copying build/lib/acme/bad/__init__.py ->
> build/bdist.linux-x86_64/egg/acme/bad
> copying build/lib/acme/bad/bad_plugin.py ->
> build/bdist.linux-x86_64/egg/acme/bad
> byte-compiling build/bdist.linux-x86_64/egg/acme/__init__.py to
> __init__.cpython-310.pyc
> byte-compiling build/bdist.linux-x86_64/egg/acme/bad/__init__.py to
> __init__.cpython-310.pyc
> byte-compiling build/bdist.linux-x86_64/egg/acme/bad/bad_plugin.py to
> bad_plugin.cpython-310.pyc
> creating build/bdist.linux-x86_64/egg/EGG-INFO
> copying acme.bad.egg-info/PKG-INFO -> build/bdist.linux-x86_64/egg/EGG-INFO
> copying acme.bad.egg-info/SOURCES.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
> copying acme.bad.egg-info/dependency_links.txt ->
> build/bdist.linux-x86_64/egg/EGG-INFO
> copying acme.bad.egg-info/entry_points.txt ->
> build/bdist.linux-x86_64/egg/EGG-INFO
> copying acme.bad.egg-info/namespace_packages.txt ->
> build/bdist.linux-x86_64/egg/EGG-INFO
> copying acme.bad.egg-info/requires.txt ->
> build/bdist.linux-x86_64/egg/EGG-INFO
> copying acme.bad.egg-info/top_level.txt ->
> build/bdist.linux-x86_64/egg/EGG-INFO
> copying acme.bad.egg-info/zip-safe -> build/bdist.linux-x86_64/egg/EGG-INFO
> creating dist
> creating 'dist/acme.bad-0.1a1-py3.10.egg' and adding
> 'build/bdist.linux-x86_64/egg' to it
> removing 'build/bdist.linux-x86_64/egg' (and everything under it)
> /usr/lib/python3/dist-packages/setuptools/dist.py:285:
> SetuptoolsDeprecationWarning: The namespace_packages parameter is deprecated,
> consider using implicit namespaces instead (PEP 420).
> warnings.warn(msg, SetuptoolsDeprecationWarning)
> running bdist_egg
> running egg_info
> creating acme.bar.egg-info
> writing acme.bar.egg-info/PKG-INFO
> writing dependency_links to acme.bar.egg-info/dependency_links.txt
> writing entry points to acme.bar.egg-info/entry_points.txt
> writing namespace_packages to acme.bar.egg-info/namespace_packages.txt
> writing requirements to acme.bar.egg-info/requires.txt
> writing top-level names to acme.bar.egg-info/top_level.txt
> writing manifest file 'acme.bar.egg-info/SOURCES.txt'
> reading manifest file 'acme.bar.egg-info/SOURCES.txt'
> writing manifest file 'acme.bar.egg-info/SOURCES.txt'
> installing library code to build/bdist.linux-x86_64/egg
> /usr/lib/python3/dist-packages/setuptools/command/install.py:34:
> SetuptoolsDeprecationWarning: setup.py install is depr
