[13:55] <dholbach> hi guys
[13:55] <dholbach> does anybody of you have an idea what's wrong with bug 538718?
[13:55] <dholbach> I don't quite see where the "cannot find -lssl" comes from
[13:55] <dholbach> is that something that's wrong in python2.6 itself?
[13:59]  * persia looks
[14:32] <dholbach> persia: found anything?
[14:33] <persia> No, but that's because I'm slow
[14:44] <persia> dholbach: Sorry that took so long : as you noticed, it's a bit confusing :)
[14:46] <dholbach> adding libssl-dev to the build-deps seems to me to be a workaround
[14:47] <persia> And not one that is compatible with the code license (see my comment on the bug)
[14:48] <dholbach> python2.6-dev mentions -lssl in /usr/lib/python2.6/config/Setup.local but it's commented out in /usr/lib/python2.6/config/Setup
[14:49] <persia> dholbach: Right.  I'm fairly certain it's an issue with one of the hildon libraries.
[14:50] <persia> The history of hildon is fussy and annoying, and nobody really ever got it working in a distribution so far as I know (although Mer got very very close)
[14:50] <persia> And nobody in Ubuntu has been paying much attention to hildon for the past 9 months (at least).
[14:51] <persia> We almost were able to drop a Qt replacement with liquid this cycle, but upstream didn't want a release until post-FF.
[14:51] <dholbach> I noticed there's 0.1.0 of python-hildondesktop out now
[14:51] <persia> Could pull a new one, I suppose.
[14:52] <persia> I'm really not sure anyone would test it much though : none of the folks I've encountered who used it were willing to try to help maintain it except the Mer folk, and their work couldn't be merged because we never figured out how to handle gtk.
[14:53] <persia> I'm all for just dropping all the ubuntu-specific packages and ubuntu-specific patches from that entire collection, but don't want to do that until we have a replacement stack, just in case someone wants to hack on that stuff.