Arch Linux User Repository

@C0rn3j The top level directory name of tarball is generated. It's more reliable.

Using python3 doesn't harm. (It was there in case somebody was still using Python 2 as default python.)

License file has been added. Also optdepends are added. namcap usually produces a lot of noise so I don't read it.

Please use ${pkver} instead of manually redefining it three times.

It's also not necessary to define python3 aspython` links to it.

Deps are missing, so is a correct licence, and there are some other things not in order, please run both the PKGBUILD and the resulting package through namcap.

yan12125 explicitly says to not bump pkgrel on rebuilds.

Anyway, you can't expect that all AUR maintainers bump their packages timely, so you'll still need to query and rebuild yourself. Something like pacman -Qo /usr/lib/python3.9 | paru -Sa --rebuild - will handle this rebuild. Bumping pkgrel at the wrong time is either too late or build a duplicate version, or both.

Packages from the official repo also bump pkgrel for new Python releases.

Binary package repositories are different than AUR.

Unless explicitly agreed by TUs, I'm not going to bump pkgrel for rebuilds.

I think you've misunderstood their request.

By longstanding policy, AUR users are firmly discouraged from committing and publishing PKGBUILD updates which merely update the pkgver= and/or pkgrel= variables in a PKGBUILD which contains a pkgver() function and builds from a git branch.

This is not a VCS package (it doesn't contain a pkgver() function, and isn't building from the tip of a git branch). Bumping pkgrel in this case will cause AUR helpers to rebuild the package against the new Python release (which makes a significant change to the contents of the package itself, not just fixing a typo). Packages from the official repo also bump pkgrel for new Python releases.

I'm not bumping pkgrel for a rebuild as TUs say. The AUR submission guidelines also says "Do not update those values if only minor changes to the PKGBUILD such as the correction of a typo are being published." Updating nothing other than pkgrel doesn't seem to be any more significant than "the correction of a typo".

@JuniorJPDJ You need to pacman -R python-telethon. There was issues with 1.17.4.

I've got error when trying to update to 1.17.5 today:

==> Starting build()...
Traceback (most recent call last):
  File "setup.py", line 22, in <module>
    from setuptools import find_packages, setup
  File "/usr/lib/python3.8/site-packages/setuptools/__init__.py", line 16, in <module>
    import setuptools.version
  File "/usr/lib/python3.8/site-packages/setuptools/version.py", line 1, in <module>
    import pkg_resources
  File "/usr/lib/python3.8/site-packages/pkg_resources/__init__.py", line 3239, in <module>
    def _initialize_master_working_set():
  File "/usr/lib/python3.8/site-packages/pkg_resources/__init__.py", line 3222, in _call_aside
    f(*args, **kwargs)
  File "/usr/lib/python3.8/site-packages/pkg_resources/__init__.py", line 3251, in _initialize_master_working_set
    working_set = WorkingSet._build_master()
  File "/usr/lib/python3.8/site-packages/pkg_resources/__init__.py", line 558, in _build_master
    ws = cls()
  File "/usr/lib/python3.8/site-packages/pkg_resources/__init__.py", line 551, in __init__
    self.add_entry(entry)
  File "/usr/lib/python3.8/site-packages/pkg_resources/__init__.py", line 607, in add_entry
    for dist in find_distributions(entry, True):
  File "/usr/lib/python3.8/site-packages/pkg_resources/__init__.py", line 2060, in find_on_path
    for dist in factory(fullpath):
  File "/usr/lib/python3.8/site-packages/pkg_resources/__init__.py", line 2125, in distributions_from_metadata
    yield Distribution.from_location(
  File "/usr/lib/python3.8/site-packages/pkg_resources/__init__.py", line 2585, in from_location
    return cls(
  File "/usr/lib/python3.8/site-packages/pkg_resources/__init__.py", line 2985, in _reload_version
    md_version = self._get_version()
  File "/usr/lib/python3.8/site-packages/pkg_resources/__init__.py", line 2767, in _get_version
    version = _version_from_file(lines)
  File "/usr/lib/python3.8/site-packages/pkg_resources/__init__.py", line 2551, in _version_from_file
    line = next(iter(version_lines), '')
  File "/usr/lib/python3.8/site-packages/pkg_resources/__init__.py", line 2762, in _get_metadata
    for line in self.get_metadata_lines(name):
  File "/usr/lib/python3.8/site-packages/pkg_resources/__init__.py", line 1415, in get_metadata_lines
    return yield_lines(self.get_metadata(name))
  File "/usr/lib/python3.8/site-packages/pkg_resources/__init__.py", line 1405, in get_metadata
    value = self._get(path)
  File "/usr/lib/python3.8/site-packages/pkg_resources/__init__.py", line 1609, in _get
    with open(path, 'rb') as stream:
PermissionError: [Errno 13] Permission denied: '/usr/lib/python3.8/site-packages/Telethon-1.17.4-py3.8.egg-info/PKG-INFO'

This package installs the tests dir in the destination python dir, this can conflict with many other packages. To fix it, add: local site_packages=$(python -c "import site; print(site.getsitepackages()[0])") rm -r "$pkgdir/$site_packages/tests/"

after executing install.

( see also https://wiki.archlinux.org/index.php/Python_package_guidelines#Test_directory_in_site-package )

Hi streetwalrus, sorry for the delay because I didn't received notification.

Issues 1 and 2 have been resolved and I will implement others soon.