[03:07] <robert_ancell> charles, how do you do SRUs for the indicators?
[03:07] <robert_ancell> just chuck stuff in debian/patches or make a new release?
[03:12] <pitti> Good morning
[06:25] <willcooke> morning folks
[06:25] <didrocks> hey willcooke!
[06:25] <didrocks> ready for day #2? ;)
[06:25] <willcooke> hehe
[06:25] <willcooke> kinda
[06:26] <willcooke> I'm off in to London in a little while, so I wanted to get the ball rolling before I sit on the train
[06:26] <willcooke> actually, I have a question for you didrocks
[06:26] <didrocks> sure
[06:26] <willcooke> I'm trying to work out who is in our team (pretty fundamental, right)
[06:26] <willcooke> so let me send you a link
[06:26] <didrocks> well, it's a good start :)
[06:30] <willcooke> hey seb128, can you make me an admin on https://launchpad.net/~canonical-desktop-team
[06:31] <seb128> good morning desktopers
[06:31] <seb128> willcooke, sure, sorry I didn't respond because I'm not fully in work mode yet, but can do that ;-)
[06:32] <willcooke> no hurry seb128
[06:32] <willcooke> I'm not either - no coffee
[07:33] <TheMuso> Hey willcooke.
[07:34] <willcooke> howdy TheMuso - good to meet you :)
[07:34] <TheMuso> You too.
[08:01] <willcooke> right - off to London.  Be back online in about an hour (depending on the trains)
[08:02] <Laney> yo
[08:05] <seb128> hey Laney, how are you?
[08:08] <Laney> hey seb128, doing good thank you
[08:09] <Laney> just sat around last night and napped/watched some tv, didn't end up going climbing ;-)
[08:09] <Laney> pent up energy, raaargh
[08:09] <Laney> you?
[08:10] <czajkowski> aloha
[08:13] <Laney> hey czajkowski
[08:13] <Laney> wie gehts?
[08:14] <czajkowski> not just yet :) 3 hrs to flight :) time to print of name badges and check in yet
[08:15] <Laney> it's a glamorous life you've got there
[08:15] <seb128> Laney, I'm fine thanks, not fully awake yet ;-)
[08:15] <didrocks> morning Laney, czajkowski
[08:15] <seb128> czajkowski, hey, unity working today? ;-)
[08:15] <Laney> seb128: still keeping up this early morning IRCing though :P
[08:16] <seb128> Laney, ye
[08:16] <didrocks> Laney: see, going in Lyon can change a man! :)
[08:16] <seb128> Laney, yeah, there is no budging there!
[08:16] <seb128> lol
[08:16] <seb128> well, let's see and wait how it goes in winter ;-)
[08:16] <czajkowski> seb128: eh no :( but I now have all the commands to restart various things so I can get back onto my main account and not live on guest
[08:17] <czajkowski> thanks for asking :)
[08:17] <seb128> but it's actually alright for summer
[08:17] <didrocks> seb128: same, but with hot wine :p
[08:17] <seb128> czajkowski, :-(
[08:17] <seb128> didrocks, lol
[08:17] <seb128> didrocks, then I'm the one with the drinking problem, right?
[08:17] <didrocks> you obviously are :)
[08:19] <seb128> tsss
[08:35]  * didrocks retries to build a desktop docker container
[08:35] <didrocks> first automated trial was a fail :)
[08:40] <seb128> didrocks, enjoying docker then? :-)
[08:44] <didrocks> seb128: yeah, it's quite nice :)
[08:44] <didrocks> just needs to find a way to install ubuntu-desktop without any priviledge
[08:45] <didrocks> ensuring that I create a passwordless sudo user and so on…
[08:45] <didrocks> (to have that container running what we need)
[08:45] <didrocks> and ensuring that coverage works as expected, even within the container
[08:59] <didrocks> willcooke: come on, The IT Crowd reference on day 2! You set the bar high :)
[09:01] <willcooke> didrocks, I'm going to Gimp up an A team picture with your faces on it later and put it on my desk.
[09:03] <didrocks> :)
[09:03] <willcooke> nearly in to London now - on the train atm.  4G is working quite well.  I get 20 Mb down, which is more than I get on ADSL at home
[09:03] <willcooke> :)
[09:03] <willcooke> shutting down - bbiab
[09:49]  * didrocks goes for exercising
[09:49] <didrocks> seems like no rain this time :)
[09:50] <seb128> didrocks, enjoy!
[10:08] <willcooke> seb128, do you have a calendar entry for the weekly meeting you could invite me to?  If not I'll create one and send it round
[10:09] <Laney> willcooke: It's on the Ubuntu fridge calendar
[10:09]  * Laney laughs at the optimistic Agenda link there
[10:10] <seb128> willcooke, there is one in the UE calendar owned by Michelle as well
[10:10] <seb128> which I copied in my calendar, personally
[10:10] <pitti> hey willcooke, welcome back!
[10:10] <seb128> but if you prefer it handled some other way please do
[10:10] <pitti> so that's the man who took my job!
[10:10] <seb128> lol
[10:10] <Laney> haha
[10:11] <pitti> willcooke: in case that's confusing to you, ask any desktop team member over a beer :)
[10:11] <willcooke|meetin> :)
[10:11] <Laney> pitti for VP of Ubuntu Engineering!
[10:12] <somedude> Laney: pitti who?
[10:13] <seb128> Laney, forget about that, let's just appoint some dude
[10:13]  * Laney looks at a photo and sees pitti in the middle of fading out
[10:26] <davmor2> seb128: some dude isn't he like that pitti chap a French guy who thinks he's German?
[10:27] <pitti> davmor2: mec, tu dois parler français ici !
[10:28] <davmor2> pitti: does that make you the anti seb128 ?
[10:28] <pitti> davmor2: koennte sein :)
[11:09] <pitti> desrt: hey Ryan, how are you?
[11:09] <desrt> pitti: hi!  pretty good
[11:10] <desrt> brain recovering nicely after a week of drowning in another language
[11:10] <pitti> desrt: do you see any reason to not commit the cgmanager bits to systemd-shim trunk, and making a new release? we're shipping that now in Ubuntu, and would like to ship it in Debian too
[11:10] <pitti> desrt: Esperanto? :-)
[11:10] <desrt> yup
[11:10] <desrt> just went to a week-long event.... no english spoken there....
[11:10] <pitti> desrt: très cool !
[11:10] <desrt> so ya
[11:10] <desrt> we can merge that stuff now
[11:11] <desrt> i actually told hallyn that i'd be OK if you pushed it (since you have commit access)
[11:11] <pitti> desrt: it's not perfect yet (old sessions don't get cleaned up sometimes), but it's workign well enough
[11:11] <desrt> ya... the stop thing is hard
[11:11] <pitti> desrt: ah ok, that got lost in the Chinese whispers then
[11:11] <desrt> because you stop the session unit, and we don't know the cgroup path (ie: under which user)
[11:11] <desrt> so we can't properly kill it
[11:18]  * Sweetsha1k smirks rolling through the backlog.
[12:18] <darkxst> didrocks, ping
[12:18] <didrocks> darkxst: please don't use contextless ping, just ask ;)
[12:20] <didrocks> (especially if you are not around to ask the next question)
[12:20] <darkxst> didrocks, so have been chatting with tracker upstream, unit tests are 100% guaranteed to pass (they won't do a release with these broken)
[12:20] <didrocks> darkxst: ok, so we can run them in our infra?
[12:20] <darkxst> functional tests are a bit iffy, at best its like 90% that will pass
[12:21] <didrocks> do we know which ones are flaky? can they be filtered out?
[12:21] <darkxst> didrocks, I already hooked up unit tests, but under autopkgtest since they require install tracker to run
[12:22] <didrocks> they are not really unit tests I guess then, but sounds good to me :)
[12:22] <darkxst> didrocks, I know which ones are flaky right now, but seems like not properly maintained upstream
[12:22] <didrocks> darkxst: they don't plan to maintain them? not sure it's a really good sign of quality for main then
[12:23] <darkxst> didrocks, seems to be a case of too many tests
[12:24] <didrocks> darkxst: would be a good contribution to upstream as well to try to separate reliable ones to flaky ones
[12:24] <darkxst> unit tests are maintained, functional tests can lag a bit
[12:24] <didrocks> and we can hook them up in autopkgtests
[12:25] <darkxst> yeh though I don't quite get the distinction here, from my quick look through test cases seems to be alot of duplication between unit tests and functional tests
[12:26] <didrocks> darkxst: so, if they don't want to maintain them, why not proposing to remove them upstream?
[12:26] <didrocks> bad tests or unlooked tests are worse than not having tests
[12:28] <darkxst> didrocks, unmaintained is probably not the right word, but a functional test failure doesn't seem to be a release blocker
[12:29] <didrocks> darkxst: do we know how many tests are failing right now? (like the % on the total number?)
[12:29] <didrocks> we can have a threshold in that case
[12:30] <darkxst> probably 6-7 fail, 1-2 just hang and timeout
[12:31] <darkxst> not too sure how many tests there are, but probably over 100
[12:31] <didrocks> darkxst: ok, maybe in a first approach, let's just blacklist the inconsistant one
[12:31] <didrocks> at least, if there is a big breakage, we can then detect them
[12:33] <darkxst> didrocks, unit tests should catch that, in fact they already caught there first breakage on build #2 with the glib update
[12:34] <didrocks> darkxst: well, it's to protect you, then, if you are fine in having something that can be broken without detection and think the unit tests are enough, good for me if you wired them up
[12:37] <darkxst> didrocks, the unit tests, go well beyond unit testing from what I can see.
[12:37] <didrocks> darkxst: from your descriptions, yeah, I just gave a quick look and they are clealy not unit tests :p
[12:37] <didrocks> so yeah, let's ensure that's wired up and that should be enough
[12:39] <darkxst> didrocks, they are https://jenkins.qa.ubuntu.com/view/Utopic/view/AutoPkgTest/job/utopic-adt-tracker/
[12:40] <didrocks> darkxst: are they? I keep seeing: # TOTAL: 0
[12:41] <didrocks> but yeah, some logs shows them passing
[12:41] <didrocks> however, the counter doesn't work :/
[12:43] <darkxst> right, the counter on stdout is broken
[12:44]  * didrocks sighs
[12:44] <didrocks> and upstream would say it's not important as well?
[12:53] <darkxst> didrocks, if a "unit" tests fails that is important, and it should trigger a failure regardless of the counters
[12:54] <didrocks> darkxst: yeah, but it's still a sign that details don't seem to matter to upstream, which is reflecting on the global quality of the product
[12:54] <didrocks> that's not a very good sign for something we have to commit to main
[12:58] <darkxst> didrocks, it could also be fallout from switching to the newever glib.mk testing framework
[13:02] <darkxst> tracker 1.0 branch is still actively maintained, and should be for the foreseeable future, and api/abi should be pretty stable from here on in
[13:02] <didrocks> yeah, I'm more concern about other moving pieces breaking them and not being catchup
[13:03] <didrocks> and the fact that the tests are in a seemly weird tests don't give the right signal
[13:03] <didrocks> but again, as long as ubuntu desktop doesn't use it and you are happy in Ubuntu GNOME to take the charge of maintaining, I'm fine with it being in main
[13:04] <pitti> desrt: pushed to master FYI; want to cut a release?
[13:05] <pitti> desrt: or perhaps let's wait a bit until cgmanager is in Debian, perhaps we'll get some more fixes by then
[13:08] <darkxst> didrocks, tests aside, it really is way ahead of where it was a year or two ago,
[13:08] <darkxst> (stability wise)
[13:11] <didrocks> darkxst: yeah, just fix the other issues then, and I'll +1
[13:12] <desrt> pitti: i wouldn't mind getting the Stop thing working either...
[13:12] <desrt> pitti: could do it by walking the cgroup tree to find the group with the matching name....
[13:13] <pitti> desrt: I think this might not even be an issue of removing the cgroup, but just to invoke the cgroups' cleanup notification?
[13:13] <darkxst> didrocks, sorting out the COPYING.LGPL that should be in next weeks 1.0.3
[13:13] <didrocks> great :)
[13:13] <desrt> pitti: from what i understand, the entire point of this cgroup exercise is to have a reliable way to kill off a group of processes when the session exits
[13:13] <desrt> so ya.... implementing Stop is kinda _the_ point
[13:13] <pitti> desrt: if I log out of a session, the cgroup (like session-c4.scope) goes away, but it's still in loginctl as "State=closing"
[13:14] <pitti> desrt: yes, of course; but that's not even what I meant
[13:14] <desrt> hallyn wanted it for another reason to do with users being able to create containers.... so he's happy now, sure.... but in theory, i think Stop is probably pretty important
[13:14] <darkxst> shlibs.local looks all correct to me, I don't see anything obsolete in there, and ricotz says the rpath thing is a non-issue
[13:14] <desrt> hmmm
[13:21] <didrocks> darkxst: why is it a non issue? We don't accept rpath in ubuntu apart if there is some real good reasons to have it
[13:21] <darkxst> ricotz, ^?
[13:23] <ricotz> didrocks, i commented on the bug, which was not completely right
[13:24] <didrocks> ricotz: ah fine, I'll have a look once you reassign (and the rest is ready) then
[13:24] <ricotz> although there are no rpath references in the source
[13:24] <ricotz> and config.rpath is created due some outdated autotools mojo
[13:24] <ricotz> git master doesnt pick it up anymore
[13:24] <didrocks> great, so let's wait for next release :)
[13:25] <ricotz> hmm, i guess we are going with 1.0.x here
[13:25] <ricotz> git master is 1.1.x though
[13:25] <pitti> mterry: welcome back! had some nice vacations?
[13:25] <mterry> pitti, yeah I was just camping with friends and family.  relaxing  :)
[13:25] <mterry> pitti, hopefully that deja-dup upload clears the blockage
[13:26] <pitti> mterry: and thanks for the deja-dup fix
[13:26] <mterry> (thanks to Laney)
[13:26] <pitti> mterry: oh, I was actually concerned the other way around -- glib breaking deja-dup :)
[13:26] <seb128> mterry, hey ;-)
[13:26] <Laney> that glib is removed anyway
[13:26] <mterry> pitti, :) no thankfully just a silly warning message
[13:26] <pitti> I kind of like having a working backup
[13:26] <mterry> Laney, oh ok
[13:26] <seb128> mterry, I +1ed your settings changes
[13:26] <Laney> but yeah, it has a new warning which makes some tests sad
[13:26] <Laney> so still good
[13:27] <pitti> mterry: btw, I switched from rsnapshot (which I'd used for like 10 years) to duplicity a few months ago; love it!
[13:27] <mterry> seb128, awesome thanks!  Now the blocker for that whole silo is the underlying config changes to livecd-rootfs
[13:27] <mterry> pitti, oh really!  Neat
[13:27] <pitti> mterry: camping sounds great, had nice weather?
[13:27] <mterry> pitti, yeah it was actually nicely cloud-covered -- no rain, but not too much sun
[13:28] <pitti> mterry: yeah, I configured deja-dup for my wife's computer a year or so ago; not quite flexible enough for me as a UI, but the duplicity backend is great
[13:28] <mterry> pitti, yeah you aren't DD's target audience  ;)
[13:28] <pitti> mterry: (not a critique -- if the UI was so flexible it would be too hard for most users :) )
[13:29] <pitti> mterry: well, actually, the only feature I'm missing is specifying an --exclude-globbing-filelist
[13:30] <mterry> pitti, mmm yes, I believe there is a feature request bug for that that I've been ignoring for the past many years
[13:30] <pitti> mterry: yeah, no biggie; I like cron and CLI
[13:31] <pitti> mterry: but I was quite amazed how easy and fire&forget it is, on my wife's PC
[13:31] <pitti> mterry: she doesn't have quite my discipline with keeping $HOME neatly organized, and I don't want to carefully go and blacklist stuff, so DD is just great
[13:31] <mterry> :)
[14:04] <Laney> since we got half of gstreamer 1.4 already, I'm going to look at the rest
[14:04] <Laney> happy days
[14:06] <seb128> Laney, thanks
[14:12] <seb128> Laney, shrug though on the people complaining about that sync
[14:12] <Laney> yeah...
[14:13] <Laney> it's not even a transition, just a bug
[14:13] <Laney> not that anyone even investigated it yet
[14:13] <seb128> no
[14:13] <seb128> they claim they are too busy for that
[14:13] <seb128> how constructive!
[14:14] <Laney> back in the day we'd have taken all of the point releases, then we'd have found the issue sooner ;-)
[14:17] <seb128> hehe
[15:19] <mvo_> seb128: would https://launchpadlibrarian.net/180511188/gst-plugins-base1.0_1.4.0-1_1.4.0-1ubuntu1.diff.gz and https://launchpadlibrarian.net/180510137/gstreamer1.0_1.4.0-1_1.4.0-1ubuntu1.diff.gz be ok with you? I'm working toward makeing apt-get install ubuntu-sdk-libs-dev:$target work and the git stuff is not multiarch enabled yet
[15:20] <seb128> mvo_, what do you mean by git stuff there?
[15:20] <mvo_> seb128: gir stuff
[15:20] <mvo_> seb128: sorry, autotyping :)
[15:20] <seb128> oh
[15:20] <seb128> how does it work for other libs? I can't believe none of our gobject libs are multiarched
[15:20] <seb128> but having -dev depends on the gir is standard rule in Debian
[15:21] <mvo_> seb128: the libs are multi-arch, this is about being able to install a cross build environment, so the -dev lib needs to be multi-arch friendly
[15:21] <mvo_> seb128: sorry, I should have mentioned that in the changelog
[15:22] <seb128> mvo_, well, as said you are going to have that issue with gobject based lib
[15:22] <seb128> dev depends on gir is standard
[15:22] <seb128> also we are in sync with debian for those packages
[15:22] <seb128> those changes look lik a local hack rather than a proper solution?
[15:23] <mvo_> seb128: the proper solution is to make gir1.2-* package multiarch capable
[15:23] <mvo_> seb128: but I'm taking one step at a time
[15:24] <mvo_> seb128: the problem is that gir has arch dependant typelibs but a single path
[15:24] <mvo_> seb128: we need triplet paths
[15:24] <seb128> mvo_, can you talk to slomo about getting that one step in Debian so we can stay in sync?
[15:24] <mvo_> seb128: but that probably(?) means that all the loads need adjustment? i.e. perl/python etc. or is there a single loader codebase :) ? if so, I'm happy to start hacking on that
[15:25] <seb128> not sure if anyone has looked at multiarching gir, did you try asking pitti?
[15:25] <seb128> he knows that stack quite well since he's one of the maintainers
[15:25] <pitti> I haven't looked into this
[15:25] <seb128> k
[15:25] <seb128> mvo_, still, changing that depends to a recommends look wrong, so -1 from me
[15:26] <mvo_> pitti: do you know if there is a single loading code or if each binding implements this? the path lookup
[15:26] <seb128> as said you are going to hit that issue with any lib shipping a gir
[15:26] <mvo_> seb128: well, we are not shipping any other gir libs in ubuntu-sdk-libs
[15:26] <pitti> mvo_: no, (hopefull) all bindings will use libgirepository, which is built by gobject-introspection
[15:26] <mvo_> seb128: those are the only offenders
[15:26] <seb128> and that seems a workaround, likely to create bugs and add divergence on debian
[15:26] <pitti> mvo_: so only that library does the .typelib lookup and parsing
[15:28] <mvo_> seb128: well, patching libgirepository and multi-arching the gir packages is also a diversion and may trigger bugs (and a even bigger one). the alternative might be to simply drop the libs from ubuntu-sdk-libs-dev
[15:28] <mvo_> pitti: thanks, I check that out then
[15:29] <seb128> mvo_, well, multiarching should be done in debian for those
[15:29] <seb128> but otherwise +1 from dropping the depends then
[15:29] <mvo_> seb128: right, I think we agree that the proper fix is gir multiarch but that is some way away
[15:30] <seb128> mvo_, sorry, it's our weekly meeting time
[15:30] <seb128> hey desktopers
[15:30] <mvo_> ok
[15:30] <seb128> it's meeting time ;-)
[15:31] <seb128> qengho, Sweetshark, Laney, tkamppeter, desrt, attente, larsu, didrocks, FJKong, willcooke, hey
[15:31] <willcooke> \o/
[15:31] <seb128> let's start by welcoming our new manager ;-)
[15:31] <seb128> willcooke, welcome on board!
[15:31] <desrt> willcooke: what's up?
[15:31] <willcooke> thank you very much
[15:31] <larsu> welcome willcooke!
[15:32] <willcooke> Hi guys, sorry I still havent got round to meeting you all 1 to 1 yet.
[15:32] <willcooke> I will get that sorted as a matter of priority
[15:32] <didrocks> hey!
[15:32] <Sweetshark> o/
[15:32] <Sweetshark> welcome willcooke!
[15:33] <willcooke> thanks Sweetshark
[15:33] <seb128> willcooke, did you want to say anything else before we start our usual team roundtable?
[15:34] <seb128> we have a slot after the roundtable for extra discussions ;-)
[15:34] <willcooke> I don't have much to say right now, other than what I've already said about 1:1 meetings with everyone.
[15:34] <seb128> k, makes sense
[15:34] <seb128> willcooke, thanks
[15:34] <seb128> ok, let's get started then
[15:34] <seb128> qengho, hey, you can start ;-)
[15:36] <seb128> no qengho?
[15:36] <seb128> Sweetshark, your turn then!
[15:36] <Sweetshark> - ongoing: create a docker/saltstacked ubuntu tinderbox for easy deployment upstream, using http://tinderbox.libreoffice.org/MASTER/status.html and http://skyfromme.wordpress.com/2013/08/03/tb3-more-efficient-tinderboxing/
[15:36] <Sweetshark> - ongoing: reenabling tests on 4.3 -- might be fixed by --disable-mergelibs
[15:36] <Sweetshark> - travel coord. for Bern (LibreOffice conference) and Montevideo (CISL Avanza)
[15:36] <Sweetshark> - cleaned up/merged changelogs for 4.2.4 security SRU
[15:36] <Sweetshark> - waiting for 4.2.6.2 tag (today) for 14.04 SRU
[15:36] <Sweetshark> - looked into bug 1170035: unfortunately a mess to solve with -l10n split out and *.desktop files having all translations in one file (which is not in an -l10n package) :/
[15:36] <Sweetshark> - various bugzilla and launchpad prowling
[15:36] <Sweetshark> - leading the ESC call, provided some LibreOffice 4.2 vs. 4.3 bug stats: http://nabble.documentfoundation.org/bjoern-michaelsen-canonical-com-minutes-of-ESC-call-2014-07-17-td4115852.html -- likely will blogify those ~around 4.3.0 upstream release
[15:36] <Sweetshark> - trying (and mostly failing) to ignore the heat
[15:36] <Sweetshark> EOF
[15:37] <seb128> Sweetshark, let me know when you get some SRU ready/if you need some sponsoring
[15:37] <seb128> didrocks, seems like you are not alone playing with docker ;-)
[15:37] <didrocks> looking so :)
[15:37] <Sweetshark> seb128: sure, will need some time riping in the PPA still
[15:37] <seb128> Sweetshark, thanks
[15:38] <seb128> k
[15:38] <seb128> Laney, hey, your turn
[15:38] <Laney> hai
[15:38] <Laney> • Sponsor xdg-utils for ochosi, provide advice on the sru process
[15:38] <Laney> • Update glib, find bugs (pcre3 in Debian breaks tests, gmutex native impl breaks shotwell)
[15:38] <Laney> ∘ Merge tracker for test fix due to new warning
[15:38] <Laney> ∘ Patch deja-dup likewise
[15:38] <Sweetshark> didrocks: kepp you hand of my docker *sternlook*
[15:38] <Laney> • Find patch for harfbuzz/myanmar crash (#1303516), upload + SRU
[15:38] <Laney> • u-s-s
[15:38] <Laney> ∘ Work a lot on test fixes, seems green now
[15:38] <Laney> ∘ Fix, not optimally due to SDK bugs, bug with scrolling in sound panel
[15:38] <Laney> ∘ On jd_strand's advice, revert apparmor profile to fix sound playback
[15:38] <Laney> ∘ Increase spacing in the main grid
[15:38] <Laney> ∘ Reviews/pushback on scope creep in the schemas
[15:38] <Laney> • DMB: Finish zequence's mail application, flush a large set of updates to all flavour packagesets - the script hadn't been run for several months if not a year.
[15:38] <Laney> • Starting to look at gst 1.4 now that we got the base packages in Utopic by syncing (good done, bad not yet)
[15:38] <Laney> • Off Thursday + Friday this week, then GUADEC, then a trip to China(!)
[15:38] <Laney> ⚘
[15:39] <seb128> Laney, enjoy the days off before the travelling ;-)
[15:40] <seb128> well done on the harfbuzz patch, installer bugs are not nice
[15:40] <Laney> we've already consulted the Good Beer Guide :P
[15:40] <seb128> Laney, thanks!
[15:40] <seb128> lol
[15:40] <seb128> good thinking ;-)
[15:40] <qengho> Ah, I missed the beep. I'm here.
[15:40] <seb128> qengho, ok, your turn then!
[15:40] <qengho> - chromium-browser 36.0.1985.125 preparation,
[15:40] <qengho> -- fixing webapps patches for package,
[15:40] <qengho> -- and fixing mir patches for testing.
[15:40] <qengho> EOF
[15:41] <seb128> qengho, what's the status for chromium 36? it has been some week where you say it's ready for upload
[15:41] <seb128> is that blocked on the security team?
[15:41] <qengho> That was 35. Security has it.
[15:41] <seb128> not utopic though?!
[15:42] <seb128> oh, well, not other series either
[15:42] <seb128> https://launchpad.net/ubuntu/+source/chromium-browser
[15:42] <seb128> so blocked on security? did you try to ping them? what is blocking? can we help to unblock?
[15:42] <qengho> That's true, I could have found someone else to upload to U. :(
[15:43] <qengho> I hear from CCC on #security that it's on his list, but I haven't harassed him.
[15:43] <seb128> ok
[15:43] <seb128> let's wait a ping and ping jdstrand or chrisccoulson then
[15:43] <seb128> thanks
[15:44] <willcooke> qengho, seb128 - let me know if you want me to take care of that
[15:44] <seb128> willcooke, well, I don't know for how long it's blocked on them but it seems to be a while, that upload was ready to go a week ago already
[15:44] <seb128> willcooke, if you want to check with jdstrand was is blocking that would be nice
[15:44] <willcooke> seb128, ack
[15:44] <qengho> Thanks.
[15:45] <seb128> qengho, thanks
[15:45] <seb128> willcooke, thanks as well ;-)
[15:45] <willcooke> np
[15:45] <seb128> tkamppeter, hey, your turn
[15:46] <seb128> no tkamppeter?
[15:46] <seb128> desrt, ok, your turn then
[15:47] <desrt> hey
[15:47] <desrt> was on vacation all of last week, and i don't remember _too_ much about the week before that
[15:47] <desrt> but git log says that i landed the gmutex-natively-on-linux stuff along with the big performance improvements to GDBus for fixed-sized arrays
[15:47] <desrt> i'd say that this sounds nice, but Laney already tells me otherwise ;)
[15:48] <Laney> did you expect it to make working apps into non working ones? :)
[15:48] <Laney> even if it turns out to be shotwell being wrong
[15:48] <willcooke> :)
[15:48] <desrt> after that i started taking larsu's comments about my markup parser stuff into account and did a fair bit of work for fleshing out the interface to something that we could think about landing... found a few thorns on the API meanwhile, but we talked about that today and came up with a good plan
[15:48] <desrt> Laney: who knows.... maybe out there somewhere is a non-working app that now works properly, too :)
[15:49] <Laney> anyways, the comments on the bug said that the speed improvements can be quite nice
[15:49] <Laney> so it'll be a win in the end
[15:49] <desrt> Laney: thanks for the support :)
[15:50] <desrt> eof for me.
[15:50] <seb128> desrt, thanks
[15:50] <seb128> attente, hey, your turn
[15:50] <tkamppeter> - system-config-printer: Work on driver download hanging when initiated out of the D-Bus service (used by other printer setup tools).
[15:50] <tkamppeter> - Mentoring of GSoC students, midterm evaluations
[15:50] <tkamppeter> - Some organizational stuff for OpenPrinting Summit.
[15:50] <tkamppeter> - Bugs.
[15:50] <attente> :)
[15:51] <seb128> lol
[15:51] <seb128> tkamppeter, thanks
[15:51] <seb128> attente, your turn now then I guess ;-)
[15:51] <attente> hey hey
[15:51] <attente> trying to do dynamic language switching again, got it somewhat working after using an insecure apparmor policy
[15:51] <attente> so working on a separate system settings service that will live on the session bus and provide read-only access to the current accountsservice user's properties
[15:52] <desrt> attente: why not in something like g-s-d or so?
[15:53] <attente> on the device?
[15:53] <desrt> hmm.  don't we have something like this there?
[15:53] <desrt> seems weird that we would have a separate daemon only for this one thing.
[15:54] <desrt> let's talk later...
[15:54] <seb128> yeah, we don't have a g-s-d equivalent in there
[15:54] <larsu> we have indicator-* there though
[15:54] <seb128> but might be a good topic for when we are together at GUADEC
[15:54] <larsu> one more won't hurt!
[15:54] <desrt> seb128: good call

[15:54] <desrt> larsu just got an elbow in the side for that comment.... before i saw the </sarcasm>...
[15:54] <seb128> attente, I did a landing of u-g-m to utopic with the 3 branches that were ready
[15:54] <larsu> desrt: I forgive you
[15:55] <attente> seb128: great, thanks!
[15:55] <seb128> attente, the SRU are still on my list, trying to get to those this week
[15:55] <seb128> yw
[15:55] <seb128> attente, anything else?
[15:55] <attente> seb128, that's it from me
[15:55] <seb128> ok
[15:55] <seb128> attente, when do you travel?
[15:56]  * Sweetshark hands out a new set of elbows to spend to everyone.
[15:56] <seb128> not a topic meeting so moving on ;-)
[15:56] <seb128> larsu, hey, your turn!
[15:56] <larsu> hey
[15:57] <larsu> I wasn't very productive last week because I didn't feel very well
[15:57] <attente> seb128: friday evening, arriving sat morning
[15:57] <larsu> I did manage to look over attente's branch and test it on my machine
[15:57] <larsu> thanks again attente
[15:57] <seb128> attente, k, safe travel!
[15:57] <larsu> also talked to Company how we could have a better situation with o-s, but he says it'll be hard
[15:57] <seb128> larsu, oh, I hope you are feeling better
[15:57] <desrt> (btw: for those who didn't guess, i'm on CEST for the next days...)
[15:58] <larsu> seb128: thanks
[15:58] <seb128> desrt, next week as well
[15:58] <desrt> seb128: eeveryone already knows that part, though :)
[15:58] <attente> larsu, seb128, thanks :)
[15:58] <larsu> I've helped desrt again with the xml reader stuff (review, api talk)
[15:59] <larsu> made adwaita (and other themes) not use overlay scrollbars because they don't have the background hacks
[15:59] <seb128> larsu, we should discuss o-s with willcooke, but let's not do that today, he's just starting and it's a bit out of topic for the weekly roundtable
[15:59] <larsu> seb128: yep, I agree
[15:59] <willcooke> kk
[15:59] <larsu> and some minor things that I don't remember :)
[15:59] <seb128> willcooke, basically the overlay scrollbar are quite hackish and not easy to maintain, they create work and problems
[15:59] <larsu> like, dropped the gtk hacks from evince
[15:59] <larsu> and lots of discussion about various things
[15:59] <larsu> eof I think
[15:59] <seb128> willcooke, they also only work for gtk apps
[16:00] <willcooke> right
[16:00] <seb128> we were wondering if we should consider dropping the feature since it's inconsistant
[16:00] <larsu> and not for every gtk app....
[16:00] <seb128> that was  a summary so you have some context
[16:00] <seb128> let's discuss that another topic
[16:00] <seb128> larsu, thanks
[16:00] <seb128> ups
[16:00] <seb128> "let's discuss that another time"
[16:00] <seb128> rather
[16:00] <seb128> didrocks, hey, your turn!
[16:00] <didrocks> * Continue adding integration tests to ubuntu developer tools center. Up to 250 small tests (~40s) and 12 large tests (~640s)
[16:01] <didrocks> * Some fixes and refactoring in the way we execute and run default frameworks with a full new set of tests and better large tests abstractions.
[16:01] <didrocks> * Better launcher icons handling.
[16:01] <didrocks> * Evaluate lxc and docker for running medium ubuntu developer tools center tests inside that destructible environment. Choose docker.
[16:01] <didrocks> * Read and rampup on docker documentation and create an ubuntu-desktop compatible image (multiple quirks).
[16:01] <didrocks> * Start (on-going) integrating that image to the medium tests (different surprises when doing that :p)
[16:01] <didrocks> * Sync up with Stephane on China trip preparation
[16:01] <didrocks> * Some sponsoring (xdg-utils on utopic) and MIR (Tracker) discussions
[16:01] <didrocks> * Minor changes to http://people.canonical.com/~platform/design/ for the design team.
[16:01] <didrocks> * ah, and grasp chinese visa from Lyon's consulate \o/
[16:01] <didrocks> EOF
[16:01] <larsu> seb128: oh I forgot: I looked into Trevinho's scrolling issues, but haven't come very far yet
[16:01] <larsu> sorry didrocks :P
[16:01] <seb128> larsu, k
[16:01] <seb128> didrocks, the launcher handling ... you use the dbus api now?
[16:02] <didrocks> seb128: no, as it won't work for our case
[16:02] <didrocks> it's only for installing, with progress, and so on
[16:02] <didrocks> (and tight to apt only)
[16:02] <didrocks> but now, I put it in a more logical place than always latest
[16:02] <didrocks> so, that workarounds the bug until Trevinho fixes it
[16:03] <seb128> k
[16:03] <seb128> didrocks, let us know how docker is working for you ;-)
[16:03] <seb128> didrocks, thanks
[16:03] <didrocks> yeah, it's "interesting" at times
[16:03] <seb128> FJKong, hey! still around? wanting to share something with us this week?
[16:03]  * didrocks keeps spawing containers and removing them
[16:03] <FJKong> hi seb128,
[16:04] <FJKong> hi willcooke and team,
[16:04] <FJKong> last week, I finished new feature about sogou Input method for Kylin. some bugs reported by QA were fixed already.
[16:04] <FJKong> this week I will keep on fixing bugs on that. thank you.
[16:04] <seb128> FJKong, thanks
[16:04] <seb128> I think it means it's my turn
[16:04] <seb128> • 4 days week (had friday as a vac)
[16:04] <seb128> • spend some time on travelling preparation still (got my visa for China, yeah!)
[16:04] <seb128> • quite some ubuntu-system-settings code reviews and testing
[16:04] <seb128> ∘ revert from apparmor changes that got deferred
[16:04] <seb128> ∘ conffile cleanups on upgrade
[16:04] <seb128> ∘ some tests improvements and bugfixes
[16:05] <seb128> ∘ lock screen work
[16:05] <seb128> ∘ bluetooth panel refactoring
[16:05] <seb128> • usual bugs/sru/sponsoring queue reviews
[16:05] <seb128> • some SRUs and sponsoring
[16:05] <seb128>  
[16:05] <seb128> that's it for this week (lot of discussions and small debugging on the side as well, as usual)
[16:06] <seb128>  
[16:06] <seb128> ok, anything else to discuss?
[16:06] <willcooke> hi FJKong
[16:06] <FJKong> willcooke: here
[16:06] <willcooke> sorry - FJKong was just replying to you hello :P)
[16:06] <willcooke> :)
[16:06] <willcooke> I'm lagging :)
[16:07] <seb128> seems like we have no other topic
[16:07] <seb128> it's a wrap then
[16:07] <seb128> thanks everyone!
[16:07] <didrocks> yeah, see you guys! thanks :)
[16:07] <Laney> thanks!
[16:07] <seb128> see you at guadec for some of you
[16:07] <FJKong> willcooke: :)  see you soon
[16:07] <seb128> oh, maybe we should skip the next meeting (and the one after that as well?)
[16:07] <seb128> not sure if I'm going to be around at the conf for the meeting
[16:08] <willcooke> FJKong, indeed - really looking to it
[16:08] <didrocks> yeah, and we know the quality of conf network :p
[16:08] <FJKong> welcome you guys to China, Have fun
[16:08] <seb128> oh, but willcooke can lead now
[16:08] <seb128> willcooke, I guess you are going to be around at the meeting time next week?
[16:08] <seb128> willcooke, some of us are going to be at guadec, but in case others still want to do the roundtable
[16:08] <seb128> if not we can just skip the meeting
[16:08] <seb128> (we might need to skip the week after that as well since a bunch of us are going to be in China then)
[16:09] <Laney> desrt loves to chair :P
[16:09]  * desrt moves Laney to the end of the list
[16:09] <seb128> lol
[16:09] <Laney> thanks boss!
[16:09] <desrt> hmm
[16:09]  * desrt moves Laney to the front of the list
[16:09] <Laney> >:( worst boss ever
[16:10] <seb128> yeah, I don't know why didrocks complains about the position
[16:10] <seb128> early sucks if you forgot to prepare your notes ;-)
[16:10] <seb128> can as well go at the end
[16:10] <didrocks> because it's unfair, I'm in this team way before most of people here ;)
[16:10]  * desrt watches seb128 wonder why didrocks likes to complain (regardless of topic) ;)
[16:10] <didrocks> and I come prepared :p
[16:11] <Laney> true that
[16:11] <willcooke> sorry - otp - will reply asap
[16:11]  * Laney gives didrocks some travel to book
[16:11] <Laney> A LOT OF TRAVEL
[16:11] <didrocks> Laney: ok, see you next month! :p
[16:12] <seb128> desrt, lol
[16:12] <desrt> seb128: takes one to know one
[16:13] <seb128> willcooke, don't worry, it's about next week meeting, can be sorted any time this week
[16:13] <seb128> desrt, indeed
[16:19] <seb128> mvo_, could you review https://code.launchpad.net/~mterry/qtmir/packaging-fixes/+merge/226693 ? ;-)
[16:19] <seb128> "Using virtual package names in Conflicts/Replaces lines for clarity and adaptability. You can just provide the virtual names rather than specific ones, and apt will figure it out."
[16:19] <seb128> is that true? ;-)
[16:28] <seb128> ok, calling it a day, have a nice evening everyone!
[16:28] <Laney> bye!
[16:30] <didrocks> you too guys!
[16:30]  * didrocks goes as well with this 4 tests running successfully in my docker image :)
[16:30] <didrocks> (and with 3 lines of code difference from the integration tests ;))
[16:31] <didrocks> more to come tomorrow \o/
[16:34] <Sweetshark> didrocks: hey, I have some more tests for you to run in _your_ docker image ;>
[16:34] <didrocks> Sweetshark: ahah, don't even try :p
[16:35] <didrocks> Sweetshark: I still install libroffice inside my docker image!
[16:35] <didrocks> so, be happy ;)
[16:35] <Sweetshark> didrocks: they are good ones. They make the room cozy by making your machine emit some heat.
[16:35] <didrocks> I'm on the balconee, see, no room… not possible :p
[16:36] <Sweetshark> didrocks: if you have libreoffice installed, can you run autopkgtests on them?
[16:36] <Sweetshark> didrocks: oh, global warming! its you!
[16:37] <didrocks> ahah ;)
[16:41] <chrisccoulson> seb128, qengho, re chromium - I wasn't sure how soon cr36 was going to be ready
[16:41] <chrisccoulson> if it's going to be several days yet, then I'll upload the current version
[16:46] <qengho> chrisccoulson: I think it will be ready Thuraday.
[16:49] <chrisccoulson> qengho, thanks
[16:53] <Laney> Sweetshark: seen https://www.gov.uk/government/news/open-document-formats-selected-to-meet-user-needs ?
[16:56] <chrisccoulson> qengho, I think that 35.0.1916.153-0ubuntu1~pkg1029 (utopic) is a lower version than 35.0.1916.153-0ubuntu1.14.04.0~pkg1027 (trusty)
[16:57] <czajkowski> Laney: great news
[16:57] <chrisccoulson> I'll upload it for now, on the basis that it's probably worth waiting until thursday to upload cr36 to the other releases
[16:57] <czajkowski> chrisccoulson: you having many crashes on utopic on chromium ?
[16:57] <chrisccoulson> czajkowski, no, I only use firefox
[16:57] <chrisccoulson> actually, that's a bit of a lie
[16:57] <chrisccoulson> I use chrome dev too
[16:58] <chrisccoulson> czajkowski, that's probably one for qengho though :)
[16:58] <willcooke> @ next weeks team meeting - yes, happy to run it while you're out at guadec, and indeed for ever more.
[16:58] <meetingology> willcooke: Error: "next" is not a valid command.
[17:03] <Laney> laters potaters
[17:04] <willcooke> l8r Laney
[17:06] <Sweetshark> Laney: yes, just about when you wrote that ... ;)
[17:07] <Laney> thought you might have ...
[17:10] <didrocks> later guys!
[17:16] <pmcgowan> geesh
[17:23] <czajkowski> Trevinho: ello again, so stil running into same issue and trying to restart the session on my admin account, can still loig in fine via guest. on tty1  I've been running GSETTINGS_BACKEND command theen switching to the root account and back to restart ligh session but it's not working today, should I log in first to admin account and then do it?
[17:29] <willcooke> off to catch the train home.  speak to y'all in the morning.  czajkowski let me know how you get on with that bug.
[17:31] <czajkowski> wastl: oh if I coulr report the bug life would be easier :)
[17:31] <czajkowski> stuid tab completion
[18:37] <mvo_> lool: hi, a quick (and potentially silly) question. I'm trying to make apt-get install ubuntu-sdk-libs-dev:armhf work and ran into the issue that gir1.2-* is not multi-arch enabled so not co-installable etc. but libqt5ebkit5-dev pulls in libgstreamer-plugins-base1.0-dev which pulls in a gir1.2 lib which then breaks the multi-arch install. would the world break if I make libgstreamer-plugin-base1.0-dev a recommends of libgstreamer-plugins
[18:37] <mvo_> -base1.0-dev? I assume it would because buildds do not pull in recommends(?). the alternative to make the gir a recommend of libgstreamer-plugins-base1.0-dev was not well received by seb128 so I wonder what we can do. (short of making gir multiarch and rebuilding all packages :)
[18:37] <mvo_> weeh, that was long
[18:38] <lool> mvo_: hey
[18:38] <lool> mvo_: hold on, there is a lot at once  :-)
[18:38] <mvo_> lool: yeah, take your time
[18:38] <mvo_> lool: its long and complicated :)
[18:39] <lool> mvo_: first, I guess making more things multiarch is always nice, so if we can fix gir for being multiarch, that'd be nice, but I suspect it's tricky or it would already be done; I guess it's something like dlopen() stuff that cant be cross-arch, or generate a C file and run it
[18:40] <lool> mvo_: then, indeed, any recommends can probably be ignored for the matter of pulling the right stuff in; I guess you could apt-get install --no-install-recommends ubuntu-sdk-libs-dev:armhf, but you already know all of this
[18:40] <mvo_> lool: yeah, I haven't looked at it, this is the last piece I need to fix and making gir multiarch is a big hammer for just two this one package
[18:40] <lool> mvo_: last, it's worth checking if it's truly a same arch dep, or whether any gir tool would fit the bill
[18:40] <mvo_> lool: unfortunately gir is arch dependent
[18:40] <lool> right
[18:41] <lool> mvo_: if there's a recommends, then this is probably a case of we want some pieces on the developer desktop, but it's not needed for buildds, so one approach could be to split the package
[18:41] <lool> e.g. -dev-bin or something
[18:41] <mvo_> lool: so I want to get it out of the dependencies of ubuntu-sdk-libs if possible without breaking too much and was wondering if you might know more about libqt5webkit5-dev
[18:41] <lool> but that's usually tricky to get backwards-compatible
[18:41] <lool> I know next to nothing about libqtwebkit
[18:42] <lool> I suspect it pulls gst to render videos, like anyone would guess
[18:42] <lool> but it seems odd that you'd need to know about the implementation
[18:44] <lool> mvo_: I find the dependency of qtwebkit on gst suspicious
[18:44] <lool> mvo_: the current webkit .pc files indeed references -lgstreamer in the Libs.private
[18:44] <lool> mvo_: but I find it very suspicious that you'd have to know about the backend implementation and explicitely link your qtwebkit app to that
[18:45] <lool> mvo_: I've unpacked the .deb, and these were the only matches
[18:45] <lool> it's not even listed in Requires...
[18:45] <mvo_> lool: oh, great, so we might get rid of it :-D
[18:46] <lool> mvo_: I have vague memories of Libs vs Libs.private, but my brain has bitrotted there; it would seem to me that Libs.private is only for static linking?
[18:46] <mvo_> lool: but it means I need to patch the .pc file probably and hope no reverse-depends break? but I can check that
[18:46] <mvo_> lool: I don't remember, need to check that myself
[18:46] <lool> mvo_: it's possible that we dont care about Libs.private and that the dep is bogus
[18:47] <lool> mvo_: so I checked pkg-config, and Libs.private is indeed just for static linking
[18:47] <lool> mvo_: if I remember Debian Policy correctly, but again .... , I dont think we require a strict dep there
[18:48] <lool> I'd certainly vote for dropping the dep
[18:48] <mvo_> lool: awsome, thanks a bunch for your help. I test it in a ppa and get back
[18:48] <lool> mvo_: but certainly there must be experience in the desktop team on similar situations with Libs.private; I'm sure seb would know
[18:49] <mvo_> lool: he shut my original proposal down to demote the gir* stuff to recommends :P so he needs to help me finding a alternative solution now ;)
[18:49] <lool> hehe
[18:49] <lool> mvo_: I'm sure he knows which kind of deps or whether we need one at all for Libs.private
[18:57] <mvo_> lool: thanks again for your help! I will send him a mail
[20:38] <Trevinho> czajkowski: set the display variable to :0
[21:12] <robert_ancell> charles, how do you do SRUs for the indicators? J ust chuck stuff in debian/patches or make a new release?
[21:29] <larsu> robert_ancell: we make new releases
[21:29] <robert_ancell> larsu, so I should just propose to a branch?
[21:29] <larsu> yep
[21:29] <larsu> to the 14.04 branch
[21:30] <robert_ancell> cool
[21:56] <arrrghhh> hello.  just updated the ubuntu install on my father's machine, and he is complaining about gnucash and the reports not working properly.  He wants to downgrade, but I don't think it's a good idea.  Is there a way to run an older version of a package when there's a newer one in the repo's?  I tried to compile 2.4.15 for him, as he said 2.6.x is no good.  It ran for a while, but some update from Ubuntu he said removed it...
[21:58] <sarnold> arrrghhh: look for 'pin' in apt_preferences manpage
[21:59] <sarnold> arrrghhh: there's no gaurantee about how well the software will work out, but there's the mechanism to make it happen :)
[21:59] <arrrghhh> hm
[21:59] <arrrghhh> so much work for something so silly... thx
[21:59] <sarnold> yeah, it isn't expected to happen often..
[22:00] <arrrghhh> he has some REALLY strong feelings about how they redid their report system, and based on some bug reports others feel the same as he does... but GnuCash is saying that's how it should be, and it was actually a bug with how it was working before in 2.4 lol.
[22:01] <sarnold> heh, I've been on both sides of that before.
[22:02] <arrrghhh> ditto, and gnucash is not going to fix it seemingly... or even provide the old report functionality.