Arch Linux User Repository

Just FYI, no GNU / Linux package should need PyInstaller.

For me it is still failing

==> Validating source files with sha256sums...
    pyinstaller-6.10.0.tar.gz ... FAILED
    fortify-source-fix.diff ... Passed
==> ERROR: One or more files did not pass the validity check!
 -> error making: pyinstaller-exit status 1

I've disabled the tests.

@yochananmarqos

The build process runs the tests using the system python instance, and if user has >older PyInstaller installed there (in this case, 6.9.0), that ends up being used in the >tests.

Tested with archlinux:latest container:

building the 6.10.0 package in "clean" python environment works as expected building the 6.9.0 package first and installing it, then trying to build 6.10.0 package >fails as reported

Suggested solution:

I think the proper fix would be to change that pytest ... invocation in PKGBUILD into >python -m pytest ...; could be that other packages are using that (or are not running >tests at all).

See issue here: https://github.com/pyinstaller/pyinstaller/issues/8725

The checksum is outdated again

https://github.com/pyinstaller/pyinstaller/issues/8725

PYTHONPATH="$(pwd)" did work on my machine

@fam007e: I can't reproduce in a clean chroot. However, I've skipped the isolation tests for now.

Recent pyinstaller update showing this particular error:

================================================================================================================= FAILURES ==================================================================================================================
___________________________________________________________________________________________________________ test_nested_isolation ___________________________________________________________________________________________________________
[gw1] linux -- Python 3.12.4 /usr/bin/python

    def test_nested_isolation():
        def isolated_function():
            from PyInstaller import isolated
            import os

            # Get this process ID of this (isolated process)
            pid = os.getpid()

            @isolated.decorate
            def isolated_subfunction():
                import os
                return os.getpid()

            other_pid = isolated_subfunction()
            return pid, other_pid

        # Test the isolated.call invocation
        pid, other_pid = isolated.call(isolated_function)
>       assert pid == other_pid, f"Did not reuse the same isolated process: {pid} vs. {other_pid}"
E       AssertionError: Did not reuse the same isolated process: 217181 vs. 217184
E       assert 217181 == 217184

tests/unit/test_isolation.py:354: AssertionError
============================================================================================================= warnings summary ==============================================================================================================
../../../../../../../usr/lib/python3.12/site-packages/altgraph/__init__.py:142
../../../../../../../usr/lib/python3.12/site-packages/altgraph/__init__.py:142
../../../../../../../usr/lib/python3.12/site-packages/altgraph/__init__.py:142
  /usr/lib/python3.12/site-packages/altgraph/__init__.py:142: DeprecationWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html
    import pkg_resources

../../../../../../../usr/lib/python3.12/site-packages/pkg_resources/__init__.py:2832
../../../../../../../usr/lib/python3.12/site-packages/pkg_resources/__init__.py:2832
../../../../../../../usr/lib/python3.12/site-packages/pkg_resources/__init__.py:2832
  /usr/lib/python3.12/site-packages/pkg_resources/__init__.py:2832: DeprecationWarning: Deprecated call to `pkg_resources.declare_namespace('zope')`.
  Implementing implicit namespace packages (as specified in PEP 420) is preferred to `pkg_resources.declare_namespace`. See https://setuptools.pypa.io/en/latest/references/keywords.html#keyword-namespace-packages
    declare_namespace(pkg)

../../../../../../../usr/lib/python3.12/site-packages/setuptools/_distutils/ccompiler.py:850
../../../../../../../usr/lib/python3.12/site-packages/setuptools/_distutils/ccompiler.py:850
../../../../../../../usr/lib/python3.12/site-packages/setuptools/_distutils/ccompiler.py:850
  /usr/lib/python3.12/site-packages/setuptools/_distutils/ccompiler.py:850: DeprecationWarning: includes is deprecated
    warnings.warn("includes is deprecated", DeprecationWarning)

../../../../../../../usr/lib/python3.12/site-packages/_pytest/config/__init__.py:1437
../../../../../../../usr/lib/python3.12/site-packages/_pytest/config/__init__.py:1437
../../../../../../../usr/lib/python3.12/site-packages/_pytest/config/__init__.py:1437
  /usr/lib/python3.12/site-packages/_pytest/config/__init__.py:1437: PytestConfigWarning: Unknown config option: timeout

    self._warn_or_fail_if_strict(f"Unknown config option: {key}\n")

-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
========================================================================================================== short test summary info ==========================================================================================================
SKIPPED [2] tests/unit/test_hook_order.py:18: Skipped
FAILED tests/unit/test_isolation.py::test_nested_isolation - AssertionError: Did not reuse the same isolated process: 217181 vs. 217184
=============================================================================== 1 failed, 334 passed, 2 skipped, 11 xfailed, 12 warnings in 70.67s (0:01:10) ================================================================================
==> ERROR: A failure occurred in check().
    Aborting...
 -> error making: pyinstaller-exit status 4
 -> Failed to install the following packages. Manual intervention is required:
pyinstaller - exit status 4

The error I am encountering is maybe when trying to install pyinstaller AUR is due to a failed test case, specifically test_nested_isolation. This test is asserting that the same process ID should be reused during nested isolation, but the assertion failed because different process IDs were returned.

I can confirm that the latest patch has the correct sha256sums set. Clearing your build cache does indeed work -- sudo pacman -Scc does the trick as it clears your entire cache, and not just the packages that are no longer installed.

problems and errors again The cleaning of the cache does not help, Yay used almost the first time Have you hacked you? The only one writes and cleaning the cache does not remove this inscription. Pyinstaller (assembly files exist)

==> Assembly of Pyinstaller 6.9.0-1 package ==> receiving the source files ... -> Load Pyinstaller-6.9.0.tar.gz ... % Total % Receved % XFERD Average Speed ​​Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0-:-:--:-:-:-:-:-0 100 3874k 0 3874k 0 0 1844k 0-:-:-0:00:02-::-:-2819K -> Found Fortify-source-fix.diff ==> Attention: Spend of checking PGP subscriptions of the source files. ==> Source file checking using SHA256SUMS ... pyinstaller-6.9.0.tar.gz ... failure Fortify-source-fix.diff ... Ready ==> Error: The source files have not passed the integrity verification! -> Error loading sources: /home/wew/.cache/yay/pyinstaller CONTEXT: Exit Status 1

==> Checking the dependencies for launching ... ==> Checking for assembly ... ==> receiving the source files ... -> Found pyinstaller-6.9.0.tar.gz -> Found Fortify-source-fix.diff ==> Source file checking using SHA256SUMS ... pyinstaller-6.9.0.tar.gz ... failure Fortify-source-fix.diff ... Ready ==> Error: The source files have not passed the integrity verification! -> Build error: Pyinstaller-Exit Status 1 Checking dependencies ...