Package Details: pygtk 2.24.0-12

Git Clone URL: (read-only, click to copy)
Package Base: pygtk
Description: Python bindings for the GTK widget set
Upstream URL:
Keywords: GTK Python widget
Licenses: LGPL
Submitter: arojas
Maintainer: ragouel
Last Packager: ragouel
Votes: 57
Popularity: 3.64
First Submitted: 2020-03-29 19:09
Last Updated: 2021-01-16 00:35

Required by (314)

Sources (4)

Latest Comments

1 2 3 4 5 6 Next › Last »

ragouel commented on 2021-01-16 00:37

Apologies for the delay. I added support for aarch64 thanks to gameslayer's suggestion.

gameslayer commented on 2021-01-09 11:47

Works on Arm64 (Raspberry pi 4)

Just edited the pkgbuild file and added aarch64 to the arch and to fix the compiling issue with pygtk I added --build=unknown-unknown-linux to the end of ./configure to make it work.

grumpymatt commented on 2020-12-25 21:41

I was able to compile on a raspberry pi 4 using;a=blob_plain;f=config.guess;hb=HEAD and modifying the pkgbuild to allow ARM architecture.

ragouel commented on 2020-11-11 21:19

If anyone has an ARM device and is willing to help me test this on it, let me know so I can provide support for ARM architecture as well.

eschwartz commented on 2020-08-16 21:50

This was already discussed around

The ONLY correct solution for updating config.guess is re-running autoreconf -fi. However, the arch=('x86_64') in the PKGBUILD does suggest it isn't tested on ARM, and it may or may not work or need additional workarounds to compile on such architectures. It is up to the maintainer to decide whether to add/test this support.

lxgr commented on 2020-08-16 21:42

This package causes problems compiling on archlinux arm aarch64, because the config.guess in the sourcecode is way out of date. This can be worked around by including a file called 'config.guess' with this;a=blob_plain;f=config.guess;hb=HEAD content and copying it to the builddir. I did this by adding 'config.guess' to source, 'Skip' to sha256sums and 'cp ../config.guess ./' at the end of prepare in the PKGBUILD.

daniel_shub commented on 2020-05-19 00:29

@zman0900 I think the point is that it is unlikely that someone maliciously replaces the patches but does not modify the PKGBUILD since they are downloaded as a bundle. Silent corruption should be caught when you clone the git repository, but is probably technically a possibility. Ideally the patches and the PKGBUILD would be signed, but in practice, the Arch way is buyer beware. You should be reading the PKGBUILD and associated files and make sure you know what they are doing.

zman0900 commented on 2020-05-18 23:58

How so? Without them, file integrity is not checked. Patches could be silently corrupted or maliciously replaced and it would go unnoticed.

ragouel commented on 2020-05-18 23:43

@zman0900 because they are redundant.

zman0900 commented on 2020-05-18 17:05

Why are checksums skipped on the patch files?