Package Details: geany-plugins-git 1.33.0.r46.gfe6cb3d0-1

Git Clone URL: https://aur.archlinux.org/geany-plugins-git.git (read-only)
Package Base: geany-plugins-git
Description: Various plugins for Geany
Upstream URL: https://plugins.geany.org/
Licenses: GPL
Conflicts: geany-plugins, geany-plugins-svn
Provides: geany-plugins
Submitter: xyproto
Maintainer: None
Last Packager: trizen
Votes: 35
Popularity: 0.000176
First Submitted: 2011-12-17 12:35
Last Updated: 2018-04-06 14:19

Required by (1)

Sources (1)

Latest Comments

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

Anonymous comment on 2011-12-17 07:07

geany-plugins project is now at https://github.com/geany/geany-plugins

eht16 commented on 2011-10-20 20:41

Weird. I don't see what's wrong.
Could you try to remove my name in the top of the wscript? Byte 0xc3 is the start of a "ö" in UTF-8 and position 96 is exactly that position in the file of the "ö" in my name. However, this is totally weird. The wscript file has the Python coding header specifying utf-8 as encoding and the file itself is UTF-8 encoded. So it should work.
Very confusing.

xyproto commented on 2011-10-20 18:49

eht16, the error only occurs with yaourt, not with makepkg or packer. My conclusion is that it's the combination of waf and yaourt that is the problem.

xyproto commented on 2011-10-18 23:05

Weird, now I get that error for both cases. Will examine the issue a bit more before concluding with anything.

xyproto commented on 2011-10-18 23:03

eht16, there, the error happened again (strangely only when updating the package, not when using makepkg). http://pastebin.com/70PbCs7M
Added make dependency on "waf" and changed the PKGBUILD to use the system wide waf, for now.

eht16 commented on 2011-10-18 22:37

Great. If it will break again, please tell us upstream. Thanks.

xyproto commented on 2011-10-18 22:32

eht16, I can't remember the exact reason, unfortunately, as I've delt with several other packages since then. I think it just didn't compile.
However, "./waf" works again now, so I'm updating the package to use that instead of depending on the "waf" package.

eht16 commented on 2011-10-18 17:19

trontonic, just for my curiosity, what problems exactly did you experience?

xyproto commented on 2011-10-12 09:14

Updated the package to use waf from the system instead of ./waf, which caused problems.

xyproto commented on 2011-10-12 08:40

eht16, you're right; thanks for noticing. Updating the package. namcap displays no errors.