Package Details: gnome-perl 1.045-8

Git Clone URL: (read-only, click to copy)
Package Base: gnome-perl
Description: Perl bindings for libgnome
Upstream URL:
Licenses: LGPL
Submitter: PhotonX
Maintainer: PhotonX
Last Packager: PhotonX
Votes: 29
Popularity: 0.66
First Submitted: 2017-01-25 19:09
Last Updated: 2018-03-03 22:07

Latest Comments

« First ‹ Previous 1 2 3 Next › Last »

PhotonX commented on 2017-06-13 09:00

@philanecros: There is no explicit dependency on perl<5.25, the package builds with perl 5.26 as well. Please post your error output if it doesn't work for you.

PhotonX commented on 2017-06-07 05:21

@wagn3r: This is a problem with gnomecanvas-perl which needs a rebuild after yesterday's perl update. But I already bumped gnomecanvas-perl to force a rebuild. If for some reason this didn't work for you, please reinstall gnomecanvas-perl manually.

wagn3r commented on 2017-06-07 04:57

Error with "xs/GnomeCanvas.c: loadable library and perl binaries are mismatched (got handshake key 0xdb80080, needed 0xde00080)"

PhotonX commented on 2017-03-02 10:34

Thanks, I did already some time ago! :) In case you reacted to my comment in the pacaur page, I was referring to the problems which have been reported here by kodiak, charlesarch and shahinism:

Spyhawk commented on 2017-03-02 10:23

@PhotonX: There is no support from provider in the AUR RPC, so helpers can't workaround this issue. You'll have to include the explicit gnome-vfs-nosmb dependency.

PhotonX commented on 2017-02-02 22:55

@Spyhawk: Another issue here: People cannot install gnome-vfs-perl due to the gnome-vfs dependency. gnome-vfs has been kicked from the repos alongside other gnome2 packages but is provided by the gnome-vfs-nosmb AUR package: However, pacaur (and other AUR helpers) users cannot install gnome-vfs-perl because it does not recognize that gnome-vfs is provided by gnome-vfs-nosmb. Is there anything which can be done on your side or shall I flout it and put gnome-vfs to the AUR? Thanks for looking into it in advance!

Spyhawk commented on 2017-01-27 18:11

@PhotonX: I just realized that this issue is already fixed in the latest pacaur-git code. I'll release a new stable version when I can (probably a few days), but that issue is, at worst, only temporary.

PhotonX commented on 2017-01-27 17:41

@Spyhawk: I already raised this question once: People basically told me that AUR packages breaking with perl updates are fine and users will get the idea of rebuilding them themselves. Not really satisfying, but maybe this is the state of the art today...

Spyhawk commented on 2017-01-27 17:21

@PhotonX: Yes, Perl modules are indeed fragile. Let me know if you find a way to solve this issue (I subscribed to new comments for this package). This is an issue that should imho be fixed in the PKGBUILD, but in the worst case I might be able to add a workaround in pacaur code. Although that is clearly not the preferred way of solving issue, and it would only fix it for pacaur users.

PhotonX commented on 2017-01-27 16:46

Well, I wouldn't call it solved, leaving the dependency list without checking the perl version seems like a very bad idea since perl updates frequently break other software if not rebuilt against the new version. But I don't see a better solution yet. Maybe this is why AUR packages of perl based software lead to the software silently breaking after perl updates...

Thanks for the clarification concerning pacaur and other AUR helpers btw!