Since 0.15, gajim has an inbuilt plugin system. The Gentoo ebuild passes --enable-site-packages to the configure script. That results in gajim's python scripts being installed to /usr/lib64/python2.?/site-packages/gajim instead of /usr/share/gajim/src. That's perfectly fine. But this argument also installs the plugins contained in the gajim tarball (it's just one plugin atm, the "plugin installer", but it's important as it's the only way to fetch plugins from inside gajim) to /usr/lib64/python2.?/site-packages/gajim instead of /usr/share/gajim/plugins. This leads to the plugin not being found, as gajim still searches for it in /usr/share/gajim/plugins. This issue was already reported to upstream and should be fixed in the next release. But until then, we can simply patch the configure script with the attached patch. Reproducible: Always
Created attachment 308195 [details, diff] proposed patch for gajim's configure script
Fix by upstream: https://trac.gajim.org/changeset/2aaa268a776f8bf0e90bcaa13da82b59b390a6de They fix it in configure.ac instead of configure, but for us it's easier to patch configure directly.
+*gajim-0.15-r1 (23 Apr 2012) + + 23 Apr 2012; Justin Lecher <jlec@gentoo.org> +gajim-0.15-r1.ebuild, + +files/gajim-0.15-plugin.patch: + Backport upstream commit 13748 to fix plugin dir location, #411253 +
