[00:25] <Trevinho> robru: hey, do you have any clue why this is back: https://requests.ci-train.ubuntu.com/#/ticket/1419?
[00:25] <Trevinho> I think britney thinking that unity is not building in s390x, where it never got built ever
[00:25] <Trevinho> but, in xenial this thing was ignored
[00:27] <robru> Trevinho: i guess the hints need to be updated. Poke pitti about that, for now just tell qa to override it and put it in the queue anyway
[00:28] <Trevinho> robru: do you know who is in charge right now?
[00:35] <robru> Trevinho: for qa? I usually see ToyKeeper at this time, not sure officially though
[00:36] <robru> Trevinho: i think of you ping "ubuntu-qa" it gets them all
[00:36] <Trevinho> robru: ok, as we don't generally need the QA ACK, so I just need someone who can push the "publish" button.
[00:36] <robru> Trevinho: oh right, sorry.
[00:36] <ToyKeeper> If it needs QA but the automated signoff can't pass for bogus reasons, I can get it into the QA queue.  But it sounds like that's irrelevant?
[00:37] <robru> Trevinho: you should be able to publish yourself if there's no packaging changes
[00:37] <robru> ToyKeeper: sorry, yakkety only landing
[00:37] <Trevinho> let me check
[00:38] <Trevinho> well there are some pkg changes
[00:39] <Trevinho> eh, no... not allowed
[00:39] <Trevinho> I need some ubuntu dev
[00:51] <robru> Trevinho: sorry, i can't do it. My go-to guys are EOD by now. Try looking at ubuntu-core-dev for timezone appropriate people, or wait a few hours for sil2100 to wake up
[00:51] <Trevinho> robru: yeah, no worries... We can wait till tomorrow morning
[06:26] <Saviq> Mirv, hey, any idea why mir 0.22 would still be unavailable in yakkety-proposed https://launchpad.net/ubuntu/+source/mir/ ?
[06:33] <Saviq> abeato, for whatever reason mir 0.22 isn't published in proposed yet
[06:33] <Saviq> ↑↑
[06:33] <abeato> Saviq, noted, thanks
[06:34] <abeato> Mirv, we need that to build aethercast too see error ^^
[06:34] <abeato> (that = mir 0.22)
[06:44] <Saviq> ah Mirv is away, forgot, we'll need to wait for sil2100
[07:05] <Mirv>  Saviq hmm
[07:05] <Mirv> Saviq: I'm away?
[07:06] <Saviq> Mirv, aren't you? :D
[07:06] <Mirv> Saviq: no, why would I be? :D I will be in two weeks though
[07:06] <Saviq> Mirv, yeah I saw that in the calendar and didn't pay attention to dates ;)
[07:07] <Mirv> Saviq: isn't that " 0.22.1+16.04.20160516.2-0ubuntu2 " "proposed (main)" what you asked?
[07:07] <Saviq> Mirv, sure, except:
[07:07] <Saviq> # apt-cache policy libmirclient9
[07:07] <Saviq> libmirclient9:
[07:07] <Saviq>   Installed: (none)
[07:07] <Saviq>   Candidate: 0.21.0+16.04.20160330-0ubuntu3
[07:07] <Saviq>   Version table:
[07:07] <Saviq>      0.21.0+16.04.20160330-0ubuntu3 500
[07:07] <Saviq>         500 http://archive.ubuntu.com/ubuntu yakkety/main amd64 Packages
[07:07] <Saviq> and yes I have proposed enabled
[07:08] <Mirv> Saviq: but, regardless, it's not in release pocket, and it's not "really" in proposed pocket either since it has new binaries that are in https://launchpad.net/ubuntu/yakkety/+queue?queue_state=0&queue_text=mir
[07:08] <Mirv> Saviq: so yes it's in proposed but it's not in proposed
[07:08] <Mirv> (source is, binaries aren't)
[07:08] <Saviq> Mirv, right, that sounds about right
[07:08] <Mirv> Saviq: abeato: so you need to ping your friendliest member of https://launchpad.net/~ubuntu-archive/+members
[07:09]  * Saviq → #ubuntu-devel
[07:10]  * abeato follows
[07:11] <Saviq> this is going to be nasty, mir will need an archive admin for basically every release...
[07:13] <Mirv> Saviq: incorrect actually
[07:14] <Mirv> Saviq: or it will, but by trainguard. I mean, train bypasses binary new queue
[07:14] <Saviq> ah
[07:14] <Saviq> right
[07:14] <Mirv> so it's manual requirement that the publisher needs to consults archive admin, and it has always been so
[07:15] <Mirv> which is boring regardless of which way archive admins need to be troubled with it
[07:15] <Mirv> but needs to be done as long as mir continues to break its stuff instead of being stable ;)
[07:15] <Mirv> 1.0!
[07:56] <Saviq> gaaah how long's it gonna take mir to get published in proposd after being binNEWed?
[07:57]  * Saviq got tricked into trio-ifying silo 58 ;(
[07:57] <Saviq> it'll be fine, they said
[07:57] <Saviq> it's best like that, they said
[08:01] <Saviq> bollocks
[08:52] <Saviq> abeato, you can rebuild, mir got published
[08:53] <abeato> Saviq, already did, thanks :)
[08:53] <abeato> seems to be building just fine
[10:20] <Saviq> rvr, jibel, https://requests.ci-train.ubuntu.com/#/ticket/1381 is good to go... again..., any chance of putting it back on the top of the queue?
[10:20] <rvr> Saviq: Sure
[10:40] <Ads20000> Uh, I don't really know how CI Train works, but it's failed to build unity8 for the Stable Phone Overlay PPA which is a bit of a problem since I use that (though I haven't loaded unity8 successfully yet anyway). I'm guessing someone's on it (but it's not in known issues)?
[10:44] <Saviq> Ads20000, why do you say that? https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/stable-phone-overlay/+packages?field.name_filter=unity8&field.status_filter=published&field.series_filter=
[10:44] <Saviq> it's only "failed" for architectures we don't support (yet) because of missing dependencies
[10:44]  * ogra_ wonders what he means by "since i use that" ... 
[10:45] <Saviq> I suppose the overlay
[10:45] <ogra_> there are thousands of phones out there using it too :) ... (but definitely not as deb packages)
[10:45] <Ads20000> Sorry, I meant that I use the PPA on my desktop, but I haven't actually used Unity 8 yet because I couldn't log into it (though I also couldn't report a bug on it because 1 package wasn't installing (can't remember what it was))
[10:45] <ogra_> urgh
[10:46] <ogra_> dont do that
[10:46] <Ads20000> Don't do what, run the PPA? Didn't help that OMG Ubuntu recommended it, maybe I could ask him to edit the article?
[10:46] <ogra_> many of these packages are solely designed for working in image based upgrades ...
[10:47] <Ads20000> I'm confused, they're DEBs right? For using on a standard APT system?
[10:47] <ogra_> there wont be config transitions etc ... and there will be things they expect tht you dont have on a PC ... just use xenial or yakkety and the unity8 from the archive
[10:48] <Ads20000> If I may ask, what's the PPA actually for then?
[10:48] <ogra_> Ads20000, they are debs designed to be used in context of image based updates
[10:48] <ogra_> images and their deltas are built from them
[10:48]  * Mirv haz Meizu Pro 5
[10:48] <ogra_> they are usually not installed directly unless someone develops on a specific package
[10:48]  * Mirv loves it, it's awesome, really
[10:49]  * ogra_ throws envious looks at Mirv  ... mine is on the truck ... still waiting 
[10:49] <Ads20000> Hmm, ogra_ could you get someone to edit the PPA description then to tell normal users not to add it? :P
[10:49] <Mirv> I moved my /home/phablet over from Bq already too
[10:49] <Mirv> camera and hotspot didn't work at first but then I noticed my first visit to System Settings hadn't told me that there's a system upgrade. both worked after that.
[10:49] <Ads20000> But OK, I suppose that makes sense, cheers, will ppa-purge now :)
[10:50] <ogra_> Ads20000, i dont know who owns it ... perhaps sil2100 can
[10:50] <Mirv> also, default was 2G network, but now I've 4G and currently ~20Mbit/s :)
[10:50] <ogra_> crazy talk !
[10:52] <Ads20000> Also, ogra_, I'm guessing the unity8 package in Xenial/Yakkety will be more out-of-date but you're saying that's OK? I can still file bugs against it?
[10:52] <ogra_> xenial -> a little since it must be SRUed ... yakkety is on the same version as the PPA usually
[10:52] <ogra_> everything landing lands in all thee
[10:53] <Saviq> ... since yesterday ...
[10:53] <ogra_> heh, yeah
[10:53] <Saviq> so this is why overlay was really needed on xenial even to get the latest and greatest
[10:53] <Saviq> but yeah, starting today yakkety should be on par
[10:55] <Ads20000> OK cool sounds good :)
[10:55] <Ads20000> Thanks for the help :)
[10:55] <ogra_> np :)
[10:56] <jin_> jibel: ping
[10:56] <jin_> jibel: Hello, there is a request from Telegram: https://requests.ci-train.ubuntu.com/#/ticket/1441
[10:57] <jin_> jibel: need your approval on pushing this into the dashboard you have :)
[10:58] <sil2100> What's up?
[10:59] <ogra_> sil2100, Ads20000 asked if you can change the overlay PPA description to tell people oit is not for general use
[10:59] <jin_> davmor2: hey buddy
[10:59] <ogra_> he enabled it on the PC to test unity8
[10:59] <jin_> davmor2: need your team's support on this version:
[10:59] <jin_> https://drive.google.com/open?id=1y8XmPqIv-0rkp8bTXYT5Lo_8jhrdF2X2mcsymTENnjY
[11:00] <jin_> davmor2: oh sorry, this one is the correct one:
[11:00] <jin_> https://requests.ci-train.ubuntu.com/#/ticket/1441
[11:00] <jin_> davmor2: the ticket #1441 for Telegram
[11:00] <jin_> :)
[11:00] <davmor2> jin_: hey dude nice okay I'll keep an eye out for it.
[11:01] <sil2100> Ads20000, ogra_: ok, let me change the description, but I thought the name itself was obvious enough ;) It's the Stable PHONE Overlay, not desktop ;)
[11:01] <jin_> davmor2: awesome!
[11:01] <ogra_> haha, yeah
[11:03] <Ads20000> sil2100: I think the problem was that it seemed like one could use the PPA for getting the stable phone packages onto the desktop and it's implied that the existence of the PPA means that Xenial/Yakkety package aren't up-do-date enough
[11:03] <Ads20000> but a description change would fix that impression :)
[11:20] <rvr> abeato: Hi
[11:21] <rvr> abeato: Would it be possible to merge silos 29 and 5?
[11:21] <abeato> rvr, not really, one of them is not a dual(trio) landing
[11:21] <rvr> Ah, I see
[11:25] <Ads20000> Oh, Saviq, I've only just realised what you were saying. I can't install unity8 from the PPA because it depends on unity8-common which depends on unity-scopes-impl-12 which isn't in the PPA or in Yakkety
[11:26] <Saviq> Ads20000, oh you're using yakkety?
[11:28] <Ads20000> Yes, is that an issue?
[11:28] <Ads20000> (Saviq)
[11:28] <Saviq> Ads20000, no, there's just no yakkety packages in the overlay PPA at all, there's a big queue of packages in proposed that will make yakkety work for you again
[11:29] <Saviq> Ads20000, unity-plugin-scopes provides unity-scopes-impl-12 (it's virtual) - https://launchpad.net/ubuntu/+source/unity-scopes-shell
[11:29] <Saviq> Ads20000, we're in a bit of a transition period right now, you'd either need to enable proposed on your machine or wait a day or two for us to resolve all this
[11:30] <Ads20000> Saviq I have yakkety-proposed enabled
[11:31] <Saviq> Ads20000, as you can see it's waiting to build https://launchpad.net/ubuntu/+source/unity-scopes-shell/0.5.7+16.04.20160505-0ubuntu2
[11:32] <Saviq> Ads20000, so as said, we're in a bit of a transition - we're working on it - give it a day please :)
[11:33] <Ads20000> Saviq, OK that's fine, I don't understand as much as I thought about how this all works! ogra_ suggested that it's best just to use the packages in the Yakkety repo though, would you agree? :)
[11:33] <rvr> kdub: Hi. We need more info about silo 69. Can you include the changelog in the description? This is a good example: https://requests.ci-train.ubuntu.com/#/ticket/1420
[11:34] <kdub> rvr, sure
[11:34] <Saviq> Ads20000, yes, but just give us a day as we complete the transition :)
[11:36] <Ads20000> OK cool, cheers :)
[11:36] <kdub> rvr, done
[11:36] <rvr> kdub: Great, thanks
[11:37] <sil2100> No-change rebuilds for the win :|
[11:37] <sil2100> Saviq: do you know if pstolowski or anyone else is on the yakkety unity-scopes-api failure?
[11:38] <Saviq> sil2100, just pung them
[11:38] <sil2100> Saviq: big thanks!
[11:53] <rvr> bzoltan: ping
[11:54] <bzoltan> rvr:  hello there, what can I do for you?
[11:54] <rvr> bzoltan: I'm checking https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1582339
[11:54] <bzoltan> rvr:  and?
[11:54] <rvr> bzoltan: Not a big issue. But cannot reproduce in stable or rc-proposed
[11:54] <rvr> I see that the section is correctly colored
[11:55] <bzoltan> rvr:  because that bug was introduced by our staging branch
[11:55] <rvr> Ah
[11:55] <rvr> So never hit the images ?
[11:56] <t1mp> rvr: no, only in our staging
[11:56] <rvr> t1mp: Cool. Mistery solved :)
[11:57] <bzoltan> rvr: as t1mp said... we introduced a regression :) but we have fixed it before it could land.
[11:58] <rvr> bzoltan: Understood
[12:05] <kdub> rvr, with silo 69, i had to rebuild a package (not a content change, but still had to rebuild) not sure if that card has to go back to square zero or not :/
[12:05] <rvr> kdub: No problem, I will remove the new card
[12:05] <rvr> Everytime a silo is rebuilt, a new card appears
[12:06] <rvr> The prioritization in trello is manual
[12:06] <kdub> rvr, thanks
[12:24] <ChrisTownsend> trainguards: Hi!  Are britney runs known to be taking a very loooong time right now?  I did a rebuild yesteday due to the triple landings and the britney run is still going: https://requests.ci-train.ubuntu.com/#/ticket/1425
[12:28] <kdub> ChrisTownsend, I noted that they were taking longer than normal yesterday as well
[12:29] <ChrisTownsend> kdub: Ok, good to know I'm not the only one.  But my run has been going on for almost 14 hours or so.
[12:29] <Mirv> ChrisTownsend: I'm not 100% sure. there has been a huge queue for yakkety http://autopkgtest.ubuntu.com/running.shtml but I don't see yours there, plus the ppc64el libertine at https://requests.ci-train.ubuntu.com/static/britney/xenial/landing-031/excuses.html seems suspicious too. our only option if somethings gets truly stuck is to ping pitti on #ubuntu-devel
[12:29] <kdub> ChrisTownsend, yeah, it took most of the day to sign off on my silo
[12:30] <ChrisTownsend> Mirv: Ok, I'll follow up w/ pitti.  Thanks
[12:30] <ChrisTownsend> kdub: ok
[12:43] <Mirv> sil2100: jibel: I upgraded my turbo to rc-proposed, now SIM unlock does not prompt when booting the phone, I need to select it from menu. sounds familiar, and under which such a bug should be filed?
[12:50] <jibel> Mirv, you mean there is no SIM unlock prompt or it doesn't show up when you press the unlock SIM button in the indicator
[12:50] <jibel> ?
[12:50] <jibel> there is a bug for both IIRC
[12:51] <jibel> davmor2, ^ do you know?
[12:51] <pstolowski> sil2100, hey, since apparently we should do triple landings now, can enable & build for yakety in silo 47 without starting from scratch?
[12:52] <davmor2> Mirv: there is a bug for it I think don't know if it is specific to turbo let me have a dig
[12:55] <davmor2> Mirv: meh I can't put my hand on it right now I'll dig it out later
[12:57] <Mirv> jibel: there's no SIM unlock prompt during bootup, but there is if I press the button from indicator
[12:57] <Mirv> davmor2: ok, that's a regression from the OTA-10.2 my turbo booted with before upgrading
[12:58] <jibel> Mirv, I'm pretty sure I saw a bug report but cannot find it
[12:59] <davmor2> jibel: yeah there is but I can't find it either, I'm not sure if it is device specific so filed there or against ofono/system-settings/network indicator
[13:01] <Saviq> sil2100, can you please recycle the regression here https://requests.ci-train.ubuntu.com/static/britney/vivid/landing-058/excuses.html thanks
[13:01] <rvr> tsdgeos: ping
[13:02] <Saviq> mterry, oh you're here now, too, can you recycle ↑ please
[13:02]  * mterry dusts off his recycling fingers
[13:03] <mterry> done
[13:03] <tsdgeos> rvr: hi
[13:04] <rvr> tsdgeos: Hi
[13:04] <rvr> tsdgeos: I'm testing #1421293
[13:05] <rvr> tsdgeos: Can you tell me whether this is right? https://trello-attachments.s3.amazonaws.com/53fc6641728df958a48bfbe1/573c2103599129a715a9863d/322d159220c9ee3f8f9f0d87eb507142/screenshot20160520_140023336.png
[13:06] <rvr> tsdgeos: Well, that's an screenshot with arale
[13:06] <tsdgeos> rvr: not sure what i'm looking at :D
[13:06] <rvr> tsdgeos: I'm trying to understand what you did :D https://launchpadlibrarian.net/197431959/icon.png
[13:07] <tsdgeos> rvr: it's with 25px and 50px as grid unity
[13:07] <tsdgeos> -y
[13:07] <tsdgeos> but i am not sure the bug was actually fixed
[13:07] <tsdgeos> ltinkl: ping
[13:08] <tsdgeos> ltinkl: do you remember the branch https://code.launchpad.net/~lukas-kde/ubuntu-ui-toolkit/staging-fix-icon-svg-image-loading ? it was marked as fixing https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1421293 but i remember some discussion about it not really fixing the bug?
[13:11] <ltinkl> tsdgeos, it should be fixed
[13:11] <ltinkl> tsdgeos, I used your testcase
[13:11] <Mirv> jibel: davmor2: sil2100: I couldn't find a bug, so I filed bug #1584049 (not sure to which package it would suite best)
[13:14] <davmor2> Mirv: I thought this was going to be your stable phone so why take it off stable????
[13:15] <tsdgeos> rvr: ltinkl: ok let me try to remember what this was about :D
[13:15] <Mirv> davmor2: because I have strong belief that OTA-11 is near ready :) I already changed the channel back to stable to stay on this particular image until OTA-11 is ready
[13:15] <Mirv> davmor2: and because OTA-10 had the Mir performance bug(s)
[13:15] <davmor2> Mirv: so you lied then ;)
[13:15] <rvr> tsdgeos: lol, ok
[13:16] <Mirv> davmor2: if I said something about staying on stable channel yes I lied :) too tempting...
[13:17] <davmor2> Mirv: you didn't say stable channel you said this is my new stable phone so I can use krillin for testing :D
[13:19]  * ogra_ finds it funny that the "gold" actually doesnt look so "gold" ... it is more somewhere between champagne and copper i think
[13:20] <Mirv> ogra_: indeed, which is a good thing. bzoltan and zsombi didn't order it since they tought it's too gold, but it's actually quite mute and mostly gray with some tints as you mentioned
[13:20] <ogra_> yeah
[13:23] <tsdgeos> rvr: yeah the bug is not fixed
[13:24] <rvr> tsdgeos: :-(
[13:24] <tsdgeos> rvr: the bug is basically that the first image looks "correct" at any GRID_UNIT_PX value
[13:24] <tsdgeos> while the second does not
[13:24] <tsdgeos> you need to add extra code (i.e. the third) for it to look correct
[13:25] <Mirv> davmor2: I will use the krillin to test any offered fix for that bug :)
[13:25] <Mirv> my turbo is back to ro mode after editing the channel.ini back to stable
[13:26] <tsdgeos> rvr: this is with different GRID_UNIT_PX for me http://i.imgur.com/EBb8PEU.png
[13:26] <davmor2> Mirv: why edit channel.ini all you had to do was system-image-cli --switch <channel_url>
[13:26] <rvr> tsdgeos: So fixed, it should like the third window, right?
[13:27] <tsdgeos> rvr: the second image should look like the third in all GRID_UNIT_PX
[13:27] <tsdgeos> and not only in the right one
[13:27] <rvr> tsdgeos: Ack
[13:28] <tsdgeos> t1mp: i edited the bug, hope it's easier to understand now
[13:29] <rvr> bzoltan: So, bug #1421293 is not fixed
[13:31] <jhodapp> sil2100, ping
[13:32] <Mirv> davmor2: I didn't remember that one and this one also easy, one line change, back to ro mode, check for updates in system settings
[13:38] <dobey> go go gadget mir already
[13:39] <Saviq> sil2100, jibel, https://requests.ci-train.ubuntu.com/#/ticket/1442 - this can probably skip QA and will unblock some things in yakkety
[13:42] <dobey> Saviq: how will that unblock things?
[13:42] <Saviq> dobey, there's things waiting to build in proposed because of it FTBFSing
[13:42] <Saviq> https://launchpad.net/ubuntu/+source/unity-scopes-api/1.0.5+16.04.20160413.1-0ubuntu2
[13:45] <dobey> the big thing still seems to be mir
[13:45] <Saviq> seb128, since I excluded you earlier today, can I ask you to ♻ https://requests.ci-train.ubuntu.com/static/britney/vivid/landing-058/excuses.html
[13:45] <Saviq> dobey, mir's in proposed already
[13:46] <dobey> Saviq: yes, but lots of things seem to be uninstallable
[13:47] <seb128> Saviq, done
[13:47] <Saviq> seb128, thanks
[13:47] <Saviq> dobey, yeah, and part of everything being uninstallable was unity-scopes-api not building
[13:47] <Saviq> now it will so we'll just get one small step further
[13:48] <bzoltan> t1mp: or better here
[13:48] <t1mp> ah, right
[13:48] <bzoltan> t1mp:  yes rvr I mean
[13:50] <t1mp> rvr, tsdgeos: is https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1421293 not fixed?
[13:50] <t1mp> I reviewed a branch with a test case that fixed it, let me see
[13:50] <t1mp> well the two attached branches are the same, just different merge target
[13:51] <tsdgeos> t1mp: i think you may have not understood what the bug was about
[13:51] <t1mp> it adds a test case in tst_icons that passes, and visual inspection showed the correct results too
[13:51] <tsdgeos> since the bug is not against svg
[13:51] <tsdgeos> and the branches where for svg improvements
[13:51] <tsdgeos> as far as i remember
[13:52] <t1mp> hmm, right, the branch name mentions svg
[13:52] <t1mp> but the test case is for png, and I checked that
[13:52] <t1mp> I didn't think of svg
[13:52] <t1mp> hmm
[13:52] <ChrisTownsend> ubuntu-qa: Hi!  Could we keep the current place on the queue for https://requests.ci-train.ubuntu.com/#/ticket/1425 since I had to rebuild for the triple landing?
[13:52] <t1mp> from the bug report: "For the SVG the width grows as the units.gu grow, but for the JPEG it does not and one has to manually add code to maitain the aspect ratio."
[13:53] <tsdgeos> t1mp: see the updated description
[13:53] <t1mp> so, the test verifies that the aspect ration is maintained, right?
[13:53] <tsdgeos> yes, i'm not complaining about sVG doing the right thing
[13:53] <tsdgeos> i'm complaining JPEG/PNG doesn't
[13:53] <tsdgeos> t1mp: which test?
[13:53] <t1mp> see l. 227 on https://code.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-toolkit/trunk-fix-icon-svg-image-loading/+merge/286585
[13:54] <t1mp> and the test function directly under it
[13:54] <davmor2> ChrisTownsend: yeah don't worry we are just deleting new tickets if they are dupes
[13:54] <ChrisTownsend> davmor2: Ok, cool, thanks
[13:54] <Mirv> ogra_: can you play back videos you take with camera? for me it says it can't and also all thumbnails are just placeholder image (both videos I took with Bq and new ones)
[13:55] <ogra_> havent tried
[13:55] <tsdgeos> t1mp: that test is broken, needs to be testing for different grid units too
[13:55] <tsdgeos> incidentally on the default gu value on the desktop it works
[13:55] <tsdgeos> i've no idea why
[13:57] <Mirv> it might be this  .cache/gstreamer-1.0/registry.arm.bin problem I read somewhere about
[13:58] <t1mp> tsdgeos: http://i.imgur.com/EBb8PEU.png indeed looks wrong
[13:58] <ogra_> Mirv, works fine
[13:58] <jibel> ChrisTownsend, sure
[13:58] <t1mp> tsdgeos: okay, so then the bug is not fixed
[13:58] <bzoltan> rvr: did I miss something?
[13:58] <tsdgeos> t1mp: yeah :/
[13:58] <t1mp> ltinkl: will you take the bug again?
[13:58] <rvr> bzoltan: tsdgeos confirms that the bug is not fixed
[13:58] <Mirv> ogra_: ok, good. I think it's something they've struggled with after OTA-10
[13:59] <t1mp> bzoltan: it appears that the bug was only fixed for the specific GU setting that was used for testing..
[13:59] <bzoltan> rvr:  would you please not fail the silo yet?
[13:59] <tsdgeos> rvr: yeah failing the silo for that makes no sense
[13:59] <rvr> bzoltan: I tested everything else and is good
[13:59] <t1mp> rvr, bzoltan: that bug is only low priority, we thought it was nice that is was fixed as a side-effect of other fixes, but I don't think we need to fail a silo for that. Just remove the bug
[13:59] <ogra_> Mirv, well, i'm on 10.2
[13:59] <jibel> Saviq, +1 to skip QA
[13:59] <tsdgeos> rvr: i mean the branch was not fixing that really, was fixing something else and i guess my bad description of the bug made people think it was actually fixed
[13:59] <bzoltan> rvr: let's keep the bug open and pass the silo
[14:00] <jibel> Saviq, (for silo 39)
[14:00] <Saviq> yup
[14:01] <rvr> tsdgeos: But if the test is wrong, and the code doesn't fix the problem...
[14:01] <rvr> Remove the branch
[14:01] <bzoltan> rvr: it is not a branch
[14:01] <tsdgeos> rvr: the code does fix the problem
[14:01] <tsdgeos> just not *this* problem
[14:01] <tsdgeos> it fixes the problem it wanted to fix
[14:01] <rvr> Hmm
[14:01] <t1mp> rvr: the branch fixed another, critical, bug. But it did not fix this low-priority bug that we thought it also fixed as a side-effect
[14:02] <rvr> I see
[14:02] <rvr> Ok, then remove the bug from the list and I'll aprove it
[14:02] <bzoltan> rvr:  and regardless of anything... the silo does not bring regression and it does fix OTA bugs... + the issue in hand does fix one case... multiply MRs can fix the same bug.
[14:03] <bzoltan> rvr: but that MR does fix one case of that bug... the way to handle it is to reopen the bug. Would not be the first case that the same bug is fixed multply time.
[14:04] <bzoltan> rvr: tsdgeos: t1mp: There is no "Fixes partially LP: #123456" syntax ... so fixing a corner case requires the same syntax in the changelogs
[14:04] <bzoltan> good job ubot5
[14:04] <rvr> lol
[14:05] <davmor2> Mirv: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1583944
[14:05] <t1mp> bzoltan: it does not properly fix this bug, so we can remove that line from the changelog and keep the bug open
[14:05] <oSoMoN> rvr, all merge requests approved for https://trello.com/c/b1JNG7NQ/3239-1387-ubuntu-landing-053-webbrowser-app-osomon
[14:05] <rvr> oSoMoN: Thanks
[14:05] <rvr> bzoltan: Approved
[14:05] <bzoltan> rvr: thanks
[14:06] <t1mp> ltinkl: do you want to take another shot at fixing that bug?
[14:06] <bzoltan> t1mp: let's let the CI machine now mark that bug and reopen... I do not remove changelog entry from the changelog without removing the code what it refers to
[14:07] <t1mp> okay
[14:07] <bzoltan> t1mp: pushing a new rev of the landing branch would hold back like 24 hours
[14:07] <ltinkl> t1mp, not really, if I don't have to :p
[14:07] <t1mp> ltinkl: who decides whether you have to? ;)
[14:07] <t1mp> ok, I'll keep it as unassigned for now then.
[14:12] <rvr> ChrisTownsend: Hi!
[14:12] <ChrisTownsend> rvr: Hey!
[14:13] <rvr> ChrisTownsend: Can you add the changelog to the libertine silo description? Like this one: https://requests.ci-train.ubuntu.com/#/ticket/1420
[14:13] <ChrisTownsend> rvr: Sure!  Is that something I should every time from now on?
[14:14] <rvr> ChrisTownsend: Yes, please. It is easier for us.
[14:14] <ChrisTownsend> rvr: Sure, no problem.
[14:17] <ChrisTownsend> rvr: Ok, updated the ticket.
[14:17] <ChrisTownsend> rvr: Let me know if that is what you are looking for.
[14:18] <rvr> ChrisTownsend: Yeah, that's fine. Thanks!
[14:18] <ChrisTownsend> rvr: Ok, cool
[15:18] <oSoMoN> sil2100, Mirv: can one of you guys please publish silo 53 on my behalf? it’s got packaging changes (which were approved by kenvandine)
[15:25] <sil2100> oSoMoN: looking!
[15:27] <sil2100> oSoMoN: done!
[15:29] <oSoMoN> sil2100, thanks!
[15:33] <oSoMoN> davmor2, I see that you moved the trello card for silo 53 to under testing, you can skip that and move it to passed, as it was validated by jibel earlier this morning and it is currently being published
[15:33] <jibel> davmor2, it's done
[15:34] <davmor2> jibel: shocking ;)
[15:36] <davmor2> oSoMoN: I did stumble across something fun in that silo, on frieza if you open system-indicator select desktop mode, then open the browser if you highlight one of the link scroll up and down the page it then triggers the mouse over dialogue at the bottom of the page with the url link in it :)
[15:38] <oSoMoN> davmor2, isn’t that the expected behaviour? if the mouse cursor is over a hyperlink, its target URL will be displayed in the overlay
[15:39] <davmor2> oSoMoN: there is no mouse cursor long press on a link and then hit cancel, then scroll up and down, ie long press the shop link, cancel that dialogue, then scroll up and down and you get the mouse hover dialogue
[15:41] <oSoMoN> davmor2, ah, got it! I guess this is still considered as a mouseover event by the web engine
[15:41] <oSoMoN> even though there is no actual cursor visible on screen
[15:42] <davmor2> oSoMoN: that's my assumption but it only happen after the scroll which was the thing that threw me :)
[15:42] <oSoMoN> davmor2, not sure that would qualify as a bug, more like a "weird behaviour", but feel free to file a bug against webbrowser-app anyway
[15:43] <davmor2> oSoMoN: I have no issue with it just a fun thing you'll note at no time did I say bug just weird :)
[16:00] <oSoMoN> davmor2, fair enough :)
[16:37] <Mirv> ogra_: jibel: davmor2: I managed to fix my video thumbnailing problem by removing the registry in .cache/gstreamer-1.0/ a couple of times (and then removing unity-thumbnailer "failures" database to get thumbnails back), but I wouldn't say the problem, discussed on some mailing list (search your mail for gstreamer registry), would be completely fixed for OTA-10 -> OTA-11 upgraders and might cause seriou
[16:37] <Mirv> s trouble for at least turbo users (since it seems it affects the fastest device the most)
[16:38] <Mirv> davmor2: s/my video thumbnailing problem/my video thumbnailing and playback of any video problem/
[16:39] <ogra_> thumbnails behave fine here
[16:44] <Mirv> ogra_: it might be because of my data transfer from Bq, hopefully no-one will encounter it then in normal situation anymore. although you also haven't upgraded to rc-proposed.
[16:45] <ogra_> yeah, i usually hand-copy my data to not carry over unwanted dot-dirs and caches
[16:45] <ogra_> a lot more initial effort, but i can be sure my device is clean
[16:46] <Mirv> maybe popey's buds should be updated to --exclude .cache/gstreamer-1.0 :) (well, really, without smiley too)
[16:49] <Mirv> davmor2: bug #1583944 seems not related to my bug #1584049 since the unlocking from indicator works fine, while it does not according to the bug linked from the former
[16:51] <davmor2> hmmm Mirv so I have sim pin unlock on mine at least on initial boot let me try a reboot
[16:52] <Mirv> I have now booted the rc-proposed several times and it always goes to the phone unlock screen without showing SIM unlock screen. but there's that 1580908 filed indeed that my bug was made duplicate of now.
[17:24] <bzoltan> Mirv:  would you help me to publish and merge the silo19 please?
[17:25] <bzoltan> Mirv:  I am sure you can do it on your huuuuuge screened Pro5 ...
[17:26] <Mirv> bzoltan: well if you ask _that_ nicely :) yes it's huge!
[17:26] <bzoltan> Mirv: i wonder how to get my dirty hand on one of them
[17:27] <Mirv> bzoltan: I do manual triple landing as discussed on mailing lists earlier today
[17:27] <bzoltan> Mirv:  OK
[17:29] <robru> Mirv: i forgot to mention, you must force merge after manual triple, it won't auto merge because it will expect xenial package in xenial archive, not overlay.
[17:29] <Mirv> robru: oh, ok, thanks!
[17:30] <Mirv> bzoltan: so done as you can see vivid+xenial https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/stable-phone-overlay/+packages?batch=75&memo=300&start=300 and yakkety (building) at bottom of https://lists.canonical.com/archives/yakkety-changes/2016-May/thread.html
[17:31] <bzoltan> Mirv:  thank you!
[17:32] <Mirv> davmor2: I'll keep your hilights on another channel untouched so I remember them on another day :)
[17:32] <davmor2> hahahaha
[18:26] <dobey> anyone know anything about http://pastebin.ubuntu.com/16530018/ in yakkety?
[19:20] <dobey> mcfly?
[19:24] <robru> dobey: no idea
[19:29] <dobey> hmm, i wish the excuses page would show 'Queued' instead of 'Test In Progress' for tests that are queued but not yet running
[19:33] <robru> dobey: file a bug against britney
[20:15] <dobey> haha
[20:15] <dobey> well i guess one 'good' thing about the yakkety migration fiasco is now all the autopkgtests are flagged as 'always failed'
[20:30] <Saviq> ;)