/srv/irclogs.ubuntu.com/2014/11/05/#ubuntu-ci-eng.txt

Saviqribru, ↑ please00:34
ribruSaviq: rtm 400:34
Saviqribru, thank you :)00:35
ribruSaviq: you're welcome00:35
ribruSaviq: out of curiousity, how did you fill out row 77? it was missing all the necessary spreadsheet formulas. I fixed it, just wondering how it gets that way...00:35
Saviqribru, it was there already00:35
ribruSaviq: you didn't like, copy & paste the values from somewhere? even if you insert a new blank row it should fill those formulas in...00:36
Saviqribru, I did, but just per-field00:36
Saviqribru, I didn't touch any of the automagic fields00:36
ribruSaviq: hm, weird. mysterious spreadsheet bs :-/00:36
Saviqribru, need help ↑00:42
Saviqhttps://ci-train.ubuntu.com/job/ubuntu-rtm-landing-004-1-build/61/console00:42
Saviqhow do I resolve that?00:42
ribruuh00:44
ribruSaviq: well the easiest thing to do would be to just bump the unity8 version number to 8.01.1 or 8.02 I guess00:45
Saviqribru, looks like sync should still rewrite 15.04 into 14.10...00:45
Saviqribru, yeah, that's what I thought, but meh :|00:45
ribruSaviq: no, the sync *did* do that, but the problem is that it shouldn't, because 15.04 is already there00:45
ribruSaviq: so I guess at some point you did a binary sync from vivid to rtm already? the version in rtm is 15.04 with no ~rtm tag00:45
Saviqribru, well, sync took the upstream 15.1000:46
Saviqribru, it is 15.04 *with* the rtm tag00:46
Saviqribru, https://launchpad.net/ubuntu-rtm/+source/unity800:46
ribrubah00:46
Saviqribru, it was a source copy, that copied 15.04, now it tried to do 14.1000:46
Saviqmeh for bumping, but what can I do...00:47
* Saviq goes for -rtm00:48
ribruSaviq: yeah I'm not sure what's going on there. it looks to me like the version number it's trying to use is correct, but this is thwarted by somehow a vivid version number already being at the destination. second time today I've seen this where rtm had a newer version than it should have and then the code that was generating a very reasonable version number00:49
ribruwas rejected.00:49
ribruSaviq: basically yeah, you have to mangle the version number yourself and upload manually00:49
Saviqribru, well, I know *how* it happened00:49
Saviqribru, just not sure what the correct resolution would be :)00:49
Saviqribru, I synced it from vivid last Friday00:50
Saviqribru, that was a source sync, but it only appended ~rtm00:50
ribruSaviq: a binary sync?00:50
Saviqribru, source sync, hence the ~rtm00:50
Saviqribru, basically a silo sync00:50
Saviqribru, line 1985 in the train archive00:51
ribruSaviq: this other error you're getting is much more interesting00:53
Saviqribru, it is indeed00:53
Saviqgetting the same for the other source :/00:53
Saviqand totally no error msg :'|00:54
ribruSaviq: I'm in the middle of converting citrain to use absolute paths instead of relative paths, because the code was a mess of spaghetti cd'ing everywhere. there was a bug where it would cd to the wrong place, do stuff, then cd back, and files weren't where we expected them00:54
ribruSaviq: I'll try reverting my last commit and see if that gets it back into a state that can hobble along00:54
ribruSaviq: ok try it again now, this time it should probably "work" (there'll still be an error, but this time the error should come after the PPA upload, and then you can run a WATCH_ONLY afterwards as a workaround)00:55
Saviqribru, it's worky00:56
SaviqI mean it's trying00:56
=== chihchun is now known as chihchun_afk
ribruUrsinha-afk: ^^ my awesome branch is less awesome than I thought00:58
Ursinharibru: s/Ursinha-afk/Ursinha/ :)00:59
Ursinharibru: oops00:59
ribruUrsinha: my next branch will convert even more relative paths into absolute ones so hopefully that gets that back into a consistent state.00:59
ribruUrsinha: for now I reverted production, so things can work while I tinker01:00
* ToyKeeper wonders why, 4 hours after imgbot announced the start of build 143, that image still isn't on the image servers01:09
ribrujustinmcp_: welcome!01:17
ribruJustin Master Control Program.01:17
ribrujustinmcp_: ok so do you know about the spreadsheet?01:18
justinmcp_ribru: i know nothing01:19
ribrujustinmcp_: ok. funny i thought we did this already once01:19
ribrujustinmcp_: ok go here: https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0AuDk72Lpx8U5dFVHQ3FuMDJGLUZCamJfSjYzbWh3Wnc#gid=001:19
ribrujustinmcp_: find the first empty row (78)01:20
justinmcp_ribru: got it01:20
ribrujustinmcp_: fill out the info as best you can (some fields are autogenerated, so just leave blank whatever you're not sure of). look at the other rows for guidance. ask me if you have any questions.01:20
justinmcp_ribru: and then magic?01:21
ribrujustinmcp_: less like magic, and more like... http://i.ytimg.com/vi/MjuioxC5WwA/maxresdefault.jpg01:22
justinmcp_ribru: :) confidence is high01:23
ribrujustinmcp_: I'd like to retroactively rename ci train to... 'ci house of cards'.01:24
ribrucase in point ^01:24
ribrujustinmcp_: column A is purely informational and isn't actually used anywhere, so don't write your life story in there like saviq does ;-)01:26
justinmcp_ribru: *disappointment*, nobody cares :(01:27
Saviq!!01:28
Saviqmy description has *links* to bugs!01:28
ToyKeeperColumn A is used by QA though...  very helpful to have a list of bugs fixed there.01:28
Saviqand everything!01:28
SaviqToyKeeper, say you like my Column A, you know you do!01:28
ToyKeeperI do, actually.01:29
ribruSaviq: what links? there's no links ;-)01:29
Saviqhmm this sounded much more sexist than I intended it to...01:29
ToyKeeperIt saves me the trouble of populating that info myself on QA's kanban cards.  :)01:29
Saviqribru, see! links! http://people.canonical.com/~platform/citrain_dashboard/#?distro=ubuntu&q=landing-00701:29
ribruSaviq: oh you are doing links now. you used to just have the numbers ;-)01:29
Saviqribru, I was hoping you'd do links :P01:29
Saviqribru, but since you don't01:29
ribruSaviq: yeah everything's gonna change when we dump the spreadsheet, doesn't make sense to do new features right now01:30
ToyKeeperMost of the time, I have to either dig up the bug numbers or at least convert them to clickable URLs.01:30
Saviqhah01:30
ribruSaviq: ToyKeeper it's just that the spreadsheet doesn't let you scroll smoothly, it forces the view to snap to the rows. and when a single row is larger than my screen it destroys the UX.01:32
Saviqribru, get a bigger screen ;p01:32
ToyKeeperribru: Indeed, that's obnoxious.  I have the same issue.  Usually I just go to one of those cells and copy/paste the info elsewhere so I can actually read it.01:32
ribruSaviq: well excuuuuuse me! my 27" is on the other side of the room. I'm just using my 10" for now because I'm in bed with broken ribs!01:33
ToyKeeperBut since I'm generally copying it anyway, it's not a big inconvenience.01:33
* ToyKeeper looks forward to no-more-spreadsheet01:33
ribruToyKeeper: soon01:33
Saviqribru, you're an engineer, you should've engineered a crane to hold your 27" over your head!01:33
Saviqribru, it'd have worked, I assure you01:33
Saviqand would be relatively safe01:34
ribruSaviq: hindsight is always 20/20. couldn't do that after I was already injured01:34
Saviqribru, excuses excuses :P01:34
Saviqribru, on that note, I think I managed to convince dch to take my version, I just needed to force a lower version in my branch01:35
Saviqand now the train-generated one will be higher again01:35
Saviqhmm hmm01:35
Saviqwait01:36
justinmcp_ribru: finished, I guess..01:36
Saviqit will not be higher than the one in distro, though, will it...01:36
Saviqyeah, that was stoopid01:36
ribrujustinmcp_: ok, just set J78 to 'Yes' (which triggers the bot to notify us that you're ready)01:38
justinmcp_its almost like magic01:40
ribrujustinmcp_: ok, I gave you silo rtm 9, which means you can go to http://people.canonical.com/~platform/citrain_dashboard/#?distro=ubuntu-rtm&q=justinmcp and click 'Build'01:40
ToyKeeperYup, magic indeed.01:44
ribruSaviq: you are just not having any luck today...01:44
Saviqribru, nah, it just uploaded01:45
ToyKeeperjustinmcp_: Fatal error on your first try.  You've got the magic touch!  :)01:45
Saviqribru, will be fine now01:45
justinmcp_this is why I code01:45
ribruhow did all this 15.04 shit get into rtm?01:45
ToyKeeper... what?01:46
ToyKeeperPlease tell me we didn't pull stuff from 15.04 into rtm...01:46
ribruToyKeeper: well the traceback that justinmcp_ got and Saviq also got just now are that they're trying to do syncs from vivid into rtm, the sync code makes the version number be 14.10.whatever, but rtm already contains version numbers 15.04.whatever and so you can't upload an older version over top of a newer version. I have no idea what's going on01:47
ToyKeeperThat's a snowball which is very difficult to stop.01:48
Saviqribru, no, that's not true01:49
Saviqribru, *syncs* don't rewrite the 15.04 part01:49
Saviqribru, standard landings do01:49
Saviqribru, so I got 15.04 from a sync last week, and that's higher than what I now get with a MP-based landing01:50
* ToyKeeper backs away slowly and goes off to do some sanity testing01:50
Saviqribru, but indeed, this will now happen to everyone that needs to move from syncs to rtm-targetted landings + series branch01:51
ribruoh right, you guys have MPs01:51
ribruSaviq: justinmcp_ well you better target your MPs into vivid then I guess.01:51
Saviqribru, they just landed in vivid01:51
Saviqribru, now I need to cherry-pick into rtm01:51
ribruugh01:52
Saviqribru, because I can't afford to not land stuff that's not rtm-approved01:52
Saviqribru, and there will be more of that as we go on01:52
ribruSaviq: I'm frustrated, I don't understand how citrain code was allowed to get as bad as it is.01:52
Saviqribru, so this needs resolving asap, otherwise everyone will have to go .1 on their upstream versions01:52
Saviqribru, I imagine because it was only meant to live for a few months01:53
ribruSaviq: I EOD in 10 minutes and I'm already putting out other fires ;-) I'll fix it tomorrow if sil doesn't beat me to it01:53
Saviqribru, yeah, I'll try and talk to sil in between talks01:53
Saviqam out for a conference tomorrow01:53
Saviqand on that note, 4h of sleep ahead of me...01:53
=== ribru changed the topic of #ubuntu-ci-eng to: Need a silo? Ping train support: trainguards | Need help with something else? Ping vanguard: cihelp | Train Dashboard: http://bit.ly/1mDv1FS | QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: CI Train is incapable of landing MPs into RTM if that package was previously synced from vivid. you have to mangle the versions and upload manually
justinmcp_how do I re-try the build?01:57
ribrujustinmcp_: well you can run the build job again, you might need to check 'FORCE_REBUILD' option or maybe 'IGNORE_STEP', just follow the errors you get.01:59
ribrujustinmcp_: did you change your MP in some way? shit's pretty broken right now, you might have to wait until tomorrow.01:59
justinmcp_ribru: I changes the target to vivid, but otherwise untouch02:00
justinmcp_ribru: I can leave it till tomorrow02:01
ribrujustinmcp_: oh if you're doing vivid we can do it today02:01
ribrujustinmcp_ it's just syncs to rtm that are busted for now02:01
ribruor mps02:01
ribrujustinmcp_: I have to free the silo to reset it for vivid, hang on02:01
ribrujustinmcp_: http://people.canonical.com/~platform/citrain_dashboard/#?distro=ubuntu&q=justinmcp click Build here now ;-)02:05
justinmcp_i feel empowered02:05
ribrujustinmcp_: that was the idea originally ;-)02:06
veebersribru: are you still around per chance?03:19
ribruveebers: what's up?03:21
veebersribru: hey, I have a silly question that I thought you would be able to answer for me :-)03:21
ribruveebers: shoot03:22
veebersribru: I'm wanting to trigger a build for this ppa so we get Utopic + arm versions: https://launchpad.net/~autopilot/+archive/ubuntu/1.5. I will need to bump the version in the changelog and dput the result to do so, I'm finding the version number a little intimidating as I don't want to break things03:22
veebersthe version number in the ppa is: 1.5.0+15.04.20141031-0~504~ubuntu14.04.1 , I should be able to branch, set the version to "1.5.0+15.04.20141105-0~504~ubuntu14.04.1 " and use that, right?03:23
ribruveebers: that looks like a recipe build, why don't you just run the recipe?03:23
veebersribru: hmm, I was under the impression that wouldn't work due to version number conflicts03:25
ribruveebers: the version number already has 15.04 in it so you're basically already boned03:25
veebershmm perhaps I miss-interpreted the comment that lead me to believe that03:25
ribruveebers: what was the comment?03:26
veebersribru: oh, really? :-\03:26
ribruveebers: https://code.launchpad.net/~autopilot/+recipe/autopilot-1.5 looking at the recipe, it won't touch the date, it'll just use whatever the current revno is.03:27
ribruveebers: so that shouldn't cause any further problems than what's already there.03:27
veebersMe: "I could use the recipes 'request build right?' response "veebers: Unless the revno hasn't changed, thus causing a version conflict."03:28
ribruveebers: the current situation is that citrain is incapable of building an MP in RTM if RTM contains a version string with '15.04' in it, because the mp generated version string is '14.10', which is less, so it rejects the upload. you already have 15.04 so it's already busted.03:28
ribruveebers: but why do you want a new build if the revno hasn't changed?03:28
veebersribru: because I didn't get the changes in this into Utopic, so I want it in the ppa so people can use it if they need to (i.e. CI) but I didn't update the 1.5 ppa until after it had built the new 1.5 branch03:29
ribruveebers: the ppa only contains trusty, IIRC that conflict that person is talking about is for the same version within the same series.03:31
ribruveebers: i would personally try the recipe build, if that fails then you can futz the version manually03:31
veebersribru: ok, yeah I changed the recipe today to build for utopic (and asked wgrant to add arm building to it) hence me wanting to trigger the build so there was a utioc version in there03:32
ribruveebers: the recipe appends the series to the version number, so if you upload utopic you'll get blah~ubuntu14.10.1 and it won't conflict.03:32
veebersribru: ack, I take it trying the recipe will fail as opposed to breaking things? (/me is being careful with this)03:33
ribruveebers: right, if there's any problem, the recipe will just fail, it won't make things worse.03:33
ribruthe conflict you heard before and the 15.04 brokenness I'm talking about now are separate issues.03:33
veebersribru: ok, I'll give that a try and see what happens, thanks for talking me through that03:33
ribruveebers: you're welcome03:33
Mirvmornings05:20
cyphermoxMirv: morning05:40
cyphermoxthis is my queue that I really should log off ;)05:40
cyphermox*cue05:40
Mirvcyphermox: correct!05:45
cyphermox;)05:46
cyphermoxMirv: good night!05:54
Mirvcyphermox: good night!05:54
tvosstrainguards, can I get a silo for line 7907:46
Mirvtvoss: there you go, Mr. Bond.07:49
Mirv(silo 007)07:49
tvosshah07:50
tvossMirv, in style ;)07:50
pstolowskitrainguards, hello, a new rtm-14.09 branch for unity-scopes-api has been created to land top blocker at line #60; do i/we need to do anything special for it to build packages against the new branch?08:25
pstolowskiMirv, morning, did you have a chance to look at this ^ ?08:27
sil2100pstolowski: hey!08:27
sil2100pstolowski: just provide MR that target this branch in your landing08:27
sil2100MRs08:28
pstolowskisil2100, hi! yep, i did that. cool, thank you08:29
Mirvpstolowski: yes, I commented on the branch since you weren't online08:45
pstolowskiMirv, awesome, thanks!08:54
ogra_damn09:05
ogra_sil2100, so we have a slight image build prob ...09:06
* ogra_ ponders how to solve it best 09:08
=== Saviq is now known as Saviq-codedive
pstolowskitrainguards, could you please reconfigure ubuntu-rtm/landing-002 ?09:15
Mirvpstolowski: done.09:16
pstolowskithanks09:17
sil2100ogra_: what's up?09:17
sil2100ogra_: everything was fine yesterday, right?09:17
Saviq-codedivesil2100, you might wanna know we're up for some train woes09:17
sil2100Saviq-codedive: what's up?09:18
ogra_sil2100, the dropping of the langpack causes the metapackage to be out of sync09:18
Saviq-codedivesil2100, everone that synced from vivid to rtm have 15.04 in their versions in rtm09:18
Saviq-codedivesil2100, but now you try to land through an MP into an rtm series branch09:18
Saviq-codedivesil2100, you end up with 14.10 in there and you're lower than what's in rtm archive09:18
Saviq-codedivesil2100, had to .1 unity8 for rtm silo 409:19
sil2100Saviq-codedive: hm, indeed this might be trouble ;/ Damn, somehow no one expected this problem to happen09:19
sil2100Saviq-codedive: ok, so I can theoretically make sure that when we do source syncs, we rewrite the series part of the version number as well09:20
sil2100But that's not something I can do without consulting slangasek and cjwatson09:20
Saviq-codedivesil2100, well, and worse, that won't help now09:20
sil2100I know...09:20
Saviq-codedivesil2100, only thing that would help now is actually keeping 15.04 there09:20
sil2100But at least it won't make the situation any worse09:20
Saviq-codedivesil2100, which is actually something I would recommend09:21
ogra_the series has no impact ... only if you put it into the version number09:21
sil2100ogra_: I mean the series in the version09:22
ogra_right09:22
sil2100ogra_: since CI Train adds the series version number to the version it creates, so I can make that being rewritten too... but well, not really possible09:22
sil2100Saviq-codedive: in any way, I indeed will have to tweak the code, as even in the likelyhood of staying with 15.04, CI Train will try to rewrite it to 14.10 on direct releases09:23
Saviq-codedivesil2100, TBH I'd recommend keeping it as is in the current top version09:23
sil2100Saviq-codedive: so I need to make sure CI Train can just say 'ok, it's 14.09, but I'll use 15.04 now still because the previous releases had that'09:24
Saviq-codedivesil2100, yup09:24
* Saviq-codedive goes to focus on the talk09:24
sil2100Saviq-codedive: thanks on letting me know about this!09:24
sil2100Saviq-codedive: I was slowly moving away from CI Train maintenance so I didn't even notice this09:24
=== chihchun_afk is now known as chihchun
davmor2thostr_: http://paste.ubuntu.com/8833284/ I took two photos and a video with the camera app and mediascanner doesn't seem to of picked up on the video though.  so it doesn't show in the video scope09:59
thostr_davmor2: close the camera app, does it show then?10:00
davmor2thostr_: I think if I reboot it will appear though judging by what ToyKeeper was saying10:00
bzoltancjwatson: fyi -> the 6.7 ssh server has removed the algorithms what the QtCreator is using (https://qt.gitorious.org/qt-creator/qt-creator/source/b72a9dd2391680b7a9ed7c82c1cfefc7cef687e8:src/libs/ssh/sshcapabilities.cpp#L65)10:00
thostr_davmor2: just close camera app10:00
brendandthostr_, davmor2 - for me just closing the app worked10:01
davmor2thostr_: yes after a couple of swipe to refresh now it shows up10:01
brendandthostr_, and that's not a new bug?10:01
thostr_no, see my comment on the mailing list10:01
thostr_it's a camera issue...10:01
thostr_it's not releasing file handles of recorded videos10:01
brendandthostr_, yeah i confirmed the same thing10:01
thostr_which means mediascanner can not pick it up as it can only react to files that are fully written10:02
thostr_or rather, we get only notified once the file handle is released10:02
bzoltanMirv: sil2100: So, right now the Vivid images are not good for app development. RTM is good as long it is on 6.6 ssh server10:03
ogra_bzoltan, you didnt see cjwatson's answer ? he wrote quite a lot yesterday10:04
bzoltanogra_:  I have missed that...10:04
* bzoltan reading logs10:04
ogra_http://irclogs.ubuntu.com/2014/11/04/%23ubuntu-ci-eng.html#t16:0710:05
bzoltanogra_: cjwatson: Ok, thanks for the explanation. That is what I too figured out today morning. I checked the qtcreator's upstream trunk and there is no sign of preparation to safer ciphers. We will talk to the devs and see if they are willing to address the problem.10:07
bzoltanogra_: in the meantime enabling legacy ciphers would be an acceptable _temporary_ solution.10:07
ogra_i would like to hear security team input to that first10:08
bzoltanogra_: whatever they say, they should understand that in the present setup there is no app development for devices with Vivid images. Even if the QtCreator upstream devs are willing to take this work on their backlog the fix will not come out quickly.10:12
ogra_bzoltan, we can likely switch on the extra cyphers again during development if the security team thinks thats ok ... but definitely not for release10:13
ogra_this has to be fixed within the next months10:13
bzoltanogra_: fine with me ... as long the devs can run their apps on the device after they switch the "development mode" on10:14
ogra_(or earlier depending when/if rtm switches to vivid10:14
ogra_shipping an insecure ssh on a sold phone is not an option10:14
bzoltanogra_: no bad feeling, but it is yet again a significant change in the platform what was rolled out without considering the app development.10:15
ogra_so upstream has to react somehow ...10:15
ogra_(i also doubt we are the only distro using a new upstream ssh)10:15
ogra_bzoltan, this is something we dont have control over ... upstream considers these cyphers to insecure to ship10:16
bzoltanogra_: for sure not.. and it is strange that the qtc devs have not yet reacted to it at all... they should know about such upcoming change.10:16
ogra_(beyond the fact that vivid at this point doesnt get Qa10:16
ogra_)10:16
dbarthhi Mirv, we'd need a binary copy of oxide in silo 15 (vivid)10:17
bzoltanogra_: yes, I know... nobody to blame. It is how it is :) The vivid is the development series, so this kind of "regressions" are acceptable10:18
dbarthor a nice trainguard if not available10:18
oSoMoNdbarth, Mirv: hold on a sec, the silo needs a rebuild first (just removed a MR from it)10:19
sil2100dbarth: o/10:20
sil2100dbarth: from which PPA?10:21
oSoMoNsil2100, we need a reconfigure of silo 15, then a copy of oxide-qt from https://launchpad.net/~phablet-team/+archive/ubuntu/ppa/+packages10:21
sil2100oSoMoN: ACK10:21
* sil2100 reconfigures then10:21
oSoMoNthanks!10:22
sil2100oSoMoN: ok, copying the package now10:24
Mirvokie10:25
sil2100uh10:25
sil2100oSoMoN: I see oxide was built for utopic in that PPA...10:25
Mirvsil2100: it probably needs to be done from command line. I can do that, I've done it before.10:25
sil2100oSoMoN: this *might* be a problem when doing binary copies, as we can't guarantee binary compatibility10:26
sil2100Mirv: ^10:26
Mirvsil2100: utopic shouldn't be a problem, vivid could be?10:26
oSoMoNsil2100, oh, you’re right! sorry about that, I guess we’ll have to rebuild it for vivid first10:26
MirvoSoMoN: no, vivid could be a bigger problem for rtm than utopic10:26
sil2100Mirv: well, the phablet PPA has utopic binaries of oxide-qt, and they need to copy it to vivid10:26
Mirvoh, this's a vivid silo, not rtm10:26
sil2100Yes10:26
oSoMoNMirv, we’re not going to sync to rtm anyway, oxide 1.3 has been rejected for rtm10:27
MirvoSoMoN: yeah so in that case indeed rebuild for vivid10:27
oSoMoNMirv, yup, will do, thanks10:27
Mirvand then we can copy10:27
sil2100Mirv: will you handle this till the end then? :)10:27
sil2100Thanks!10:27
dbarthsil2100: what oSoMoN said ;)10:27
Mirvsil2100: sure, no problem, but with Oxide I'll be EOD's when the build finishes in 5h ;)10:27
dbarththanks guys10:27
sil2100Eeej10:27
sil2100Eeek10:27
sil2100;)10:27
oSoMoNMirv, sil2100, no worries, there’s no urgency on this one, it can wait till tomorrow10:27
Mirvmy last build was 5h 26min https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-002/+build/651443710:28
oSoMoNwe’ll get oxide built for vivid first, and ping you tomorrow when done and tested10:28
pstolowskiMirv, hey, failure in ubuntu-rtm/landing-002 with missing gcc-4.9 and then with version number (which i'm not sure where it comes from). anything todo for me?10:34
sil2100uh10:36
sil2100Mirv, pstolowski: seems like the issue mentioned by Saviq-codedive...10:37
* sil2100 sighs10:37
sil2100What to do what to do...10:37
pstolowskisil2100, ah..10:38
sil2100pstolowski: can you wait a little bit? Since fixing this might be easy, but current CI Train trunk is b0rken so I need to first work-around the changes ribru made10:39
sil2100cjwatson: hello! Are you around for a quick advice? :)10:40
pstolowskisil2100, sure10:40
sil2100cjwatson: I was thinking: would it be sane to just use 15.04 in rtm version-numbers instead of 14.10 by default? i.e. the 1.1+15.04.20141105~rtm instead of 1.1+14.10 as we have now?10:41
sil2100Since it should probably point to the current developmnent series anyway10:42
psivaa_sil2100: the unity8 run came back ok on the rerun10:59
sil2100psivaa_: how many failures? 2-3?10:59
psivaa_ok meaning at least it completed10:59
ogra_sigh11:06
sil2100ogra_: any luck?11:07
ogra_sil2100, no, and i see no way to fix this ... pitti doesnt seem around either, nor does cjwatson ...11:07
sil2100Yeah, I would need cjwatson's or slangasek's opinion as well to fix the train11:07
ogra_as a last resort i tried to hack the metapackage in rtm ... to read from the rtm archive ... that works up to the point where germinate needs debootstrap ... no 14.09 distro there11:08
ogra_the prob here is that germinate needs to recognize the langpack gone ...11:08
ogra_by default it reads from the utopic archive ... where the landgapck simply isnt gone11:09
ogra_*langpack11:09
ogra_(and where we cant remove it now that utopic is released)11:09
sil2100Can't we retarget it somehow?11:09
ogra_yes, thats what i tried ... but there is debootstrap involved ...11:09
ogra_and debootstrap neither knows what rtm is nor that there is a 14.09 release11:10
ogra_the rtm archive only knoows 14.09 and devel as distros11:10
ogra_(and no, debootstrap doesnt know devel)11:11
sil2100Damn11:12
ogra_i'll sync the latest changes into vivid now at least ...11:13
ogra_we coould theoretically binary snyc from vivid once this is done ... but that completely messes up the changelog11:13
sil2100I'm starting to think that maybe removing those langpacks wasn't such a good idea, maybe it could have been worked-around some other way11:13
sil2100Like blacklisting those langauges somehow in the UI11:13
ogra_well, the seed has "langpack-ubuntu-touch-*" ... it reads the actual list from the available packages in the archive11:14
ogra_read: this isnt even a seed change at all ... just a germinate run11:14
ogra_blacklisting but shipping would be quite some hack11:15
ogra_i think the only sane way is to pull the vivid meta in ... but at the cost of losing the histroy :(11:16
sil2100Let's hack germinate!11:16
sil2100\o/11:16
ogra_heh11:16
sil2100Anyway, I would still wait for at least pitti to appear11:17
ogra_right11:18
cjwatsonsil2100: sorry, variously on vacation / conference leave this week so not really enough brainspace to advise, hopefully somebody else is around11:21
cjwatsonogra_: I'd just hack the metapackage manually (carefully!) and not worry too horribly much about germinate-update-metapackage being unhappy11:22
cjwatsonit's not actually a hard requirement11:22
ogra_cjwatson, you mean hack the deps directly ?11:22
ogra_ok, that shouldnt be to hard11:23
cjwatsonsure11:23
ogra_thanks11:23
cjwatsonwell, the files used to generate them11:23
ogra_thats the one option i didnt consider :)11:23
* ogra_ uploads and crosses fingers11:32
brendandMirv, do you happen to know where the latest clicks for e.g. calculator might be?11:54
ogra_sil2100, ok, starting a test build for both distros ... cross your fingers :)12:03
sil2100ogra_: \o/12:03
ogra_(the bot wont announce them, it still waits for the finishing of vivid9 and rtm143)12:04
sil2100I go to lunch, back in some time12:13
sil2100pstolowski: after lunch someone from should be already available to review my proposal and I might be able to unblock your landing12:15
ogra_phew, looks like the build got past the failure ... great12:19
pstolowskisil2100, k, thanks for heads up12:20
Mirvbrendand: http://s-jenkins.ubuntu-ci:8080/job/calculator-app-click/12:23
Mirvbrendand: they all tend to be of the same form (url)12:28
ogra_mdeslaur, could you take a look at the ssh discussion between colin and zoltan on http://irclogs.ubuntu.com/2014/11/04/%23ubuntu-ci-eng.html ? seems upstream dropped some cyphers, the SDK uses its own ssl lib that can only be used with these cyphers ...12:38
ogra_mdeslaur, there is a request from the SDK team to re-enable them in vivid12:39
ogra_while i think we could indeed technically re-enable them i would like to hear some security team opinion12:39
* mdeslaur reads12:41
ogra_(there is subsequent discussion between zoltan and me in todays backlog too btw)12:42
mdeslaurogra_: what component is responsible for that?12:44
ogra_openssh-server12:45
ogra_on the phone side ...12:45
mdeslaurah, I see the qtcreator commit now12:45
ogra_not sure what component of QtCreator12:45
mdeslaurI'm not thrilled about adding the ciphers back, they were removed for a reason. The real solution is to fix qtcreator by adding in some of the better ciphers. That being said, you could _temporarily_ add them back to the phone image until qtcreator gets updated12:50
mdeslaurbut as a temporary measure only12:50
ogra_right12:50
ogra_and who keeps track of this12:50
pmcgowanogra_, was a 143 built? trying to debug my updates12:50
ogra_and who makes sure that doesnt slip into a potential vivid-rtm if we merge before feature freeze etc12:51
ogra_pmcgowan, no, we have image build issues12:51
pmcgowanok12:51
ogra_working on them ... with luck there should be an image in a few12:51
ogra_... and so we will ... phew12:51
ogra_rootfses build again ... waiting for system-image importer now12:52
ogra_~20-30min12:52
ogra_mdeslaur, i'm not so musch worried about adding them back temporary than i am about forgetting that we did that in a few months12:52
ogra_*much12:52
mdeslaurogra_: right, someone needs to own the bug to fix qtcreator and to remove the workaround12:53
mdeslaurhonestly, it's probably as easy to fix qtcreator12:53
ogra_bzoltan, ^^^^see backlog12:53
ogra_yeah, one would hope so ... especially since it will surely be hit by that in other distros too12:54
pmcgowanmdeslaur, whats the fix - to use a different lib?12:59
mdeslaurjust add a couple of extra algorithms, no?12:59
mdeslauror are those the _only_ ones that are available?13:00
* mdeslaur looks at source13:00
mdeslaurah, yeah, it's going to require some modifications, hrm13:09
mdeslaurI guess adding the ciphers back to the phone images until upstream replaces the ciphers in qtcreator is the workaround for now13:10
ogra_hmm, k13:11
ralsinatraingards, a silo for row #71 pretty please? :-)13:16
tvossdavmor2, brendand can I get your help to test vivid silo 7?13:16
ralsinatrainguards ^13:16
brendandtvoss, today is your lucky day13:17
tvossbrendand, cool13:18
tvossbrendand, please test media playback, too13:25
imgbot=== trainguards: IMAGE 9 DONE (finished: 20141105 13:45) ===13:44
imgbot=== changelog: http://people.canonical.com/~ogra/touch-image-stats/9.changes ===13:44
imgbot=== trainguards: RTM IMAGE 143 DONE (finished: 20141105 13:45) ===13:44
imgbot=== changelog: http://people.canonical.com/~ogra/touch-image-stats/rtm/143.changes ===13:44
ogra_\o/13:44
ogra_allthefixes !13:44
popey☹ my phone hung when drawing welcome screen on unlock13:45
ogra_popey, i have seen that on the weekend13:45
ogra_but no crashes or anything :(13:45
popeyyeah13:46
popeyand takes ages to phablet-shell13:46
popeyi think it's not coming out of sleep properly13:46
ogra_well, powerd seems to still work in that state13:46
popeyhmm13:46
ogra_(i can toggle screen on/off with the powerbutton)13:46
popeysame13:46
* popey looks for a a bug13:47
popeycan't find one...13:47
* popey files one13:49
brendandtvoss, ok testing silo 7 now13:55
tvossbrendand, ack13:55
=== chihchun is now known as chihchun_afk
olliogra_, is there a list of bugs that were fixed in images since #140?14:03
ogra_olli, only if yu look through the individual changelogs ... i think sil has a tool for that14:04
davmor2Mirv: I just saw your silo man you need help :P  Silos are not distributions you know :D14:05
olliheh14:05
ogra_olli, you find the chnagelogs at https://lists.ubuntu.com/archives/rtm-14.09-changes/2014-November/thread.html and the list of changed packages at http://people.canonical.com/~ogra/touch-image-stats/rtm/143.changes14:06
fgintherballoons, if you have a moment, can you give this MP to move the core-apps to vivid a review? https://code.launchpad.net/~fginther/cupstream2distro-config/vivid-core-apps/+merge/24063414:06
olliogra_, I'll wait to talk about sil200's tool14:06
=== jgdxx is now known as jgdx
balloonsfginther, sure14:07
ogra_olli, usually lands here ... http://people.canonical.com/~lzemczak/landing-team/ubuntu-rtm/ but it takes my change list as input asnd i dont know exactly when it runs, might be manual14:07
olliogra_, I can wait until he is back14:08
ogra_well, if it is cron driven it will just show up, but yeah14:09
ogra_hmm, still no push notification on my krillin14:10
ogra_Chipaca, i thought the cron job for that runs every 5 min now ?14:11
bfillerMirv: can you do a reconfigure on rtm silo 17? just added a package14:11
Chipacaogra_: are you looking at the logs?14:11
Chipacaogra_: you only get the visible notification when it's finished downloading14:11
ogra_Chipaca, no, at the images :) i cant look at your server :P14:12
ogra_oh14:12
ogra_hmm14:12
Chipacaogra_: the push client logs when it gets the broadcast; then it calls system image asking to download the image14:12
Chipacaunless you've turned off automatic downloads, in which case you get it immediately14:12
ogra_i have them on indeed14:12
Mirvdavmor2: that's the smallest it can be, we could include various other things like updating qtpim snapshots and their reverse dependencies too :) but yeah, you're right that I need help!14:13
Mirvbfiller: ok.14:13
Chipacaogra_: and if any of system settings is in the foreground you never see the notification14:13
ogra_ok14:13
Chipacaogra_: answering your original question, yes, the cron runs every five minutes14:13
ogra_right, i was just wondering since it is more than 30 that the image showed up14:14
Chipacaogra_: you can look at ~/.cache/upstart/ubuntu-push-client.log (and in fact, please do)14:14
Chipacaogra_: ok, so please let me see your logs then14:14
Mirvbfiller: ^ done14:14
bfillerMirv: thank you14:14
=== chihchun_afk is now known as chihchun
Chipacaogra_: there are some weird things happening wrt this, which if have just happened to you i'd appreciate the logs and such14:15
seb128hum, I just got a duplicate update notification14:15
seb128is that a known issue?14:15
Chipaca"some weird things" -> broadcast arriving but the push helper dying in less-than-useful ways14:15
seb128I'm on r141 and there is r143 available14:15
Chipacaseb128: no you didn't! :-p14:15
ogra_seb128, you probably got mine then :P14:15
Chipacaseb128: explain "duplicate"14:15
ogra_Chipaca, http://paste.ubuntu.com/8836200/14:15
seb128Chipaca, the messaging indicate lists 2 "update available" entries14:16
seb128indicate->indicator14:16
Chipacaseb128: that shouldn't happen14:16
seb128just did14:16
Chipacaseb128: get me your logs14:16
Chipacastat :)14:16
seb128which ones?14:16
ogra_Chipaca, this log is gigantic, can you make sure to drop the debug spam before final release goes out ? ß14:17
Chipacaogra_: could you check whether you have a python process alive?14:17
Chipacaogra_: https://code.launchpad.net/~chipaca/ubuntu-push/logging-is-for-the-birds-tweet-tweet/+merge/24071314:17
ogra_phablet@ubuntu-phablet:~$ ps ax|grep python14:17
ogra_18506 ?        Sl     0:01 /usr/bin/python3 /usr/sbin/system-image-dbus14:17
ogra_seems fine14:17
seb128Chipaca, http://paste.ubuntu.com/8836225/ if that's the log you want14:17
Chipacaogra_: and check the tail of the push client log again in case it's just died (system-image-dbus should go away shortly after everything stops talking to it afaik)14:18
ogra_only one line added since the paste14:19
ogra_2014/11/05 15:15:22.916197 DEBUG ping.14:19
Chipacaseb128: yes, it was14:19
Chipacaseb128: so, it's explicitly clearing the indicator before posting the new one14:20
balloonsfginther, you build now for python3 only, amd64 only?14:20
seb128Chipaca, that somewhat failed I guess :/14:20
seb128hum, the indicator log has14:21
seb128g_menu_remove: assertion '0 <= position && position < menu->items->len' failed14:21
seb128dunno if that has to do with it14:21
tvossbrendand, any first impression?14:22
Chipacaseb128: i'll ask larsu14:22
popeyogra_: bug 138971814:23
ubot5bug 1389718 in unity8 (Ubuntu) "krillin 142 frozen on welcome screen when unlocking" [Undecided,New] https://launchpad.net/bugs/138971814:23
brendandpopey, sure you didn't just hit one of the cpu hogs?14:23
brendandtvoss, patience :)14:24
ogra_popey, confirmed ... pmcgowan olli ^^^^14:24
popeybrendand: no14:24
ogra_brendand, yes, that is different than just being sluggish14:24
popeytop - 14:24:54 up 17:00,  2 users,  load average: 0.00, 0.01, 0.0514:24
popeyits completely idle14:25
ogra_the UI hangs hard on the greeter14:25
ogra_sometimes the panel is even empty14:25
brendandogra_, sometime that happens and location stuff is going haywire14:25
ogra_i have seen this every two days since the weekend14:25
brendandpopey, right so top is idle14:25
ogra_but that is no data or info anywhere to be found14:25
ogra_*there14:26
Chipacaogra_: do you still have that device up?14:26
ogra_sure14:27
ogra_Chipaca, system-image-dbus is still sitting there14:27
ogra_nothing changed14:28
fgintherballoons, yes. at one time there was a specific job for running tests with python2, plus the one for python3 because detecting just proved to be unreliable. Now that everything is python3, there is only need for a single generic job14:29
balloonsfginther, right.. I left a comment, a little nitpick and a note about some future work we need to do.14:29
Chipacaogra_: please pastebin the output of14:30
Chipacaogra_: gdbus call --session --dest com.ubuntu.Postal --object-path /com/ubuntu/Postal/_ --method com.ubuntu.Postal.PopAll _ubuntu-system-settings14:30
brendandtvoss, you might have broken video rotation14:31
fgintherballoons, thanks! I'll get a comment added14:31
tvossbrendand, that's a bit weird. How do you test?14:31
rsalvetiogra_: great, seems we can now build images again14:32
ogra_rsalveti, yeah, that was a hard bone to chew though14:32
ogra_Chipaca, http://paste.ubuntu.com/8836388/14:33
rsalvetiogra_: thanks for working on that14:33
ogra_np14:33
ogra_rsalveti, in general out rtm seed changes will now be rather hackish ...14:33
rsalvetiogra_: yeah =\14:34
ogra_needing to hack meta directly14:34
rsalvetiurgh14:35
ogra_yeah14:35
Chipacaogra_: INteresting. thanks.14:36
brendandtvoss, take a video in portrait mode and view it in the photo roll14:36
brendandtvoss, it will be sideways14:37
brendandtvoss, it will be played in the correct orientation though14:37
ogra_jhodapp, is that the thumbnail rotation fix you are working on ^^^ ?14:37
jhodappogra_, the video yes, but the preview in the photo roll is not me14:38
jhodappogra_, that's Satoris14:38
tvossjhodapp, but it's a known issue?14:38
jhodapptvoss, yes14:38
tvossbrendand, ^14:39
brendandjhodapp, sorry i thought that was fixed in RTM14:39
jhodappbrendand, if it was I've never seen it :)14:40
jhodappbrendand, we need to ping Satoris to see if he ever got that landed14:40
jhodappbrendand, he was working on it in DC14:40
tvossbrendand, just tried without my silo, same issue14:41
brendandtvoss, ok14:41
tvossbrendand, did you see any unity 8 crash?14:41
brendandtvoss, not so far. but haven't been using it that long14:42
tvossbrendand, ack14:42
tvossbrendand, it will go through full qa for that anyway14:42
tvossbrendand, do you test vivid or rtm?14:42
brendandtvoss, vivid, as you asked14:42
tvossbrendand, ack and thx14:42
ogra_Chipaca, do you need anything more ? else i'll force the update14:43
Chipacaogra_: dmesg?14:45
Chipacaogra_: just in case :)14:45
=== karni is now known as karni-afk
ogra_Chipaca, http://paste.ubuntu.com/8836542/ ... beware, it is hugfe14:51
ogra_*huge even14:51
sil2100Ursinha: right, missed the test, fixed it now - before I can land this I need to talk with slangasek or someone from the archive admins first though14:51
sil2100:)14:51
Chipacaogra_: for next time, remind me to ask you for dmesg -T :)14:52
ogra_Chipaca, one sec14:52
Chipacaogra_: nah, it's fine14:52
Chipacaogra_: nothing there of interest to me :-(14:52
ogra_yeah, it looked like ... apart from the sleep and wakeup messages perhaps14:53
Chipacawas hoping for a juice OOM or something :)14:53
ogra_heh14:53
Chipacaanyway, school run14:53
Ursinhasil2100: okay :)14:55
sil2100slangasek: ping14:55
thostr_jhodapp: brendand: the rotation fix is in vivid... back then it wasn't seen as critical enough14:56
fgintherballoons, I added a bug report14:56
jhodappthostr_, it's not in vivid yet, just confirmed that with Satoris14:57
jhodappthostr_, he's going to get it landed in vivid shortly14:57
satorisThis is the MR: https://code.launchpad.net/~jpakkane/thumbnailer/videoflip/+merge/23890714:57
thostr_jhodapp: ok. brendand: how critical do you see this for rtm? adding to wishlist?14:57
jhodappthostr_, I personally think it's pretty critical since it's a very easy bug to spot for anybody14:58
satorisI'd want to talk to jamesh first. Thumbnailer does not have an rtm branch yet because we have kept them identical for the time being.14:58
thostr_satoris: but if it's identical then landing to rtm should be even easier, no?14:59
=== plars changed the topic of #ubuntu-ci-eng to: Need a silo? Ping train support: trainguards | Need help with something else? Ping vanguard: plars | Train Dashboard: http://bit.ly/1mDv1FS | QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: CI Train is incapable of landing MPs into RTM if that package was previously synced from vivid. you have to mangle the versions and upload manually
sil2100thostr_, brendand: what bug are you  talking about now?15:00
ogra_sil2100, thumbnail rotation15:00
ogra_it is on the list somewhere15:00
satoristhostr_: there's stuff to land in trunk that will never make it into rtm. One of the reasons being that they are not for super duper critical top blockers.15:01
satorisEventually we need different branches.15:02
satorisIf we just want to land this one thing to rtm and trunk, then there's no problem.15:02
satorisThough didn't it already land in rtm, I remember someone from qa testing it and verifying that it works?15:03
brendandsatoris, yes it did - http://people.canonical.com/~davmor2/pr.png15:03
brendandsatoris, maybe it never landed in vivid though?15:04
satorisbrendand: it's spreadsheet line 22.15:04
satoris"Ready to build".15:04
brendandsatoris, ok - that's your concern now :)15:05
satorisbrendand: I distinctly remember talking to mirv about this ages ago (last week?). There was some confusion at the time. Why has it not built the packages by now and what do we need to do to make it happen?15:07
brendandsatoris, the landing team can help you with that15:07
brendandsil2100, ^15:07
satorisOk, thanks.15:08
sil2100satoris: let me take a look at that silo15:10
sil2100satoris: ok, just so you know - with this, trunk will start pointing to vivid releases from now on15:12
satorissil2100: ack, should we set up a branch for rtm and if yes are there instructions on how to do that correctly?15:13
=== karni-afk is now known as karni
sil2100satoris: this depends on how you want to develop - if you're certain that anything that you work on eventually should go to ubuntu-rtm, then you can stay with one trunk and just sync to ubuntu-rtm15:15
sil2100satoris: but if you think you want to develop features/changes that are not meant for ubuntu-rtm, then just do a copy of the current trunk to some different name and use that one for ubuntu-rtm landings15:15
sil2100Where you would only cherry-pick changes that are rtm-enabled15:15
satorisOk, thanks for the info.15:16
brendandtvoss, so i don't get any volume overlay at all here15:32
brendandtvoss, unless somehow that feature isn't in vivid...15:32
sil2100pstolowski: can you try working on your silo now? e.g. rebuilding it?15:44
pstolowskisil2100, ok15:45
=== chihchun_afk is now known as chihchun
pstolowskisil2100, i'll soon need to do the same excercise with new rtm branch for another project (unity-scopes-shell)15:51
sil2100pstolowski: if all works correctly for -api, then it should work for all branches now15:52
sil2100I bumped the ubuntu-rtm version number to the current development focus15:52
sil2100(it's a hotfix, but we need to figure out how to proceed with this for the future)15:53
cjwatsonogra_,mdeslaur: I'd like to review whatever you/whoever do to fiddle with cipher configs, btw; not around that much this week but I'll see highlights eventually15:54
sil2100tvoss: hey! How's the CPU eater bug? What's the overall status on all fronts?15:57
ogra_cjwatson, will show you once i have somethin15:58
bzoltancjwatson: ogra_: mdeslaur: would it be possible to enable those "unsafe" ciphers only when the dev mode is switched on? The  fix for QtCreator to support the more safe ciphers are not going to come quick.. more like months than weeks.15:58
ogra_bzoltan, i would just add them to the hardcoded cmdline we already have in the ssh.override upstart job15:59
cjwatsonyes, that sounds like a good idea to make it easier to control15:59
ogra_fancy dev mode integration is just extra work for something we want to drop asap16:00
ogra_cjwatson, yeah, i imagine the implementation is trivial, my biggest fear is that we forget about it (which is why i'm so reluctant to add it)16:01
cjwatsonbzoltan: I'm surprised it's that hard though; a minimal fix for 6.7 interoperability doesn't require a fundamental new cipher implementation, just running it in a different mode (CTR rather than CBC)16:03
cjwatsonbzoltan: And QtC uses libbotan, as far as I can see, which already supports CTR mode16:04
cjwatsonSshEncryptionFacility::makeCipherMode and SshDecryptionFacility::makeCipherMode would need to be made smarter of course16:07
cjwatsonI appreciate that it requires getting somebody with relevant competence to care, but it looks like it needs plumbing rather than actual difficult new crypto code16:07
cjwatsonBumping to aes256-ctr rather than just aes128-ctr while there would be a good idea too, but that actually does look trivial once the cipher mode stuff is done16:08
slangaseksil2100: contentless pong? :)16:08
sil2100slangasek: hey! I made a hotfix for CI Train which I'm not sure if is good or not - people had trouble with releasing stuff to rtm from their RTM trunks when they made any syncs from vivid before16:10
bzoltancjwatson:  you are right. But note that it is about changing the QtC upstream code, what has never been quick. Even if it is a single line change. Also , the fix would land on teh upstream's trunk and migrating to a new QtC would take some time too. It is more time consuming job than difficult.16:10
sil2100slangasek: as per topic, every sync from vivid carried a 15.04 number in the version number, while native builds for ubuntu-rtm used 14.10 in the versions16:10
sil2100slangasek: so what I did I made it to now use 15.04 as well16:11
sil2100slangasek: + the additional append of ~rtm of course16:11
cjwatsonbzoltan: Well, that's certainly the type of change we ought to cherry-pick16:14
bzoltancjwatson: at least we managed to draw the upstream's attention to it https://bugreports.qt-project.org/browse/QTCREATORBUG-13340 I will for sure backport the fix in a form of distro patch to LTS and U/V when it comes out.16:17
cjwatsonGreat16:17
=== sil2100 changed the topic of #ubuntu-ci-eng to: Need a silo? Ping train support: trainguards | Need help with something else? Ping vanguard: plars | Train Dashboard: http://bit.ly/1mDv1FS | QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: None
slangaseksil2100: I don't understand the concern here - this is just about whether it's ok to use 15.04 as the version number for packages in rtm/14.09?16:21
sil2100Yes16:21
ogra_well, there isnt really an alternative :)16:22
sil2100So I made it that ubuntu-rtm-built silos will generate version numbers in the format of 1.1+15.04.20141105~rtm now instead of 1.1+14.10.20141105~rtm - just asking in case you have any better ways of solving this16:23
sil2100To enable both syncs and 'native' builds16:23
=== chihchun is now known as chihchun_afk
sil2100tvoss: ping16:53
sil2100ricmm: ping16:53
ricmmsil2100: sup16:54
pstolowskisil2100, #60 has been built ok16:54
ricmmsil2100: whats up?16:57
sil2100pstolowski: \o16:57
sil2100ricmm: hey! How's the media-hub fix for the CPU issue, is that landed already?16:57
ricmmsil2100: its moving through the bowels of the landing process17:03
sil2100davmor2: meeting!17:04
john-mcaleelyogra_, sil2100 new device tarball, incoming17:24
john-mcaleelyhttp://people.canonical.com/~jhm/barajas/device_krillin-20141105-4a6bca7.tar.xz17:24
john-mcaleelyhttp://people.canonical.com/~jhm/barajas/device_krillin-20141105-4a6bca7.changes17:24
ogra_whee !!17:24
john-mcaleelyhttp://people.canonical.com/~jhm/barajas/device_krillin-testresults-20141105-4a6bca7.ods17:24
john-mcaleelythis will be the last 'universal' tarball. next time I'll be doing separate ones for rtm & V17:25
john-mcaleelyany chance of davmor2 or brendand taking a look at this when they have time in their queue17:25
john-mcaleelyfixes are from the list, but not TOPBLOCKER17:25
john-mcaleely(to make priority calls)17:25
john-mcaleelysil2100, ^ :-)17:26
brendanddavmor2, add that to the trello board17:28
brendandjohn-mcaleely, davmor2 should be able to look at it today/tomorrow17:29
john-mcaleelybrendand, sounds perfect, thanks!17:30
sil2100\o/17:32
sil2100john-mcaleely: but all from the wishlist, right?17:32
john-mcaleelysil2100, yes17:34
davmor2john-mcaleely, sil2100: what all there is only one change :)17:46
tedgtrainguards, can I get a silo for line 85 please?17:47
ogra_davmor2, but it will make your logs 50MB smaller :)17:47
ribrutedg: vivid 2417:48
davmor2ogra_: turn logs off they will be at 0MB then ;)17:51
ogra_haha17:52
tedgribru, thanks!17:55
ribrutedg: you're welcome!17:56
ribruinfinity: https://ci-train.ubuntu.com/job/ubuntu-landing-014-2-publish/lastSuccessfulBuild/artifact/packaging_changes_compiz_1%3A0.9.12.0+15.04.20141105-0ubuntu1.diff here's the response to your NACK, can you confirm it's now up to your standards? thx17:56
=== alan_g is now known as alan_g|EOD
john-mcaleelydavmor2, but it's a change on 'the list' :-)18:14
davmor2john-mcaleely: indeed I didn't say it wasn't, it was just the way sil2100 said ALL18:16
john-mcaleelydavmor2, :-)18:16
john-mcaleelyset logic still works for 1 item in the set :-P18:16
tvossdavmor2, you still around?18:39
=== tvoss is now known as tvoss|test
=== tvoss|test is now known as tvoss
tvosssil2100, pong18:41
ogra_dont disturb davmor2 he is testing a heavy patchset in the device tarball :P18:42
tvosssil2100, or better: ping18:42
sil2100tvoss: ping pong18:49
sil2100ogra_: ;p18:49
ogra_:)18:49
john-mcaleelylol18:50
davmor2ogra_: no I'm not I was at tea and then I have the sanity testing on mako to finish first :P18:56
=== plars changed the topic of #ubuntu-ci-eng to: Need a silo? Ping train support: trainguards | Need help with something else? Ping vanguard: cihelp | Train Dashboard: http://bit.ly/1mDv1FS | QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: None
ribrutvoss: https://ci-train.ubuntu.com/job/ubuntu-landing-007-2-publish/28/console needs top approvals19:02
tvossribru, ack, gimme two19:04
=== Saviq-codedive is now known as Saviq
tvossribru, top-approved19:07
ribrutvoss: thanks19:07
davmor2tvoss: I'm back around now19:07
tvossdavmor2, ack19:07
davmor2john-mcaleely: can you check the permissions on the tar ball please19:13
john-mcaleelydavmor2, argh19:14
john-mcaleelydavmor2, I can. I have. they are now fixed. sorry!19:14
davmor2john-mcaleely: makes it easier to test when you can download it :)19:15
john-mcaleelydavmor2, over-rated!19:16
* davmor2 Fails the tarball on grounds of untestability 19:18
sil2100davmor2: ;)19:18
=== karni is now known as karni-afk
davmor2john-mcaleely, sil2100, ogra_: right flashing now19:19
davmor2john-mcaleely: about an hour I'll give you a ping19:20
john-mcaleelydavmor2, I'll be around19:20
john-mcaleelydavmor2, thanks!19:20
ribruungh19:31
* sil2100 jumps out for a while, bbl19:40
balloonsping fginther19:49
fgintherballoons, hey19:49
balloonsfginther, :-) howdy. So I have a quick question/ request. Can we make sure all the click jobs for core apps on s-jenkins build automagically after a merge to trunk? It seems calender for instance does not:19:49
balloonshttp://s-jenkins.ubuntu-ci:8080/job/calendar-app-click/19:49
fgintherballoons, yeah that just sounds like a bug in the job, I can try to fix that19:51
=== karni-afk is now known as karni
=== fginther changed the topic of #ubuntu-ci-eng to: Need a silo? Ping train support: trainguards | Need help with something else? Ping vanguard: fginther | Train Dashboard: http://bit.ly/1mDv1FS | QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: None
davmor2john-mcaleely: so the sanity test passed, next to look at the logs and see what that is like :)19:53
john-mcaleely\o/19:53
ogra_still noisy i guess19:53
ogra_but a lot less than before :)19:54
ogra_(not one line per second at least)19:54
brendandtvoss, around?19:54
john-mcaleelywhen the machine was 'doing nothing', the logs did seem to stop when I looked19:54
tvossbregma, yup19:54
john-mcaleelywhich seemed like a plus19:55
tvossbrendand, for the volume overlay: that's not in vivid19:55
ogra_john-mcaleely, yeah, but fallung asleep and waking up still produce like 30lines or so per event19:55
john-mcaleelyit's an important event!19:55
ogra_lol19:55
john-mcaleely:-)19:55
brendandtvoss, yeah realised that in the end19:59
brendandtvoss, after reflashing19:59
brendandtvoss, seems like a few things have not landed there19:59
tvossbrendand, yup20:03
tvossbrendand, so with that, I set the vivid silo to testing done20:03
davmor2john-mcaleely: phablet@ubuntu-phablet:~$ ls -l /var/log/syslog   -rw-r----- 1 syslog adm 550734 Nov  5 20:02 /var/log/syslog    That doesn't in comparison to the -rw-r----- 1 syslog adm 2438369 Nov  5 20:04 /var/log/syslog on mako that has been up for 2 hours20:05
davmor2john-mcaleely: I'd say let it loose20:05
brendandtvoss, and the crashing is apparently gone - bonus!20:05
ogra_yay20:05
tvossbrendand, yup20:05
davmor2ogra_: should be roughly a 40-45% reduction that's not bad20:08
ogra_i want 90-95% :P20:08
ogra_but yeah, its a good start :)20:08
davmor2ogra_: turn all logs off you get 100% :P20:09
davmor2ogra_: man you had to talk to john-mcaleely about falling asleep and now we get no response from him,  I blame you entirely ;)20:12
ogra_hahaha20:12
davmor2ogra_: you and your hypnotic text20:13
ogra_*grin*20:13
davmor2ogra_: no that would be a proper Muhahahahaha and rubbing of hands :)20:14
davmor2evil plotting ahead :)20:14
=== fginther changed the topic of #ubuntu-ci-eng to: Need a silo? Ping train support: trainguards | Need help with something else? Ping vanguard: cihelp | Train Dashboard: http://bit.ly/1mDv1FS | QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: None
ribruSaviq: vivid 1620:28
ribrukgunn: ^20:28
kgunnsah-weet20:29
bfillerribru: can you publish rtm silo 6 please?20:46
sergiusensplars: hey, do the jobs/workers auto update from ppa:phablet-team/tools ?20:48
plarssergiusens: no20:49
sergiusensplars: you copy to another ppa?20:49
sergiusensplars: or just do it manually?20:49
plarssergiusens: not at the moment, but I would assume that we'll need to once it goes over to an is-control production server20:49
plarssergiusens: at the moment, we have some control over the box, so we just update packages as needed20:50
sergiusensplars: when the adb stuff lands, you'll need what landed in vivid today20:50
plarssergiusens: ok, what's changing?20:50
plarssergiusens: and we're not running vivid, we're on trusty20:50
sergiusensplars: adb only enabled after the screen is unlocked20:50
sergiusensplars: it's the same package ppa-copy-ed20:50
plarssergiusens: err, so is there a new option for this? or does --developer-mode still take care of it all for us?20:51
sergiusensplars: it's what I had you test during the sprint, no new option, no flag day, no zero day; --developer-mode takes care of it20:51
sergiusensplars: and it's harmless to use before the device stuff lands20:52
plarssergiusens: I didn't test this during the sprint did I? I thought all I tested was the new ubuntu-device-flash that added subcommands20:52
sergiusensplars: right20:52
sergiusensplars: but it's a noop today20:52
plarssergiusens: ok, when do you expect it will hit the ppa?20:53
sergiusensplars: as soon as you want it too20:53
sergiusensplars: when would you want to update?20:54
plarssergiusens: I can update it anytime20:54
sergiusensplars: great, I'll ping you once copied20:58
john-mcaleelyso, thanks davmor220:59
john-mcaleelyI guess I push this tarball then ogra_ ?20:59
sergiusensplars: will you juju setup the box eventually?21:00
plarssergiusens: it's like that now21:01
sergiusensplars: oh, nice21:01
plars:)21:01
john-mcaleelyin the absense of ogra_ I think I need to check with the trainguards to see if a build is underway right now?21:01
john-mcaleelyif not, I think I'm clear to push21:01
ribrujohn-mcaleely: a build of what?21:02
sergiusensjohn-mcaleely: I can check on cdimage21:02
john-mcaleelyribru that ^ thanks sergiusens21:02
ribrucool21:02
sergiusensjohn-mcaleely: nothing seems to be running on cdimage21:08
john-mcaleelysergiusens, thanks. I'll push it then :-)21:08
john-mcaleelyogra, sergiusens pushed. should see a build appear in 30 mins or so21:09
john-mcaleelyogra_, ^21:09
john-mcaleelysil2100, ^21:13
infinitybregma: That new changelog looks much better, thanks!21:16
bregmainfinity, I'm still learning how to defeat the ci-train robot's idea of what a good changelog looks like21:17
* bregma is getting a bigger hammer21:17
infinitysil2100: What's the magic required to register my ACK of bregma's compiz changes?21:20
AlbertA2trainguards: can vivid silo landing-017 be published?21:26
nik90sergiusens, ogra_: Who do I talk to with regards to the volume of a phone call or alarm? Since the recent update (#6 on N4), despite the volume slider set to maximum, I can barely hear a phone call or an alarm. I just read an email in the mailing list where another person also experienced this.21:38
tedgtrainguards, can you please publish vivid/24 ?21:46
sergiusensnik90: that would be rsalveti21:46
nik90sergiusens: cool, thnx21:47
ribrukenvandine: mterry: any core devs around for a packaging ack? https://ci-train.ubuntu.com/job/ubuntu-landing-017-2-publish/lastSuccessfulBuild/artifact/packaging_changes_location-service_2.1+15.04.20141105.1-0ubuntu1.diff is adding boost-dev, IIRC that's tricky22:02
* kenvandine looks22:03
ribrutedg: sorry was on lunch, published22:03
kenvandineribru, that looks fine22:04
kenvandine+122:04
tedgribru, No worries, thanks!22:05
ribrutedg: you're welcome22:05
ribrukenvandine: isn't there some kind of restriction where boost-dev can't be in main, you have to check which individual boost components you're using and only depend on those instead? like boost-dev is too large a thing and brings in too many unused deps or something22:06
kenvandineit is in main22:06
kenvandinethe dev package needs some headers from boost to work, so it's really so other apps that build depend on location service22:07
kenvandineget the right build depends22:07
kenvandineone thing that has bitten us in versioned dev packages22:07
kenvandinelike libboost-54-dev22:07
kenvandineor something... that has caused all kinds of pain in the past22:08
ribrukenvandine: hm, not sure what I'm thinking of then22:08
kenvandinewell there are a bunch of broken down ones22:08
kenvandinewe wouldn't want the runtime of location service to depend on all of libboost22:09
kenvandinebut this is just the -dev package22:09
kenvandinedepending on the other -dev22:09
kenvandineit could make builds faster if they depended on libboost-math1.55-dev22:10
ribrukenvandine: ahhh ok, it's the runtime I'm thinking of then. thx22:10
kenvandinefor example22:10
kenvandineif all they needed was in that22:10
kenvandinebut then again... that's versioned hell22:10
kenvandinei think there are virtuals for all of those actually22:10
kenvandinebut for dev packages, i wouldn't make a stink about it22:10
rsalvetinik90: is this with vivid?23:37
rsalvetinothing changed in the audio stack, wonder if something else is causing that bug23:37
nik90rsalveti: no this is rtm image #6 stable image23:38
nik90it seems another person on the mailing list has that issue23:39
rsalvetinik90: that's interesting, mind opening a bug?23:39
rsalveticould be against pulseaudio, will try to take a look23:39
nik90I talked to brendand about it, and he said I should try adjusting the volume while receiving the call since that would then change the ringer volume instead of the media volume.23:39
nik90If that doesnt fix it, then I will report the bug23:40
rsalvetiright, it depends on the active role23:42
rsalvetifor you to change the current volume for voice call you need to have an active voice call in place23:43
rsalvetiand then try changing volume23:43
rsalvetiwithout anything playing, it'll change the volume for the alert role by default23:43
rsalvetiwhich means ringtone23:43
rsalvetisame for alarm and multimedia23:43
nik90rsalveti: which is fine, but there should still be a UI for this where it shows the volume for individual roles23:49
rsalvetinik90: indeed, that's something that would be part of system settings23:49
nik90rsalveti: is that something targetted for rtm, or ota?23:49
rsalvetiprobably for ota, but would need to check23:50
nik90ok23:50

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!