[00:24] <kgunn> any idea why we lost silo 20 on the greeter revert ?
[00:26] <dobey> cjwatson: you forced it last time :)
[00:27] <dobey> cjwatson: thanks again though
[00:29] <kgunn> robru: stgraber any idea why line 32 lost silo 20 ?....we're kind of expecting some folks in europe to test when they wake
[00:39] <cjwatson> dobey: couldn't see it in bzr; ref to irc log would be welcome so I can figure that out
[01:29] <robru> kgunn, yeah spreadsheet is just completely borked, don't worry your silo is still there
[01:30] <robru> kgunn, please refer to http://people.canonical.com/~rbpark/citrain/ as the authoritative status for citrain silos
[01:30] <robru> I'm trying to restore the spreadsheet but it's slow
[02:09] <tedg> robru, How does one land the dbus-test-runner MR then?
[02:10] <robru> tedg, just merge it? it's already in distro, just push it to trunk
[02:10] <tedg> robru, Oh, I thought that was against the rules.
[02:10] <tedg> I'll do that though, clean things up.
[02:11] <robru> tedg, well, laney already broke the rules by doing an upload without using ci train in the first place. so you have to just push to trunk in order to get things back in sync.
[02:11] <tedg> Oh, cool. It's so rare I get to blame Laney for something :-)
[02:11] <tedg> Will do.
[02:12] <robru> tedg, yeah, CI train is totally not set up to do merges like that. it freaks out because that component never built, and then it insists that you rebuild and republish the compnent, which is completely unnecessary
[02:15] <tedg> Makes sense. Mostly package based I guess.
[03:29] <imgbot> [03:29] <imgbot> [07:23] <cjwatson> So I roughly doubled the speed of the PPA publisher yesterday, and we deployed that a few hours ago.  Hopefully that will make the CI engine feel a bit more responsive :-)
[08:04] <Laney> What?
[08:05] <Laney> There is *no* rule against anyone doing direct uploads.
[08:46] <asac> Laney: why do you think there is a rule?
[08:47] <ogra_> asac, because tedg claimed that
[08:47] <Laney> asac: http://irclogs.ubuntu.com/2014/06/12/%23ubuntu-ci-eng.html#t02:11
[08:48] <seb128> ogra_, it's not ted who claimed, see that log
[08:48] <ogra_> (and robru agreed)
[08:48] <ogra_> seb128, i have it 109cm above on my screen here :)
[08:48] <asac> so there are laws for the world
[08:48] <ogra_> *10cm
[08:48] <seb128> they are both wrong though
[08:48] <ogra_> indeed
[08:48] <asac> and there is common sense :)
[08:49] <ogra_> but there was nobody around to tell them
[08:49] <asac> is tedg a core-dev?
[08:49] <ogra_> nope
[08:49] <asac> ok then it doesnt really matter i guess :)
[08:49] <ricmm> robru: hi, are you around?
[08:50] <ogra_> ricmm, i doubt that ... and sil is out this morning, should be back in 20-30min though
[08:50] <ricmm> right
[08:50] <ricmm> I wanted to drop a pkg from my silo
[08:51] <ogra_> i think technically i can delete packages from silos ... but i dont know what is involved beyond that (which kind of rebuild etc)
[09:19] <sil2100> Argh! Didn't make it for the meeting in the end :<
[09:21] <sil2100> robru: you didn't use the backups?
[09:21] <sil2100> robru: when did the spreadsheet failure happen?
[09:21] <sil2100> ogra_: ^ do you know?
[09:22] <sil2100> We should have backups for that case...
[09:23] <ogra_> sil2100, nope, no idea
[09:23] <ogra_> but it looks fine now it seems
[09:24] <ogra_> sil2100, so we decided to quickly dogfood 79 instead of 78 since the test results are so much better, as soon as davmor2 gives his OK i'll promote something
[09:27] <sil2100> Awesome o/
[09:28] <sil2100> Test results look really good indeed
[09:33] <sil2100> ricmm: how's the papi v2 landing going?
[09:33] <ogra_> he was looking for you to drop one package from the silo
[09:33] <ogra_> (sorry, i forgot)
[09:33] <ricmm> right, I need to drop dbus-cpp from the silo
[09:34] <ricmm> to then rebuild the whole thing with 4.8
[09:34] <ricmm> as the 4.9 default has been reverted for now
[09:39] <sil2100> hmm
[09:39] <sil2100> Ok
[09:40] <sil2100> ricmm: I can remove the package from the PPA for you - do you need a reconfigure of the silo as well? Like, removing some dbus-cpp merge or somethin?
[09:42] <ricmm> yes, dbus-cpp has an MR to have it rebuild
[09:42] <ricmm> it is the last one in the spreadsheet
[09:42] <ricmm> can you remove it and reconf for me?
[09:43] <sil2100> Sure
[09:46] <sil2100> ricmm: reconfigured, you can build stuff now
[09:47] <ricmm> sil2100: thank you
[09:48] <ricmm> sil2100: building
[09:48] <ricmm> after this is done, it should be landable
[09:48] <sil2100> davmor2: how's the dogfooding going?
[09:48] <ricmm> 4.9 creeped in with ABI breakage
[09:48] <sil2100> ricmm: yay \o/
[09:48] <ricmm> that was unexpected
[09:48] <ricmm> sorry
[09:48] <sil2100> Right, I saw some other projects having trouble with that as well
[09:48] <sil2100> We had some issues in the OSK for instance
[10:00] <asac> ricmm: creeped in? was there no announce or something?
[10:03] <davmor2> sil2100: I'm starting it properly now but it looked pretty stable on 79 already
[10:04] <ricmm> asac: I'm sure there were announcements, but the gcc-defaults upload happened yesterday and I didnt see that
[10:04] <ricmm> but I also dont dive deep in lists every other hour
[10:05] <ricmm> but it was catched in my silo when I tried to rebuild something for a change
[10:05] <ricmm> then realised the toolchain had moved to 4.9
[10:07] <cjwatson> asac: it's already been reverted pending investigation
[10:08] <ricmm> it allows us to move forward without doubting breakage
[10:08] <ricmm> so, its good while doko investigates I guess
[10:14] <sil2100> I didn't see an official message that 'switch is done', I only remember reading an e-mail from doko in May about the gcc switch pending
[10:36] <popey> davmor2: ever seen this bug 1329275
[10:37] <davmor2> popey: no but I guess you can replicate using the house phone with 141 or whatever the hide my number is
[10:37] <popey> yeah, i tried, but 141 doesn't work on virgin
[10:59] <mandel> sil2100, I gave up a silo yesterday to give a hand to other so that they can get silos, may I get one back (line 22) pretty please :) :)
[11:00] <sil2100> mandel: o/ Is that dbus-cpp?
[11:00] <mandel> sil2100, yes :)
[11:00] <mandel> sil2100, before we go back to gcc 4.9 ;)
[11:00] <sil2100> mandel: since there is a landing from thostr_ that already locks dbus-cpp, but I guess it's for testing right now
[11:00] <sil2100> mandel: could you coordinate with him :) ?
[11:01] <sil2100> i.e. that everything is rebuilt when released
[11:01] <mandel> sil2100, I can wait for him to land and will do the landing after, I'm just adding macros to be used by other projects, conflicts should not happen at all
[11:02] <sil2100> mandel: from what thostr_ said, it's still not '100% ready', so we might try landing your thing first
[11:02] <sil2100> mandel: just make sure you inform thostr_ when that happens :)
[11:02] <sil2100> So you guys don't step on your toes
[11:04] <mandel> thostr_, let me know what you are changing in dbus-cpp so that I make sure we have no issues :)
[11:05] <sil2100> mandel: assigned a silo for you with override, but please try to proceed with the landing - we would appreciate not having many idle silos :)
[11:05] <sil2100> Thanks!
[11:06] <asac> cjwatson: thanks!
[11:07] <mandel> sil2100, ok, will be fast fast fast :)
[11:10] <davmor2> popey: 141 works but mine just displays unknown caller
[11:10] <davmor2> popey: http://help.virginmedia.com/system/selfservice.controller?CMD=VIEW_ARTICLE&ARTICLE_ID=4022&CURRENT_CMD=SEARCH&CONFIGURATION=1001&PARTITION_ID=1&USERTYPE=1&LANGUAGE=en&COUNTY=us&VM_CUSTOMER_TYPE=Cable
[11:10] <davmor2> nice short url there
[11:11] <mandel> sil2100, since I consider you my new *.symbols guru, can you take a look at https://code.launchpad.net/~mandel/ubuntu-download-manager/leak-symbols/+merge/222472
[11:13] <sil2100> mandel: give me a moment :)
[11:13] <davmor2> popey: can you reproduce this https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1329289
[11:13] <mandel> sil2100, thx
[11:13] <popey> davmor2: 141 doesn't work here
[11:13] <davmor2> popey: don't know what to say it does here
[11:14] <davmor2> oh nice if you screenshot the split gretter you can't slide it to get to the phone
[11:15] <popey> davmor2: for that messaging bug, i sent another and the previous one came through
[11:16] <davmor2> popey: hahahaha that's broken that is :)
[11:16] <popey> well, i mean the previous one and the one I sent game through
[11:16] <popey> like it pushed them
[11:17] <thostr_> mandel: yes, will do so
[11:19] <mandel> thostr_, I'm just adding a set of macros for other projects to use so that they do not have to write the entire method struct definition => https://code.launchpad.net/~mandel/dbus-cpp/provide-macros/+merge/221840
[11:20] <mandel> thostr_, we should not have any problems, what are you guys landing?
[11:20] <davmor2> popey: not seen that I got the first I replied to that I got the reply I replied to that :)
[11:20] <Wellark> mandel: go ahead and land.
[11:20] <davmor2> popey: if you call your phone does the ringer repeat?
[11:20] <Wellark> we are not landing right now
[11:20] <thostr_> mandel: I don't think we'll land it today
[11:20] <sil2100> mandel: the changelog is still b0rken there in the u-d-m branch ;) See my comment
[11:20] <mandel> Wellark, thostr_ ack, thx
[11:20] <popey> davmor2: what do you mean "repeat"?
[11:21] <mandel> sil2100, ew.. I hate making those mistakes, let me check
[11:21] <davmor2> popey: for me it is playing once and then doesn't ring again
[11:22] <popey> same
[11:22] <davmor2> ogra_, sil2100 ^
[11:22] <ogra_> did that work in 78 ?
[11:23] <davmor2> ogra_: pass I went 77-79
[11:23] <ogra_> and did it work in 77 then ?
[11:23] <davmor2> ogra_: pass I normally pick it up straight away :)
[11:24] <mandel> sil2100, weird, 'casue debuild did not complain about that  missing ' ' pushing
[11:24] <ogra_> lol, so it could be broken since a while
[11:24] <davmor2> ogra_: it has worked in the past
[11:24] <davmor2> ogra_: I'll dig into after
[11:24] <ogra_> ok
[11:25]  * ogra_ is most interested if we have promoted with that before 
[11:25] <davmor2> popey: does it work on stable?
[11:26] <davmor2> well last promoted
[11:27] <davmor2> popey: confirming your x-ofono issue the notifcations display correctly it's just the message in the indicator that is wrong
[11:29] <ogra_> davmor2, so on 71 it plays on ...
[11:29] <ogra_> just tried here
[11:29] <davmor2> ogra_: plays more than once right?
[11:29] <davmor2> ie it keeps repeating
[11:30] <ogra_> yes
[11:30] <davmor2> cool so its a recent regression then
[11:31] <davmor2> I'll try 77 in a minute and see if it is the alarms wake up fix that broke it
[11:34] <ogra_> err, thats only in 78
[11:35] <davmor2> yes hence trying 77 so it is before that fix ;)
[11:45]  * sil2100 sighs
[11:46] <sil2100> davmor2: what's up?
[11:47] <davmor2> sil2100: ringer only rings once
[11:47] <ogra_> ringtone doesnt repeat anymore it seems
[11:49] <sil2100> That's serious ;/
[11:50] <sil2100> Well, in the end we can promote #77 I guess
[11:50] <sil2100> And then maybe try aiming for #80 if this gets fixed by then
[11:51] <davmor2> sil2100: trying 77 now to see if it work right there
[11:57] <sil2100> davmor2: keep us updated
[11:58] <sil2100> I would really like to see 79 released, but I guess we can't do it with such a regression
[11:59] <ogra_> well, not ringing at all would be worse :)
[12:00] <sil2100> Yeah, but you can miss calls this way anyway
[12:01] <davmor2> sil2100: so 77 rings more than once
[12:01] <sil2100> ;(
[12:02] <sil2100> Well, I should be happy I guess?
[12:02] <sil2100> Since we can at least promote 77
[12:02] <davmor2> sil2100: at least we get to blame rsalveti for everything :D
[12:02] <sil2100> davmor2: yeah :)
[12:02] <sil2100> rsalveti: ^
[12:03] <sil2100> davmor2: btw...
[12:03] <sil2100> davmor2: can you take 77 and upgrade just the bits from rsalveti
[12:03] <sil2100> ?
[12:03] <sil2100> And see if it breaks?
[12:03] <sil2100> ogra_: anyway, let's promote #77 for now, and then think of what to do with the next images
[12:03] <davmor2> sil2100: should be able to give me 5
[12:03] <sil2100> But I want to have something new at least
[12:04] <ogra_> sil2100, could we wait til we have proper results ?
[12:04] <ogra_> 77 78 and 79 wont go away ... we can promote them any time
[12:04] <ogra_> let davmor2 do his research first
[12:04]  * ogra_ cant really belive the indicator changes actually cause this ...
[12:05] <sil2100> ogra_: yeah, but I guess there's nothing bad in promoting 77 anyway, right? We can surely wait a moment anyway
[12:05] <ogra_> sil2100, we dont know yet if 77 doesnt have the same issue
[12:05] <sil2100> davmor2: you want help with the component lists?
[12:05] <ogra_> it hasnt been tested for this yet
[12:05] <sil2100> ogra_: davmor2 just tested
[12:05] <sil2100> ogra_: 14:01 < davmor2> sil2100: so 77 rings more than once
[12:05] <ogra_> oh, i missed that ... sorry
[12:06] <ogra_> 77 had these unity8 crashes :(
[12:06] <sil2100> ogra_: I just wanted to make double sure that it's that particular landing by asking davmor2 to upgrade the HW bits themselves at 77
[12:06] <sil2100> :<
[12:06] <sil2100> It's better than nothing!
[12:06] <davmor2> sil2100, ogra_: by the look of it most of 78 is the fix right?
[12:06] <ogra_> sure
[12:06] <ogra_> davmor2, indicator-datetime and lxc-android-config have the fix
[12:07] <ogra_> the rest are langpacks and heimdal (encryption libs) updates
[12:07] <davmor2> ogra_: ah right give me 5 then
[12:07] <ogra_> dont forget you need to install lxc-android-config from recovery
[12:07] <ogra_> (or just quickly hack the udev rule it chnages yourself ... )
[12:08] <davmor2> ogra_: damn it why is it never easy ;)
[12:08] <ogra_> just hack the udev rule ;)
[12:09] <davmor2> ogra_: how exactly would I hack that please
[12:11] <ogra_> davmor2, /lib/udev/rules.d/65-android.rules ...
[12:11] <ogra_> change:
[12:11] <ogra_> ACTION=="add", KERNEL=="alarm", OWNER="system", GROUP="system", MODE="0664"
[12:11] <ogra_> to:
[12:11] <ogra_> ACTION=="add", KERNEL=="alarm", OWNER="system", GROUP="phablet", MODE="0660"
[12:11] <davmor2> ogra_: ta
[12:13]  * sil2100 jumps out for lunch
[12:13] <sil2100> No time to cook!
[12:18] <rsalveti> morrrning
[12:19] <davmor2> sil2100, ogra_: right with just those 2 packages installed and and the udev.rules changed I get one ring then it goes click and I get no more ringtone however the notification for the incoming call is still in place so you could conceivably still answer the call even though it only rings once
[12:19] <ogra_> 2 packages ?
[12:20] <ogra_> you mean only the indicator package, right ?
[12:20] <davmor2> ogra_: indicator-datetime and the lxc-android-config
[12:20] <ogra_> well, lets hear what sil2100 says ...
[12:21] <ogra_> i personally think the indicator notification is enough ... as long as we notify about the issue in the daily landing mail
[12:21] <ogra_> and make sure it gets fixed asap
[12:21] <ogra_> davmor2, can you revert the udev rule and try again (after a reboot indeed, else udev wont pick it up)
[12:21] <davmor2> ogra_: of course I still blame rsalveti 110%
[12:22] <ogra_> so we can poinpoinnt it to either tthe indicator or the rule
[12:22] <davmor2> ogra_: sure one second
[12:23] <rsalveti> nah, should be the indicator
[12:23] <rsalveti> would be surprised if the udev rule caused that hahah
[12:23] <rsalveti> charles: around already?
[12:23] <ogra_> yeah, just wanna make sure
[12:23] <seb128> rsalveti, what has the indicator to do with ringing?
[12:23] <rsalveti> seb128: you tell me
[12:23] <seb128> nothing!
[12:23] <Laney> you're the one trying to blame it!
[12:23] <ogra_> especially since it is the datetime one
[12:23] <seb128> though it started using the platform-api
[12:23] <seb128> so maybe it's triggering a bug there
[12:24] <ogra_> yeah, we wont fix bugs in that
[12:24] <ogra_> v2.0 is already waiting to land :)
[12:24] <davmor2> Laney: I'm not I'm trying to blame rsalveti :D
[12:24] <seb128> the new platform-api is about to land right?
[12:24] <ogra_> yep
[12:24] <seb128> that might fix it, who knows :p
[12:24] <seb128> land it!
[12:24] <rsalveti> hahah
[12:24] <seb128> before doko gets you again by changing gcc
[12:25] <davmor2> rsalveti, ogra_: reverted the udev rule now it reings more than once
[12:25] <ogra_> ha !
[12:25] <rsalveti> wtf
[12:25] <ogra_> davmor2, try changing the group to audio please and keep the 0664
[12:26] <ogra_> then try again
[12:26] <rsalveti> but that also means that the indicator code that talks with platform-api -> alarm will fail
[12:26] <rsalveti> because it can't set the alarm
[12:26] <ogra_> well
[12:26] <ogra_> but you tested that ... and charles too
[12:26] <ogra_> and it worked
[12:26] <ogra_> i think its the 0660 that bites us
[12:27] <ogra_> but lets see what davmor says
[12:27] <rsalveti> how would that bite us
[12:28] <davmor2> ogra_: so I reverted the udev to 0664 already so you want me to leave the system in but change it to 0660 right?
[12:28] <ogra_> dunno, but if the ringtone gets somehow routed through /dev/alarm ...
[12:28] <ogra_> davmor2, GROUP=audio
[12:28] <rsalveti> makes no sense
[12:28] <ogra_> davmor2, and leave the permissions at 0664
[12:29] <davmor2> ogra_: right rebooting
[12:29] <ogra_> rsalveti, well, it makes no sense at all that it goues through /dev/alarm ...
[12:29] <ogra_> but apparently it does
[12:29] <seb128> ogra_, what makes you think it does?
[12:30] <ogra_> seb128, behaviorial changes if you change /dev/alarm
[12:30] <ogra_> thats the only thing that davmor2 is fiddling with atm (the udev rule that sets its permissions)
[12:30] <seb128> could also be an issue with the platform-api though, as rsalveti said, if you change the permission you make platform-api uses different codepaths
[12:31] <ogra_> indeed
[12:31] <ogra_> for now i'm looking for a quick fix so we can have an image in a few hours with a fix *and* working alarms
[12:31] <ogra_> this is all about promoting something before landing the new platform-api
[12:35] <davmor2> ogra_: bugger it looks like it works the very first call after a reboot but not after that so I'm going to start again from a fresh 77 and double check that it works after the first call on that and then go from there again
[12:36] <ogra_> davmor2, thanks
[12:37] <rsalveti> ogra_: do you know how to simulate a call (probably with phonesim)?
[12:37] <rsalveti> can't trash my mako right now, but can help testing with flo
[12:37] <ogra_> rsalveti, not really ... pitti should know
[12:37] <ogra_> he wrote phonesim
[12:38] <ogra_> i think you can install it and then dail a special number so it calls you back
[12:38] <rsalveti> yeah
[12:38] <ogra_> not sure how to simulate outgoing
[12:38] <rsalveti> the alarm itself rings more than once
[12:44] <davmor2> ogra_: right back to 77
[12:46] <davmor2> ogra_, rsalveti: right just rung 77 5 times and the ringtone repeated 3 times without issue
[12:47] <ogra_> so it worked all the time ?
[12:47] <rsalveti> great, now install just the indicator
[12:47] <davmor2> yes
[12:47] <ogra_> rsalveti, no
[12:47] <ogra_> rsalveti, the udev rule was what could tirgger it before even without the indicator changed
[12:47] <davmor2> ogra_: so now you want me to tweak udev without the indicator in place
[12:47] <ogra_> at least as i understan
[12:47] <rsalveti> I don't believe in that
[12:47] <rsalveti> but well :-)
[12:47] <ogra_> davmor2, right ... for a start just change 0664 to 0660
[12:48] <ogra_> reboot and see (hear)
[12:50] <mhr3> ehm, can i get silo for #30?
[12:50] <mhr3> sil2100, ^?
[12:55] <rsalveti> great, can't even open the dialer-app on flo after installing phonesim
[12:55] <davmor2> ogra_: so with 0660 the ring keeps ringing tested 3 times
[12:56] <davmor2> ogra_: so group change to phablet next right?
[12:56] <ogra_> right
[12:59] <rsalveti> ogra_: weird, latest on flo, phonesim installed, simulated an incoming call, could hear the ring 3 times
[12:59] <ogra_> well, phonesim ...
[12:59] <ogra_> dont trust it :P
[13:00] <rsalveti> well, the ringing part should be the same
[13:00] <ogra_> one would hope .... but ...
[13:00] <davmor2> ogra_: okay so now with phablet in it is still ringing correctly again tested 3 times
[13:01] <ogra_> ok, now install the indicator
[13:10] <davmor2> ogra_: okay now I get the crackle after the first ring finishes but it continues
[13:11] <ogra_> weird
[13:11] <dbarth> o/ sil2100: hi, i've got an mp to fix the gmail issue for asac
[13:12] <davmor2> ogra_: attempt number 5 this time I got the crackle and it stopped
[13:12] <ogra_> sounds really random
[13:13] <davmor2> ogra_: the crackle is only introduced with the indicator update, there was no crackle before that
[13:13] <ogra_> well, not sure what to make out of that
[13:13] <davmor2> I wonder if there is a race of some sort
[13:14] <davmor2> cause those are always the easiest things to trace
[13:14] <asac> dbarth: you are my hero of the day if this lands :)
[13:15] <asac> yesterday it was charles for the alarm :P
[13:15] <ogra_> asac, who broke calls
[13:15] <ogra_> :/
[13:15] <dobey> cjwatson: http://irclogs.ubuntu.com/2014/05/26/%23ubuntu-devel.html#t12:50 is where you jumped in last time. was during malta so easy enough to forget :)
[13:15] <davmor2> ogra_: not calls just the ringer
[13:15] <ogra_> yeah
[13:15] <ogra_> well
[13:16] <davmor2> I'm going to do a fresh install of 78 and see what is what then
[13:16] <ogra_> ++
[13:16] <ogra_> wha the frmer one an OTA ?
[13:16] <ogra_> *former
[13:16] <ogra_> oh, right, you said so
[13:16] <cjwatson> dobey: ah, so I removed the binary rather than forcing it
[13:17] <dobey> right
[13:17] <davmor2> ogra_: the first was ota
[13:17] <ogra_> yeah
[13:17] <cjwatson> dobey: what confused me was that the binary was present in utopic last night though
[13:17] <davmor2> last one was bootstrap install of 77 then tweaking, this will be a bootstrap of 78
[13:18] <ogra_> ++
[13:18] <mhr3> Mirv, silo for #30?
[13:18] <ogra_> lets see
[13:18] <dobey> cjwatson: weird. or was it the old binary without the dep on ubuntu-sdk-libs, and the previous upload was just removed from the upload, and not from the archive?
[13:18] <cjwatson> dobey: I think possibly that was some kind of bug in the LP copying process; https://launchpad.net/ubuntu/utopic/arm64/unity-scope-click shows the arm64 binary being copied to release at the same time as i386, despite the previous removal
[13:19] <dobey> oh
[13:19] <cjwatson> maybe a race because the removal hadn't been published yet or something
[13:21] <dobey> cjwatson: thanks again. hopefully no more weird breakage from new gcc again before we can get another release done
[13:27] <davmor2> ogra_: okay so a fresh 78 works no issues
[13:28] <ogra_> now do a OTA ;)
[13:28] <davmor2> so now lets try a fresh 79
[13:31] <seb128> ricmm, rsalveti: I know you are working on the platform api landing ... is that still on track? if it keeps being delayed maybe we can land our trivial fix for the iso autologin and rebase the silo unity8-desktop-mir work then?
[13:32] <ricmm> it should be ready to land
[13:32] <ricmm> after removing 4.9 from gcc defaults I've rebuilt the silo with 4.8 to retest
[13:32] <ricmm> thats what I'm doing right now, and we publish
[13:32] <ricmm> seb128: ^
[13:32] <seb128> ricmm, great, thanks
[13:33] <dbarth> asac: hopefully
[13:33] <dbarth> does that give me a silo more quickly? ;)
[13:33] <sil2100> mhr3: o/
[13:40] <sil2100> uh
[13:41] <rsalveti> ogra_: davmor2: so fresh 78 works? o_O
[13:41] <ogra_> well
[13:42] <ogra_> with cracks
[13:42] <rsalveti> always?
[13:42] <ogra_> oh, wait, no cracks in the fresh one
[13:42] <rsalveti> davmor2> ogra_: okay so a fresh 78 works no issues
[13:42] <ogra_> cracks when he changes it manually
[13:42] <rsalveti> no issues I assumed it worked perfectly
[13:42] <ogra_> yeah
[13:42] <ogra_> sorry
[13:42]  * ogra_ is super stressed having his mailserver freak out over here today
[13:43] <rsalveti> hahah
[13:43]  * popey sends ogra_ some more mail
[13:43] <ogra_> DSL issues so i had to switch to my fallback DSL ...
[13:44] <ogra_> which means my smtp address is gone temporarily ...
[13:44] <davmor2> rsalveti: no issues on 78
[13:44] <sil2100> hmmm
[13:44] <ogra_> so i thought, since i route all my mail through gmail anyway (to abuse their spam filter) ... i could just set up fetchmail to poll instead of using smtp
[13:45] <sil2100> davmor2: ok, so it's not rsalveti fault in the end, right? ;)
[13:45] <ogra_> sadly that just started downloading 2mio duplicated mails :(
[13:45] <davmor2> ogra_, rsalveti: oh this is interesting.  I can't change the ringtone I can hear and select a new one however it doesn't seem to change
[13:45] <davmor2> sil2100: no I still blame rsalveti :D
[13:45] <ogra_> because he can
[13:46] <davmor2> popey: did you change your ringtone from the default
[13:46] <popey> dont think so
[13:46] <popey> rington: ubuntu, message received: xylo
[13:46] <davmor2> popey: thanks
[13:46] <sil2100> davmor2: we need to get info if it worked on the last promoted image
[13:47] <dbarth> sil2100: o/ (not sure if you caught my silo request above)
[13:47] <davmor2> sil2100: the ringer worked on 71
[13:47] <sil2100> davmor2: I mean changing the ringtone
[13:47] <sil2100> dbarth: o/ Not yet, but will get to it in a moment :)
[13:47] <sil2100> dbarth: see it, assigning
[13:47] <dbarth> thank you
[13:48] <davmor2> ogra_, rsalveti: so 79 fresh flash I hear the ringtone but it has definite crackles at the end
[13:48] <ogra_> does it repeat ?
[13:49] <davmor2> sil2100: right leave that with me I'll get back to that in a minute
[13:49] <rsalveti> davmor2: yeah, can't change ringtone in 79
[13:49]  * sil2100 is confused with the ringtone issues
[13:49] <rsalveti> here it repeats fine
[13:50] <rsalveti> can hear some crackles sometimes as well
[13:50] <ogra_> sil2100, well, it plays ... it seems to for no weird reason not repeat *sometimes* ... but the indicator works properly and shows the missed calll in the panel ... so i think we could go with that as long as we note it in the landing mail
[13:50] <rsalveti> not being able to change ringtone is a regression, not sure when that started though
[13:50] <davmor2> rsalveti, ogra_: okay so it rings reliably
[13:51] <sil2100> hmm, if it's not 100% reproducible then I guess, if QA thinks it's plausable, we should promote #79
[13:51] <ogra_> and after all we can just blame asac ... since he wanted the alarms to work
[13:51] <seb128> not having call ringing as they should seems like an usability blocker
[13:51] <sil2100> ;)
[13:51] <davmor2> rsalveti: that definitely worked in 77
[13:51] <sil2100> hehe
[13:51]  * sil2100 likes the 'blame asac' strategy
[13:51] <asac> whats the problem?
[13:51] <davmor2> I'm wonder if it is the ota from 77 - 79 and the non-changing ringtone that is the issue maybe?
[13:52] <rsalveti> probably
[13:52] <davmor2> so I'll try that next
[13:52] <ogra_> seb128, its a usability "issue" ... wether it is a blocker lies in the eye of the beholder^WQA guy
[13:52] <rsalveti> let me flash 77 and see if I can indeed change rintone in there
[13:52] <ogra_> asac, rigntones sometimes dont repeat
[13:52] <ogra_> asac, and you seemingly can not change them in the settings
[13:53] <asac> ogra_: does that affect the default ringtone?
[13:53] <ogra_> yes
[13:53] <ogra_> sometimes it seems to ring only once and doesnt repeat
[13:53] <ogra_> even though the phone is still ringing
[13:53] <ogra_> but it isnt reliably reproduceable
[13:54] <ogra_> (and now not at all anymore if i see the above discussion)
[13:55] <ogra_> davmor2, i get the cracking on a promoted 71 when playing the tones from system-settings ... i dont think it is related at all
[13:55] <ogra_> rsalveti, ^^
[13:55] <ogra_> sounds simply like the amp powers off
[13:56] <sil2100> For me it sounds serious, but it makes me feel a bit more easy when I hear it being hard to reproduce - but I leave the final decision to QA as I guess Dave knows best if this is something unacceptable or not ;)
[13:56] <sil2100> He's got the experience
[13:58] <rsalveti> yeah, I get the cracking in system-settings as well
[13:59] <davmor2> ogra_, rsalveti: right that's one thing less then.  I'm reflashing 77 I'm going to leave the default ringtone in place and ota to 79
[14:23] <davmor2> ogra_, rsalveti: so leaving everything on default everything just works moving from 77-79 I'm now going to change the ringtone and seed what happens then
[14:26] <ogra_> davmor2, that sounds less serious though
[14:28] <davmor2> ogra_: remarkable less so but it might just be that the system is still basically fresh rather than used :(
[14:29] <seb128> shrug
[14:30] <seb128> ricmm, rsalveti, bregma: of course the platform-api silo updates make unity8-desktop-mir session stop working :/
[14:30] <rsalveti> thought that was tested
[14:30] <ogra_> is the silo done yet ?
[14:30] <seb128> no
[14:30] <seb128> rsalveti, who tested?
[14:30] <ogra_> i thought there were still rebuilds/changes needed
[14:30] <ricmm> thats not true, the silo has been tested by me and bregma
[14:30] <ogra_> due to the gcc issue
[14:30] <ricmm> unless something else has changed somewhere
[14:31] <davmor2> ogra_, rsalveti: okay so changing the ringtone in 77 and then upgrading to 79 presents the issue with the ringtone again
[14:31] <rsalveti> seb128: ricmm and bregma
[14:31] <seb128> ricmm, hum, maybe it's the current state? are rebuilds still ongoing?
[14:31] <ogra_> ricmm, you didnt test on a french system :)
[14:31] <davmor2> brb I need to go say hello to some people
[14:31] <rsalveti> davmor2: ok, the issue then an issue when retrieving the ringtone file when playing it I'd guess
[14:31] <rsalveti> as it gets changed by system-settings
[14:32] <seb128> ricmm, the unity8-mir.log ends on "Ubuntu Platform API: Unable to load selected model. -- Aborting"
[14:32] <ogra_> now i would like to know if that was broken in 71
[14:32] <ricmm> seb128: do you have ubuntu-application-api2-desktop installed?
[14:33] <ogra_> rsalveti, davmor2, i can reproduce it on 71 from the devel channel
[14:33] <ogra_> sil2100, ^^^
[14:33] <seb128> ricmm, no
[14:33] <ricmm> seb128: a proper upgrade should've replaced the old plugin with it
[14:33] <sil2100> ogra_: the no repeated ringing?
[14:33] <ricmm> according to our reviewed packaging, no?
[14:33] <ricmm> it certainly brought it in for me
[14:33] <ogra_> sil2100, yes, after chaning the ringtone once in system-settings
[14:33] <seb128> ricmm, I did a partial upgrade because of other things I didn't want to pull in, I guess unity8-desktop-mir-session could use some updated depends?
[14:34] <ogra_> sil2100, seems 78 and 79 are fine if you dont do that ... and seems it is reproducable in 71
[14:34] <ogra_> sil2100, so its an older bug we already promoted with
[14:34] <ricmm> seb128: did you update qtubuntu-desktop?
[14:34] <sil2100> NOTAREGRESSION
[14:34] <sil2100> Ship it
[14:34] <sil2100> ;D
[14:34] <ogra_> seb128, ricmm why dont you use the tools that only pull the ppa packages ?
[14:34] <ricmm> https://code.launchpad.net/~ricmm/qtubuntu/platform-api-v2/+merge/220722
[14:34] <ricmm> qtubuntu-desktop brings in the correct depedency
[14:35] <ricmm> so what happened on your system is that you probably did not upgrade qtubuntu-desktop, it is also a part of the ppa
[14:35] <ogra_> from the phablet-tools-citrain package
[14:35] <ricmm> ogra_: we like to live on the edge
[14:35] <ogra_> but you test crap is you use apt
[14:35] <ogra_> s/is/if/
[14:35] <ricmm> depends on how much attention you put to the upgrade list
[14:36] <ogra_> since it will mix up with archive packages/dependencies
[14:36] <ogra_> afaik the tools pull the debs and dpkg -i them
[14:36] <ricmm> as I just said, depends on how much attention to pay to the upgrade list
[14:36] <ogra_> so that you cant taint your install
[14:36] <ogra_> sure
[14:36] <seb128> ricmm, yeah, I didn't, ... did now, that resolved that error but I still get nothing to render our of the hardware cursor
[14:37] <rsalveti> ogra_: davmor2: alright, not my fault :P
[14:37] <ogra_> yeah
[14:37] <ogra_> definitely older than 71
[14:38] <ogra_> so we still can blame asac ... we just dont know for what since it is so long ago already :)
[14:38] <ricmm> seb128: do you have an error in the log?
[14:39] <asac> i take all the blame
[14:39] <ogra_> :)
[14:39] <ogra_> how did i knwo you would say that :)
[14:39] <asac> i will deflect it to some engineer that caused it though in the end :P
[14:39] <asac> so dont blame me for your own stuff :P
[14:39] <ogra_> pfft
[14:39] <asac> lol
[14:39] <ogra_> :)
[14:39] <ricmm> seb128: trying locally
[14:39] <seb128> ricmm, let me do a proper reboot to be sure, I had cases where Mir was in weird state until I powered off the machine
[14:40] <ricmm> rsalveti: silo updated for 4.8 seems to be working all fine on the tablet
[14:40] <ogra_> asac, so looks like we can after all promote the alarm fixes
[14:40] <ricmm> some manual + unity8 APs all passed
[14:40] <ricmm> rsalveti: do you want to take a look yourself?
[14:40] <rsalveti> ricmm: I can give it a shot
[14:40] <ricmm> that'd be great, thanks
[14:40] <rsalveti> but I'd guess you're ready to land it, right?
[14:40] <ricmm> if I can't repro seb's breakage, yes
[14:41] <seb128> ricmm, don't block the landing on desktop, it's not like it was usable/anyone relied on it yet
[14:41] <seb128> we can fix bugs with another landing
[14:42] <seb128> but we need to start getting it stable this cycle ;-)
[14:42] <sil2100> ogra_, davmor2: so in the end it got confirmed that this only happens once the ringtone gets changed at least once?
[14:42] <seb128> ricmm, the log is
[14:42] <seb128> "()
[14:43] <seb128> libEL: warning: unsupported platform (null)
[14:43] <ricmm> ???
[14:43] <asac> ogra_: so ringtone works?
[14:43] <ogra_> sil2100, right and i can reproduce it on 71
[14:43] <seb128> WARNING: Application was not created in the main() thread.
[14:43] <seb128> libEL: warning: unsupported platform (null)
[14:43] <seb128> "
[14:43] <ricmm> about to test anyways one sec
[14:43] <ricmm> you dont get more output?
[14:43] <ogra_> asac, no, but it is already broken on former promoted images
[14:43] <seb128> k
[14:43] <seb128> ricmm, no
[14:43] <asac> ok
[14:43] <asac> didnt get worse?
[14:43] <sil2100> asac: no :)
[14:43] <asac> oki
[14:43] <sil2100> Let's add a testcase for this, document the issue and promote
[14:44] <ogra_> asac, if you change it manually in the settings it will never repeat but only play once on incoming calls
[14:44] <asac> seems you guys know how to assess whether this is promote worthy or not
[14:44] <sil2100> davmor2: is there a bug for this already?
[14:44] <ogra_> sil2100, i doubt that, since we only found it today
[14:44] <ogra_> will be hard to trace back when that stated happeneing though
[14:45] <sil2100> Well, we didn't have a testcase (even manual) for that before, so I wouldn't block promotion on that
[14:46] <sil2100> The usual thing we should do in such cases is note a test case for this to ensure it's being tested for the future
[14:46] <sil2100> And try fixing it then
[14:46] <ogra_> right
[14:48] <ricmm> seb128: works for me
[14:48] <ricmm> =/
[14:48] <ricmm> have you updated things like Mir recently?
[14:48] <seb128> no
[14:48] <ricmm> if you havent, thats no good, this platform-api is rebuilt against latest Mir from utopic
[14:48] <seb128> let me ppa purge that one
[14:48] <ricmm> if you try to upgrade it explicitly it will try to bring 0.2.0 in
[14:49] <seb128> well, I was on utopic mostly uptodate
[14:49] <ricmm> this is just a guess
[14:49] <seb128> it worked
[14:49] <seb128> then I opted for the ppa
[14:49] <seb128> and it stopped working
[14:49] <ogra_> you want Mir 0.2.0 i guess
[14:49] <ricmm> you need everything thats in the PPA
[14:49] <ricmm> and Mir 0.2.0
[14:49] <ricmm> libmirserver20
[14:50] <ricmm> you cant test the ppa against a not-up-to-date utopic
[14:50] <ricmm> for example, yesterday gcc-defaults was 4.9
[14:50] <ricmm> today is 4.8
[14:50] <ricmm> tomorrow will probably be 4.9 again
[14:50] <ricmm> the flux is strong with this one :)
[14:51] <ricmm> ogra_: are you on up to date utopic?
[14:51] <ricmm> ogra_: care to give the ppa a try with u8 desktop session?
[14:51] <ogra_> on any desktop ? nope
[14:51] <ricmm> ah, nvm then
[14:51] <ogra_> laptop runs trusty, desktop precise
[14:51] <davmor2> sil2100: no I will file one now we know the cause
[14:51] <seb128> ricmm, the only thing which is not uptodate is GTK because I've 3.10-mir rather than 3.12 that landed in utopic
[14:51] <ogra_> davmor2, so any objections to promoting 79 ?
[14:51] <seb128> ricmm, but let me dist-upgrade in case that's an issue
[14:52] <ogra_> popey, ^^^^ same to you
[14:52] <davmor2> sil2100: also in that case 77 and 79 are as good as each other so you can promote either
[14:52] <popey> hmm?
[14:52] <popey> 79 seems good to me
[14:52] <popey> or at least no worse than previous images
[14:52] <ogra_> popey, thanks !
[14:52] <ogra_> sil2100, promoting then ...
[14:52] <popey> I have now switched my daily driver to -proposed
[14:52] <sil2100> davmor2: we could promote both, but not sure if that makes sense ;) #79 would be good in overall
[14:52]  * ogra_ tries to find a spare terminal
[14:53] <davmor2> sil2100: go with 79
[14:53] <ogra_> sil2100, yeah, only 79
[14:53] <davmor2> now then to file a bug and then start testing silo 020 for kgunn
[14:53] <ricmm> bregma: hey, are you around?
[14:54] <seb128> ricmm, ok, it started working after another power down cycle, go figure
[14:54] <bregma> ricmm, yep
[14:54] <seb128> ricmm, sorry for the noise :/
[14:54] <ricmm> no problem
[14:54] <seb128> I think the video might have been in a weird state
[14:54] <ricmm> bregma: nvm wanted a second opinion on seb's non starting u8
[14:54] <ricmm> but it seems to work now
[14:54] <ogra_> french ... as i said :)
[14:54] <ricmm> rsalveti: on your plate bro, publishedededed it
[14:54] <seb128> yeah, after a forced power down
[14:54] <ogra_> go go go °
[14:54] <ogra_> !
[14:58] <rsalveti> ricmm: cool, rebooting, will do a quick test and will happrovelandship
[14:58] <ricmm> happrovelandshipdone
[14:59] <ricmm> seb128: ready to sponsor NEWs ?
[14:59] <seb128> ricmm, yes
[14:59] <ricmm> awesome
[14:59] <sil2100> ricmm, rsalveti: do I hear correctly?! New papi v2 almost ready? :)
[14:59] <rsalveti> almost
[14:59] <ogra_> sil2100, nah ...
[14:59] <ogra_> :P
[15:00] <ricmm> I wouldnt put my money on it
[15:00] <ricmm> lol
[15:00]  * sil2100 trusts that all things were checked and no surprises will happen
[15:00] <ogra_> god
[15:00]  * ogra_ upgraded to 79 ... 
[15:00] <ogra_> and immediately got a notification for the phonedations standup !
[15:01] <ogra_> but i see no apps
[15:01] <ricmm> sil2100: dont put that kind of pressure on us
[15:01] <sil2100> hah!
[15:01] <ogra_> sil2100, my click scope is completely empty in 79
[15:01] <ogra_> davmor2, ^^^
[15:01] <sil2100> uh!
[15:02] <ogra_> all others are fine
[15:02] <ogra_> doesnt even have local apps listed
[15:02] <asac> anything came up or did we promote?
[15:02] <ogra_> oh, btw
[15:02] <davmor2> ogra_: I see apps in the apps scope
[15:02] <ogra_> [15:02] <sil2100> o/
[15:02] <ogra_> davmor2, well, i dont :P
[15:02] <sil2100> Yay
[15:02] <asac> ogra_: err... i didnt get a notifaction yet :)
[15:02] <davmor2> ogra_: open search and look for an app
[15:03] <ogra_> sil2100, davmor2, searching once helped
[15:03] <ogra_> still not so great
[15:03] <ogra_> asac, try harder ... i did :)
[15:03] <sil2100> NOTABUG, just ship it and stop finding problems!
[15:03] <sil2100> ;)
[15:03] <ogra_> the new statup animation looks weird with webapps
[15:03] <ogra_> very flashy
[15:04] <davmor2> sil2100: https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1329351
[15:08] <ogra_> davmor2, popey, do you guys get an app startup animations if there is already an app open ? i only get a black screen
[15:09] <ogra_> only the first app seems to trigger the actual animation
[15:09] <davmor2> .
[15:09] <davmor2> ogra_: how do you mean?
[15:09] <ogra_> the rotating triangle of dots
[15:10] <ogra_> i just started 4 webapps ... only the first one got me an animation
[15:10] <ogra_> the subsequent three just gave a black screen
[15:10] <davmor2> ogra_: yeah possibly because the browser is already open maybe?
[15:11] <ogra_> well, bug anyway :)
[15:11] <ogra_> but yeah, indeed there are other webapp-container apps running
[15:11] <davmor2> ogra_: so I just did facebook and gmail and got the animation on both
[15:11]  * ogra_ blames dbarth :P
[15:11] <ogra_> weird
[15:11] <davmor2> and again for twitter
[15:12] <rsalveti> ricmm: seems fine, will publish it
[15:12] <davmor2> and again for amazon
[15:12] <ogra_> i started with G+. then golem.de, heise.de and n-tv.de
[15:12] <elopio> ping Ursinha: I think that jenkins is not running the filemanager autopilot tests.
[15:12] <elopio> http://91.189.93.70:8080/job/ubuntu-filemanager-app-utopic-amd64-ci/51/?
[15:12] <elopio> can you help me finding out why?
[15:12] <ogra_> only G+ got me the animation
[15:12] <Ursinha> elopio: let me have a look
[15:12] <davmor2> I wonder if it is installed apps verses default I was only trying default apps I haven't set the phone up yet
[15:13] <ogra_> davmor2, and i can reproduce it with only G+ and golem.de ... the second app doesnt get the animation
[15:13] <davmor2> ogra_: now try gmail and twitter
[15:14] <ogra_> if gmail ever starts
[15:14] <ogra_> davmor2, yeah, works for them
[15:15] <davmor2> ogra_: so I wonder if the way the installed ones are called differently to the default ones
[15:16] <ogra_> no, thats not the pattern it seems
[15:16] <ogra_> others work fine too
[15:16] <ogra_> oh !
[15:16] <ogra_> i have all apps in my launcher
[15:16] <ogra_> and strted them from there
[15:16]  * ogra_ tries from the app scope
[15:17] <sil2100> robru: no worries, my pings were about the spreadsheet ;)
[15:17] <sil2100> robru: like, did you use the backups or not, since this shouldn't result in us loosing anything
[15:17] <ogra_> davmor2, yeah, starting the apps from the launcher is the issue here
[15:18] <davmor2> ogra_: okay so that is where your bug lies let me see if I can reproduce it
[15:19] <ricmm> rsalveti: awesome, thanks
[15:19]  * ogra_ removes all apps he added manually from the launcher
[15:20] <ogra_> crap
[15:20] <ogra_> now my session died
[15:20] <davmor2> ogra_: ouch so open app 1 from the launcher, while it has the animation page is running open a second app from the launcher
[15:21] <sil2100> davmor2: thanks for the bug!
[15:21] <ogra_> davmor2, lovely
[15:21] <ogra_> looks like the launcher still needs some love
[15:22] <ogra_> ugh
[15:22] <seb128> you people stop opening bugs against settings
[15:22] <ogra_> and session crashed again
[15:22] <ogra_> damned
[15:22] <seb128> the settings only write a gsettings key for the ringtone
[15:22] <ogra_> thats not really stable
[15:22] <davmor2> ogra_: pleasure
[15:22] <seb128> how can that bug be a settings one?
[15:22] <robru> sil2100, no i didn't use the backup, wasn't sure how to restore it
[15:22]  * ogra_ reboots ... thats why to crashy 
[15:23] <davmor2> seb128: feel free to move it it's just the thing I interact with to make the change
[15:23] <sil2100> robru: I would only use it as a manual helper to restore the missing items
[15:24] <seb128> seems like Laney beat me to that
[15:24] <seb128> davmor2, can you reply to his comment?
[15:24] <seb128> so we can reassign to the service
[15:24] <dbarth> ogra_: is that a webapp issue that lack of animation
[15:25] <dbarth> (having a hard time catching up with the latest and greatest)
[15:25] <asac> now i cannot set the alarm
[15:25] <asac> clock app is broken?
[15:25] <ogra_> dbarth, well, i only have it in webapps ... but apparently only for some that i place in the launcher and start from there
[15:25] <asac> i edit the alarm, but then i can only change the hour
[15:25] <asac> no way to change the minute
[15:26] <ogra_> sigh
[15:26] <ogra_> crached again
[15:26] <dbarth> that may be an api we're not calling yet
[15:26] <ogra_> i cant use my phone for more than ten minutes in a row
[15:26] <dbarth> but which qml apps call bydefault
[15:26] <sil2100> uh
[15:26] <ogra_> dbarth, i doubt its your fault
[15:26] <ogra_> dbarth, it works fine if i start the apps from the apps scope ... it doesnt when i start from the launcher
[15:27] <ogra_> but its only webapps that behave like this though
[15:27] <dbarth> ok
[15:27] <dbarth> file a bug if it gets confirmed it's a webapp only thing
[15:30] <sil2100> rsalveti: yeah, so the publishing fails because the build job basically didn't succeed
[15:30] <sil2100> rsalveti: as there are some archs that failed I guess?
[15:31] <davmor2> seb128: done and moved
[15:31] <rsalveti> sil2100: weŕ e on it already
[15:31] <rsalveti> we're
[15:31] <seb128> davmor2, thanks
[15:35] <Ursinha> elopio: so, the tests are being run in another job: http://91.189.93.70:8080/job/ubuntu-filemanager-app-ci/ -> http://91.189.93.70:8080/job/generic-mediumtests-utopic/
[15:36] <elopio> Ursinha: ah, I see them now. Thanks.
[15:37] <Ursinha> elopio: no problem. Sorry taking a few to reply, I'm yet figuring out the jenkins labyrinth
[15:38] <elopio> Ursinha: don't worry, it's the same to me :)
[16:01] <ogra_> hmpf ... stopping a notification still plays the tune to the end
[16:01] <ogra_> thats annoying
[16:03] <rsalveti> ogra_: something is broken in there
[16:03] <rsalveti> might just be the notification itself
[16:03] <ogra_> well, at least it doesnt go on looping it :)
[16:04] <davmor2> ogra_: I blame rsalveti bound to be his fault ;)
[16:04] <ogra_> but yeah, the tone is very long for a simple notification
[16:15] <dbarth> sil2100: still around? i had to change the branch in silo 014 (to fix the conflict), could you reconf. the silo please?
[16:18] <sil2100> dbarth: still here, reconfiguring :)
[16:18]  * sil2100 stays around late now usually, even more during UOS
[16:22] <dbarth> ah cool, thx
[16:34] <robru> SRUs! bregma you got silo 10, seb128 you got silo 3
[16:34] <seb128> robru, thanks
[16:34] <robru> seb128, you're welcome!
[16:36] <robru> ricmm, yeah, it was 2AM when you pinged me ;-) Still need my help?
[16:37] <ricmm> robru: nop :) thank you
[16:37] <robru> ricmm, you're welcome!
[16:41]  * sil2100 didn't assign the SRU ones because SRUs are bad silos
[16:41] <sil2100> They tend to linger for ages ;)
[16:59] <robru> sil2100, yeah, I know, but they have to happen sooner or later.
[16:59] <sil2100> SRUs are soo last year
[16:59]  * seb128 slaps sil2100
[16:59] <sil2100> :<
[17:00] <sil2100> ;)
[17:00] <seb128> sil2100, we got the hud and unity-settings-daemon reviewed/approved and I M&C my silo when that happened
[17:00] <seb128> so we can get a few new SRU in exchange ;-)
[17:00] <sil2100> Indeed ;) I was also happy seeing hud in -proposed finally, since it's been a while!
[17:01] <ogra_> "a few" ...
[17:01] <seb128> ogra_, a bunch of you prefer?
[17:01] <seb128> don't start nitpicking !
[17:02] <ogra_> trading one for "a few" ... :P
[17:02] <ogra_> doesnt sound like a good deal
[17:02] <robru> ricmm, wow congrats on publishing 7!
[17:02] <robru> see we have a new free silo right away here ;-)
[17:03] <ogra_> oh, did it happen ?
[17:03] <ogra_> yay
[17:03] <seb128> nice
[17:03] <rsalveti> seb128: sil2100: ogra_: ricmm: plat v2 just landed
[17:03] <robru> rsalveti pulled the trigger
[17:03] <seb128> \o/
[17:03] <rsalveti> just need to new the packages
[17:03] <seb128> rsalveti, well done sir
[17:03] <sil2100> rsalveti: \o/
[17:03] <ogra_> hooray \o/
[17:03] <seb128> rsalveti, I'm on it
[17:03] <sil2100> Woohooo!
[17:03]  * ogra_ dances
[17:03] <rsalveti> now we see the world explode while I watch the initial world cup game
[17:03] <rsalveti> :P
[17:03] <seb128> lol
[17:04] <ogra_> rsalveti, i wont watch the image while doing that :P
[17:04] <ogra_> work is to distracting
[17:04] <sil2100> rsalveti: ;) I trust in you and ricmm! *puts more pressure on both landers*
[17:04] <robru> hah, well we can promote 79 right? no need for traincon when p-api v2 explodes
[17:04] <sil2100> robru: it's promoted already
[17:04] <seb128> sil2100, does it mean we can get a silo for l18?
[17:04] <ogra_> robru, you are so behind over there in canada
[17:04] <ogra_> robru, 79b was promoted ;)
[17:04] <ogra_> -b
[17:04] <robru> hey I just woke up ;-)
[17:04] <robru> and there was no meeting this morning to tell me anything!
[17:04] <ogra_> :)
[17:05] <sil2100> seb128: I already see a silo for this one - just be sure to rebuild once papi v2 lands in the archive
[17:05]  * sil2100 is in the middle of writing the e-mail
[17:05] <sil2100> Since there was a lot distractions today
[17:05] <ogra_> yeah
[17:05] <robru> seb128, line 18 has a silo, did you mean a different line?
[17:05] <robru> seb128, (line numbers aren't permanent)
[17:05] <ogra_> but we found a lot of new wonderful bugs :)
[17:06] <seb128> robru, oh, so it has ... no I though it didn't, because unity8-desktop-session was in the platform-api landing and there is a comment saying "locked by"
[17:06] <ricmm> is the NEW'ing process long?
[17:07] <seb128> I guess it needs a rebuild, once the changes are merged back in trunk
[17:07] <seb128> ricmm, no
[17:07] <robru> seb128, yep, needs a rebuild
[17:07] <robru> brb guys, gotta eat breakfast during UOS lunch break
[17:07] <seb128> but after than the other changes are in trunk, right?
[17:10] <robru> seb128, yeah
[17:10] <seb128> k, makes sense, thanks
[17:41] <popey> gah, phone red hot. can't adb shell in, can't do anything, had to hard reboot
[17:42] <mdeslaur> pocket warmer mode
[17:42] <sil2100> popey: on the promoted image?
[17:42] <popey> yes
[17:42] <sil2100> popey: do you know what happened?
[17:42] <popey> well no.
[17:43] <ogra_> blame the greeter ... and low ram conditions
[17:43] <sil2100> Did you do anything specific? Let's hope this will stop happening after the greeter revert
[17:43] <ogra_> might have started swapping ...
[17:43] <popey> i expect so
[17:43] <popey> i had ~3 or 4 apps open
[17:43] <ogra_> i had two session crashes right after OTA
[17:44] <ogra_> but since then it is stable with 4 webapps constantly open
[17:44] <popey> it also seems to think the battery is dead
[17:45] <popey> yet it's been on charge most of the day, it's drawing 0.5A
[17:45] <popey> maybe going red hot sapped the battery a lot
[17:45] <popey> hah, battery gauge has gone from dead (0:00) to (0:01) to (unknown) ☻
[17:46] <popey> sil2100: I had calendar and i think bbc news webapp open
[17:47] <popey> oh and dialer and messaging app too
[18:16] <sil2100> mandel: ah! Aaaand it seems because of all this work I forgot double-checking the symbols in your leak-symbols branch
[18:16] <sil2100> mandel: can I get to you with that tomorrow?
[18:31] <charles> rsalveti, ogra_, looks like I picked the wrong morning to be gone
[18:32] <charles> looking at scrollback now, did the alarm issue get resolved and if so, how?
[18:40] <robru> boiko, you got silo 1, but just be advised that your telephony-service conflicts with the almost-but-not-quite-landed silo 7, so you'll need to rebuild after that one gets merged
[18:41] <boiko> robru: ok, let me see what's in silo 7
[18:41] <boiko> robru: ah, the platformv2, ok
[18:41] <robru> yeah
[18:42] <boiko> robru: is that getting close to land?
[18:42] <robru> boiko, yeah, it's published already, just migrating through -proposed right now. will probably be ready in a couple hours assuming all goes well
[18:43] <robru> actually it already says Valid Candidate, might be ready sooner
[18:43] <boiko> robru: that's fine, I will take care of that after the game then :D
[18:43] <robru> boiko, great ;-)
[18:46]  * ricmm back
[18:48] <ricmm> seb128: hi seb, did you manage to take a look at the new ?
[18:50] <robru> ricmm, I think he did, silo status shows everything is in -proposed (if he hadn't it should say NEW queue). also proposed_excuses says everything is valid, so it should land in distro very shortly
[18:51] <ricmm> robru: super-awesome
[18:51] <ricmm> wasnt too sure what the steps for new through CI were, thanks for clarifying
[18:51] <ricmm> and yea, I did see it as valid in the excuses
[18:51] <ricmm> so I guess it will migrate on its own
[18:51] <ricmm> DONE
[18:52] <sil2100> o/
[18:52] <robru> ricmm, haha, yup!
[18:53] <robru> now we just need to ram qt 5.3 through... ;-)
[18:53] <ricmm> qt 5.3 is not that terrible
[18:53] <ricmm> only like 20 bugs
[18:53] <ricmm> ;)
[18:53] <robru> hehe
[18:55] <sil2100> robru: that later ;)
[18:55] <sil2100> robru: first the greeter revert!
[18:55] <robru> sil2100, yeah, greeter revert is important, but it's only 2 MPs. the qt5.3 silo is *huge*, it just boggles...
[19:02] <davmor2> ricmm: man that less than platform-api land it now ;)
[19:08] <ricmm> davmor2: technically platform-api didnt have bugs, maybe like 2, fixed 2 weeks ago
[19:09] <ricmm> this was more the work of dark forces
[19:10]  * charles crosses himself
[19:10] <ogra_> with roller skates on a surface full of pebbles :)
[19:10] <ogra_> (everything underneath you moving in all directions all the time)
[19:21] <jdstrand> I tried upgrading to 79. it said it downloaded and then I click 'Install and Restart'. it then restarted but it still shows as 71
[19:23] <pmcgowan> jdstrand, I have seen that in the past but it was like sun spots
[19:23] <pmcgowan> usually doing it again worked
[19:23] <jdstrand> I tried. same things
[19:23] <jdstrand> thing
[19:23] <pmcgowan> hmm
[19:24] <jdstrand> when I retry, it finds the previous download and just prompts to Install and Restart
[19:25] <pmcgowan> thats different then, not good
[19:25] <jdstrand> oh, guess third time is the charm
[19:25] <jdstrand> I see the swirling logo this time
[19:25] <pmcgowan> jdstrand, did you enter the update page the same way each time?
[19:25] <pmcgowan> I have seen different behavior with the two ways in
[19:26] <jdstrand> yes. system-settings, then at the top it said I had updates. tapped it
[19:26] <pmcgowan> ok
[19:26] <pmcgowan> no idea
[19:26] <pmcgowan> racey, we need diego back on the case
[19:26] <seb128> ricmm, rsalveti: so, britney seems unhappy with the platform-api transition, did anyone look at why yet?
[19:26] <ricmm> seb128: where to see the error?
[19:26] <seb128> ricmm, http://people.canonical.com/~ubuntu-archive/proposed-migration/update_output.txt
[19:27] <rsalveti> let me look
[19:27] <seb128>     * i386: edubuntu-desktop, indicator-datetime, qthybris, qtubuntu-android, ubuntu-desktop, ubuntu-desktop-next, ubuntu-touch, unity-control-center, unity-control-center-signon, unity-control-center-signon-autopilot, webaccounts-chromium-extension, webaccounts-extension-common, xul-ext-webaccounts
[19:27] <seb128> so it's claiming those are made uninstallable by the update
[19:27]  * seb128 fires pbuilder to test
[19:28] <seb128> indicator-datetime qthybris xul-ext-webaccounts looks like potential "bottom" ones
[19:28] <seb128> things like unity-control-center are going to be fallout of the indicator
[19:31] <ricmm> qtubuntu-android being uninstallable?
[19:31] <ricmm> I dont see a reason for that, unless it being unable to find ubuntu-application-api2-touch
[19:34] <seb128> ricmm, hum, I wonder if it tries to co-install ubuntu-desktop-next and qtubuntu-android
[19:34] <seb128> those conflicts
[19:34] <ricmm> whats ubuntu-desktop-next?
[19:34] <seb128> because the first tries to pull in qtubuntu-desktop which conflicts with qtubuntu-android
[19:34] <seb128> ricmm, the unity8-desktop-mir session
[19:35] <seb128> I might be reading that wrong though
[19:35] <seb128> that page is difficult to parse :/
[19:35] <ricmm> its tough yea
[19:36] <ricmm> rsalveti: are you really looking at it? considering its T-25min
[19:36] <seb128> trying: indicator-location
[19:36] <seb128> skipped: indicator-location (0 <- 353)
[19:36] <seb128>     got: 34+0: i-34
[19:36] <seb128>     * i386: indicator-location, ubuntu-desktop-next, ubuntu-touch
[19:36] <seb128> but that's earlier in the pag
[19:36] <seb128> having cjwatson or stgraber or Laney or infinity around would help, they know how to parse that better
[19:37]  * seb128 tries to poke around in pbuilder by installing things listed as non installable
[19:37] <ricmm> perhaps stgraber
[19:37] <rsalveti> yeah, easier to try with pbuilder
[19:37] <seb128> well, I sort of pinged the people who I though could help there
[19:41] <ricmm> well if you do try to install both it will complain
[19:41] <ricmm> but I dont see why it would block on installing both?
[19:42] <ricmm> those package relationships havent changed
[19:42] <seb128> yeah, I guess it's not the issue
[19:42] <ricmm> indicator-location installs with either of them
[19:43] <ricmm> so not sure what that paste before meant :(
[19:43] <ricmm> need a parser, lets just wait for that
[19:43] <seb128> yeah, the first entries are partial set tries
[19:44] <seb128> the bottom one has
[19:44] <seb128> leading: platform-api,unity-mir,location-service,powerd,indicator-location,qtubuntu,qtubuntu-camera,telephony-service,qtubuntu-sensors
[19:44] <seb128> which means those are tried together
[19:44] <seb128> but they lead to the
[19:44] <seb128>     * i386: edubuntu-desktop, indicator-datetime, qthybris, qtubuntu-android, ubuntu-desktop, ubuntu-desktop-next, ubuntu-touch, unity-control-center, unity-control-center-signon, unity-control-center-signon-autopilot, webaccounts-chromium-extension, webaccounts-extension-common, xul-ext-webaccounts
[19:44] <seb128> which means somewhat britney thinks the update is going to make those binaries not installable
[19:45] <ricmm> individually?
[19:45] <seb128> yes
[19:45] <seb128> slangasek is done doing his wrapup summary, he might be able to help us ;-)
[19:45] <ricmm> :)
[19:46] <boiko> robru: so, what happens with silo 7 now that libdbusmenu is in the unapproved queue?
[19:46] <boiko> robru: regarding silo 1 (which has a telephony-service change)
[19:46] <robru> boiko, well you can build telephony-service now but you will have to rebuild it later once silo 7 finishes landing
[19:47] <boiko> robru: ok, I think I'll do that
[19:47] <slangasek> seb128, robru: yo; what's the question?
[19:47] <seb128> slangasek, we need help reading/debugging http://people.canonical.com/~ubuntu-archive/proposed-migration/update_output.txt
[19:47] <robru> slangasek, what he said
[19:48] <slangasek> seb128: which package are we trying to get in?
[19:48] <seb128> slangasek, the platform-api transition
[19:48] <seb128> Trying easy from autohinter: platform-api/2.0.0+14.10.20140612-0ubuntu1 unity-mir/0.4+14.10.20140612-0ubuntu1 location-service/0.0.3+14.10.20140612-0ubuntu1 powerd/0.15+14.10.20140612-0ubuntu1 indicator-location/13.10.0+14.10.20140612-0ubuntu1 qtubuntu/0.54+14.10.20140612-0ubuntu1 qtubuntu-camera/0.3.3+14.10.20140612-0ubuntu1 telephony-service/0.1+14.10.20140612.1-0ubuntu1 qtubuntu-sensors/0.6+14.10.20140612-0ubuntu1
[19:48] <seb128> ups
[19:48] <seb128> slangasek, ^
[19:48] <slangasek> ok, looking
[19:48] <seb128> slangasek, I've been trying to co-install things in pbuilder but it works
[19:48]  * sil2100 waves
[19:48] <seb128> trying to install qtubuntu-android an qtubuntu-desktop doesn't work, but I don't see why britney would try those together
[19:52] <ricmm> across all packages the only dep change is that qtubuntu-desktop depends on ubuntu-application-api2-desktop
[19:52] <ricmm> and the opposite for -android
[19:52] <ricmm> seb128: slangasek ^
[19:52] <ricmm> but I still dont see why that would cause further issues
[19:53] <slangasek> we may have to unpick these one at a time
[19:53] <slangasek> indicator-datetime is very strange - did something add a conflict on it?
[19:53] <ricmm> nop
[19:54] <ricmm> I need to feed some people here... but I'll check as soon as I can
[19:54] <seb128> slangasek, the log has, a bit earlier
[19:54] <seb128> trying: indicator-location
[19:54] <seb128> skipped: indicator-location (0 <- 353)
[19:54] <seb128>     got: 34+0: i-34
[19:54] <seb128>     * i386: indicator-location, ubuntu-desktop-next, ubuntu-touch
[19:54] <seb128> but I guess a subset is not useful information?
[19:56] <seb128> slangasek, hum, indicator-datetime depends on libubuntu-platform-hardware-api1 though
[19:56] <seb128> but that transition has changed soname to libubuntu-platform-hardware-api2
[19:57] <cjwatson> no point looking at earlier entries - use the first one from the autohinter, ignore earlier
[19:57] <seb128> # apt-get install indicator-datetime libubuntu-platform-hardware-api1-
[19:57] <seb128>  indicator-datetime : Depends: libubuntu-platform-hardware-api1 (>= 1.2.0+14.10.20140522.1) but it is not going to be installed
[19:57] <seb128>  
[19:57] <seb128> needs rebuild for the new soname?
[19:57] <cjwatson> britney assumes that NBS from the updates e removed
[19:57] <cjwatson> sothat sounds plausible
[19:58] <cjwatson> apologies for typing, using phone
[19:58] <slangasek> oh indeed, I was looking at showsrc by mistake
[19:58] <seb128> cjwatson, slangasek: so I try a no-change rebuild of indicator-datetime to pick the new libubuntu-platform-hardware-api soname?
[19:58] <slangasek> yeah, indicator-datetime needs a no-change rebuild
[19:58]  * seb128 tries
[20:00] <seb128> cjwatson, slangasek: thanks
[20:02] <seb128> ricmm, rsalveti, tedg: uploaded an indicator-datetime no change rebuild, I think that depends got introduced with the landing ted did yesterday, so it was missing for the silo
[20:04] <slangasek> however, I don't see why qtubuntu-android is uninstallable here
[20:04] <tedg> seb128, Oh, okay. Is it really no change?
[20:04] <tedg> seb128, I thought we'd have to change a build dep ,no?
[20:05] <slangasek> ah, qtubuntu-android is libubuntu-application-api1 -> libubuntu-application-api2
[20:05] <seb128> tedg, they did dummy transitionnal packages
[20:05] <slangasek> so does qtubuntu-android also need a no-change rebuild?
[20:05] <tedg> seb128, Ah, I see, but we should change it for real in the next silo for datetime then.
[20:06] <tedg> charles, FYI ^ next time we open up datetime.
[20:06] <seb128> tedg, yes, I just went for the trivial option to unblock that migration
[20:07] <charles> ack
[20:08] <seb128> slangasek, weird, https://launchpad.net/ubuntu/utopic/+source/qtubuntu/0.54+14.10.20140612-0ubuntu1 ... it was in the silo
[20:08] <slangasek> which were the dummy transitional packages?
[20:08] <slangasek> seb128: ah, but perhaps it's being held back
[20:09] <slangasek> seb128: oh; no, somebody changed the package to now build only on armhf
[20:10] <cjwatson> qtubuntu-android comes from qtubuntu-gles on i386/amd64
[20:10] <cjwatson> and I don't see qtubuntu-gles in that autohinter list
[20:10] <slangasek> ah
[20:10] <seb128> those archs should use qtubuntu-desktop now I guess
[20:10] <cjwatson> nor anywhere in -proposed
[20:10] <slangasek> no, qtubuntu-android still needs to exist on x86
[20:10] <seb128> hum, right
[20:10] <slangasek> e.g. for the emulator
[20:11] <slangasek> but maybe the source package was missed in the silo because it's x86-only
[20:11] <seb128> likely, people to check on the archs they use
[20:11] <slangasek> anyway, that probably needs a trivial update
[20:11] <seb128> let me try
[20:11] <cjwatson> qtubuntu-android/i386 depends: libubuntu-application-api1
[20:11] <seb128> I'm in a x86 pbuilder
[20:11] <cjwatson> so needs a no-change rebuild
[20:12] <seb128> cjwatson, thanks
[20:12] <cjwatson> pbuilder won't show this because it doesn't filter out NBS from things in -proposed
[20:12] <seb128> cjwatson, well, I was speaking about trying a rebuild
[20:12] <cjwatson> unfortunately that sort of thing needs manual analysis or a transition tracker
[20:12] <cjwatson> oh sure
[20:13] <cjwatson> unity-control-center etc. is something else though
[20:14] <seb128> they are indicator-datetime rdepends
[20:14] <cjwatson> oh, that's indicator-datetime
[20:14] <cjwatson> right
[20:14] <cjwatson> so aye, indicator-datetime + qtubuntu-gles should do it
[20:19] <seb128> ricmm, rsalveti: qtubuntu has code/packaging changes, do those need to be copied to qtubuntu-gles?
[20:19] <seb128> http://launchpadlibrarian.net/177500145/qtubuntu_0.54%2B14.10.20140526.1-0ubuntu1_0.54%2B14.10.20140612-0ubuntu1.diff.gz
[20:22] <robru> seb128, yes, I believe so, -gles needs to be kept in sync
[20:23] <seb128> yeah, no change rebuild fails to build
[20:24] <seb128> but I need to go for a bit...
[20:24] <robru> seb128, wait
[20:24] <seb128> if somebody want to work at that, please do, otherwise I'm going to look at it later
[20:24] <robru> seb128, should I apply that diff to -gles and upload to the silo? or somewhere else?
[20:24] <seb128> robru, ideally to utopic
[20:24] <robru> seb128, right, but I don't have upload rights :-P
[20:25] <seb128> no need of a silo there
[20:25] <seb128> right, but I'm sure you can find people who have to sponsor it for you
[20:25] <seb128> like rsalveti or slangasek
[20:25] <robru> seb128, alright, I'll do it in a sec then.
[20:25] <seb128> bbl
[20:31] <slangasek> yeah, AFAIK the silo doesn't help since that only tests on armhf anyway
[20:42] <robru> slangasek, hey if I make this diff will you be around to sponsor it shortly?
[20:44] <slangasek> robru: yes
[20:44] <robru> cool, th
[20:44] <robru> thx
[20:58] <robru> ugh, gotta update my pbuilder
[21:08] <robru> slangasek, alright, got this diff, confirmed it builds in pbuilder. what's the best way to do this? put it in my ppa?
[21:08] <robru> i think putting it in the silo would be best, then all the pieces are in one place
[21:11] <slangasek> robru: an MP on the UDD branch?
[21:11] <robru> ahhh UDD... ok
[21:12] <cjwatson> the silo doesn't really gain us anything here; package that doesn't do anything on armhf anyway, plus the packages are already migrating to the primary archive
[21:12] <cjwatson> just extra overhead+time
[21:12]  * slangasek nods
[21:12] <robru> just that it's easy for me to upload things there, that's all.
[21:13] <slangasek> well, if you intend to upload it to the silo and publish from there without a sponsor, that's one thing :)
[21:14] <robru> slangasek, no i was expecting you to pocket copy it from there
[21:14] <slangasek> but if you're looking for a sponsor, an MP and a sponsored upload direct to the archive is better
[21:17] <robru> ugh.... how do I push a UDD branch?
[21:17] <robru> $ bzr push lp:~/ubuntu/qtubuntu-gles/platform-api-v2-sync
[21:17] <robru> bzr: ERROR: Invalid url supplied to transport: "lp:~/ubuntu/qtubuntu-gles/platform-api-v2-sync": No such distribution series qtubuntu-gles.
[21:17] <robru> $ bzr push lp:~/qtubuntu-gles/platform-api-v2-sync
[21:17] <robru> bzr: ERROR: Permission denied: "~robru/qtubuntu-gles/platform-api-v2-sync/": : Project 'qtubuntu-gles' does not exist.
[21:17] <cjwatson> lp:~/ubuntu/utopic/qtubuntu-gles/platform-api-v2-sync
[21:17] <robru> ah
[21:19] <robru> ok
[21:19] <robru> slangasek, https://code.launchpad.net/~robru/ubuntu/utopic/qtubuntu-gles/platform-api-v2-sync/+merge/222998 if you please
[21:21] <slangasek> robru: ok, will be a couple of minutes
[21:21] <robru> slangasek, no worries, I have a meeting shortly
[21:23] <robru> cjwatson, was this the only bit? if I understood correctly indicator-location got away with a no change rebuild?
[21:23] <robru> datetime rather
[21:30] <slangasek> robru: those were the only bits we saw, yes
[21:30] <robru> slangasek, right but, do I need to do an MP for datetime as well, or was that one taken care of already?
[21:30] <slangasek> I thought someone did the no-change upload for that already
[21:30] <slangasek> you can probably check current update_output to see
[21:32] <robru> it's still listed in the platform-api stanza
[21:33] <slangasek> alright, I'll have a closer look once I'm done with this review
[21:47] <slangasek> robru: diff looks good, source doesn't want to build because there's no orig.tar.gz for this upstream version; did you prepare one?
[21:47] <robru> slangasek, sure didn't.
[21:48] <robru> maybe my version should have been 0ubuntu2 or something
[21:48] <slangasek> I wonder if the tarball should be identical to the qtubuntu one
[21:48] <robru> slangasek, no, i don't think so, but it should be identical to the previous version
[21:49] <slangasek> robru: actually, I think the tarballs *should* be identical
[21:49] <slangasek> (and if I use it, I get zero upstream diff)
[21:49] <robru> slangasek, well, maybe check that before steamrolling over rsalveti's work
[21:49] <robru> oh ok
[21:51] <slangasek> robru: uploaded
[21:51] <robru> slangasek, thanks!
[21:53] <cjwatson> robru: I didn't do a mechanical analysis so I might have made a mistake, but yeah it looked like everything
[21:54] <cjwatson> indicator-datetime has an hour-old upload in the release pocket, which is pretty suspicious
[21:54] <cjwatson> https://launchpad.net/ubuntu/utopic/armhf/indicator-datetime/13.10.0+14.10.20140611-0ubuntu2 doesn't seem to actually use the new ABI
[21:55] <cjwatson> it has an explicit build-dep on libplatform-hardware-api1-dev
[21:55] <cjwatson> needs a sourceful change to switch to the new -dev packages
[21:55] <cjwatson> possibly should be libubuntu-platform-hardware-api-dev instead?  just guessing
[21:56] <seb128> yeah, it picked libplatform-hardware-api1-dev from the release pocked rather than the proposed version ... is that normal?
[21:56] <seb128> libplatform-hardware-api1-dev is a dummy transition in the new platform-api version
[21:56] <cjwatson> huh, no, I may be misunderstanding
[21:57] <seb128> Get:356 http://ftpmaster.internal/ubuntu/ utopic/main libplatform-hardware-api1-dev i386 1.2.0+14.10.20140605-0ubuntu1 [1980 B]
[21:57] <cjwatson> I'm pretty puzzled by that build log
[21:57] <cjwatson> it must not have been able to resolve the build-deps using the newer version ...
[21:57] <seb128> new binaries in universe I bet
[21:58] <cjwatson> but it works fine in a simulation here
[21:58] <seb128> or indicator-datetime is in main
[21:58] <seb128> so the transitionnal didn't resolve
[21:58] <cjwatson> oh, yeah
[21:58] <cjwatson> when I restrict to main the simulation produces the same results
[21:58] <seb128> that keeps biting use on copies, since things don't get through binNEW
[21:58] <boiko> robru: so, in the end telephony-service won't build, as platform-api v2 already landed in the archive
[21:58]  * cjwatson runs "change-override -s utopic-proposed -c main -y libplatform-api-headers libplatform-api1-dev libplatform-hardware-api-headers libplatform-hardware-api1-dev libubuntu-application-api-dev libubuntu-application-api-doc libubuntu-application-api-headers libubuntu-application-api2 libubuntu-platform-hardware-api-dev libubuntu-platform-hardware-api-headers libubuntu-platform-hardware-api2 ubuntu-application-api2-desktop ubuntu-applica
[21:58] <seb128> we don't get to pick where the binaires land
[21:59] <cjwatson> seb128: yeah, I have a partially-finished branch to fix that
[21:59] <cjwatson> https://code.launchpad.net/~cjwatson/launchpad/copies-respect-new/+merge/221529
[21:59] <boiko> robru: I'll have to wait
[21:59] <seb128> cjwatson, great
[21:59] <seb128> cjwatson, so, need another no change rebuild after next publisher run?
[21:59] <robru> boiko, really?
[21:59] <cjwatson> the ancestry calculation is buggy there so I need to spend some more time on it
[21:59] <boiko> robru: seems so, let me get the failure
[21:59] <cjwatson> seb128: right, check that rmadison reports the binaries in main first
[21:59] <seb128> right
[22:00] <boiko> robru: https://launchpadlibrarian.net/177512791/buildlog_ubuntu-utopic-armhf.telephony-service_0.1%2B14.10.20140612-0ubuntu1_FAILEDTOBUILD.txt.gz
[22:00] <robru> boiko, oh weird
[22:00] <robru> that must be related to this whole thing
[22:00] <robru> boiko, yeah we're working on it. slangasek just uploaded my fix
[22:00] <boiko> robru: nice! thanks
[22:00] <rsalveti> robru: slangasek: thanks, was watching the world cup
[22:00] <rsalveti> brazil won at least :P
[22:01] <cjwatson> boiko: yeah, (get somebody to) retry that after my overrides change above lands
[22:01] <cjwatson> should work then
[22:02] <cjwatson> boiko: no need to reupload, somebody in either ~ci-train-ppa-service or ~launchpad-buildd-admins can retry those builds
[22:02] <robru> cjwatson, when is that going to land?
[22:05] <cjwatson> robru: end of next publisher run - I would guesstimate about 20 minutes from now
[22:05] <boiko> cjwatson: ok ,thanks
[22:06] <robru> cjwatson, ah great. ok I'll take a late lunch and come back and retry that
[22:06]  * cjwatson itches for the apt-ftparchive source caching work to be done
[22:07] <cjwatson> oh, it'll probably be less than that, the most recent proposed-migration run didn't copy anything into release
[22:07] <cjwatson> which puts it at more like five minutes from now
[22:14] <robru> cjwatson, ugh, sorry, so what happened with indicator-datetime? does it need another rebuild?
[22:15] <rsalveti> I'm migrating to plat v2
[22:15] <cjwatson> robru: will do shortly
[22:15] <rsalveti> using the right packages, but we should have a transitional packages for the current dependencies
[22:15] <cjwatson> hm, oh, haha, I think rmadison is lagging behind because the previous proposed-migration run is slow and has locked the mirror
[22:16] <cjwatson> should be nearly done though ...
[22:16] <cjwatson> amusing when p-m takes longer than the publisher!
[22:16] <robru> cjwatson, congrats on making the publisher so fast ;-)
[22:17] <rsalveti> robru: mind getting a silo for line 41?
[22:19] <robru> rsalveti, ok, you got 15
[22:19] <cjwatson> there, have retried telephony-service/armhf
[22:19] <rsalveti> robru: thanks
[22:19] <robru> cjwatson, nooooo
[22:19] <cjwatson> let's see if that actually resolves build-deps now, then we can try indicator-datetime again
[22:19] <cjwatson> why not?
[22:19] <robru> cjwatson, it just needs to be rebuilt after the one in proposed lands anyway
[22:20] <robru> was hoping we'd get this p-api through proposed, merge & clean silo 7, then build telephony-service for boiko
[22:20] <cjwatson> well, ok, but why's it bad to build it?  it's a cheap canary for whether an indicator-datetime rebuild is worthwhile
[22:20] <rsalveti> silo 15 has the plat v2 renaming for indicator-datetime as well
[22:20] <cjwatson> we can afford the armhf builder time
[22:20] <rsalveti> to use the right packages now
[22:20] <cjwatson> and you can just not publish it
[22:21] <robru> cjwatson, not that we can't afford the time, i just thought p-api was coming shortly, somewhat pointless to build it twice in the same horu
[22:21] <robru> hour
[22:21] <cjwatson> ok, but I have a point :)
[22:21] <cjwatson> it's building against the new p-api anyway ...
[22:21] <cjwatson> or should be
[22:21] <cjwatson> but the previous builds on other arches may not have done, indeed
[22:21] <robru> cjwatson, it's building against the new p-api, but it won't include the diff from the telephony-service MP in silo 7, which needs to be merged back into trunk, and then boiko's silo rebuilt
[22:22] <robru> in fact thats probably why it failed in the first place
[22:22] <cjwatson> sure, not objecting to you rebuilding it, just saying it's harmless to finish this build first so that we can confirm that build-deps are now installable.
[22:22] <robru> ok
[22:22] <cjwatson> no, it failed because of incorrect platform-api overrides
[22:23] <cjwatson> huh, well, maybe it was both
[22:23] <cjwatson> ok, whatever, failed again :)
[22:23] <robru> cjwatson, https://code.launchpad.net/~ricmm/telephony-service/papi-v2/+merge/221322
[22:23] <cjwatson> anyway, a better simulation looks fine for indicator-datetime
[22:23] <cjwatson> I'll go ahead and upload a no-change rebuild just as seb128 did
[22:24] <robru> cjwatson, thanks
[22:24] <rsalveti> cjwatson: silo 15 has the change that renames to the right packages
[22:24] <rsalveti> we can just land that instead
[22:24] <rsalveti> a rebuild will use the transitional packages, will work, but we need to change that anyway
[22:24] <cjwatson> ok, if you like
[22:25] <robru> rsalveti, can you land that quickly? all of p-api is waiting for it
[22:25] <rsalveti> yup
[22:25] <rsalveti> package is building
[22:26] <cjwatson> qtubuntu-gles is in the autohinter set now and has improved things
[22:27] <robru> cjwatson, improved things how? like excuses will explain the situation if it comes up again rather than just saying "valid" and not doing anything?
[22:28] <cjwatson> robru: no, that's expected, excuses is only the first stage of processing
[22:28] <robru> bah
[22:28] <cjwatson> http://people.canonical.com/~ubuntu-archive/proposed-migration/update_output.txt shows "Trying easy from autohinter: platform-api/..." and below that lists the remaining uninstallables that result from attempting to promote that set of packages to release
[22:28] <cjwatson>     * i386: edubuntu-desktop, indicator-datetime, ubuntu-desktop, ubuntu-desktop-next, ubuntu-touch, unity-control-center, unity-control-center-signon, unity-control-center-signon-autopilot, webaccounts-chromium-extension, webaccounts-extension-common, xul-ext-webaccounts
[22:28] <cjwatson>     * amd64: edubuntu-desktop, indicator-datetime, ubuntu-desktop, ubuntu-desktop-next, ubuntu-touch, unity-control-center, unity-control-center-signon, webaccounts-chromium-extension, webaccounts-extension-common, xul-ext-webaccounts
[22:29] <cjwatson>     * armhf: edubuntu-desktop, indicator-datetime, ubuntu-desktop, ubuntu-desktop-next, ubuntu-touch, unity-control-center, unity-control-center-signon, webaccounts-chromium-extension, webaccounts-extension-common, xul-ext-webaccounts
[22:29] <robru> ah, no qtubuntu
[22:29] <cjwatson> improvement: qtubuntu-android and friends are gone
[22:29] <cjwatson> indeed
[22:29] <cjwatson> the rest look like they're all from indicator-datetime
[22:29] <robru> i guess we'll find out soon!
[22:30] <cjwatson> update_excuses => package-local tests (well, aside from autopkgtests).  update_output => global (and much slower) installability analysis
[22:30] <cjwatson> as a rough rule of thumb
[22:32] <cjwatson> it's a lot easier to read when there aren't half a dozen incomplete enormous intertwined sets all trying to migrate at the same time.  hopefully will be able to make some further inroads into those next week
[22:32] <rsalveti> robru: package is building in the ppa
[22:33] <cjwatson> oh, I could probably shift the rtmidi transition at least.
[22:34] <cjwatson> anyway, must sleep, early start tomorrow.  night
[22:35] <robru> cjwatson, thanks again, good night@
[22:40] <rsalveti> robru: hm, the build wasn't able to find the new packages, wonder if it used proposed at all
[22:40] <rsalveti> robru: yeah, didn't build against proposed
[22:40] <rsalveti> robru: I'll just upload it directly
[22:41] <robru> rsalveti, alright
[22:41] <rsalveti> robru: but we might want to check with silo 15 didn't use proposed
[22:41] <rsalveti> *why
[22:44] <robru> rsalveti, yeah that is really strange
[22:44] <rsalveti> robru: not configured properly
[22:44] <rsalveti> robru: go to silo 15 -> edit ppa dependencies
[22:44] <rsalveti> robru: dependencies is just 'default'
[22:45] <robru> hmm, i wonder if they're all like that
[22:45] <robru> fixed 15 anyway
[22:45] <rsalveti> robru: uploaded directly, can you abort silo 15?
[22:45] <robru> rsalveti, yeah
[22:45] <robru> rsalveti, thanks
[22:46] <rsalveti> robru: thanks
[22:47] <robru> rsalveti, hmmm, none of them have proposed enabled, should I turn that on? not sure why that's set that way
[22:47] <rsalveti> robru: well, then not sure if that was by design
[22:48] <robru> yeah, maybe i'll leave that since it's been working fine thus far
[22:48] <rsalveti> confusing at least as uploads always target proposed
[22:48] <robru> we can just be aware to enable that when needed
[22:48] <rsalveti> yeah
[23:05] <rsalveti> robru: built fine, waiting now to be migrated, lets see if it all work as expected :-)
[23:07] <robru> rsalveti, great ;-)
[23:08] <robru>  13.10.0+14.10.20140611-0ubuntu3 best version number ever
[23:20] <rsalveti> robru: should I just erase line 41?
[23:20] <rsalveti> robru: line 8 can be removed as well
[23:21] <robru> rsalveti, yeah please, delete row
[23:21] <rsalveti> done
[23:21] <cjwatson> I think it's deliberate that silos don't use proposed normally, so that they build against a consistent base.  also think exceptions are ok but we should remember to configure the silo back to normal at the end
[23:22] <robru> cjwatson, yeah
[23:47] <rsalveti> robru: indicator-datetime just migrated
[23:47] <rsalveti> platform-api is also a valid candidate
[23:48] <robru> rsalveti, yeah, p-api has been a valid candidate for like 4 hours
[23:48] <rsalveti> right
[23:48] <robru> rsalveti, rmadison doesn't show indicator-datetime migrated yet
[23:49] <rsalveti> yeah, lp is in that state that makes it disappear as well
[23:49] <robru> oh excellent
[23:49] <robru> well ci train is satisfied that the whole silo 7 migrated, so that's good news
[23:49] <robru> rmadison should catch up shortly
[23:50] <rsalveti> yeah
[23:50] <rsalveti> hopefully it should be all good in a few
[23:51] <robru> at least I can merge the silo so boiko's telephony-service can build on the new trunk
[23:55] <rsalveti> yeah
[23:56] <rsalveti> guess we can just wait for the cron image as well, should be started in a few hours
[23:57] <robru> yeah