Package Details: pygtk 2.24.0-14

Git Clone URL: https://aur.archlinux.org/pygtk.git (read-only, click to copy)
Package Base: pygtk
Description: Python bindings for the GTK widget set
Upstream URL: https://wiki.gnome.org/Projects/PyGTK
Keywords: GTK Python widget
Licenses: LGPL-2.1-or-later
Submitter: arojas
Maintainer: creyon
Last Packager: creyon
Votes: 76
Popularity: 1.19
First Submitted: 2020-03-29 19:09 (UTC)
Last Updated: 2024-06-02 15:27 (UTC)

Pinned Comments

ragouel commented on 2022-06-11 23:26 (UTC) (edited on 2022-06-12 19:54 (UTC) by ragouel)

From official GNOME docs:

"Attention: PyGTK 2.24 will be the last release in the PyGTK series and will support the full GTK-2-24 API. PyGTK should not be used for new projects and existing PyGTK applications are recommended to be ported to PyGObject. See here for more information."

https://wiki.gnome.org/Projects/PyGTK/WhatsNew224

Please stop asking me to update this package. I only "keep" it, so that it is not messed with by others, as some older applications still rely on it to function.

Thank you.

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 Next › Last »

grumpymatt commented on 2020-12-25 21:41 (UTC)

I was able to compile on a raspberry pi 4 using http://git.savannah.gnu.org/gitweb/?p=config.git;a=blob_plain;f=config.guess;hb=HEAD and modifying the pkgbuild to allow ARM architecture.

ragouel commented on 2020-11-11 21:19 (UTC) (edited on 2021-01-16 00:38 (UTC) by ragouel)

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 (UTC)

This was already discussed around https://aur.archlinux.org/packages/pygtk/?PP=250#comment-740369

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 (UTC)

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 http://git.savannah.gnu.org/gitweb/?p=config.git;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 (UTC)

@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 (UTC)

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 (UTC)

@zman0900 because they are redundant.

zman0900 commented on 2020-05-18 17:05 (UTC)

Why are checksums skipped on the patch files?

eschwartz commented on 2020-04-26 08:37 (UTC)

What's the actual command you ran?

ragouel commented on 2020-04-26 08:14 (UTC)

What Operating System are you using ?

« First ‹ Previous 1 2 3 4 5 6 7 8 9 Next › Last »