[07:17] <sil2100> o/
[07:17] <sil2100> Is it only so hot at my place or is it a plague in all Europe?
[07:34] <abeato> sil2100, in my case it is actually cooler this week ;)
[07:35] <abeato> sil2100, I have created a vivid silo to sync with a wily silo because of this limitation for dual silo (as you cannot have CI packages+direct uploads for that kind of silos)
[07:35] <abeato> sil2100, but not working as you see ^^
[07:35] <abeato> sil2100, any idea why this can be happening?
[07:36] <sil2100> abeato: hey, let me take a look
[07:37] <abeato> sil2100, great
[07:41] <sil2100> abeato: what packages would you like in this silo?
[07:42] <abeato> sil2100, ubuntu-touch-session synchronized from silo 57, pulseaudio that will need to be manually uploaded
[07:43] <abeato> sil2100, concretely from here https://launchpad.net/~canonical-arm-dev/+archive/ubuntu/ppa
[07:43] <sil2100> ok, so I'll reconfigure the silo to be a sync from 57 and enable the pulsaudio source upload
[07:43] <abeato> sil2100, awesome, thanks
[07:50] <dbarth> hey there
[07:50] <dbarth> so first, it's not so hot here today (25 deg.) so it's not a plague like /everywhere/ in Europe
[07:51] <dbarth> but close to it still, 34 tomorrow :/
[07:51] <dbarth> that's for sil2100 ;)
[07:51] <dbarth> then, i'm still trying to get silo 31 cleared
[07:52] <sil2100> dbarth: you want it completely gone and wiped away from the surface of earth? ;)
[07:52] <dbarth> well, if i could merge it in trunk, it would be good
[07:57] <sil2100> dbarth: let me take a look at it
[07:57] <sil2100> dbarth: ah, it's waiting on QA sign-off, right?
[07:58] <sil2100> I suppose QA should have more resources this week
[08:00] <abeato> sil2100, I need some help to upload pulseaudio to the silo, the people that could do that in my team is on holiday, who could help with that?
[08:01] <pete-woods> trainguards: hey guys. to mark a silo as tested now, do I just edit it to say "Ready for QA"?
[08:02] <pete-woods> just wanted to check before I nagged someone in QA :)
[08:08] <sil2100> abeato: on it
[08:08] <sil2100> pete-woods: yes :)
[08:09] <sil2100> abeato: hm, I have no permission to open the PPA ;)
[08:09] <pete-woods> sil2100: thanks for the info :)
[08:11] <abeato> sil2100, I thought you had permissions for anything :)
[08:12] <dbarth> sil2100: it's not; it's mostly building / packaging; smoke testing merely
[08:13] <dbarth> sil2100: but it's a left over of an initial dual landing attempt
[08:13] <dbarth> hence the qa required tag that may still be floating around that silo
[08:14] <dbarth> at least, if qa wants to take it, it should be on the dashboard, but it's not; it's nowhere, so i'm trying to have it move "somewhere" at least ;)
[08:18] <sil2100> dbarth: ah! I only noticed it now that it's wily
[08:18] <sil2100> Ok, let me publish
[08:18] <sil2100> abeato: apparently not ;)
[08:19] <sil2100> dbarth: hm, when was the package built?
[08:19] <sil2100> dbarth: was it built with gcc-5 already?
[08:20] <sil2100> dbarth: I think we might need to rebuild it just in case
[08:21] <dbarth> sil2100: it was before gcc5, so yes, i'll respin that one, and will do just as quick install on a wily phone to check that the program loads
[08:21] <sil2100> dbarth: excellent :) Once you're done and happy with it, please switch the status to 'Publish without QA'
[08:22] <sil2100> This means the silo has been tested and is ready for release
[08:23] <dbarth> ok, deal !
[08:33] <mardy> sil2100: hi! There is an error here (see line from queuebot ^)
[08:34] <mardy> sil2100: but I cannot find 0.17+15.04.20150410-0ubuntu2~gcc5.1 anywhere... where was it published?
[08:34] <mardy> sil2100: http://packages.ubuntu.com/search?keywords=signon-ui&searchon=names&suite=wily&section=all doesn't have it
[08:35] <Laney> https://launchpad.net/ubuntu/+source/signon-ui/0.17+15.04.20150410-0ubuntu2~gcc5.1
[08:35] <mardy> Laney: thanks, I'll sync that, then
[08:45] <darkxst> Hi, I now have ubuntu-desktop rights, but can't access the CI stuff apparently since I am not a core-dev, is it possible to get this added?
[08:58] <sil2100> mardy: hey!
[08:58] <mardy> sil2100: nw, it's solved now
[08:58] <sil2100> mardy: we recommend using launchpad for checking published versions ;) The ~gcc5.1 version is in -proposed with all the other packages that are transitioning
[08:59] <sil2100> (was in the landing meeting)
[08:59] <mardy> sil2100: yep, Laney pointed me at the right files
[09:06] <ogra_> sil2100, jibel, image published, importer should pick it up now
[09:06] <popey> hmm, unity8-dash was killed on my retail krillin by the OOM killer
[09:06] <popey> and never came back
[09:07] <popey> bah, can't file a bug against unity8 because it came from a ppa
[09:07] <popey> thought we'd fixed that :(
[09:16] <sil2100> ogra_: \o/ thanks!
[09:24]  * ogra_ sighs ... 
[09:26] <ogra_> cjwatson, someone abused the cdimage production branch as activity log (two pointelss direct commits about removing and re-adding a mairror entry), can i just revert that on nusakan or will that confuise the ~/cdimage/production branch even more ?
[09:26] <ogra_> (I'm trying to add sil2100 to notify-addresses)
[09:30] <ogra_> ah, just uncommitting them worked fine
[09:43] <ogra_> sil2100, hmm so http://cdimage.ubuntu.com/ubuntu-touch/vivid/daily-preinstalled/20150810.1/ was published but i dont see the importer pick it up at all
[09:43] <sil2100> ogra_: let me check that
[09:43] <ogra_> in fact, despite the cdimage error the same image got published as 20150810/ too
[09:44] <ogra_> aha
[09:44] <ogra_> the MD5SUMS files didnt get updated
[09:44] <sil2100> ugh, yeah, the imported dies in the middle
[09:45] <sil2100> When generating the deltas
[09:45] <dbarth> sil2100: ok, i need you for the publish button, i think, and then this should be all over (silo 031, no rush)
[09:45] <sil2100> dbarth: on it!
[09:45] <ogra_> sil2100, i'll try something, seems it fell over on the missing i386 build ... that will get us a .2 though
[09:47] <sil2100> ogra_: better than not having anything ;)
[09:47] <sil2100> dbarth: published :)
[09:48] <ogra_> hmm, that doesnt seem to have produced anything :/
[10:02] <sil2100> The importer still crashes
[10:02] <sil2100> ogra_: I see it dies when generating diffs in the ubuntu-touch/devel-proposed-g++5/ubuntu channel
[10:02] <sil2100> So maybe that's related to some things slangasek was doing during the weekend?
[10:21] <ogra_> sil2100, why would it do any diffs there for vivid, i think the two issues are rather unrelated
[10:25] <ogra_> (cdimage not releasing the right thing vs system image not importing)
[10:33] <dbarth> \o/ thanks sil2100
[10:41] <ogra_> sil2100, ok, i got the cdimage side of things fixed now ...
[10:41] <sil2100> I'm looking at the importer still
[10:41] <ogra_> sil2100, for the importer you shoudl perhaps just comment out wily for the moment
[10:41] <sil2100> Looks like a tarball corruption...
[10:42] <ogra_> there were no successful livefs builds for a while
[10:46] <sil2100> Yeah, I'll switch it for manual for now and try to debug in the background
[10:47] <sil2100> It looks to me as if one of the recent g++5 builds for wily simply generated a bollocks tarball
[10:49] <ogra_> that can well be ... slangasek and infinity were experimenting with usin metapackages instead of tasks
[10:50] <ogra_> though that shouldnt result in corrupted tarballs ... just with messed up content
[10:54] <sil2100> ogra_: importer running anyway
[10:54] <sil2100> Well, yeah
[10:55] <sil2100> Messed up content can be the cause here as well as it fails during delta generation... but it failed really strangely almost as if when trying to get tarball content
[10:59]  * sil2100 starts getting spammed by cd image mails
[10:59] <sil2100> :D
[10:59] <Trevinho> Hey, how can I get the powers to be able to land compiz/unity and all the rest of the deb-desktop stuff?
[11:00] <sil2100> Trevinho: let me give you teh powerz
[11:00] <Trevinho> sil2100: thanks... seb128 will assist me on first landings
[11:00] <sil2100> We give them out for free ;)
[11:01] <sil2100> Trevinho: added to the right group, remember we have documentation for this: https://wiki.ubuntu.com/citrain/LandingProcess
[11:04] <Laney> sil2100: did you add darkxst?
[11:07] <Trevinho> sil2100: thanks
[11:12] <sil2100> Laney: no, I can add him if needed
[11:12] <Laney> yes please, he's in the desktop team now
[11:12] <Laney> sil2100: or maybe make ubuntu-uploaders a train driving team?
[11:15] <sil2100> I suppose we could do that, we already have the core-devs team as a member
[11:15] <Laney> ubuntu-uploaders is supposed to contain all people who have any upload rights
[11:41] <ogra_> yay
[11:41]  * ogra_ got the update notification
[11:42] <ogra_> 105 MB !!!!
[11:44] <ogra_> sil2100, how can we have grown by 105 MB since friday ?
[11:45] <ogra_> oh
[11:45] <ogra_> new device tarball
[12:16] <sil2100> Ok guys, I need to go for lunch now and do some groceries shopping
[12:16] <sil2100> Might be away for a bit longer, but will be around for longer as always
[13:01] <jhodapp> davmor2, finally got the qtmultimedia patch correct so vivid still boots, so just doing a quick sanity check of things and then I'll be ready to turn silo 38 over to you and your team
[13:02] <davmor2> jhodapp: excellent how quickly do you want it broken?
[13:02] <jhodapp> davmor2, ha, as soon as I give the green light, as quickly as you can
[13:03] <davmor2> jibel: ^ this is the silo that frees up indicators and scopes iirc
[13:20] <jhodapp> pstolowski, tsdgeos: feel free to give silo 38 a try with the music-scope...background playlists should be working from it
[13:20] <tsdgeos> jhodapp: cool
[13:22] <pstolowski> jhodapp, great, thanks!
[13:23] <jhodapp> np
[13:24] <jhodapp> tsdgeos, pstolowski: FYI, if you find bugs with it, file them against qtubuntu-media (ubuntu-rtm) and media-hub (ubuntu-rtm)
[13:27] <tsdgeos> oki
[13:32] <pstolowski> jhodapp, can you do your testing and land the silo, or do you need us to verify? we need our another silo to land first before we're able to build our playback changes
[13:33] <jhodapp> pstolowski, no it's ok, I just wanted to let you know about the silo in case you were anxious to get testing your stuff right away
[13:34] <jhodapp> pstolowski, I expect bugs, this first release is merely to get the code landed making sure that it doesn't break any existing playback scenarios
[13:34] <pstolowski> jhodapp, that's ok, we should land asap due to FF, then we can fix remaining issues
[13:34] <jhodapp> sounds good!
[13:36] <jibel> davmor2, why is silo 19 set to "QA required" on bileto while you approved it earlier today?
[13:38] <davmor2> jibel: meh my fault I forgot to mark it passed cause lunch got called
[13:40] <davmor2> jibel: done now
[13:40] <jibel> davmor2, np, I thought it had been rebuilt or something
[13:40] <davmor2> jibel: no but good job you noticed
[15:00] <slangasek> sil2100, ogra_: the only change I made for tasks vs. metapackages was for the ubuntu desktop image; nothing that would have affected phone images or their importing.  Is the importer still failing or did that get figured out?
[15:02] <sil2100> slangasek: no, I'm looking into that now (was on lunch) - but I temporarily made the g++5 channel manual so that other channels can get imported
[15:02] <ogra_> slangasek, i understood that sil2100  just ripped out the wily imports for now
[15:05] <slangasek> ok
[15:05] <ogra_> slangasek, arent you in heidleberg ?
[15:05]  * ogra_ kind of expected you in a EU TZ
[15:07] <slangasek> ogra_: no, DebConf doesn't start until this coming weekend
[15:07] <ogra_> well, debcamp :))
[15:07]  * ogra_ ponders going this week, all the TLSP people seem to be there 
[15:07] <ogra_> *LTSP
[15:09] <pstolowski> sil2100, hello! could you please purge ppa 5 for me?
[15:11] <sil2100> pstolowski: hey! Sure, clean completely?
[15:11] <pstolowski> sil2100, yes, i've some stale packages there
[15:12] <sil2100> You want to re-assign it then?
[15:12] <sil2100> Ok, cleaning
[15:16] <pstolowski> sil2100, ok, but i need a new one with same stuff
[15:17] <sil2100> pstolowski: assigning
[15:18] <pstolowski> thanks
[15:26] <morphis> sil2100: is there a timeframe when you can land silo 48 in wily?
[15:27] <sil2100> morphis: on it now! Sorry, was deep in debugging :)
[15:27] <sil2100> Thanks for the poke
[15:27] <morphis> sil2100: np :)
[15:28] <morphis> just want to setup the sync silo to get it into vivid too
[15:28] <sil2100> morphis: don't worry about the message ^
[15:28] <morphis> ok
[15:28] <sil2100> I'm running the watch_only build as that's required and publishing then
[15:29] <morphis> ok
[15:40] <jhodapp> davmor2, silo 38 ready to test in about 5 mins
[15:51] <sil2100> robru, jibel, davmor2, ogra_: I don't suppose we have anything to discuss specifically on our evening meeting
[15:52] <sil2100> Too hot to put a shirt on
[15:52] <jhodapp> davmor2, alright, silo 38 is ready for test (is there no way with bileto to mark a silo as ready for QA to test?)
[15:52] <sil2100> jhodapp: yes
[15:52] <sil2100> 'Ready for QA' in the sign-off field
[15:52] <jibel> sil2100, nothing from me.
[15:52] <jhodapp> sil2100, under edit?
[15:53] <sil2100> jhodapp: yes
[15:53] <jhodapp> sil2100, unless I'm just missing it, I don't see that
[15:53] <jhodapp> sil2100, oh nm, same as QA Required
[15:53] <jhodapp> same list
[15:55] <ogra_> sil2100, +1 for the shirt thing
[16:06] <sil2100> hmmm, interesting
[16:24] <sil2100> slangasek: ok, so I investigated a bit, and from what I see from daily-preinstalled-20150809 onward the custom tarball tarfile is hm... broken
[16:25] <sil2100> slangasek: starting from that build onward, every custom tarball generated python tarfile dies when iterating through the files in the tarball and actually tar -xf also has some issues:
[16:26] <sil2100> slangasek: http://paste.ubuntu.com/12049072/
[16:26] <sil2100> slangasek: the earlier tarballs do not have this error
[16:26] <sil2100> slangasek: did you change anything that could be related when doing experiments over the weekend?
[16:26] <sil2100> slangasek: the livecd build logs for good and bad builds seem to be almost identical
[16:33] <slangasek> sil2100: nothing at all
[16:35] <sil2100> slangasek: interesting thing is (might be a red herring though) is that both the broken builds have been done on kishi12
[16:35] <sil2100> Two good ones I saw so far were kishi11 and kishi13
[16:35] <slangasek> oh. is that the same one that I had a failed package build from over the weekend that made no sense?
[16:36] <sil2100> Not sure, hm
[16:36] <slangasek> no, that was kishi14
[16:36] <slangasek> sorry, all even numbers look alike to me
[16:39] <sil2100> Anyway, really really strange
[16:39] <sil2100> The two broken builds even have more 'Built files' in the LP view, the good ones only list the manifest - do you know if this means anything?
[16:40] <slangasek> afraid I don't, sorry
[16:40] <slangasek> infinity may be able to clarify
[16:40] <sil2100> infinity: hey! Would appreciate your expertise in LP builders and such ;)
[16:40] <sil2100> infinity: ^
[16:45] <dobey> that builder thinks it's 1939?
[16:46] <sil2100> Yeah, apparently
[16:47] <sil2100> Although the build logs show a normal date
[16:47] <dobey> yeah
[16:48] <dobey> well, not quie
[16:48] <dobey> oh, doh
[16:49] <dobey> gotta remind myself to ignore the kernel date
[16:49] <sil2100> slangasek: can I kick an image for testing?
[16:49] <sil2100> Maybe I'll get a new builder, and the same way I'll check if it's not anything funny and transient
[16:53] <sil2100> hmmmmm
[16:55] <sil2100> The interesting thing is that all the good builds had only the manifest in the Built Files, even when accessing it through LP API I can't get the resulting tarballs, although cdimage seems to find them somehow through the librarian - anyway, I'll kick off a new image
[17:01] <infinity> sil2100: I'll look in a second.
[17:02] <sil2100> infinity: thanks - let me paste you the links to the builds here (the ones with 'good customs' and bad ones)
[17:02] <sil2100> infinity: https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/wily/ubuntu-touch/+build/34535 <- a good one, for instance
[17:03] <sil2100> infinity: https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/wily/ubuntu-touch/+build/34639 <- a bad one (with lots of files in it, and it actually makes sense that the builder lists those)
[17:15] <infinity> sil2100: I think you might have your good and bad reversed...
[17:15] <infinity> sil2100: The one with all the files is clearly "good", no?
[17:15] <sil2100> infinity: well, from the LP POV, yes, but those with all the files actually have broken custom tarballs generated
[17:15] <infinity> sil2100: The one missing all the boot images is "bad", but it's a product of how ogra wrote this bit of livecd-rootfs that it ignores failures on copying those.
[17:15] <sil2100> (with invalid timestamps in some files)
[17:16] <sil2100> Oh
[17:16] <infinity> sil2100: If they're broken, that's not LP's fault. :P
[17:16] <ogra_> infinity, i was asked to do that
[17:16] <sil2100> infinity: so does it mean that when there are no files listed, it means it uses some old versions of the files it failed to copy?
[17:16] <infinity> ogra_: I'm not saying it's only your "fault", per se, but ignoring failure is always dangerous.
[17:16] <ogra_> so that the missing zip doesnt make the build fail since we had a transition period wheer you could install phones from android zips
[17:16] <sil2100> Since I see the cd-image build logs still mention that it's fetching all those files from the librarian, but I'm not sure where it's taking those from
[17:17] <ogra_> nowadays we dont produce zips at all so that code could as well get wiped
[17:17] <ogra_> it just produces log noise
[17:17] <infinity> ogra_: zips?  Y
[17:18] <infinity> ogra_: Sorry, I'm ignorant of the touch build process.  Do you mean all the .img stuff is irelevant to the final product?
[17:18] <ogra_> infinity, we started with android zips when doing the phone images
[17:18] <ogra_> no, the img stuff is relevant
[17:18] <infinity> ogra_: Okay, the img stuff is what I'm talking about.
[17:18] <infinity> ogra_: When they fail to exist, you ignore errors on copying them.
[17:18] <ogra_> the zip stuff that is explicitly || true'ed isnt
[17:19] <ogra_> hmm, for the actual phone imgs ?
[17:19] <infinity> ogra_: See https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/wily/ubuntu-touch/+build/34535 which has no .img files, cause they all didn't copy.
[17:19]  * ogra_ checks the code
[17:19] <sil2100> infinity: maybe you could help me out in understanding something: http://people.canonical.com/~ubuntu-archive/cd-build-logs/ubuntu-touch/wily/daily-preinstalled-20150808.log <- this mentions fetching all the files like the custom tarball, rootfs etc. but the build in LP doesn't list those at all
[17:19] <infinity> Actually, it has no livefs either.  This is kinda special.  Why did this "succeed"?
[17:19] <sil2100> infinity: do you know where it takes those from in that case, since you said it actually failed copying them?
[17:19] <sil2100> (it's this one: https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/wily/ubuntu-touch/+build/34535 )
[17:20] <ogra_> 77                         # Android 4.4.2 based images do not ship a .zip file, do not fail if it does not exist
[17:20] <ogra_> 478                         cp -v chroot/usr/share/android/product/*-preinstalled-touch-armel+${subarch}.zip\
[17:20] <ogra_> 479                                 "${PREFIX}.armel+${subarch}.zip" || true
[17:20] <infinity> ogra_: Oh, no.  Some of them did copy, I'm misreading the log.  They didn't get returned to LP.  Or something.
[17:20] <ogra_> thats the only place where i skip copying
[17:20] <infinity> ogra_: Yeah, sorry for maligning you, I was misreading the log.
[17:20] <ogra_> live-build/auto/build ... at the bottom
[17:20] <ogra_> but these three lines should really get wiped
[17:21] <infinity> sil2100: This is an LP display issue, perhaps.  If the files are in the librarian and being fetched, it's bizarre that they're not on the page.
[17:21] <ogra_> we will never again produce zips
[17:21] <infinity> cjwatson: Halp.
[17:23] <infinity> sil2100: Individual builders have no control over what shows up in the UI, except for building the bits in the first place.  THey must be being built and returned, or there'd be nothing to fetch from the librarian, so the UI here is confusing, to say the least.
[17:24] <sil2100> infinity: ok, I tried fetching them from lp-shell but .getFileUrls() also returns just the manifest, which is strange!
[17:24] <sil2100> Probably unrelated to our tarball issues tho
[17:24] <sil2100> Still, it confused me a bit
[17:24] <sil2100> infinity: anyway, thanks for the explaination
[17:25] <infinity> I suppose the CD build could be failing to find files and reverting to an old build, but I'd think it would log when it does that.
[17:26] <sil2100> hmm, that could explain some of our problems, I wonder if that's the cae
[17:26] <ogra_> cdimage doesnt use LP at all
[17:26] <sil2100> *case
[17:26] <sil2100> pfff
[17:26] <ogra_> it only looks at nusakans local FS
[17:26] <ogra_> (unless i misremember)
[17:26] <infinity> ogra_: Well, the bit that builds and pulls livefses looks at LP. :P
[17:26] <ogra_> yeah, that does
[17:26] <infinity> ogra_: And the build log clearly shows it downloading from the librarian.
[17:26] <sil2100> Anyway, I'll get back to this tomorrow, now I need to go and cool myself up or I'll go crazy
[17:26] <ogra_> but the final publishing doesnt, does it ?
[17:27] <ogra_> oh, then i remember wrong
[17:27] <infinity> ogra_: This isn't about the final publish, but where the files came from before then.
[17:27] <ogra_> ah
[17:28] <infinity> sil2100: Anyhow, the newer build seems to be correct, right?  (as in, building the right bits, not necessarily building them correctly, but that wouldn't be an LP issue)
[17:28] <infinity> sil2100: What's the actual complaint about the new bits?
[17:29] <sil2100> infinity: the new build looks ok, so no complaint besides the issues that we're seeing, probably caused by something strange somewhere else
[17:30] <ogra_> did xz change in incompatible ways in wily ?
[17:30] <sil2100> The issues being the custom tarball having files timestamped at 1939-06-11 07:15:28
[17:30] <infinity> sil2100: Oh, I thought you said the new ones were weirdly broken.
[17:30] <ogra_> so that you cant properly diff the tarballs anymore ?
[17:30] <sil2100> Well, only the new custom tarball is weirdly broken
[17:30] <sil2100> Which causes the system-image importer to die when trying to import those
[17:30] <ogra_> well, that doesnt involve LP or cdimage or live-build at all
[17:31] <ogra_> the custom tarballs come from some jenkins build afaik
[17:31] <sil2100> ogra_: no, not the /ubuntu ones
[17:31] <sil2100> We create those at run time with livecd-rootfs
[17:31] <ogra_> ah
[17:31] <sil2100> I mean, cdimage-custom creates those
[17:32] <ogra_> yeah, i remember that, that was slangasek's work iirc
[17:32] <infinity> sil2100: Which file(s)?
[17:32] <ogra_> 317         (cd "binary/$INITFS/custom.dir/" && tar -c *) | \
[17:32] <ogra_> 318                 gzip -9 --rsyncable > "$PREFIX.custom.tar.gz"
[17:32] <ogra_> 319         chmod 644 "$PREFIX.custom.tar.gz"
[17:32] <infinity> Oh, I see them.
[17:32] <infinity> -rw------- 1 root root   4249 Jun 10  1939 click_com.ubuntu.filemanager_filemanager_0.4.386
[17:32] <sil2100> infinity: http://paste.ubuntu.com/12049072/ <- click apparmor profiles
[17:33] <infinity> Etc.
[17:33] <infinity> Are those created at build time, or copied from a package?
[17:33] <ogra_> (from livecd-rootfs)
[17:33] <ogra_> hmm
[17:34] <sil2100> infinity: created at build time by a livecd-rootfs hook IIRC
[17:34] <infinity> Okay, it's just the ones in the cache, so I assume that's build-time.
[17:34] <infinity> But buildds ntpdate at runtime.
[17:34] <infinity> 10 Aug 02:04:20 ntpdate[23960]: adjust time server 10.211.37.1 offset 0.000787 sec
[17:34] <ogra_> infinity, live-build/ubuntu-touch/hooks/60-install-click.chroot
[17:35] <infinity> Which went correctly for that build.
[17:35] <sil2100> Right, all seemed fine with the date on the builder apparently
[17:35] <ogra_> that script wgets the clicks from http://archive-team.internal/click_packages
[17:36] <infinity> So, click/apparmor bug?
[17:36] <ogra_> nd then runs "click install" n them
[17:37] <infinity> Should be able to test that in a chroot.  It's not doing anything terribly complex.
[17:37] <ogra_> that message is fine in teh log "WARN: AppArmor not available when processing AppArmor hook"
[17:37] <ogra_> (expected)
[17:38] <sil2100> No recent apparmor or click upload to wily
[17:38] <sil2100> Or anywhere else
[17:39] <sil2100> Ok, I need to disconnect now, thanks for looking into this o/ I'll get back to this tomorrow if anything
[17:39] <ogra_> well, and the log looks fine on both, broken and good builds
[17:39] <infinity> Do old/good builds have that vala complaint about connecting to logind?
[17:39] <ogra_> yes
[17:40] <ogra_> even the duplicated apparmor message in the later few clicks
[17:40] <ogra_> that part of the log looks exactly the same
[17:45]  * ogra_ notes that the app store was recently upgraded ... i wonder if that possibly influenced the timestamps of the clicks 
[17:52] <ogra_> infinity, i bet itis the nnew store that was just rolled out
[17:52] <ogra_> since we pull the clicks from there
[17:55] <ogra_> oh, no, wait
[17:55] <ogra_> thats only the apparmor profiles
[17:55] <ogra_> live-build/ubuntu-touch/hooks/90-precompile-apparmor-policies.chroot generates them
[17:56] <ogra_> cho "I: precompiling custom click apparmor policies"
[17:56] <ogra_> mkdir -p /custom/cache/apparmor
[17:56] <ogra_> /sbin/apparmor_parser -M ${FEATURES} -Q --write-cache --cache-loc=/custom/cache/apparmor/ `find /var/lib/apparmor/profiles/ -maxdepth 1 -type f -not -path '*/\.*'`
[17:56] <ogra_> i wonder if there is a -v switch to apparmor_parser ;)
[17:57] <ogra_> hmm, no, only --debug ... and that doesnt sound like it would only be verbose
[17:57] <ogra_> bah, i'm blind, there iis --verbose
[17:58] <ogra_> i would suggest we add that be default to these lines ... so we get more output (even if that doesnt fix anything it should make it easier)
[18:02] <robru> Mirv: you still around? I need some gl/gles advice.
[18:20] <davmor2> oSoMoN: silo 005 is still in needs review state can you get it approved please
[18:20] <oSoMoN> davmor2, oh, right, let me do that now
[18:21] <oSoMoN> done
[18:30] <pete-woods> trainguards: does anyone have some time to publish silo 56? it's holding up one of my silos
[18:30] <robru> pete-woods: oh sure. I assumed kenvandine would do it, but I'm here
[18:31] <pete-woods> robru: that would be great :)
[18:32] <pete-woods> woot! packages migrating
[18:33] <davmor2> oSoMoN: thanks
[18:34] <kenvandine> robru, pete-woods: thx, i hadn't noticed it was ready to publish :)
[18:34] <robru> kenvandine: pete-woods you're welcome
[20:42] <bfiller> popey: if you get a chance need a review of new gallery-app
[20:42] <bfiller> in store
[21:44] <robru> veebers: hah, for real this time?
[21:44] <veebers> robru: heh, it was for realz last time too but got changed back :-P
[21:45] <robru> veebers: you didn't ask me to publish it when we discussed it though
[21:45] <robru> veebers: anyway do you want me to publish it now?
[21:49] <veebers> robru: ah right, due to the confusion and another comment I wanted to double check the testing. Yes please :-)
[21:49] <robru> ok
[21:50] <veebers> robru: awesome, thanks
[21:51] <robru> veebers: you're welcome