[00:04] <robru> cjwatson, Chipaca: https://ci-train.ubuntu.com/job/landing-009-1-build/120/console looking good now, sorry for the hassle there
[00:51] <Chipaca> robru: thanks!
[00:53] <Chipaca> i guess build 120 was wonky in some way too?
[00:55] <robru> Chipaca, hum, looks like it failed to upload for some unrelated reason. but at least the original problem is fixed. I tried a FORCE_REBUILD in the hopes that it was just a version number issue (force rebuild does a version bump and has a chance of working...)
[00:56] <robru> Chipaca, yeah, build 121 looks like it's going: https://ci-train.ubuntu.com/job/landing-009-1-build/121/console
[00:56] <Chipaca> yep, watching it with bated breath :)
[00:57] <Chipaca> actually, scratch that, i'm going to catch some sleep
[01:00] <robru> Chipaca, goodnight!
[01:11] <robru> Chipaca, ah, looks like you got a test failure there
[02:04] <imgbot> [03:34] <imgbot> [03:34] <imgbot> [05:25] <veebers> robru, trainguards: Any chance anyones around? :-)
[05:45] <robru> veebers, oh hey
[05:46] <veebers> hey robru, do you ever sleep? :-)
[05:46] <robru> veebers, haha, not even 11PM here... ;-)
[05:46] <veebers> robru: :-) I just wanted to check in, 2 things. I've _finally_ marked autopilot release as good to go
[05:47] <robru> veebers, I see that, I was wondering ;-)
[05:48] <veebers> 2nd, I have a libautopilot-qt release setup, I released too late that thomi bottom approved but not top approved before he EOD. I'm hoping you don't mind assigning the silo for it as is so I can get the testing phase underway (as it takes ~3-4 hours)
[05:48] <robru> veebers, yeah for sure, we changed citrain so that you only need top-approval to publish, not to build
[05:49] <veebers> robru: ah nice. Thanks for that :-)
[05:49] <robru> veebers, thank sil2100, he made that change ;-)
[05:49] <veebers> robru: Do I need to fire off the build or is that done automatically now days?
[05:49] <robru> veebers, ah, you still need to kick the build I think
[05:49] <veebers> robru: cool will  do so
[05:50] <robru> veebers, not sure if I'm comfortable publishing that autopilot silo, sil should be up soon to look at that.
[05:50] <veebers> robru: ack, no worries
[05:50] <robru> veebers, alright, I'm going back to the TV. have fun!
[05:51] <veebers> robru: Thanks again, much appreciated o/
[05:51] <robru> veebers, you're welcome!
[05:59] <robru> veebers, ^^ you know how to fix that? ;-)
[05:59] <veebers> robru: heh, your supposed to be watching tv. I was waiting for sil or someone to come online to check, but I'm pretty sure that's its because I screwed up in one of my ppas
[05:59] <veebers> robru: i.e. https://launchpad.net/~veebers/+archive/ubuntu/tmp-autopilot-qt-non-visual
[06:00] <veebers> that version should have a ~veebers1 or something after it
[06:00] <robru> veebers, huh, that's weird, it shouldn't be getting versions from random PPAs, it should be just looking at what's in the archive.
[06:01] <robru> veebers, https://launchpad.net/ubuntu/+source/autopilot-qt yeah that same version is in distro
[06:01] <veebers> robru: that's what I thought, but I pulled trunk and the version in the change log is '1.4+14.04.20140312-0ubuntu2'
[06:01] <veebers> robru: oh, bad assumption on my part then
[06:02] <robru> veebers, ah, xnox made an upload. you gotta take this diff: https://launchpadlibrarian.net/175664192/autopilot-qt_1.4%2B14.04.20140312-0ubuntu2_1.4%2B14.04.20140312-0ubuntu3.diff.gz and just push it direct to trunk, then rebuild in the silo.
[06:02] <veebers> robru: does that mean someone pushed directly to arc. . .
[06:02] <robru> veebers, yes ;-)
[06:03] <veebers> robru: ah awesome, thanks for the heads up. So I should push that to trunk, not create a MP with those changes?
[06:03]  * veebers looks at the diff
[06:03] <robru> veebers, yeah, when people make direct archive uploads, there's no real point to bother with MPs, it's already too late for that. so just push it to trunk and then the build can proceed.
[06:04] <veebers> robru: awesome, I owe you one
[06:04] <robru> veebers, hehe, no worries! ok, out for real this time ;-)
[07:34] <Chipaca> robru: yes, test failure. Digging into it after I've had my coffee.
[07:53] <xnox> Chipaca: hmmm, yes coffeeeee that's what i need!
[08:01] <cjwatson> sil2100: I won't make the landing meeting today - will be cycling into town, meeting doko to work in a café for the morning
[08:01] <sil2100> cjwatson: oh, let mvo_ sheriff today, as it seems he'll be off on Friday so he preferred starting today - if possible
[08:01] <cjwatson> oh?  ok
[08:02] <sil2100> Oh, doko in the UK? My my!
[08:08] <cjwatson> I'll let mvo_ take the topic once he's around
[08:12] <sil2100> Go away heat..!
[08:22] <xnox> sil2100: nice and cool overcast here =) we've had boiling hot heat last week though.
[08:23] <sil2100> I hope it'll be the same here, I *need* coolness!
[08:23] <seb128> xnox, you mean like 25°C? ;-)
[08:23] <sil2100> psivaa: hm, what's up with mantas in our latest images?
[08:23] <sil2100> psivaa: and I saw some mako tests didn't finish?
[08:24] <psivaa> sil2100: mantas are both down in adb.. probably dead without charge. i've askes IS to take a look
[08:25] <psivaa> sil2100: mako health check was still running and i rekicked unity8 tests because we only had 20 unity8 tests (instead of 53) due to a 'string exception'
[08:28] <xnox> seb128: well we actually did have 31 last week.
[08:28] <seb128> xnox, nice ;-)
[08:31] <cjwatson> mvo_: ta
[08:31] <mvo_> cjwatson: no problem
[08:42] <tvoss> davmor2, ping
[08:43] <davmor2> tvoss: wassup,  location got good testing last week.  Location found me in seconds on the campsite never failed to amaze me :)
[08:46] <psivaa> brendand: http://pastebin.ubuntu.com/7829158/
[08:57] <asac> bzoltan: uitoolkit is really bad in dashboard?
[08:57] <ogra_> asac, yea
[08:57] <asac> did that thing got landed?
[08:58] <bzoltan> asac: nopez
[08:58] <asac> ogra_: what caused this?
[08:59] <bzoltan> asac: ogra_: there was not even a single successful Jenkins job for the UITK for a week. Jenkins is busted badly
[08:59] <ogra_> asac, i thought sil2100 discussed that with bzoltan on friday
[08:59] <ogra_> asac, we would fix it if we knew :P
[08:59] <ogra_> asac, brendand did some research as well as the AP guys
[09:00] <asac> http://ci.ubuntu.com/smokeng/utopic/touch/mako/131:20140715:20140712/9061/
[09:00] <asac> that one is good
[09:00] <ogra_> yes
[09:00] <asac> 132 as well
[09:00] <ogra_> 133 too
[09:00] <ogra_> (we promoted it)
[09:00] <asac> 134 too
[09:01] <asac> 135 started
[09:01] <ogra_> right, as i said, it is being investigated
[09:01] <asac> noone tried to figure out what caused this on 135?
[09:02] <ogra_> it is being looked at since it started
[09:02] <sil2100> asac: we're looking at it since it started, and we know more or less what causes it
[09:02] <sil2100> asac: and the fun thing is that most of the failures are not caused by any particular landing
[09:03] <bzoltan> asac: my previous landing was on last Tuesday
[09:03] <sil2100> asac: but caused by a timestamp issue in autopilot that just started happening because the date changed (got big enough)
[09:03] <sil2100> Which is very funny
[09:03] <sil2100> And there's the qmlscene crash, but it's actively being looked at
[09:04] <asac> sil2100: the date changed?
[09:04] <ogra_> well, today it turned into system-compositor and unity8 crashing
[09:05] <ogra_> davmor2, are you running 133 (devel) constantly somewhere ? i see frequent session restarts
[09:05] <ogra_> (once a day at least)
[09:06] <brendand> sil2100, apparently we can workaround it in uitk
[09:06] <ogra_> sil2100, ugh, i just relaoded the dashboard ... seems the indicator-location crash is back in the four tests
[09:07] <sil2100> ogra_: yeah, saw that, it's a promotion blocker so I suppose we need to poke tvoss again ;)
[09:07] <sil2100> ogra_: as charles needed some input from tvoss to identify
[09:07] <ogra_> yup, tie him up in a corner til he has fixed it
[09:28] <tvoss> davmor2, great @location. So can I ask you to give silo 8 a spin?
[09:32] <bzoltan> sil2100: asac: sorry for the delay... this is one of the bugs what blocks the UITK tottaly - https://bugs.launchpad.net/ubuntu-app-launch/+bug/1329141
[09:34] <asac> bzoltan: seems thgey want a unity8.log
[09:34] <asac> mirv not on today?
[09:35] <ogra_> nope
[09:35] <bzoltan> asac:  he is on holiday for two weeks
[09:35] <ogra_> two weeks vacation
[09:35] <asac> Saviq: https://bugs.launchpad.net/ubuntu-app-launch/+bug/1329141 ... something for your team?
[09:35] <asac> qtubuntu
[09:35] <asac> seems leo has attached a good repro instruction
[09:36] <asac> so gerry could get the log himself easily
[09:41] <bzoltan> asac: and this is the other one -> https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1328600
[09:44]  * ogra_ wonders if that also happens if you just run with a POSIX or C locale 
[09:44] <ogra_> (and default to UTC)
[09:47] <bzoltan> sil2100: may i get a silo for the line28, please?
[09:51] <sil2100> mvo__: ^
[09:52] <mvo__> sure
[09:52] <sil2100> asac: we already had ricmm and greyback looking at this bug, waiting for them to proceed
[09:52] <mvo__> bzoltan: could you please set it to "ready" (column I)
[09:53] <bzoltan> mvo__: Ahh... thanks.
[09:54] <mvo__> bzoltan: :) this part will ensure  the trainguard s get a ping from the bot
[09:54] <mvo__> bzoltan: you have the silo now
[09:56] <asac> sil2100: well, greyback asks for a log
[09:56] <asac> sil2100: while there are repro instructions... so if he has priority on it, he culd just run and get that log on his own
[09:57] <davmor2> tvoss: will do
[09:57] <tvoss> davmor2, thank you
[09:58] <davmor2> sil2100: looks like manta never completed the update, stuck on the google logo it was the update it was installing before D'oh I'll plug it into the pc and reboot it and see what happens
[09:58] <tvoss> cjwatson, can I get your vote here? https://code.launchpad.net/~thomas-voss/platform-api/explicit-gcc-version/+merge/227511
[09:58] <tvoss> cjwatson, had to take over Steve's MP to explicitly specify the dbus-cpp version to build against
[10:06] <cjwatson> lgtm
[10:06] <cjwatson> but fix whatever ps-jenkins doesn't like :)
[10:07] <cjwatson> oh, that's just newest dbus-cpp being unavailable, ok
[10:07] <sil2100> davmor2: ouch
[10:08] <tvoss> cjohnston, thanks
[10:08] <tvoss> damn
[10:08] <tvoss> cjwatson, thanks :)
[10:08] <Saviq> sil2100, greyback didn't really look at that bug, ricmm did you (re: bug #1329141)
[10:08] <Saviq> asac, ↑
[10:08] <Saviq> I'm running the steps now, 5 mins in, no crash
[10:09] <sil2100> We were poking ricmm hard about this one on Friday
[10:10] <asac> Saviq: awesme
[10:10] <asac> thanks
[10:11] <asac> sil2100: ricmm was sprinting last week; this week he is busy too... have you checked that this regression was caused by an upload of qtubuntu?
[10:15] <davmor2> sil2100, ogra: okay so adb seems to be working, nothing in /var/crash where is the best place to look next or who is the best person to talk to about what they mighty need,  Been on the google logo for about 12 minutes according to uptime
[10:16] <sil2100> asac: we checked, but there was no qtubuntu upload when this started happening, but it might have been a hidden issue caused by something else - when the crash started happening we landed a fix for a blocker in unity-system-compositor, but we weren't able to exactly find any relation... that's why ricmm was pointed to as the main person that could know more
[10:22] <asac> sil2100: kk
[10:22] <mvo__> sil2100: I'm at lunch now - just to let you know :)
[10:22] <asac> lets see if saviq finds something too
[10:25] <ogra_> davmor2, sounds like the container doesnt start then
[10:30] <cjwatson> sil2100: How's the RTM stuff going?
[10:46] <camako> cihelp: we have the same failure on three different MPs on the mir/0.5 branch... All on armhf... any ideas?
[10:47] <asac> camako: where is such an example?
[10:49] <camako> asac, https://jenkins.qa.ubuntu.com/job/mir-mediumtests-runner-mako/2114/console
[10:49] <davmor2> ogra_: mtp keeps restarting
[10:49] <ogra_> well, does the caontainer run ?
[10:49] <ogra_> *container
[10:49] <ogra_> (mtp only reacts to property changes)
[10:50] <ogra_> sounds like it is restarting (and thus settiing/unsetting the property)
[10:51] <ogra_> davmor2, pastebin the oputput of /system/bin/logcat -d ... and syslog
[10:52] <davmor2> ogra_: http://paste.ubuntu.com/7829641/
[10:53] <ogra_> there you go
[10:53] <ogra_> https://code-review.phablet.ubuntu.com/#/admin/projects/
[10:53] <ogra_> err
[10:53] <ogra_> W/libEGL  ( 2071): eglTerminate() called w/ 1 objects remaining
[10:53] <ogra_> E/libEGL  ( 2071): validate_display:263 error 3001 (EGL_NOT_INITIALIZED)
[10:53] <ogra_> (paste error)
[10:54] <ogra_> talk to the Mir guys
[10:55] <ogra_> davmor2, i'm surprised you dont see the display flashing actually ... seems to restart and die several times
[10:55] <davmor2> ogra_: no solid on the google logog
[10:55] <davmor2> -g
[10:55] <ogra_> yeah
[11:00] <davmor2> ogra_: and there is syslog http://davmor2.co.uk/~davmor2/syslog
[11:01] <ogra_> Jul 21 10:03:41 ubuntu-phablet kernel: [   32.623884] mali mali.0: state save latency exceeded, new value 1346833 ns
[11:01] <ogra_> Jul 21 10:03:42 ubuntu-phablet kernel: [   33.060695] init: lightdm main process (2060) terminated with status 1
[11:01] <ogra_> Jul 21 10:03:42 ubuntu-phablet kernel: [   33.060784] init: lightdm respawning too fast, stopped
[11:02] <ogra_> graphics driver dies ... and then it tries to respawn the container over and over (which causes the adb/mtp restarts)
[11:03] <Saviq> sil2100, asac, https://bugs.launchpad.net/ubuntu-app-launch/+bug/1329141/comments/15
[11:03] <ogra_> davmor2, so thats either an android update ... (wait for rsalveti to show up) or a Mir issue
[11:04] <asac> Saviq: awesome
[11:04] <asac> yes for fixing both sides :)
[11:04] <sil2100> Saviq: o/
[11:04] <asac> is this random tmp thing a new feature?
[11:05] <asac> so who is fixing the underscore thing?
[11:05] <asac> tedg: ^^
[11:06] <davmor2> ogra_: will do :) /me curses rsalveti for daring to not be online when I have issues that need diagnosing :D
[11:06] <ogra_> yeah, these americans ... sleeping all day
[11:07] <Saviq> asac, I'm looking into UITK
[11:07] <Saviq> asac, it's not new, it's just... random ;)
[11:08]  * sil2100 needs to lay down for a moment
[11:08] <asac> Saviq: hmm. started with build 134
[11:08] <asac> so maybe we have multiple issues here ... one that is random
[11:08] <Saviq> asac, something probably changed there
[11:08] <asac> one that is repro
[11:08] <Saviq> asac, but the quick solution is still valid
[11:08] <asac> yeah
[11:08] <Saviq> asac, and then we can investigate
[11:08] <asac> this one sounds sensible
[11:09] <asac> Saviq: uitk is creating the randomstring?
[11:09] <asac> not ual?
[11:09] <Saviq> asac, yes
[11:09] <asac> sh ok
[11:09] <asac> sh
[11:09] <asac> ah
[11:09] <asac> :)
[11:09] <Saviq> asac, UITK creates a fake app
[11:09] <asac> bzoltan: ^
[11:09] <asac> 13:02 < Saviq> sil2100, asac, https://bugs.launchpad.net/ubuntu-app-launch/+bug/1329141/comments/15
[11:10] <bzoltan> asac: Saviq: let me check that out
[11:12] <Saviq> bzoltan, tests/autopilot/ubuntuuitoolkit/fixture_setup.py:84
[11:14] <Saviq> bzoltan, doesn't look like you can easily tell it to not use underscores...
[11:14] <bzoltan> Saviq: yes
[11:15] <Saviq> maybe we can rename it after it's created
[11:18] <bzoltan> Saviq: I hate all these modern libs ... :)
[11:24] <Saviq> bzoltan, it did discover a real bug, though ;)
[11:24] <bzoltan> Saviq: :D how true
[11:25] <ogra_> bugs ? there are no bugs !
[11:25] <ogra_> they are just features in camouflage ...
[11:26] <ogra_> (or was that the other way round ?)
[11:27] <sil2100> ;D
[11:40] <ogra_> davmor2, so looking at the test results manta seems to have started failing with 137 .... which at the same time was shipping the new Mir 0.5
[11:41] <ogra_> davmor2, would probably good to confirm that it works with 136 and breaks with 137
[11:41] <davmor2> ogra_: will do, playing catchup on correspondence at the minute.
[12:04] <davmor2> ogra_: 136 is working
[12:04] <ogra_> davmor2, so 137 should fail :)
[12:05] <davmor2> ogra_: installing it now
[12:41] <brendand> sil2100, the messaging-app failure is reproducible by the way
[12:45] <tvoss> davmor2, ping
[12:46] <davmor2> ogra_: 137 is broken on manta
[12:46] <ogra_> davmor2, great, thanks ! so it is in fact the Mir update i guess
[12:46] <ogra_> tell #ubuntu-mir to fix it ;)
[12:47] <davmor2> tvoss: sorry bunch of manta tests and Lunch back now, silo 8 is next on the list
[12:47] <tvoss> davmor2, awesome, thank you :)
[12:47] <tvoss> davmor2, the sooner, the better
[12:47] <tvoss> davmor2, quite some components in there
[12:48]  * sil2100 is at lunch still
[12:48] <davmor2> tvoss: is there some instructions then so I know everything is installed? Or should it all be covered from and dist-upgrade?
[12:48] <sil2100> davmor2, ogra_: could you just overview what's the manta status? Is it completely broken since 137?
[12:48] <tvoss> davmor2, I would propose citrain device-upgrade 8
[12:49] <ogra_> sil2100, yeah, the graphics driver falls over with the new Mir it seems
[12:49] <sil2100> ogra_: but didn't we get some test runs in smoketesting for manta that were ok?
[12:50] <ogra_> not since 137
[12:54] <sil2100> uh
[12:55] <sil2100> Damn, we should REALLY look at non-mako platforms everyday
[12:55] <sil2100> Since I missed this for instance
[12:55] <sil2100> psivaa: in case I forget about this, could you maybe make sure we at least look if all our platforms had all tests running?
[12:57] <ogra_> manta is difficult lbecause it never charges enough in the lab
[12:58] <psivaa> sil2100: ack, will do. that. not sure if i'll be having enough time to do that before the landing meeting though.. I guess i could do it after the meeting
[12:59] <tvoss> davmor2, and the silo contains packages built with a new toolchain. So testing instructions as "simple" as: "test everything"
[13:21] <rsalveti> ogra_: mir 0.5 also broke the hammerhead image: bug 1343198
[13:21] <rsalveti> so yeah, it'd be good to test such landing on more devices (not necessarily hammerhead)
[13:21] <rsalveti> but at least mako, flo and manta
[13:21] <rsalveti> ops, wrong bug
[13:22] <rsalveti> bug 1345533
[13:24] <ogra_> no bot ?
[13:27] <rsalveti> vacation maybe
[13:29] <ogra_> ah, yeah, its summer in the northern hemisphere
[13:29] <ogra_> summer vacation then ...
[13:31] <mvo__> sil2100, Chipaca: hm, when I try to publish landing-009 I get: "2014-07-21 13:30:32,492 ERROR Some merge requests are not yet approved. Please review all merges and re-run the build job"
[13:31] <Chipaca> mvo__: hm? wha?
[13:32] <Chipaca> do I have to +1 something?
[13:32] <mvo__> Chipaca: yeah, very odd, let me look over the branches
[13:32] <sil2100> Yeah, it means there's a branch that's not yet Approved
[13:33] <mvo__> Chipaca: https://code.launchpad.net/~chipaca/ubuntu-push/the-push-automatic/+merge/227420 is in state "needs review", someone needs to set it to approved
[13:34]  * Chipaca approves
[13:34] <Chipaca> there
[13:36] <oSoMoN> sil2100, hey, can silo 12 be published, please?
[13:36] <mvo__> Chipaca: thanks, its happier now, looking over the debdiff of the debian changes (https://ci-train.ubuntu.com/job/landing-009-2-publish/44/artifact/packaging_changes_ubuntu-push_0.49+14.10.20140721.1-0ubuntu1.diff) I can see e.g. changes in what looks like a already released debian/changelog stanza. is this on purpose or a accident?
[13:36] <mvo__> oSoMoN: I can publish it if everytihng is ready and tested
[13:36] <sil2100> mvo__: ^ can you take a lookie once you're free? ;)
[13:37] <oSoMoN> mvo__, it’s ready and tested indeed, all it needs is publication
[13:37] <Chipaca> mvo__: it might be? can you point me at the line?
[13:37] <mvo__> Chipaca: the bits after "@@ -11,6 +64,10 @@"
[13:38] <mvo__> oSoMoN: thanks! publishing now
[13:39] <mvo__> Chipaca: there is also a "+  [ John R. Lenton ]\n[Samuele Pedroni]" at the beginging of the changelog, but that could be a merge artifact, not sure if you can do much about it
[13:40] <oSoMoN> mvo__, thanks
[13:42] <mvo__> Chipaca: other than that the debian/* changes look fine
[13:44] <Chipaca> mvo__: sorry, was in a meeting and couldn't focus on this and that at the same time. What artifact are you referring to when you say "@@ -11,6etc"?
[13:44]  * Chipaca is in a maze of diffs, all different
[13:46] <Chipaca> mvo__: i saw the [john]\n[samuele] thing, wondering if it's worth fixing -- last couple of merges the names were stripped out anyway
[13:46] <Chipaca> makes reading the changelog harder, but eh
[13:48] <Chipaca> dammit, you pointed me *at* the diff
[13:48]  * Chipaca reads that
[13:49] <Chipaca> mvo__: that seems like a bad merge, possibly our side of things
[13:49] <mvo__> Chipaca: yeah, the [joh]\n[samuele] is just costmetic, the other one is more important to not add entries that are not really valid :)
[13:49] <Chipaca> mvo__: those same lines (different wording) are in the right changelog
[13:51] <Chipaca> mvo__: i need to fix the branch, and re-build. Give me a few.
[13:51] <mvo__> Chipaca: no problem, just let me know when you are ready and I'm happy to click the right button
[13:52] <fginther> camako, looking at the scripts in lp:~mir-team/+junk/mir-medium-test-runner-for-jenkins and the console log. Those tests are getting stuck here: exec_with_adb_user "/sbin/initctl stop unity8"
[13:53] <fginther> camako, and then the build timesout out waiting for that to return
[14:03] <davmor2> tvoss: there is a regression in mediascanner, it is not collecting artwork/showing the music title for an age http://davmor2.co.uk/~davmor2/screenshots-phone/device-2014-07-21-150018.png  this then became http://davmor2.co.uk/~davmor2/screenshots-phone/device-2014-07-21-150207.png just before the screen blanked so 45-55 seconds.
[14:04] <tvoss> davmor2, ack, let me look into it
[14:06] <tvoss> davmor2, is that an otherwise unknown regression?
[14:07] <davmor2> tvoss: let me double check, I think previously it showed the title and the music notes in a blank tile if it didn't know or until it updated
[14:10] <davmor2> tvoss: yeap like this http://davmor2.co.uk/~davmor2/screenshots-phone/device-2014-07-21-150837.png  note the title only appears on the one at the front but you get the idea of what I'm used to seeing while it refreshes.
[14:11] <davmor2> tvoss: which is what is happening now for a group of say 20 or so at a time with the screen nearly blanking on each group
[14:11] <tvoss> davmor2, ack
[14:15] <sil2100> geh, I feel bad today...
[14:21] <ogra_> xnox, do you do the meta upload too (for indicator-transfer) ?
[14:23] <xnox> ogra_: no, merge only.
[14:23] <xnox> ogra_: not that urgent to land.
[14:28] <tvoss> davmor2, mediascanner2 rebuilding in silo
[14:30] <davmor2> tvoss: nice
[14:41] <Chipaca> mvo__: done
[14:41] <Chipaca> queuebot: you so slow lol
[14:42] <mvo__> Chipaca: thanks, on it
[14:55] <tvoss> davmor2, should be upgradeable
[14:56] <cyphermox_> ChickenCutlass: seb128: brendand: let's land ubuntu-system-settings for the bluetooth updates today hopefully...
[14:56] <cyphermox_> brendand: I've updated the manual tests document
[14:56] <seb128> cyphermox_, no
[14:56] <ChickenCutlass> yes let's land asap
[14:57] <cyphermox_> seb128: any other things you'd like to land in u-s-s?
[14:57] <seb128> cyphermox_, there is a landing we just put in the landing queue and I'm reviewing your changes and have needs fixing comments coming
[14:57] <cyphermox_> ok
[14:58] <cjwatson> bfiller: How's silo 1 looking?
[14:58] <bfiller> cjwatson: I commented in the landing sheet
[14:59] <bfiller> cjwatson: ready to go from my perspective, just wanted clarification of steps. Typically we release the silo then generate the click from trunk once it's merged
[14:59] <cjwatson> bfiller: We can't in this case, circular
[14:59] <bfiller> cjwatson: right
[15:00] <bfiller> cjwatson: should I manually merge to trunk then generate and upload click?
[15:00] <cjwatson> bfiller: Can't go on trunk until it's in utopic, can't reach utopic until we unblock the exiv2 transition, can't unblock that transition until we have this in the store
[15:00] <davmor2> tvoss: got it now let see what happens
[15:00] <bfiller> cjwatson: shall I upload the version that I built in jenkins?
[15:00] <cjwatson> bfiller: Couldn't we release this to utopic-proposed, and then generate the click package from ~ps-jenkins/gallery-app/utopic-proposed?
[15:01] <cjwatson> Or from something equivalent
[15:01] <cjwatson> At least that way it's clearly on track
[15:01] <bfiller> cjwatson: that sounds like a plan
[15:01] <davmor2> tvoss: that looks better :)
[15:01] <tvoss> davmor2, awesome
[15:02] <bfiller> cjwatson: can you take care of that and ping me once it's in proposed and I can generate the click and upload
[15:02] <cjwatson> bfiller: Hm, important to make sure versions are correct I guess
[15:03] <cjwatson> bfiller: the utopic-proposed branch has slightly fewer revisions than trunk does due to translation updates automatically committed to trunk
[15:03] <cjwatson> bfiller: So maybe a manual merge to trunk would be safest, so that it correctly comes out as revision 1017 ...?
[15:04] <bfiller> cjwatson: that works
[15:04] <cjwatson> sil2100: ^- do you see any problems with this plan?
[15:05] <sil2100> cjwatson, bfiller: I didn't backlog everything, but we could wait for it to get to utopic-proposed and then force merging it to trunk (as if it was released) and roll out a click package from trunk?
[15:05] <cjwatson> Right, that was the plan
[15:06] <sil2100> cjwatson, bfiller: so just using CI Train for that
[15:06] <cjwatson> bfiller: OK, I'll go ahead and release this to -proposed
[15:06] <cjwatson> sil2100: Oh, for the merge as well?
[15:06] <sil2100> cjwatson: yes, you can force the merge and clean to merge the change even though it didn't reach the destination yet
[15:06] <sil2100> We do that for some SRUs
[15:07] <sil2100> If we know that it's in -proposed and passed all verifications for bugs, we allow merging it in already
[15:07] <cjwatson> I guess so - we just need to make sure not to build gallery-app again until the transition's done
[15:07] <sil2100> Ok
[15:07] <sil2100> Indeed
[15:07] <cjwatson> Which is now a matter of hassling the security team until they review an MIR
[15:09] <seb128> cyphermox_, ok, commented with a list of need fixing
[15:09] <seb128> cyphermox_, I didn't code review, just played with it a bit
[15:09] <cjwatson> argh some more blockers have appeared
[15:09] <seb128> cyphermox_, but commenting anyway if you want to start working on fixing some of the issues
[15:09] <cyphermox_> seb128: sure
[15:09] <cjwatson> hate hate hate
[15:09] <sil2100> brendand: btw. any luck with the autopilot timestamp thingie?
[15:10] <tvoss> davmor2, do you keep on testing?
[15:10] <davmor2> tvoss: yeap lot to test, Everything :)
[15:10] <tvoss> davmor2, lol
[15:11] <brendand> sil2100, i'll talk to elopio about working around it. that's the only option at the moment
[15:11] <balloons> sil2100, I was just asking about that :-) I pushed a workaround for the toolkit tests at least on friday
[15:11] <davmor2> meh never noticed that before me files a bug for the teams to unify on names.
[15:13] <Laney> seb128: you took out the test fixes?
[15:13] <seb128> Laney, what where?
[15:13] <Laney> I thought I saw them in the uss landing
[15:13] <cyphermox_> seb128: sounds like your bluetooth is broke too
[15:13] <sil2100> balloons: hi! For the timestamp problems? :)
[15:14] <seb128> Laney, which ones?
[15:14] <Laney> oh wait
[15:14] <balloons> sil2100, yes..
[15:14] <seb128> Laney, silo 004 has it?
[15:14] <Laney> line 31 is another one
[15:14] <Laney> got confused
[15:14] <sil2100> hmmm
[15:14] <seb128> cyphermox_, "too"?
[15:15] <sil2100> balloons: we still have tons of failures, so I thought we didn't have any workarounds for that one
[15:15] <balloons> sil2100, it hasn't landed but it works. I'll work on getting the sdk team to review
[15:15] <seb128> Laney, silo 004 is good for you then?
[15:15] <sil2100> Oh
[15:16] <davmor2> sil2100: in the lack of a popey for confirmation can you quickly drag down the network indicator no the name mobile settings click on it and then tell me the name of the section it takes you too please
[15:16] <cyphermox_> seb128: part of the issue seems that your bluez may not have started properly
[15:16] <Laney> seb128: just wanted to check if the replaceme worked
[15:16] <sil2100> balloons: how many failures does it fix?
[15:16] <seb128> Laney, let me know if it does ;-)
[15:17] <Laney> seb128: looks right
[15:17] <seb128> great
[15:17] <cyphermox_> seb128: wait, scratch that, that's the remote device
[15:17] <balloons> sil2100, it will allow the UITK to pass again. thomi rejected my change to AP to fix everything ;-) Looks like it's harder than my proposed fix
[15:18] <sil2100> davmor2: hm, I would have to re-flash my phone, can you wait for that?
[15:18] <davmor2> sil2100: it's possible in any image so that shouldn't be an issue unless you flashed android back on it ;)
[15:19] <sil2100> Ah, oh!
[15:20] <ogra_> yay, statically linked gallery-app
[15:20] <ogra_> \o/
[15:20] <ogra_> cjwatson, so theoretically we should be ablke to unseed exiv2 now
[15:20] <sil2100> davmor2: I clicked Cellular settings and it takes me to the Cellular section
[15:21] <sil2100> davmor2: when clicking on Wi-Fi settings it takes em to Wi-Fi
[15:22] <davmor2> sil2100: ah it is a recent change then that's why I didn't see it before, I wonder if it is english GB as language setting from the welcome screen
[15:23] <davmor2> sil2100: I see mobile settings instead of cellular and then it takes me to the cellular page in the settings app
[15:23] <cjwatson> ogra_: Right, I know, just waiting for a couple of other things
[15:23] <sil2100> Oh, ok, well... my image is quite outdated so maybe it changed now
[15:23] <cjwatson> ogra_: Do we normally silo ubuntu-touch-meta or just upload directly?
[15:23] <ogra_> just directly
[15:24] <ogra_> onyl if it is a bunch of packages that also live in a silo we use silos for it
[15:24] <davmor2> brendand: what do you see in network indicator mobile settings or cellular settings?
[15:24] <ogra_> single additions/removals dont really need a silo
[15:24] <brendand> davmor2, Mobile settings
[15:25] <cjwatson> ogra_: OK.  We shouldn't unseed this until after the new gallery-app is in the store, but I can deal with it after that.
[15:25] <davmor2> brendand: and did you pick English_GB when setting up the phone?
[15:25] <ogra_> cjwatson, great, thanks !
[15:25] <cjwatson> ogra_: (Note it's not entirely statically linked, it just statically links that one library, for now)
[15:25] <ogra_> yeah
[15:25] <brendand> davmor2, yes. because i speak english, and i'm in the uk
[15:25] <ogra_> i saw the code change
[15:26] <cjwatson> Somebody owes me the hour of my life I spent figuring out how to do that in cmake
[15:26] <davmor2> brendand: I'm click on mobile settings and see where it takes you :)
[15:26] <sil2100> ogra_: ok, so I don't feel to well today, could you lead todays meeting? I'll compose an e-mail later on, there's just some small things to discuss today anyway
[15:26] <sil2100> ogra_: just that there's progress on the UITK front
[15:26] <brendand> davmor2, to Cellular page in u-s-s
[15:27] <davmor2> brendand: So not the Mobile page then ;)
[15:27] <sil2100> ogra_: btw. how's the manta situation? Did the Mir guys mention anything?
[15:27] <ogra_> sil2100, right, i think thats our major issue today
[15:27] <brendand> davmor2, nope
[15:27] <ogra_> sil2100, yeah kgunn has put the right people on the task
[15:27] <ogra_> it is all handled fine
[15:27] <brendand> davmor2, probably because there's no such thing :)
[15:28] <sil2100> ogra_: as mentioned above, with UITK we have both issues almost done, at least well identified... the UITK autopilot issues are worked-around by balloons, waiting for release, and the qmlscene crash is identified and worked on a fix
[15:28] <sil2100> ogra_: kalikiana has a fix for the crash even
[15:28] <ogra_> cool !
[15:28] <sil2100> Or workaround rather!
[15:29] <sil2100> https://code.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-toolkit/noScores/+merge/227541 <- it's EVIL but I guess that in this case I could even accept it ;)
[15:29]  * sil2100 goes to lay down for a while
[15:31] <kalikiana> I figured we'd want to avoid rewriting the whole way to pick unique filenames and possibly hitting other corner cases :-)
[15:31] <brendand> sil2100, did balloons submit a workaround for the uitk failures?
[15:31] <brendand> sil2100, i didn't see anything
[15:32] <balloons> brendand, https://code.launchpad.net/~nskaggs/ubuntu-ui-toolkit/fix-1328600/+merge/227394.. MP's go to staging for them, so they might be a bit hidden
[15:33] <balloons> brendand, elopio pointed out there's one more test to update, so I'll do that now so it passes
[15:58] <tvoss> slangasek, ping
[16:00] <slangasek> tvoss: hi
[16:00] <brendand> sil2100, stuck in another meeting
[16:00] <tvoss> slangasek, so davmor2 finished his testing :) all good \o/
[16:00] <slangasek> tvoss: huzzah
[16:01] <tvoss> slangasek, with that, we can walk through all the mps again and see if they are all top-approved before finally publishing :)
[16:01] <slangasek> tvoss: why do we need to do that?
[16:02] <tvoss> slangasek, not sure that all are top-approved and I thought the publishing step would fail if they were not
[16:02] <tvoss> slangasek, https://code.launchpad.net/~thomas-voss/platform-api/explicit-gcc-version/+merge/227511
[16:04] <tvoss> thostr_, you marked https://code.launchpad.net/~charlesk/indicator-datetime/make-gcc-version-explicit/+merge/224467 as "Needs fixing"?
[16:05] <thostr_> tvoss: IIRC that was about the gcc or g++-4.9 string.... charles ^^^
[16:07] <charles> ...?
[16:07]  * charles looks
[16:08] <tvoss> slangasek, there is a merge conflict here: https://code.launchpad.net/~vorlon/media-hub/explicit-gcc-version/+merge/226567
[16:08] <charles> thostr_, you approved with a LGTM, then marked 'needs fixing' without comment...
[16:09] <thostr_> charles: yes, because later I detected something wrong.... at least that's what I remember
[16:09] <slangasek> tvoss: merge conflict> yes, someone appears to have been manually creating changelog entries ;)
[16:09] <thostr_> charles: can you quickly check the gcc string?
[16:10] <slangasek> tvoss: FWIW, I don't believe there's any technical reason that top-approval should be required for publication
[16:10] <cjwatson> No technical reason but citrain makes you override it if not, and it seems generally sensible to get it
[16:10] <tvoss> slangasek, okay ... would be great to have them top-approved to merge&clean as soon as possible :)
[16:10] <tvoss> slangasek, sorry for the changelog thingy :)
[16:11] <charles> thostr_, tvoss, the changes are the same as in the other indicator-make-gcc-version-explicit MPs...
[16:11] <tvoss> slangasek, can you fix in your branch?
[16:11] <slangasek> yes, fixing
[16:11] <charles> thostr_, I don't understand what you mean, I don't see a problem in the diff
[16:13] <tvoss> cjwatson, could you revisit: https://code.launchpad.net/~thomas-voss/pay-service/explicit-gcc-version/+merge/224763
[16:13] <slangasek> tvoss: fixed
[16:13] <tvoss> slangasek, thanks
[16:13] <charles> thostr_: it would have been better to add an explanation when marking as "Needs Fixing" ;-)
[16:13] <seb128> kenvandine, Laney: can you help testing the settings in silo 004?
[16:13] <seb128> I don't have a sim to run that part of the testplan
[16:13] <tvoss> slangasek, would you mind top-approving here: https://code.launchpad.net/~thomas-voss/platform-api/explicit-gcc-version/+merge/227511
[16:13] <tvoss> ?
[16:13] <thostr_> charles: yeah....
[16:13] <Laney> I don't have one with any credit
[16:13] <Laney> is that required?
[16:14] <kenvandine> seb128, sure
[16:14] <seb128> Laney, not sure, in fact we don't even touch that panel in this landing, so not sure we need to test it at all, still would be good to just see if you can connect to your carrier
[16:15] <cjwatson> tvoss: You don't seem to have addressed my comments
[16:15] <tvoss> cjwatson, let me re-read
[16:16] <cjwatson> I had two different comments both of which are still problems AFAICS
[16:16] <thostr_> charles: or, it was the dh auto configure thingy...
[16:16] <thostr_> charles: that didn't set the compiler env?
[16:16] <tvoss> cjwatson, okay, let me see
[16:17] <kenvandine> 854577
[16:17] <kenvandine> whoops
[16:23] <kenvandine> seb128, what needs testing?
[16:23] <seb128> kenvandine, just install, restart settings, check that things seem to work fine (including update date in about panel)
[16:24] <seb128> kenvandine, not sure we need to run the full testplan since we didn't do much changes (mostly about panel for the update timestamp and test bugfixes)
[16:24] <tvoss> cjwatson, updated https://code.launchpad.net/~thomas-voss/pay-service/explicit-gcc-version/+merge/224763
[16:24] <kenvandine> ok, nothing SIM specific :)
[16:24] <seb128> no
[16:28] <tvoss> slangasek, quick dinner, back after
[16:31] <cjwatson> tvoss: thanks, approved
[16:31] <robru> Laney, hey, did you build anything with that 0replaceme yet? Let me know how that works for you...
[16:31] <Laney> robru: yeah, u-s-s in 004 has it, seems to have worked!
[16:32] <robru> sweet
[16:32] <kenvandine> seb128, yay... sounds!
[16:32] <kenvandine> seb128, looks good to me
[16:32] <robru> ogra_, has anything big landed during your shift? should I kick an image before publishing autopilot?
[16:32] <sil2100> robru, ogra_: the meeting finished?
[16:33] <robru> sil2100, yep
[16:33] <robru> was short
[16:33] <sil2100> robru: ah, I'll be pushing my second (better!) approach to auto-m&c today probably, so watch out when you redeploy ;)
[16:33] <sil2100> If I find enough strength for that
[16:34] <robru> sil2100, heh, take it easy, you're no good to us dead from heat stroke! ;-)
[16:34] <seb128> kenvandine, thanks, to me too
[16:34] <seb128> Saviq, +1 from the settings side
[16:35] <Saviq> seb128, anything I should still look at in there?
[16:35] <Saviq> seb128, run autopilot?
[16:36] <seb128> Saviq, no, it's fine, we tested it enough between us I think
[16:36] <Saviq> seb128, ok cool, just running u8 now
[16:37] <Laney> seb128: it seems fine to me
[16:37] <Laney> seb128: we should put some more vertical spacing in I think
[16:38] <Laney> the rows under 'System' look too close to me
[16:38] <bfiller> sil2100: regarding gallery, let me know when the -proposed merges to trunk so I can generate a click from trunk
[16:39] <bfiller> sil2100: or if I need to run merge and clean
[16:41] <sil2100> bfiller: ah, let me take care of that ;)
[16:41] <sil2100> robru: thanks ;p
[16:41]  * sil2100 is a person of winter
[16:41] <sil2100> I like sun and summer, but not when it's hot!
[16:43] <sil2100> bfiller: ok, it's now merged in trunk
[16:43] <seb128> Laney, yeah, feel free to mp a change for that
[16:43] <Laney> will do
[16:44] <bfiller> sil2100: thanks!
[16:47] <sil2100> ogra_,davmor2: do we have a bug for the dead mantas?
[16:48] <davmor2> sil2100: rsalveti does for the hammerhead and it is a similar issue so should fix both as I understand it
[16:49] <sil2100> Can anyone throw me a bug number? ;)
[16:49] <sil2100> For teh e-mail
[16:52] <robru> kgunn, ^ bug number for that manta issue?
[16:52] <kgunn> robru: lp: 1345533
[16:53] <robru> sil2100, ^
[16:54] <sil2100> Thank you!
[17:30] <robru> Saviq, seb128, Laney: just did a big autopilot landing, I guess I'll wait for that to migrate, kick an image, and then publish silo 4
[17:31] <Saviq> robru, ok
[17:44] <tvoss> cjwatson, slangasek can I get your votes here?
[17:44] <tvoss> https://code.launchpad.net/~charlesk/indicator-datetime/make-gcc-version-explicit/+merge/224467
[17:47] <slangasek> tvoss: what are we voting on?
[18:08] <bfiller> popey, cjwatson: new version of gallery-app uploaded to store if you could approve popey
[18:16] <tvoss> slangasek, just a review please :-)
[19:14] <imgbot> [19:24] <robru> stgraber, ^^ did you land any changes to queuebot recently? not sure why it's double-pinging about new landings.
[19:24] <robru> I suppose if people edit the description field after marking ready: yes it would double-ping. hrm
[19:24] <stgraber> robru: haven't changed anything but yeah, I'd suspect someone editing the description after setting it ready
[19:27] <tvoss> slangasek, ping
[19:27] <tvoss> slangasek, seems like we have a build error for media-hub after I triggered a rebuild to match the latest version in the MP: https://launchpadlibrarian.net/180424031/buildlog_ubuntu-utopic-amd64.media-hub_1.0.0%2B14.10.20140721-0ubuntu1_FAILEDTOBUILD.txt.gz
[19:29] <robru> stgraber, can I get a core dev ack? https://ci-train.ubuntu.com/job/landing-013-2-publish/lastSuccessfulBuild/artifact/packaging_changes_ubuntu-download-manager_0.7+14.10.20140721-0ubuntu1.diff
[19:34] <kgunn> fginther: did you help camako turn on autolanding for mir0.5 branch ? or do i need to manual merge ?...its ok either way, i'm just shepherding a critical fix thru
[19:35] <stgraber> robru: sorry, I'm busy and on vacation at the moment.
[19:35] <fginther> kgunn, the problem was not resolved. I found the bit of test code that is causing the problem, but camako must have been offline or unable to respond to debug it further
[19:36] <robru> stgraber, ah sorry, didn't know
[19:36] <robru> stgraber, sign off IRC :-P
[19:36] <robru> kenvandine, can I get a core dev ack? https://ci-train.ubuntu.com/job/landing-013-2-publish/lastSuccessfulBuild/artifact/packaging_changes_ubuntu-download-manager_0.7+14.10.20140721-0ubuntu1.diff
[19:36] <stgraber> robru: I never sign off IRC because I use IRC for way more than just work stuff :)
[19:37] <kgunn> fginther: no worries, i'll do it
[19:41] <tvoss> slangasek, would be great if you could fix the build error and trigger a rebuild for media-hub. I could ask davmor2 for a more focused round of testing tomorrow morning before finally publishing
[19:45] <tvoss> robru, ping
[19:45] <robru> tvoss, pong
[19:45] <tvoss> robru, hey there :) silo8 is almost good to go and I would like to avoid a resync to trunk
[19:45] <tvoss> robru, could you make sure that silo 8 takes the lock on the packages in it?
[19:46] <tvoss> asac, ^
[19:46] <robru> tvoss, oh ok
[19:51] <robru> tvoss, so I'm taking lunch in an hour, but my official EOD isn't until 5 hours from now, and I'll probably even be around a bit after that, so just ping me when you're ready to publish
[19:51] <tvoss> robru, I will EOD now, kinda late here
[19:52] <tvoss> robru, would be great if you could hand over the information to the next shift :)
[19:52] <robru> tvoss, oh, so you're aiming to publish tomorrow?
[19:52] <tvoss> robru, yup
[19:52] <robru> tvoss, ok
[19:53] <tvoss> robru, thanks a lot
[19:53] <robru> tvoss, no worries!
[20:34] <slangasek> tvoss: media-hub> right, looking; however, why do we think another round of testing is needed?
[20:44] <imgbot> [20:44] <imgbot> [20:55] <slangasek> tvoss: also, this media-hub build failure is clearly unrelated to the gcc change; is someone else likely to be working on fixing it?
[20:58] <slangasek> jhodapp: are you by any chance looking at the media-hub FTBFS introduced by the new gst?  Don't want to step on your toes, and we need to get https://code.launchpad.net/~vorlon/media-hub/explicit-gcc-version/+merge/226567 landed for g++4.9
[21:07]  * robru -> lunch
[21:11] <jhodapp> slangasek: no I'm not
[22:41] <kgunn> robru: hey, sorry to double pester behind the bot...but its a hot one, can i get a silo for the mir fix ? line 32
[22:53] <robru> kgunn, sorry, was on lunch, can assign now
[22:55] <robru> kgunn, you got silo 4, and building: https://ci-train.ubuntu.com/job/landing-004-1-build/145/console
[22:55] <kgunn> thanks!
[22:56] <robru> you're welcome!
[22:58] <robru> infinity, cjwatson: anybody around for a packaging ack? https://ci-train.ubuntu.com/job/landing-013-2-publish/62/artifact/packaging_changes_ubuntu-download-manager_0.7+14.10.20140721-0ubuntu1.diff
[23:01] <infinity> robru: Looking.
[23:01] <robru> infinity, thanks!
[23:03] <infinity> robru: Looks reasonable to me.
[23:03] <robru> infinity, thanks!
[23:03] <infinity> robru: That symbol version should be higher, but if, as stated, nothing really uses this yet anyway, meh.
[23:03] <robru> ah ok
[23:04] <infinity> robru: But, actually, please fix that.
[23:04] <robru> infinity, oh i hit publish already
[23:04] <infinity> robru: That new symbol should be 0.7+14.10.20140721
[23:04] <infinity> robru: Oh.  Well, ask them to fix it in trunk. ;)
[23:04] <robru> infinity, or it could be 0replaceme ;-)
[23:04] <robru> infinity, ok
[23:05] <infinity> robru: It's harmless to get it wrong when there's no danger of partial upgrades happening, but it's also a nice changelog for when symbols were added.
[23:06] <infinity> robru: (Basically, what that symbols file means is that if a package starts using that symbol, it will depend on libthing (>= old-version) when it should depend on (>= version-where-symbol-appeared))
[23:07] <robru> infinity, ahh i see
[23:07] <robru> I'll prep a branch to fix that
[23:09] <infinity> robru: Looking at the small amount of context there, I suspect they're bumping upstream version when they change the API, so those could be simplified to "0.4" and "0.7" etc, rather than the whole ugly version string.
[23:09] <infinity> robru: At least, in that case, we went from 0.6 to 0.7
[23:11] <infinity> robru: Which would have the nice side effect of making this sort of thing more backportable, should that be needed in the future (ie: 0.7+14.04 is << 0.7+14.10, but both are >> 0.7)
[23:12] <infinity> Probably not neede for this specific package, but worth thinking about.  Symbol versions should reflect upstream changes, except in the really weird case where a Debian patch adds a symbol.
[23:13] <robru> infinity, technically the +14... is part of the upstream version number, but the line is blurry when we're the upstream.
[23:14] <infinity> robru: Right, in the Debian sense, foo+release+date is the "upstream" version, but in the upstream versus daily release sense, I'd contend the real upstream version there is just 0.7
[23:14] <infinity> Or, at least, from the POV of symbol versioning.
[23:14] <infinity> THe rest is muddier. :P
[23:15] <robru> infinity, so you want to see it like this? http://bazaar.launchpad.net/~robru/ubuntu-download-manager/utopic-proposed/revision/316
[23:16] <infinity> robru: Yeah.  Realistically, the +foo should be stripped from all of them, so it's more obvious what we're going for there (and even as a subtle reminder that API additions should be bumping that version).
[23:16] <infinity> Cause tracking API/ABI changes by a datestamp could well lead to madness (see above argument, re: backportability)
[23:17] <robru> infinity, it's not *really* a datestamp though. it's version by upstream + by distro release series before the datestamp bit.
[23:17] <infinity> We won't backport any of this from U to T, but we may well see backports and forward ports between U and V.
[23:17] <infinity> robru: Right, it's a date twice, though.  Just one happens to be an Ubuntu version. ;)
[23:17] <infinity> robru: The point is that a dependency of >> 0.7+14.10 is wrong, if 0.7+14.04 can also satisfy it, and the obvious choice is 0.7
[23:17] <infinity> (Same for the 0.4, etc)
[23:18] <robru> ah, ok
[23:19] <infinity> robru: I doubt it matter at all for this specific thing (yet), if it'll generally only exist in system images, but best practices and all, and it may well be abused by apt later (ie: when it ends up on my desktop some day).
[23:19] <infinity> And making apt's life easier on partial upgrades by not forcing it to sort out upgrade ordering it doesn't need to is always a win.
[23:20] <robru> cool
[23:25] <slangasek> jhodapp: pushed a fix for the gst-induced FTBFS to lp:~vorlon/media-hub/explicit-gcc-version.  Do you prefer that I separate this out into a separate branch for review?