[01:46] <dobey> CommandError: Multiple image matches found for 'ubuntu/ubuntu-vivid-15.04-ppc64el-server-20151117-disk1.img', use an ID to be more specific.
[01:46] <dobey> trainguards: ^^ this seems to be blocking some autopkgtests on ppc64el
[01:47] <robru> Wat
[01:47] <robru> dobey: where are you seeing that?
[01:48] <dobey> http://autopkgtest.ubuntu.com/running.html
[01:48] <dobey> scroll to the bottom, and ubuntuone-credentials shows that
[01:49] <dobey> i saw the "request autopkgtests" button on citrain and thought i'd try it. now my request's status is stuck at "Autopkgtest: in progress." because ppc64el test runner is stuck in an infinite loop trying to spawn an image or something
[01:49] <robru> dobey: that's nothing to do with the train. I guess you should poke pitti
[01:50] <robru> dobey: also don't click that it's experimental and not working very well
[01:50] <dobey> robru: is there any way to unblock the train status? or should i just ignore that and move along with requesting QA?
[01:50] <robru> dobey: well i could clear it manually. The only way for you is to rebuild the silo. Want me to clear it?
[01:51] <dobey> robru: yes please. thanks
[01:51] <robru> dobey: OK. Which silo was that?
[01:51] <dobey> https://requests.ci-train.ubuntu.com/#/ticket/668
[01:52] <kgunn> robru: hey, i got a little bit of a strange one...in silo 20, the qtmir for vivid didn't rebuild even tho i chose FORCE_REBUILD
[01:53] <kgunn> i had swapped out original mp's...and retargeted to dual landing...so maybe it's just a bug
[01:53] <kgunn> not sure if you wanna debug? or if you would, just delete the qtmir for vivid out of that ppa
[01:53] <kgunn> and i'll rebuild
[01:53] <robru> dobey: ok that should clear up in a sec
[01:54] <robru> kgunn: looking
[01:54] <kgunn> np
[01:54] <kgunn> thanks
[01:54] <dobey> robru: thanks
[01:55] <robru> dobey: you're welcome
[01:56] <robru> kgunn: https://ci-train.ubuntu.com/job/ubuntu-landing-020-1-build/284/consoleFull this log looks like it's building qtmir and qtmir-gles. what went wrong?
[01:58] <robru> kgunn: huh that's weird the log shows "2015-11-17 22:47:22,811 INFO Creating secondary build in /var/lib/jenkins/silos/ubuntu/landing-020/qtmir_+vivid." but I see it is missing from the PPA
[02:03] <robru> kgunn: http://paste.ubuntu.com/13322918/ that log shows the vivid version being uploaded, since it didn't make it into the PPA we need somebody like cjwatson to dig in and see why lp rejected the upload.
[02:04] <robru> kgunn: although there sure are a lot of strange errors about missing dependencies in that log, not sure how it got past that to do the package upload...
[02:14] <kgunn> robru: so am i stuck ?
[02:14] <kgunn> i kinda need to rebuild that qtmir before euro morning
[02:15] <robru> kgunn: yeah sorry, I don't have access to the info to figure out what went wrong in order to fix it
[02:15] <robru> kgunn: if it's urgent you could also try pinging infinity or wgrant, they might be more likely to be around at this time than colin
[02:15] <kgunn> robru: hmm...could i just create a new silo request as a way to start over
[02:16] <robru> kgunn: I don't know if that would fix it, it's possible the reason it's being rejected is unrelated to the silo.
[02:16] <kgunn> kk
[02:16] <robru> kgunn: I mean you could certainly try that, but I'd try to reach those other people I mentioned first, they'll be able to say definitively why the package didn't make it to the ppa
[02:22] <robru> kgunn: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-020/+packages?field.name_filter=qtmir&field.status_filter=&field.series_filter=vivid looks like the ppa already has 0.4.7 in it and you're trying to upload 0.4.6.
[02:22] <robru> which is weird because I thought the train had a check against that...
[02:23] <robru> kgunn: so you need to either go back to 0.4.7 or get a different silo, yeah
[02:25] <robru> off to the gym, brb
[02:25] <robru> (brb in 2 hours)
[07:56] <FourDollars> Hi, how can I reuqest a landing for https://code.launchpad.net/~fourdollars/unity-settings-daemon/fix-lowest-brightness/+merge/277326 ?
[08:02] <FourDollars> Where is trainguards?
[08:03] <robru> FourDollars: Hi
[08:03] <robru> FourDollars: did you ever use the train before?
[08:03] <FourDollars> robru: Can you give me the required permissions for operating the CI Train?
[08:03] <FourDollars> robru: No
[08:04] <robru> FourDollars: OK, one sec. What's your launchpad name?
[08:04] <FourDollars> robru: fourdollars
[08:04] <robru> OK
[08:05] <FourDollars> robru: Then?
[08:06] <robru> FourDollars: instructions are here: https://wiki.ubuntu.com/citrain/LandingProcess but may be stale. Feel free to ping trainguards if you need help. I'm EOD but others should be around soon
[08:07] <FourDollars> robru: Have you given me  the required permissions for operating the CI Train?
[08:07] <robru> FourDollars: yes
[08:07] <FourDollars> robru: thx
[08:07] <robru> FourDollars: if it isn't working, log out and log back in. You're welcome
[08:11] <Mirv> FourDollars: I'm here
[08:11] <FourDollars> Mirv: Thx
[08:15] <FourDollars> Mirv: I have created https://requests.ci-train.ubuntu.com/#/ticket/672. What should I do next?
[08:15] <FourDollars> Mirv: Never mind. I got it.
[08:18] <FourDollars> Mirv: Could you help to check https://requests.ci-train.ubuntu.com/#/ticket/672?
[08:18] <Mirv> FourDollars: checking
[08:18] <FourDollars> Mirv: thx
[08:20] <Mirv> FourDollars: looking correct for a xenial landing otherwise, but set the QA setting to "No QA Needed" first. once you've assigned a silo, built and tested it, you can set it to "Publish without QA" so that it'll set to published
[08:21] <FourDollars> Mirv: OK. Let me try it.
[08:21] <Mirv> FourDollars: that setting and its options are confusing, we know, there's a bug about it.
[08:22] <robru> FourDollars: is this change needed for ubuntu touch?
[08:22] <FourDollars> robru: I don't know.
[08:22] <Mirv> robru: looks like desktop
[08:22] <FourDollars> robru: It is for the desktop users.
[08:22] <Mirv> FourDollars: ok, the next step is to assign the silo. then you can click build and it starts building.
[08:23] <robru> ok
[08:23] <FourDollars> Mirv: Still failed. :-(
[08:23] <FourDollars> Mirv: I saw "2015-11-18 08:22:55,354 ERROR Prepare failed: Low on silos: Ask a trainguard to assign."
[08:25] <Mirv> FourDollars: oh! sorry about that, let me check if there's anything to free up some silos.
[08:28] <Mirv> FourDollars: ok you got one?
[08:28] <FourDollars> Mirv: yes
[08:29] <Mirv> I freed one silo
[08:29] <Mirv> FourDollars: great!
[08:29] <FourDollars> Thx a lot~
[08:29] <FourDollars> What should I do now?
[08:30] <Mirv> FourDollars: so now you've a new action "Build" available. that runs a jenkins job which eventually gets the package to the assigned silo (010, https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-010/) from where you can test it
[08:31] <FourDollars> Mirv: OK
[08:32] <Mirv> FourDollars: so now you received an error regarding the MP that you need to fix
[08:32] <Mirv> FourDollars: the commit message will be used in the changelog entry
[08:33] <Mirv> (you've only set the description so far)
[08:33] <FourDollars> Mirv: I see. Thx.
[08:38] <Mirv> FourDollars: hey, rather just add the commit message on this page: https://code.launchpad.net/~fourdollars/unity-settings-daemon/fix-lowest-brightness/+merge/277326 than in changelog
[08:39] <Mirv> FourDollars: in changelog it's ok but actually it's cleaner if you just revert your last commit and use the commit message field in LP, so that the changelog gets generated automatically
[08:40] <FourDollars> Mirv: OK
[08:40] <bzoltan> jibel: the UITK with the updated translation files is available in silo5.
[09:19] <FourDollars> Mirv: What is the next step?
[09:19] <mardy> Mirv: hi! Is there something I should correct with this? https://requests.ci-train.ubuntu.com/#/ticket/591
[09:23] <Mirv> FourDollars: it would be ready for testing (it's useful to always test the fresh build once more). but the changelog currently looks funny: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-010/+sourcepub/5707430/+listing-archive-extra - if you want to fix that, set the text you want in the MP's commit message instead and remove the debian/changelog change from the MP, so that the tra
[09:23] <Mirv> in can generate the changelog by itself.
[09:23] <FourDollars> Mirv: Haha
[09:23] <Mirv> FourDollars: anyway, when ready, upgrade to the PPA, and if the testing is fine you can set the status to "Publish without QA". after that is set, you can either try to publish yourself (it will tell you if you can't), or you can get a trainguard to publish it.
[09:24] <FourDollars> Mirv: OK. Thx.
[09:33] <FourDollars> Mirv: I saw "2015-11-18 09:32:15,795 ERROR Merging failed: No commit message found. Please specify one either in your merge proposal or in debian/changelog." again.
[09:34] <FourDollars> Mirv: Could you tell me where is problem I should fix on https://code.launchpad.net/~fourdollars/unity-settings-daemon/fix-lowest-brightness/+merge/277326?
[09:34] <seb128> FourDollars, do what the error says?
[09:34] <seb128> FourDollars, you need a commit message on the mp and you don't have one, there is a button to set one
[09:35] <FourDollars> seb128: I got it. Thx a lot. :D
[09:35] <seb128> yw
[09:38] <Mirv> FourDollars: yes, now it looks correct! the next build should be fine in the PPA.
[09:39] <FourDollars> Mirv: Thx.
[09:41] <FourDollars> Mirv: I was not aware there is a button to set the commit message on https://code.launchpad.net/~fourdollars/unity-settings-daemon/fix-lowest-brightness/+merge/277326.
[09:42] <Mirv> mardy: it claims to have a gregression in armhf autopkgtests which is why it hasn't migrated http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#online-accounts-api
[09:43] <Mirv> FourDollars: right, that bit of LP I've found a bit weird - when you create the MP, you only can fill the "Description" field - only after the MP is created, you can set the commit message which is what is actually used for merges, changelogs etc.
[09:44] <FourDollars> Mirv: I agree.
[09:45] <FourDollars> It seems that I don't need to use pbuilder or sbuild to build the package manually. I just need to use the CI train.
[09:51] <seb128> Mirv, FourDollars, that statement is untrue, there is a small arrow on the mp submition page which gives you details, including a commit message section
[09:51] <seb128> but yeah, it's not on screen by default
[09:51] <bzoltan> Mirv: zbenjamin:  I have pushed the qmake-extras to the silo5 ... it is nothing but a version bump
[09:52] <zbenjamin> bzoltan: ok!
[09:52] <FourDollars> seb128: It is optional so people always ignore it by default. XD
[09:52] <seb128> right, that's annoying
[09:54] <Laney> Not once you get burned by it a few times
[10:02] <Mirv> seb128: wow, I never noticed that
[10:02] <Mirv> I've gradually started to use the Extra Options on other pages but not there before this
[10:03] <Mirv> bzoltan: ok
[10:15] <FourDollars> 2015-11-18 10:14:12,916 ERROR Needs review: https://code.launchpad.net/~fourdollars/unity-settings-daemon/fix-lowest-brightness/+merge/277326
[10:15] <FourDollars> 2015-11-18 10:14:12,917 ERROR Publish failed: unity-settings-daemon has merges in bad states
[10:15] <FourDollars> Mirv: Any idea?
[10:15] <pete-woods> sil2100: okay, we have a successfully built silo again, and seb128 acked the packaging yesterday
[10:16] <pete-woods> I obviously can't publish gmenuharness myself, so what's the next stap?
[10:16] <pete-woods> *step
[10:17] <Mirv> FourDollars: the MP needs to be top-approved (the Status at the top), you can probably ask pitti to do that
[10:17] <FourDollars> Mirv: OK.
[10:19] <xavigarcia> sil2100: Hi there! What would be the statu of silo 000? is it waiting to get reviewed by somebody else?
[10:20] <sil2100> xavigarcia: hey! Yes, we need an archive admin doing the preNEW review, I poked seb128 yesterday but not sure if he wasn't waiting for the package to get renamed
[10:20] <sil2100> seb128: did you manage to take a look at the new package in silo 000?
[10:20] <seb128> xavigarcia, pete-woods, read backlog, that's what pete-woods was talking about
[10:22] <pete-woods> xavigarcia: FYI I manually merged all the outstanding MRs into the tree for seb128's review
[10:22] <pete-woods> so he'd get the complete fiew
[10:22] <pete-woods> view
[10:22] <pete-woods> and the silo just has an empty MR in it now
[10:23] <seb128> I had a look yesterday and it was fine to me, just the descriptions could be a bit more descriptive
[10:23] <pete-woods> yeah, I agree with that
[10:23] <FourDollars> Mirv: What is the next step for https://requests.ci-train.ubuntu.com/#/ticket/672?
[10:23] <pete-woods> you could probably generate those descriptions ;)
[10:24] <sil2100> seb128, pete-woods: remember that you can now always access the merged branch of the train
[10:25] <sil2100> https://code.launchpad.net/~ci-train-bot/gmenuharness/gmenuharness-ubuntu-xenial-landing-000
[10:25] <sil2100> (as an example)
[10:26] <Mirv> FourDollars: it is now published (congrats for your first train publishing!), the next step is simply waiting to see if it migrates from -proposed pocket to -releae pocket, after which the ticket will be marked as Landed. this takes often takes hours at minimum, so there's nothing to do right now. the package is at https://launchpad.net/ubuntu/+source/unity-settings-daemon/15.04.1+16.04.20151118.1-0ubu
[10:26] <pete-woods> yeah, that's good to know :)
[10:26] <Mirv> ntu1
[10:26] <Mirv> FourDollars: https://launchpad.net/ubuntu/+source/unity-settings-daemon/15.04.1+16.04.20151118.1-0ubuntu1 (repaste since IRC cut the line)
[10:27] <FourDollars> Mirv: Cool. Thx a lot. :)
[10:27] <Mirv> FourDollars: you're welcome
[10:29] <rvr> xavigarcia: ping
[10:29] <xavigarcia> rvr: pong
[10:30] <rvr> xavigarcia: Hi, yesterday I was testing silo 51
[10:30] <xavigarcia> rvr: I was now testing what you posted for it
[10:30] <rvr> xavigarcia: Ah, cool
[10:31] <xavigarcia> rvr: let me check and will ping you back
[10:31] <rvr> xavigarcia: Sure
[10:31] <xavigarcia> rvr: what was the case exactly when you cannot trigger the warning?
[10:32] <xavigarcia> rvr: after moving volume down or after pressing cancel?
[10:33] <rvr> xavigarcia: Hmm
[10:33] <seb128> FourDollars, congrats on the landing, and thanks for handling it ;-)
[10:33] <rvr> xavigarcia: I pressed "Ok"
[10:33] <xavigarcia> rvr: ah, in that case you approved the warning... and it does not appear again
[10:34] <xavigarcia> rvr: maybe the test plan is not clear enough
[10:34] <rvr> xavigarcia: Yeah, I was confused about what to do with the notification
[10:34] <rvr> xavigarcia: Is there any way to reset it?
[10:35] <xavigarcia> rvr: the idea is that when you approve the warning it should not appear again until you unplug and plug the headphones again
[10:36] <rvr> xavigarcia: Yeah, understood
[10:36] <xavigarcia> rvr: so... unplug the headphones.... keep playing music, plug the headphones again and the warning should be reseted
[10:36] <xavigarcia> rvr: If not it would be annoying for the user to be all the time approving the warning once he already did
[10:37] <rvr> xavigarcia: I thought the notification only appeared once "in a lifetime"
[11:16] <xavigarcia> rvr: sorry, I had a phone call
[11:16] <xavigarcia> rvr: yeah, but there was a bug opened asking to reset that then unplugging the headphones
[11:22] <rvr> xavigarcia: Ack
[12:39] <pete-woods> seb128: so do we need you to do that prenew thingy then? or is that someone else
[12:49] <rvr> xavigarcia_lunch: Take a look to the card (when you're back :)
[13:10] <seb128> pete-woods, I did that yesterday no?
[13:11] <renatu> Mirv, ping
[13:16] <Mirv> renatu: pong
[13:17] <Mirv> renatu: I see your email
[13:17] <renatu> Mirv, I just sent you a e-mail :D
[13:17] <renatu> Mirv, nice thanks
[13:21] <pete-woods> seb128: I have no idea. I don't know how to check what has or hasn't been done on that end. does that mean I just need a properly authorised person to hit "publish" now?
[13:21] <pete-woods> (https://ci-train.ubuntu.com/job/ubuntu-landing-000-2-publish/build)
[13:21] <seb128> somebody with upload rights I guess
[13:22] <pete-woods> seb128: okay, well at least I know you've done the pre-upload now :)
[13:22] <seb128> right
[13:22] <pete-woods> just need to badger for the CI train publish
[13:23] <pete-woods> sil2100: apparently the pre-upload was done by seb already yesterday
[13:23] <pete-woods> I think we just need to publish now
[13:23] <rvr> tvoss: Hey. FYI, silo 47's merge proposals need review.
[13:25] <xavigarcia> rvr: Ok thanks... I'm taking a look
[13:32] <jibel> tvoss, mardy you can publish silo 57 the status is bileto is wrong
[13:33] <xavigarcia> rvr: I have one question... what do you mean with "After the volume confirmation dialog has auto-closed"?
[13:33] <rvr> xavigarcia: The high volume dialog, I wait until it is auto-dismissed
[13:34] <xavigarcia> rvr: ah, ok... good one.. I've never tried that
[13:34] <xavigarcia> rvr: In relation with the volume changing while the warning is showing... you can modify the volume, but it will never go beyond the warning level until you press OK
[13:34] <xavigarcia> rvr: I think that is what we expect
[13:35] <rvr> xavigarcia: The test case explicitly says that volume shouldn't change while the high volume dialog is displayed
[13:35] <xavigarcia> rvr: in relation to the label in the volume notification. After discussion with design we decided that it was best to remove it, as it was not specified in the regulations and because we now have the output label
[13:36] <xavigarcia> rvr: I think I need to update the test plan
[13:36] <rvr> xavigarcia: Yes, please :)
[13:36] <xavigarcia> rvr: I will confirm with the spec first, but in relation to the label it was removed intentionally
[13:36] <mterry> sil2100, robru: I have a silo I want to add a manually uploaded package to.  It's been a little while since I've done this.  I add the package name to the "Source Package Names" field and just upload to the ppa?  for both overlay and xenial?
[13:36] <xavigarcia> rvr: OK, I will update and will ping you when it's ready
[13:37] <xavigarcia> rvr: I also need to test the auto-dismissed warning dialog. I don't think that's what we want to happen
[13:44] <xavigarcia> rvr: Ok, I managed to recreate the issue you mention... looking for a fix. thanks!
[13:45] <jibel> robru, hey, some silos in bileto have a status 'Requesting autopkgtests for this silo...' can you fix them?
[13:53] <rvr> xavigarcia: Ack
[13:59] <tvoss> rvr, I know
[13:59] <tvoss> rvr, see comment on the silo
[14:01] <rvr> tvoss: The reason to do QA after reviews is that, even if the developer doesn't expect any change, there could be, and would be wasted time if verification was done or in progress.
[14:02] <tvoss> rvr,  as you wish, I just set it to qa'able as it works fine
[14:05] <bzoltan> Mirv: could you help me with the silo number five?
[14:14] <Mirv> bzoltan: helping
[14:15] <bzoltan> Mirv:  thank you
[14:17] <bzoltan> Mirv: ^ WUT?
[14:18] <bzoltan> Mirv:  queuebot: 3.5.2+16.04.20151118-0ubuntu1
[14:18] <Mirv> bzoltan: might be because of the binary -> source trick. I'll publish manually.
[14:18] <bzoltan> Mirv: could be. Thank you
[14:21] <bfiller> is errors.ubuntu.com working for anyone? I keep getting Aw Snap page in chromium
[14:28] <jibel> bfiller, works fine here
[14:28] <sil2100> mterry: hey! Yeah, that's more or less what you should do
[14:28] <mterry> sil2100, cool
[14:29] <bfiller> jibel: weird ok
[14:48] <seb128> pmcgowan, jibel, there was langpack regression in the ota8 candidate pointed this morning on #ubuntu-touch, unsure how much of an issue it is
[14:48] <seb128> I reported https://bugs.launchpad.net/canonical-devices-system-image/+bug/1517501 about it
[14:49] <seb128> basically the unity8 translations got reverted to their june state because somebody changed the domain on launchpad
[14:51] <pmcgowan> wha??
[14:51] <sil2100> huh?
[14:54] <sil2100> I wonder how serious it is
[14:54] <sil2100> rvr: hey, could you install the recent rc image and check if unity8 translations look okayish?
[14:54] <seb128> xavigarcia, charles, shrug, seems like the most recent indicator-sound landing regressed notifications under unity7, mouse scrolling over the indicator makes notify-osd grumpy :-/
[14:54] <seb128> xavigarcia, charles, reported https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1517502
[14:54] <rvr> seb128: o_O
[14:55] <seb128> xavigarcia, charles, that's 2 recent regressions under unity7, you guys need to start testing your changes on desktop as well please
[14:57] <seb128> rvr, sil2100, pmcgowan, seems we fixed the template at the right time, today langpacks in the overlay fixes the issue
[14:57] <seb128> the ones that landed an hour ago
[14:57] <rvr> seb128: Cool
[14:57] <sil2100> seb128: still, this would mean we'd need to import the new langpacks to OTA-8 and re-spin
[14:58] <seb128> right
[14:58] <sil2100> Which is pretty bad
[14:58] <seb128> well I think that the revert to june is an issue for e.g Chinese
[14:58] <seb128> they had incomplete translations by then
[14:58] <seb128> and we lost quite some strings
[14:58] <rvr> Right
[14:58] <sil2100> pmcgowan, jibel, rvr: we need to check this, we might need to re-spin or issue an emergency OTA-8+
[14:58] <seb128> see https://launchpadlibrarian.net/226898897/language-pack-touch-zh-hans_1%3A15.04%2B20151111_1%3A15.04%2B20151118.diff.gz
[15:00] <seb128> strings like "Device Locked" or "Power"  or "Return to Call" were lost
[15:00] <seb128> remove/add to favorite, pull to refresh
[15:00] <seb128> going to be quite a step back on chinese
[15:05] <xavigarcia> seb128: roger that.... I will take a look
[15:05] <seb128> xavigarcia, thanks
[15:06] <xavigarcia> seb128: is this happening in wily?
[15:06] <seb128> xavigarcia, I guess not, that landing was in xenial only
[15:07] <seb128> xavigarcia, though I didn't try wily in the overlay ppa if that's what you mean
[15:07] <xavigarcia> seb128: so to recreate... I should move the mouse over any sound notification?
[15:07] <seb128> xavigarcia, no, you should mouse scroll over the indicator to change the volume
[15:08] <seb128> like using a mouse wheel or touchpad edge scrolling/fingers
[15:08] <xavigarcia> seb128: ah, ok... understood
[15:08] <pete-woods> seb128: FYI, when I've tried to run changes to packages (e.g. HUD) through the QA process, I was told that QA don't do desktop packages, only phone ones
[15:08] <seb128> xavigarcia, did you change the format of the notifications?
[15:08] <pete-woods> so the only testing will be done by the devs themselves
[15:08] <seb128> pete-woods, right, doesn't mean devs shouldn't test on their unity7 sessions
[15:09] <xavigarcia> seb128: I've only added a label to show the output
[15:09] <pete-woods> seb128: sure, just thought that info might be useful
[15:09] <seb128> pete-woods, it is, thanks
[15:09] <pete-woods> (like, I think it's probably an issue - that we don't have enough QA resource to do the desktop)
[15:10] <xavigarcia> seb128: just to double check... you are changing the volume with the mouse wheel?
[15:10] <seb128> xavigarcia, yes
[15:11] <xavigarcia> seb128: Ok, I'm never doing that
[15:11] <seb128> xavigarcia, is there other ways to make indicator-sound send notifications on unity7?
[15:11] <seb128> middle click for muting seems also to bug
[15:12] <seb128> though I'm unsure that was sending a notification
[15:12] <Trevinho> seb128: no, there was no notification on middle-click
[15:12] <seb128> k, makes sense
[15:12] <xavigarcia> seb128: the change I've added is just adding a string. That, in fact, I didn't add in first place
[15:13] <xavigarcia> seb128: that string was added for the warning notification dialog, but now the string is shown all the time
[15:13] <xavigarcia> seb128: anyway... will keep an eye and will try to get it fixed asap
[15:14] <Trevinho> thanks
[15:14] <pmcgowan> seb128, sil2100 yeah I dont know that we can ship that
[15:14] <seb128> xavigarcia, we are discussing it on #ubuntu-desktop
[15:14] <pmcgowan> whats it take to fix, one langpack?
[15:14] <seb128> xavigarcia, <larsu> seb128: got it. It sends a title for the notification now, which throws off notify osd
[15:15] <seb128> pmcgowan, well, all locales are buggy, but some probably had an ok status in june and it doesn't matter much
[15:15] <pmcgowan> seb128, how did this happen?
[15:15] <seb128> pmcgowan, somebody changed the unity8 domain name on launchpad
[15:15] <seb128> but seems like launchpad has no log of those events
[15:16] <seb128> so we don't know why/when/why
[15:16] <seb128> it made the langpack update not have an unity8.po but an unity90something.po
[15:16] <pmcgowan> seb128, sil2100 I would vote to fix it with a respin
[15:16] <sil2100> Maybe we could get some logs from LP through the launchpad admins?
[15:16] <pmcgowan> the teal issue is we didnt detect it
[15:17] <seb128> I asked on #launchpad earlier but wgrant didn't find any record of a change
[15:17] <sil2100> Ah, ok, good
[15:17] <seb128> well "good"
[15:17] <sil2100> pmcgowan: I'll copy the langpacks over to the snapshot PPA in a moment
[15:17] <pmcgowan> yep
[15:17] <sil2100> Well, good that you asked ;)
[15:17] <seb128> except it happened,  we have no record of it and no way to know it's not going to happena gain
[15:18] <sil2100> Indeed...
[15:18] <pmcgowan> seems we could detect that we regressed the packs, are they versioned?
[15:18] <sil2100> pmcgowan: I wonder if BQ noticed any regressions in the translations
[15:18] <sil2100> rvr: did you have a chance to check the rc image?
[15:18] <rvr> sil2100: On it
[15:18] <sil2100> pmcgowan: they're versioned, yes, but no one checks their contents as it would be crazy, I would suspect us seeing it during testing
[15:19] <sil2100> Maybe they didn't regress enough to trigger a red flag during QA
[15:19] <pmcgowan> sil2100, we should have an auto test for it, not quite sure how to define it
[15:19] <seb128> sil2100, I think main european languages were fine in their june version
[15:19] <seb128> so likely little different for e.g spanish
[15:19] <rvr> sil2100: pmcgowan: While testing OTA8, I didn't found any big problem
[15:19] <xavigarcia> seb128: so, just to be clear... is this something I need to fix or should be fixed in unity7?
[15:19] <sil2100> We might indeed do a test for this case of a change in the domain name
[15:19] <rvr> in Spanish
[15:20] <seb128> xavigarcia, maybe you can join #ubuntu-desktop?
[15:20] <seb128> xavigarcia, unsure, Lars is looking at the notifications specification
[15:20] <pmcgowan> sil2100, its very important for chinese to be as well translated as possible
[15:21] <sil2100> pmcgowan: yeah, indeed, I wonder since I suppose the meizu.zh channel was tested by the China team
[15:21] <sil2100> jibel: ^
[15:22] <seb128> sil2100, pmcgowan, looking at the diff things like "Device Locked" or "Power"  or "Return to Call" were lost
[15:22] <seb128> or "pull to refresh"
[15:22] <seb128> in the chinese translations
[15:22] <rvr> I found many untranslated strings for click packages in Chinese
[15:22] <rvr> But unfortunately I didn't compare with the previous run
[15:22] <rvr> (from August)
[15:24] <rvr> For a subset of debian packages, these are the stats:
[15:24] <rvr> $ wc -l deb*.log
[15:24] <rvr>    46 deb-es.log
[15:24] <rvr>    46 deb-fr.log
[15:24] <rvr>    60 deb-zh_CN.log
[15:25] <rvr> 60 untranslated strings for Chinese and 46 for Spanish and French
[15:25] <rvr> For click packages:
[15:25] <rvr>    20 click-es.log
[15:25] <rvr>    17 click-fr.log
[15:25] <rvr>   207 click-zh_CN.log
[15:25] <sil2100> So, before I copy all langpacks, I would like someone to make triple sure that the current langpacks fit to the contents of OTA-8
[15:26] <rvr> Which is a similar figure (a bit lower) than in August
[15:28] <rvr> sil2100: In rc #182, in webbrowser-app.mo I see  PO-Revision-Date: 2015-09-24 06:53+0000
[15:29] <sil2100> I think the biggest issue is unity8 translations
[15:29] <sil2100> As that's what regressed
[15:30] <rvr> 2015-09-24
[15:30] <rvr> sil2100: Yeah, checking more recent dates in https://translations.launchpad.net/ubuntu-rtm/15.04/+lang/es
[15:31] <rvr> sil2100: unity8 PO-Revision-Date: 2014-08-26 12:31+0000
[15:31] <rvr> Bad
[15:31] <rvr> In launchpad, unity8 was last edited on 2015-11-11
[15:32] <davmor2> rvr: blame Saviq it won't fix it but you feel so much better ;)
[15:36] <bzoltan> seb128:  I need a coredev to ack the silo5 ... it is pure string update no code change. Would you please help me?
[15:36] <seb128> bzoltan, looking
[15:37] <seb128> bzoltan, ubuntu-sdk-qmake-extras seems to no exist in Ubuntu atm?
[15:38] <bzoltan> seb128:  it does... it used to come from different source. the qtcreator-plugin-ubuntu used to provide it. No it is a separate project
[15:38] <seb128> bzoltan, so it's not as trivial as a pure string update
[15:38] <bzoltan> zbenjamin: or how was it? ^
[15:39] <bzoltan> seb128: wait a sec... am I an idiot or not?
[15:39] <zbenjamin> bzoltan: yes we had to split it off the qtcreator-plugin-ubuntu
[15:39] <bzoltan> seb128: Ohh.. yes, that revision has the shorter control... seb128 is right
[15:39] <sil2100> rvr: could you upgrade your rc device with the latest overlay-ppa langpack for spanish and check if everything looks okayish? Remember that the rc image has stable-snapshot in the sources.list - you need to change it to the overlay first
[15:40] <rvr> sil2100: Ok
[15:40] <sil2100> rvr: thanks :)
[15:44] <bzoltan> zbenjamin: so we need to land the ubuntu-sdk-qmake-extras to 16.04 asap
[15:45] <bzoltan> seb128: zbenjamin: hold on.. we do have that package, I have landed it myself - http://packages.ubuntu.com/search?keywords=ubuntu-sdk-qmake-extras
[15:45] <seb128> bzoltan, https://launchpad.net/ubuntu/+source/ubuntu-sdk-qmake-extras
[15:45] <bzoltan> seb128:  but too old
[15:46] <seb128> ah, it's in the NEW queue
[15:46] <seb128> let me review it
[15:47] <bzoltan> seb128: Huhh... thanks bigbang we have coredevs who udnerstand these things :D
[15:48] <rvr> sil2100: seb128: So, at least in Spanish, the language files that are not up-to-date  are dialer-app, indicator-sound, messaging-app, telephony-service, ubuntu-system-settings and unity8
[15:48] <seb128> bzoltan, that package seems arch neutral, shouldn't be be arch all rather than any?
[15:48] <sil2100> rvr: with the latest overlay langpacks?
[15:49] <rvr> sil2100: No, no, with current rc
[15:49] <sil2100> Ah, ok
[15:49] <zbenjamin> seb128: it needs to be installed into the qt arch specific directories
[15:49] <sil2100> Well, the most recent regression that we're about to fix is the unity8 one
[15:49] <seb128> zbenjamin, ah, ok
[15:50] <rvr> sil2100: What about the others?
[15:50] <seb128> zbenjamin, bzoltan, the export DPKG_GENSYMBOLS_CHECK_LEVEL=4 in the rules is not needed but it's not an issue either ... NEW accepting it
[15:50] <sil2100> rvr: those should be ok, nothing we can do here, the langpacks are auto-generated and we didn't get any news of the domain changing for those
[15:50] <seb128> bzoltan, I published now as well
[15:51] <bzoltan> seb128: thanks, i will fix it and land it for the next round
[15:51] <pete-woods> trainguards: who do I need to bug to click the publish button for the new package (gmenuharness) in silo 000? (seb already pre-new'ed it and acked the packaging)
[15:52] <sil2100> So if there are regressions there then those are from different reasons, we'll have to investigate separately
[15:52] <pete-woods> do we need to corner an archive admin or something?
[15:52] <sil2100> pete-woods: ok, let me press the button then :)
[15:52] <bzoltan> seb128: ^ wadahell?
[15:52] <seb128> bzoltan, hum, publish failed because of ^
[15:52] <sil2100> pete-woods: I can do it as the package is treated by default as an universe package I suppose, it will land in xenial NEW for archive admins and in the overlay
[15:53] <seb128> bzoltan, looks like pitti already landed it ?! https://launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/1.3.1705+16.04.20151118-0ubuntu1
[15:53] <bzoltan> seb128:  feels like Mirv has published it manually
[15:53] <seb128> yeah, unsure what's going on there
[15:53] <seb128> but it's uploaded
[15:54] <rvr> sil2100: What do I need to change in sources.list again?
[15:54] <bzoltan> seb128:  that is the most important! thanks for your help
[15:54] <seb128> yw
[15:54] <sil2100> rvr: I think the sources.list has stable-snapshot instead of overlay, right?
[15:54] <pete-woods> sil2100: awesome, thanks!
[15:54] <pete-woods> I guess the MIR will happen as a separate task
[15:54] <rvr> deb http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu
[15:56] <sil2100> pete-woods: yw!
[16:00] <sil2100> rvr: hm, ok, could you check if pinning is ok as well?
[16:01] <rvr> sil2100: Pin: release o=LP-PPA-ci-train-ppa-service-stable-phone-overlay Pin-Priority: 1001
[16:01] <sil2100> rvr: anyway, strange that the rc images don't have stable-snapshot in it... you sure you using rc, not rc-proposed? And latest?
[16:01] <rvr> Oh, shit
[16:01] <rvr> this is rc-proposed
[16:01] <sil2100> Well, not a big deal, we only had a few landings
[16:02] <rvr> sil2100: Just re-checked the dates
[16:02] <sil2100> But still, best to flash rc ;) And there you'd have to change both pin priority and sources.list
[16:02] <rvr> sil2100: Most are one day off and another is an update for OTA9
[16:02] <rvr> sil2100: So just unity8 looks fine
[16:02] <sil2100> \o/
[16:03] <sil2100> Anyway, I suppose using current langpacks is better than the previous thing...
[16:03] <sil2100> Copying to snapshot
[16:06]  * rvr is finally flashing rc 
[16:27] <rvr> This upgrade takes time
[16:45] <rvr> sil2100: unity8.mo (es) X-Launchpad-Export-Date: 2015-11-18 10:31+0000
[16:46] <rvr> sil2100: unity8.mo (zh_CN) PO-Revision-Date: 2015-07-28 03:57+0000 X-Launchpad-Export-Date: 2015-11-18 10:31+0000
[16:50] <rvr> sil2100: zh_CH revision date matches Launchpad (2015-07-28), so looks good
[16:53] <pmcgowan> sil2100, rvr  what did we end up changing in the respin then, all the langpacks or just unity8
[17:00] <sil2100> pmcgowan: all the langpacks, there was nothing landing that could cause a regression in langpacks
[17:01] <sil2100> pmcgowan: since... generating separate langpacks would be really troublesome
[17:01] <sil2100> rvr, pmcgowan: am I good to copy the langpacks to the snapshot PPA?
[17:02] <pmcgowan> sil2100, do we have an image yet?
[17:02] <pmcgowan> I would copy after verifying the image?
[17:02] <pmcgowan> or does the image use the snapshot
[17:02] <sil2100> We can't have an image without copying to the snapshot
[17:02] <pmcgowan> then yes :)
[17:03] <sil2100> But rvr checked the langpacks manually on the rc image ;)
[17:03] <pmcgowan> got it
[17:04] <sil2100> Ok, copying in progress, once it's done I instantly build an image
[17:05] <rvr> sil2100: Looks good
[17:19] <sil2100> rvr, jibel: image building
[17:20] <sil2100> I jump out now for a walk
[17:20] <jibel> sil2100, okay, I rechecking the language packs you cpoied to the stable snapshit
[17:20] <jibel> oops, snapshot*
[17:21] <jibel> sorry
[17:26] <kenvandine> jibel, system-settings is held up in proposed because it's waiting for autopkgtests from ubuntu-system-settings-online-accounts, which claims to be "Test in progress" on the excuses page
[17:27] <kenvandine> jibel, if i click on the Test in progress link, it shows passed tests, not currently running tests
[17:27] <kenvandine> is the status broken?  or does it only show completed tests?
[17:28] <jibel> kenvandine, I cannot help, it's entirely pitti's domain now. sorry
[17:28] <kenvandine> jibel, ah, ok
[17:29] <kenvandine> i suspect the tests are running but it doesn't show that on the status page, but we'll see :)
[17:34] <robru> mterry: yep, you're a core dev so you can just dput directly to the silo PPAs. Other people need trainguards/core=devs to do itfor them.
[17:52] <jibel> rvr, sil2100 here are all the string changes in unity8 between 34 and the image currently building.
[17:52] <jibel> http://paste.ubuntu.com/13332679/
[18:07] <cjwatson> the liburcu/ppc64el problems are fixed now, so that should unblock mir/qtmir (modulo whatever library transition problems are involved)
[18:09] <dobey> kenvandine: are they running on the running page? :)
[18:11] <dobey> hmm, it's not
[18:16] <pmcgowan> jibel, did anything change outside of unity8?
[18:17] <pmcgowan> sil2100, jibel see my email to john mc
[18:17] <jibel> sil2100, pmcgowan rvr here is the list of strings that were not translated http://paste.ubuntu.com/13332907/ essentially greeter and indicators
[18:17] <jibel> pmcgowan, no nothing else
[18:19] <jibel> pmcgowan, chinese, turkish, basque and greek had much more strings missing than other languages.
[18:20] <pmcgowan> apparently
[18:20] <pmcgowan> jibel, are you comfortable with a sanity check on the respin and then publish that
[18:21] <jibel> pmcgowan, let me check what landed in vivid through SRUs
[18:22] <pmcgowan> jibel, I thought we didnt pick those up now?
[18:22] <bzoltan> pmcgowan: jibel: the translation stuff of the UITK has landed on the Overlay
[18:23] <pmcgowan> bzoltan, yep saw that
[18:23] <pmcgowan> bzoltan, we really just needed it in trunk so translators could do there thing
[18:23] <jibel> bzoltan, yes, thanks for that
[18:23] <bzoltan> pmcgowan: small thing, but makes difference.. it was an easy landing
[18:25] <jibel> sil2100, anything in vivid is not in the snapshot and pulled from the archive directly?
[18:30] <jibel> pmcgowan, any package not in the ppa is installed from vivid, I don't think sil2100 copies everytghin to the stable-snapshot
[18:31] <pmcgowan> jibel, he mentioned something yesterday about changing this but I was not clear on it
[18:31] <pmcgowan> it being controlling what came in from updates
[18:32] <jibel> pmcgowan, the only risk would have been lxc but the broken version is in proposed so it's fine to sanity check the image the respin and publish
[18:32] <pmcgowan> this must be the new verbose ci train
[18:32] <pmcgowan> jibel, great
[18:32] <jibel> pmcgowan, but I'd need a diff of the manifest to be really sure
[18:32] <pmcgowan> yep
[18:33] <jibel> or the delta once it's on system-image
[18:45] <kenvandine> dobey, where's the running page?
[18:55] <dobey> kenvandine: http://autopkgtest.ubuntu.com/running.html
[18:55] <kenvandine> dobey, thx
[18:56] <pmcgowan> jibel, when we build the new image do we still have the option to publish the last one?
[18:56] <dobey> kenvandine: the "Running" link at the top of the status pages on autopkgtest.u.c :)
[18:56] <mterry> robru, nice status verbosity changes.  Looks very verbose now, but presumably better to err on that side  :)
[18:56] <kenvandine> dobey, so clearly something's broken here :/
[18:57] <dobey> kenvandine: assuming that "in progress" does not also mean "waiting in a queue you can't see"
[18:57] <mterry> robru, tiny feature request in that regard -- endlines after each status line?
[18:57] <kenvandine> dobey, perhaps
[18:57] <sil2100> pmcgowan: yes
[18:57] <sil2100> pmcgowan: we do
[18:58] <sil2100> pmcgowan: I'm importing the new image to the rc channel now... but we can publish the previous one no problem
[18:59] <pmcgowan> ok
[19:22] <robru> mterry: yeah that's something I need to figure out. I can't put real newlines in the strings because it breaks the IRC ping. but maybe I can s/./.\n/ in the web view or something
[19:23] <robru> mterry: also I should probably take the arches off 'Successfully built' so that statuses like ^^ are simpler.
[19:24] <mterry> robru, yeah.  And/or replace "amd64" with "all" or "*" when appropriate; unless you know the packages is arch: all, it makes it seem like it only built for one arch
[19:24] <robru> mterry: that's a bit harder as the code that reports that doesn't have knowledge of the packaging, only what it sees in the ppa
[19:25] <mterry> robru, ah fair, then not worth it  :)
[19:26] <robru> mterry: oh god it takes 18 minutes to set all statuses for all silos.
[19:26] <robru> I need to parallelize this somehow
[19:35] <sil2100> pmcgowan: see my OTA-8 proposition I just sent through e-mail
[20:48] <robru> mterry: how's that: https://requests.ci-train.ubuntu.com/#/ticket/670 ?
[20:49] <mterry> robru, looks good.  Is it obvious if not all arches are built?  Like one arch has a ftbfs or something?
[20:50] <robru> mterry: I've just changed it so that if the status is the same on all arches, it hides the arch list, but if the statuses are different on different arches it'll say "Failed to build [i386] Sucessfully built [amd64 etc et]"
[20:50] <mterry> robru, awesome
[20:51] <robru> mterry: just like that ^ ;-)
[20:51] <mterry> :)
[22:14] <mterry> robru, I'm seeing that error you just emailed about on https://requests.ci-train.ubuntu.com/#/ticket/255
[22:14] <robru> mterry: looking
[22:16] <robru> mterry: sigh, there's a lot of silos (sighlos?) affected by this. I'm tempted to just declare bankruptcy on that one check, clear it from all silos...
[22:18] <robru> mterry: what I really need to do is re-engineer that check so it doesn't cache any data that can get into an inconsistent state.
[22:19] <mterry> robru, that sounds suspiciously like work
[22:19] <robru> heh
[22:20] <robru> mterry: this is just another in a long line of bugs where the train tries to save some state on disk, but then the world changes around it, and the state on disk is inconsistent with the world, and it causes problems.
[22:20] <robru> mterry: I'm trying really hard to eliminate the concept of "state" that can become "inconsistent". Checking authoritative sources directly, etc