[02:18] <jbicha> robert_ancell: did you see https://code.launchpad.net/~jbicha/lightdm/have-lib-only-suggest-lightdm/+merge/184439 ?
[02:19] <robert_ancell> jbicha, makes sense to me
[02:20] <robert_ancell> jbicha, actually, can you do a quick merge with trunk and bump the version number?
[02:20] <robert_ancell> Then can land
[02:21] <jbicha> ok, I did that earlier today but I can do it again if it will be accepted :)
[02:22] <robert_ancell> jbicha, sorry :)
[02:23] <jbicha> done, thanks :)
[02:25] <didrocks> robert_ancell: please no more lightdm today
[02:25] <robert_ancell> didrocks, why not? I hear you love LightDM!
[02:26] <didrocks> robert_ancell: we already try to stabilize the ubuntu-touch image
[02:26] <didrocks> and having stuff changing is making it… hard ;)
[02:26] <didrocks> not a question of love/hate ;)
[03:38] <cyphermox> didrocks: https://code.launchpad.net/~mathieu-tl/unity-system-compositor/0.0.1+13.10.20130903-0ubuntu2/+merge/184917
[03:39] <didrocks> approved
[04:04] <Mirv> wow, arm64 has cu2d in jenkins and apparently needs cu2d-skip for mir
[04:04] <Mirv> how it has arrived there is beyond me, the PPA doesn't have it so obviously it's not finished "building"
[04:05] <Mirv> cu2d has arm64, not arm64 has cu2d, need to finish this coffee
[04:10] <Mirv> didrocks: cyphermox: any idea where that arm64 has come from to cu2d, and maybe it shouldn't be there?
[04:16] <Mirv> oh, great, it does happen now with each stack, so each stack is halted because it waits for non-existend arm64 build eternally
[04:17] <Mirv> but, I'm happy to see unity8 has landed, so we're on our way away from manual publishing
[04:23] <didrocks> Mirv: I think the support in the ppa is coming
[04:23] <didrocks> Mirv: I'm totally exhausted, can you try to ignore arm64 like we do for powerpc if there was no build before in cu2d?
[04:23] <didrocks> the code should be straightfoward
[04:24] <didrocks> now that unity8 landed, I'll EOD
[04:24] <Mirv> didrocks: sure, sure, go sleep, I'll look or if nothing else I'll keep cu2d-skip:ing :)
[04:25] <didrocks> Mirv: thanks! ;)
[04:25] <didrocks> Mirv: just don't publish before asac or I ack on those, we need the current image
[04:25] <Mirv> yeah, I know
[04:26] <didrocks> oh, in fact I can push that quickly and run
[04:26] <didrocks> if things explodes, it's not me
[04:27] <didrocks> Mirv: is it waiting on arm64 or armel64?
[04:27] <didrocks> (the exact string)
[04:28] <Mirv> didrocks: arm64, I see it could be added to cupstream2distro/settings.py
[04:28] <didrocks> Mirv: right, just pushing quickly, one sec
[04:28] <didrocks> and pulling on mangers
[04:28] <Mirv> ok
[04:29] <didrocks> Mirv: as you probably figured out: http://bazaar.launchpad.net/~cupstream2distro-maintainers/cupstream2distro/trunk/revision/386
[04:30] <Mirv> yep
[04:30] <didrocks> deployed on magners, so next tick should be fine
[04:30] <Mirv> grep -r powerpc made it quite easy find
[04:30] <Mirv> cool, thanks
[04:30] <didrocks> heh, I didn't even remember I used an array
[04:30] <didrocks> FYI, we workarounded the DNS issue
[04:30] <didrocks> so we should be safer for that
[04:31] <didrocks> everything should be fine today
[04:31] <didrocks> or at least, "finer" if I would say so
[04:31] <didrocks> time to go to bed, good luck Mirv, have a nice day!
[04:31] <Mirv> thanks, g'night!
[04:31] <didrocks> thx!
[08:04] <Laney> morning
[08:06] <darkxst> hi Laney
[08:06] <Laney> hello darkxst
[08:06] <Laney> how do?
[08:08] <hyperair> lwl/w #bakabt
[08:08] <hyperair> oops
[08:08] <Laney> nice password
[08:08] <hyperair> that's not a password. i was trying to switch windows
[08:08] <Laney> suuuuuuuuuuuuure :P
[08:08] <hyperair> but this happened enough times to make that assumption eh? =p
[08:08] <Mirv> so you even try to avoid the need to change the password by claiming it didn't leak ;)
[08:08] <hyperair> i think i typed my password into ##c++ once and #ck once
[08:09] <hyperair> Mirv: eh well you're free to go try that password elsewhere :)
[08:09] <Mirv> hehe
[08:09] <Laney> OH GOD HAND ME THE MIND BLEACH
[08:09] <hyperair> my username's hyperair everywhere except steam (it's hypera1r there because somebody took my nickname. *shakes fist*)
[08:09] <Laney> why do you have that kind of stuff in your email?!
[08:09] <darkxst> Laney, yeh good, nice spring weather here now ;)
[08:09] <hyperair> Laney: that was a honeypot account
[08:09]  * hyperair whistles
[08:11] <Laney> you got me good
[08:11] <Laney> darkxst: heading the opposite way for us now :(
[08:11] <Laney> still managed to get out on the bike yesterday
[08:11] <darkxst> nice, I have to wait until the weekend for another ride
[08:15] <darkxst> Laney, my bike has been feeling its age of late, been spending as much time fixing as riding, although getting close to being a brand new bike again!
[08:16] <Laney> mine is new enough to not have those kind of problems yet
[08:16] <Laney> which is good because I don't really know much about fixing stuff :P
[08:24] <darkxst> and mine is too expensive to replace very often!
[08:24] <Laney> hehe
[08:24] <Laney> they are skills that are good to have
[08:25] <Laney> probably need a new chain actually
[08:26] <darkxst> bikes are rather overpriced here, but either way I could buy a cheap car cheaper than my MTB!
[08:43] <mlankhorst> your *expensive* MTB :P
[09:03] <Mirv> sil2100: can you approve the branch from status page before your next tick?
[09:08] <darkxst> mlankhorst, all good MTB's are expensive!
[09:08] <xnox> darkxst: mostly yes.
[09:08] <Laney> woah channel switch
[09:15] <sil2100> Mirv: doing...
[09:17] <Mirv> sil2100: thanks!
[09:17] <Mirv> deploying
[09:19] <darkxst> xnox, there is some bit you don't like?
[09:19] <sil2100> Mirv: feeling sicklish today, had only a few hours of sleep - how are the stacks today?
[09:20] <Mirv> sil2100: did you read my e-mail? the stacks status is getting better all the time now.
[09:20] <sil2100> Mirv: yes, I read the e-mail, but heard about some arm64 pop-ups there
[09:20] <Mirv> sil2100: take care, hopefully you'll feel better soon
[09:20] <sil2100> Do we have to cu2d-skip that every time, or is this arch ignored by cu2d automatically?
[09:20] <Mirv> sil2100: yeah so the fix fixed it
[09:21] <Mirv> that was proven now during this 2nd tick of mine
[09:21] <Mirv> ignored as was previously done with powerpc
[09:21] <seb128> sil2100, you might want to ask on #ubuntu-devel about the arm64 thing, cjwatson or the launchpad guys (wgrant/StevenK/infinity) might have a clue what's going on
[09:22] <Mirv> seb128: I resolved it with didrocks in the morning already
[09:22] <seb128> ok, do you know where the arch was added? to launchpad?
[09:22] <seb128> do they plan to enable the port soon?
[09:23] <Mirv> seb128: not exactly, but yes apparently it's planned to be enabled now soon and coming to PPAs as well
[09:23] <Mirv> I mean, I don't know exactly
[09:23] <Mirv> and that's why it hit cu2d as well, as it started waiting on arm64 builds that didn't happen
[09:23] <sil2100> Mirv: btw. do you know anything about the unity8/platform bits? Do you know if Ricardo was able to get a nice binary copy of the packages?
[09:23] <seb128> Mirv, how did you get it fixed?
[09:23] <sil2100> asac: ^ ?
[09:24] <Mirv> sil2100: it seems stuff landed yesterday, but we're still not touching anything until asac/didrocks say otherwise
[09:24] <sil2100> seb128: cu2d now automatically 'doesn't care' about arm64 it seems, we have that for powerpc as well
[09:24] <seb128> k
[09:24] <Mirv> seb128: we added arm64 to be in the same list as powerpc
[09:25] <Mirv> to 'ARCHS_TO_EVENTUALLY_IGNORE' in cupstream2distro settings.py
[09:37] <seb128> sil2100, Mirv: thanks
[09:37] <seb128> sil2100, Mirv: do you think we could publish indicators today or is that blocked on asac/didrocks' to approve as well?
[09:38] <seb128> qengho, hey, did you get a fixed chromium-browser ready for upload (do you need sponsoring)?
[09:38] <seb128> chrisccoulson, hey, ^ do you know?
[09:39] <sil2100> seb128: not sure what the status is today, but I guess it would be alright to publish that, as it has those important things right?
[09:39] <sil2100> The next tick should fix the Indicator stack
[09:39] <chrisccoulson> seb128, i don't sorry (i've just had 2 days off, so still catching up)
[09:39] <seb128> sil2100, yes, that has important fixes for the messaging menu on the phone and for the hud
[09:39] <seb128> chrisccoulson, ah, welcome back ;-)
[09:40] <seb128> chrisccoulson, I hope you had a good mini-holiday! did you go anywhere?
[09:40] <Mirv> seb128: seems blocked if I understand this correctly '< didrocks> Mirv: just don't publish before asac or I ack on those, we need the current image'
[09:40] <chrisccoulson> seb128, yeah, we went to legoland :)
[09:40] <Mirv> seb128: meanwhile that config commit I got sil2100 to approve might mean successful build & autopilots on indicators stack, which would then mean possibility to ask for permission to publish it
[09:41] <seb128> chrisccoulson, nice!
[09:41] <sil2100> ;)
[09:41] <sil2100> Mirv: ok, good to know
[09:41] <seb128> Mirv, great!
[09:42] <sil2100> Just hope didrocks or asac will be up in the next few hours
[09:42] <Mirv> well didrocks went to sleep 5h ago, so depending on how much sleep he needs :)
[09:42] <Laney> seb128: don't you want the buildClickView branch reviewed then?
[09:43] <Laney> oh, it misses the new files, that makes a bit more sense
[09:44] <seb128> Laney, I welcome input/comments on it
[09:45] <ochosi> hi Laney
[09:45] <seb128> Laney, doh, I forgot to bzr add those? fixing
[09:46] <Laney> seb128: yeah, see the bot's angry message
[09:46] <Laney> hi ochosi
[09:46] <ochosi> Laney: sorry for pinging you out of the blue, i'm part of the xubuntu team (mostly dealing with artwork) and maintaining lightdm-gtk-greeter
[09:47] <ochosi> Laney: you submitted a patch a while back for xfce4-session and logind (if i'm not mistaken)
[09:47] <Laney> I kind of remember that
[09:47] <ochosi> Laney: which fixed reboot and shutdown, but at the moment logout still seems broken
[09:47] <ochosi> and we noticed because the greeter was misbehaving
[09:47] <ochosi> so i tried to fix the greeter (robert gave me a few pointers)
[09:48] <ochosi> but that didn't work, and then i realized that it takes me 8+ seconds to logout (when it used to take me 1sec on raring with the same machine)
[09:48] <ochosi> so i drew a connection and started to read xfce4-session's source, but i'm just not familiar enough with sessions and logind to be able to fix this
[09:48] <ochosi> so i cowardly come to you for help
[09:49] <seb128> Laney, did you find a good tutorial for QAbstractListModel? that api seems complex (at least compared to using a List<QObject*>), I'm not sure if it's overdoing it for the simple model we have there (no filtering needed, though we need sorting ...)
[09:50] <Laney> ochosi: not sure that I'm going to be able to help there :-/
[09:50] <Laney> we have some problems like that in ubuntu too that we haven't debugged yet
[09:51] <ochosi> Laney: oh, you do? could you ping me when you start the debugging? (or is there a bugreport yet?)
[09:51] <Laney> yeah logout taking a while, seems like it hits some timeout
[09:52] <ochosi> here it also seems to crash the session or something
[09:52] <ochosi> but tbh i'm not a debugging master and now that xsession-errors seems kinda gone and half-empty i'm not sure where to look anymore
[09:52] <Laney> are you on upstart user sessions?
[09:52] <Laney> if so: ~/.cache/upstart/<service>.log.*
[09:53] <Laney> seb128: hmm, don't remember a tutorial
[09:53] <Laney> seb128: anyway, that's something I've done before so I could look at that for storage if you want
[09:53] <Laney> it does make things nice from the qml side if you do it using models in cpp
[09:53] <ochosi> Laney: startxfce is there, so far i haven't found anything useful there
[09:57] <seb128> Laney, after spending 1 day on that code I start really liking my few lines of js better :p
[09:59] <Laney> heh
[09:59] <Laney> well, leave it to me if you like
[09:59] <Laney> otherwise I'm a bit unsure of what setting to work on next
[10:03] <seb128> Laney, well, I'm done with that, as said I'm on vac tonight for 1.5 week, I don't want to spend my day on that, need to put things in order for the week I'm not there
[10:03] <Laney> ok
[10:03] <seb128> Laney, so if you want to pick it up and turn it to a qabstractmodel please do
[10:03] <Laney> will do some of that then
[10:03] <seb128> Laney, I mostly put it up because it has the json parsing done, so it's a base
[10:03] <Laney> so yeah kind of stuck for what settings to do otherwise
[10:03] <Laney> got any ideas?
[10:04] <sil2100> hm, is LP down for you guys as well?
[10:04] <Laney> yes, maintenance
[10:04] <seb128> sil2100, yes
[10:04] <seb128> sil2100, usually a few minutes I think
[10:04] <sil2100> ACK, thanks
[10:04] <Laney> https://twitter.com/launchpadstatus/status/377723930133274624
[10:04] <seb128> Laney, things that you can help on if you are looking for idea:
[10:04] <sil2100> Bad timing, as the next tick just started...
[10:04] <seb128> - the click model
[10:04]  * sil2100 sighs
[10:05] <sil2100> We're all red again
[10:05] <seb128> - Laney: backporting https://git.gnome.org/browse/glib/commit/?id=6ec2bb17c393c411a2182e865aa0979165dfbac5 and using it to get the size of the xdg directories in storage
[10:05] <seb128> e.g video, music
[10:05] <seb128> Laney, libgdata handing tests
[10:05] <seb128> Laney, building e-d-s without goa on armhf
[10:05] <Laney> handing tests?
[10:05] <Laney> hanging?
[10:05] <seb128> hanging
[10:06] <Laney> aha
[10:06] <seb128> yes
[10:06] <seb128> https://launchpad.net/ubuntu/+source/libgdata/0.14.0-1ubuntu1
[10:06] <Laney> yeah saw that
[10:06] <seb128> Laney, do you have access to https://docs.google.com/a/canonical.com/document/d/1Anaxk4gaIjAJYdgpKICwxRpEinCVprIHl01sOGDaCFs/edit ?
[10:07] <Laney> seems so
[10:07] <seb128> Laney, ok, I'm going to add comments on that, but that's the current list of things we think need to be done/postponed
[10:09] <Laney> changing OSK options is what attente has a branch up for atm
[10:09] <seb128> right
[10:09] <Laney> or is it not hooked up in maliit yet?
[10:09] <seb128> they have an ini style config
[10:09] <seb128> we had a meeting about that 10 days ago
[10:09] <seb128> they plan to port ubuntu-keyboard's config to gsettings
[10:09] <seb128> I don't think that happened yet though
[10:10] <Laney> yeah it uses QSettings
[10:10] <Laney> seems alright though if it works
[10:10] <seb128> right
[10:11] <seb128> Laney, anyway, the click model and the xdg disk space are good ones to work on next, then power maybe (the wifi on/off might be better off using the dbus status/get dynamic update, bluetooth should be easy to do using dbus methods as well I think, and the screen brightness slider should copy what indicator-power does)
[10:13] <Laney> those last ones in the battery panel you mean?
[10:13] <seb128> Laney, yes
[10:13] <Laney> ok
[10:13] <Laney> seems like a decent list, thanks
[10:13] <seb128> yw
[10:13] <Laney> i'll be off friday and monday anyway
[10:13] <sil2100> seb128, Laney: related to the settings, is it normal that I can't change the background wallpaper? How can I do that? Since when I access 'Background', I get the two 'Welcome screen' and 'Home screen' images but clicking on them doesn't work - am I doing anything wrong?
[10:14] <Laney> sil2100: I haven't been tracking that since Ken started working on the content hub stuff
[10:14] <Laney> but I thought someone made it work
[10:14] <sil2100> I could try working on that as a first thing for familiarization, just wanted to make sure it's not just broken on my device
[10:15] <Laney> maybe it was blocked by the delayed releases
[10:16] <seb128> sil2100, the fix for the gallery activation is pending landing since thursday or something :/
[10:16] <Laney> sil2100: Getting rid of the snail and cogs would be good
[10:16] <Laney> i.e. use the default unity8 does
[10:16] <sil2100> Maybe, I built and installed the latest u-s-s on the device, so it should be the latest one I guess...
[10:16] <seb128> sil2100, that's using the file picker which is supposed to spawn the gallery app, but the spawning was not done
[10:16] <seb128> sil2100, the fix is in content-hub
[10:16] <sil2100> Ah, ACK
[10:16] <Laney> if you want somethingn to work on
[10:17] <sil2100> Good to know ;)
[10:17] <seb128> sil2100, http://bazaar.launchpad.net/~phablet-team/content-hub/trunk/revision/35
[10:17] <sil2100> Laney: hm, ok, is there a bug for that already?
[10:17] <seb128> sil2100, we need that to land
[10:17] <Laney> no
[10:17] <sil2100> seb128: noted!
[10:17] <Laney> just look at the fallback logic
[10:17] <Laney> it's for what happens if you pick an invalid image
[10:17] <Laney> i.e. in gnome you can have these .xml files
[10:17] <Laney> or some corrupt file or so
[10:18] <Laney> you need to fall back to something - see what unity does there and copy that
[10:18] <sil2100> Laney: ACK ;)
[10:18] <seb128> Laney, can you open a bug for tracking maybe?
[10:18] <Laney> ok
[10:18] <seb128> thanks
[10:19] <Laney> It shouldn't be that much work as there's already logic in there for trying to load an image and doing something if that fails
[10:19] <Laney> it's making the "something" not be "set my background to a picture of a snail"
[10:20] <seb128> sil2100, Laney: I'm going to file some bugs today, for the things I know that are missing/buggy/todo
[10:20] <seb128> that should help having a list of things to pick up
[10:20] <Laney> as much as I do like seeing that thing around the place :-)
[10:20] <seb128> ;-)
[10:20] <sil2100> \o/
[10:20] <sil2100> Laney: ;D
[10:24] <Laney> hmm, actually, I guess you want to fall back to the default wallpaper
[10:25] <Laney> filed anyhow
[10:26] <seb128> chrisccoulson, is there a place where qengho usually puts chromium updates when they need sponsoring?
[10:32] <seb128> sil2100, you might want to look at bug #1221179
[10:32] <ubot2`> Launchpad bug 1221179 in ubuntu-system-settings "[background] image previews should include shell components" [Low,Confirmed] https://launchpad.net/bugs/1221179
[10:33] <seb128> sil2100, we don't have the asset but it should be possible to get the code ready with a faked image/local hack
[10:33] <seb128> sil2100, it's basically stacking asset from unity/greeter ui on top of the image
[10:33] <sil2100> Ah, sounds fairly simple indeed!
[10:34] <Laney> I decided the fallback case was more complex and added some of my annoying thoughts to the bug
[10:34] <sil2100> seb128: I'll assign this to myself for starters maybe, then look at Laney's proposition inbetween stack and appmenu-qt5 actions :)
[10:34] <Laney> https://bugs.launchpad.net/ubuntu-system-settings/+bug/1223798
[10:34] <ubot2`> Launchpad bug 1223798 in ubuntu-system-settings (Ubuntu) "[background] Remove initial fallback images" [Undecided,New]
[10:35] <Laney> there's some thinking to be done there unless I've gone nuts
[10:35] <seb128> sil2100, great, thanks
[10:35] <Laney> yes, welcome to the u-s-s team
[10:35] <Laney> muhahaha
[10:36]  * sil2100 is scared
[11:02] <sil2100> seb128: btw. is it 'safe' to install the touch ubuntu-system-settings on my desktop system?
[11:11] <seb128> sil2100, sure
[11:11] <Laney> that's how we develop it
[11:11] <seb128> sil2100, I do 95% of my work/testing on the desktop, I just run it once every now and then on the device to check that everything is ok and see how it behaves with touch
[11:23] <seb128> dpm, hey
[11:23] <dpm> hi seb128
[11:24] <seb128> dpm, replying there to your launchpad question, that bug means the pot of all sources under daily landing are not updated
[11:25] <seb128> dpm, daily landing includes all unity, indicators, touch components, settings, sdk, etc
[11:26]  * seb128 kicks firefox, you piece of c***
[11:27] <seb128> it's downloading stuff when it said download failed, without telling me what nor letting me a way to stop the downloads
[11:30] <dpm> seb128, ah, thanks, I wasn't sure I could follow it. But it is not the builders task to update the templates according to the package rules when the packages are uploaded? I thought that happened automatically. Or is it just about those updated .pot files from the tarballs not getting updated in https://translations.launchpad.net/ubuntu ?
[11:30] <seb128> dpm, it's about the .pot/.mo files not being imported from the build dir to launchpad
[11:31] <seb128> dpm, e.g the translations tarball generated on the builders is not used
[11:48] <seb128> dpm, basically we should manually update all those pots before saucy I guess :/
[11:48]  * dpm otp, bbiab
[12:04] <seb128> chrisccoulson, help, how do I stop firefox to keep downloading stuff that he claims failed to download?
[12:05]  * seb128 kicks firefox in the nuts
[12:21] <Mirv> sil2100: https://code.launchpad.net/~timo-jyrinki/cupstream2distro-config/platform_additions/+merge/185032
[12:24] <sil2100> Mirv: finishing lunch and approving ;)
[12:24] <qengho> seb128: On Chromium, I have the two known bugs fixed, but there's one additional webapps-related bug I want to squash also.
[12:25] <seb128> qengho, hey ... ok, do you have an eta on that? we need to get the other ones fixed
[12:25] <sil2100> Mirv: things are building a long time today...
[12:26] <qengho> seb128: Want these now and another package in a day?  It's hard to estmate the unknown.
[12:26] <Mirv> sil2100: yes, there are clearly some performance problems now
[12:27] <seb128> qengho, well, I don't want to end up like the previous time, where "it's going to be fixed in the next update, just one thing to sort out" took weeks
[12:27] <seb128> qengho, what's the webapp issue and its impact?
[12:28] <pitti> hey hey
[12:28] <qengho> Open a webapps page first from a docked icon. Then open normal window. Normal window doesn't respond to Ctrl-T tab opening.
[12:28] <seb128> pitti, good morning!
[12:28] <pitti> seb128: ça va ?
[12:28] <qengho> seb128: ^
[12:28] <seb128> qengho, ok, that doesn't seem worth delaying the other fixes, can be in another upload next week imho ... what do you think?
[12:28] <seb128> pitti, très bien, et toi ?
[12:28] <Mirv> sil2100: how about this one https://code.launchpad.net/~timo-jyrinki/cupstream2distro-config/mirslave_allow_both_libmirclient2_and_3/+merge/185034 - it seems that it was not a good idea to replace 2 with 3 in the previous commit, since it tries to actually install both at the moment
[12:29] <seb128> qengho, currently we have upgrades that hit package conflicts and some users who can't use their browser because they are missing the UI elements ... let's get those fixed
[12:29] <sil2100> Checking the diff
[12:29] <seb128> qengho, there is going to be another upload soon enough which can fix the webapp issue
[12:30] <pitti> seb128: mon aussi, didn't get ubuflu so far (although overcooled rooms are eeeverywhere :/), and jetlag wasn't too bad
[12:30] <seb128> pitti, you seem up very early ... but I guess that's usual for you
[12:30] <seb128> pitti, are people at the sprint starting to get ubuflu? be careful, it often hits at the end of the week
[12:31] <sil2100> Mirv: *sigh* ok, let's do it like that, I usually tend to workaround this not to introduce noise into the repo (i.e. just changing the packages list in the jenkins job temporarily) as this will be gone once mir is released
[12:31] <seb128> pitti, is the sprint productive? do you guys do hacking or more discussions?
[12:31] <sil2100> Mirv: but I guess now it makes sense
[12:31] <Mirv>  sil2100 temporary is fine for me as well, ie just deploying
[12:31] <pitti> seb128: I looked into IRC around 7, but now it's 8:30, we just arrived at the office
[12:31] <pitti> seb128: there's two buses, so not that much choice
[12:31] <sil2100> Mirv: especially that we're not releasing stuff, so better have it in the branch
[12:31] <seb128> k
[12:34] <pitti> seb128: we actually do have quite some discussions, but we get to do hacking in the afternoons
[12:34] <seb128> pitti, k, shame that we don't a joined sprint, I miss you guys!
[12:35] <desrt> brrrraaaaiiinnnsssss
[12:35] <pitti> seb128: likewise! didrocks and jibel are here at least, so I have at least some of my favourite French here :)
[12:35] <seb128> ;-)
[12:35] <Mirv> sil2100: there's some random stuff going on, once again. http://10.97.0.1:8080/job/autopilot-saucy-daily_release/label=qa-nvidia-gtx660/1738/console doesn't seem like progressing.
[12:36] <Mirv> I'm going to just abort that
[12:38] <sil2100> Thanks
[12:39] <sil2100> hm, too bad it's from platform, that's a base package that I'd like released with anything else
[12:40] <sil2100> Mirv: nvidia seems awfully strange today
[12:40] <sil2100> Mirv: not moving really on the mirslave job...
[12:44] <sil2100> Mirv: I think we'll have to reset the nvidia machine
[12:44] <Mirv> sil2100: argh
[12:44] <sil2100> Mirv: http://10.97.0.1:8080/job/autopilot-saucy-daily_release/1739/label=qa-nvidia-gtx660/console <- it's not moving, and when I ssh to the nvidia machine and try to do lxc-ls --fancy, it's just hanging
[12:44] <sil2100> b0rken :<
[12:44] <Mirv> that's b0rken indeed
[12:44] <Mirv> bah
[12:45] <sil2100> Should I sudo reboot it?
[12:45] <Mirv> sil2100: will you powerswitch or will I?
[12:45] <Mirv> sil2100: yes, by all means
[12:45] <Mirv> of course that's softer way :)
[12:45] <sil2100> Mirv: I'll try by ssh, if it doesn't work we'll powerswitch it ;p
[12:46] <sil2100> heh, ok, reboot doesn't seem to work ;p
[12:46] <Mirv> seb128: at least some good news anyway. as I predicted indicators would be now happy to publish itself if we'd just allow it.
[12:47] <seb128> Mirv, \o/
[12:47] <seb128> just need to get asac to +1 that then
[12:47] <Mirv> yep
[12:49] <sil2100> Mirv: I powerswitched it
[12:50] <sil2100> Reboot just made things worse ;p
[12:50] <qengho> seb128: Cr updates in  chinstrap:~cmiller/packages/ , if you care to sponsor.
[12:51] <seb128> qengho, thanks, I can do that ;-)
[12:51] <qengho> seb128: merci bien.
[12:51] <seb128> de rien ;-)
[12:52] <seb128> didrocks, oh a didrocks, can we get the hud and indicators published today? there are important fixes for touch and desktop in there
[12:52] <sil2100> didrocks: morning! Less jet-lagged now? ;)
[12:52] <didrocks> sil2100: seb128: hey! well. First asac wants a touch image with unity8 + mir running
[12:53] <Mirv> sil2100: oh..
[12:53] <didrocks> so gating on the tests to turn green before releasing the rest of locks
[12:53] <kenvandine> Laney, seb128: should setting timezone with the datetime plugin in system-settings work?
[12:53] <didrocks> sil2100: no jetlag, but slept 4 hours because of the above (finished at 1am yesterday) ^
[12:53] <seb128> kenvandine, hey, on desktop yes
[12:53] <sil2100> didrocks: I noticed there was a publish of unity8 last night, was that ACKed by you and done by Ken?
[12:53] <seb128> kenvandine, touch still has the logind issue
[12:53] <kenvandine> seb128, ah, ok
[12:54] <didrocks> seb128: acked and done by me
[12:54] <didrocks> asac was next to me to testify
[12:54] <seb128> sil2100, ^
[12:54] <Mirv> sil2100: so does the nvidia machine look like kaboom now?
[12:54] <sil2100> ACK
[12:54] <didrocks> we had beers and pizzas
[12:54] <didrocks> and worked :p
[12:54] <didrocks> (I guess that was the deal)
[12:54] <sil2100> Mirv: it looks better, at least lxc-ls doesn't die ;)
[12:54] <Mirv> sil2100: hmmkay
[12:54] <sil2100> Mirv: is it visible on jenkins?
[12:55] <pitti> seb128: darn, https://translations.launchpad.net/ubuntu/saucy/+language-packs didn't get a new delta tarball for a week, so no new langpacks today :/
[12:55] <pitti> seb128: but it did copy ubuntuone-client into the local source packages now
[12:55] <pitti> so the next actual export will have it
[12:55] <Mirv> sil2100: not sure yet, but guess what intel seems stuck http://10.97.0.1:8080/job/autopilot-saucy-daily_release/label=autopilot-intel/1739/console
[12:56] <seb128> pitti, so next update should have it? do you know why previous one didn't?
[12:56] <sil2100> Come oon...
[12:56] <pitti> seb128: yes, it was considered to be KDEish
[12:56] <sil2100> Mirv: the machine seems responsive, checking the container
[12:56] <Mirv> sil2100: didrocks: just as one more data point there was some apparently daily otto autopilot job, which stuck at "starting lxc" or such on both intel and nvidia machine and didn't continue from there
[12:57] <Mirv> around 09:45 UTC
[12:57] <seb128> pitti, oh ok, good if it's fixed in the next update then ... do you know what's the issue with the "no tarball for a week"?
[12:57] <pitti> no, I don't
[12:57] <pitti> I just noticed myself
[12:57] <didrocks> Mirv: interesting, let jibel knows when connected, he said he will look at those kinds of issues today
[12:57] <sil2100> Mirv: the container seems responsive, not sure on what process it's hanged, let me try moving that
[13:00] <Mirv> sil2100: can you let jibel know about http://10.97.0.1:8080/job/autopilot-saucy-setup_otto/label=autopilot-intel/116/console when he arrives?
[13:00] <Mirv> so it just stuck there, and same for nvidia
[13:00] <Mirv> until aborted
[13:00] <Mirv> the logs stated that yesterday at the same time it worked fine
[13:01] <sil2100> Mirv: ok, will do
[13:01] <Mirv> sil2100: now nvidia seems offline..
[13:01] <sil2100> Mirv: ah, you aborted the intel job? I was in the container when you did that ;
[13:02] <sil2100> ;p
[13:02] <sil2100> And it was like 'huh, what happened?!'
[13:02] <sil2100> Mirv: ok, so the jenkins slave didn't start again probably...
[13:02] <Mirv> sil2100: haha, right....
[13:02] <Mirv> sil2100: yes, I just started the slave again
[13:02] <Mirv> sil2100: jibel is probably already aware that it doesn't automatically seem to start?
[13:03] <sil2100> Mirv: yes, I'll re-inform him since I though he mentioned having a workaround
[13:03] <Mirv> sil2100: ok, I'll let you have the full control so that I won't come to your turf, the queue and hangs just look so sad :)
[13:04] <sil2100> Mirv: I always appreciate help ;) Especially when I'm doing something else as well
[13:05] <sil2100> Mirv: but I opt for even missing the next tick just to get the stacks into shape - what do you think?
[13:05] <sil2100> I wonder what's happening with the test machines recently, since in the past we never had so many issues like these
[13:06] <Mirv> sil2100: well, depending on how it goes. if it's just unity 55mins from now, it might be easier to abort its job and allow normal "restart all"
[13:06] <Mirv> sil2100: but on the other hand hand-guiding this tick to an actual end would be nice as well
[13:06] <seb128> sil2100, they send didrocks and jibel in the US to drink beers and eat pizzas, that's where it all started going down ;-)à
[13:07] <sil2100> ...;D
[13:13] <sil2100> Mirv: ok, now the machines seem to work correctly (so far)
[13:15] <sil2100> didrocks: could you do a final review of https://code.launchpad.net/~canonical-desktop-team/cupstream2distro-config/new_saucy_series/+merge/184641 ? Francis already ACKed it - if it's ok, I'll maybe top-approve once we get something released from the current arch
[13:15] <Mirv> seb128: sure..
[13:15] <sil2100> didrocks: and move on with redeploying and filling RT's
[13:15] <Mirv> sil2100: sure.. (meant for you)
[13:16] <Mirv> but well I agree also with seb's analysis of the situation
[13:16] <seb128> (I was wondering/reading backlog for context :p)
[13:16] <sil2100> ;)
[13:32] <sil2100> Mirv: intel again hanged up...
[13:32] <sil2100> jibel, didrocks: we have a problem with the intel machine it seems
[13:33] <sil2100> jibel, didrocks: it's the second time this happens - otto hangs after hook 10-autopilot and doesn't move a muscle
[13:33] <sil2100> jibel, didrocks: last time, I couldn't even reboot the machine by SSH, had to powerswitch it
[13:33] <sil2100> jibel, didrocks: http://10.97.0.1:8080/job/autopilot-saucy-daily_release/1743/label=autopilot-intel/console
[13:34] <sil2100> Mirv, didrocks, jibel: daily-release is pointless in this state, as it implies someone from the maintainance team to look at every test job every 5 minutes and abort
[13:34] <jibel> sil2100, given the place it stopped it'd means the session fails to start
[13:35] <jibel> sil2100, did you look at any error message from lightdm or X or kernel?
[13:35] <sil2100> I'll try attaching to the container, as it's still running
[13:37] <sil2100> jibel: kernel seems fine, at least nothing obvious - you would know better, but checking other logs
[13:38] <jibel> sil2100, check lightdm logs
[13:38] <sil2100> Ok, I see a crash in X
[13:39] <jibel> sil2100, it doesn't look good
[13:39] <jibel> [+2.22s] DEBUG: Launching process 3699: /usr/bin/X -core :0 -auth /var/run/lightdm/root/:0 -mir 0 -mirSocket /tmp/mir_socket -nolisten tcp
[13:39] <jibel> [+2.22s] DEBUG: DisplayServer x-0: Waiting for ready signal from X server :0
[13:39] <jibel> [+2.56s] DEBUG: Process 3699 terminated with signal 6
[13:39] <sil2100> jibel: ok... the last stack that ran before this was unity8 I think ;/
[13:39] <mterry> seb128, didrocks, pitti:  you guys are members of the lightdm dev team I see...  Do you ever review branches for landing?
[13:40] <pitti> mterry: not really, I'm not involved in day-to-day development; Robert added me when I added some apparmor/guest session fixes
[13:41] <pitti> I can certainly review/merge some easy fixes when someone asks me to
[13:41] <pitti> but I don't feel qualified to review bigger changes (design, behaviour, etc.)
[13:42] <sil2100> jibel: I guess we'll have to terminate this run, right? But I wonder why mirslave AGAIN causes problems, this time on intel
[13:42] <sil2100> jibel: should I inform upstream about it? You think it's a real mir problem?
[13:43] <mterry> pitti, well, this might be too nuanced, but it's just a bug fix, not a feature: https://code.launchpad.net/~mterry/lightdm/keep-vt-around/+merge/184887
[13:45] <seb128> mterry, not often, I don't know the codebase enough to be comfortable reviewing most of the changes ... I can have a look to something easy/that doesn't need to know in detail how lightdm works though
[13:45] <pitti> mterry: (will look in a bit, in meeting here)
[13:45] <jibel> sil2100, there has been an upload of intel driver on the 9th and mir yesterday, file a bug, ping the mir guys and they'll have to handle it from here, didrocks ^^ what do you think?
[13:45] <mterry> seb128, just trying to land that bugfix branch ^
[13:45] <pitti> mterry: in fact, perhaps I'm sitting on your old chair :)
[13:46] <mterry> pitti, you're in lex now?
[13:46] <jibel> sil2100, it is not a problem with the test system anyway
[13:46] <pitti> mterry: yes, QA team sprint
[13:46] <pitti> mterry: my first time in Lex
[13:46] <mterry> pitti, awesome  :)  I was in on Monday, didn't notice ya
[13:46] <pitti> ah, too bad
[13:46] <sil2100> jibel: thanks! After checkign that with you, filling out the bug
[13:51] <Laney> where can I get a test click package from?
[13:51] <Laney> I just want one to install on my desktop for this s-s stuff
[13:54] <seb128> Laney, http://people.canonical.com/~ubuntu-archive/click_packages/
[13:54] <seb128> Laney, install them with "sudo click install --force-missing-framework --user=Laney ...click"
[13:56] <Laney> ok, ta
[13:58] <Laney> cool, seemed to work
[13:58] <seb128> Laney, great ;-)
[13:59] <seb128> Laney, some of the infos are going to be missing from some clicks btw, that's normal
[13:59] <seb128> Laney, installed-size is only available for clicks built with > 0.4.something
[13:59] <Laney> I noticed that
[13:59] <seb128> some didn't get rebuilt since
[13:59] <Laney> what are you doing then?
[13:59] <seb128> the icon is a new field also, they don't all provide it
[14:00] <seb128> Laney, atm I display a N/A for the size when it's missing, and the icon has a fallback
[14:00] <Laney> sounds fair
[14:00] <seb128> Laney, but the size isn't going to be missing over time, we have only a few old packages leftover, any new package isn't going to have that issue
[14:01]  * Laney runs this for the first time ...
[14:11] <Laney> yay
[14:11] <seb128> Laney, working?
[14:12] <Laney> gets the data
[14:12] <Laney> no sorting yet
[14:13] <jbicha> seb128: what do you think of bug 1092719?
[14:13] <ubot2`> Launchpad bug 1092719 in gnome-disk-utility (Ubuntu) "FFe: Update gnome-disk-utility to 3.8" [Wishlist,Confirmed] https://launchpad.net/bugs/1092719
[14:13] <seb128> jbicha, that you should stop being new versions addict ;-)
[14:14] <seb128> jbicha, how did you resolve the libdvdread depends?
[14:16] <jbicha> I've got a big patch to revert the dependency/feature because I didn't want to be blocked by the mir
[14:16] <seb128> "big patch" :/
[14:17] <jbicha> yeah :( it'll be fine for 3.8 but it'll probably be a headache for any newer version
[14:17] <seb128> jbicha, well, in any case I've no objection to the update, under the condition that whoever does the update deals with issues/fallouts
[14:17] <pitti> mterry: what is the use_vt_switching flag?
[14:18] <mterry> pitti, that's when we can't start the compositor, we fall back to using VTs
[14:18] <mterry> pitti, (if we are using the compositor, everything happens on the same VT)
[14:18] <pitti> mterry: ah, so true -> lightdm running on system mir, false -> old way?
[14:19] <mterry> pitti, yeah.  And my branch tries to add a fallback for the old way, when we don't have mir yet and don't have VTs either
[14:19] <mterry> pitti, by just faking it on VT 1, where we are stuck because we can't switch VTs
[14:20] <pitti> mterry: so in that case when we don't have mir yet, wouldn't use_vt_switching be false?
[14:20] <mterry> pitti, (my understanding is that XDG_VTNR is an override to logind's normal VT detection, so we force it to assume a VT.  That's what we do in the Mir case, and what I want to do in this fallback case
[14:20] <pitti> mterry: so your fallback code wouldn't even run?
[14:20] <pitti>  if (!SEAT_UNITY (seat)->priv->use_vt_switching)
[14:20] <pitti> 18+ vt = SEAT_UNITY (seat)->priv->vt;
[14:20] <mterry> pitti, if (have_mir) use_vt_switching = false
[14:20] <pitti> so without mir (old way) this would run?
[14:21] <mterry> pitti, with Mir, we don't need VT switching.  Everything happens on same VT
[14:21] <mterry> pitti, without Mir (old way), we fallback to switching between VTs, as if it were the 2000s
[14:21] <pitti> right
[14:22] <pitti> mterry: ah sorry, I was wrong above
[14:22] <pitti> it's true -> old way, false -> mir
[14:22] <pitti> right?
[14:23] <ochosi> sorry to interfer, but would VT switching also not be needed with XMir?
[14:24] <pitti> ochosi: (why sorry? :) )
[14:24] <mterry> pitti, so without Mir, we set use_vt_switching to true
[14:24] <mterry> But sometimes (like on phone), we don't have Mir, and our VT subsystem doesn't work.  So we're stuck on VT1
[14:25] <mterry> pitti, right
[14:25] <pitti> mterry: right, so I got it the wrong way around above; it makes much more sensenow
[14:25] <ochosi> pitti: heh, because i'm not really technically on top of Mir etc so it could be a really silly question (and you seemed to talk about something important)
[14:25] <mterry> ochosi, I believe in that case, the system compositor is still running in one VT, and XMir sessions just talk to it
[14:26] <pitti> mterry: approved, merging now
[14:26] <mterry> pitti, awesome, thanks!  :)
[14:26] <pitti> mterry: ah no, it gets auto-merged I assume
[14:26] <mterry> pitti, yeah, but not auto-released...  :(
[14:27] <ochosi> mterry: so when switching to the greeter (which would usually spawn a new VT), would there still be the blackout and flickering with XMir?
[14:27] <mterry> ochosi, I believe the idea is "no"
[14:28] <ochosi> mterry: that sounds like a nice feature. so no-one has tested this yet?
[14:29] <mterry> ochosi, I'm not sure.  I've been so phone focused these days, I don't know where we are with the desktop and XMir
[14:29] <ochosi> mterry: okies, thanks though!
[14:45] <didrocks> mterry: we need it for deploying the branches
[14:46] <didrocks> seb128: I'll look at it in the incoming hours
[14:47] <seb128> didrocks, that's re what? sorry so much going on during the day, I forgot what that specific ping was aobut
[14:48] <didrocks> jibel: sil2100: ack with pinging Mir team
[14:48] <sil2100> didrocks: they're ping, aware and hopefully will fix this soon, for now I skipped mirslave so that we're not blocked on a broken intel machine
[14:49] <didrocks> seb128: that's re: failing s<tab>
[14:49] <didrocks> sil2100: I'll look at it in the incoming hours
[14:49] <didrocks> it being your branch
[14:49] <seb128> didrocks, I see :p
[14:49] <sil2100> didrocks: thank you, no rush, I think top-priority for now is to get things released
[14:49] <didrocks> seb128: I know you pinged me, will be your turn soon :p
[14:50] <seb128> didrocks, btw I need you input on why it would be hard to list click updates in the system update panel ... it feels like it's just another list widget/model/delegate if they have a working backend
[14:50] <seb128> didrocks, right
[14:50] <sil2100> Poor seb128 is pinged in my stead so many many times ;p
[14:52] <didrocks> seb128: because the design UI totally changed?
[14:52] <didrocks> and we need to have one daemon to talk to I guess
[14:52] <didrocks> and rick told that we need to "finish what we have"
[14:52] <didrocks> and they already have a separate app for that
[14:52] <didrocks> so let's have V1 doing that
[14:53] <didrocks> design changed late
[14:53] <seb128> didrocks, ok, we just don't have a design for the solution you guys suggest :/
[14:53] <seb128> didrocks, I guess it's up to design to update back the design then
[14:54] <didrocks> seb128: yeah, and we can say, for us, too late, let's focus on make V1 rock solid first
[14:54] <didrocks> (and use the apps already written by the team for click packages)
[14:55] <seb128> didrocks, sure, we don't have a design anymore for our current UI though, since the wiki got updated
[14:55] <seb128> didrocks, so it's a bit flacky
[14:55] <didrocks> seb128: we can go back in history, it's versionned
[14:55] <seb128> didrocks, and we don't have guidance for handling of the error/some of the cases
[14:55] <seb128> didrocks, right, but we were lacking details by then
[14:55] <seb128> oh, well
[14:55] <didrocks> yeah, on the error handling
[14:55] <didrocks> anyway, I won't have time to implement the new design, and I asked the management about it and they agree to finish what we have
[14:56] <seb128> didrocks, ok, btw I already modified some of the UI bits while you were on holidays
[14:56] <didrocks> seb128: ah great! Sure, feel free
[14:56] <seb128> didrocks, but it's minor, moving the never/on wifi/always selector to a new screen
[14:56] <didrocks> there is this qdbus stuff with the array of dict
[14:57] <didrocks> which worries me
[14:57] <seb128> didrocks, which was part of the design changes (ported it to the new optionselector as well)
[14:57] <didrocks> but I'll have a look at it next week
[14:57] <seb128> k
[14:57] <didrocks> seb128: perfect, thanks a lot!
[14:57] <seb128> yw
[15:09] <didrocks> sil2100: +  dest: ubuntu-unity/next-next
[15:09] <kenvandine> didrocks, can i publish services?  we really need content-hub published
[15:09] <sil2100> didrocks: oh, ok ;p next-next it will be...;p
[15:10] <didrocks> -      target_branch: lp:autopilot/1.3
[15:10] <didrocks> 347+      target_branch: lp:autopilot
[15:10] <didrocks> -> not needed
[15:10] <didrocks> just remove target_branch
[15:10] <didrocks> to target trunk
[15:10] <didrocks> kenvandine: not as long as I didn't talk to alexander
[15:10] <sil2100> Right, slipped through, fixing too! Thanks
[15:10] <didrocks> kenvandine: we need to publish an image
[15:10] <didrocks> -      target_branch: lp:autopilot-gtk/1.3
[15:10] <didrocks> 363+      target_branch: lp:autopilot-gtk
[15:10] <didrocks> sil2100: same ^
[15:11] <didrocks> -      target_branch: lp:autopilot-qa/1.3
[15:11] <didrocks> 375+      target_branch: lp:autopilot-qa
[15:11] <didrocks> same ^
[15:11] <sil2100> didrocks: indeed, all those I just removed the 1.3 it seems
[15:11] <sil2100> Unnecessarily
[15:11] <sil2100> kenvandine: let's wait for this tick to finish, maybe the stacks will be in much better state
[15:11] <sil2100> kenvandine: and then we talk to asac about publishing smaller stacks
[15:12] <kenvandine> sil2100, ok, the only package that'll publish in services is content-hub
[15:13] <didrocks> sil2100: shouldn't we remove    manualpublish: True # XXX: as requested by asac, we're in manual mode!
[15:13] <kenvandine> which is being added to the seed
[15:13] <didrocks> on all head's?
[15:13] <sil2100> kenvandine: ACK, let's have a chat with asac then
[15:14] <didrocks> kenvandine: don't change anything on the touch image before we are sure we are in a good state
[15:14] <kenvandine> didrocks, understood
[15:14] <didrocks> let me gather the state in ~50 minutes
[15:14] <sil2100> didrocks: understood as well, but I agree that new content-hub is needed, since otherwise settings background-changing is b0rken ;)
[15:14] <kenvandine> yup
[15:14] <didrocks> sil2100: kenvandine: when did that change?
[15:14] <kenvandine> it's a little broken right now :)
[15:15] <didrocks> the previous settings is already broken?
[15:15] <kenvandine> kind of
[15:15] <kenvandine> missing depends on content-hub
[15:15] <kenvandine> gallery-app and uss depend on the lib
[15:15] <didrocks> hum…
[15:15] <kenvandine> which doesn't depend on the service
[15:15] <didrocks> ah, so the red on the dashboard is because of this?
[15:16] <kenvandine> not sure actually... maybe
[15:16] <didrocks> for gallery-app?
[15:16] <didrocks> can you check please?
[15:16] <kenvandine> yeah
[15:16] <didrocks> keep me posted
[15:17] <kenvandine> didrocks, actually, no
[15:17] <kenvandine> it wouldn't cause a failure in gallery-app
[15:17] <didrocks> so let's get the baseline green
[15:18] <didrocks> and then, move
[15:18] <kenvandine> but if there were tests in settings for background, then it would fail
[15:18] <kenvandine> yeah
[15:18] <didrocks> it's difficult enough already
[15:18] <kenvandine> please ping me :)
[15:18] <didrocks> kenvandine: will surely do
[15:18] <kenvandine> thx
[15:18] <didrocks> I need to get my hand on the German first
[15:18]  * didrocks will look near the fridge, beers are here, we should find him :)
[15:19] <kenvandine> asac, fyi we need to add content-hub to the touch seed, i have that ubuntu-touch-meta ready to upload... but i'll wait until you have images :)
[15:19] <sil2100> ;D
[15:20] <sil2100> didrocks: fixed those issues that you pointed out, I'll create the next-next PPA now
[15:21] <didrocks> kenvandine: yeah, don't upload it
[15:21] <didrocks> let's get green first
[15:21] <didrocks> sil2100: create the next-next?
[15:21] <kenvandine> don't worry, i won't :)
[15:21] <didrocks> sil2100: wait, what's this?
[15:21] <sil2100> didrocks: ...scratch that, don't look at that branch
[15:22] <sil2100> didrocks: wait, going for some coffee and then repushing the branch ;p
[15:23] <didrocks> k
[15:24] <sil2100> didrocks: anyway, now it should be good
[15:24]  * didrocks refreshessssss
[15:27] <didrocks> sil2100: approved
[15:27] <didrocks> I'll let you redeploy once ready :)
[15:28] <sil2100> ACK, thanks!
[15:42] <sil2100> jibel: oh my god, again the DNS problem on the otto machines :P!
[16:02] <tkamppeter> larsu, hi
[16:05] <larsu> tkamppeter: hi
[16:07] <asac> kenvandine: yeah. we want to land indicators and the unity8 fix now
[16:09] <Sweetshark> OMG another heroic effort finished at libreoffice: runnable instdir -- this build LibreOffice in a work directory, out of which it can then directly run without additional copying foo ...
[16:10] <didrocks> sil2100: around at all?
[16:10] <tkamppeter> larsu, we have the conference call
[16:11] <sil2100> didrocks: yes
[16:11] <didrocks> sil2100: hangout ready?
[16:11] <sil2100> didrocks: coding something
[16:11] <sil2100> What hangout?!
[16:11] <sil2100> :O
[16:11] <didrocks> need to talk to you for 10 minutes
[16:11] <didrocks> right NOW
[16:11] <sil2100> : O
[16:11] <sil2100> Ok, ready if anything, I guess
[16:12] <didrocks> https://plus.google.com/hangouts/_/633f1bb81a28926867d218765030050bc23a5be9?hl=fr
[16:15] <larsu> tkamppeter: please do it without me today, I don't have anything printing-related to report. I'll look at the notes later
[16:40] <attente> seb128, is it better to have the maliit schema in gsettings-ubuntu-touch-schemas or in ubuntu-keyboard?
[16:41] <qengho> seb128: I haven't seen anything about Cr package acceptance. Should I be worried?
[16:45] <Laney> GOD
[16:45] <Laney> QT :|
[17:06] <Laney> attente: I'd say in the keyboard itself
[17:06]  * Laney leaves, irritated at qt
[17:06] <attente> Laney, yeah, that made the most sense to me initially
[17:06] <Laney> maybe I'll have an evening brainwave
[17:06] <attente> :)
[17:06] <Laney> see you
[17:28] <seb128> qengho, sorry, pings didn't stop and I forgot about it, uploaded now
[17:29] <qengho> seb128: my french obviously dazzled you, n'est pas?
[17:29] <seb128> qengho, on dirait que oui ;-)
[17:30] <attente> seb128, do you have time to help me with a build issue?
[17:42] <seb128> attente, sure
[17:44] <attente> seb128, when building http://bazaar.launchpad.net/~phablet-team/ubuntu-keyboard/trunk/, i get dpkg-source: unrepresentable changes to source
[17:46] <seb128> attente, update the version number in debian/changelog
[17:46] <seb128> attente, it tries to use the tarball from the archive for that version and add the changes in a diff on top
[17:46] <seb128> attente, and you probably have a binary file or something that can't be diffed
[17:46] <seb128> attente, if you bump the changelog it's going to create a new tarball rather than reusing the archive one, that should work
[17:47] <seb128> attente, version = the part before "-0ubuntu1"
[17:47] <attente> seb128, thanks, i'll give it a try
[17:47] <seb128> attente, yw
[17:48] <qengho> seb128: Can we revert the chromium back to 28 and take a few days to test 29 more?
[17:48] <attente> seb128, thanks, that fixed it completely
[17:48] <seb128> attente, great
[17:49] <seb128> qengho, we could, what's the issue with 29?
[17:50] <seb128> qengho, are the user profiles compatible (e.g can you run 28 again after running 29, or is 29 writing configs that 28 can't understand?)
[17:52] <qengho> seb128: I haven't had any trouble going back to 28, but I have no formal knowledge about no change.
[17:52] <seb128> qengho, what's the rational for going back?
[17:53] <qengho> seb128: #webapps is scared of it and wants to test thoroughly. One bug means there could be other bugs.
[17:54] <seb128> qengho, that doesn't seem a strong rational for a revert, that needs better coordination next time/them keeping more on top of the beta channel
[17:55] <qengho> seb128: reverting the index of released wouldn't help people who have aready installed anyway, right?
[17:55] <seb128> qengho, you can't revert in versions, you would have to use an epoch or reupload 28 as 29.is.really.28
[17:55] <seb128> qengho, e.g fake the version to be > 29
[17:56] <qengho> seb128: right.
[17:56] <seb128> qengho, but we don't have enough proved issues to justify going through a revert, especially when we are unsure it's not going to create issues with user configs (not to mention file conflicts with l10n)
[18:16] <dbarth> seb128: quick note, we're sorry about the regression on chromium; we're re-testing the new build right now to ensure this doesn't snowball
[18:16] <seb128> dbarth, thanks
[18:19] <qengho> seb128, dbarth: Thank you for your help, too.
[18:20] <seb128> qengho, thanks for getting those fixes out!
[18:20] <seb128> qengho, that, and for considering the webapps issues as well ;-)
[18:22] <qengho> seb128: Next chromium will have UI autopkgtests covering everything we saw today!  I'm excited.
[18:22] <seb128> \o/
[19:50] <didrocks> pitti: around? mind bumping some stuff?
[19:50] <pitti> didrocks: bring'em on
[19:50] <didrocks> https://launchpad.net/~ubuntu-unity/+archive/daily-build-next/+build/4956393
[19:50] <didrocks> https://launchpad.net/~ubuntu-unity/+archive/daily-build-next/+build/4956391
[19:50] <pitti> didrocks: fait
[19:50] <didrocks> https://launchpad.net/~ubuntu-unity/+archive/daily-build-next/+build/4956399
[19:51] <didrocks> https://launchpad.net/~ubuntu-unity/+archive/daily-build-next/+build/4956397
[19:51] <didrocks> pitti: et ce sera tout ;)
[19:51] <didrocks> merci!
[19:51] <pitti> didrocks: de rien
[19:54] <didrocks> pitti: it's back to 10 minutes? https://launchpad.net/~ubuntu-unity/+archive/daily-build-next/+build/4956397
[19:54] <didrocks> did you bump for the last 2 the priority?
[19:55] <pitti> didrocks: oh, sorry
[19:56] <pitti> didrocks: done all 4 now
[19:56] <didrocks> pitti: merci beaucoup
[20:09] <qengho> fg
[20:13] <qengho> Bah!