[03:17] <tonyyarusso> txwikinger: Something's breaky about the web site and I'm not sure why yet - http://ubuntu-ca.org/ works fine, but http://www.ubuntu-ca.org/ goes to some blank Jesus-y site.
[14:52] <dscassel> Oh, awesome! http://ubuntu-ca.org/ is switched over. :D
[15:47] <txwikinger> tonyyarusso: fixed that
[16:53] <tonyyarusso> txwikinger: excellent.
[18:14] <infoverload> hi, does anyone here dual boot ubuntu with windows 7?
[18:17] <dscassel> infoverload: Yes, but not often.
[18:18] <infoverload>  I was just wondering whether you run something so you are able to access ubuntu files from windows 7?
[18:37] <dscassel> I used the ext2 driver on Windows XP, but I haven't tried it with Windows 7.
[18:37] <infoverload> hmmmm
[18:59] <Yompa> I run dual with 7 too on my desktop. Haven't looked for any ext drivers, that would actually be handy sometimes.
[18:59] <infoverload> where is hypatia these days? haven't seen her lately?
[19:01] <dscassel> infoverload: end of term and exams.
[19:02] <infoverload> ahh


 @craigbass76 [<craigbass76> Anyone got a recommendation on how to get live video from my Nikon …], Do you mean Live Streaming?
[00:27] <craigbass76> studiobot, Yes, and I'm reading that I'm out of luck
 Lol. I think you can do it via the Snapbridge app via Android. But, I can do some research for you
[00:28] <craigbass76> Just got qdsrldashboard running, and I can SEE the live stream, but can't record it.
 Aye, let me check it out, I do have a nearby d3500
[00:30] <craigbass76> And I've got my son's Canon here, but can't do the livestream. I've got one other kid with a camera (sony I think) that I can try.
[00:31] <craigbass76> I can just stick whatever on a tripod and hit go that way, but someone's lost the camera mount for the tripod...
[00:31] <craigbass76> Damned kids.
 It says Qdslr only works with Nikon
[00:32] <craigbass76> Fah... Well, it sort of lies then, I guess. I can snap a picture on a Canon with it too.
[00:33] <craigbass76> It was nice anyway. His camera is sporting the strap that was on my mother's 70's Fujica (the one I used in high school). My other son's SOny is sporting the lenses...
 Wait, Does d3300 have wifi?
 Or just bluetooth?
[00:36] <craigbass76> I haven't a clue.I have a D3200. This is my first digital camera -- I'm tried to make it act as close to a Pentax K1000 as I can.
 XD
 Hmm. I would try to get a capture card to be honest.
[00:38] <craigbass76> I know, eh? And I made it a rule when the kids got theirs "No auto anything. You will understand fstop, focus, ISO, and shutter speed, or I'm taking it back to the store."
 As DSLR camera's aren't really meant to live stream. The sensors can overheat quickly
 I 100% agree
 I love the manual mode of DSLR
[00:39] <craigbass76> Yeah, I was just hoping for something better than my webcam. I'm giving bass lessons to a kid from church, and wanted to stick something up on youtube for him
[00:40] <craigbass76> What I really love about DSLR is no darkroom.  As soon as you throw the card into a laptop, you know.
 Yeah, best thing is to probably get a capture card.
[00:40] <craigbass76> There is something to be said for the smell of fixer though...
 lmfaooo
[00:41] <craigbass76> And the feeling of developing color prints (room is darker than four feet up a bear's behind -- no red light like in B&W photography)
[00:42] <craigbass76> I was in high school in the early 90s, so we had a darkroom.
 Manual ISO settings does wonders
[00:44] <craigbass76> You can screw with stuff. Maybe you WANT grainy.
[00:44] <craigbass76> Same with shutter speed and fstop. Maybe you WANT blurry all around, or just in the background.
[00:44] <craigbass76> I think flowers was what I taught them depth of field with.
 @craigbass76 [<craigbass76> You can screw with stuff. Maybe you WANT grainy.], Anyways, let's move this conversation to Ubuntu Studio Cafe
[00:47] <craigbass76> SOrry. I'm done. :)
 No problem mate
[00:48] <craigbass76> Well, about that. Anyone know how to get hydrogen and ardour running at the same time?
 You can run them together like plugins, Check out Jack-Transport
 Take a look here
 https://www.youtube.com/watch?v=fEduGnD6ZKQ
[00:50] <craigbass76> I'll make a note and look it up next time I'm downstairs on the big box. I record in the basement. I want my album to be a big cellar.
[00:50] <craigbass76> Nyuck nyuck nyuck
 xD
[00:52] <craigbass76> Toodles, folks. So long, and thanks for all the fish.
[03:37] <MntJolt> Hey I Have a question
[03:38] <MntJolt> What makes Ubuntu studio (other than the additional software) better than regular Ubuntu
[03:56] <DirtyEar> Hi I am from Colombia
[03:57] <DirtyEar> I have a pc with Ubuntustudio and I have the mixer Behriger XR18 but I cannot setup my xr18
[03:59] <DirtyEar> Is there any way to install some driver in order to configure it as the main output device in my ubuntustudio?
[04:12] <krytarik> MntJolt: Someone from the Studio team who actually does any audio work would probably have to answer any further question, but things that come to my mind are: 1.) lowlatency kernel, 2.) Ubuntu Studio Controls, and 3.) various configuration tweaks to improve audio work further.
[04:13] <krytarik> DirtyEar: Sorry, I can't help you there.
[04:15] <DirtyEar> No problem.
 Did you try working with Jack?
[11:22] <tomreyn> https://i1.ytimg.com/vi/xHKZvL4WICw/hqdefault.jpg
[14:39] <dirtyear> Hi, I have ubuntustudio and my audio interface is a Behringer XR18 but It does not sound anything.
[14:40] <dirtyear> Is there any way to install my interface in UbuntuStudio?
[14:41] <Eickmeyer> dirtyear: It should just work and show up in Ubuntu Studio Controls. I used to use X32s all the time.
[14:41] <Eickmeyer> !ubuntustudio-controls
[14:41] <dirtyear> Thanks a lot. I will try
[14:47] <dirtyear> It shows me only "USER SETTINGS" and "SYSTEM SETTINGS" but It does not show anything else and I cannot change anything
[14:47] <dirtyear> Any idea?
[14:50] <dirtyear> I already do it!
[14:51] <dirtyear> I look for "Control de Volumen de PulseAudio" and in the last part in "configuration" I just shut down the internal audio card and it works.
[14:52] <dirtyear> Thanks for always be willing to help me. Thanks a lot!
[15:01] <Eickmeyer> dirtyear: What version of Ubuntu Studio?
[15:02]  * Eickmeyer suspects 18.04
[15:02] <Eickmeyer> !ubuntustudio-backports | dirtyear
[15:02] <OvenWerks> Eickmeyer: It appears they were looking to get desktop audio working
[15:03] <OvenWerks> Eickmeyer: so just setting the default device in pulse was what was needed
[15:03] <Eickmeyer> OvenWerks: Yeah, going into an 18-input mixer it's going to default to channels 1 and 2 though.
[15:03] <Eickmeyer> In my experience, that's highly undesirable, but oh well. ¯\_(ツ)_/¯
[15:03] <OvenWerks> :)
[15:04]  * OvenWerks is still aiting for a 1394 PCIe card
[15:06] <dirtyear> Thanks to all of you. I really appreciate your help!
 Word, 1394 pcie cards. I have a few firewire devices I'd love to use.
[16:34] <Eickmeyer> @SomeIrrelevantPerson0000: Better support for 1394 cards is coming.
 Yessssssss
 I have a laptop that has a 1394 port on it, I had recently retrofitted with KXStudio. Haven't tried it out though
[16:45] <Eickmeyer> !kxstudio | @SomeIrrelevantPerson0000: FYI:
 I know this. :)
 I just have a really outdated laptop, and just KXStudio is lightweight enough.
 I do however support Kxstudio. Although, I understand it is probably rude to speak of it here.
[18:47] <OvenWerks> @SomeIrrelevantPerson0000: I don't think it rude to talk about kxstudio really. We are working on bringing the most useful packages into ubuntu so you can just install from the ubuntu repos.
[18:52] <OvenWerks> We have already brought in Carla and it looks like Catia will be coming too. I think the kxstudio dev is hoping to make all his packages available from debian/ubuntu repos as he has a lot less time to keep up kxstudio. We are not upset with him or agaist his software, only the way in which some of his packages cause trouble when used with other ubuntu software... cadence in particular once it has
[18:52] <OvenWerks> been run can not be easily removed from your system without removing files from various places by hand. This makes it really hard to help someone who has had trouble with their audio.
 Ahh. I see


[00:28] <tsimonq2> why does xenial only have -16 when wily has -17? ()
[00:28] <tsimonq2> *(kernel)
[01:03] <Daekdroom> tsimonq2, Xenial was synced before -17 was released, most likely.
[01:03] <Daekdroom> This is not something unusual to happen during development. Firefox stays behind every development cycle...
[01:04] <tsimonq2> Daekdroom: when will it be fixed? and why aren't you updating Xenail and THEN backporting to wily?
[01:04] <tsimonq2> *xenial
[01:04] <Daekdroom> I don't know why I'm doing anything. I'm not an Ubuntu developer.
[01:04] <Daekdroom> besides, Wily is the released version. It's the one that needs all security fixes asap.
[01:05] <Daekdroom> xenial isn't supposed to be used in production systems in the first place.
[01:05] <Daekdroom> I'm just saying this is not the first time I see something like this happen.
[01:06] <tsimonq2> Daekdroom: when will it happen where Xenial gets it first? or does someone have to do that
[01:07] <Daekdroom> tsimonq2, actually, -17 isn't even released for wily
[01:07] <Daekdroom> It's in -proposed
[01:07] <Daekdroom> Both have 4.2.0-16 kernels...
[01:08] <tsimonq2> Daekdroom: but it isn't in Xenial proposed
[01:08] <tsimonq2> why is that?
[01:09] <Daekdroom> Not sure. That's something up to Canonical Kernel Team, I think. Probably not a priority.
[01:09] <Daekdroom> I mean, Xenial doesn't even have daily builds yet.
[01:10] <tsimonq2> Daekdroom: yes it does
[01:11] <Daekdroom> Huh. /topic needs to be updated, then.
[01:11] <tsimonq2> http://cdimage.ubuntu.com/lubuntu/daily/current/
[01:11] <tsimonq2> at least for Lubuntu :P
[01:11] <tsimonq2> and Ubuntu http://cdimage.ubuntu.com/ubuntu/daily-live/current/
[01:12] <tsimonq2> Daekdroom: so is this versioning situation only with the kernel, or with other packages as well?
[01:12] <Daekdroom> tsimonq2, like I said, I've seen it happen before with Firefox.
[01:13] <Daekdroom> But why even bother about a bugfix release of a kernel? It's not like Xenial will end up using 4.2
[01:14] <tsimonq2> but regardless, who makes the decision on that? why does wily get something before xenial?
[01:16] <tsimonq2> Daekdroom: or is it package-by-package?
[01:16] <tsimonq2> Daekdroom: and regardless, doesn't somebody make that decision with Debian imports?
[01:18] <Daekdroom> I believe it's package by package.
[01:21] <Daekdroom> Packages imported from Debian are synced atleast once per development cycle, up to the DebianImportFreeze point
[01:21] <Daekdroom> https://wiki.ubuntu.com/DebianImportFreeze
[01:21] <Daekdroom> (Kernel is not treated as that, though)
[08:15] <Fudge> yesterdays xenial image fails at live boot drops to a busybox prompt. is that still the case?
[08:17] <Fudge> actually the current one
[11:05] <BluesKaj> Hiyas all


[00:21] <robru> jhodapp: that looks like a network error to me, feel free to retry
[02:10] <imgbot> [02:14] <jhodapp> robru, cool
[03:10] <imgbot> [03:20] <imgbot> [03:20] <imgbot> [04:01] <elopio> ping cihelp: somebody around to check some weird errors on the devices?
[04:02] <elopio> https://jenkins.qa.ubuntu.com/job/generic-deb-autopilot-runner-vivid-mako/752/
[04:02] <elopio> this was not happening a couple of hours ago. Things fail on settle, and we are getting crashes.
[04:20] <imgbot> [04:20] <imgbot> [07:29] <michi> ci-help: cloud-worker-09 is running ridiculously slowly, causing our tests to fail. Can someone please fix it or take it off-line?
[08:25] <robru> michi, cant help you, but ping cihelp for a response (no hyphen)
[08:25] <michi> robru: Ah, thanks! Sorry for that!
[08:26] <robru> michi, youre welcome. Bedtime for me!
[08:26] <michi> Sure. Thanks for the heads-up!
[08:42] <vila> michi: which job are you seeing ? The history for cloud-worker-09 (http://s-jenkins.ubuntu-ci:8080/computer/cloud-worker-09/builds) doesn't seem that bad
[08:42] <michi> vila: sec…
[08:44] <michi> vila: Maybe it’s not limited to cloud-worker-09
[08:44] <michi> Basically, we are seeing totally ridiculous test failures. They can happen only if the machine runs like a dog.
[08:44] <michi> As in less than 1/5th the speed of a Nexus 4
[08:45] <vila> michi: I need to start somewhere... We're still investigating why *some* workers suddenly become slow
[08:45] <michi> vila: right. Let me find one of the silly failures.
[08:47] <michi> vila: Here is one: http://s-jenkins.ubuntu-ci:8080/job/unity-scopes-api-vivid-amd64-ci/57/console
[08:47] <michi> It’s *impossible* for test 8 to fail unless the machine is seriously ill.
[08:48] <vila> michi: right, I'm not denying slow workers lead to failures ;)
[08:49] <michi> OK. I just wanted to re-assure you that I’m not blaming you for something that’s our fault :)
[08:49] <vila> michi: hehe, thanks ;)
[08:49] <michi> Basically, when our tests fail, we see a pattern that’s occured before.
[08:49] <michi> Every now and then, a node on Jenkins goes really slow, and then tests blow up in random places.
[08:50] <vila> michi: yeah, it's hard to track, so far workers 06, 08, 11, 12 and now 09 have been caught slacking...
[08:50] <vila> and 03 too...
[08:51] <vila> sometimes we can point to CPU or mem starvation, sometimes we look and all is well, a pain...
[08:51] <michi> :(
[08:51] <michi> How many jobs are on those nodes concurrently?
[08:51] <vila> and 05...
[08:51] <michi> Normally jsut one build at a time, I thought?
[08:51] <vila> yes
[08:52] <michi> So, if memory goes missing, that must be caused by the previous run of some build.
[08:52] <michi> In other words, that would point at a really low level VM bug or some such.
[08:52] <vila> michi: sorry, I was unclear, those are cloud instances, the starvation is at the cloud level
[08:52] <vila> not a t the worker itself level
[08:52] <michi> Aha
[08:53] <michi> So a whole bunch of nodes can slow down, presumably because the hardware for those VMs is under-provisioned.
[08:56] <vila> michi: something like that... :-/
[09:00] <pstolowski> trainguards hey, we don't need landing-021 anymore, you can free this silo, thanks!
[09:00] <sil2100> pstolowski: ok, will do, thanks for the info!
[09:07] <vila> michi: s-jenkins is behaving weirdly but it seems http://s-jenkins.ubuntu-ci:8080/job/unity-scopes-api-vivid-amd64-ci/62/consoleFull was succesful...
[09:07] <michi> vila: yes, occasionally one happens to work.
[09:07]  * vila cries
[09:08] <michi> I feel with you :)
[09:10]  * vila chases 04 isntead
[09:49] <vila> michi: the plot goes more obscure, but I see weird things on cloud-worker-10: kern.log is full of lines like: Jan 20 08:01:33 juju-jenkins-stack-prod-machine-13 kernel: [3988674.042973] .mir_unit_tests[17386]: segfault at 0 ip<PHONE_NUMBER>607241 sp 00007fff7a02f4d0 error 4 in .mir_unit_tests-uninstalled[400000+2996000]
[09:50] <vila> michi: that's where http://s-jenkins.ubuntu-ci:8080/job/unity-scopes-api-vivid-amd64-ci/61 is running, swapping like mad (~2G) and apparently blocking job #62 to finish (even if the console says it's succesful)
[09:51] <vila> michi: does that remotely ring any sort of bell ?
[09:51] <michi> No.
[09:51] <michi> mir has nothing to do with us.
[09:52] <michi> If mir core dumps in some of its tests, that shouldn’t affect anything else on the machine though.
[09:52] <michi> It’s just a core dump, after all.
[09:52] <vila> isn't it ? :-/
[09:53] <vila> swap divided by 2 already 833504 used
[09:55] <michi> vila: I’m very sure it’s not anything we are doing in unity-scopes-api :)
[09:56] <vila> michi: hehe, lucky you, I wish I can be sure of *something* ;)
[10:15] <vila> michi: #61 finished, tests appear to be succesful yet the job is marked as fail, can you see why ?
[10:17] <vila> michi: sry, the url is http://s-jenkins.ubuntu-ci:8080/job/unity-scopes-api-vivid-amd64-ci/61/consoleFull
[10:18] <vila> oh, the last test was interrupted maybe ?
[10:45] <oSoMoN> trainguards: can silo 16 be published, please?
[10:45] <sil2100> oSoMoN: doing!
[10:46] <sil2100> Ah, it's this ;)
[10:47] <sil2100> oSoMoN: +1, releasing
[10:51] <oSoMoN> cheers!
[11:08] <rhuddie> cihelp, is there a known problem with makos currently? We are seeing some strange failures in autopilot: https://jenkins.qa.ubuntu.com/job/generic-deb-autopilot-runner-vivid-mako/757/testReport/autopilot.tests.unit.test_introspection_search/ProxyObjectTests/test_find_matching_connections_attempts_multiple_times/
[11:08] <psivaa_> rhuddie: let me take a look
[11:09] <rhuddie> psivaa_, thank you
[11:20] <psivaa_> rhuddie: I remember seeing ths: http://paste.ubuntu.com/9793526/  traceback before, probably some autopilot experts to take a look at
[11:23] <rhuddie> psivaa_, is it possible the mako might need reboot/refresh ? or some environment issue?
[11:24] <rhuddie> as we were not able to reproduce this locally
[11:29] <psivaa_> rhuddie: the devices are rebooted anyway for each tests. (by using reboot-and-unlock.sh) and reflashed ( the latest being image 71)
[11:29] <psivaa_> rhuddie: and i see image 71 does not have this issue
[11:29] <psivaa_> rhuddie: so this boils down to the autopilot version that *this test is trying to test
[11:29] <psivaa_> rhuddie: i.e. python3-autopilot_1.5.0+14.10.20140806bzr527pkg0vivid865+autopilot0_all.deb
[11:30] <psivaa_> rhuddie: so again, that's autopilot guys :)
[11:31] <rhuddie> psivaa_, thanks
[11:31] <psivaa_> rhuddie: yw
[12:26] <sil2100> o/
[12:27] <sil2100> bzoltan_: https://code.launchpad.net/~fboucault/ubuntu-ui-toolkit/activity_indicator_animator_rtm/+merge/246631 needs to be approved
[12:28] <bzoltan_> sil2100: this is  ambarassing ... i am sorry
[12:46] <alan_g> cihelp we're seeing a lot of "error: device not found" failures - e.g. https://jenkins.qa.ubuntu.com/job/mir-mediumtests-runner-mako/3999/console - can you help?
[12:50] <satoris_> ping trainguards, something seems to be broken: https://jenkins.qa.ubuntu.com/job/thumbnailer-vivid-amd64-ci/11/console
[12:53] <boiko> trainguards: could you please check why the "Reconfigure Silo" of row 60 is not a link? I added some extra MRs there
[12:58] <sil2100> boiko: looking
[12:58] <sil2100> satoris_: that's more like a thing for cihelp ^
[12:59] <sil2100> boiko: hm, looks like a link to me
[12:59] <sil2100> boiko: could you try to refresh the page?
[13:00] <boiko> sil2100: sure, let me see
[13:00] <boiko> sil2100: oh, refreshing the page did fix it, sorry for the noise, and thanks for looking into that :)
[13:01] <satoris_> ping cihelp, there seems to be something wonky with build machines: https://jenkins.qa.ubuntu.com/job/thumbnailer-vivid-amd64-ci/11/console
[13:06] <jibel> Elleo, when do you plan to update silo 2 with the additional dep for autopilot and the bug fix you wanted to add?
[13:10] <Elleo> jibel: they've just landed in trunk, I'm going to ping bill to update his rtm sync stuff for silo2 when he gets on in about an hour
[13:10] <jibel> Elleo, OK, thanks
[13:18] <cprov> satoris_: let me check.
[13:22] <satoris_> thanks
[13:28]  * sil2100 needs to jump out for lunch
[13:28] <sil2100> brb
[13:33] <cprov> satoris_: something is wrong with some cloud worker (I suspect), I will dig further
[14:27] <bfiller> sil2100: trying to rebuild ubuntu-keyboard in rtm 2 and keep getting this error: https://ci-train.ubuntu.com/job/ubuntu-rtm-landing-002-1-build/100/console
[14:27] <sil2100> bfiller: let me take a look
[14:28] <sil2100> bfiller: ah, crap... ok, it seems robru didn't fix that yet
[14:29] <bfiller> sil2100: any workaround? just need a resync of ubuntu-keyboard
[14:29] <sil2100> bfiller: this error pops up when you try to build/work with a package that didn't get yet published for the given distribution...
[14:29] <sil2100> bfiller: let me try pushing the packages directly
[14:29] <sil2100> (at least the ones that cause problems)
[14:29] <bfiller> sil2100: ok, thanks!
[14:37] <sil2100> pete-woods: we need to get this approved: https://code.launchpad.net/~unity-api-team/unity-scopes-shell/fix-location-caching-vivid/+merge/246981
[14:38] <pete-woods> sil2100: even for vivid?
[14:38] <pete-woods> oh, sorry the MR
[14:38] <sil2100> pete-woods: yeah, no one would want to release un-approved branches anywhere, right? ;)
[14:38] <pete-woods> d'oh!
[14:41] <pete-woods> have asked someone to look at it
[14:42] <sil2100> cjwatson: hey! Could you maybe copy myspell-hr to ubuntu-rtm? It's a main package so I have no power over it, and it will be required by a landing after it lands :)
[14:42] <sil2100> cjwatson: not sure if we can do a binary copy from utopic or not
[14:43] <sil2100> cjwatson: CI Train currently has issues handling new packages
[14:43] <cjwatson> sil2100: done
[14:44] <sil2100> cjwatson: wow, that was fast, thanks \o/
[14:44] <ogra_> plars, yo
[14:44] <plars> ogra_: hi
[14:45] <ogra_> plars, so i need to land this adbd change that blocks on locked screen this week ... iirc there was an issue with the lab that you need a newer u-d-f which we didnt solve before the holidays ... do you know if that was solved now ?
[14:46] <plars> ogra_: right, I pushed a MP on friday to make our stuff work with it and use a recovery image on krillin only (this is the only place where we'll have this problem right?)
[14:47] <ogra_> plars, err,no ... this is about adb
[14:47] <plars> ogra_: A lot of us were out yesterday, so I'm going to try to get someone to review it and get it pushed in today
[14:47] <plars> ogra_: oh, adb
[14:47] <ogra_> adb not accepting connections when the screen is locked
[14:47] <plars> ogra_: sorry, refresh me... I thought this was about the recovery image update
[14:47] <ogra_> there was a u-d-f that puts the right override file in place you need to upgrade to
[14:48] <ogra_> not sure which u-d-f version that was, perhaps sergiusens recalls ?
[14:50] <plars> ogra_: we're currently on 0.10-0ubuntu1 it seems, I'm not sure who updated it though. Could be landscape forced it on us again. We were on the latest previous one before that though
[14:50] <plars> ogra_: when I looked on friday, we were on 0.4+15.04.20141125-0ubuntu1
[14:50] <plars> (of udf)
[14:51] <sergiusens> ogra_: plars hah, we are at 0.13 now
[14:51] <sergiusens> ogra_: plars --recovery was introduced on 0.11 iirc
[14:51] <ogra_> sergiusens, well, which version had the adbd lockscreen stuff ?
[14:52] <plars> no, it's in .10
[14:52] <ogra_> this isnt about recovery atm
[14:52] <plars> Candidate: 0.10-0ubuntu1 is the latest I see for trusty
[14:52] <sergiusens> ogra_: you want to make me navigate debian/changelog it feels :P
[14:53] <ogra_> well, thats what i'm doing here (on the vivid-changes ML though)
[14:53] <ogra_> i cant find any entry foir this
[14:53] <sergiusens>   * ubuntu-device-flash: --developer-mode extended to now also inhibit
[14:53] <sergiusens>     adb disabling when the screen is locked
[14:54] <sergiusens> (0.4+15.04.20141104.1-0ubuntu1
[14:54] <ogra_> heh, i didnt go that far back :P
[14:54] <sergiusens> ogra_: I know; so much changelog :-P
[14:54] <sergiusens> ogra_: this was during the washington sprint
[14:54] <sergiusens> I recall asking plars to test now :-P
[14:55] <sil2100> bfiller: ok, I'm re-syncing ubuntu-keyboard, let's see how it goes
[14:55] <ogra_> plars, well, if you are running 0.10 to provision teh krillins i guess we're fine
[14:55] <bfiller> sil2100: thanks
[14:55] <sil2100> bfiller: we might need to remove myspell-hr from the silo list later though, as it's already in the archives now
[14:56] <bfiller> sil2100: that's fine
[14:56] <plars> ogra_: I saw some chatter this morning about some device issues yesterday though, so I need to go check into what was going on with that, and if it's related. I'm in a meeting right now though. Let me get back to you on that..
[14:56] <ogra_> plars, ok
[14:56] <sil2100> rsalveti: hey! If you have a moment, could you take a look at https://bugs.launchpad.net/ubuntu/+source/goget-ubuntu-touch/+bug/1412495 ?
[14:57] <plars> ogra_: but if .10 is working then we should be ok, is that right? sergiusens?
[14:57] <rsalveti> sil2100: sure
[14:57] <sil2100> Thanks :)
[14:57] <ogra_> plars, thats how i understand it, yes
[14:58] <plars> and 0.4+15.04.20141125-0ubuntu1 is what we were running before for a long time I know
[15:03] <sergiusens> plars: yes
[15:04] <sergiusens> plars: you can go all the way to .13, .11 or .12 allows customization tarball overrides in case you plan on adding that as well
[15:38] <renatu> sil2100, could you check why silo 000 is not updating the ppa packages
[15:39] <renatu> sil2100, bfiller just push a new build but the ppa did not get updated
[15:51] <sil2100> renatu: hey! Let me take a look
[15:51] <renatu> sil2100, thanks
[15:52] <sil2100> renatu: so, you want to rebuild sync-monitor in the PPA, right?
[15:52] <renatu> yes
[15:53] <sil2100> renatu: the problem is that the build was started with 'watch-only' selected, which means 'don't do anything, just watch what's up in the PPA'
[15:53] <sil2100> renatu: let me rebuild it without that
[15:53] <renatu> bfiller, ^^
[15:54] <renatu> sil2100, thanks
[15:54] <sil2100> renatu: yeah, it seems building now, yw
[15:54] <renatu> sil2100,  ^^
[15:54] <bfiller> renatu, sil2100 : ok thanks, I guess I checked that by accident and didn't realizes
[16:06] <sil2100> ogra_, jibel, davmor2, popey, brendand, robru: I need to skip todays evening meeting - you can still sync up on it if you want, but if there's anything important for me just leave me a ping on IRC
[16:06] <popey> ok
[16:06] <ogra_> sil2100, i would like ot skip today as well
[16:07] <jibel> sil2100, OK
[16:07] <ogra_> (my evening is still full of stuff)
[16:08] <ogra_> (and its surely depressing anyway, i guess brendand will just show off his new phone the whole meeting :P )
[16:08] <brendand> ogra_, :P
[16:13] <jgdx> cihelp: Hello, I'm seeing a failure [1] on the u-s-s ci run for RTM on jenkins, but cannot reproduce that on my device. Any clue? :) [1] https://jenkins.qa.ubuntu.com/job/generic-deb-autopilot-runner-14.09-mako/14/testReport/junit/ubuntu_system_settings.tests.test_datetime/TimeDateTestCase/test_same_tz_selection/
[16:14] <jgdx> … using krillin
[16:33] <rsalveti> sil2100: alright, triggering a new rtm build
[16:33] <sil2100> rsalveti: ok, thanks ;)
[16:40] <imgbot> [16:48] <fginther> jgdx, the first thing that comes to mind is that jenkins is using a mako and not a krillin, hopefully that doesn't matter, but maybe it does?
[17:12] <pstolowski> cihelp hello, i need help with silo 15 notoriously failing on powerpc with one of our tests... I've just increased the timeout in the test from 2 to 8 seconds and that didn't help...
[17:21] <elopio> ping cihelp: can somebody please check the last run in this MP:
[17:21] <elopio> https://code.launchpad.net/~canonical-platform-qa/autopilot/custom-assert-doc/+merge/246963
[17:21] <elopio> a couple of bad things there. One of the jobs failed, but jenkins still approved the review.
[17:21] <elopio> and on the failed test, I see: error: device not found
[17:22] <alecu> yes, please.
[17:26] <alecu> that was quick, thanks!
[17:26] <Ursinha> elopio: alan_g pointed me another job with device not found, plars said he would have a look
[17:27] <elopio> Ursinha: ok, thanks.
[17:38] <jgdx> fginther, maybe. Shouldn't though.
[17:38] <plars> elopio: Ursinha: yeah, I'm looking at it right now. It seems a lot of devices failed and I'm trying to recover them
[17:39] <elopio> plars: thanks. yesterday we saw a lot of weird crashes.
[17:39] <plars> I did kill https://code.launchpad.net/~alan-griffiths/mir/MVC-introduce-default-controller-object/+merge/246924 on one which was clearly stuck, I'll restart in a moment after I get that device back up
[17:50] <imgbot> [17:51] <imgbot> [18:23] <pmcgowan> bfiller, om26er is silo 14 blocked on the thumbs fix? was hoping to have sd card done
[18:24] <om26er> pmcgowan, kind of yes, I am not able to completely run the test plan due to thumbnail issue.
[18:36] <bfiller> pmcgowan: yes it's blocked
[18:36] <bfiller> pmcgowan: we might have to consider reverting thumbnailer, the fixes are not appearing to be trivial
[18:37] <pmcgowan> bfiller, thats unfortunate although not sure what the thumbnailer change got us
[18:38] <bfiller> pmcgowan: a slight performance increase first time they are being created, that is it
[18:38] <pmcgowan> hmmm
[18:38] <bfiller> pmcgowan: nerochiaro is looking at a gallery fix but there are a few things broken because of the change
[18:39] <pmcgowan> bfiller, not sure I get why photo roll works but gallery doesnt, do we need more code sharing?
[18:39] <bfiller> pmcgowan: yup
[18:40] <bfiller> pmcgowan: and gallery is broken when doing rotation/cropping/editing which is not present in camera
[18:40] <pmcgowan> I see, seems like we should revert then?
[18:40] <bfiller> pmcgowan: the black image problem is fixed and was easy, but we having issues with the others
[18:41] <bfiller> pmcgowan: lets make a call tomorrow and see if we can get gallery fixed
[18:41] <bfiller> if not or too risky I'd say revert
[18:41] <pmcgowan> ok
[18:42] <nerochiaro> bfiller: if thumbnailer only buys us some perf i would say revert, then when the rtm rush is past release the new image editor which will hopefully make things more maintenable for everyone
[18:42] <nerochiaro> bfiller: (new image editor + improved photo image provider)
[18:43] <nerochiaro> bfiller: then we can put back the thumbnailer changes
[18:57] <robru> jgdx: hm, I just assigned you silo rtm 4 for your request on row 55, just be aware it conflicts with silo rtm 19.
[19:04] <bfiller> popey: can you review the updated camera-app in the store so we can release it?
[19:05] <popey> sure thing
[19:05] <bfiller> popey: thanks
[19:06] <popey> bfiller: done
[19:07] <bfiller> popey: nice
[19:07] <bfiller> pmcgowan: ^^^ new camera-app should be available soon, just happroved in the store
[19:07] <bfiller> Kaleo: ^^
[19:07] <popey> its available now, I just updated my phone fwiw
[19:08] <bfiller> even better
[19:13] <pmcgowan> nice
[19:14] <pmcgowan> hmm dont see it
[19:15] <pmcgowan> popey, what version of click do you have
[19:16] <popey> now? phablet@ubuntu-phablet:~$ click list | grep camera
[19:16] <popey> com.ubuntu.camera       <IP_ADDRESS>9
[19:16] <pmcgowan> why cant I see it in the store
[19:17] <popey> nice new features!
[19:18] <pmcgowan> popey, is <IP_ADDRESS>9 same as 3.0.0.latest?
[19:18] <popey> did you manually install it at some point?
[19:19] <popey> the version in the store is <IP_ADDRESS>9, the .latest suffix is common if you built your own (or someone built for you) in qtc
[19:19] <pmcgowan> I didnt think so
[19:19] <pmcgowan> must have
[19:19] <pmcgowan> probably loaded the ppa and forgot
[19:26] <Kaleo> bfiller: fuck yeah
[19:53] <rsalveti> davmor2: pmcgowan: camera-app is fine with 172/mako
[19:53] <rsalveti> feel free to update
[19:53] <davmor2> rsalveti: thanks
[19:54] <pmcgowan> rsalveti, will do
[20:50] <jgdx> robru, thanks. Noted. I'll wait
[20:53] <robru> jgdx: ah you don't necessarily have to wait, you can build your silo if you want to start testing it now, you just have to be aware that whoever publishes first has to let the other person know to rebuild their silo after the first silo is merged.
[20:58] <robru> dobey: https://ci-train.ubuntu.com/job/ubuntu-landing-021-2-publish/21/console need you to approve these merges
[21:00] <jgdx> robru, ah, right. thanks
[21:01] <robru> jgdx: you're welcome
[21:02] <dobey> robru: oh right. oops. sorry about that, done
[21:04] <robru> dobey: no worries, publishing
[21:47] <michi> cihelp: I need help with failing builds on Jenkins-ci and in Silo 15. Anyone around?
[21:48] <fginther> michi, I can help with jenkins-ci, what's the job?
[21:48] <michi> Basically, we have builds and tests failing left right and center on Jenkins-ci. It’s happening because the build machines are ridiculously slow.
[21:48] <michi> fginther: thanks!
[21:48] <michi> Lots of jobs, and different nodes.
[21:48] <michi> If you search through the scrollback, I chatted with vila yesterday, who was trying to help.
[21:49] <michi> fginther: Here is one: https://jenkins.qa.ubuntu.com/job/unity-scopes-api-vivid-i386-ci/61/consoleFull
[21:49] <michi> That’s one of many.
[21:49] <michi> This time, the build was aborted because the compilation hadn’t finished after two hours.
[21:49] <michi> We are also seeing tests failing randomly due to timeouts.
[21:50] <michi> We also have a problem with Silo 15, on PPC only.
[21:50] <michi> A test keeps timing out.
[21:50] <michi> We have no way to diagnose or fix this, because none of us has a PPC machine.
[21:51] <michi> Is it theretically possible that the PPC run in the silo is affected by the same thing as the Jenkins-ci nodes?
[21:51] <michi> This particular test has not failed in months, which makes us think that it may be an infrastructure issue.
[21:52] <fginther> michi, I'll have a look at vila's notes and try to sort out if there is a job configuration change that would help (we had similar problems with mir that have been helped by similar changes)
[21:52] <michi> Thanks! Anything you can do would be most appreciated. Things started going wrong either last Friday or Saturday. Prior to that, everything was fine.
[21:52] <michi> What about the PPC issue?
[21:52] <fginther> michi, the PPC build in silo 15 is whole done in launchpad which is on separate infrastructure from the jenkins ci infrastructure
[21:53] <michi> OK, so it’s not the same thing then.
[21:53] <michi> How can we get access to a PPC machine so we can work out what’s going wrong?
[21:55] <fginther> michi, there may be a way through IS or maybe the foundations team to get access to a PPC system. I'll also ask a few others that might know of some machines
[21:55] <michi> Thanks! Whom should I be talking to?
[21:57] <dobey> ironically, it didn't fail on ppc64
[22:01] <michi> dobey: ? Are the 32 and 64 buiilds for PPC?
[22:01] <tedg> trainguards, thanks for the silos!
[22:02] <robru> tedg: ah, you're welcome
[22:02] <dobey> michi: yeah, there's powerpc and ppc64el archs
[22:02] <michi> Ah, I didn’t know that.
[22:03] <dobey> michi: looking at the failure log, it looks like the test is expecting a timeout, but the "slow" server is returning a response in under 10 seconds?
[22:04] <michi> Possible. I have no idea.
[22:04] <michi> I’ll dig into the test code today and see what I can learn. It’s not my own code, so I’m not too familiar with it.
[22:04] <dobey> ok. well that's what it looks like, jut from the log anyway (expecting an exception, and a 200 OK in the log).
[22:05] <michi> But, yes, if no exception arrives when one is expected, you’d think that response arrived when it shouldn’t have. Or it’s a race of some kind.
[22:06] <dobey> michi: it could maybe be clock drift happening, and then being corrected by ntpd, while the tests are running, and might cause sleep() or such to skip out early
[22:06] <dobey> just a possibility :)
[22:07] <michi> dobey: Interesting thought. But I would expect that to be very rare. We are seeing the test failing repeatedly. And ntpd adjusts the time by slowly creeping it, rather than just setting it.
[22:10] <dobey> i guess it would depend on the remaining capacity of the battery in the hardware, on how rare the drift would happen.
[22:10] <dobey> i do find it quite odd that it only happens on powerpc though
[22:13] <dobey> i gotta run though. later :)
[23:38] <fginther> michi, FYI, we'll continue to look at the problem you raised and will try to have some improvements by EOD. I need to go afk for a few hours, but will pick it back up when I return
[23:39] <michi> fginther: Thank you, much appreciate it!
[23:46] <cjwatson> michi: Is there any pattern in the builders it's succeeded on in the past?  (They're all pretty similar, but not quite identical, in ways that mostly don't matter)
[23:46] <michi> cjwatson: I honestly don’t know.
[23:46] <cjwatson> dobey: The builders it's failed on today are VMs :-)
[23:46] <cjwatson> michi: You could look.
[23:46] <michi> I suspect that some change last Friday or Saturday caused it. Up to then, things were working just fine.
[23:46] <cjwatson> (So could I, but I'm not on my usual system right now.)
[23:47] <michi> Branches that used to work started failing then.
[23:47] <cjwatson> michi: I'm not aware of any changes.
[23:47] <cjwatson> You could diff the build logs in case it's something inside the chroot.
[23:47] <michi> cjwatson: I’ll go through the past half dozen failures or so
[23:47] <cjwatson> (That would also tell you about kernel changes.)
[23:48] <cjwatson> There's really not a lot else that could possibly affect anything, so diffing the build logs is a good place to start.
[23:48] <michi> vila told me yesterday that some of the build nodes are swapping themselves into oblivion
[23:48] <cjwatson> That's jenkins, not Launchpad.
[23:48] <cjwatson> Totally different.
[23:48] <michi> Ah
[23:48] <michi> OK, you are talking about the silo failure
[23:48] <cjwatson> Yes
[23:48] <michi> I’m building in a chroot on PPC now, to see whether I can at least reproduce
[23:48] <cjwatson> OK, good, you found porter-powerpc then
[23:49] <cjwatson> But sorry, yes, I'm talking about the powerpc issues on the grounds that fewer people are usually able to respond to those so it's more worth helping.
[23:50] <michi> I appreciate it!
[23:51] <cjwatson> Of the last six successful builds on powerpc, they're evenly distributed among our three regular powerpc builders.
[23:51] <cjwatson> So that rules out that theory.
[23:52] <cjwatson> Start with https://launchpad.net/ubuntu/+source/unity-scopes-api/+publishinghistory and you can find the historically successful builds from there; easy enough to grab and diff build logs then.
[23:52] <michi> Cool, tahnks!
[23:52] <cjwatson> infinity might know if the VM software has changed.
[23:52] <cjwatson> (on denneed)
[23:53] <cjwatson> We could rule that out by trying on sagari, but last I checked it hadn't come back since the power work in 3FP earlier today.
[23:57] <infinity> cjwatson: Nothing on denneed has changed.
[23:58] <michi> cjwatson: can’t reproduce in the build I did in the chroot.
[23:58] <michi> tests are ticking over just fine.
[23:58] <infinity> michi: YOu have a link to the PPA build that was failing?
[23:59] <michi> All the failures we’ve seen on PPC relate to timeouts. Basically, it looks like the machine is super-busy or thrashing from the symptoms.
[23:59] <michi> infinity: sec...
[23:59] <michi> https://launchpadlibrarian.net/195403187/buildlog_ubuntu-vivid-powerpc.unity-scopes-api_0.6.11%2B15.04.20150120.4-0ubuntu1_FAILEDTOBUILD.txt.gz
[23:59] <infinity> michi: Link to the build instead of the log would be more friendly. :P


[15:31] <elopio> kgunn: I will send you the link to join the hangout ~10 minutes before we start.
[15:31] <elopio> let me know if you need something else from our side.
[15:31] <kgunn> elopio: nope that will be great...i just need to setup a little with the camera
[15:44] <CoderEurope> Who is doing the Ubuntu On air today ?
[15:44] <CoderEurope> https://www.youtube.com/watch?v=oGsA55RvqLI
[15:46] <elopio> CoderEurope: yes, we'll be there soon.
[15:46] <elopio> kgunn will show Unity8.
[16:00] <CoderEurope> kgunn, Is that kevin gunn ?
[16:00] <kgunn> it is
[16:04] <CoderEurope> kgunn , I put you on the subreddit :) https://redd.it/44c5z0
[16:24] <kgunn_> elopio, so i'm here actually
[16:24] <elopio> kgunn_: I've just sent you the lnk
[16:26] <CoderEurope> 3 minutes to go ..
[16:29] <CoderEurope> elopio: ?
[16:30] <la_juyis> CoderEurope: hello!
[16:30] <la_juyis> we're starting :D
[16:30] <CoderEurope> hiya
[16:31] <CoderEurope> I see the stream !
[16:31] <eyescream_> QUESTION: what is classic?
[16:32] <kyrofa> eyescream_, just desktop ubuntu
[16:32] <kyrofa> eyescream_, as opposed to one based on snaps
[16:33] <eyescream_> thanks
[16:33] <kyrofa> (e.g. ubuntu core or ubuntu personal)
[16:33] <kgunn_> https://docs.google.com/document/d/1o-jKITqUxRsujmN3OwRj3wRnn6dgblKuvrhKjeN8-Wc
[16:33] <CoderEurope> QUESTION: kgunn, When realistically do you think we shall see Unity 8 in a Long Term Release ?
[16:34] <kyrofa> CoderEurope, i.e. as the default?
[16:34] <CoderEurope> right.
[16:34] <eyescream_> kgunn_: You need permission to view the doc
[16:34] <CoderEurope> I cannot open that document ...
[16:35] <eyescream_> You need permission  Want in? Ask for access, or switch to an account with permission. Learn more
[16:35] <DaveGinBoav> QUESTION for snap - read sand-box, right?
[16:36] <CoderEurope> I see the doc.
[16:36] <kyrofa> DaveGinBoav, I'm not sure I understand the question
[16:37] <WLBI> I really like that Unity8 especually on my Phoen and tablet, but I can't use it on the desktop with Ubuntu 16.04. WHen I choose Unity 8 to login, the desktop freeze at login, I just can reboot
[16:38] <eyescream_> QUESTION: is it safe to install unity8 snap? will it mess with my os?
[16:38] <CoderEurope> CoderEurope: kgunn, Give me an example (in IRC) of that 'bitch of a bug' for Unity 8 that is bottle-necking development ?
[16:40] <CoderEurope> guess I am asking - what is the worst Unity 8 bug ?
[16:43] <Blue2> Will you be able to force server side decorations on client side decoration on apps?
[16:44] <eyescream_> QUESTION:what laptop is it?
[16:44] <Blue2> QUESTION: Will you be able to force server side decorations on client side decoration on apps?
[16:48] <Blue2> QUESTION: Is a juju-like graphical interface (or something else) planned to see and manage dependencies and interfaces on snappy?
[16:48] <WLBI> QUESTION: Is it possible to run a server with snaps. Apache, FTP, E-Mailserver..
[16:48] <kyrofa> WLBI, definitely!
[16:48] <kyrofa> WLBI, check out the nextcloud snap for an example
[16:49] <la_juyis> WLBI: you mean if all those snaps exist?
[16:49] <la_juyis> Blue2: with snaps you shouldn't have dependency problems :)
[16:50] <kyrofa> Blue2, snaps include their dependencies, so such an interface probably isn't realistic
[16:50] <la_juyis> Blue2: and there is the software center that should allow you to install snaps as well (at least in classic)
[16:50] <CoderEurope> I was looking for a bug to fund - no one mentioned one.
[16:50] <Blue2> I know, but it has interfaces and will have some dependencies in UI Toolkits
[16:51] <la_juyis> Blue2: ubuntu-core images should instead have a web interface - snapweb, from where you can install new snaps
[16:51] <WLBI> la_juyis: yes, snaps for apache2 and FTP
[16:51] <kyrofa> Blue2, ah, then really for interfaces then (including the content interface which is how snaps can sort of depend on each other)
[16:52] <WLBI> I don't know how to list all snaps. I foudn out: sudo snapfind $
[16:52] <eyescream_> QUESTION: can we install install unity8 snap session on M10 tablet?
[16:52] <eyescream_> bq
[16:52] <WLBI> It shows a big list, but no apache
[16:52] <DaveGinBoav_> #QUESTION if in 18.10 LTS UNITY 8 Iis working in snap along with other snaps how do you deal with matters that need to communicate between each distint snap environment?
[16:52] <la_juyis> WLBI: not in stable, at the moment (have tried snap find apache, for example :))
[16:52] <kyrofa> WLBI, there's no standalone apache snap right now. There are various web applications that are snapped though (like nextcloud) which bundle apache
[16:53] <WLBI> snap find apache shows no apache snap
[16:53] <Blue2> Those are big glasses! kinda cute
[16:54] <kyrofa> Blue2, mine? Thanks!
[16:54] <la_juyis> WLBI: right - you can also use the unofficial site: https://uappexplorer.com/
[16:54] <cyn> I have a question: Will this talk include information about how unity8 is tested? e.g. user testing, GUI testing, or whether there unit tests are also used for the back-end? Thanks
[16:54] <la_juyis> Blue2: kyrofa: we can do a session on those, too :P today elopio is without, that's a pity!
[16:55] <kyrofa> DaveGinBoav_, snapd has a concept of "interfaces," which is a way for snaps to communicate
[16:55] <kyrofa> DaveGinBoav_, but in a confined manner
[16:55] <la_juyis> cyn: we're covering that :)
[16:56] <Blue2> kyrofa: 8) :P
[16:56] <WLBI> sudo snap install apache2
[16:56] <WLBI> error: cannot install "apache2": snap not found
[16:56] <la_juyis> DaveGinBoav_: interfaces would be like plugs to have two different snaps talk to each other
[16:56] <eyescream_> QUESTION: is it possible to install unity8 on other distro that support snaps? like maybe arch
[16:56] <DaveGinBoav_> thanks
[16:57] <Blue2> QUESTION: Will a snap based ubuntu make distribution-upgrades easier and safer than now? (My dad got the frustrating login loop after upgrading from 14.04 to 16.04)
[16:57] <la_juyis> WLBI: right, it doesn't exist yet as a snap standalone - it's currently being delivered along with other software (as part of the snap) such as nextcloud, like kyrofawas saying
[16:58] <la_juyis> Blue2: it's the idea, yes :) upgrades are transparent to the user
[16:58] <WLBI> la_juyis: oh I see, now I got it... :-) Thanx
[16:58] <la_juyis> WLBI: np :)
[16:59] <CoderEurope> QUESTION: The wiki page of 'known bugs' [ https://wiki.ubuntu.com/Unity8Desktop ] just goes to the Unity8 bug list - is this correct for the 'known problems list' or is there another page that needs linking to the one a gave ?
[16:59] <la_juyis> cyn: if you have any specific questions, do raise your arm!
[16:59] <scopes> These videos are awsome! We need on for Scopes as well
[16:59] <davmor2> elopio: move the mouse to the bottom right hand corner then top right bottom left top left, that should then calibrate the mouse so you can hit the whole area of the screen
[17:00] <elopio> davmor2: nice, thankyou.
[17:00] <kyrofa> davmor2, hahaha, only you would know that
[17:00] <andy-k> QUESTION sorry, quite late to the stream. Will the default unity8 session eventually be deployed via snap package on all platforms?
[17:00] <kyrofa> andy-k, indeed!
[17:01] <DaveGinBoav_> pardon my cynicsm. i am old school, but all this sounds like re-inventing the wheel and when finished it will go round like the old wheel :)
[17:01] <cyn> thanks @la_juyis, I haven't experience in the ubuntu development process (although I have been using it for years) and I'm in general interested in the QA processes used
[17:01] <WLBI> QUESTION: Is teher any buglist for Ubuntu Touch OTA 15? The one for OTA14 https://launchpad.net/canonical-devices-system-image/+milestone/14 - But 15 doesn't exist.
[17:01] <scopes> QUESTION: Laptops with unity8  will have gestures capabilites? Like macOS has with macbooks (Swipes, multi touch...)
[17:01] <WLBI> I mean milestones, not buglist ;-)
[17:01] <kyrofa> DaveGinBoav_, heh, which part? unity8? snaps?
[17:01] <DaveGinBoav_> both
[17:02] <CoderEurope> QUESTION: So do we need a separate wiki page for Known Unity 8 'highlighted bugs' doing for 'testing' and guidance ?
[17:02] <la_juyis> cyn: yes!! we want you!
[17:02] <la_juyis> :D
[17:04] <Blue2> ok :D
[17:04] <Blue2> Dirty cow? :P
[17:05] <kgunn_> CoderEurope, we try to stick to launchpad bugs in order to not create a wiki...and then have to keep that updated
[17:05] <DaveGinBoav_> exit
[17:05] <DaveGinBoav_> quit
[17:05] <kgunn_> i will say that we do use another meta project to kinda collect things we "care about"
[17:05] <kgunn_> one sec lemme grab a link
[17:06] <kgunn_> if you follow this meta project
[17:06] <kgunn_> https://launchpad.net/canonical-devices-system-image
[17:06] <kgunn_> the milestones have the top bugs we're targeting for the next milestone
[17:06] <kgunn_> in this case...next milestone is p2
[17:07] <eyescream_> QUESTION: what is a good laptop or a good video card to run unity8 on?
[17:08] <kgunn_> eyescream_, mainly make sure you are running freedrivers
[17:08] <kgunn_> mir relies on kms/drm gfx stack (think freedesktop.org)
[17:08] <kgunn_> ...mir also runs on android drivers..but i digress
[17:09] <kgunn_> so for sure intel gpu gfx stacks are solid for u8/mir
[17:09] <andy-k> QUESTION kgunn, can you make any comment on progress with nvidia and the esgl support?
[17:09] <eyescream_> thanks kgunn_
[17:09] <kgunn_> the free drivers for nv and amd have had issues in the past...as they're not well maintained
[17:10] <kgunn_> andy-k, i can say that we've been working with them very close with them, we have a mir functioning on some early version drivers
[17:11] <andy-k> kgunn_ you guys are super amazing, thanks
[17:11] <kgunn_> modulo  some issues we've reported back to them
[17:11] <andy-k> ... i have maxwell hardware, and unity8 blows up pretty easily, but unity7 won't run on nouveau
[17:17] <andy-k> thanks everyone for starting this testing day a little earlier! it was great to finally ask a question in IRC
[17:18] <thibran> QUESTION: Right now starting a application on unity8 is quite slow (as on Ubuntu Touch), any improvements on that front for the next months?
[17:21] <kyrofa> thibran, to be clear, are you asking about starting apps in unity8 on a desktop, or phone?
[17:22] <CoderEurope> QUESTION: General Question: Has 'Desktop Development' for Unity and Ubuntu in general slowed down this year (?) - Give us a picture of how things are looking ?
[17:22] <thibran> I would like to know if the start-up time will be reduced on the desktop (but I'm interested in the phone too)
[17:23] <kgunn_> https://developer.ubuntu.com/en/snappy/guides/mir-snaps/
[17:27] <CoderEurope> kyrofa: See you soon - I shall miss those glasses :)
[17:27] <kyrofa> CoderEurope, you know it
[17:30] <CoderEurope> QUESTION: (funnies) What happened to kgunn's beard - did it go for Movember ?
[17:31] <Blue2> CoderEurope: Kyrofa took it
[17:31] <WLBI> Well done! :-)
[17:31] <CoderEurope> haha !
[17:31] <la_juyis> I was late :(
[17:31] <kyrofa> CoderEurope, his wife told him no
[17:31] <la_juyis> next year it shall be mine!
[17:31] <kgunn_> CoderEurope,  spousal approval rating was very low
[17:31] <la_juyis> OH NO! how do they date!
[17:31]  * la_juyis is a moutache lover
[17:31] <CoderEurope> fair enough kgunn, good presentation BTWay.
[17:32] <la_juyis> *moustache
[17:32] <kyrofa> CoderEurope, kgunn_ I'll admit I miss it, too
[17:32] <CoderEurope> kgunn loses his beard in Ubuntu - if it affects one - it affects us all :)
[17:33] <kgunn_> lol
[17:33] <la_juyis> I'll raise a bug, you put "it affects me too"
[17:33] <la_juyis> :P
[17:33] <la_juyis> j/k, j/k
[17:33] <kgunn_> ok...disappearing...will reappear in moment
[17:34] <CoderEurope> Hey in other news - I hear Trisquel has gone with Mate as a D.Environment. +1
[17:35] <CoderEurope> anyway - good show guys :)
[17:35] <kyrofa> Thanks CoderEurope!
[17:35] <CoderEurope> kyrofa: I dont want to pry but are you Spanish or Portugese ?
[17:35] <kyrofa> CoderEurope, italian
[17:36] <CoderEurope> oh ok thats good !
[17:36] <CoderEurope> I had a friend in 2014 from southern Italy (he was on the bottom of the foot near the sea).
[17:37] <CoderEurope> kyrofa: Did you ever go to a Linux User Group in Italy, where you are ?
[17:37] <kyrofa> CoderEurope, haha, I'm afraid I misunderstood-- I live in the states
[17:38] <CoderEurope> oh ok. figures that you 'made it'.
[17:39] <CoderEurope> anyway kyrofa bye byes .. have a good day :)
[17:39] <CoderEurope> o/


[12:22] <JohnFlux> Riddell: can you send me the details of your train travel?
[12:24] <shawarma> @schedule Copenhagen
[12:24] <ubotu> Schedule for Europe/Copenhagen: 27 Mar 10:00: MOTU | 27 Mar 22:00: Technical Board | 28 Mar 22:00: Edubuntu | 29 Mar 00:00: Xubuntu | 29 Mar 23:00: Ubuntu Development Team | 01 Apr 22:00: Marketing Team
[01:48] <nixternal> @schedule chicago
[01:48] <ubotu> Schedule for America/Chicago: 27 Mar 03:00: MOTU | 27 Mar 15:00: Technical Board | 28 Mar 15:00: Edubuntu | 28 Mar 17:00: Xubuntu | 29 Mar 16:00: Ubuntu Development Team | 01 Apr 15:00: Marketing Team
[08:11] <AndrewB> !london
[08:11] <ubotu> Sorry, I don't know anything about london - try searching on http://bots.ubuntulinux.nl/factoids.cgi
[08:11] <AndrewB> !schedule london
[08:11] <ubotu> Sorry, I don't know anything about schedule london - try searching on http://bots.ubuntulinux.nl/factoids.cgi
[08:15] <bimberi> @schedule london
[08:15] <ubotu> Schedule for Europe/London: 27 Mar 09:00: MOTU | 27 Mar 21:00: Technical Board | 28 Mar 21:00: Edubuntu | 28 Mar 23:00: Xubuntu | 29 Mar 22:00: Ubuntu Development Team | 01 Apr 21:00: Marketing Team
[08:15] <bimberi> AndrewB: ^^^^
[08:15] <AndrewB> ahh
[08:15] <AndrewB> thanks bimberi
[08:16] <bimberi> AndrewB: yw :)
[10:00] <ajmitch> ok, are we having a meeting or not? :)
[10:00] <TheMuso> Hey all.
[10:00] <ajmitch> hi TheMuso
[10:01] <TheMuso> Have I missed anything? )
[10:01] <ajmitch> nothing at all
[10:01] <ajmitch> so far it's just the two of us
[10:01] <TheMuso> Ah ok.
[10:02] <ajmitch> & the only thing on the agenda so far is the MC charter
[10:02] <ajmitch> hi sistpoty
[10:02] <TheMuso> SO I can see.
[10:02] <TheMuso> Hey sistpoty.
[10:02] <sistpoty> hi ajmitch and TheMuso
[10:02] <ajmitch> you're up very early today ;)
[10:03] <sistpoty> hehe
[10:05] <sistpoty> ok, do we want to start with the meeting?
[10:05] <dholbach> heya
[10:05] <sistpoty> hi dholbach
[10:06] <ajmitch> hi dholbach
[10:06] <ajmitch> sistpoty: we've been trying ;)
[10:06] <sistpoty> :)
[10:06] <sistpoty> ok, anyone volunteering to do the minutes?
[10:07] <TheMuso> Yeah ok.
[10:08] <sistpoty> TheMuso: does that mean you're volunteering for the minutes? :)
[10:08] <ajmitch> yes
[10:08] <TheMuso> sistpoty: It does indeed.
[10:08] <ajmitch> don't let him get away
[10:08] <sistpoty> great, thanks!
[10:08] <TheMuso> np
[10:08] <dholbach> ok, let's get started
[10:09] <sistpoty> yes... *looking at the agenda*
[10:09] <dholbach> sistpoty wants to discuss "Work out MOTU Council's charter MOTU/Council/Charter"
[10:09] <dholbach> https://wiki.ubuntu.com/MOTU/Meetings
[10:09] <dholbach> https://wiki.ubuntu.com/MOTU/Council/Charter
[10:10] <sistpoty> ok, since the motu council still is in the way in finding its place in motu community, which has caused some annoyance recently, we've tried to get this sorted out into a proposal during the last motu council meeting
[10:11] <sistpoty> now, I've tried to put this in the charter somehow last night, I hope I got it in a good way ;)
[10:11] <sistpoty> so basically I'm asking here everyone, what you think of it, what needs to be changed/improved
[10:11] <sistpoty> and finally to acknowledge the charter (or reject it, if it's all wrong *g*)
[10:12] <dholbach> I'm basically very happy with it
[10:13] <dholbach> any other opinions on it?
[10:13] <TheMuso> I like the idea of a MOTU meeting every two weeks.
[10:13] <dholbach> regular events++
[10:14] <TheMuso> The way I see the MOTU council, is a group of individuals that are well known and respected in the group, who have the skills and experience to approve/decline candidates, and make difficult decisions if needed.
[10:14] <TheMuso> WHich is basically what it is anyway.
[10:14] <TheMuso> So yeah sounds good to me. :)
[10:14] <sistpoty> :)
[10:15] <TheMuso> What disputes if any would there be between MOTUs?
[10:15] <ajmitch> technical arguments, generally
[10:15] <TheMuso> I find it hard to think of any, as we all seem to work well with each other.
[10:16] <dholbach> yeah, we're all quite focussed on "getting work done"
[10:16] <sistpoty> yep... this was basically a leftover from the first try... should we drop it?
[10:16] <ajmitch> I think it'd be more for where there's real disagreement on how to get something done
[10:16] <TheMuso> ajmitch: SOunds good.
[10:17] <dholbach> sistpoty: I'd keep it - I think it's a good thing there's somebody responsible for mediating between groups if it comes to disagreements
[10:17] <TheMuso> Pitty there aren't more of us here.
[10:17] <dholbach> we should blog more about MOTU :-)
[10:17] <sistpoty> hehe
[10:17] <ajmitch> not pointing any fingers or anything
[10:17] <TheMuso> ajmitch: ??
[10:17] <sistpoty> dholbach: ah... mediating was apparently the wording I was really looking for here :)
[10:18] <geser> LaserJock started with interviews of MOTUs
[10:18] <TheMuso> Ah.
[10:18] <Burgundavia> I will chase down the Behind Ubuntu people
[10:19] <Burgundavia> and get them to do more interviews
[10:19] <Burgundavia> and then I will chase all you down for interviews :)
[10:19] <ajmitch> but they probably won't want that again :)
[10:20] <sistpoty> ok, let's get back to the charter... is there something obvious missing?
[10:20] <ajmitch> not that I could see
[10:20] <TheMuso> Me neither.
[10:21] <dholbach> it'd be nice to integrate ajmitch's summary somehow
[10:21] <dholbach> but apart from that it's fine
[10:21] <ajmitch> summary from MC meeting?
[10:21] <TheMuso> But since there are only a few of us here, what do you say we put a final call to the ml? I don't like the fact that not everybody is getting a chance to have a say.
[10:21] <ajmitch> TheMuso: I thought there'd be a *few* more people here
[10:21] <TheMuso> ajmitch: My point exactly.
[10:21] <ajmitch> like Hobbsee
[10:22] <sistpoty> TheMuso: good idea
[10:22] <TheMuso> heh
[10:23] <sistpoty> dholbach: I'd also like to see the summary in the actual charter, but I've only managed to transform it into a foreword somehow :(
[10:23] <sistpoty> <- no brainer ;)
[10:24] <dholbach> sistpoty: will you mail the list about it?
[10:24] <sistpoty> ok, I will
[10:24] <dholbach> super
[10:24] <dholbach> any other business before we move on to fixed items?
[10:25] <sistpoty> is the TODO list up to date?
[10:25] <TheMuso> Yeah I have something I just want to ask about
[10:25] <dholbach> I tagged quite a bunch of bugs and filed the unmetdeps bugs
[10:25] <dholbach> and there's been quite some activity on fixing bugs
[10:25] <dholbach> TheMuso: fire away
[10:26] <gpocentek> (morning MOTUs)
[10:26] <TheMuso> Since we are getting/want to get more people on board, I am wondering whether we should consider putting something in place for merging at the begiinning of a release, like what we have had previously.
[10:26] <sistpoty> hi gpocentek
[10:26] <ajmitch> hey gpocentek
[10:26] <ajmitch> TheMuso: like the merge web tool?
[10:26] <TheMuso> ajmitch: To indicate who is doing what. The more people we have, the harder it will be to determine who has got what merge.
[10:26] <ajmitch> which is exactly what that did
[10:27] <ajmitch> basically stating that you had a lock on that package
[10:27] <TheMuso> I believe some people in this cycle filed bugs etc, but that wasn't manditory if I remember correctly.
[10:27] <TheMuso> ajmitch: Ah I don't really remember seeing that anywhere.
[10:27] <TheMuso> I may have been out of the loop at the time.
[10:27] <ajmitch> it was very useful, used malone bugs to track it
[10:27] <ajmitch> I think we used it for dapper?
[10:27] <sistpoty> yes, sounds like a good idea to me, as I think the merges for feisty stagnated at some point because too few people touched other people's merges
[10:27] <ajmitch> sistpoty coded it :)
[10:28] <TheMuso> ajmitch: Got an URL that we can give newcomers? And can the bot be updated with info about merging perhaps?
[10:28] <ajmitch> no, it was disabled since then
[10:28] <ajmitch> iirc
[10:28] <ajmitch> bot can be updated
[10:28] <sistpoty> yep, it's disabled (and a little bit broken atm)
[10:28] <TheMuso> sistpoty: Yeah, and the more of us there are, the messier it could be.
[10:28] <ajmitch> code would need revived & freshened
[10:28] <TheMuso> If we don't have something like that.
[10:29] <sistpoty> I guess I could set it up pretty quickly again, but the bug parser really should be redone (there was no x-launchpad thingy in bug mails at the beginning *g*)
[10:30] <ajmitch> should be a trivial task ;)
[10:30] <TheMuso> sistpoty: I am sure some of us would be happy to help you get it back up again.
[10:30] <TheMuso> But I think it should be ready before the new release cycle starts.
[10:30] <ajmitch> code is at http://tiber.tauware.de/~sistpoty/mergeWebTool/ in a bzr branch I think
[10:31] <sistpoty> that would be great... because it has had some issues at the past, where I'd have to manually fix things, and it would also be a great help if I there were more people who could then fix things ;)
[10:31] <sistpoty> and I must admit that I don't have much of a clue about the packages thingy I stole from ajmitch :P
[10:31] <ajmitch> heh
[10:31] <ajmitch> which thing was that?
[10:32] <sistpoty> ajmitch: it imported package versions from unstable into the database
[10:32] <ajmitch> ah
[10:32] <dholbach> with the use of tags it should be quite easy
[10:32] <ajmitch> ah yes, I see that code now
[10:32] <ajmitch> shameful ;)
[10:32] <sistpoty> hehe
[10:33] <dholbach> one could use python-launchpad-bugs for the launchpad end
[10:33] <sistpoty> dholbach: to file merge bugs? or for s.th. else?
[10:33] <ajmitch> sistpoty: I made it about 100x faster by using britney code
[10:33] <sistpoty> :)
[10:33] <TheMuso> Ok this python is a little beyond me. :)
[10:33] <ajmitch> which is what I use each night for the RC bugs list
[10:33] <dholbach> sistpoty: to get an overview over which bugs are filed, who filed them, etc etc
[10:34] <sistpoty> ah...
[10:34] <ajmitch> dholbach: instead of mail?
[10:34] <TheMuso> And I think a few of us have wishes that MOM had a comments field for packages. Should we pursue that with Scott?
[10:34] <dholbach> ajmitch: yeah, why not? I don't insist on it - was just an idea
[10:34] <ajmitch> either that or scrape the pages & add in annotatoin :)
[10:35] <Mithrandir> TheMuso: no, ask doko or me for MOM stuff now.
[10:35] <sistpoty> oh, we need also some script to actually file bugs... iirc the script from \sh: we had back then broke somewhen due to lp changing
[10:35] <TheMuso> Mithrandir: Oh ok.
[10:35] <ajmitch> Mithrandir: excellent :)
[10:35] <TheMuso> haha
[10:35] <ajmitch> sistpoty: just hack requestsync
[10:36] <sistpoty> good idea :)
[10:36] <ajmitch> though it can't tag by email yet
[10:37] <dholbach> python-launchpad-bugs can tag
[10:37] <ajmitch> useful
[10:37] <dholbach> http://people.ubuntu.com/~pitti/scripts/retag.py
[10:38] <TheMuso> Did we not have a package in universe that had useful MOTU tools at some stage?
[10:38] <dholbach> yeah, we should pursue that
[10:38] <dholbach> I'm sure everybody of us has nifty small tools that make life easier
[10:38] <TheMuso> Mostly tools others have written, but yeah.
[10:39] <sistpoty> how about starting a bzr-repo to collect useful scripts?
[10:39] <dholbach> who creates a motutools product in launchpad so we can have a bzr branch for that?
[10:39] <dholbach> branches
[10:39] <TheMuso> I can if people would like.
[10:39] <dholbach> great
[10:39] <sistpoty> :)
[10:40] <ajmitch> I know I had some of my stuff in a branch on tiber
[10:41] <dholbach> good to have it in LP
[10:41] <sistpoty> I guess the "something somewhere" is part of the problem ;)
[10:41] <TheMuso> Ok I'll do that after the meeting.
[10:41] <ajmitch> ;)
[10:41] <dholbach> ok... anything else?
[10:41] <TheMuso> And annouce to the ML.
[10:41] <dholbach> TheMuso: thanks a lot
[10:41] <sistpoty> next motu meeting time? 2 weeks from now?
[10:41] <TheMuso> ajmitch: COmmit them, and we can do it together. :)
[10:42] <dholbach> sistpoty: same time? later?
[10:42] <TheMuso> Yeah I can do that.
[10:42] <sistpoty> dholbach: maybe we should rotate times?
[10:42] <ajmitch> 2 weeks from now is just after Easter
[10:42] <TheMuso> I am happy to rotate.
[10:42] <sistpoty> (in case there won't be a conflict)
[10:42] <TheMuso> ajmitch: True.
[10:42] <ajmitch> rotating may be good, given how few people showed up here
[10:42] <TheMuso> I'll probably be catching up with a weekend's worth of email
[10:43] <TheMuso> After being away. :)
[10:43] <sistpoty> apr, 10 is tb meeting at 20.00utc, so we can't rotate to *that* time
[10:43] <sistpoty> (unless I can't count weeks now, like last meeting *g*)
[10:43] <dholbach> 18:00 utc then?
[10:44] <sistpoty> ok with me
[10:44] <dholbach> so we get the americans too
[10:44] <TheMuso> Um, if you want an aussie, I can't do that.
[10:44] <ajmitch> you can have a kiwi, as long as you supply the caffeine IV drip
[10:44] <TheMuso> ajmitch: hehe
[10:44] <ajmitch> (6AM for me)
[10:44] <ajmitch> 4AM for TheMuso & others in that area
[10:45] <dholbach> wed 20:00 utc?
[10:45] <TheMuso> Yeah thats fine.
[10:45] <ajmitch> ok
[10:45] <sistpoty> yep
[10:45] <TheMuso> I don't think it has to be two weeks exactly.
[10:45] <ajmitch> I think :)
[10:45] <dholbach> hang on
[10:45] <dholbach> there's edubuntu meeting
[10:46] <highvoltage> somoene said edubuntu meeting?
[10:46] <TheMuso> I think us down under will have to face the fact that we can't make all meetings.
[10:46] <dholbach> apr 11th
[10:46] <highvoltage> ah scheduling... (/me moves on)
[10:46] <sistpoty> mon 9 apr still contains no schedules *g*
[10:47] <dholbach> sistpoty: isn't that when easter still is?
[10:47] <TheMuso> We can't please everybody.
[10:47] <Hobbsee> ooh strike, the meeting!  just when i went afk for a while!
[10:47] <sistpoty> dholbach: right
[10:47] <sistpoty> now that explains why the slot is still empty *g*
[10:48] <dholbach> apr, 12th 20:00 utc then
[10:48] <ajmitch> Hobbsee!!
[10:48] <ajmitch> dholbach: alright ;)
[10:48] <dholbach> we have to make it a quick one, as the distro team meets one hour after that
[10:48] <sistpoty> dholbach: ubuntu dev team meeting
[10:48] <sistpoty> ah, right
[10:48] <dholbach> but given that we're short before release, there's not much to discuss anyway
[10:49] <ajmitch> april 12th, 20:00UTC will do
[10:49] <TheMuso> Yep sounds good.
[10:49] <dholbach> don't talk - fix bugs :)
[10:49] <ajmitch> ooh, friday 13th!
[10:49] <sistpoty> anyone unhappy with 12th, 20:00UTC?
[10:50] <ajmitch> nope :)
[10:50] <sistpoty> 3
[10:50] <sistpoty> 2
[10:50] <sistpoty> 1
[10:50] <sistpoty> set
[10:50] <sistpoty> :)
[10:50] <ajmitch> yay!
[10:50] <TheMuso> haha
[10:50] <dholbach> rock
[10:50] <Hobbsee> ajmitch!!!
[10:50] <dholbach> next universe hug day?
[10:50] <Hobbsee> sistpoty: i am.  grah.
[10:51] <Hobbsee> oh, i wont even make that, most likely
[10:51] <Hobbsee> but that's OK
[10:51] <sistpoty> hm... once again, /me was too quick
[10:51] <Hobbsee> that whole merging thing with comments would help
[10:51] <Hobbsee> but i never sued the dapper merging thing
[10:51] <ajmitch> I'd hope not
[10:51] <ajmitch> you weren't as involved back then though
[10:51] <TheMuso> ROFL
[10:52] <TheMuso> Sorry, I took that the wrong way.
[10:52] <ajmitch> my poor DSL line at home... ;)
[10:52] <dholbach> when is the next universe hug day?
[10:52] <dholbach> do you find it useful?
[10:52] <Hobbsee> ajmitch: true
[10:52] <Hobbsee> s/sued/used/
[10:52] <ajmitch> dholbach: friday?
[10:52] <TheMuso> I haven't been round for the last couple, so can't say.
[10:53] <dholbach> ajmitch: sounds good to me
[10:53] <dholbach> i'll write an announce
[10:53] <sistpoty> but I guess the hug days have been pretty good, weren't they?
[10:53] <TheMuso> Friday sounds good.
[10:54] <ajmitch> as well as fixes for my code for feisty
[10:55] <dholbach> thanks a lot everybody - I think we're all set with the meeting, right?
[10:55] <TheMuso> Yep.
[10:56] <TheMuso> I'll go grab some dinner, and will do the meetings/create motutools product.
[10:56] <dholbach> TheMuso: you rock
[10:56] <ajmitch> thanks!
[10:57] <sistpoty> thanks everyone!
[10:57] <ajmitch> dholbach: yep, meeting finished, etc :)
[10:57] <ajmitch> sistpoty can return to sleep
[10:57] <TheMuso> Ok, thanks all.
[10:57] <sistpoty> haha
[10:57] <dholbach> thanks all
[03:27] <deep> j #ubuntu-motu
[03:27] <deep> sry.
[04:20] <Phoenix24> @motu
[09:59] <Keybuk> looking at the agenda, this should be nice and quick :)
[10:00] <mjg59> Indeed
[10:00] <mjg59> We expecing mdz or Mark?
[10:00] <Keybuk> I was talking to mdz only a few minutes ago
[10:01] <Keybuk> so I'd expect so
[10:01] <mdz> evening all
[10:01] <mjg59> Evening
[10:02] <Keybuk> ok, so let's get started
[10:02] <mdz> https://wiki.ubuntu.com/TechnicalBoardAgenda
[10:03] <mdz> (hmm, need to update that template for the new motu process)
[10:03] <mdz> I'm not aware of any core-dev applicants today, are you?
[10:03] <mjg59> Nope
[10:03] <Keybuk> none that I'm aware of
[10:04] <mdz> there is one motu application pending confirmation
[10:04] <mdz> Lionel Le Folgoc
[10:04] <mdz> I haven't reviewed it yet
[10:04] <mdz> just received today
[10:04] <Keybuk> I had reviewed it, and was happy
[10:04] <mdz> ok, your ack is sufficient to effect the change in LP
[10:05] <Keybuk> done
[10:05] <Keybuk> (when beta does it)
[10:05] <mjg59> I concour, for the record
[10:05] <mdz> Keybuk: will you also send a welcome to -devel?
[10:06] <Keybuk> do we have a template for that?
[10:06] <Keybuk> ah, I see dholbach has one
[10:07] <mdz> Keybuk: you can use the last one I sent as a template
[10:07] <mdz> and maybe put it into a wiki somewhere
[10:07] <Keybuk> yup
[10:08] <mdz> thanks
[10:08] <mdz> is there any other business?
[10:09] <mdz> short and sweet
[10:09] <mdz> thanks all
[10:09] <Keybuk> thanks
[10:37] <Daviey> @schedule london
[10:37] <ubotu> Schedule for Europe/London: Current meeting: Technical Board | 28 Mar 21:00: Edubuntu | 28 Mar 23:00: Xubuntu | 29 Mar 22:00: Ubuntu Development Team | 01 Apr 21:00: Marketing Team | 02 Apr 16:00: Community question time


[08:29] <free> wgrant: hey there, around?
[08:31] <wgrant> free: Hi
[08:32] <free> wgrant: hi, I was wondering if you noticed this txlongpoll MP from a while back https://code.launchpad.net/~free.ekanayaka/txlongpoll/fast-rabbit-reset/+merge/278287
[08:34] <wgrant> free: I didn't. Let me see.
[08:35] <free> wgrant: cheers
[08:35] <wgrant> free: There's no better solution for that OptimisingTestSuite hack in __init__.py?
[08:36] <free> wgrant: not if we want to avoid to create a specialised test runner
[08:36] <free> wgrant: or introduce runner-specific idioms
[08:46] <wgrant> free: Isn't that already runner-specific, by patching testtools.run?
[08:46] <wgrant> I might be slightly more comfortable with a custom entrypoint, but surely there's a better way :(
[08:47] <free> wgrant: testtools.run by itself is not test-runner specific, afaict
[08:47] <free> wgrant: testools is unittest.TestCase compatible
[08:48] <wgrant> free: But isn't testtools.run the testtools testrunner?
[08:48] <wgrant> lifeless: Maybe you have suggestions on the best way to do this :)
[08:52] <free> wgrant: yeah that's true, I think I have been running tests with a different runner and it was working because atm there's no assumption on the runner. But subclassing the testtools runner and making it mandatory sounds fine
[08:57] <free> wgrant: there is probably going to be a bit of annoyance for supporting subunit output, so I think I'll need to grow the branch a bit and basically create a subclass of testtools' runner that also handles subunit output. That's essentially what I meant above
[09:00] <free> wgrant: also looking better, at the moment my reading is that we don't really use testtools.run at all, since the check target in Makefile calls "bin/testpy -m subunit/run -- discover" and bin/testpy just sets sys.path. So we use the subunit runner.
[09:00] <wgrant> Yeah, I ignored the makefile because the buildout seems to have bitrotten somewhat.
[09:02] <free> wgrant: yeah, I guess that's the reason why just ran the tests with a random runner, which worked fine iirc (now looking again)
[09:04] <free> wgrant: "make check" seems to work fine in trunk actually, except for some spurious output that my branch fixes
[09:04] <wgrant> free: Branch looks fine apart from that. I'll see if Robert replies, if not then it'll do :)
[09:05] <wgrant> Thanks.
[09:06] <free> wgrant: looking at that now, I might add a custom runner to make things cleaner. Unfortunately this is a known limitation of testresources.OptimisingTestSuite, because there's no standard way of telling a runner to use it
[09:06] <wgrant> free: Right, I remember running into this once in the past.
[09:06] <wgrant> Quite possibly this very case, in txlongpoll.
[09:06] <wgrant> So I just gave up :(
[09:06] <wgrant> But a custom runner seems sensible here, I think.
[09:09] <free> wgrant: fwiw if you have troubles with buildout, I think this is the culprit https://pastebin.canonical.com/157090/ (from README)
[09:12] <wgrant> free: I ran into the setup_requires pbr mess and just fell back to pip+virtualenv without debugging.
[10:06] <free> wgrant: fyi I've pushed r91 which removes the monkey patching hack and fixes the buildout breakages that I could spot
[10:10] <lifeless> wgrant: 'sup?
[10:13] <lifeless> free: have you filed a bug on the tearDown + inlinecallbacks issue?
[10:13] <lifeless> free: seems like a genuine bug
[10:14] <lifeless> free: wgrant: threw a review comment up
[10:15] <lifeless> free: there is a standard way
[10:15] <lifeless> free: https://docs.python.org/2.7/library/unittest.html#load-tests-protocol
[10:15] <free> lifeless: yeah but is it supported by testtools/subunit?
[10:16] <free> reading the comment
[10:16] <free> lifeless: ah yeah *that* way, but does it require to add that function in every file?
[10:17] <lifeless> free: no, you add it to __init__.py
[10:17] <free> lifeless: ah nice
[10:17] <lifeless> free: (needs unittest2 or python3.5 because of various bugs, but testtools depends on unittest2 for that reason)
[10:17] <free> lifeless: I see
[10:18] <lifeless> free: https://github.com/testing-cabal/testrepository/blob/master/testrepository/tests/__init__.py#L57
[10:19] <free> lifeless: re AsynchronousDeferredRunTest, probably a genuine bug, yes, I guess I'll file one and propose a branch. I've also noticed that it breaks with latest Twisted 16.2.0 (because of the move from twisted.python.log to twisted.logger)
[10:19] <lifeless> free: thanks
[10:21] <free> lifeless: is the load_tests convenience in testresources release? if not I might just copy it
[10:21] <free> s/realease/released/
[10:22] <lifeless> free: thats the concrete one from testrepository :)
[10:22] <lifeless> free: just copy what you need from it :)
[10:22] <free> lifeless: ah :)
[10:34] <free> lifeless: pushed r93 which drops the custom runner
[11:16] <lifeless> free: one nit
[11:17] <free> lifeless: hm did you post it?
[13:37] <free> wgrant: does Launchpad invoke txlongpoll as standalone deamon with something like "twistd txlongpoll -c /some/config.yaml" or do you have a more sophisticated deployment?
[13:44] <cjwatson> free: Slightly more sophisticated but not by much; https://git.launchpad.net/launchpad/tree/lib/lp/scripts/runlaunchpad.py#n241
[13:44] <cjwatson> (or less sophisticated, depending on your point of view)
[13:46] <cjwatson> TxLongPollServer is TxLongPollFixture with service_config set to "[txlongpoll]\nfrontend_port: %d\n" % config.frontend_port
[13:47] <cjwatson> And txlongpollfixture is https://pypi.python.org/pypi/txlongpollfixture
[13:52] <free> cjwatson: ah I see, that's on the "unsophisticated" side with respect to the quesiton above. I mainly wanted to know if you were using lower-level APIs like QueueManager and FrontEndAjax directly or via the plugin, and it seems the latter
[13:53] <free> cjwatson: or perhaps you do use QueueManager elsewhere in other LP services for publishing AMQP messages to be consumed by txlongpoll?
[13:55] <cjwatson> free: I'm no expert here but I think we just use our own more generic AMQP code for that
[13:56] <cjwatson> We don't use QueueManager or FrontEndAjax, at least, and our only direct txlongpoll imports are in the code that starts the service
[13:57] <free> cjwatson: okay thanks, I was considering changing the API of QueueManager slightly to leverage some new twisted features like ClientService and simpliyfing the code. Also, it'd help a bit Landscape which uses that stuff a bit more intrusively. Just wanted to know what the impact on LP would be. Anyway, nothing fully concrete for now.
[13:58] <cjwatson> Right, I don't think we care about that level of detail at the moment.
[13:58] <free> cjwatson: cool
[13:59] <free> cjwatson: are you depending on some twisted version or are you generally tracking the latest (e.g. with backported debs or buildout/virtualenv) ?
[14:00] <cjwatson> free: haha a sad story
[14:00] <cjwatson> free: we're stuck on a patched version of 13.0.0 at the moment because newer versions end up pulling in pbr which is hell with buildout
[14:01] <free> cjwatson: understandable
[14:01] <cjwatson> free: plan is to move to virtualenv/pip but it's fairly complicated
[14:01] <free> cjwatson: I'll avoid touching anything that requires >13 then, for the time being
[14:01] <cjwatson> free: anyway, don't worry about that from txlongpoll's point of view, we have no pressing reason to upgrade it
[14:02] <cjwatson> free: lots of our dependencies are blocked on this overall issue at the moment, one more would be no big deal
[14:02] <free> cjwatson: yeah is still nice to know that you're running trunk and you can upgrade txlongpoll at any time
[14:02] <cjwatson> true; I'm not sure I've ever touched any longpoll code in LP :)
[14:02] <free> cjwatson: so I'd prefer preventing you guys on having yet another block
[14:03] <cjwatson> I'm hoping to be able to find time to finish off the virtualenv/pip migration in a couple of months
[14:03] <cjwatson> we need to be able to move to new twisted for improved crypto support, new zope for all kinds of reasons, new testtools, etc.
[14:04] <free> cjwatson: yeah, it's not hard to keep backward compatibility in txlongpoll, even if I end up needing a few tweaks
[14:04] <cjwatson> OK
[19:59] <lifeless> free: I thought so?
[20:00] <lifeless> free: I clicked on a line, entered a commment and hit ctrl-enter
[20:01] <cjwatson> lifeless: that stages an inline comment, but you also have to submit the form as a whole (can be an empty comment - there should be a checkbox for whether to include inline comments)
[20:01] <cjwatson> it is possibly slightly odd but allows for easy batching of a whole review
[20:04] <lifeless> ok done
[20:04] <lifeless> cjwatson: trap for new players; not specially weird, but was not clear
[20:08] <cjwatson> lifeless: I agree; bug welcome.  It does IIRC say "Unsaved comment" but there should probably be a clearer indication of what you need to do to save it
[20:19] <lifeless> https://bugs.launchpad.net/launchpad/+bug/1585354 for your prioritising pleasure
[20:31] <free> lifeless: replied, it's actually a real documentation fix
[20:50] <lifeless> free: k
[22:02] <blr> cjwatson: lifeless: it is a bit awkward having to make a comment (e.g. 'see inline comments') to save an inline comment.
[22:03] <blr> not really sure what a good solution would be however...
[22:04] <blr> cjwatson: perhaps the problem is the email threshold should be higher?
[22:05] <cjwatson> I don't know what threshold you mean


[01:18] <tsimonq2> pleia2: Done
[01:19] <guiverc_t> i see canonical news; has someone added planet (nothing interesting etc) or not?  .. am starting to look anyway
[01:20] <pleia2> haven't added
[01:20] <pleia2> tsimonq2: thanks, it's been a busy week over here
[01:21] <guiverc_t> well i'm reading thru via my rss feeds (planet) & adding any i think worthwhile
[01:21] <pleia2> ty
[01:22] <guiverc_t> ps:  i'm slow as reading any that interest me, ie. not just UWN read..
[01:22] <tsimonq2> pleia2: Does it look good?
[01:22] <tsimonq2> OH
[01:23] <tsimonq2> On phone with grandma, I'll fix it soon
[01:24] <pleia2> still need the citation
[01:24] <tsimonq2> yeah that
[01:24] <pleia2> :)
[01:24] <tsimonq2> grandma
[01:25] <tsimonq2> :P
[01:26]  * pleia2 meetup
[01:27] <pleia2> tsimonq2: also, are you not using the script? the script writes the citation for you, no mistakes about formatting :)
[01:27] <guiverc_t> nah see nothing in planet ; one general OSS & one cute konqi pic but not *buntuy
[01:29] <pleia2> boo, slow news week for our 500th edition
[01:30] <pleia2> ok, for real, should focus on this meetup ;)
[02:04] <tsimonq2> pleia2: Just had a nice conversation with my grandma, she's in Tuscon for the winter. ;)
[02:04] <tsimonq2> Ok, so back to this.
[02:05] <tsimonq2> pleia2: No, I didn't think of the scrip[t
[03:44] <guiverc_t> fyi:  just looked and don't see a summary writers email....    (i'm not doing well pain|health wise so not doing much anyway)
[03:48] <tsimonq2> guiverc_t: It's Thursday ;)
[03:49] <tsimonq2> When I wake up tomorrow, I can look it over and send it.
[03:58] <guiverc_t> wtf:   i thought it was friday hours ago, but started when I wrongly thought it was saturday...  which way is up??
[03:59] <guiverc_t> its still early arvo here - i'm going to bed too!  i'm just not with it.
[04:05] <pleia2> guiverc_t: I hope you feel better <3
[04:06] <pleia2> and I thought you were just getting a head start on tomorrow :)
[04:26] <guiverc_t> :) @ pleia2     alas no, but thanks  (i'm still in doc; will try and complete one i started later)
[08:48] <PaulW2U> added some blogosphere articles and some re beta release to prep doc