Package Base Details: python-cheetah3

Git Clone URL: (read-only, click to copy)
Submitter: alexbrinister
Maintainer: alexbrinister (fryfrog)
Last Packager: fryfrog
Votes: 7
Popularity: 0.28
First Submitted: 2018-07-30 02:37
Last Updated: 2021-04-24 18:16

Latest Comments

« First ‹ Previous 1 2 3 Next › Last »

alexbrinister commented on 2020-01-27 03:39

@fryfrog A split package is probably the way to go. I will make you a co-maintainer so you can make the changes for split package.

fryfrog commented on 2020-01-01 21:15

Hey @alexbrinster, it looks like python2-cheetah was removed from community. I needed it for sabnzbd, so I've created a python2-cheetah3. In that one, I named the binaries cheetah2 and such, so if you wanted you could flip yours to not put a 3 in them.

Also, if you wanted to make this a python/python2 split package... that'd be cool too and I could merge mine into yours. Happy to do it myself, if you like. Can submit a patch or you can make me co-maintainer or whatever.

stardiviner commented on 2019-11-22 11:01

@alexbrinister Thanks, I use command deactive to disable user virtualenv. It is installed correctly. Thanks very much. :)

alexbrinister commented on 2019-10-17 22:29

@stardiviner I have reproduced your issue. Are you in a virtualenv when you build the package? This would mess up the directory into which python installs the package. If you build the package in a virtualenv, the package files will end up being installed into your home directory (or wherever you have your virtualenv set to) by pacman. I have tested this with another python package from the AUR and the files are indeed installed in the virtualenv. Since most packages do not need to change names of binaries, there is no issue, other than the package files being installed in the virtualenv as opposed to the default location (/usr).

alexbrinister commented on 2019-10-16 21:16

@stardiviner have you tried building in a chroot as described in

stardiviner commented on 2019-10-16 10:09

@alexbrinister After deleted ~/.cache/yay/ . I still got this error. Weird.

alexbrinister commented on 2019-10-09 02:30

@stardiviner Strange, I have built this package using aurutils (in and out of chroot), yay, and straight makepkg and I do not get this error. Have you tried removing the package directory in ~\.cache\yay and reinstalling?

stardiviner commented on 2019-10-01 09:59

I got following error when installing:

running install_scripts creating /home/stardiviner/.cache/yay/python-cheetah3/pkg/python-cheetah3/home/stardiviner/.virtualenvs/python3.7/bin copying build/scripts-3.7/cheetah-analyze -> /home/stardiviner/.cache/yay/python-cheetah3/pkg/python-cheetah3/home/stardiviner/.virtualenvs/python3.7/bin copying build/scripts-3.7/cheetah -> /home/stardiviner/.cache/yay/python-cheetah3/pkg/python-cheetah3/home/stardiviner/.virtualenvs/python3.7/bin copying build/scripts-3.7/cheetah-compile -> /home/stardiviner/.cache/yay/python-cheetah3/pkg/python-cheetah3/home/stardiviner/.virtualenvs/python3.7/bin changing mode of /home/stardiviner/.cache/yay/python-cheetah3/pkg/python-cheetah3/home/stardiviner/.virtualenvs/python3.7/bin/cheetah-analyze to 755 changing mode of /home/stardiviner/.cache/yay/python-cheetah3/pkg/python-cheetah3/home/stardiviner/.virtualenvs/python3.7/bin/cheetah to 755 changing mode of /home/stardiviner/.cache/yay/python-cheetah3/pkg/python-cheetah3/home/stardiviner/.virtualenvs/python3.7/bin/cheetah-compile to 755 mv: cannot stat '/home/stardiviner/.cache/yay/python-cheetah3/pkg/python-cheetah3/usr/bin/cheetah': No such file or directory ==> ERROR: A failure occurred in package(). Aborting... Error making: python-cheetah3

alexbrinister commented on 2019-08-11 18:23

@jamespharvey20 thank you for the patch, I have updated to the latest version and renamed the binaries to prevent clashing with python2-cheetah.

jamespharvey20 commented on 2019-08-11 02:05

Patch below, for your consideration, with these changes:

  • Update from 3.1.0 to 3.2.3
  • Add depends of python-setuptools, required by the new version (which requires itself requires python so no longer needs to be listed
  • Removes provides/conflicts of cheetah3 and python-cheetah3, which I believe are based off community/python2-cheetah, but as far as I can tell, cheetah3 and python-cheetah3 never existed
  • Removes usage of msg and msg2, which although are taken from community/python2-cheetah, their usage is discouraged
  • Simplifies the installation of LICENSE, since already in the directory being specified
  • Renames the 3 binaries, per suggestion of @bitfehler to prevent conflict with community/python2-cheetah


diff --git a/PKGBUILD b/PKGBUILD
index [`cf460e7`]( 100644
@@ -2,18 +2,16 @@

 pkgdesc="A Python 3-powered template engine and code generator"
-provides=('cheetah3' 'python-cheetah3')
-conflicts=('cheetah3' 'python-cheetah3')

 build() {
   cd "${srcdir}/${_name}-${pkgver}"
@@ -21,10 +19,12 @@ build() {

 package() {
-  msg "Install..."
   cd "${srcdir}/${_name}-${pkgver}"
   python install --root="${pkgdir}" --optimize=1 --skip-build
+  install -Dm644 LICENSE "${pkgdir}/usr/share/licenses/${pkgname}/LICENSE"

-  msg2 "Install copyright resources in /usr/share/licenses/${pkgname}..."
-  install -Dm644 "${srcdir}/${_name}-${pkgver}/LICENSE" "${pkgdir}/usr/share/licenses/${pkgname}/LICENSE"
+  # Avoid conflict with python2-cheetah
+  for name in cheetah cheetah-analyze cheetah-compile; do
+    mv "${pkgdir}/usr/bin/${name}"{,3}
+  done