Package Base Details: python-cheetah3

Git Clone URL: (read-only, click to copy)
Submitter: alexbrinister
Maintainer: alexbrinister (fryfrog)
Last Packager: fryfrog
Votes: 7
Popularity: 2.18
First Submitted: 2018-07-30 02:37
Last Updated: 2020-05-19 15:31

Latest Comments

1 2 Next › Last »

fryfrog commented on 2020-02-10 03:29

Looks like I goofed up and had setuptools as a depends instead of makedepends. Should be sorted now.

Orionis commented on 2020-02-09 22:16

That was odd. When updating from 3.2.4-2 to 3.2.4-3 yay didn't install setuptools, so I ran into an error updating. After installing setuptools manually the update went fine.

fryfrog commented on 2020-01-27 03:51

@alexbrinister, I've got the updated PKGBUILD all worked up and submitted a merge request for my python2-cheetah3. I'll push it once they approve, usually takes a day or seven. :)

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?