Arch Linux User Repository

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 ...

If you meet the problem with checksum, you can remove your local cache and then rebuild the package. I did this and solved this problem.

@fyoory: I've just corrected the checksum for the second time. It was correct each time until it wasn't. I don't know if upstream is doing something or there's an issue with GitHub.

Rude comments are not welcome here.

When oh when will the maintainer get off their tail and fix the checksums? Its like the first thing you should check, if you have not got a clue.

The checksum is wrong again, the right one for pyinstaller-v6.8.0.tar.gz is 8e1d14eb185ff37793f32fe96f6881abb0952f4c0f27f8bf7237f542ae149554, not 28baf23b178e581ea3ca5002bd33c974a7044bd9d5ec0a4cc6464fee7d912eeb

By the way, big thanks for reducing the number of tests run

Sorry if this is inappropriate, but I was unable to download this package for the good part of an hour because no mirrors were working.

error: failed retrieving file 'libimagequant-4.3.0-1-x86_64.pkg.tar.zst' from mirror.osbeck.com : The requested URL returned error: 404
error: failed retrieving file 'libimagequant-4.3.0-1-x86_64.pkg.tar.zst' from mirror.ufscar.br : The requested URL returned error: 404
error: failed retrieving file 'libimagequant-4.3.0-1-x86_64.pkg.tar.zst.sig' from arch.kurdy.org : The requested URL returned error: 404
warning: failed to retrieve some files
error: failed to commit transaction (failed to retrieve some files)
Errors occurred, no packages were upgraded.

Same here:

Building pyinstaller...
==> Making package: pyinstaller 6.6.0-2 (Thu 18 Apr 2024 06:55:25 BST)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found pyinstaller-6.6.0.tar.gz
  -> Found fortify-source-fix.diff
==> Validating source files with sha256sums...
    pyinstaller-6.6.0.tar.gz ... FAILED
    fortify-source-fix.diff ... Passed
==> ERROR: One or more files did not pass the validity check!
Failed to build pyinstaller

It looks to me that the checksum for the source is wrong:

$ makepkg --geninteg 
==> Retrieving sources...
  -> Found pyinstaller-6.6.0.tar.gz
  -> Found fortify-source-fix.diff
==> Generating checksums for source files...
sha256sums=('443974ecda7addbd5ab22a62875fa9e371cdaef451f7630f3a4020b3a1fe0000'
            '46f7cfd082570a3f4c138a868e55dc39deacccbff602ce7e70d033236566fa1b')

but the current checksum is: a37fa49f49232b27d87238e3c7b48b98e688d256c2667c2368d5366193d04775