[01:00] <fginther> bfiller, in case you didn't already see this: http://s-jenkins.ubuntu-ci:8080/view/click/job/gallery-app-click/263/artifact/out/com.ubuntu.gallery_2.9.1.1205_armhf.click
[01:00] <fginther> bfiller, from http://s-jenkins.ubuntu-ci:8080/view/click/job/gallery-app-click/263/
[02:52] <bfiller> fginther: thanks
[06:18] <bzoltan_> robru:  do you know who should I ask if need help to make jenkins doing its job instead of blocking the integration?
[06:19] <robru> bzoltan_: which Jenkins? You need cihelp for anything other than ci-train.u.c
[06:20] <robru> bzoltan_: oh you mean the mp reviews? Yeah you need cihelp for that
[06:21] <robru> bzoltan_: i would recommend disabling that for train projects since it has no ability to handle deps across multiple MPs
[06:25] <bzoltan_> robru:  good point
[06:37] <bzoltan_> robru:  is there a separare channel for that or it should be a highlight here?
[06:38] <robru> bzoltan_: this is the spot, i don't know if any ci people are around just yet though. Maybe wait a few hours
[06:42] <bzoltan_> robru: OK, I will ping fginther or elopio or anybody who hears the cihelp call :)
[06:43] <robru> bzoltan_: Francis is us time, that might be a wait. Ev is uk, should be sooner
[06:43] <thomi> robru: ev is us too. psivaa is UK
[06:44] <robru> Ooh right
[06:44] <bzoltan_> robru:  thomi: would be nice to have a GMT+N (N>=1) cihelper
[06:44] <robru> I forgot he moved to Houston
[06:44] <robru> Austin
[06:44] <thomi> bzoltan_: psivaa
[06:44] <robru> That place we just were ;-)
[07:46] <ogra_> hmpf
[07:46] <ogra_> http://i.imgur.com/B1bX5SO.png
[07:46] <ogra_> i assume this shouldnt actually be possible :P
[07:48] <jibel> I saw it once and some else reported it too (don't remember who though)
[08:06] <psivaa> bzoltan_: hey
[08:06] <psivaa> Which is the MP being blocked by jenkins?
[08:06] <bzoltan_> psivaa:  good morning, we have all kinds of problems with Jenkins... most of our MRs do not pass jenkins
[08:07] <bzoltan_> psivaa:  almost all of them https://code.launchpad.net/ubuntu-ui-toolkit/+activereviews
[08:07] <psivaa> bzoltan_: morning, let me take a look
[08:07] <bzoltan_> psivaa:  this one I would like to land most https://code.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-toolkit/qtmacros/+merge/259477
[08:09]  * zbenjamin looks
[08:10] <zbenjamin> psivaa: seems some tests (always different ones) can not get a Mir connection
[08:12] <psivaa> bzoltan_: zbenjamin: yea as you said they are actual test failures, (albeit different ones) not related to the infrastructure
[08:13] <psivaa> so we'd not be able to do anything to fix them
[08:13] <psivaa> but if you want them the whole test to be disabled, we could do that
[08:13] <zbenjamin> psivaa: i wonder how can not getting a mir connection be a test failure?
[08:14] <zbenjamin> this one for example https://jenkins.qa.ubuntu.com/job/generic-deb-autopilot-runner-vivid-mako/2765/testReport/junit/ubuntuuitoolkit.tests.gallery.test_textinput/WriteAndClearTextInputTestCase/test_clear_textfield_must_remove_text_Nexus_4_standard_textfield_/
[08:15] <zbenjamin> psivaa: especially this MR fails always with that error, but always in different tests
[08:17] <zbenjamin> psivaa: or am i missing something?
[08:17] <psivaa> zbenjamin:  if that (not getting mir connection) is causing an autopilot test to fail and the process depends on that test to pass for the MP to be merged.
[08:17] <psivaa> zbenjamin: i dont know the depth of how this *test works and we in CI wont be able to debug that
[08:18] <zbenjamin> :(
[08:18] <psivaa> zbenjamin: the process depended on each of the tests to pass so that has to be debugged by someone with in-depth knowledge of the tests
[08:19] <psivaa> zbenjamin: sorry if I coming across straight, :), still haviing my first coffee
[08:19] <psivaa> zbenjamin: do you by chance run the tests locally ?
[08:19] <psivaa> on a mako?
[08:19] <zbenjamin> bzoltan_: ^^ there is a script for that right?
[08:20] <ogra_> bzoltan_, oh, just FYI, sil2100 manages the metapackages nowadays (i saw the discussion in the other channel)
[08:21] <bzoltan_> ogra_:  Good to know. Thank you.
[08:21] <bzoltan_> zbenjamin:  the test plan script can run UITK AP tests of course
[08:22] <zbenjamin> bzoltan_: the script also might need to adapt to the new build structure?
[08:23] <bzoltan_> zbenjamin: what new build structre? Why?
[08:23] <bzoltan_> psivaa:  sorry I missed to understand the Mir display issue... how is that not an infrastructure problem?
[08:24] <bzoltan_> psivaa:  zbenjamin: I am running dozens of times the UITK AP tests locally on krillin and never seen that failure.
[08:24] <zbenjamin> bzoltan_: because the plugins are now compiled into a folder named "qml" and not "modules"
[08:24] <zbenjamin> bzoltan_: thats a result from using the qt macros
[08:25] <bzoltan_> zbenjamin: so? how does that effect the test plan?
[08:26] <zbenjamin> bzoltan_: well i assumed its using the push_to_phone script. But maybe not :D
[08:26] <bzoltan_> zbenjamin:  absolutely not
[08:26] <psivaa> bzoltan_: sorry, what should we in the infrastructure, do to fix 'Mir display issue'
[08:26] <zbenjamin> bzoltan_: ok then just forget what i said :D
[08:26] <psivaa> i'm putting this in quote is because that's all what i understand :)
[08:27] <bzoltan_> psivaa:  no idea ... I do not see it locally
[08:27] <psivaa> bzoltan_: also do you run this test on Mako?
[08:27] <bzoltan_> psivaa:  no
[08:27] <bzoltan_> psivaa: we work on OTA updates what target bq devices
[08:28] <psivaa> bzoltan_: ok, so running these tests in mako do not make much sense
[08:28] <psivaa> ?
[08:28] <bzoltan_> psivaa: sense it might make ... but it would not be enough to pass the QA validation
[08:29] <psivaa> bzoltan_: if that's the case, we'd need to get an agreement if
[08:29] <psivaa> 1. we should disable the tests on Mako
[08:29] <psivaa> 2. Fix the tests for mako even though the target is BQ
[08:30] <psivaa> 3. Change the devices to krillin
[08:30] <bzoltan_> psivaa: 3.
[08:30] <bzoltan_> psivaa:  testing changes on mako has value ... but blocking landings on krillin because of mako does not sound good to me
[08:31] <psivaa> I'd need to discuss 3 with the team, but especially whilst we're in the process of moving away from a single entity running all the product/ project tests towards each team, i'm not sure if that will be done in time
[08:31] <bzoltan_> psivaa:  do you think the same tests would pass on krillin?
[08:31] <psivaa> bzoltan_: I thought that's what you said above :)
[08:31] <psivaa> ' I am running dozens of times the UITK AP tests locally on krillin and never seen that failure.'
[08:32] <bzoltan_> psivaa:  I strongly doubt that the only difference between the Jenkins testing is the device type :)
[08:32] <psivaa> bzoltan_: but that's all we in CI have control over :)
[08:32] <bzoltan_> psivaa:  but I find it very very strange that the CI infra is not testing on the primary target device
[08:33] <bzoltan_> psivaa:  what would it take to replace those makos with krillins?
[08:34] <psivaa> bzoltan_: (whilst running the risk of discussing something which I do not think will happen soon, due to change of focus as i said above)
[08:34] <psivaa> we'd need more krillins
[08:34] <bzoltan_> psivaa:  anyhow... right now running AP tests on UITK MRs does not make much sense as I am doing super massive 4 time full AP tests before landings.
[08:35] <bzoltan_> psivaa:  The UITK test plan covers more AP test than any QA/CI process ...
[08:35] <psivaa> bzoltan_: ok, shall we disable that then?
[08:35] <bzoltan_> psivaa:  we run _all_ available AP tests ...
[08:36] <bzoltan_> psivaa: temporally I would do that
[08:36] <bzoltan_> zbenjamin: ^ are you OK with that?
[08:37] <zbenjamin> bzoltan_: psivaa: +1
[08:37] <psivaa> bzoltan_: zbenjamin: ok, i'll work on it then
[08:37] <bzoltan_> psivaa:  Thank you a bunch!
[08:37] <zbenjamin> \o/
[08:37] <psivaa> zbenjamin: bzoltan_: thanks for the info
[08:39] <bzoltan_> psivaa: at the same time I will enforce the QA process of the UITK project. It means we will do more tests on our staging branch.
[08:40] <psivaa> bzoltan_: that sounds great
[08:51] <popey> sil2100: on todays image on krillin and arale, neither of them will stop buzzing after a notification...
[08:51] <popey> having to restart both phones to shut them up
[08:52] <sil2100> popey: oh, hm, let me check the commitlog on what landed
[08:52] <popey> brb
[08:53] <sil2100> popey: yeah, looks like we had unity-notifications landing
[08:53] <sil2100> "Make unity8 notifications server more robust against misbehaving clients"
[08:54]  * sil2100 waits for pete-woods
[08:55] <popey> ok
[08:55] <popey> want a bug filed?
[08:57] <sil2100> popey: yeah, please, might use that if I want to revert it
[08:57] <sil2100> Thanks!
[08:57] <popey> ok will do
[09:05] <jibel> popey, after a calendar notification or any notification?
[09:08] <oSoMoN> trainguards: hey, I need to reconfigure silo 16 to target both wily and vivid overlay, can someone do that for me please?
[09:17] <sil2100> oSoMoN: you mean, you want it to be a dual-landing silo, right?
[09:17] <oSoMoN> sil2100, yes
[09:17] <psivaa> bzoltan_: just one more question, do you only want the AP tests to be disabled in mako or even in amd64 as well?
[09:17] <sil2100> oSoMoN: on it
[09:18] <oSoMoN> thakns
[09:18] <oSoMoN> thanks
[09:18] <sil2100> oSoMoN: done!
[09:19] <oSoMoN> sil2100, thanks
[09:19] <popey> jibel: calender here
[09:25] <popey> sil2100: jibel bug 1470031
[09:26] <mzanetti> sil2100, hey, did you have a chance to look into the wily builds?
[09:26] <mzanetti> still failing it seems
[09:27] <jibel> popey, did you file a bug? I saw that last week but don't remember if it was with or without the silo
[09:27] <popey> see above :)
[09:27] <popey> I am not on any silos, unmodified largely.
[09:28] <jibel> popey, heh sorry :)
[09:34] <bzoltan_> psivaa:  on mako as start ... if I start to see green Jenkins jobs then the amd64 can stay
[09:34] <sil2100> mzanetti: I think for this one we'll need some LP/builder specialists
[09:34] <psivaa> bzoltan_: ack, that's what i've done, MP waiting for approval. thanks
[09:35] <sil2100> cjwatson, wgrant: could you help us with something? We have https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-017 that seems to fail to build basically all its packages stating that dependencies couldn't be met
[09:35] <sil2100> While the new packages don't even change their dependencies
[09:36] <psivaa> bzoltan_: zbenjamin: https://code.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-toolkit/qtmacros/+merge/259477 is now green ( from a manual run skipping mako tests)
[09:37] <jibel> sil2100, I confirm popey's bug, very likey silo 18 that landed yesterday
[09:37] <bzoltan_> psivaa: \o/
[09:37] <sil2100> jibel: could you try reverting qtdeclarative5-unity-notifications-plugin to 0.1.2+15.04.20141104-0ubuntu1 ?
[09:37] <jibel> sil2100, on it
[09:38] <cjwatson> sil2100: Looking
[09:38] <cjwatson> Yikes
[09:38] <cjwatson> sbuild: warning: can't parse dependency g++-4.9:native
[09:39] <cjwatson> So there are two possible fixes for this
[09:39] <cjwatson> One is a thing I'm working on today anyway, to have sbuild use apt-get build-dep - it's non-trivial because it requires rearranging how we detect dep-waits
[09:40] <cjwatson> The other is to have sbuild strip the qualifier there, which I kind of thought it already did
[09:40] <cjwatson> Let me have a look at why the latter isn't working
[09:40] <sil2100> cjwatson: thanks! hah, actually with the new output I somehow missed this particular error
[09:40] <sil2100> The output is too clean for me and it confuses me
[09:42] <cjwatson> I wonder if precise's libdpkg-perl is too old for this
[09:53] <cjwatson> wgrant: Right, so precise's dpkg is lacking https://anonscm.debian.org/cgit/dpkg/dpkg.git/commit/scripts/Dpkg/Deps.pm?id=40d51dc36b2375679a00ed9ff64ee017dc78b0a9, possibly other related things.  I propose we hack the precise sbuild backport to strip off architecture qualifiers before deps_parse sees them.  Any objections?
[09:53] <cjwatson> We wouldn't have seen this in PPA testing, of course.
[09:53] <cjwatson> (because trusty)
[09:55] <wgrant> cjwatson: Argh.
[09:55] <wgrant> But sounds like the best solution.
[09:55] <jibel> sil2100, I confirm that it's a regression introduced by silo 18
[09:56] <sil2100> jibel: ok, best way is to soft-revert and poke pete for a real fix
[09:56] <sil2100> Let me prepare everything, would need to revert it for both archives
[09:57]  * rvr tested silo 18, not happy :-/
[09:59] <rvr> popey: Good catch
[09:59] <popey> np
[10:01] <jibel> sil2100, can you rebuild an image once it is reverted?
[10:01] <sil2100> Sure
[10:01] <jibel> thanks
[10:10] <cjwatson> mzanetti: I think I have a patch, just setting up a suitable test environment
[10:10] <sil2100> cjwatson: thanks \o/
[10:12] <mzanetti> cjwatson, awesome! thanks a lot!
[10:23] <sil2100> jibel: the revert is building in the overlay and archive, will be tracking once it's done and kick an image
[11:10] <sil2100> jibel: the image is building
[11:36] <cjwatson> wgrant: Could you review http://paste.ubuntu.com/11798585/, please?
[11:36] <cjwatson> Seems to work here, tested with unity-api from that silo.
[11:39] <cjwatson> The regex is basically the start of the one from Dpkg::Deps.
[11:42] <wgrant> cjwatson: Looks sane to me, as long as it also works.
[11:43] <cjwatson> Thanks.
[12:05] <popey> sil2100: do we not have an image bot anymore?
[12:06] <sil2100> popey: it's not working right now
[12:06] <ogra_> well, it could tell you about old images ...
[12:06] <ogra_> but thats about it ... the re-swetting of the image versions caused quite some havoc i havent found time to fix
[12:10] <cjwatson> mzanetti,sil2100: https://rt.admin.canonical.com/Ticket/Display.html?id=82496, shouldn't be long now
[12:11] <sil2100> cjwatson: thanks for that!
[12:12] <mzanetti> great :)
[12:17] <cjwatson> mzanetti: Um, I didn't say you could rebuild yet :)
[12:17] <mzanetti> cjwatson, sorry, I triggered the rebuild before your last messages
[12:18] <cjwatson> mzanetti: Also, don't rebuild it like that.
[12:18] <cjwatson> mzanetti: Unless you were actually making source changes.
[12:18] <mzanetti> didn't know I get those nice status updates so I thought I just retry every couple of hours
[12:18] <mzanetti> cjwatson, how should I build then?
[12:18] <mzanetti> or rather: what exactly is the difference?
[12:19] <cjwatson> mzanetti: When it's upgraded, I'll retry it for you in the PPA, without needing a new source upload (which is what the "Build" button in the train amounts to)
[12:19] <mzanetti> ohh. that makes sense
[12:19] <mzanetti> ack
[13:08] <brendand> sil2100, when was the last image built?
[13:08] <brendand> sil2100, for vivid
[13:08] <brendand> actually let me check the image server
[13:09] <brendand> this morning
[13:10] <jibel> brendand, there was one this morning and another is currently buildiong
[13:10] <brendand> jibel, how do you find if one is in progress? my connection is not reliable so i often miss the pings here
[13:11] <jibel> brendand, because sil2100 said so 2 hours ago
[13:11] <jibel> brendand, otherwise https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/vivid/ubuntu-touch/
[13:12] <jibel> you can trust this more than what I say :)
[13:30] <sil2100> I was building an image in the morning, it should be in the channel
[13:43] <psivaa> bzoltan_: the change to disable the touch tests on UITK has landed in the infra. if you re-run any failed MP, they should pass
[13:48] <cjwatson> mzanetti,sil2100: That's all fixed for you now, PPA builds retried, and ci-train is doing a watch-only build
[13:51] <sil2100> \o/
[13:53] <mzanetti> cjwatson, thank!
[13:53] <mzanetti> +s
[13:54] <cjwatson> mzanetti: also, it may be relevant to your interests that :native now works in recipes, as of a day or two ago
[13:54] <mzanetti> cjwatson, that is interesting indeed. thanks for that too :)
[13:54] <cjwatson> no more pbuilder in recipe builds!  phew
[14:21] <kenvandine> 2015-06-30 14:20:34,372 ERROR Uncaught exception: ServerNotFoundError: Unable to find the server at api.launchpad.net
[14:21] <kenvandine> trainguards: ^^ tried to rebuild a silo
[14:22] <kenvandine> citrain isn't happy
[14:34] <sil2100> hmmmm
[14:34] <sil2100> kenvandine: could you re-try?
[14:35] <kenvandine> sure, i'll re-try again
[14:35] <kenvandine> sil2100, boom
[14:35] <kenvandine> socket.gaierror: [Errno -2] Name or service not known
[14:40] <sil2100> uuuh
[14:40] <sil2100> Some network issues on the jenkins server it seems
[14:49] <mzanetti>  /subscribe to when this is resolved ^ :)
[14:50] <cjwatson> sil2100: being chased in #is-outage internal
[14:50] <cjwatson> general DNS problem in PS4.5
[14:50] <sil2100> cjwatson: hah, just asked on #webops, thanks ;)
[14:56] <cjwatson> sil2100: should be fixed now, you can retry stuff
[14:57] <sil2100> Yay
[15:04] <brendand> ogra_, sil2100 - it seems that -updates and -security are in the sources.list for these vivid images, but not used during the build?
[15:04] <sil2100> They should
[15:05] <brendand> sil2100, that's what pitti tells me
[15:05] <sil2100> Interesting, the build config doesn't have anything specific that would say it's like that
[15:06] <ogra_> brendand, they definitely shoudl eb used ...
[15:06] <ogra_> unless someone explicitly hacked them out in livecd-rootfs ... which i dont think happened
[15:09] <brendand> ogra_, ok i'm trying to figure out why i have oxide-qt-codecs-extra 1.7.8 installed, but 1.7.9 is in -security
[15:09] <brendand> i mean -updates
[15:10] <brendand> ogra_, i just moments ago did the image update
[15:10] <ogra_> had it migrated already when the image was built ?
[15:10] <ogra_> s/was built/started building/
[15:15] <brendand> ogra_, that's one possibility
[15:16] <brendand> ogra_, pitti pointed me to - https://launchpad.net/ubuntu/+source/oxide-qt/1.7.9-0ubuntu0.15.04.1
[15:16] <brendand> ogra_, that was last week
[15:30]  * sil2100 goes lay down for a while
[15:39] <boiko> trainguards: can I get the telepathy-qt5 package removed from silo 39? it has already landed in wily
[15:56] <bfiller> trainguards: silo 6 can be freed and I need a silo for line 62 please
[16:02] <bzoltan_> psivaa: thank you
[16:14] <brendand> ogra_, sil2100 - would it be okay to ask for another vivid image build? this oxide landing is giving us bother
[16:14] <ogra_> brendand, well, someone should check the log and see if -security is actually enabled during builds ...
[16:15] <brendand> ogra_, who would be able to do that?
[16:15] <ogra_> i guess someone who has time :P
[16:16] <ogra_> (dunno if we have anyone who is responsible for phone image builds already, i can perhaps look later but i dont plan to do a long day today)
[16:23] <cjwatson> mzanetti: ^- that looks like an actual failure this time
[16:23] <mzanetti> looking
[16:23] <cjwatson> mzanetti: if you think it's transient we can retry just that one build
[16:24] <mzanetti> cjwatson, indeed
[16:24] <mzanetti> no, it's a test failure
[16:35] <brendand> ogra_, i'd do it myself but i don't even know where the logs are
[16:36] <ogra_> https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/vivid/ubuntu-touch perhaps
[16:37] <brendand> ogra_, ok then it does appear to be using -updates and -security
[16:37] <ogra_> Get:44 http://ports.ubuntu.com/ubuntu-ports/ vivid-security/main liboxideqtcore0 armhf 1.7.8-0ubuntu0.15.04.1 [21.3 MB]
[16:37] <brendand> go build go!
[16:38] <brendand> ogra_, that's looking like it was a timing issue. i think it migrated only 3 hours ago
[16:38] <brendand> ogra_, perhaps during that build
[16:38] <ogra_> well, at least it is definitely pulling the packages from -security
[16:39] <brendand> ogra_, yep so we can do a build
[16:40] <popey> sil2100: I'd like to request a debian package be added to the phone, how do I do that these days?
[16:40] <ogra_> popey, file an MP against the seed and point sil2100 to it
[16:40] <ogra_> oh, wiat
[16:40] <ogra_> no seed :P
[16:40] <popey> :)
[16:40] <popey> glad I asked
[16:41] <ogra_> i guess then by simply asking sil2100 :)
[16:41] <ogra_> (or via a bug ... to prevent typos of the package name )
[16:42] <popey> haha, that's the voice of experience.
[16:42] <popey> filed against what?
[16:44] <ogra_> ubuntu-touch-meta
[16:44] <popey> kk
[16:47]  * popey tickles sil2100 with https://bugs.launchpad.net/ubuntu/+source/ubuntu-touch-meta/+bug/1470166
[16:47] <popey> should keep studio_ happy :)
[16:47] <ogra_> oh man ... how many deps does that pull in ?
[16:47] <ogra_> did anyone check ?
[16:51]  * popey will add some detail to the bug :)
[16:51] <pmcgowan> uh oh
[16:51]  * ogra_ has no intention to make studio_ happy ... where would be the fun in that :P
[16:51] <popey> spoilsport
[16:52] <popey> After this operation, 31.0 MB of additional disk space will be used.
[16:52] <popey> tiny :)
[16:53] <ogra_> rrright ... tiny ...
[16:53] <ogra_> i guess thats a bottle of mccallan 18 for pmcgowan to get that in
[16:53] <pmcgowan> ooo
[16:54] <popey> python 2.7 :S
[16:54] <ogra_> we need a "bribes" field in LP bugs ;)
[16:54] <popey> hah
[16:54] <ogra_> awww
[16:55] <davmor2> popey: no no, not landing no python 2.7 on phone
[16:55] <ogra_> python 2.7 is rather a no ...
[16:55] <popey> right, so how do we do this then
[16:55] <popey> (I prefer solutions then flat out 'no')
[16:55] <popey> and no, "snappy fixes this" is not a solution I accept :)
[16:56] <ogra_> obey !
[16:56] <ogra_> :)
[16:56] <popey> :)
[16:56] <davmor2> popey: but but but but "Snappy fixes everything"!!!!!!!  ogra_ said so
[16:56] <popey> fact is someone using a converged device is quite likely to want this
[16:56] <ogra_> well, i guess you ask slangasek if foundations could work on porting libsmbclient to python 3
[16:56] <popey> be good to test this _before_ then
[16:57] <cjwatson> popey: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781913
[16:57] <popey> thanks cjwatson
[16:57] <ogra_> ha !
[16:57] <popey> "yay"
[16:58]  * popey goes outside to eat. will come back when the flames die down.
[17:00] <davmor2> popey: man you I love the fact that you know you are going to combust in the heat of outside but you are still doing it ;)
[17:07] <charles> trainguards, ^ yes, please
[17:08] <robru> charles: silo 41
[17:08] <charles> robru, thanks
[17:08] <robru> charles: you're welcome!
[17:25] <charles> on it
[17:57] <bfiller> robru: I don't need silo 6 anymore so it can be freed
[17:59] <charles> ...2.0.0+15.10.20150619.1-0ubuntu1 is the current version number for 15.04...?
[17:59] <charles> ah
[18:00] <robru> charles: hm?
[18:01] <charles> robru, fixable on my end, I think it's an MR error -- this should be going into the 15.04 branch but was MRed for trunk
[18:01] <robru> charles: ah ok
[18:04] <charles> robru, well actually, since we're still testing it, maybe the shorter path would be to switch line 64 from vivid to wily...
[18:05] <robru> charles: can do
[18:05] <charles> looks like that's doable via Landing Tools
[18:07] <robru> charles: yep, I made some changes recently so that you're able to take care of that yourself. but I just did it already so don't worry
[18:07] <charles> robru, :-)
[23:32] <karni> ping tranguards - I'd like to have Telegram re-QA'ed, we've updated translations (which has been the only comment from last QA pass, as the scope was missing some strings)
[23:33] <karni> (FTR I'm off on Wednesday)
[23:49] <robru> karni: you'll need to ping qa about that, ask jibel.