[04:57] veebers: do you have any reply for this? https://code.launchpad.net/~townsend/autopilot/fix-gcalctool-desktop-file/+merge/256702 [04:58] I wanted to tell him to change his test to do a normal launch hardcoding the app info in his branch instead, but I'm not sure if you have other plans. [05:01] elopio_: lol that fix is the opposite of the fix that we needed recently for autopilot. I have no comment, a quick fix for the legacy branch seems fine [05:01] I want to fix that within autopilot though, it's pretty crummy [05:02] elopio_: I'm off, I might be back later though [05:03] elopio_: to answer your questions: legacy reasons :-) this is really old part of autopilot / unity7 tests (i.e. launching known apps to test the desktop with). [07:26] jibel: FTR, I created wily i386/amd64 VMs everywhere, and updated most vivid->wily things in lp:a-p-t [07:27] jibel: so I guess we'll need to copy the jobs now, to give adt-britney something to chew? :-) [07:27] http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html [07:28] pitti, yep, I'll create the views on jenkins [07:29] jibel: the views are nice of course, but what will cause the actual jobs to get created? does that need further changes somewhere? [07:29] jibel: or just the RELEASE= bit in a-p-t? [07:29] pitti, no, that won't create the job, I'll create the job afterwards, otherwise I won't be able to see what is created automatically [07:30] actually I might not be able to do that anymore, they removed my privileges [07:30] I'll try [07:30] jibel: want me to copy/set up setup-testbed and setup-lxc for now? [07:30] jibel: or will that get in the way of your mass-copy? [07:30] pitti, i'll do it [07:31] *nod* [07:31] jibel: we'll need to leave setup-testbed disabled for now (I'll update the VMs manually every now and then until we get cloud images) [07:43] pitti, you setup proposed-migration on snakefruit? [07:43] jibel: I didn't; if you tell me how, I'm happy to [07:43] pitti, someone did it apparently [07:44] jibel: then infinity, I guess [07:44] jibel: he asked me this morning about adt-britney support for wily [07:44] ok [07:44] jibel: I pulled a-p-t there now [08:36] jibel: can we disable the old-style VMs part in http://d-jenkins.ubuntu-ci:8080/job/wily-adt-setup-testbed/configure and enable your new DKMS bit now? [08:37] pitti, no, not yet, we still need it for custom kernels [08:37] jibel: I'll verify and enable setup-lxc [08:37] jibel: ah, I'll build the old-style VMs for wily on wazn then [08:37] pitti, the new dkms bit only works for the default kernle [08:37] jibel: ok; can we still turn this on to see how it goes? [08:38] pitti, sure, I'll push the code [08:38] pitti, don't you prefer to wait for a first successful run of britney? [08:39] jibel: ah, ok [09:40] DanChapman: thanks for wanting to look into the automatic image testing issues! [09:43] ubuntu-qa - a review of https://code.launchpad.net/~canonical-platform-qa/unity-scope-click/wait_for_search_button/+merge/258002 much appreciated [09:45] brendand_: why the _ ? [09:52] davmor2, dunno [09:52] davmor2, won't let me change it [09:52] davmor2, probably someone else logged in with it [09:58] pitti, there are 2 jobs in the queue but no executors [09:59] jibel: because of the long build queue? [10:00] http://d-jenkins.ubuntu-ci:8080/job/wily-adt-mpich/1/console [10:00] jibel: that just says that it's waiting for an executor? [10:00] pitti, yes [10:01] pitti, new glibc in vivid? [10:01] jibel: new KDE [10:02] ah [10:02] + new kernel [10:28] jibel: old-style VMs created for wily on wazn [10:40] pitti, thanks, I'll find some time to finish porting the old-style dkms tests to autopkgtest [10:53] jibel: http://d-jenkins.ubuntu-ci:8080/view/Wily/view/AutoPkgTest/ \o/ [11:43] pitti, do you want me to trigger $world for wily or wait a bit? [12:33] jibel: oh, do we need to? i. e. not just copy the last successful result? [12:33] pitti, no we don't have to [12:33] jibel: if so, sure -- aside from armhf the queues have caught up [12:34] but we need to copy the last successful vivid result either way, no? [12:34] pitti, history has been copied over from vivid, it's all good [12:34] to detect regressions [12:34] ah, great [12:34] jibel: many thanks [12:34] lets save some CPU cycle and some trees :) [12:35] pitti, I'll wait next publisher run to make sure results are copied back to britney and push the code to enable dkms [12:36] \o/ [13:02] pitti, results have been synced. pushing the patch for dkms [13:08] well, I've to fix the grep-dctrl command first :) === elopio_ is now known as elopio [13:25] pitti, the expression in detect in autodep8 returns 23 dkms packages while there are 40 in vivid [13:25] with main, universe, restricted and multiverse enabled [13:33] nm, if I consider all the apt index files it's better :) [13:39] pitti, so, there'll be some dkms packages missing because proposed migration only uses sources files [13:41] for example there is nothing in restricted_source that tells if nvidia is a dkms package or not [14:50] jibel: ah, I thought we were looking at binary packages [14:50] jibel: wrote that down as TODO, it's quick email/UOS time now [14:52] pitti, proposed-migration reads source packages for an XS-Testsuite header matching autopkgtest. The place where we added dkms detection will read the same sources [14:53] pitti, anyway we can start with that [14:53] jibel: agreed, let's see how these 24 perform now [14:53] pitti, okay to push http://paste.ubuntu.com/10990321/ ? [14:54] pitti, it's basically the same thing we did at the sprint fixed to be python compliant [14:55] (removed some quotes and escape characters and use source files instead of debian/control) [14:55] jibel: LGTM, let's roll with that and see how it goes? [14:55] jibel: and we'll refine later (maybe just add a static list for now) [15:21] pitti, pushed [15:22] jibel: go, go, go! :-) [15:23] jibel: now we just need to upload something which triggers them :) [15:23] pitti, I'll tail britney's logs before cjwatson pings me telling I broke it ;) [15:29] vila: fgimenez: published the trusty versions. [15:29] I think. I'm still a newbie with ppas. [15:30] elopio, ok thanks lot, i'll relaunch the job [15:32] elopio: right, you copied the vivid versions ;) recipes are a bit easier to build for multiple releases at once (and provide clearer versions too IMO) [15:32] elopio, perfect, it liked your ppa ;) [15:33] vila: how do I make a recipe? [15:33] ah, nevermind. I'll just search the launchpad docs when I have some free time. [15:35] elopio: from a branch you click the 'Create packaging recipe' button [15:35] elopio: the most painful part is to select the target PPA in the huge list [15:46] hello [15:46] balloons receiving some bad news about the LXD session, tych0 realizing he has a conflict [15:51] tych0, ohh.. when can we reschedule? [15:52] balloons: i could do tomorrow at the same time? [15:54] alesage, you should have the power to move things around. [15:54] tych0, we are full schedule but we can try and fit. if you can't do it today, you can't do it :-) [15:54] balloons: yeah, sorry [15:54] meaning, we'll make it work for later [15:54] balloons, will this make a conflict with an existing session? --right ok [15:54] well, or anyt ime really [15:54] sorry, not to confuse. I mean, if today doesn't work, pull it off the schedule and we'll make it work later [15:55] balloons: sure, understood [15:55] but it will be hard. just have a look at the schedule and see [15:56] balloons, tych0 there's an empty slot Thursday 16:00 ? [15:57] tych0, which I think is 3:00 PM for you? [15:57] alesage: 1600 UTC? [15:57] tych0, yessir [15:58] hm, i think that's 10AM MDT unless i'm misunderstanding [15:58] tych0, or sorry, 10:00 AM my mistake in CO [15:58] but yeah, that works [15:58] tych0, you're right, I'm bad at math [15:58] tycho ok I'll move the session if you're willing :) [15:58] alesage: sure, works for me [15:58] tych0, great [18:49] elopio, ready for the helpers session. [18:49] balloons: almost, just recording the last demo. [18:49] I'll set everything up [18:54] balloons: can you send the official documentation links to the channel when we start? [18:55] I have my history full of old links [18:55] elopio, yes [18:58] veebers: #ubuntu-uos-appdev [19:56] balloons: the three unity8 branches are in a silo. After that lands, we can propose the namespace refactor + sphinx. [20:03] elopio, awesomeness [20:20] Hello :) [20:25] All to work? ;-) [20:32] bip: hello [20:33] Hello elopio :) [21:37] hi bip [21:38] Hey man! sorry for disturb! :) [21:38] You can test ISOs on virtual machines if you want, it sppeds up the process of testing so most people use VMs [21:38] *speeds [21:39] Noskcaj: ok. There's a standard option for a good testing? Type 1 Gb ram - 20 gb hdd etc? [21:39] That should be enough, as long as there is enough hdd space to install, anything should work [21:40] Noskcaj: you're a ISO Tester? [21:41] I started my ubuntu contributions with iso testing, i mostly do packaging work now [21:41] Noskcaj: perfect i think is a good start for me in this team :) [21:41] :) [21:41] Noskcaj: can you help me in this startup ? [21:42] sure. [21:42] If you're using a GUI, you might want to have a look at the program "testdrive" [21:42] It's not super well maintained, but it allows you to sync the current iso and automatically makes a VM with it [21:43] Noskcaj: yes on server i got KDE. This becouse i make some Organizzation Test :) [21:45] Donwload. [21:46] Noskcaj: very good idea. Thx you. Now I'm download Vivid-Desktop-amd64.iso (10 min)