[00:31] <phillw> hi good people, with reference to bug 1098080 has an SRU request been made? We confirm it works in raring.
[00:31] <ubot2> Launchpad bug 1098080 in testdrive (Ubuntu) "Testdrive gets stuck on "configuring Virtual Machine" if Virtualbox 4.2 is installed" [Undecided,Fix released] https://launchpad.net/bugs/1098080
[01:28] <cjohnston> phillw: it does not look like an SRU request has been made
[01:30] <phillw> cjohnston: thanks, should I go ask https://launchpad.net/~bkerensa to make this? I'm not 100% sure on SRU things, but have managed to get one through (with a lot of help) :)
[01:32] <infinity> phillw: Anyone can propose it for other series', but if you do, you should also fill out the usual SRU boilerplate in the bug description and justify it.
[01:32] <infinity> phillw: https://wiki.ubuntu.com/StableReleaseUpdates#Procedure
[01:33] <phillw> infinity: thanks, you read my mind... I do recall being sent that link before. I'm sorry to be a slow learner on this stuff and am very grateful for all the help you guys give in pointing me to the correct areas to head for :)
[01:34] <infinity> phillw: Googling for "ubuntu SRU" brings that up on the first hit, FWIW.
[01:52] <phillw> infinity: am I any where close on getting the description updated?
[01:54] <infinity> phillw: Test cases should be instructions that people who aren't you can follow.
[01:55] <infinity> phillw: Or, more importantly, people who aren't familiar with what "Using Testdrive to gain an iso and launching it using Virtualbox will work." means.  How do I do any of that, and what does "working" versus "not working" look like?
[01:57] <phillw> Hmm, well, this should be fun :) ... I'm just going to track down Jacksons' classroom session on using testdrive for how to install it all and get iso's :)
[02:19] <phillw> infinity: am I allowed to use
[02:19] <phillw> sudo apt-get
[02:19] <phillw> ?
[02:19] <infinity> phillw: Of course.
[02:20] <infinity> phillw: This isn't meant to be an exercise in weird constraints or anything, just "if you gave me these steps, I could make the bug happen".
[02:21] <infinity> If the bug was "when I hit my laptop with a hammer, the screen stops working", the steps would be "obtain hammer, apply liberally to laptop, observe".
[02:21] <phillw> infinity: it is not taken as. I've been told off by pleia2 for overly assuming things when I was writing up stuff for the classroom sessions earlier this month :)
[02:23] <phillw> just, I've got basic knowledge of Testdrive, so it will take a little while as I battle how to remove virtualbox 4.1 (in the repos) and add in 4.2 (not in the repos, but what people use).
[02:23] <phillw> I'm not even sure where to start with getting 4.2 into the repos!
[02:24] <infinity> Sure, but someone's going to need to reproduce and verify the bug is fixed, so either you need to know how so you can do it yourself, or you need to know how so you can get others to do it.
[02:24] <infinity> We're not going to get 4.2 in older releases, period.
[02:24] <pleia2> I don't tell people off :(
[02:24] <infinity> Getting it in raring probably means getting it in Debian.
[02:24] <infinity> pleia2: Maybe you should start. ;)
[02:24] <pleia2> I really was trying to be helpful to improve documentation for newcomers
[02:25] <phillw> infinity: 4.2 into older releases is not a requirement. Into 13.04 would be nice.
[02:25] <phillw> pleia2: I was joking! I simply said that I have been asked to explain more clearly once, or twice, before :D
[02:26] <pleia2> ok :)
[02:29] <phillw> infinity: I just used https://www.virtualbox.org/wiki/Linux_Downloads to grab the 12.10 version, GDebi did the rest once I had un-installed 4.1 from the system. Not really sure what is going on here, but that is not the issue with the bug and SRU request.
[02:38] <phillw> infinity: do the current (12.10) *buntus have Synaptic Package Manager?
[02:44] <infinity> Probably not installed by default.  You don't need to give EXACT instructions "install this package" is enough.
[02:56] <phillw> infinity: I need to have 4.1 uninstalled as GDebi will not install 4.2 if it is there :'(
[02:59] <phillw> Is it sufficient to state 'completely remove VBox 4.1, e.g. via Synaptic Package Manager' ?
[03:04] <phillw> is apt-get --purge remove virtualbox-4.1* okay?
[03:08] <phillw> infinity micahg: sorry for keep bothering you, does https://bugs.launchpad.net/ubuntu/+source/testdrive/+bug/1098080 look reproducable?
[03:08] <ubot2> Launchpad bug 1098080 in testdrive "Testdrive gets stuck on "configuring Virtual Machine" if Virtualbox 4.2 is installed" [Undecided,Fix released]
[03:16] <micahg> phillw: makes sense, I proposed a similar fix a while back for another version
[04:01] <phillw> micahg: can I now go hunt down a bug supervisor to mark it up?
[04:03] <phillw> s/can/should/
[04:04] <infinity> phillw: I already did.
[04:05] <phillw> infinity: ahh, thanks.. I was desperately trying not to ping you guys too much :/
[04:12] <phillw> I guess you guys have had the 'one line change before' SRU request. --> "It's just a one-line change!" Rest assured, if accepted to proposed, it will be tested within the 7 day window. As well as the bug report, there is chatter on the quality mailing list about it. fingers crossed, it will not break anything. My only concern would be the other things that got added into the new release, but I'm sure you people know what you're doing :)
[04:23] <phillw> infinity: on a slightly different note, as it is more wiki based. It seems that apturl is not installed by default on lubuntu and Chromium cannot use it any ways. Is apturl 'generally' installed or should the wiki people be changing the likes of https://help.ubuntu.com/community/RestrictedFormats#Easy_Install to https://help.ubuntu.com/community/RestrictedFormats#Manual_Install I *know* this is not a release team issue, but if the quick links v
[04:23] <phillw> users at 13.04 will be scratchign their heads.
[04:25] <phillw> I ask informally before I ask people to start raising bugs.
[04:30] <infinity> phillw: And why can't apturl be made to work with chromium-browser?
[04:31] <infinity> phillw: That would be the correct answer, IMO.
[04:33] <phillw> infinity: I 100% agree, however https://code.google.com/p/chromium/issues/detail?id=152400 is a an unloved bug.
[04:33] <phillw> -a
[04:34] <infinity> phillw: I see no reason this needs to be fixed in chrome/chromium.  Writing an extension to handle apt: URLs should be fairly trivial.
[04:35] <infinity> phillw: As in, this should be the responsibility of flavors who want to use chromium by default, not upstream.
[04:35] <phillw> there is an extension. https://chrome.google.com/webstore/detail/apt-linker/oljmaangfgmmokjpnojhfblppgeijikp?hl=en
[04:36] <infinity> Yeah, I already stumbled on that, it looks incomplete and a bit broken.
[04:36] <infinity> Plus scary, in that it parses random text in web pages, instead of well-formed apturl lines.
[04:36] <infinity> Installing that by default would be pretty not okay, IMO.
[04:37] <phillw> the other side to it, is apturl installed by default? On my firefox install in lubuntu I had to install apturl. So, I'm not sure how lubuntu / Chromium specific the problem is.
[04:38] <infinity> My gut feeling is that writing an extention that just farms apt: links off to software-center wholesale would probably take someone about 10 minutes.
[04:38] <infinity> (base)adconrad@cthulhu:~$ apt-cache show apturl | grep ^Task
[04:38] <infinity> Task: ubuntu-desktop, ubuntu-usb, edubuntu-desktop, edubuntu-usb, lubuntu-desktop
[04:38] <infinity> Looks default to me.
[04:38] <infinity> With the notable exception of xubuntu...
[04:39] <infinity> Oh, and kubuntu.
[04:40] <phillw> Hmm, okies, I have a replacement usb drive ordered so I can move from virtual machines to having a 'real' machine without risk of messing up my production machine.
[04:41] <phillw> but, if apturl is missing from kubuntu and xubuntu maybe I should suggest dropping it from wiki pages and using the sudo apt-get xyz ?
[04:42] <infinity> kubuntu may do something different entirely.
[04:42] <infinity> and with xubuntu, it's likely an oversight.
[04:46] <phillw> infinity: there is another proposed way round, using http://appnr.com/ but I'm not familiar with that site?
[04:47] <phillw> I found that via http://www.neowin.net/forum/topic/951076-ubuntu-how-to-use-apturl-anywhere/
[04:48] <phillw> as they are both 'off area', I'm minded to think that we just use sudo apt-get xyz
[04:52] <phillw> For ubuntu and the default browser, which I assume works fine. for the other flavors they need to sort out this issue for themselves?
[04:53] <infinity> I have no problems with people giving both an apturl link, and manual instructions, but I think we should be trying to default to apturl type stuff, and flavours should be making that work, ideally.
[04:54] <infinity> Given that you can feed an apturl URL *directly* to software-center and it does the right thing, integrating that into a flavour's browser should be trivial.
[04:54] <infinity> The browser/extension needs to know nothing about how to parse them, just that it needs to spew it to SC and let it do the work.
[04:54] <phillw> maybe the chromium bug needs a bit of 'heat' :D
[04:55] <phillw> oh, and what software center?
[05:00] <phillw> in firefox, I'm told the apturl for lubuntu restricted extras is already there, If I select xubuntu it asks if I want to install it. what database is apturl using? I'm assuming it is checking up on the apt-get database?
[05:04] <phillw> Well, I've troubled / distracted you more than enough. As always, thank you for your patience with me. as it now 05:03 here, I had better get into my alclove for my regeneration cycle :)
[09:47]  * cjwatson clears a stuck semaphore that meant that the cdimage mirror wasn't getting updated
[09:51] <cjwatson> Now, what's up with these weird Lubuntu preinstalled build failures
[10:28] <ogra_> theer are build failures ?
[10:29] <ogra_> oh, evo crashed once again ... thats why i didnt check my mails yet :P
[10:29] <ogra_> looks like a stale lock on the builder
[10:35] <ogra_> cjwatson, oh, there is bug 1133213
[10:35] <ubot2> Launchpad bug 1133213 in Ubuntu CD Images "cdimage/bin not in PATH of subprocess.check_call" [Undecided,New] https://launchpad.net/bugs/1133213
[10:35] <ogra_> (awesome that someone uses cdimage out of the DC !)
[10:36] <cjwatson> I'll sort it out, thanks
[11:58] <cjwatson> ah, phew, lubuntu/daily-preinstalled build is behaving itself now
[11:58] <cjwatson> next, look for chaos caused by this
[11:58] <cjwatson> I've also fixed the bug that led to locks/semaphores not being cleaned up properly on Ctrl-C
[12:21] <cjwatson> And I think that's pretty much everything cleaned up now.  There might still be some oddities caused by a stale mirror, but those should sort themselves out tomorrow at the latest.
[12:26] <xnox> all sorted way before nexus7 images are croned =) so when it spins today, it should everything i hope for it to hate ;-)
[12:26] <xnox> s/hate/have/
[12:27]  * xnox failed at english.
[12:27] <Laney> not like you!
[14:50] <ogra_> cjwatson, phablet syncs -> lool works on getting the android builds happening in the cdimage area, after that (and after all packages are in raring) we will start to roll the userspace with live-build ... since none of that is there and i would have to hack up a lot in cdimage for an interim jenkins sync solution i decided to go with a simple sync script for now (currently outside of the cdimage tree, running under my own crontab on nu
[14:50] <ogra_> sakan), are you ok with that ?
[14:54] <dobey> hey all. can someone accept tomboy upload into precise-proposed ?
[14:56] <cjwatson> ogra_: It's OK as a strictly temporary measure, but could you please run it as the cdimage user instead?
[14:57] <cjwatson> Just in case anyone else needs to apply emergency fixes when you're on leave or something
[15:00] <ogra_> cjwatson,
[15:00] <ogra_> ogra@nusakan:~$ crontab -l|grep sync
[15:00] <ogra_> 35 * * * * sudo -u cdimage -i /home/ogra/sync-phablet-images
[15:01] <ogra_> already doing, else i would get permission issues writing to www and log
[15:01] <cjwatson> Ah
[15:01] <cjwatson> Grotty, but OK
[15:01] <ogra_> heh
[15:01] <cjwatson> It would be clearer to just edit cdimage's crontab for the time being
[15:01] <cjwatson> (not in bzr, just live)
[15:01] <ogra_> yeah, i might do that
[15:02]  * ogra_ does so
[15:04] <ogra_> doing these builds on our side will require some painful changes (images are a mixture of armel and armhf and have a bunch of different subarches as well as three "subimages" per subarch etc etc)
[15:38] <lool> ogra_: I am not directly working on getting android builds happening on cdimage
[15:38] <lool> ogra_: I did propose various options, but I think rsalveti, Sergio and perhaps me need to think of the more concrete steps that are ahead for some bits
[15:38] <ogra_> lool, huh ? you said you wanted to take that task when i said i was planning to work on it
[15:39] <lool> ?
[15:39] <ogra_> when we spoke last week
[15:39] <ogra_> well, chatted
[15:39] <lool> ogra_: You mean moving the mwc-demo dir around?
[15:40] <ogra_> lool, well, in the end someone will have to do it ... i'm fine doing it, but understood you wanted to
[15:40] <ogra_> lool, before the moving stuff iirc
[15:40] <lool> ogra_: I don't even know exactly what you're talking about!
[15:40] <lool> I remember offering to move stuff around the day of the release
[15:40] <ogra_> lool, building phablet images on cdimage
[15:41] <lool> Yeah, I don't recall offering that and there are many subtasks to complete around that that Sergio and/or rsalveti are in a better place to handle
[15:41] <ogra_> i told you that i'm tasked with that and you asked if you could do the android side
[15:41] <lool> like finishing the patches to the build scripts to use the new LP project names
[15:41] <ogra_> (which i appreciated)
[15:43] <lool> ogra_: I tried to grep my logs, and I can't find that; either I said and don't recall it (pointers appreciated), or someone else promised that, or we misunderstood each other
[15:44] <ogra_> hmpf, and i chatted from my chromebook which doesnt log
[15:44] <ogra_> grep for TODO
[15:44] <ogra_> i'm pretty sure i said its on my TODO
[15:45] <ogra_> or for "tasked"
[15:45] <lool> 16:26 < rsalveti> lool: I got it ported to a recent livebuild at https://code.launchpad.net/~rocket-scientists/aal+/ubuntu-build-phablet
[15:45] <lool> 16:26 < ogra> sergiusens, but i had it on my TODO for later
[15:45] <lool> [...]
[15:45] <lool> 16:27 < lool> sergiusens, rsalveti: see also email I've sent earlier today on this (lol, like you guys can read email today)
[15:45] <lool> 16:27 < ogra> if lool does it i'm fine with that
[15:46] <lool> I never said I would!
[15:46] <ogra_> heh, ok
[15:46] <lool> ogra_: sent you the log
[15:46] <ogra_> well, seems there is a lot of stuff to be sorted out before it can happen anyway
[15:46] <ogra_> so lets talk again once its ready :)
[15:47] <lool> in the context, rsalveti offers to finish porting of the live-build to new branch names
[15:47] <lool> ogra_: So much is happening that you made me doubt I had promised something and had completely forgotten about it
[15:47]  * lool is relieved now
[15:47] <ogra_> heh, sorry
[15:48] <ogra_> lool, btw, do we already have a kernel upgrade plan for these images ?
[15:49] <ogra_> (or android system upgrade plan since i think thats one blob)
[15:53] <rsalveti> lool: ogra_: I'd vote to just port when we start having the raring based image
[15:53] <rsalveti> which will happen soon I believe
[15:53] <ogra_> rsalveti, heh, well, we need all the UI bits in the archive first
[15:54] <rsalveti> ogra_: "soon" :-)
[15:54] <ogra_> :)
[15:54] <rsalveti> unless we *really* want to run lb at cdimage *now*
[15:54] <ogra_> on cdimage ?
[15:54] <ogra_> we usually dont do that
[15:54] <rsalveti> not cdimage
[15:55]  * rsalveti just woke up
[15:55] <ogra_> k
[15:55] <ogra_> do you do cross builds or native ?
[15:55] <ogra_> (i assume cross)
[15:56] <rsalveti> ogra_: the ubuntu lb runs natively with armhf builders at offspring
[15:56] <lool> rsalveti: +1
[15:56] <rsalveti> just the android part that is cross
[15:56] <ogra_> thats what i mean
[15:56] <ogra_> ubuntu userspace is clear to me already
[15:56] <ogra_> and shouldnt need more than a specific seed
[15:57] <ogra_> but we need the android side from somewhere ... and preferably properly integraded in cdimage
[15:58] <rsalveti> yeah
[15:58] <rsalveti> ogra_: do you think it'd be a problem to keep it running at jenkins?
[15:59] <ogra_> apart from the fact that its ugly to not build them in the common system we use for all images ?
[15:59] <ogra_> dunno, it would be good if we could just actually run the builds with the common commands and scripts
[16:01] <ogra_> having the images scattered across miltiple datacenters doesnt seem sane to me in the long term
[16:01] <ogra_> *multiple
[16:03] <ogra_> and even then, cdimage must be able to trigger builds etc at release times so we would definitely need to integrate jenkins with it to be able to run builds etc, i'm not sure if its clever to do that on a system where the cdimage team has no control
[16:04] <ogra_> dunno what other cdimage team members think about it
[16:05] <cjwatson> By an order of magnitude, I'd prefer being able to run it in our usual configuration - that is, ssh to a machine with an ssh trigger set up to run BuildLiveCD
[16:05] <ogra_> yeah
[16:05] <cjwatson> If it's already based on live-build this shouldn't be that hard
[16:05] <ogra_> same for me
[16:05] <cjwatson> And it will be way easier to integrate than having to invent something to deal with jenkins
[16:05] <ogra_> well, not sure about the cross built android bits
[16:05] <ogra_> i guess that would need to be run from some cdimage command on the x86 builder
[16:06] <ogra_> for the ubuntu userspace live-build already has what we need, the android parts are buiolt from a git tree though, we would need something that handles this
[16:07] <cjwatson> Sounds like those could reasonably be separate-ish build jobs which we than collate
[16:08] <ogra_> well, but we would have to be able to trigger them as well
[16:08] <cjwatson> Yeah
[16:16] <rsalveti> cjwatson: ogra_: sure, we'll get there, was more concerned about the timeframe for it
[16:17] <rsalveti> I'd suggest the full migration to be part of the quantal -> transition
[16:17] <rsalveti> *-> raring
[16:19] <ogra_> yeah
[16:28] <lool> rsalveti: (sorry for putting you on the spot here!)
[16:29] <lool> rsalveti: Yes; I think it makes sense to get the livefs builds working on raring on developer machines, then look at scheduling builds on livefs builders; I don't think we need to use jenkins for that, but I definitely think we ought to use jenkins for the android cross-builds for now
[16:29] <lool> rsalveti: I was also thinking we could look at building some parts of the phablet images relatively soon for raring such as boot.img
[16:31] <rsalveti> lool: these android specific parts are not depending on the ubuntu series
[16:32] <rsalveti> lool: ogra_: and when I say we should worry about this during raring transition is that I know we still have a lot to come even from the architecture perspective
[16:32] <rsalveti> like if we're able to make ubuntu as the main host, then the way we're building the android part will change completely
[16:32] <lool> Yeah
[16:33] <rsalveti> we might not even need jenkins/etc
[16:33] <lool> There are some interdependencies between Ubuntu and Android changes too for now
[16:33] <ogra_> i guess there will always be
[16:33] <lool> So I'd wish for some way to track which Android bits we combine with which Ubuntu raring bits fairly closely
[16:34] <ogra_> and thus i think its even essential that both come out of the same build infrastructure
[16:34] <lool> Yup; eventually they should
[16:34] <rsalveti> sure
[16:34] <ogra_> and i agree that we dont need jenkins for that in the long term
[16:35] <lool> rsalveti: So you're the one currently porting the lb configs to the public branches and to raring?  Didier mentioned a list of branches he had published, but I'm not sure how to track progress of the raring merge/rebase of the phablet packages
[16:35] <ogra_> we should just have a cross build machine where cdimage can trigger the builds via ssh ... as cjwatson descrived above ...
[16:35] <ogra_> largely how we use live-build today but well, wirh a make command on the other end
[16:35] <lool> I think cjwatson meant the livefs builds; not sure about the cross-built bits
[16:36] <lool> but indeed, I guess we could use livefs x86 builders for that; not a bad idea
[16:36] <rsalveti> lool: yup, we'll be discussing and coming to a better plan about the transition this week
[16:36] <rsalveti> there are still a lot to packages to port to raring
[16:36] <ogra_> right, and have something like live-cross ... that builds the three android images
[16:36] <ogra_> yeah
[16:36] <rsalveti> and the unity* ones are kind of a concern
[16:36] <ogra_> no hurry yet
[16:37] <rsalveti> yup, lot of fun ahead :-)
[16:37] <ogra_> but we should have a UDS discussion and blueprint imho
[16:37] <ogra_> to plan that properly
[16:38] <lool> rsalveti: Ack; sounds all good -- and fun  :-)
[16:39] <ogra_> rsalveti, the other thing spinning in my head are upgrades of the android side ... do you already have plans for that ?
[16:40] <ogra_> i assume we'll just mount recovery and dump the zip in and reboot or some such
[16:43] <rsalveti> ogra_: yup
[16:43] <rsalveti> ogra_: that will come this/next week
[16:43] <ogra_> great
[16:43] <rsalveti> ogra_: as you see, all to be investigated/discussed still :-)
[16:43] <ogra_> yeah
[16:43] <ogra_> thats the exciting bit :)
[16:43] <rsalveti> yeah :-)
[16:44] <rsalveti> new stuff, everybody is excited :-)
[16:44] <rsalveti> which is good
[16:44] <ogra_> yup, and we even win prizes with a half way done system :)
[16:44] <ogra_> thats so awesome
[16:47] <rsalveti> ogra_: yeah :-)
[17:42] <lool> ogra_: I see a new image was pushed today; would you be tempted to send an udpate to phablet-tools to point at it?
[17:42] <lool> ogra_: a mp against lp:phablet-tools, and then check how to land it in Ubuntu
[17:42] <ogra_> lool, i think sergio just did
[17:43] <lool> cool
[17:43] <ogra_> should have a switch to use dailies
[17:43] <lool> uploaded as well?
[17:43] <ogra_> duno, i just saw rsalveti signing it off
[17:44] <ogra_> so it will be soon, if it isnt yet
[17:44] <rsalveti> lool: ogra_: CI should publish the package automatically soon
[17:44] <rsalveti> the branch was merged
[17:45] <ogra_> great
[17:56] <lool> rsalveti: awesome, so which jenkins is this?
[18:28] <dobey> any archive admin around? if so can someone please approve https://launchpad.net/ubuntu/precise/+queue?queue_state=1&queue_text=tomboy
[18:29] <infinity> dobey: Changing the bug task to fix committed made it somewhat difficult to notice that one series wasn't.
[18:29] <cjwatson> dobey: done
[18:30] <cjwatson> And yes, agreed with infinity, DDT please
[18:34] <dobey> sorry. i didn't realize it wasn't approved then. pitti had marked the merge proposal 'merged' which suggested it was, and i noticed that it wasn't fix committed on the bug.
[18:51] <cjwatson> ogra_: is that kubuntu-active build failure just now you working on nusakan, or is it my breakage?
[18:52] <cjwatson> cardamom's the i386 builder so I'm going to guess it's my fault :-(
[18:52] <cjwatson> oh, no, kubuntu-active defaults to i386
[18:53] <cjwatson> except why are preinstalled builds enabled for it ...
[18:53] <cjwatson> I guess somebody must be working manually
[18:53] <infinity> Sounds like Oli, yes. :P
[19:30] <ogra_> cjwatson, that was a manual test build
[19:31] <ogra_> i didnt make any code changes or anything, just tried a build with ARCHES set to see what happens
[19:31] <ogra_> sorry if that caused confusion
[19:34] <ogra_> i didnt get any build failure mail :/
[19:37] <ogra_> oh, full disk ... hmm
[19:38] <ogra_> and there it is
[19:39] <ogra_> urgh
[19:47] <ogra_> cjwatson, hmm, so i used "ARCHES=armhf+nexus7 for-project kubuntu-active cron.daily-preinstalled", looking at livefs.py i dont see how it could pick the x86 livefs builder instead of celbalrai.buildd
[19:54] <ogra_> ogra@nusakan:~$ PROJECT=kubuntu-active /srv/cdimage.ubuntu.com/bin/find-live-filesystem armhf+nexus7 rootfs.tar.gz
[19:54] <ogra_> sh: 49: /srv/cdimage.ubuntu.com/etc/config: default-arches: not found
[19:54] <ogra_> http://celbalrai.buildd/~buildd/LiveCD/raring/kubuntu-active-nexus7/current/livecd.kubuntu-active-nexus7.rootfs.tar.gz
[19:54] <ogra_> hmm, that looks okayish too
[20:10]  * ogra_ doesnt see where the error could be ...
[20:16] <ogra_> Riddell, som the livefs build succeeded ... but i cant convince buildlive to accept armhf+nexus7 for it in teh right way ... i'll go on inspecting that tomorrow
[20:16] <ogra_> err
[20:17] <ogra_> s/buildlive/for-project/
[20:19] <Riddell> ogra_: thanks, probably some confusion about what it image name and what is image type
[20:20] <infinity> ogra_: Don't you mean ARCH=, not ARCHES=?cdimage@nusakan:~$ default-arches kubuntu-active daily-preinstalled raring
[20:20] <infinity> i386
[20:20] <infinity> Err.
[20:20] <infinity> TYPING FAIl.
[20:20] <infinity> cdimage@nusakan:~$ default-arches kubuntu-active daily-preinstalled raring
[20:20] <infinity> i386
[20:20] <ogra_> well, i looked through all the code and ran each bit individually, they all seem to DTRT
[20:21] <ogra_> cdimage@nusakan:~$ ARCHES=armhf+nexus7 buildlive kubuntu-active daily-preinstalled && ARCHES=armhf+nexus7 for-project kubuntu-active cron.daily-preinstalled
[20:21] <ogra_> kubuntu-active-armhf-nexus7 on celbalrai.buildd starting at 2013-02-26 16:55:03
[20:21] <ogra_> kubuntu-active-armhf-nexus7 on celbalrai.buildd finished at 2013-02-26 18:30:18 (success)
[20:21] <ogra_> You have new mail in /var/mail/cdimage
[20:21] <infinity> ogra_: You have no daily-preinstalled for kubuntu-active in etc/default-arches
[20:21] <ogra_> infinity, why did the buildlive command DTRT then (and yeah, emabrrasing))
[20:21] <ogra_> (or if i could type ...)
[20:22] <ogra_> infinity, yes, on purpose since i wanted to set ARCH manually (which i obviously failed :P )
[20:23] <infinity> 'ARCHES=armhf+nexus7 for-project kubuntu-active cron.daily-preinstalled' seems to work here...
[20:23] <ogra_> yeah, i just clashed with you
[20:23] <ogra_> sacry errors that throws
[20:23] <ogra_> *scary too
[20:28] <ogra_> infinity, well, your command only does a mirror sync up to now
[20:28] <ogra_> ah, and failed the same way
[20:29]  * ogra_ tries with ARCH
[20:29] <infinity> No, I was wrong about ARCH.
[20:29] <ogra_> oh
[20:29] <infinity> That was the typing fail, I meant to delete that line. :P
[20:29] <ogra_> heh
[20:31] <ogra_> and guess what, ARCH indeed failed the same way, it seems to ignore it written either way
[20:32] <ogra_> but i see etc/config parsing it
[20:35] <infinity> PROJECT=kubuntu-active find-live-filesystem armhf+nexus7 rootfs.tar.gz
[20:36] <infinity> ^-- That behaves.
[20:36] <ogra_> yes, see above
[20:36] <infinity> Ahh, yes.
[20:37] <ogra_> download-preinstalled-filesystems also looks fine (i didnt run that one though)
[20:37] <ogra_> somewhere at the toplevel ARCHES gets reset i assume
[20:38] <infinity> Oh well.  Just set up etc/default-arches, and worry about ARCHES later? :P
[21:40] <cjwatson> ogra_: ARCHES - fixed in trunk
[21:40] <cjwatson> ogra_: I just didn't expect anyone to be trying this before I had a chance to merge it :)
[21:41] <cjwatson> ogra_: try again no
[21:41] <cjwatson> w
[23:48]  * ScottK suspects release engineering is about to get much simpler.
[23:49] <TheDrums> Bleh, another flash update...
[23:50] <infinity> ScottK: I wouldn't bank on it.
[23:50] <ScottK> UDS every three months makes no sense with a 6 month release cycle.
[23:52] <knome> from the flavor point of view, i'm not sure how it'll make communicating with other teams any easier than it is now. judging that, i'm not sure if uds is rendered useless for flavors.
[23:52] <ScottK> knome: I think it's rendered useless period.
[23:53] <knome> ScottK, unfortunately it seems like it
[23:53]  * ScottK certainly isn't going to take a week off of work to do Google+.
[23:53]  * knome isn't going to join G+
[23:53] <jbicha_> if there's enough backlash, they could keep 1 in-person UDS a year at least
[23:54] <knome> if that's in the states, it doesn't make it much easier for our team than an online udes
[23:54] <knome> -e
[23:54] <ScottK> Wait until release schedule changes are announced.  Two UDS's per release doesn't make any sense, so I think there is another shoe waiting to drop.
[23:54] <ScottK> And I doubt they are about to double the number of releases.
[23:55] <knome> ScottK, does that comment imply you have some inside information with your release team hat on? :P
[23:55] <ScottK> No.
[23:55] <ScottK> That's me inferring stuff from what I've heard.
[23:55] <ScottK> AFAIK there's been no discussion of the UDS change (or any other) outside Canonical.
[23:55] <jbicha_> ScottK: maybe that's what we're supposed to discuss next week since there's little time for blueprints
[23:56] <knome> ScottK, why would there? in the end, it's canonical-driven event. if the community wants, nothing stops us creating our own
[23:56] <ScottK> I've no idea.  I'll read about it afterwards.
[23:56] <ScottK> I kind of have work commitments for next week already.
[23:57] <ScottK> knome: If Ubuntu, the project, is a free software project that's bigger than Canonical, then that's not accurate (and other corporations sponsor UDS too).
[23:57] <knome> not without canonical though
[23:58] <knome> it's clear that uds brought big benefits for canonical internal communication as well, no doubt there
[23:58] <ScottK> True.
[23:58] <knome> that's one of the reasons i don't really get it
[23:58] <ScottK> That was also true because most of them were there the week before.
[23:59] <ochosi> i would assume it's primarily a monetary issue