[10:39] <ricotz> mlankhorst, hello :)
[10:40] <ricotz> mlankhorst, was there are a reason not to sync libx11?
[10:42] <ricotz> while building it in a ppa it bails on xsltproc with "... Bus error ...", maybe you saw something like this yet? https://launchpadlibrarian.net/152123093/buildlog_ubuntu-saucy-i386.libx11_2%3A1.6.2%2Bgit20131002.18a5278b-0ubuntu0ricotz_FAILEDTOBUILD.txt.gz
[11:35] <tjaalton> a3/away
[11:35] <tjaalton> uh
[11:36] <mlankhorst> ricotz: yes that was exactly the reason
[11:36] <mlankhorst> bug in w3m somewhere or something, and i cant reproduce it..
[11:37] <tjaalton> well the current version fails just as well
[11:38] <tjaalton> doko poked me about it
[11:44] <ricotz> mlankhorst, i see, i thought so :\
[12:01] <tjaalton> anyone here with gen5 intel, arrandale/ironlake?
[12:01] <tjaalton> aka original 'core'
[12:10] <tjaalton> there are updates to w3m available in debian
[12:10] <tjaalton> -8 -> -11
[12:10] <tjaalton> a couple of patches to fix "potential segfault" too
[12:11] <tjaalton> i'll sync it
[14:25] <tjaalton> w3m update is now in proposed
[14:38] <mlankhorst> ok, syncpackaged libx11
[14:40] <tjaalton> cool
[14:41] <tjaalton> to the ppa first?
[14:41] <mlankhorst> naw
[14:43] <mlankhorst> we already know the only thing that broke libx11 was w3m, so if it's still broken some other solution has to be found anyway
[14:46] <tjaalton> right
[15:07] <mlankhorst> and building
[15:14] <mlankhorst> https://launchpadlibrarian.net/152143920/buildlog_ubuntu-saucy-i386.libx11_2%3A1.6.1-1_FAILEDTOBUILD.txt.gz
[15:14] <mlankhorst> looks like 0.5.3-11 is still borked
[15:14] <tjaalton> bah
[15:20] <mlankhorst> we should just upload libx11 and create it without the .txt documentation
[15:22] <mlankhorst> blah tomorrow, afk
[15:24] <ricotz> xorg-sgml-doctools could be synced too (doesnt solve the libx11 issue though)
[15:28] <tjaalton> the specs aren't getting built on debian?
[15:29] <tjaalton> then again I don't see why not
[15:29] <ricotz> tjaalton, yeah, according to the build log they aren't built there
[15:30] <tjaalton>  Functional specs building enabled:       no
[15:32] <ricotz> tjaalton, could be they are disabled due build-indep and the binary amd64 upload already contained the arch-all packages
[15:32] <tjaalton> probably
[15:32] <tjaalton> but it has no build logs available
[15:33] <ricotz> yes, because they were uploaded and built locally
[15:33] <tjaalton> bah :)
[15:34] <tjaalton> right, it runs debian/rules build-arch
[15:37] <tjaalton> oh well, it builds on sbuild just fine
[15:37] <ricotz> heh, it builds fine here too, but the builders dont like it ;)
[15:38] <ricotz> maybe even another ancient kernel issue
[15:39] <ricotz> https://bugzilla.samba.org/show_bug.cgi?id=9515
[16:10] <Sarvatt> https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/1163805 looks like it happens a lot..
[16:22] <ricotz> Sarvatt, hey :), how are you?
[19:02] <mdeslaur> I have a question about Mir
[19:02] <mdeslaur> I noticed that to support the Raspberry Pi, you need to add a backend to weston
[19:03] <mdeslaur> Since weston is just a reference compositor, does that mean that every compositor implementation would need to add hardware specific code?
[19:03] <mdeslaur> Does using Mir improve that? In other words, if a compositor uses Mir, does that get abstracted?
[19:04] <mdeslaur> perhaps I'm misunderstanding something fundamental?
[19:08] <tjaalton> mir only(?) has an egl backend, so the platform needs to have drivers to provide that
[19:10] <mdeslaur> oooohhh...they're not using egl on the raspberry pi...I see
[19:10] <tjaalton> gl(es)
[19:10] <tjaalton> sry
[19:10] <tjaalton> i've no idea if it can work
[19:10] <mdeslaur> er, yeah, gl
[19:15] <tjaalton> so for weston the default backend is drm, but rpi doesn't have open driver aiui
[19:15] <tjaalton> *drivers
[19:34] <mdeslaur> tjaalton: so it mir gains an alternate backend because it needs a funky driver for hardware support, and some compositor is using mir, it gets that backend support for free, right?
[19:38] <ricotz> tjaalton, btw, could you still sync libevdev?
[19:41] <tjaalton> ricotz: done, no guarantees
[19:41] <tjaalton> mdeslaur: well, it's the drivers that need to learn new tricks, not the way around I think
[19:41] <tjaalton> but yes, like you said aiui
[19:42] <tjaalton> also I think you'd get less vague answers on #ubuntu-mir :)
[19:42] <ricotz> tjaalton, thanks, it builds and doesnt have any rdepends yet, so i hope it gets accepted
[19:42] <mdeslaur> tjaalton: thanks!
[19:43] <ricotz> tjaalton, have you done it for xorg-sgml-doctools too yet?
[19:43] <tjaalton> nope
[19:44] <tjaalton> fixed
[19:44] <ricotz> thanks
[19:44] <tjaalton> mlankhorst: the package-status page still seems to not update the debian versions :/
[20:00] <mlankhorst> hm meh :/
[20:01] <mlankhorst> sorry, bike broke and I had to walk home for an hour instead
[20:01] <mlankhorst> not in the best of moods
[20:03] <tjaalton> take your time :)
[20:04] <mlankhorst> I wonder why it doesn't update debian versions though, afaict it can pull all the versions from launchpad just fine
[21:09] <mlankhorst> ok libx11 ubuntu1 uploaded, i killed the .txt files
[21:10] <tjaalton> looks like just retrying the build could've worked
[21:10] <mlankhorst> i bet we could kill libx11-doc without anyone caring
[21:10] <mlankhorst> well i did retry the build, no luck
[21:10] <tjaalton> ok
[21:10] <mlankhorst> and in the ppa i tried like 5 times
[21:11] <tjaalton> heh..
[21:11] <tjaalton> i blame the buildd
[21:12] <tjaalton> or did they all fail?
[21:12] <mlankhorst> only fails with w3m on i386
[21:12] <mlankhorst> unfortunately the -doc is only built on i386
[21:12] <tjaalton> hah
[21:12] <mlankhorst> but it's a arch all package
[21:12] <tjaalton> right