Package Details: python2-singledispatch 3.7.0-3

Git Clone URL: https://aur.archlinux.org/python2-singledispatch.git (read-only, click to copy)
Package Base: python2-singledispatch
Description: Backport of functools.singledispatch from Python 3.4
Upstream URL: https://pypi.org/project/singledispatch/3.7.0/
Licenses: MIT
Submitter: jelly
Maintainer: MarsSeed
Last Packager: MarsSeed
Votes: 3
Popularity: 0.121065
First Submitted: 2021-03-14 20:16 (UTC)
Last Updated: 2022-06-29 23:25 (UTC)

Latest Comments

1 2 Next › Last »

tpaniaki commented on 2022-06-30 07:03 (UTC)

@MarsSeed: I was trying to apply cmsigler's patch. 3.7.0-3 also solves the issue on my system. Thank you!

politas commented on 2022-06-30 03:58 (UTC)

Success!

==> Finished making: python2-singledispatch 3.7.0-3 (Thu 30 Jun 2022 13:56:39)

MarsSeed commented on 2022-06-29 23:27 (UTC)

Please check if the latest bump (3.7.0-3) fixes the setuptools-scm issue.

politas commented on 2022-06-29 22:46 (UTC)

I'm getting the same error as below:

LookupError: setuptools-scm was unable to detect version for u'/var/tmp/pamac-build-tangomyk/python2-singledispatch/src/singledispatch-3.7.0'.

Make sure you're either building from a fully intact git repository or PyPI tarballs. Most other sources (such as GitHub's tarballs, a git checkout without the .git folder) don't contain the necessary metadata and will not work.

For example, if you're using pip, instead of https://github.com/user/proj/archive/master.zip use git+https://github.com/user/proj.git#egg=proj
==> ERROR: A failure occurred in build().
    Aborting..

patlefort commented on 2022-06-29 20:50 (UTC)

Same problem for me. Proposed change:

diff --git a/PKGBUILD b/PKGBUILD
index 2d9c64e..07d09ff 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -14,12 +14,12 @@ depends=(
   'python2-six'
 )
 makedepends=('python2-setuptools')
-_tarname="${_name}-${pkgver}"
-source=("${_tarname}.tar.gz::https://github.com/jaraco/${_name}/archive/refs/tags/v${pkgver}.tar.gz")
-b2sums=('b488ebea8aeb1055fd91422d0ce7a91f321e3a0b9b99387f936fd1fd95a1016492baeabecfc0fd7ad8988a93c1054ff7681b8c4d0affa2d6114b90b6c8c58bdd')
+_dir="${_name}"
+source=("git+https://github.com/jaraco/${_name}.git#tag=v${pkgver}")
+md5sums=('SKIP')

 prepare() {
-  cd "${_tarname}"
+  cd "${_dir}"

   echo 'Changing hashbangs in *.py files to refer to python2'
   sed -e '1s|#![ ]*/usr/bin/python[^2]\?|#!/usr/bin/python2|' \
@@ -29,12 +29,12 @@ prepare() {
 }

 build() {
-  cd "${_tarname}"
+  cd "${_dir}"
   python2 setup.py build
 }

 package() {
-  cd "${_tarname}"
+  cd "${_dir}"
   python2 setup.py install --prefix='/usr' --root="${pkgdir}" --optimize=1 --skip-build

   install -Dm 644 'LICENSE' -t "${pkgdir}/usr/share/licenses/${pkgname}"

By pulling from the git repo, python setuptools is able to detect the version.

Cysioland commented on 2022-06-29 19:01 (UTC)

deleted the src/singledispatch-3.7.0/ folder and replaced it with a normal clone of https://github.com/jaraco/singledispatch, it worked

gnaggnoyil commented on 2022-06-29 18:02 (UTC)

The "setuptools-scm was unable to detect version" error I posted here before still exists with the newest PKGBUILD. Any ideas?

MarsSeed commented on 2022-06-29 15:01 (UTC)

It seems to me you didn't actually use the current PKGBUILD. Instead, you used this, which is not part of this repo.

MarsSeed commented on 2022-06-29 14:40 (UTC)

There is no patch in this package, afaik. Builds fine for me.

Could you maybe send the full build log, including the actual command you used to run the build?

tpaniaki commented on 2022-06-29 14:13 (UTC) (edited on 2022-06-29 14:13 (UTC) by tpaniaki)

patch: **** malformed patch at line 16:     451ec4ce7ba49b751fb5c097c34')

Any clue?