[00:17] robru, hey, can you reconfigure l31-silo-003 for me? added an MR [00:18] sergiusens, sure [00:18] robru, or do I not need to do that? [00:18] the MR targets the same project [00:18] sergiusens, if you added an MP then I need to reconfig it, for now. we're working on a way to give you more autonomy here [00:19] ok, thanks [00:19] sergiusens, ok done, please build. [00:20] thanks [00:32] doanac`, seems https://code.launchpad.net/~doanac/phablet-tools/autopilot-args/+merge/207315 still needs rebasing [00:32] doanac`, http://162.213.34.102/job/landing-003-1-build/35/console [00:43] fginther, failed again === wgrant_ is now known as wgrant [01:20] * cyphermox logs off [01:54] doanac`: plars: do you know why 206 is still in "running" state? [01:54] as are 202 and 201 [01:54] here: http://ci.ubuntu.com/smokeng/trusty/touch/ [02:23] ok dropping out ... cu tomorrow [04:08] asac: known bug being worked on: https://bugs.launchpad.net/qa-dashboard/+bug/1284298 [04:08] Ubuntu bug 1284298 in Ubuntu CI Services "Need a way to timeout 'running' smoke jobs" [Undecided,New] [05:36] robru: ping [05:37] robru: I see an entry in the CI train for UITK. Was not it so, that I am the releasing dude for the UITK? [05:38] robru: That MR -> https://code.launchpad.net/~renatofilho/ubuntu-ui-toolkit/limit-alarms-fetch/+merge/207629 is not approved by the SDK team [05:38] renato: ping [05:39] Is anybody here from the CI? [07:43] hello didrocks [07:43] hey bzoltan [07:44] didrocks: In the Self service CI (CI train) I watched the line nro 38 with some surprise. Does robru know that the UITK releasing belong to me and my team? He was about to release an MR what was not even approved yet. [07:45] bzoltan: I don't know why he set himself as a lander. I told we are not lander for anything though [07:45] bzoltan: so, I'll talk again about this with him [07:45] bzoltan: the MP has landed bt [07:45] didrocks: thank you [07:45] btw [07:46] didrocks: I am preparing a new MR bundle for today ... [07:48] bzoltan: ok, just be aware (see emails) that we are not releasing anything that's not to fix all the issues we have on the image first [07:48] didrocks: clear and +1 that [08:55] sil2100, y 29 no publish yet? [08:56] mhr3: we don't publish anything that impact touch [08:56] see the phone ML [08:56] hmm === psivaa changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: psivaa | CITrain support - US: robru, cyphermox, rsalveti - EU: sil2100, Mirv, didrocks | CITrain support no answer: use mup bot after 30 minutes, but chooose right timezone | Landing instructions: http://goo.gl/8H1Du3 | Known Issues: - [09:12] ralsina_: what was your rebuild in the updates silo about? [09:13] also, can we retry builds in the landing PPAs? [09:14] Laney: you can request the ci team to do that if you don't want to rebuild the MP itself [09:15] Laney: some other people like pitti, rsalveti have access to it [09:15] you can have if you don't mind the spam :) [09:15] https://launchpad.net/~ci-train-ppa-service/+archive/landing-010/+build/5633952 [09:15] you can give me it you want ;-) [09:15] procmail is a beautiful thing [09:16] Laney: one sec, giving to you. please, if you need to dput to a ppa direclty some stuff, target the right one! :) [09:16] hah [09:16] Laney: you have power! [09:17] Power \o/ [09:17] thanks didrocks! [09:17] yw ;) [09:17] I guess the spreadsheet won't notice if the retry succeeds though [09:17] 'watch only'? [09:18] exactly :) [09:28] didrocks: hmm, there's no morning meeting today? [09:28] omg my trusty is so borken today [09:29] * sil2100 didn't get an e-mail [09:29] sil2100: hum, there is [09:29] I did receive it [09:29] https://plus.google.com/hangouts/_/calendar/Y2Fub25pY2FsLmNvbV91cTRvNmQyMWJvNmJ0bm1mcW9xZWtsNTdnOEBncm91cC5jYWxlbmRhci5nb29nbGUuY29t.us2orfbhb8ssqjui2u15tajj3s [09:29] grrrr [09:29] didrocks: thanks [09:29] 20 seconds! [09:29] (ish) [09:30] Mirv, what's the issue with trusty? [09:31] Mirv: can you come to the meeting or you are really really broken? [09:32] comig [09:36] sil2100: the lightdm thing is the same I saw at the sprint. but I have really no idea what has happened otherwise. I upgraded and did this stuff less than hour ago... [09:36] it's possible removing lightdm messed up /etc/group or something like that [09:36] Mirv, what's the issue with lightdm? [09:38] seb128: the issue I've been seeing is a cosmetic one, some background parts like the machine name's turn to grey when pressing enter, ie the UI looks wrong. I got that fixed once by reinstalling lightdm including resetting its configuration. [09:39] that doesn't make sense [09:39] seb128: the rest of my problems are probably related to lightdm removal scripts or such breaking up other things, plus the fact that installing lxde/gdm etc is not completely smooth either [09:39] reinstalling a package makes no difference [09:40] seb128: it was a combination of things I don't remember all of which, but I thought to try again to find out what's the reason behind the UI ugliness [09:52] Mirv: https://jenkins.qa.ubuntu.com/job/trusty-touch-mako-smoke-daily/87/artifact/clientlogs/ubuntu_weather_app/ [09:52] has the crash file [09:56] psivaa: thanks, got it [10:12] sil2100, ping [10:14] tvoss: pong! [10:14] sil2100, I guess we are meeting in an hour from now on? [10:14] tvoss: yep [10:14] sil2100, ack and thx :) [10:14] ;) === vrruiz_ is now known as rvr [10:33] Mirv: is the qmlscene crash good enough to work on it? [10:33] Mirv: do not hesitate to involve the SDK team as well on that one :) [10:33] didrocks: it was not, for some reason, but I edited it manually to get backtrace which should be soon ready on the device [10:34] hgreat ;) [10:34] didrocks: the .crash was missing "Package:" line [10:34] ah ok [10:34] seems apport tried to report it without sucess [10:34] success* [10:34] (probably due to sdk in proposed) [10:35] and because I didn't start 'screen' on the device, I'm now stuck with LXDE and lxdm-binary consuming 100% CPU until the retrace is finished :P [10:35] ahah :) [10:37] didrocks: so, we're waiting for rsalveti to appear regarding the unity8 crashes - Saviq tried mapping the crash to a specific library, but it doesn't seem to be possible [10:38] didrocks: that memory range doesn't seem to be mapped to any library [10:38] didrocks, yeah, I can't get any symbol out of those :| [10:39] /we should build non-stripped system.imgs [10:39] Saviq: yeah, I was about to say that [10:39] Saviq: just build for one device [10:39] that will be quicker [10:39] (in case you are using the package) [10:40] didrocks, you'll have to give me more data on that [10:40] ok, one sec, downloading the source [10:40] I'll tell you what I did for this :) [10:40] didrocks, appreciated [10:41] Saviq: ok, so: debian/android-targets [10:42] didrocks, which pkg? [10:42] remove all lines you don't want :) [10:42] apt-get source android [10:42] right! [10:42] of course ;D [10:42] then in debian/rules [10:43] remove everything in the override_dh_install: after the dh_install call [10:43] That's hacky ;) [10:43] (the 2 tar commands) [10:44] rm debian/ubuntu-emulator* [10:44] as well [10:44] (even if that's not strictly needed) [10:44] so then build [10:44] Morning all [10:44] it will take only 15 minutes on my machines instead of 15 minutes*number of devices [10:44] wb davmor2! [10:45] Saviq: finally, just dpkg-deb -x android.deb foo [10:45] you will have the img in foo/usr… [10:45] sil2100: well, yeah, we should add more hacks to only build successfully for some sources :) [10:46] Saviq: you will need a 32 bits chroot, I was never have able to build it on x64 here [10:46] didrocks, oh ok good to know [10:47] didrocks, anything special I need to tell sbuild to not strip the binaries? [10:47] Saviq: the usual NOSTRIP (that you can hardcode in debian/rules while you are it to ensure ;)) [10:48] and then, just something like sbuild -d trusty -c trusty-proposed+multiverse-i386 --arch i386 android_-0ubuntu1.dsc -A should do it [10:49] didrocks, ok, going for it! [10:49] good luck, do not hesitate if you have any questoin [10:49] question* [10:51] didrocks, thinks we should consider building debug-enabled system.img as part of our image builds or do you think we could get -dbgsym packages out of it? [10:52] Saviq: I thinkg we should just create some -dbg and have system.img without being stripped part of that package [10:52] (I don't think we can automate that as -dbgsym) [10:52] didrocks, mhm, /me files bug [10:52] Yeaaa [10:53] but I'm maybe just on crack, I'm sure Ricardo is way more knowledgeable than I on that crazy package :) (I can understand the debian/rules though, so it's a start :p) [10:53] basically it's creating in your sbuild an armhf source [10:53] (so you have a chroot in chroot) [10:53] qmlscene bug #1284581 seems inside the (now obsolete) V8 engine of Qt [10:54] bug 1284581 in Ubuntu "qmlscene crashed with SIGSEGV in FindInlineFunctionGenerator()" [Undecided,New] https://launchpad.net/bugs/1284581 [10:54] Mirv: I'm about to send an email with latest state, would you mind answering that? [10:54] didrocks: ok [10:54] I wonder if that's something Android 4.4 related [10:55] didrocks, bug #1284583 [10:55] bug 1284583 in android (Ubuntu) "Should provide debug-enabled system.img" [Undecided,New] https://launchpad.net/bugs/1284583 [10:56] Saviq: thanks, I'll discuss that once the firefighting is off with Ricardo [10:57] hmm [10:57] that will put quite some build time penalty on us [10:58] ogra, how often do we build that though? [10:59] once or twice a month ... but if you are waiting for it to roll a test image it is annoying to wait 1h more :) [10:59] how often do you actually need dbg symbols inside android ? [10:59] twice a release for one specific arch ? [10:59] lightdm back, compiz still broken [11:00] seb128: oh, sorry, I managed to forget what triggered my tinkering with lightdm - after today's dist-upgrade + reboot, I was for some reason not able to type anything in lightdm [11:00] ogra, in lieu of that package, clear information on how to get it would be nice [11:00] Saviq: one can trivially locally build android with debug symbols, but we can't ship a debug img easily as it's too big and unflashable. [11:00] mouse worked. now after this adventure also typing works, plus the funny UI issues are gone [11:00] xnox, unflashable? crap [11:00] Saviq: thus one uses gdbserver, with debug symbols on the host and debug things over adb. [11:01] Saviq, yeah, i would even vote to have a PPA with debug builds ... [11:01] Mirv: you can work-around that by clicking on one of the indicators and then clicking away [11:01] Saviq: but since that relies on relative paths, one does a local android build with /detached/ symbols. [11:01] xnox, the system.img should be fine [11:01] sil2100: aha... :D [11:01] Saviq: flashes the images to devices and then does adb remote debugging with gdbserver. [11:01] Mirv, oh, right, that's a quite frequently reported issue :/ you can use indicators to workaround the typing bug, that gives the focus back to the entry [11:01] as it doesnt rely on y specific flash size [11:01] Mirv: you can then type normally - I have it like every second boot [11:01] Mirv: email sent [11:01] (it lives inside the ubuntu rootfs) [11:01] Saviq: i think rsalveti / sergiusens can guide you how to do it. [11:02] didrocks: ok [11:02] Laney: barry asked for one [11:02] Saviq: it's been a while since i last had to do it. [11:02] xnox, yeah, rsalveti is being waited on ;) [11:02] =)))) [11:07] ralsina_: ah, well you can give a package name to just try that particular one (system-image in this case) to not use resources unnecessarily [11:07] anyway, his stuff doesn't build :( [11:19] bzoltan: on https://code.launchpad.net/~bzoltan/ubuntu-ui-toolkit/ubuntu-ui-toolkit-RC_2502/+merge/208064, the commit message is used to commit to trunk [11:19] bzoltan: and in the changelog [11:19] a better description will be needed I guess :) [11:47] bzoltan: that MR itself won't be merged right? [11:48] t1mp: didrocks: that is just a testing MR, not meant to land [11:48] t1mp: didrocks: what I proposed to land is in the CI sheet [11:48] bzoltan: ah ok :) [11:48] bzoltan: ok, clear. that's what I thought :) [11:49] t1mp: didrocks: I want to be sure that there are no conflicts between the MRs [11:49] bzoltan: ++ [11:49] bzoltan: sure sure, you just frightened me :) [11:50] didrocks: Sorry for that :) [11:50] heh, no worry :) [12:11] didrocks, shall we move the OIF packages under ci-train or should I just move them to regular Debian-sync releases? [12:11] bregma: I would say citrain [12:12] of course you would, I didn;t expect any other answer :) [12:12] why did you ask then? :p [12:12] bregma: btw, I fixed my unity issues [12:12] was due to the decor plugin still loaded [12:12] however [12:12] now, I have no more Ctrl + Alt + T working :/ [12:13] bregma: oh! I see unity7 landing is ready to be assigned a silo [12:13] sil2100, yeah, I just did than, need a silo if you please [12:15] bregma, sil2100: wait [12:15] seb128: too late, silo assigned ;/ [12:15] seb128, is there a fix from xnox about to appear? [12:16] seb128: we can reconfigure in a moment [12:16] * sil2100 was trigger-happy [12:16] bregma, https://code.launchpad.net/~xnox/unity/no-debug-symbols/+merge/208093 from this morning [12:16] sil2100, no worry, I just want debug symbols to be fixed with that landing [12:17] bregma: can you add that to the MP list if needed ^ ? [12:18] seb128: do we know what changed? the default CFLAGS doesn't have -g now? [12:18] sil2100, added, does the silo need a reconfigure? [12:19] Yes, reconfiguring [12:19] didrocks, I don't know, https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1284047/comments/1 [12:19] Ubuntu bug 1284047 in unity (Ubuntu) "Build stripped binaries, lead to missing debug symbols" [High,Confirmed] [12:20] seb128: yeah, I just read your command, but seems changing changed on the default CFLAGS anyway [12:20] I guess there are quite some impacts on various packages [12:20] didrocks, I've run into that same problem in other packages, it seems there was a change to debhelper at some point [12:20] bregma: interesting, ok [12:21] it explicitly says to not set CFLAGS, so the packaging was broken before and just happened to work [12:21] bregma, didrocks: http://irclogs.ubuntu.com/2014/02/24/%23ubuntu-devel.html#t10:56 [12:21] "debhelper changed to BuildType=None, that might affect cmake based projects..." [12:21] not sure that's the issue there though [12:22] didrocks, bregma: the default flags seems to be fine, it's the hackery in debian/rules which is buggy (otherwise dropping those lines wouldn't be enough to fix it) [12:22] seb128: ah, thanks :) [12:22] yeah, at the time, it was the only way to remove -Wall though [12:24] I had the problem with an autotools project that set CFLAGS in the debian/rules file, it started losing hardening and debug flags after the build toolchain was upgraded after the last Debian release [12:25] fact is, Unity doesn;t need those fancy build flags any more, so good riddance [12:25] k [12:27] yep :) [12:30] didrocks, hey, so I got: [12:30] ubuntu-android-ramdisk+mako.img [12:30] ubuntu-preinstalled-boot-armhf+mako.img [12:30] ubuntu-preinstalled-recovery-armel+mako.img [12:30] ubuntu-preinstalled-system-armel+mako.img [12:30] ubuntu-ramdisk+mako.img [12:30] ubuntu-ramdisk-recovery+mako.img [12:30] I assume -system- is what I want to flash, anything else? [12:30] Saviq: yeah, I don't think you segfaulted on the recovery :p [12:31] and the ramdisk are included in the preinstalled ones [12:31] didrocks, and the corresponding ubuntu-*tar.xz as rootfs? [12:31] Saviq: no, the system img is what you need alone [12:31] didrocks, can I flash the system.img alone? [12:32] no [12:32] ogra: there will be a mismatch? [12:32] it lives inside the ubuntu system.img file [12:32] flashing it wont gain you anything [12:32] oh right [12:32] you need to rebuild the image with it [12:32] argh [12:33] you need to boot into recovery, loop mount /userdata/system.img and then put the android system.img file into /var/lib/lxc/android in there [12:33] ogra, ok, trying [12:33] ogra: if you do that once booted, do you expect to see bad things happening with libhybris? [12:34] (in recovery mode it is actually /data/system.img iirc) [12:34] didrocks, nope, as long as the hybris version is still the same [12:34] same goes for the kernel [12:34] ok :) [12:35] (the modules live inside the android system.img) [12:35] ok [12:39] * Saviq is worried there's no symbols [12:39] same size :/ [12:40] ;/ [12:43] no booting grr [12:47] ogra: are you sure not flashing the system partition is correct? We don't use anything from it, right? [12:47] ogra: because https://wiki.ubuntu.com/Touch/Building doesn't match [12:47] thats for the old flipped model [12:47] not for system-image [12:48] ogra: should probably be updated :) do we have one for system-image with similar instruction? [12:48] i dont think so [12:48] didrocks, didn't boot :|, /me wonders if 207 would help [12:49] Saviq: I don't think it would especially help, if you are already on 207… [12:49] ooppss [12:49] on 206 [12:49] I meant [12:49] didrocks, but anyway, the file should be bigger, shouldn't it :| [12:50] yeah, it should [12:51] the aosp build system is complex, not sure they respect our flags… [12:51] didrocks, yeah, I'm waiting for Ricardo [12:51] he'll do it in 5s [12:52] yep, sounds better :) [12:52] smells like you missed some build option when rolling the android package [12:53] added to debian/rules: [12:53] export DEB_BUILD_OPTIONS=nostrip noopt debug [12:54] and commented out all emulator-related things === cjohnston changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: cjohnston | CITrain support - US: robru, cyphermox, rsalveti - EU: sil2100, Mirv, didrocks | CITrain support no answer: use mup bot after 30 minutes, but chooose right timezone | Landing instructions: http://goo.gl/8H1Du3 | Known Issues: - [13:02] cjohnston: Our (Mir) CI has started failing all MPs. Can you tell if something changed? https://jenkins.qa.ubuntu.com/job/mir-team-mir-development-branch-trusty-amd64-ci/ === alan_g is now known as alan_g|lunch [13:05] ogra: we don't use trusty-preinstalled-touch-armel+mako.zip anymore, right? [13:05] in system-image [13:05] nope [13:05] looking [13:05] but some ports do ... [13:05] (which is why i didnt remove it yet from the build) [13:06] yeah [13:10] alan_g|lunch: I don't see anything that changed. I'm wondering if a release of something else maybe effected it [13:10] alan_g|lunch: I'll ask fginther to look when he comes around [13:21] morning [13:21] didrocks: Saviq: still checking emails, do you have a crash file available and how to reproduce the crash easily? [13:35] didrocks: ogra: awesome, dashboard for 207 looks way better [13:35] the pulse fix I did yesterday still didn't land [13:35] well, kind of [13:35] that will reduce cpu usage as well [13:35] ogra: well, system-settle is better (not sure if fixed :-) [13:35] rsalveti, we seem to have set CONFIG_RT_GROUP_SCHED in our kernel ... seems that prevents rtkit-daemon from functioning [13:35] rsalveti: I don't have the crash file handy, Saviq has one [13:35] system-settle was re-written [13:35] rsalveti: yeah, you are hit by beta freeze [13:36] ogra: is that preventing or are we missing some other options? [13:36] rsalveti: otherwise, not a lot of progress overall (see my email entitled "summaring up issues on current touch…") [13:36] rsalveti, seems it is preventing on purpose if i read the docs right [13:36] yeah, we'll get more fixes til end of my day [13:36] :-) [13:37] ogra: oh, ok [13:37] rsalveti, waiting for stgraber to show up, he should know if we need that option at all [13:37] i assume having pulse in rt mode will give us some boost in audio stuff :) [13:37] * ogra would love if the kbd even made click sounds when you type fast) [13:37] hahah [13:38] it kind of looses it if you get to a certain typing speed [13:38] rsalveti, oh, and hammerhead ucm files uploaded ;) [13:38] ogra: \o/ [13:38] not final but at least people have sound [13:39] that's awesome anyway [13:39] and comes fully from the community ... thats what i like most about it [13:39] :) [13:40] yeah [13:43] rsalveti, yes I've a .crash (plenty of them, actually) [13:43] rsalveti, way to repro: phablet-test-run -p unity8-autopilot -n unity8 [13:43] rsalveti, but if possible and you have some time, I'd like to learn how to tackle this next time [13:44] Saviq: basically https://wiki.ubuntu.com/Touch/Core/UbuntuDebugAndroid [13:45] Saviq: but first you'd need a local build of your android [13:45] then you can get the libs with debug symbols (we should probably be exporting that somehow via android-dbg [13:45] I'll try to get to that later this week) [13:46] repo init -u https://code-review.phablet.ubuntu.com/p/aosp/platform/manifest.git -b phablet-4.4.2_r1 [13:46] repo sync [13:46] source build/envsetup.sh [13:46] lunch aosp_mako-userdebug [13:46] that should get you the 4.4 based images [13:47] rsalveti, bug #1284583 btw :) [13:47] bug 1284583 in android (Ubuntu) "Should provide debug-enabled system.img" [Undecided,New] https://launchpad.net/bugs/1284583 [13:47] Saviq: thanks [13:47] rsalveti, but yeah, problem is... http://pastebin.ubuntu.com/6993715/ [13:48] right, smells like android [13:48] rsalveti, also, you can't get the map if you only got a .crash file [13:48] interesting that I coudn't get any crash when running the autopilot test this weekend [13:48] rsalveti, it doesn't always happen [13:48] oh, I thought you had procmaps in there [13:48] rsalveti, ah you're right [13:48] in the .crash directly [13:49] rsalveti, once in every 20-30 runs [13:49] got it [13:49] Saviq: can I get your crash file as well [13:49] ? [13:50] rsalveti, of course [13:50] * Saviq preprocesses [13:51] rsalveti, and how do I get a symbolized local build? we actually tried to build a complete system.img with nostrip, but that didn't work (same .img file size, and didn't boot anyway) [13:51] Saviq: yeah, need to change the build rules internally [13:51] that's what I'm planning to do to fix your bug [13:52] rsalveti, so yeah, problem with the maps part is that, according to what I was able to find, no library is actually mapped at the address where it crashed :/ [13:52] oh, hm [13:52] could this be mir related? [13:53] I know we had tls issues with mir as they are heavily using tls with c++11 now [13:54] rsalveti, one thing I know is the crash happens after libcrypto causes SIGILL [13:54] if that has any bearing [13:54] hm, that always happens [13:54] when it's testing for supported features [13:57] rsalveti, yeah I know, just saying === alan_g|lunch is now known as alan_g [13:58] yeah, I got annoyed by that once already [13:58] rsalveti, http://people.canonical.com/~msawicz/_usr_bin_unity8.32011.crash [13:59] rsalveti, so yeah, as you can see maps doesn't mention anything :| [14:01] rsalveti, that's why /me wanted a fully symbolic system.img, if at all possible :| [14:01] * sil2100 jumps out to the vet again, quickie [14:10] sil2100, lol === pete-woods is now known as pete-woods-lunch [14:41] alan_g, looking at the mir failures. the only difference I see so far is that there is a new libc version in the builds that are failing tests [14:42] fginther: alf_ wonders if it could be related to https://bugs.launchpad.net/mir/+bug/1284653 [14:42] Ubuntu bug 1284653 in valgrind (Ubuntu) "valgrind packages ouf of sync with current glibc version (2.19)" [Undecided,New] [14:42] alan_g, hmmm, libc went from libc6_2.18-0ubuntu7_amd64.deb to libc6_2.19-0ubuntu2_amd64.deb [14:46] alan_g, ok, based on this bug, it looks the issue has been identified. Can you work with the foundations team to get a new valgrind built? [14:46] kgunn: ^^ [14:47] alan_g: fginther ...yep, trying to get someone to reply :) [14:47] kgunn, thanks! [14:47] rsalveti, so... I'll be your PITA today, can you point me anywhere which would tell me how to actually nostrip system.img? [14:48] Saviq: no worries, getting dedicated to your issue now [14:49] didrocks: diwic found why pulse is always consuming ~2% of the cpu, and he found the fix as well [14:49] didrocks: should hopefully land in the archive later today [14:49] better battery life as well :-) [14:54] rsalveti: excellent, let's hope we can convince the release team to accept it despite the beta freeze :) [14:54] yeah [14:55] * didrocks really goes for a run before it's raining [14:57] just wait, will save you the shower afterwards [14:58] (take some shower gel with you though) [14:59] sil2100: can i get a silo for line 30? [15:03] Saviq: I think this is all you need to have a not-stripped image: http://paste.ubuntu.com/6994774/ (at build/) [15:03] Saviq: checking still [15:04] rsalveti, /me builds [15:04] argh, still stripping [15:04] Saviq: you also need the vendor files which I forgot: bzr branch lp:~rocket-scientists/aal+/aosp-vendor-4.4.2 vendor [15:05] let me do a clean build as well [15:06] thostr_: let me see [15:06] rsalveti, and where do I put the vendor files? [15:07] Saviq: builddir/vendor [15:07] builddir is your build dir root directory [15:07] rsalveti, I'm actually in `apt-get source android` [15:08] Saviq: oh, if you rebuild that it'll work fine, as it copies the files from the android-src-vendor package [15:08]