[08:26] <ppisati> brb
[08:58] <apw> hallyn, i assume you rocked on it and things are good
[10:27] <tjaalton> trying to build a useful dbgsym package from a custom branch, but I always end up with stripped modules
[10:39] <apw> tjaalton, as in you don't get a .ddeb package at all ?
[10:43] <tjaalton> I do, but the .ko's are stripped
[10:43] <apw> as ddebs are disabled by defualt when not building on a buildd, full_build=true to get the buildd experience
[10:43] <tjaalton> ok, I tried AUTOBUILD=1
[10:44] <apw> tjaalton, which release are you testing
[10:44] <tjaalton> building on raring, drm-intel-nightly
[10:44] <tjaalton> plus the packaging from.. dunno
[10:44] <tjaalton> "fresh"
[10:44] <tjaalton> got it from Sarvatt :)
[10:44] <apw> is that you trying to rebuild the mainline builds ... oh ok
[10:44] <tjaalton> yeah
[10:44] <apw> well i'd try full_build in case, and in parallel i'll build saucy tip and check
[10:46] <apw> make sure it is not systemic, people tend to not notice the ddebs have gone to hell until months after release
[10:46] <tjaalton> those should end up in the parent dir
[10:46] <apw> i mean if the contents have gone to hell
[10:47] <apw> we had totally empty ones for some months :)
[10:47] <apw> back in lucid
[10:47] <tjaalton> ah
[10:47] <apw> i'll ask gomeisa to do the do on it and have a peek inside for a change :)
[10:48] <tjaalton> would it be possible to create ddebs for mainline builds too?
[10:48] <tjaalton> I know they are huge..
[10:49] <apw> they are massive, they are 10x the size of the originals
[10:49] <tjaalton> yup
[10:49] <apw> technically it is possible i am sure, but ... woh, i am not sure we have the space to keep them
[10:49] <apw> very long, and we keep the mainline builds 'in perpetuity' in theory
[10:49] <tjaalton> well, if I can get this working probably not needed
[10:49] <tjaalton> i mean, if it's easy to recreate one
[10:50] <apw> it should be, i recreated a lost one from the archive and it worked with the binaries from that release
[10:51] <tjaalton> alright
[10:52] <apw> tjaalton, i'll get back to you when i have built this one
[10:53] <apw> tjaalton, also if it works i might be able to checkout the actual tree used for that build and make a ddeb for it, if it is a mainline you are testing
[10:53] <apw> tjaalton, in principle if you are only caring for the dirty upstream trees, the ones which are frankly likely to blow up and eat your lunch, we might be able to enable them for those only
[10:54] <apw> anyhow ... build is in progress so i'll let you know what i find
[10:54] <tjaalton> heh, right
[10:54] <tjaalton> I'm building too, race you to it :)
[10:55] <apw> tjaalton, hopefully my builder is bigger than your builder, else i will hjave to sulk
[10:55] <apw> tjaalton, though obviouly you are building what you wnat, and mine is only a build for the master tip to make sure we haven't knobbed it
[10:55] <tjaalton> just my ivb desktop
[10:56] <tjaalton> but full build, maybe I'm missing some bdeps for the tools or such
[10:56]  * apw curses henrix who is wrecking my race :)
[10:56] <henrix> apw: ?
[10:56] <apw> nothing, just joshing you
[10:56] <henrix> heh
[10:56] <apw> henrix, making gomeisa go slow
[10:57] <henrix> apw: ah! i can cancel my job if you have something urgent ;)
[10:57] <henrix> apw: just doing routine builds on 3.5
[10:57] <apw> henrix, nothing urgent at all ...
[10:57] <henrix> apw: :)
[10:57] <apw> henrix, and i have like 4 other machines if it was
[10:57] <apw> and 'slow' means 12m instead of 8m not life ending
[10:58]  * henrix goes back to UEFI backports fun
[10:58] <apw> henrix, yeah it looks like you have some real untestable backports to do there, good luck with that crap
[11:00] <henrix> apw: i have the backport already... i'm just trying to make sure i won't have people hitting me with bricks in a few weeks :)
[11:01] <apw> henrix, literally :)
[11:28] <apw> tjaalton, ok my .ddeb has come out at 47M so i suspect something has broke
[11:29] <tjaalton> ha :)
[11:29]  * apw will poke it and let you know
[11:29] <tjaalton> thx
[11:40] <tjaalton> tried a full build and it failed, also on sbuild:
[11:40] <tjaalton> make[1]: Leaving directory `/«PKGBUILDDIR»/debian/build/tools-perarch/tools/power/x86/turbostat'
[11:41] <tjaalton> make[1]: *** No targets specified and no makefile found.  Stop.
[11:42] <tjaalton> although it might be result of the way I run clean
[11:42] <tjaalton> so nevermind
[11:43] <apw> tjaalton, hmmm no that is tools which needs a couple of patches against mainline to even have a makefile
[11:43] <tjaalton> ah, ok
[11:43] <apw> tjaalton, i probabally should suck that stuff up into the main debian packaging ... arse
[11:44] <tjaalton> heh
[11:44] <apw> do_tools=false will drop them
[11:44] <tjaalton> yeah
[20:07] <stgraber> apw: I've just been told by the lttng guys that their code now builds fine against 3.10 (I noticed it got disabled with the switch to 3.10 in Ubuntu)
[21:02] <cyphermox> sforshee: hey
[21:02] <cyphermox> sforshee: I seem to be missing a device for bluetooth on mako -- ttyHS0.
[21:02] <cyphermox> ttyHSL0 shows up, but for some reason although CONFIG_SERIAL_MSM_HS=y, it still doesn't get brought up, would you be able to help me figure out why?
[21:03] <cyphermox> quickly looking I wonder if it couldn't be because some other piece is missing, like perhaps that CONFIG_SERIAL_MSM_SMD
[21:07] <cyphermox> nevermind that