Arch Linux User Repository

It is suspicious that the setup wants to access a file in the root directory. I did a rebuild with the the current PKGBUILD and it works like a charm with makepkg.
Also of note is, that yay cached those files. Maybe this cache causes the failure. But only a speculation. Please try it with makepkg and check for modifications in the PKGBUILD.

Any ideas on how to solve the error below?

==> Starting build()...
Traceback (most recent call last):
  File "/home/jack/.cache/yay/patool/src/patool-upstream-1.12/setup.py", line 26, in <module>
    from setuptools import setup
  File "/usr/lib/python3.10/site-packages/setuptools/__init__.py", line 16, in <module>
    import setuptools.version
  File "/usr/lib/python3.10/site-packages/setuptools/version.py", line 1, in <module>
    import pkg_resources
  File "/usr/lib/python3.10/site-packages/pkg_resources/__init__.py", line 3243, in <module>
    def _initialize_master_working_set():
  File "/usr/lib/python3.10/site-packages/pkg_resources/__init__.py", line 3226, in _call_aside
    f(*args, **kwargs)
  File "/usr/lib/python3.10/site-packages/pkg_resources/__init__.py", line 3255, in _initialize_master_working_set
    working_set = WorkingSet._build_master()
  File "/usr/lib/python3.10/site-packages/pkg_resources/__init__.py", line 559, in _build_master
    ws = cls()
  File "/usr/lib/python3.10/site-packages/pkg_resources/__init__.py", line 552, in __init__
    self.add_entry(entry)
  File "/usr/lib/python3.10/site-packages/pkg_resources/__init__.py", line 608, in add_entry
    for dist in find_distributions(entry, True):
  File "/usr/lib/python3.10/site-packages/pkg_resources/__init__.py", line 2063, in find_on_path
    for dist in factory(fullpath):
  File "/usr/lib/python3.10/site-packages/pkg_resources/__init__.py", line 2128, in distributions_from_metadata
    yield Distribution.from_location(
  File "/usr/lib/python3.10/site-packages/pkg_resources/__init__.py", line 2591, in from_location
    )._reload_version()
  File "/usr/lib/python3.10/site-packages/pkg_resources/__init__.py", line 2989, in _reload_version
    md_version = self._get_version()
  File "/usr/lib/python3.10/site-packages/pkg_resources/__init__.py", line 2770, in _get_version
    version = _version_from_file(lines)
  File "/usr/lib/python3.10/site-packages/pkg_resources/__init__.py", line 2554, in _version_from_file
    line = next(iter(version_lines), '')
  File "/usr/lib/python3.10/site-packages/pkg_resources/__init__.py", line 2765, in _get_metadata
    for line in self.get_metadata_lines(name):
  File "/usr/lib/python3.10/site-packages/pkg_resources/__init__.py", line 1417, in get_metadata_lines
    return yield_lines(self.get_metadata(name))
  File "/usr/lib/python3.10/site-packages/pkg_resources/__init__.py", line 1407, in get_metadata
    value = self._get(path)
  File "/usr/lib/python3.10/site-packages/pkg_resources/__init__.py", line 1611, in _get
    with open(path, 'rb') as stream:
PermissionError: [Errno 13] Permission denied: '/usr/lib/python3.10/site-packages/google_api_core-2.3.2-py3.10.egg-info/PKG-INFO'
==> ERROR: A failure occurred in build().
    Aborting...
 -> error making: patool

I'm not a fan of bumping in those cases. Without a bump, the program fails for users, but they know afterwards they need to rebuild it. If pkgrel is bumped there still could be the issue, that someone still runs python3.8 and after an upgrade still has a broken package.
Either way has its quirks.

Can you bump the package number so it prompts helpers to rebuild this package? It needs to be rebuilt for python 3.9 to work again.

Thanks for the research bmwinger. If it is solved by switching the location of the source, then I will do this change.

The contents of /usr/lib/python3.6/site-packages/patool-1.12-py3.6.egg-info/ seem to be lacking read permissions, 640 rather than 644. This causes all python imports to fail

It looks like the issue here is that the archive on pypi already contains a patool.egg-info directory with 640 permissions. Removing this before building the package, or using the archive from github (which doesn't come with patool.egg-info already built) will create the patool.egg-info directory with the correct permissions.

Error importing module named 'setuptools'.

Traceback (most recent call last):
  File "setup.py", line 26, in <module>
    from setuptools import setup
ImportError: No module named setuptools
==> ERROR: A failure occurred in package_patool-py2().
    Aborting...
Error making: patool

Since ever, or since the change where I added --optimize=1? If the first, then it should probably be brought to upstream

The contents of /usr/lib/python3.6/site-packages/patool-1.12-py3.6.egg-info/ seem to be lacking read permissions, 640 rather than 644. This causes all python imports to fail

@jschmoe: It seems yaourt cannot handle packages that are from the same PKGBuild and conflicting each other. This is a fault in yaourt. The issue should be avoided if you remove the conflicts line (aka both packages should be build). The naming and setting of variables itself is correct (see Split-PKGBuilds. The pkgbase var can just hold the main and only name. In pkgname you can declare all the names of all the packages you want to create with the PKGBuild) The conclicts line is somewhat necessary because the binary is installed with both python versions under patool and I didn't want to rename one of the binaries (Could be misleading if patool2 or whatever). And it doesn't make sense to have both python versions installed.