=== chihchun_afk is now known as chihchun
=== chihchun is now known as chihchun_afk
=== chihchun_afk is now known as chihchun
=== marcusto_ is now known as marcustomlinson
[08:27] <dednick> davmor2: Hi. Waiting on QA test for silo54. You know if anyone has picked it up?
[08:28] <davmor2> dednick: it's in the queue, not picked up yet
[08:28] <dednick> davmor2: ta.
[09:23] <seb128> btw for those who wonder about the mir blocked in proposed/bootest regression
[09:24] <seb128> it seems that the bootest test tries to update only the package it considers, not the silo set
[09:24] <seb128> e.g https://jenkins.qa.ubuntu.com/job/wily-boottest-mir/lastBuild/artifact/results/log/*view*/ updates mir
[09:24] <seb128> but doesn't update things that got rebuilt
[09:24] <seb128> so in this case old unity-system-compositor is kept and mir update
[09:24] <seb128> and the mismatch makes the compositor hit a stack smash error
[09:25] <seb128> ideally new mir should for to upgrade u-s-c then
[09:40] <mandel> sil2100, ok, si I'm getting a little annoyed with my silo hehe => https://ci-train.ubuntu.com/job/ubuntu-landing-009-1-build/298/console
[09:40] <mandel> sil2100, timeout? wtf?
[09:41] <sil2100> mandel: hey! Missing build dependencies: libubuntuoneauth-2.0-dev (>= 15.10) <- the vivid part of the dual landing is missing this dep
[09:42] <mandel> sil2100, agh, and how can we fix that?
[09:42] <sil2100> mandel: the train was waiting and waiting for the dependency to be resolved and suddenly said it's enough waiting, since the dep still doesn't exist
[09:42] <mandel> sil2100, makes sense, but how can that be fixed?
[09:43] <mandel> sil2100, do we have to build the unit-click-scope in a diff silo?
[09:43] <sil2100> Let me check for this package
[09:43] <mandel> thx
[09:45] <sil2100> mandel: I think you'll have to ask tsdgeos or someone from the ubuntuone-credentials team to release the latest version to the vivid overlay-ppa...
[09:46] <tsdgeos> sil2100: mandel: i know nothing about  ubuntuone-credentials, dobey is your man
[09:46] <mandel> tsdgeos, ack
[09:46] <mandel> dobey, please.. whenever you are up ^^
[09:47] <sil2100> tsdgeos: latest release in wily was from your commit so I thought you were driving that ;)
[09:47] <tsdgeos> sil2100: nah, i just fixed a wrong anchors in the qml
[10:20] <doko> sil2100, whoever: https://bugs.launchpad.net/bugs/1475982  can you tell me how this was built in the past?
[10:20] <ubot5> Ubuntu bug 1475982 in mir (Ubuntu) "mir (main) build-depends on abi-compliance-checker (universe)" [Critical,Confirmed]
[10:44] <cjwatson> kyrofa: I cancelled some more unity-scope-snappy builds because they were hanging.  It looks like you still have a problem with processes (perhaps test harnesses or something) being left around by your build process.  You need to make sure that you clean them up.
[11:36] <marcustomlinson> trainguards: could somebody please reconfigure silo 8, had to add 2 MPs
[11:45] <zbenjamin> trainguards: can someone please assign line 66 ?
[11:46] <dobey> mandel, sil2100: yeah, you can't do dual landings for unity-scope-click
[11:46] <sil2100> marcustomlinson, zbenjamin: on it
[11:46] <zbenjamin> sil2100: thanks :)
[11:46] <marcustomlinson> sil2100: thanks
[11:54] <cwayne_> davmor2, sil2100 yo, you guys need me for anything or are we all set?
[11:55] <sil2100> cwayne_: hey! We'd need the custom tarballs pushed - we also were thinking we need the wily custom tarballs
[11:55] <sil2100> Once those land, we'll release the hooks and build a new image
[11:55] <davmor2> cwayne_: we alway needs someone to blame and ogra_ gets all of snappy now so feel free to hang around I'm sure we'll find something :)
[11:57] <cwayne_> davmor2, :P
[11:58] <cwayne_> sil2100, so am i good to press the buttons for both bq and arale?
[11:58] <davmor2> cwayne_: number 1 is obvious how did you let your phone get run over?
[11:58] <ogra_> davmor2, just to make popey happy... let me tell you that switching to snappy will fix that
[11:58] <ogra_> :P
[11:58] <popey> \o/
[11:58]  * popey adds 1 to the counter
[11:58] <ogra_> :)
[11:58] <sil2100> davmor2: ^ it's fine to release the vivid custom tarballs, right?
[11:59] <davmor2> sil2100: if it is the one I tested then yes
[11:59] <sil2100> davmor2: yeah, those you tested with the customization hooks
[11:59] <davmor2> sil2100: yeap that is fine
[12:00] <sil2100> cwayne_: then you're good to press teh buttonz
[12:00] <sil2100> cwayne_: I tried contacting penk to create the wily versions of the tarballs too...
=== alan_g is now known as alan_g|lunch
[12:07] <cwayne> sil2100: ze buttonz, zey have been pushed
[12:07] <dobey> mandel, sil2100: it looks like content-hub and system-settings also have separate trunk and 15.04 branches
[12:07] <sil2100> zbenjamin: which line? 66 seems assigned already
[12:07] <sil2100> cwayne: thankz!
[12:08] <sil2100> dobey: system-settings is being dual-landes since a while now
[12:08] <cwayne> sil2100: ill try and whip up a wily guy today too if we dont hear from penk
[12:08] <sil2100> Content-hub I guess too
[12:08] <dobey> sil2100: well the upstream branches don't have matching history, so if that's true something is very broken there
[12:09] <sil2100> dobey: content-hub and system-settings don't have matching history as their being now built only from one trunk, the other is out of date probably
[12:09] <zbenjamin> sil2100: meh i was in the deprecated one again ....
[12:10] <dobey> sil2100: anyway, unity-scope-click/ubuntuone-credentials definitely do not support dual landings.
[12:11] <sil2100> mandel: ^
[12:11] <dobey> and almost everything using the dual landings is probably going to find things breaking soon
[12:12] <dobey> did u-d-m break abi?
[12:12] <zbenjamin> sil2100: 78 there it is
[12:12] <sil2100> zbenjamin: on it!
[12:14] <sil2100> zbenjamin: assigned
[12:18] <ogra_> did anyone else notice that there is quite some dealy before apps take input after being brought to fg ?
[12:18] <ogra_> that used to be below or around 1sec ... now it is rather 2-3 sec
[12:18] <ogra_> for me at least
=== _salem is now known as salem_
[12:19] <seb128> on what device?
[12:19] <seb128> no such issue on my bq
[12:19] <ogra_> seb128, most noticeable on arale but bq as well ... just not as long
[12:19] <ogra_> it used to be fine a while ago ... but recently got worse
[12:20]  * ogra_ cant nail it to a particular image version sadly
[12:21] <dobey> mandel: ugh, you broke ABI but aren't bumping the so version?!
[12:21]  * popey has no update to his bq e.45
[12:23] <ogra_> popey, system-image-dbus can take 20-30 min to time out
[12:23]  * popey reboots :)
[12:25]  * sil2100 away to prepare lunch
[12:25] <dobey> ugh and it's a 5 month old silo with the main MP still not approved
[12:25]  * ogra_ gets an rc-propoased update on arale
[12:26] <ogra_> dobey, like a good wine :)
[12:27] <dobey> ogra_: no such thing. and whisky needs a lot more time :)
[12:27] <ogra_> true
[12:28] <ogra_> so let it be for another 8 years :)
[12:28] <jibel> davmor2, sil2100 only 6 preferred apps on arale rc-proposed 63, is it expected?
[12:28] <dobey> but the really good ones are like $5000
[12:28] <ogra_> dobey, well, perhaps that is what mandel is after with that silo :)
[12:29] <dobey> ogra_: well, then i guess we'll have to wait another 30 years to land it ;)
[12:29] <ogra_> but by then it will have become really tasty at least :)
[12:30] <dobey> and we'll be deep into world war III wand won't care about it :)
[12:31] <ogra_> nah we'll be past wars by then
[12:32] <popey> \o/ OTA-5 installed on my retail bq
[12:32] <popey> nice work everyone
[12:32] <sil2100> jibel: the custom hooks didn't land there yet
[12:32] <sil2100> Next image should be fine
[12:32] <dobey> ogra_: then we'll be dead, so still won't care :)
[12:32] <sil2100> (no new rootfs)
[12:33] <jibel> sil2100, okay, thanks. I wasn't sure it landed at the same time than the tarball or not.
[13:04] <boiko> sil2100: hi, so I know silo assignment is now self-service, but is it also the case for source landings?
[13:07] <sil2100> boiko: well, assignment of source landings is self-service, but you still need someone with rights to upload the source package
[13:07] <sil2100> (core-dev or trainguard)
[13:09] <boiko> sil2100: ah ok, thanks, so could you please copy the source deb from this PPA to silo 57: https://launchpad.net/~boiko/+archive/ubuntu/source-uploads
[13:20] <sil2100> boiko: sure, will do in a moment
[13:20] <boiko> sil2100: thanks!
=== alan_g is now known as alan_g_
[13:31] <ogra_> sil2100, err
[13:31] <ogra_> i just got an update on my arale and now my favorites reverted to 6
[13:31] <ogra_> i had 8 for the last week or longer
[13:32] <ogra_> jibel, davmor2 ^^
[13:32] <ogra_> that looks like a regression
[13:32] <davmor2> ogra_: you should have 8 I did
[13:33] <ogra_> i used to have 8 for the last 7-10 days
[13:33] <ogra_> the last two just vanished with this recent upgrade
[13:33] <davmor2> ogra_: how it only just landed
[13:33] <ogra_> (there were definitely 8 before reboot, i used the gallery from there right before updating)
[13:33] <davmor2> ogra_: what channel are you on
[13:33] <ogra_> rc-proposed
[13:34] <ogra_> which i assume just got the same new custom tarball
[13:34] <davmor2> ogra_: oh that is because the tarball is in but the hooks package isn't
[13:34] <davmor2> ogra_: next image will fix it
[13:34] <sil2100> ogra_: oh, don't worry, that's normal...
[13:34] <ogra_> ah, so it will switch back to 8 with next rootfs ?
[13:34] <ogra_> ok
[13:34] <sil2100> Yeah, should
[13:34] <ogra_> phew
[13:34] <sil2100> ;)
[13:34] <davmor2> ogra_: I thought you meant on the stable channel you git ;)
[13:35]  * ogra_ was a bit shocked ... last minute regression... yadda yadda ...
[13:38] <jibel> ogra_, the debconf db is precompiled now in the custom tarball and the new hooks package uses the new path, so you need both to really fix the fav apps
[13:39] <ogra_> uh, debconf ?
[13:39] <jibel> dconf*
[13:39] <ogra_> why would we use it at all
[13:39] <jibel> sorry
[13:39] <ogra_> ah
[13:39] <ogra_> k
[13:39] <sil2100> rc-proposed is ment to be broken! I vote for renaming rc-proposed to rc-breakage
[13:40] <ogra_> it wasnt til last week :P
[13:40]  * ogra_ wishes the telegram breakage would also quieten the telegram notifications
[13:44] <davmor2> ogra_: you can disable the notifications per channel :P
[13:44] <ogra_> davmor2, if you can start the app, yeah :P
[13:44] <ogra_> (telegram doesnt work anymore on -proposed)
[13:45] <davmor2> ogra_: or turn them off in system-settings
[13:45] <davmor2> ogra_: then you can turn them back on when it is fixed
[13:45] <ogra_> yeah, i could do that i suppose
[13:46] <davmor2> ogra_: you're welcome :)
[13:47] <ogra_> :D
[13:48] <balloons> josepht, good morning! When do you expect the changes to sudoku-app-ci to land today?
[13:48] <josepht> balloons: within the next hour or so.
[13:48] <balloons> awesome, ty
[13:49] <josepht> balloons: np
[13:57] <sil2100> boiko: uploaded
[13:58] <boiko> sil2100: thanks!
[14:22] <sil2100> Ok, landing the customization hooks
=== chihchun is now known as chihchun_afk
[14:27] <sil2100> jibel, davmor2, rvr, robru: any objections for cancelling the evening meeting?
[14:27] <sil2100> I need to jump out to the vet and I don't know if I'll make it on time
[14:28] <davmor2> sil2100: what did you do to the cat
[14:28] <sil2100> It's either running around like crazy in the appartment or sleeping
[14:28] <sil2100> Currently sleeping
=== tvoss is now known as tvoss|afk
=== mihir_ is now known as mihir
[14:46] <sil2100> brb
[14:46] <josepht> balloons: the sudoku-app utopic jobs should now be disabled
[14:47] <balloons> josepht, thanks. I still see it as a downstream project on the job though
[14:48] <josepht> balloons: sorry, I forgot to click the build linke, should be done in a few minutes
[14:48] <balloons> sudoku-app-utopic-amd64-ci and the link to generic-mediumtests-utopic should be going away yes?
[14:49] <josepht> balloons: I believe so
[15:15] <balloons> josepht, ohh, don't forget about the -autolanding portion too :-)
[15:18] <josepht> balloons: you should be all set now
[15:27] <balloons> jobs look good
[15:27]  * balloons fires a build
[15:45] <karni> ping trainguards - I've added Telegram to CI Train sheet. Telegram is completely broken on rc-proposed, because the old thumbnailer that we dynamically linked with, has been removed from the image. I would politely ask to prioritize if possible, as this affects a number of users/developers on rc-proposed.
=== timp is now known as t1mp
[15:59] <robru> karni: I don't see anything in the spreadsheet?
[16:00] <karni> robru: last row
[16:00] <karni> robru: row 50
[16:00] <robru> karni: https://docs.google.com/spreadsheets/d/1LiPHq39XvPaTQoE8vmi-dqSVMTGGLfCh7bFY01BcNNk/edit#gid=0 last row is 81 and isn't your thing
[16:01] <karni> robru: tarballs and clicks sheet
[16:01] <karni> robru: https://docs.google.com/spreadsheets/d/1LiPHq39XvPaTQoE8vmi-dqSVMTGGLfCh7bFY01BcNNk/edit#gid=50
[16:02] <karni> robru: sorry I wasn't specific
[16:03] <robru> karni: I guess you need QA then. jibel ^
[16:03] <karni> yes, thank you
[16:13] <jibel> karni, did you test it already, is it ready for verification by someone in QA?
[16:13] <karni> jibel: yes
[16:13] <karni> jibel: 3 people tested this change
[16:14] <karni> jibel: If you're on rc-proposed, it would make it easy to test the fix. If not, you could temporarily move /usr/lib/arm-linux-gnueabihf/thumbnailer/vs-thumb to vs-thumb.old, and confirm thumbnail generation still works in Telegram for sent videos.
[16:15]  * karni goes link the branch with the appropriate bug
[16:16] <karni> done. jibel, here I describe how I tested it. I also had 2 other people confirm. https://code.launchpad.net/~libqtelegram-team/libqtelegram/app-bundle-thumbnailer/+merge/265260
[16:16] <jibel> karni, that's fine it should be alright. Which part of telegram uses thumbnails?
[16:17] <karni> jibel: sent videos ;) like I mentioned just above :)
[16:17] <jibel> just sent videos?
[16:17] <karni> jibel: yessir
[16:17] <jibel> ok
[16:17] <karni> :)
[16:27] <rvr> dobey: alecu: https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1476319
[16:27] <ubot5> Ubuntu bug 1476319 in unity-scope-click (Ubuntu) "[Dash] App label word being wrapped" [Undecided,New]
[16:27] <slangasek> robru, sil2100: I'm afraid I have a conflict today for our call; would you be ok to move it a half hour later, or should we skip?
[16:28] <robru> slangasek: I'm ok to skip; just working with IS and nothing really to report
[16:30] <sil2100> I'm ok to skip as well
[16:49] <boiko> kenvandine: do you by chance have some time to look into the packaging changes on silo 57?
[16:49] <dobey> rvr: that is the dash
[16:50] <rvr> dobey: Sorry. Which project is that?
[16:50] <dobey> rvr: unity8
[16:50] <dobey> there's already a bug or two open on it even
[16:50] <rvr> dobey: Ok
[16:53] <kenvandine> boiko, sure
[16:53] <boiko> kenvandine: thanks!
[16:53] <dobey> i thought so, but i can't find it now. i know i moved a bug about that over to unity8 recently
[16:54] <dobey> oh, no
[16:54] <dobey> that's a different bug than the previous one i moved, ok
[16:56] <kenvandine> boiko, ack on silo 57
[16:56] <boiko> kenvandine: great! thanks!
[16:56] <kenvandine> np
[16:56] <boiko> kenvandine: do I need to tell the trainguards I got an ack, or do you mark a flag there or something like that?
[16:56] <kenvandine> tell them
[16:57] <boiko> trainguards: hey, kenvandine gave his ack on the packaging changes on silo 57, could you please go ahead and publish it?
[16:57] <boiko> kenvandine: thanks!
[16:57] <sil2100> boiko: sure
=== alan_g is now known as alan_g|EOD
[17:08] <doko> infinity, can you setup additional transition trackers for the silo16?
[17:09] <doko> for now, it would be icu, boost1.57 and apt
[17:12] <rvr> boiko: Silo 30 approved
[17:12] <boiko> rvr: nice! thanks!
[17:13] <boiko> rvr: I know you have a queue, but silo 43 is a really trivial one (just testing that one string shows translated in messaging-app), so in case you are looking for a break from long testplans, that's a good candidate :)
[17:14] <rvr> boiko: EOD here :)
[17:14] <rvr> boiko: Buy maybe tomorrow
[17:15] <boiko> rvr: no worries, enjoy your evening!
[17:15] <rvr> Thanks :)
[17:37] <infinity> doko: silo-016 is just represented in the main transition tracker, it's not a seperate instance.  So, if you just commit ben files to the tracker, they'll DTRT.
[17:38] <balloons> fginther, fyi all the -ci jobs are cloned on jenkaas now, I'm just going through and resolving the build errors
[17:41] <mandel> dobey, around?
[17:42] <dobey> hi
[17:42] <infinity> doko: Oh, I realised you didn't commnit the last one, Colin did for you.  So, yeah, if you get me the right configs and either propose an MP to https://code.launchpad.net/~ubuntu-transition-trackers/ubuntu-transition-tracker/configs or just give me the files raw, I can commit them.  Or, if you'd rather be added to the team to do it yourself, we can do that.
[17:44] <dobey> mandel: you cannot do an ubuntu/dual landing for unity-scope-click
[17:45] <mandel> dobey, really? how come?
[17:45] <mandel> dobey, does that mean that we will have a diff scope in the overlay ppa? is that what we want?
[17:45] <dobey> mandel: we maintain separate branches for wily and vivid landings.
[17:45] <mandel> ack
[17:45] <dobey> mandel: yes, because we develop features in the development release, not the stable tree
[17:45] <mandel> sil2100, so... that ppa cannot be a double one, sigh :-/
[17:46] <dobey> there are also lots of other things different in wily, from what's in vivid
[17:46] <dobey> dual landings is going to be pretty much impossible in 2 weeks anyway
[17:51] <bfiller> robru: can I get a silo for line 80 please?
[17:56] <boiko> bfiller: according to robru silo assignment is now self-service, so you just select the row, Landing Tools -> Assign/Reconfigure
[17:56] <bfiller> boiko: ok cool, didn't know that
[17:57] <boiko> bfiller: yep, I have been using it for a few days already
[17:57] <robru> bfiller: yeah it's a recent thing. there'll be a larger announcement about this when the spreadsheet replacement goes live (any. day. now...)
[18:02] <kyrofa> trainguards: My silo has passed its test plan, and I'm ready to put a "yes" into column K. However, it's destined for Ubuntu Personal which does not have an official release image yet. Will "Yes (#1 Ubuntu Personal kyrofa)" break things?
[18:03] <boiko> robru: so, now sync doesn't work for non-train generated versions, right? should I ust change the silo to be a source land to vivid too? (regarding silo 54)
[18:03] <fginther> balloons, cool.  Have you tested any of the .click artifacts?
[18:03] <balloons> fginther, no, but I should do so for the ones that built. lol, thanks for the reminder :-)
[18:04] <robru> kyrofa: won't break anything... the train has no ability to push packages to anything other than ubuntu though, so you'll have to get your packages manually copied from the PPA I guess.
[18:04] <robru> boiko: did that start as a manual upload to wily?
[18:05] <boiko> robru: yep
[18:05] <boiko> robru: well, not manual, a source landing via train
[18:05] <robru> boiko: righ
[18:05] <kyrofa> robru, I actually want it to land in wily-- Ubuntu Personal is currently only a seed
[18:05] <kyrofa> robru, is that okay?
[18:05] <robru> boiko: yeah you'll have to do another source landing for vivid then. if you'd faked the train-style version number it could have done a sync for you.
[18:05] <robru> kyrofa: just put 'yes' in column K
[18:06] <kyrofa> robru, well that's easy!
[18:06] <robru> kyrofa: ok what's going on? is this the one that's never been released in wily before?
[18:06] <sil2100> cwayne1: ping!
[18:06] <boiko> robru: ok, no problems, let me cook a vivid package and then I put it on a ppa for you to copy to the silo
[18:06] <robru> boiko: ok
[18:06] <kyrofa> robru, that's correct
[18:06] <sil2100> cwayne1: could you add ci-train-bot to the https://launchpad.net/~savilerow-team/ team?
[18:07] <sil2100> cwayne1: the train was unable to merge the branch in...
[18:07] <robru> kyrofa: and you're ready to publish? you tested the packages in the PPA and they look good?
[18:07] <kyrofa> robru, the failure is only due to a lack of depends on a few archs. The issues are ignorable and should get better after the initial publish
[18:07] <kyrofa> robru, yessir!
[18:07] <robru> kyrofa: ok, will publish
[18:08] <kyrofa> Thanks robru :)
[18:08] <robru> kyrofa: you're welcome
[18:08] <kyrofa> robru, and that will merge the relevant branches into trunk as well and update the status of the MPs?
[18:08] <robru> kyrofa: what happened with your packaging? I know we were talking about that last week. aside from me/steve did anybody else look at that?
[18:09] <kyrofa> robru, changing to quilt solved all my problems
[18:09] <robru> kyrofa: right but did you get any blessing from any official people?
[18:10] <kyrofa> robru, well, I guess not. Like who?
[18:11] <robru> kyrofa: ultimately it needs an archive admin to do a NEW review, hang on
[18:11] <kyrofa> robru, ah, that makes sense-- brand new package and all
[18:14] <robru> kyrofa: ok it's publishing, it'll sit in the NEW queue for a bit, I just asked in #ubuntu-release if they can review it, we'll see if there's any takers. Maybe ping there again if nothing happens after a few hours
[18:15] <kyrofa> robru, on freenode?
[18:15] <robru> kyrofa: yeah
[18:15] <kyrofa> robru, great, thank you!
[18:15] <robru> kyrofa: you're welcome
[18:17] <balloons> fginther, clicks work. I heard rumblings about tarmac the other day in regards to having jenkins respond to mp's. Are you planning to provide some more example jobs
=== elopio_ is now known as elopio
[18:27] <fginther> balloons, that's one of the questions we're planning on addressing this week.
[18:27] <boiko> robru: can you please copy the source deb from this PPA to silo 54? https://launchpad.net/~boiko/+archive/ubuntu/source-uploads/+packages
[18:28] <robru> boiko: one sec
[18:28] <boiko> robru: sure, take your time
[18:29] <balloons> fginther, ack. Something else that came across my mind in regards to sustainability. Can we setup the jobs to pull from an lp source?
[18:30] <robru> boiko: ah, apparently I can't copy the binaries until after the binaries finish publishing. will be a few minutes then.
[18:30] <balloons> fginther, I mean, pull the job definitions ofc, not code :-)
[18:32] <boiko> robru: ok
[18:32] <fginther> balloons, do you mean store the job configurations in a LP branch? For saving and restoring?
[18:33] <balloons> fginther, yes. In theory that could allow others to easily suggest tweaks to job configs, etc
[18:35] <dobey> hrmm?
[18:36]  * dobey sees "tarmac" and raises a brow
[18:37] <robru> boiko: ok, started a "build": https://ci-train.ubuntu.com/job/ubuntu-landing-054-1-build/4/console
[18:37] <boiko> robru: thanks! on a different matter, silo 30 is ready to publish whenever you get some time
[18:37] <robru> boiko: oh,s ure
[18:38] <fginther> balloons, We're not providing any pre-package method for doing this, but it can be done. I would recommend something like python-jenkins as the interface for a simple script to read and write job configuration data from a branch
[18:38] <balloons> fginther, noted. I'll look into it
[18:44] <jgdx> the qa signoffs "ready for testing" column, is that an ordered queue?
[18:46] <robru> jgdx: maybe? they track it at https://trello.com/b/AE3swczu/qa-testing-requests-for-questions-ping-eu-jibel-us-jfunk-or-ubuntu-qa-on-ubuntu-ci-eng
[18:49] <jgdx> robru, okay
[19:04] <robru> boiko: no qa on 54?
[19:05] <boiko> robru: it is just a missing dependency on the dev package
[19:05] <boiko> robru: so I guess it is not worth spending the precious time of QA on that, right?
[19:06] <robru> boiko: oh, is it really so trivial? ok then, will publish
[19:06] <robru> boiko: lel https://ci-train.ubuntu.com/job/ubuntu-landing-054-2-publish/lastSuccessfulBuild/artifact/libphonenumber_content.diff/*view*/
[19:06] <boiko> robru: you can check the diff to confirm, but it is basically that the  dev package should require libprotobuf-dev
[19:36] <kyrofa> robru, should I ping anyone specific in #ubuntu-release, or just ask in general?
[19:37] <robru> kyrofa: ask in general I guess, those guys are usually pretty busy and I've seen them get fussy about being pinged by name
[19:37] <kyrofa> robru, soudns good
[19:46] <charles> woo
[19:50] <robru> brb
=== karni is now known as karni-afk
=== karni-afk is now known as karni
[21:18] <veebers> trainguards, Do I need anything to trigger another publish attempt for my silo (051) failed earlier due to MP not being approved
[21:28] <robru> veebers: ah crap i stepped out, just on phone now. Will be a couple hours as in at the doctor's
[21:28] <robru> veebers: maybe kenvandine is around to hit publish?
[21:31] <veebers> robru: ack, if he's not I can wait for you. Hope all is well :-)
[21:32] <robru> veebers: yeah I'm OK just a checkup, thanks. I'll probably be 3 or 4 hours though.
[22:00] <robru> veebers: ah, that was way faster than I thought ;-)
[22:01] <veebers> robru: ^_^
[22:01] <veebers> I guess a quick checkup is a good checkup
[22:05] <robru> bzoltan_: zbenjamin: need this top-approved: https://code.launchpad.net/~zeller-benjamin/qtcreator-plugin-ubuntu/mzanettis_switches/+merge/264168
[22:05] <robru> veebers: indeed! all good news
[22:05] <bzoltan_> robru:  done, thanks
[22:49] <robru> cihelp: http://people.canonical.com/~platform/citrain_dashboard/#?q=ubuntu%2Flanding-004 did anybody look at these boottest regressions yet?
[22:52] <fginther> robru, ah, these are all part of the same landing... These all fail. In the ones I've looked at more closely, there's an unity-system-compositor crash
[22:52] <robru> fginther: oh wow, so it's a legit failure and not just flakiness?
[22:52] <fginther> robru, I thought something else was going on, but didn't realize these were all connected
[22:53] <fginther> robru, yes, I've been able to reproduce locally and look at the symptoms. unity8 does not come up
[22:54] <fginther> robru, I have to run to dinner, but will be online later if you have more questions
[22:55] <robru> fginther: no worries, thanks
[22:55] <robru> anpok: are you aware of this ^^ ? seems silo 4 is broken
[23:03] <slangasek> fginther: hi, I notice your name on https://jenkins.qa.ubuntu.com/job/wily-boottest-bind9/lastBuild/console - are you actively debugging boottest stuff? infinity just noticed it was broken and blocking things
[23:07] <infinity> slangasek: Read a few lines up from your ping, he seems to think all the failures are a legit unity8 bug.
[23:09] <slangasek> infinity: that appears to be referring to a landing; not clear to me that he's talking about a problem with something in the archive
[23:10] <robru> slangasek: that landing is stuck in proposed due to bootest failures...
=== salem_ is now known as _salem