=== panda is now known as Guest80225
=== fenris is now known as Guest83782
=== Guest83782 is now known as ejat
[07:04] <kees> halfie: right, PIE and BIND_NOW aren't default. (relro and all the rest are)
[07:04] <kees> however, the push in Debian has been to make PIE the default on amd64.
[07:05] <kees> so packages that have converted to dh(1) in debian are getting PIE on amd64.
[07:05] <kees> iirc
[07:05] <kees> I need to check :)
[07:06] <kees> halfie: ah, no, I lied. that's the plan, but not how it's implemented yet.
[07:06] <halfie> kees, thanks for the info!
[07:07] <halfie> selling PIE and BIND_NOW is hard
[07:09] <kees> see http://outflux.net/debian/hardening/
[07:10] <kees> and http://outflux.net/ubuntu/hardening/ (though I need to fix the release -- that's showing quantal)
[07:10] <kees> and note that're using different max values -- ubuntu has more packages, so the graph auto-scaled the y axis
[07:10] <kees> IMO, selling PIE is easy on amd64 :)
[07:11] <kees> and selling bind_now is easy too -- there's no measureable perf hit any more since the hashed symbol tables
[09:17] <ogra_> doko_, gcc did buiold fine for me over nicght, no issues
[09:18] <ogra_> (oh my ... /me needs coffee and type training)
[09:26] <infinity> ogra_: Yeah, it eventually completed on sigbin too.
[09:27] <ogra_> yeah, i noticed he had restartred a build in parallel to calling me
=== doko_ is now known as doko
[09:41] <doko> ogra_, \o/
[09:41] <ogra_> :)
[09:43] <doko> infinity, the armel and armhf gcc-4.8 builds on precise did fail, will retry these too
=== mbiebl_ is now known as mbiebl
[10:03] <doko> meh, the gcc-4.8 builds on precise did fail in dh_shlibdeps for the non-default multilib. will just ignore the return code then for precise
=== hrww is now known as hrw
[12:31] <jtaylor> doko: the python configure failures is not fixed without predepends :(
[12:37] <doko> jtaylor, ok, thanks. good to know
=== OdyX` is now known as OdyX
=== security is now known as fire
=== sikon is now known as lucidfox
[17:22] <IDWMaster> I'm not sure if this is the appropriate place for this discussion, but I was wondering if there are plans to implement multitouch support for Unity, and if so, how could I contribute?
[17:32] <penguin42> IDWMaster: I'm not sure; but there is a https://blueprints.launchpad.net/canonical-multitouch  section in lp, and there are a series of blueprints hung off that, including one or two unity ones
[17:33] <penguin42> IDWMaster: You might also try #ubntu-unity
[17:33] <penguin42>  add the missing u ^
[17:38] <IDWMaster> OK. Thanks
=== zykes-_ is now known as zykes
=== thomi_ is now known as thomi
[20:40] <infinity> apw / BenC: Want to rebase lowlatency and ppc against the shiniest raring upload?
=== Nisstyre-laptop is now known as Nisstyre