It's not possible to upload images to a Sone profile unless x11-libs/libXtst is installed because that library is used by the java.awt.Toolkit. Freenode #freenet: [15:13:24] <justusranvier> Got this trying to upload an image on Sone: http://pastebin.com/fBw6U9ia [15:14:26] <@operhiem1> Bombe: I like it! [15:14:45] Iso-Nisse [~isonisse@h-34-156.a238.priv.bahnhof.se] has joined #freenet [15:15:15] <@operhiem1> justusranvier: I don't suppose you anticipate having time to update FSNG for official Freemail v0.2? Shall I schedule a day this week to do it? [15:16:04] <@Bombe> justusranvier, hu. Are you running Freenet on a headless system? [15:16:34] <justusranvier> operhiem1: I have time; didn't realize there was a new version to update to. [15:17:04] <justusranvier> Bombe: Yes, Freenet is running in a qemu-kvm instance that contains no GUI. [15:17:43] <justusranvier> I got this one too: http://pastebin.com/fcZF9iVb [15:20:38] <@Bombe> Resolution [15:20:38] <@Bombe> Install whatever package provides "libXtst.so.6" (libXtst on RHEL 5) [15:20:47] <@Bombe> I guess you need some parts of X11 after all. :) [15:22:53] <justusranvier> x11-libs/libXtst on Gentoo. [15:24:24] <@operhiem1> Bombe: That's odd that Sone requires X11. Any idea why? [15:24:52] <@Bombe> operhiem1, yes. I use the image parsing code that’s somewhere tied into java.awt.Toolkit. [15:24:58] <@Bombe> Why they did that, I don’t know. [15:26:26] illutionist [~illutioni@202.65.158.21] has joined #freenet [15:26:45] <@Bombe> I could use some other library to parse images but I would put that far down on my prioritized list. :)
The Sone plugin is not provided by freenet and freenet itself does not need libXtst, so there is no reason to add a dependeny to freenet. An ebuild for the Sone plugin should obviously have this dependency included, but that is out of scope of this bug. Feel free to create an ebuild for Sone with the dependency on libXtst and then open a new bug for the addition of that ebuild to our main tree.
Never mind, I've given up on using ebuilds to manage Freenet entirely. It's far too frequent to end up with a system that can't connect to the rest of Freenet because the ebuild is out of date compared to the minimum required version on the network. Using ebuilds to manage Freenet plugins seperately, if that's even architecturally possible at all, is pure madness. I was just hoping that maybe we could save other users some time and hassle by adding a nice convienience feature, but apparently that's not welcome.
