Arch Linux

Yeah, I think so. I noticed them when I fixed the pkgbuild for the changes in makepkg. My guess is that the memory leaks were always there, but at some point SWIG introduced a warning mechanism. Kiki itself hasn't been updated for *years*, which explains why the memory leaks haven't been fixed.

It works, thank you. :-)

Was this errors there before the upgrade?
"swig/python detected a memory leak of type 'KikiWall *', no destructor found." for example.

There you go; should be fixed :)

Yeah, that's to be expected. I'll try to set it up to work with the legacy python2 package when I have some time.

I've got a problem after python-upgrade (python3) => http://pastie.org/1233110

It turns out this package was broken by recent changes in makepkg. It should be working again now :)

Yeah, I'm seeing the same. It looks like bitrot: some dependency has move on and Kiki needs catching up. Looks like it could be either Python or GCC (again). I'll try to look into this if I can find time.

Doesn't build here http://pastie.org/1184791

I'm removing the out-of-date flag submitted by napa3um, as according to the Kiki Sourceforge page (http://sourceforge.net/projects/kiki), the current version is still 1.0.2. I do see 1.0.3 on the Kiki website (http://kiki.sourceforge.net/download/index.html), but I can only assume it's a Mac-only release.

If a new source release is made, please do re-flag :)

This was broken and orphaned when I wanted to build it, so I've done pretty much the bare minimum to get in to build again; there may be more that could be done to clean it up. If someone else would like to take the time, I'll happily step aside.