/srv/irclogs.ubuntu.com/2016/03/14/#ubuntu-ci-eng.txt

=== chihchun_afk is now known as chihchun
=== chihchun is now known as chihchun_afk
=== chihchun_afk is now known as chihchun
=== Saviq_ is now known as Saviq
jin_dpm: ping08:33
dpmhi jin_, please, feel free to ask directly, no need to ping first08:33
jin_dpm: thanks for your comment in the MP I raised08:34
jin_I left some comments there and need you to take a look ;)08:34
jin_sending you the link:08:34
jin_dpm: https://code.launchpad.net/~libqtelegram-team/telegram-app/remove-po-files-from-version-control/+merge/28888308:34
jin_dpm: any comments from you will be welcomed, thanks!08:35
dpmjin_, oh, why do you want to remove the po files from bzr?08:36
jin_dpm: I just removed those .po files from only "bzr record"08:36
jin_no effects to the real *.po files we have in the branch/trunk08:36
dpmjin_, what's bzr record?08:37
jin_so that leave all *.po files updated by Launchpad itself08:37
jin_= bzr version control08:37
jin_since main trunk already tracked (means record these .po files in bzr)08:38
jin_so if we wanna untrack .po files, we can use this way to unmark them in bzr08:39
robrujin_: i don't think that's how it works... the mp looks pretty clearly like you are removing all .po from trunk.08:40
dpmyeah08:40
dpmjin_, what's the trunk branch you are talking about?08:40
jin_dpm: lp:telegram-app08:40
jin_this one08:40
dpmjin_, the way I read the MP, you're effectively a) ignoring all *.po files in bzr, then b) removing them from revision control and c) hoping that LP will regardless auto-commit translations there08:41
robrujin_: yea I don't know why you want to "untrack" .po files, we want those tracked so that launchpad can update them.08:41
dpmI'm not quite sure c) works08:41
robrudpm: even if c) worked it'd just undo what this branch is doing.08:41
dpmagreed08:41
dpmjin_, all that was needed was to revert the po file changes on that other branch that you guys were trying to merge08:42
jin_dpm: yeah.... I get it now..08:42
dpmor even then, you could actually merge the .po changes if you want to keep things easy, and LP will overwrite the .po files on the next translations auto-commit. But I think it'd make more sense to just leave the .po files alone alltogether08:43
jin_dmp: okay, thanks, so the only thing need to be added at the moment I think will be the .bzrignore08:43
jin_dmp: yes, yes08:43
jin_dpm: okay, I will modify the MP ;)08:43
dpmI'm not sure I'd do that either, as LP is using bzr and is not ignoring the .po files08:44
jin_(sorry for typo)08:44
dpmno worries08:44
dpmI mean LP auto-commits to the translations branch, using bzr08:44
jin_dpm: yeah I see what you mean08:44
dpmI think all I'd do would be to revert all .po file changes on that branch: https://code.launchpad.net/~libqtelegram-team/telegram-app/converged/+merge/28686108:45
jin_dpm: good idea, and that makes sense to me,08:45
jin_dpm: I will add a patch to the merge you mentioned08:46
dpmjin_, no worries: and actually, unrelated, but while we're on that subject...08:46
jin_dpm: thanks ;)08:46
dpm-#: /home/karni/src/telegram/telegram-app/v2/telegram/app/qml/components/DelegateUtils.qml:4108:46
dpm2122+#: /home/jin/Works/Applications/Telegram/converged/telegram/app/qml/components/DelegateUtils.qml:4108:46
dpmthese are the changes that were made to the .po files ^^08:47
dpmI'd recommend not to hardcode your home directory paths there08:47
dpmand make the paths in the .po files relatives08:47
jin_dpm: make sense08:47
dpmthat'd help you: a) keep privacy of your personal filesystem layout :) and b) not have to modify all files when a new developer comes along08:48
jin_dpm: okay, will do!08:49
jin_;)08:49
dpmjin_, have a look at http://bazaar.launchpad.net/~ubuntu-clock-dev/ubuntu-clock-app/trunk/view/head:/po/CMakeLists.txt - that is how the core apps do it (clock, in this example)08:49
jin_dpm: hmmmm from #2308:50
jin_dpm: checking08:51
dpmjin_, I think it's rather in the first command, starting at L808:51
jin_dpm: right.. good reference, Telegram will follow08:52
dpmI can't remember exactly which part takes care of it, perhaps L13 or L14. But I see telegram uses .pro files and qmake instead of CMakeLists.txt and cmake, so you will need to adapt to it. We used to have an example of doing this in qmake, but then we migrated to cmake.08:53
dpmbut if it turns out not to be trivial, I can see if I can find that example08:53
dpmit should be in old revisions of the clock tree, or in any other core app's old history08:54
alextuhi~ there , I just created a ci-train request there, https://requests.ci-train.ubuntu.com/#/ticket/1108 , but can not see my ticket on trello : https://trello.com/b/AE3swczu/qa-testing-requests-for-questions-ping-ubuntu-qa-on-ubuntu-ci-eng08:54
alextuI used to change the status to "read for QA", but it seems can not be set now .08:55
jin_dpm: sure! I will search that and look a look deeper (make Telegram adaptive on this way), will ask you to be the reviewer after done,08:55
alextuDoes someone know how can I let my ticket present in trello list ?08:55
alextudavmor2, ^08:56
jin_dpm: at the moment I think I will drop the merge proposal I just mentioned, is that okay to you?08:56
dpmsure, thanks jin_!08:56
dpmyes to both :)08:56
jin_dpm: thanks mate! we will do that!08:56
dpmcook08:56
jin_dpm: nice! super08:56
dpm*cool :)08:56
michirobru: ping09:23
robrumichi: Heya09:27
michiHey. Why did you reject your MR?09:28
michiI suspect it will have merged already09:28
Mirvjibel: davmor2: lukasz is away, do you have any topics for the hangout?09:28
jibelMirv, nothing from me09:28
michirobru: Yes, it has merged already.09:29
michiTo remove it, we’ll have to do another MR with a reverse diff, or hack devel by hand.09:29
robrumichi: oh you merged it already? I hadn't seen that. Didn't you see my comment about the extra commits?09:29
michiCurrently, it is still the most recent revision, so it’s easy to revert09:29
michiSure.09:30
Mirvjibel: davmor2: ok let's skip it then. I can't even complain about GPS anymore since it's working great now.. landings seem ~normal at the moment.09:30
michiThat was just because you based it on trunk.09:30
michiWe do all the work on devel and merge periodially in bulk to trunk.09:30
michiVia the silo09:30
robrumichi: yeah but that means there were trunk commits not in devel09:30
michiSo, rejecting this has done nothing.09:30
michiI don’t believe there were any.09:30
michiThere shouldn’t be.09:31
michiNot normally09:31
michipstolowski: ^09:31
davmor2Mirv: alextu might need a hand with his silo for the device tarball https://requests.ci-train.ubuntu.com/#/ticket/1108 he can't set it manually to qa ready09:31
robrumichi: i know rejecting it doesn't revert it, i just didn't notice it had been merged already, had a stale tab open i didn't refresh09:31
michipstolowski: This is the MR: https://code.launchpad.net/~robru/unity-scopes-api/vivid-tweaks/+merge/28886509:31
michirobru: No problem.09:31
michiSo, I tested this yesterday and was happy with it, so I approved.09:31
michiIf you are happy with it too, it’s all good.09:32
robrumichi: yeah I'm happy with the work i did, i was just worried the extra commits would cause a problem. If there's no problem for you then it's fine i guess09:33
michiNo, no problem. Can you top-approve again please?09:33
michiOtherwise, it’ll look weird later.09:33
robrumichi: yep, done. Reviewed the diff, looks good, I'm not sure what those extra commits were but i don't see them in the diff09:34
michiTrunk was behind devel.09:34
robrumichi: no trunk was ahead of devel09:34
michiSo, when you rebased against devel, you probably didn’t do a pull first?09:35
Mirvdavmor2: alextu: ok the 1108 is now set to Ready (for QA)09:35
michirobru: Not sure whether trunk was behind. Let me check...09:35
robrumichi: i started with trunk, did my commits, then just merged devel09:36
davmor2Mirv: thanks dude09:36
michiSorry, “ahead”, I meant.09:36
robrumichi: so extra trunk commits were in my branch09:36
michiThat’s trunk: 359: CI Train Bot 2016-02-09 {1.0.3+16.04.20160209-0ubuntu1} Releasing 1.0.3+16.04.20160209-0ubuntu109:36
michiThere were changes to devel since, but not the other way around.09:37
michiMaybe your devel was out of date or something?09:37
robrumichi: the changelog of the silo is generated by running "bzr missing" against the branch before merging it, so the fact that names other than mine were in the changelog could only happen if there were commits on the branch not by me, and not in devel09:37
michiAnyway, when I tested and pulled your MR, it all looked good.09:37
alextuMirv, thanks a lot, but I still can not see it on trello, so should I track it until it present on trello ? https://trello.com/b/AE3swczu/qa-testing-requests-for-questions-ping-ubuntu-qa-on-ubuntu-ci-eng09:37
michirobru: I honestly have no idea what happened there.09:38
robrumichi: OK well if it looked good to you i guess i won't worry too much, but the diff i made in the staging silo looked weird so I was worried09:38
michiBut devel is where the action is for us, and devel is healthy.09:38
michiWhat I saw there were lots of changes we’d made to devel in the past few weeks.09:38
robrumichi: OK great09:39
michiLike the logging changes, which was the bulk of the diff.09:39
michiNo more boost::log, finally!09:39
robruYay!09:39
pstolowskimichi, robru is this critical for ota10?09:43
michiI don’t know. robru ?09:44
Mirvalextu: there's just a few minutes' delay there, it's now there already09:44
pstolowskii know it's not a feature etc. the question is if it's worth disrupting the existing big unity8/filters silo with it?09:45
robrupstolowski: michi nope nope, it doesn't affect anything at all, totally not noticeable change, just prepping for train changes that are still a month or more away09:45
michipstolowski: No need to get it into the silo then.09:45
robruYep09:45
alextuMirv, cool! thanks for help09:47
Mirvno problem!09:48
pstolowskimichi, robru ok, we will land it on the next occasion then09:49
robrupstolowski: yep, no rush, thanks09:52
=== essembe is now known as sbeattie
morphisMirv: you know what is with sil2100 today?11:25
Mirvmorphis: he's away, back tomorrow11:25
morphisMirv: ah ok, can you publish https://requests.ci-train.ubuntu.com/#/ticket/1081 instead?11:26
morphisMirv: or should I better wait for sil2100 to be back?11:27
Mirvmorphis: looks ok, approved by QA, but what's up with those unresolved emulator dependencies mentioned by britney?11:28
MirvI see there's no actual related packaging change, but just interested11:30
morphisMirv: sil2100 said that is due to some missing things for britney, afaik he just published it last time for this landing11:30
Mirvmorphis: ok, that's good enough for me. maybe something multi-arch related, the emulator is a bit special.11:32
morphisMirv: good11:33
Mirvmorphis: seems to be at correct places now, let's see if xenial release pocket migration is of any problem because of that same thing11:36
morphisMirv: yeah11:36
=== chihchun is now known as chihchun_afk
=== kyrofa_ is now known as kyrofa
=== alan_g is now known as alan_g|lunch
=== chihchun_afk is now known as chihchun
=== chihchun is now known as chihchun_afk
=== koza|away is now known as koza
=== alan_g|lunch is now known as alan_g
boikorobru: could you please rebuild dialer-app on xenial ppc64el on silo 78?14:11
rvrrenatu: ping14:20
renaturvr, hi14:23
rvrrenatu: Hey14:28
rvrrenatu: I'm testing silo 22. I found a problem creating a yearly event.14:29
rvrrenatu: It won't let me go back.14:29
renaturvr, what do you mean?14:29
rvrrenatu: In the Repeat screen, selecting the "Yearly" frequency, I can't go back to the Create event screen.14:30
rvrrenatu: file:///opt/click.ubuntu.com/com.ubuntu.calendar/0.5.775/EventRepetition.qml:120: TypeError: Cannot call method 'getMonth' of null14:30
rvrHmm... I can in the store version.14:31
renatuyeah this is a know bug it is fixed on a new branch14:31
rvrrenatu: Does it only happens with version 0.5.775?14:32
renatuno its happen before14:32
rvrrenatu: Ah, just tried with the version in the store and couldn't reproduce it14:34
rvrhttps://bugs.launchpad.net/ubuntu-calendar-app/+bug/143891014:36
ubot5Launchpad bug 1438910 in qtorganizer5-eds (Ubuntu) "unable to set event as yearly or monthly" [Undecided,In progress]14:36
renaturvr, this is the branch to fix that: https://code.launchpad.net/~renatofilho/ubuntu-calendar-app/fix-edit-ocurrence14:39
renatuwill be the next MR on the list14:39
renaturvr, if you want I can merge it now and send a new package14:40
renaturvr, but in any cases recurrence is buggy on the calendar app, and we are preparing a new set of MR to fix that14:41
rvrrenatu: I was worried it was a regression introduced by the package in the silo, but as it is not, the fix can wait to another silo.14:42
renaturvr, thanks14:43
Mirvubuntu-qa: can you confirm that oxide silo https://requests.ci-train.ubuntu.com/#/ticket/1085 wouldn't need QA signoff?14:48
davmor2oxide would need qa sign off14:49
rvrMirv: ??14:49
rvrMirv: Of course it needs QA :)14:49
Mirvrvr: yes, that's why I pointed you to it14:50
rvrMirv: It says "N/A" :-/14:50
Mirvrvr: so I'm taking dbarth meant it's ready for QA instead of "N/A", and putting into your queue14:50
rvrMirv: Ahh, thanks14:50
Mirvexcept that it resets back to N/A :(14:51
Mirvweird14:51
rvrMirv: That blue color, usually is set when the silo is ok to publish :-/14:51
Mirvrvr: yes, and that is true if QA wouldn't be needed ("N/A"), which is incorrect14:52
jibelMirv, it's one a the feature we're waiting for this ota14:52
Mirvrvr: for now, I'm adding a DO NOT PUBLISH comment there14:52
Mirvjibel: can you put it into the queue manually since train is not accepting my commands?14:52
rvrMirv: Great, thanks14:52
rvrI'll do14:53
Mirvrobru: is there a particular reason why https://requests.ci-train.ubuntu.com/#/ticket/1085 does not allow changing "N/A" to Required or Ready? it keeps on resetting back.14:53
jibelinteresting bug in bileto14:53
Mirvrvr: ok, thanks!14:53
jibelMirv, forced to 'ready for qa'14:53
Mirvjibel: oh, why the train respects you more than me!14:54
rvrlol14:54
davmor2Mirv: we're in QA we have bigger hammers14:54
Mirv:(14:54
jibelMirv, you didn't whisper the sweet words it expected14:54
Mirvmeanwhile I'm recreating the diff since the silo was also not targeted to overlay14:54
davmor2Mirv: the secrets are "Work or I'll rip you hard drive out"14:55
=== chihchun_afk is now known as chihchun
boikotrainguards: can someone please rebuild dialer-app on xenial ppc64el on silo 78?15:06
mzanettitrainguards, the silo bumps unity8 version to 8.13 here even though no branch does that. We did have a branch in there which did it but it was removed.15:18
mzanetticould it be that it doesn't ever decrease the version again unless we'd clear the unity8 package out of the silo and do a clean build?15:19
cjwatsonboiko: done15:57
Mirvboiko: seems done now16:14
Mirvmzanetti: yes it's possible it works like that.16:14
Mirvmzanetti: but we could try deleting both the superseded and current package and then try again in 30mins or so16:15
Mirvmzanetti: since you apparently don't want 8.13 anyway, I'm trying that16:16
mzanettiMirv, let me just ask back with the team... might be they rely on the 8.13 fact already. will let you know in a bit16:16
Mirvmzanetti: oh, ok16:16
popeydavmor2: have you seen any notifications on latest rc-proposed? on my krillin I'm seeing grey on grey, unreadable notifications16:21
popeydidn't get a screenshot in time16:21
kenvandinepopey, i'm seeing the same thing on arale16:21
davmor2popey: there is a bug in unity8 for it16:21
popeythanks kenvandine16:21
popeyok16:21
jibelpopey, it's a known bug16:21
popey\o/16:21
* popey goes back to sleep16:21
jibelpopey, bug 155461616:22
ubot5bug 1554616 in unity8 (Ubuntu) "Shell and dash visual issues with new UITK and palette" [Critical,In progress] https://launchpad.net/bugs/155461616:22
jibelpopey, if you find anything unity8 related not in the list please add it16:22
popeykk16:22
popeycomment 17 covers my issue16:23
=== tyhicks` is now known as tyhicks
boikocjwatson: Mirv: thanks16:36
=== koza is now known as koza|away
=== pstolowski is now known as pstolowski|bbl
rvrrenatu: ping17:30
renaturvr, hi17:34
rvrrenatu: Something weird happened with a reminder (-5 minutes). It wasn't triggered. But then I re-edited the event, and cannot reproduce.17:35
rvrrenatu: Anyway, there is this test case "Change the guests by adding and removing (swipe right)"17:35
rvrrenatu: I cannot swipe right an event, because the calendar view moves.17:36
renatulet me check the test plan, you should not swipe right the event. I think the test plans want you to swipe right the guest17:37
rvrrenatu: You may be right17:37
rvrrenatu: Event modification "Change the guests by adding and removing (swipe right), save the event, re-open and make sure the changes were properly saved"17:37
renaturvr, yes, open the event editor and swipe right a guest, save it and open again to check if the changes was commit17:38
rvrrenatu:  Right.17:38
rvrDone17:38
rvrrenatu: Final question. Will this calendar app version be published on the store?17:39
renaturvr, no. it will be land on OTA 1017:39
renaturvr, but still some fixes to land17:39
rvrrenatu: Ah, cool17:39
rvrrenatu: I'm approving the silo, then17:40
renaturvr, thanks man[17:40
renaturvr, sorry for the confusion with test plan It was wrote a log time ago. I started to work on calendar app some weeks ago17:41
rvrrenatu: np :)17:41
robrumzanetti: yes, PPAs will never accept an upload with a lower version than what was in there before, so the train always picks the highest possible version when generating version numbers. If you want to go back down, you need to abandon & reassign to get a fresh ppa17:44
mzanettiI don't think it's that critical. we'd want to bump it anyways, and as this silo is already a FFE I don't feel like it's worth delaying it any further for skipping one version number tbh17:44
mzanettibut thanks for explaining, yes17:45
robruMirv: bileto enforces na/required/ready states based on series & dest, so it wouldn't let you because it wasn't targeting overlay i think, the trick is that there's an exception for tickets with manual download URLs set, so jibel set "http://" there and then you can set any qa status17:51
robruMirv: sooner or later I'll need to fix up the qa field to behave more predictably but I've just had other priorities, sorry17:51
mzanettirobru, fwiw, Mirv dropped just the unity8 package from the silo, I've rebuilt it now and it seems to be back to 8.12 (as opposed to the wrong 8.13 from before)17:52
mzanettiso seems a complete silo clean is not required17:52
robrumzanetti: oh interesting, thanks, i was under the impression that PPAs always remembered the versions even if you deleted the packages17:53
mzanettirobru, doesn't a "clear silo" just delete all the pacakges from a ppa too?17:53
mzanettiapart from the other train magic, but from a ppa point of view it seems to be just like deleting all the packages17:54
robrumzanetti: yes, but then when you re assign, you get a different one17:54
robrumzanetti: they're assigned in random order17:54
mzanettirobru, well, but if that wouldn't be enough, we would frequently get silos with wrogn versions because someone tested something in that silo before17:54
robrumzanetti: oh do you guys bump the version number a lot? I assumed that was rare17:55
mzanettinot *a lot* but well... whenever we change something in unity-api17:55
robruFair enough17:55
mzanettiwhich does happen every 1.5 landings I'd say17:55
=== jhodapp is now known as jhodapp|errand
=== joc_ is now known as joc|away
=== pstolowski|bbl is now known as pstolowski
=== jhodapp|errand is now known as jhodapp
=== boiko_ is now known as boiko

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