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: 78
Popularity: 0.22
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 »

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

What Operating System are you using ?

thumbless commented on 2020-04-26 08:07 (UTC)

I just get error: missing package metadata When trying to install this.

eschwartz commented on 2020-04-21 15:12 (UTC)

Hmm, this could be because gitlab generated patches have the server's running git version embedded in the footer, and they've updated their server. Kind of silly... :(

If the current version of the patch is git added to the AUR repository it should continue to work with no modifications to the PKGBUILD, and be proof against this in the future.

spdyn1 commented on 2020-04-21 13:29 (UTC)

@fdo10 : in order to compile, you need to : sha512sum 4aaa48eb80c6802aec6d03e5695d2a0ff20e0fc2.patch if you decide to trust it, and edit the PKGBUILD file accordingly (replace the 2nd "sha512sums") Hope it helps. sp

fdo10 commented on 2020-04-21 12:02 (UTC)

I'm getting this error while trying to install:

user@hostname git clone https://aur.archlinux.org/pygtk.git

user@hostname ~/pygtk $ makepkg -si
==> Making package: pygtk 2.24.0-12 (di 21 apr 2020 13:21:20)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found pygtk-2.24.0.tar.bz2
  -> Found 4aaa48eb80c6802aec6d03e5695d2a0ff20e0fc2.patch
  -> Found python27.patch
  -> Found fix-leaks-of-pango-objects.patch
==> Validating source files with sha512sums...
    pygtk-2.24.0.tar.bz2 ... Passed
    4aaa48eb80c6802aec6d03e5695d2a0ff20e0fc2.patch ... FAILED
    python27.patch ... Passed
    fix-leaks-of-pango-objects.patch ... Passed
==> ERROR: One or more files did not pass the validity check!

Peach commented on 2020-04-19 09:55 (UTC)

FYI I've created a thread on the forums re the issue with pango-font.h https://bbs.archlinux.org/viewtopic.php?pid=1899239#p1899239

ragouel commented on 2020-04-19 06:33 (UTC)

OK, I reverted back the changes.

eschwartz commented on 2020-04-19 05:07 (UTC)

@Trillien,

Can you really not suggest downloading completely random, unchecksummed code during prepare()? Especially over http without even SSL to protect users against this utter trash malware vector?

config.guess and config.sub come from automake, and if you need to regenerate them, rerun autoreconf -fi.

Not that this is a problem anyway, unless you're on archlinuxarm. While it is of course permissible at the maintainer's discretion to support architectures other than x86_64, the current arch=() variable lists x86_64 only which indicates that yes, there may be problems on architectures the maintainer has not tested.

@ragouel,

I object most strongly to the use of wget in prepare for essentially any purposes whatsoever, and even moreso for code which is executed during build(), and demand in the most certain terms possible, this must be removed. Immediately.

If you wish to officially support ARM architectures for this package, please do so by adding the relevant architectures to the arch=() array, and testing that they work with any needed modifications such as autoreconf, not wget.

gok commented on 2020-04-18 09:41 (UTC) (edited on 2020-04-18 09:42 (UTC) by gok)

@ragouel: is there a specific reason why you switched the integrity checks from sha256sums to md5sums? If not, it would be great if you could switch back to sha256sums, because the MD5 algorithm isn't secure anymore (see 1), and upstream provides the reference checksums using SHA256 (see 2).

Thanks for taking the time to maintain this package :-)

ragouel commented on 2020-04-17 21:26 (UTC)

Done.