/srv/irclogs.ubuntu.com/2015/07/15/#ubuntu-ci-eng.txt

=== robru changed the topic of #ubuntu-ci-eng to: Need a silo or CI Train support? ping trainguards | Need help with something else? ping cihelp | Train Dashboard: http://bit.ly/1mDv1FS | QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: Train offline because disk full; see #is-outage
=== robru changed the topic of #ubuntu-ci-eng to: Need a silo or CI Train support? ping trainguards | Need help with something else? ping cihelp | Train Dashboard: http://bit.ly/1mDv1FS | QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: -
veeberstrainguards: anyone around perchance?03:14
Mirvveebers: now there is04:53
veebersHi Mirv o/ :-)04:54
veebersMirv: I'm wondering 2 things, one why did using the silo process to release a branch add a bunch of details to the changelog: http://bazaar.launchpad.net/~canonical-platform-qa/autopilot/overlay/view/head:/debian/changelog04:54
veeberssecondly is there a way to rectify that or is changing that in the next release bad-form04:55
Mirvveebers: o/04:55
Mirvveebers: 1. autopilot fills in the changelog automatically always from the commit messages, although potentially if you edited changelog yourself it shouldn't have done that (I'm not sure about the current implementation)04:55
Mirvveebers: I don't think it's a bad thing if you manually edit the changelog for the next release04:56
veebersMirv: this is the MP that was used for that silo release04:56
veeberserr, this one: https://code.launchpad.net/~canonical-platform-qa/autopilot/overlay_fix-touch-device/+merge/26409204:56
veebersI'm not sure where all the other details came from.04:56
veebersMirv: at any rate, I can change the changelog to make more sense for the next release (will probably be tomorrow now)04:57
Mirvveebers: it's possible it wouldn't have change the changelog if you would have set the last release to UNRELEASED instead of wily in the changelog. now it added its own. but it think it's adding all the commit messages for commits that were in that branch but were not yet at lp:autopilot/overlay before the branch04:58
veebersMirv: ugh, so it's totally my fault then, that should have been UNRELEASED somehow (probably me screwing up a merge) broke that04:59
Mirvveebers: this probably wouldn't happen with a normal release process, ie if lp:autopilot/overlay actually matched what is in archives. since you have a custom process (you had your own autopilot (1.5.0) UNRELEASED; urgency=medium in the branch so the branch was not handled only by the train before), it's always a bit more fragile/delicate on how train needs to be guided in that case.05:00
Mirvveebers: ok, that's probably it then especially if your previous releases have gone according to the planning :)05:00
veebersMirv: ah right, makes sense. Annoying that I almost made a 'normal' release, and I'm about to do that again.05:01
Mirvhehe :)05:01
veebersI'll fix up the changelog log details for that though. Thanks for clarifying that05:01
MirvI'm happy you feel clarified, I'm myself always a bit puzzled with these changelog things ;)05:02
robruveebers: yeah this is a known train bug, don't have the number handy. It happens because you guys pre-merge your merges into one big mega-merge which has commits from your whole team. Train will generate sensible changelogs if you put individual merges into the silo without pre-merging05:03
robruveebers: it's on the radar to be fixed, for now i recommend writing your own changelogs05:05
veebersrobru: ack, I understand that it was triggered this time because there wasn't a 'UNRELEASED' stanza in the log?05:06
robruveebers: yeah that to, when you write your own you need to mark the entry UNRELEASED or the train will make a new entry for you.05:07
veebersrobru: ah ok, right so as Mirv mentioned had it been 'UNRELEASED' I wouldn't have seen this. I'll keep that in mind. Cheers all05:12
robruveebers: yeah the unreleased thing isn't a bug, you need to do that. But i mean the terribleness if the generated changelog is a bug that I'll work on after the spreadsheet replacement goes live, so you won't need to generate your own changelog at all.05:13
veebersrobru: ack thanks for clarification05:15
robruveebers: you're welcome!05:16
=== marcusto_ is now known as marcustomlinson
Mirvrobru o/05:23
robruMirv: how's it going? I'm winding down05:23
Mirvrobru: very well, ~well slept nights here nowadays so it's pretty good. good night!05:28
robruMirv: Ooooooooooh yeah i forgot you have a newborn! Crazy. Goodnight!05:30
Mirv:)05:35
MirvGCC5 transition of Qt nearing completion probably today05:36
AmyQuan+06:30
=== _stowa_ is now known as _stowa
sil2100davmor2: hey, did you fill in a bug for the missing icons after OTA upgrade?08:19
davmor2sil2100: nope but I can I was still trying to figure out what exactly the problem was when everything I could dig into registered correctly08:20
davmor2sil2100: was it the delta?08:20
davmor2sil2100: and I'll file one now08:20
sil2100davmor2: I want to dig deeper, but I would say it's the delta's fault08:29
sil2100I'm feeling a bit under the weather today, but I'll try digging into that if I have the chance08:29
davmor2sil2100: https://bugs.launchpad.net/canonical-devices-system-image/+bug/147473908:30
ubot5Ubuntu bug 1474739 in Canonical System Image "Move from ota4 image to ota5 image does update the override file for the favourite apps" [Undecided,New]08:30
sil2100davmor2: thanks!08:30
Mirvsil2100: FYI I start to be ready with Qt GCC5 transition.. it seems Steve is handling at least some of the other touch stack transition?08:30
sil2100Mirv: I talked with Steve and he was supposed to send me a list of packages he wants me to help out with08:31
sil2100But my mailbox is empty!08:31
Mirvsil2100: :)08:31
Mirvsil2100: maybe he's building first batch now at https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-016/+packages as it looks and then asks for help for fixing those that don't build without changes08:32
sil2100davmor2: hm, could you try something? I just want to confirm something - could you flash your arale to '2' and then OTA to '3'? Can you do that somehow?08:38
davmor2sil2100: not that I am aware of I think it only does latest let me have a look at the system-image-cli options08:40
sil2100davmor2: ok, well, I'm pretty sure it would be broken anyway... checking the custom tarball delta now08:45
sil2100hmmmm08:46
sil2100davmor2: now this is interesting, I would really like to know if OTAing to 3 results with the same problem08:48
sil2100As the delta for 3 from 2 has the correct custom.key08:48
davmor2sil2100: trying out --build to see if taht will update me to 308:49
sil2100So either something in the upgrader is busted and it doesn't apply this at all, or maybe there's a breakage that causes the custom delta not being properly applied for the case of an upgrade from 2 to 4, where the 3rd upgrade is missing08:49
sil2100davmor2: thanks!08:49
sil2100davmor2: do you know if we have any upgrade logs?08:53
davmor2sil2100: no idea08:54
sil2100davmor2: did the --build parameter work?08:56
davmor2sil2100: I think it conflicted with image 4 that had downloaded in the background I have a cunning plan though https://www.youtube.com/watch?v=pKRxX3s3JlM08:59
sil2100hoho, nice one09:01
sil2100;)09:01
sil2100I just hope your cunning plan is better!09:01
davmor2sil2100: nope I just get a black screen so that didn't go so well :(09:12
sil2100:<09:12
davmor2sil2100: cunning plan number 209:13
sil2100I'm checking the code in the meantime09:14
sil2100davmor2: hmmm, once you try your cunning plan, could you maybe run system-image-cli upgrade from 2 to 4 with --dry-run and -vvvv ?09:19
=== greyback__ is now known as greyback
=== DanChapman_ is now known as DanChapman
mzanettisil2100, hey, please drop unity-api from the ppa of silo 4811:58
sil2100mzanetti: on it11:58
mzanettithanks mate11:58
sil2100mzanetti: done11:59
mzanettisil2100, I've read a mail somewhere that you're in charge of the phone image seed now12:02
mzanettisil2100, I've a project here for receiving/sending files via bluetooth12:03
mzanettican we add qml-module-qtbluetooth to the seed?12:03
mzanettiI'll do some more evaluation, but at least for allowing an app to search for devices it's working fine already12:04
sil2100mzanetti: hm, ok, makes sense12:05
sil2100Let me add that to my TODO list for today12:06
* sil2100 goes prepare lunch12:06
Mirv_mzanetti: sil2100: yeah I've been waiting on someone to request it but so far no-one really has. but it's a stable upstream module nowadays. my only thought at some point was if we want to restrict Bluetooth usage to some hub or such.12:34
Mirv_mzanetti: sil2100: but all of our current Bluetooth code (obviously) uses bluez directly, I wonder if some would then want to migrate using Qt Bluetooth...12:35
mzanettiMirv_, not sure what you mean with restricting it to the hub12:37
mzanettiMirv_, so my project actually is a content hub plugin to share files via BT12:38
mzanettiMirv_, however, for things like SPP that won't work12:38
mzanettiit's used for multiplayer games etc12:38
mzanettineeds direct access to the stack... we still need an apparmor profile tho to enable it12:38
mzanettifor now I plan to publish my stuff unconfined in OpenStore, and then check out what needs to be done to either move it into the image or the official store12:39
Mirv_mzanetti: I was thinking about something like "share files only via content-hub" or such12:41
Mirv_but then again, many kinds of BT apps are possible so that'd be quite limiting12:41
mzanettiMirv_, yeah well... I guess you can do this:12:42
mzanettieither you request BT apparmor permissions and can connect to other devices,12:42
mzanettior you don't do that and just invoke contenthub with the preexisting BT plugin12:42
Mirv_mzanetti: yep, makes sense. I'm absolutely for adding it, I was just curious why no-one had requested it yet. (also, we had stuff like "we want Qt 5.4 because it supports Bluetooth LE" even though we didn't have Qt Bluetooth in use in the first place :D)12:42
mzanettiMirv_, the BT LE discussion got quiet when it turned out we won't move to bluez512:43
mzanettibut I've been talking to seb128 about that... we agreed that this discussion needs to get rolling again12:43
mzanettiat least the discussion :D not sure who will do it in the end :D12:43
=== _salem is now known as salem_
Mirv_mzanetti: ouch, yes bluez5... long overdue, no-one to work on it12:46
Mirv_mzanetti: let's found a committee on discussing how someone would really need to ship bluez512:48
=== Mirv_ is now known as Mirv
boikosil2100: hi, so, silo 8 is ready for QA to test, but because of the manual upload of telepathy-qt5, its status is shown as Failed to build13:08
pmcgowansil2100, what was the conclusion on the update issue13:16
Mirvboiko: I'll run watch_only build job, maybe that's only thing that's needed13:18
pmcgowanor jibel ^^13:21
Laneypsivaa / cihelp: hi, do you have anywhere I can file bugs on iso smoke testing?13:22
jibelpmcgowan, sil2100 was looking at the delta generation code, davmor2_ filed bug 1474739 but I don't have more info for the moment13:25
ubot5bug 1474739 in Canonical System Image "Move from ota4 image to ota5 image does update the override file for the favourite apps" [Undecided,New] https://launchpad.net/bugs/147473913:25
pmcgowanjibel, I think that should be "does not"13:29
pmcgowandavmor2_, did you check if any other elements get updated from the custom ball, like today scope?13:29
jibelindeed, fixed13:29
fgintherLaney, psivaa stepped out for a bit, hopefully he has the answer when he's back online13:35
Mirvboiko: so the telepathy-qt5 was manually uploaded, not a sync? in that case the silo needs to be reconfigured13:35
Mirvlooks so, uploaded by sil13:36
Mirvfixing13:36
boikoMirv: yep, sorry, OTP, talk to you in a minute13:38
psivaaLaney: fginther: We have no project specifically for iso smoke testing, but ubuntu-ci-services is the general project we used to accept bugs13:42
seb128shrug13:42
psivaathere could be an option to select utah or anything else you're intending for13:43
Mirvboiko: ^ seems ok now13:43
Mirvor ^13:43
boikoMirv: so, to explain the whole situation: a new telepathy-qt5 landed on wily, and we need to sync it back to vivid, but in order to do that we need to get the dependent packages updated too13:47
boikoMirv: telepathy-qt5 is not a package we are upstream for, so it was a source landing (or a direct landing without even going through the citrain)13:48
pmcgowansil2100, jibel so I am a little unclear if we released the ota or are waiting on something wrt the update glitch13:54
sil2100pmcgowan: BQ got the update, we'll release it to users on Monday13:55
sil2100As that was Alex's request13:55
ogra_what about meizu ? did that go out already ?13:55
sil2100Since BQ needs time to test, but they don't want to have a Friday release13:55
sil2100ogra_: no, we'll release both at once13:55
ogra_good13:55
pmcgowansil2100, what about the custom tarball update bug13:56
sil2100pmcgowan: looking into that right now... looks like the files on system-image are fine, something probably goes wrong during update13:56
pmcgowanhmmm13:56
sil2100A Monday release gives us time to find the source of that too13:56
pmcgowansil2100, do we need anyone else for that? barry?13:57
sil2100pmcgowan: I'll probably poke barry for that too13:57
sil2100Doing it now actually13:58
barrysil2100, pmcgowan hi13:58
sil2100davmor2_: you around?14:05
AlbertAfginther:  sorry missed your Q yesterday,  yes mir-clang-ts-wily-amd64-build should be enabled for lp:mir/ubuntu as well, thanks!14:07
Mirvboiko: ok!14:13
boikorvr: so for silo 30, sorry for the unapproved MRs, I reviewed the code and tested from the silo, forgot to approve them, all approved now14:14
rvrboiko: Ack14:15
sil2100rvr: hey! You have an arale, right?14:20
rvrsil2100: Right14:20
sil2100rvr: you busy with silos now?14:21
rvrsil2100: What do you want me to check?14:21
sil2100rvr: https://bugs.launchpad.net/canonical-devices-system-image/+bug/147473914:21
ubot5Ubuntu bug 1474739 in Canonical System Image "Move from ota4 image to ota5 image doesn't update the override file for the favourite apps" [Undecided,New]14:21
sil2100rvr: I just tried reproducing this and couldn't14:21
rvrChecking14:21
sil2100davmor2_: ^14:21
rvrsil2100: I'm installing build 4 to check it14:23
sil2100rvr: you need to upgrade from 2 to 414:24
rvrsil2100: Oops, ok14:25
seb128is publishing photos from gallery to facebook working for anyone?14:27
rvrseb128: I think I saw a bug this morning about that14:32
seb128rvr, yeah, which is why I'm asking if others can confirm it14:33
seb128rvr, before trying to escalate that said bug14:33
sil2100rvr: were you able to find a moment to do this upgrade path?14:45
mandelsil2100, so, I'm utter crap with this errors => https://ci-train.ubuntu.com/job/ubuntu-landing-009-1-build/292/console14:48
mandelsil2100, any idea14:48
mandel??14:48
sil2100Looking14:48
sil2100mandel: yeah... so the silo is a vivid-overlay silo, where you're trying to release from a trunk that was used to release wily packages14:49
mandelsil2100, me swears.. how can I fix that?14:50
mandelsil2100, I guess I need some sudo powers, right?14:50
sil2100mandel: the train does not allow that, as the trunk has wily version numbers in it 1.234+15.10.blabla - while you suddenly want to release something that has 1.234+15.04.blabla14:50
sil2100We don't allow that... you either should have a separate trunk for 15.04 landings, or dual-land everything14:51
sil2100Or use syncs14:51
rvrsil2100: Phone is flashing14:51
mandelsil2100, but the complain is about content-hub, which I dod not control, I just want to make it recompile with the version of udm in that silo14:51
sil2100hmmm14:52
sil2100kenvandine: pong ^14:53
sil2100mandel: btw. why is it an overlay-only silo?14:53
sil2100Why not a dual? Is it already landed in wily?14:53
mandelsil2100, honestly, I have not touch that in aaaaaaages I was distracted by other urgent things and I have been an asshole14:53
mandelkenvandine, sorry!14:53
sil2100mandel: maybe we should turn this to a dual landing silo?14:54
sil2100mandel: then it would just all work fine, we'd release it both for wily and vivid14:54
mandelsil2100, sounds good, is a recompilation that is needed in both AFAIK14:54
sil2100mandel: ok, we'll have to rebuild the silo then... would that be fine?14:56
mandelsil2100, sure, no problem14:56
mandelsil2100, I want to land this :)14:56
sil2100mandel: ok, reconfigured... we need to rebuild it - do we need it to be rebuilt in a specific order?14:59
mandelsil2100, yes, udm first, then the others14:59
mandelsil2100, since they depend on udm14:59
sil2100ok, let's do it like that then14:59
kenvandinemandel, we should make that a dual silo15:00
mandelkenvandine, done already :)15:00
mandelkenvandine, landing this asap, sorry I have been a mess lately15:00
kenvandineawesome15:00
sil2100Building the u-d-m there15:00
mandelkenvandine, getting back on track15:00
rvrseb128: On krillin, "Your photo was uploaded successfully"15:00
seb128rvr, do you see it on facebook?15:01
seb128e.g is that true? ;-)15:01
seb128rvr, what image version as well?15:02
rvrsil2100: Which apps are the ones favourited?15:04
sil2100rvr: do you see 8 favourited apps?15:04
sil2100rvr: check the file /custom/etc/dconf_source/db/custom.d/custom.key if it has an override list of apps15:05
rvrseb128: ubuntu-touch/rc-proposed/bq-aquaris.en #6715:05
sil2100rvr: (you can simply pastebinit for us after the upgrade)15:06
rvrsil2100: I dont understand what "favourited" mean. Where? In the launcher?15:06
sil2100rvr: it's the 2 first rows of apps in the apps scope15:06
seb128rvr, k, weird15:06
rvrsil2100: Phone, Messaging, Contacts, Camera, Browser, Click15:07
sil2100rvr: on krillin there are 6 apps, 2 rows of 3 apps - on arale we increased that to 4 apps per row15:07
sil2100rvr: so after upgrade you have 6?15:07
sil2100Not good...15:07
rvrsil2100: No, this is image 415:08
rvrerr 215:08
sil2100Ah, ok, good15:08
sil2100Now, OTA to image number 4 :)15:08
sil2100The expectation would be that there's 8 apps, so additionally Music and Gallery15:08
rvrsil2100: Restarting15:09
sil2100But Dave said that after update there's still 6 there, meaning the override from the custom update didn't work15:09
sil2100Or didn't get copied15:09
rvrsil2100: I see. I didn't understand what favorite meant.15:09
jibelyeah, they are not favorites since you cannot change them and it is not necessarily your favorite apps15:11
ogra_i thought they are supposed to become favorites and editable one day15:12
rvrsil2100: davmor2_: Only 6 after upgrade. Gallery and Music not in "favorite"15:12
jibelsil2100, is there any other bits of the custom tarball that we could check if they have been updated or not?15:13
pmcgowanjibel, yes the scopes, today scope15:13
jibelsil2100, could we diff the unpacked custom tarball with the content of the upgraded device?15:14
sil2100jibel: I checked the generated delta of the custom tarball and it had the override file in place15:16
jibelargh, I cannot flash my arale :(15:16
sil2100So it's not a bug on s-i15:16
sil2100The delta from 2 -> 3 has the override, and system-image-cli tool said that the upgrade path was 3 and then 4, so correct15:17
sil2100rvr: :<15:17
sil2100rvr: I couldn't reproduce the bug...15:17
sil2100But I didn't flash image no. 2 with wipe15:17
sil2100ALthough I confirmed that after flashing to #2 the custom.key file had no override and after upgrading to #4 the override was in place15:18
kenvandinealesage, i just replied about silo 39, what you're seeing is a separate ofono bug 145557415:19
ubot5bug 1455574 in ofono (Ubuntu) "Failures to disable call waiting" [Undecided,Confirmed] https://launchpad.net/bugs/145557415:19
alesagekenvandine, super thanks15:20
kenvandinethank you!15:20
rvrsil2100: Let me check that file in #215:21
sil2100This makes me worry15:25
jibelsil2100, I'm flashing 215:25
sil2100kenvandine: whoops! Wanted to re-publish your package ;)15:26
sil2100Forgot it was your silo15:26
sil2100jibel, rvr: it seems the problem might be somewhere in the recovery upgrader, since as barry mentioned s-i client only downloads all the files and reboots15:27
sil2100jibel: but yeah, would be good if you guys see if other things from the custom got upgraded or not15:27
jibelsil2100, I'll upgrade and diff the device with the tarball15:27
barrysil2100: i think the upgrader leaves a log file15:28
sil2100barry: do you know where?15:28
jibelbarry, where is the log file?15:28
jibelsomewhere in recovery?15:28
barryjibel, sil2100 /android/cache/recovery15:29
sil2100Ooooh15:29
* sil2100 looks15:30
sil2100barry: thanks!15:30
barryi see 3 files there, but i'm not entirely sure what the differences are15:30
sil2100jibel, rvr: after upgrading, could you pastebin your logs from there? I would compare those with what I got15:30
sil2100Applying update: custom-3a6411261d5e2fc1a158bf7f1937fb2f54aa639effc765306fbd06a5b0ab84ca.delta-custom-aa22aaea5347f22e04123aa6689ef07ba6c774c68c1b1dc3e58f3de40c7c6e2d.tar.xz <- so at least I know it's applying the custom update here15:31
rvrsil2100: Before upgrade, image #2 http://paste.ubuntu.com/11883173/15:32
kenvandinesil2100, sorry :)15:33
kenvandinei try to be self service :)15:33
sil2100kenvandine: apologies from my side ;p15:34
sil2100I never publish your silos since I know you do that yourself15:34
sil2100I simply, hm, didn't check ;p15:35
sil2100rvr: could you also pastebin the /android/cache/recovery/log file after upgrading to #4?15:38
jibelsil2100, I confirm I've 6 apps, checking the logs15:38
sil2100jibel: could you pastebin?15:38
jibelsure, when it lets me in15:38
sil2100LET HIM IN!15:39
* sil2100 shouts on jibel's arale15:39
jibelpermission denied :(15:39
sil2100sudo!15:39
rvrsil2100: Yes, upgrading15:39
jibelsil2100, I mean when I try to log into the phone15:40
sil2100uh15:40
jibelsil2100, barry http://paste.ubuntu.com/11883237/15:42
sil2100jibel: ok, so it's applying it... and still 6 icons only?15:43
sil2100jibel: can you confirm that /custom/etc/dconf_source/db/custom.d/custom.key doesn't have the override?15:43
jibelsil2100, yes15:43
jibelchecking15:43
rvrsil2100: http://paste.ubuntu.com/11883245/15:44
sil2100Since on Dave's machine it wasn't set, but it doesn't make sense...15:44
rvrsil2100: After upgrade http://paste.ubuntu.com/11883247/15:44
sil2100rvr: oh! So the override is there!15:45
sil2100rvr: and still only 6 apps?15:45
rvrsil2100: Right, still only 6 apps15:45
sil2100Maybe the dconf database needs to be rebuilt15:45
sil2100mzanetti: ping15:45
mzanettisil2100, hey ho15:45
jibelsil2100, http://paste.ubuntu.com/11883261/ thre are 8 apps in the list15:45
sil2100mzanetti: hey! Do you know how the /custom/etc/dconf_source/db/custom.d/custom.key file is used? When is it recompiled to the dconf database?15:46
mzanettiI don't :/15:46
* mzanetti does some reading15:47
mzanettisil2100, looks like when "glib-compile-schemas" is called15:47
sil2100hmmm, so probably it's not called during update15:48
sil2100cwayne_: ping15:48
cwayne_sil2100, yo15:48
sil2100cwayne_: hey! We're investigating a bug in custom-tarball custom.key overrides15:49
kenvandinesil2100, since citrain can't dual land regular dput packages, once it's built for wily i can create a 2nd vivid + overlay landing with sync:22 right?15:49
kenvandineto sync from silo 22?15:49
sil2100cwayne_: so there's that file in the custom tarball /custom/etc/dconf_source/db/custom.d/custom.key15:49
sil2100cwayne_: an override for the 8 apps instead of 6 was written there... but it seems the dconf database wasn't rebuilt during the upgrade15:50
sil2100cwayne_: do you know anything about this there? Is there a plan that the db should be recompiled during upgrade?15:50
cwayne_sil2100, it should be updated based on the build_id15:51
cwayne_there's an upstart job that checks if the build_id is old, and if so, run dconf update15:51
sil2100cwayne_: hmmm15:52
sil2100cwayne_: where is that upstart job? Can we find some logs for that?15:52
cwayne_sil2100, i think it's /etc/init/custom-dconf.conf15:53
cwayne_it's in package ubuntu-touch-customization-hooks15:53
mandelsil2100, I though the changelog should not be touched => https://ci-train.ubuntu.com/job/ubuntu-landing-009-1-build/294/console15:54
sil2100hmmmm15:55
sil2100cwayne_: something is not right, checking /var/log/upstart/custom-dconf-update.log and I see: skipping dconf update15:55
sil2100Even though the custom got updated15:55
sil2100jibel: could you check /var/log/upstart/custom-dconf-update.log if you also have skipping dconf update15:55
mandelsil2100, any idea? for me all this ci is close to magic :-15:56
mandel:-/15:56
sil2100mandel: could you poke kenvandine? Since he's working on u-s-s so he should know more about what that version means15:56
sil2100And where it's coming from15:56
mandelkenvandine, any idea => https://ci-train.ubuntu.com/job/ubuntu-landing-009-1-build/294/console15:57
mandel??15:57
sil2100kenvandine: let me get to you in a moment ;)15:57
jibelsil2100, the only difference between the tarball and the upgraded device is the dconf db http://paste.ubuntu.com/11883304/15:57
sil2100cwayne_: hm, maybe it's caused by the invalid custom tarball build ID?15:57
cwayne_sil2100, what's /custom/build_id15:57
kenvandinecould it be because we have a version in proposed that isn't merged into trunk yet?15:57
sil2100jibel, cwayne_, ogra_, pmcgowan: I'm worried that the problem is the reported by ogra_ custom tarbal build ID change...15:57
kenvandinestill waiting to be promoted to release15:58
sil2100cwayne_: 143646372215:58
sil2100cwayne_: shouldn't it be the ID that we see in system-image instead?15:58
jibelsil2100, cwayne_ apparently dconf update failed http://paste.ubuntu.com/11883310/15:58
sil2100jibel: uh?15:58
cwayne_sil2100, no that's a proper build_id15:59
mandelkenvandine, oh, that could be it, can you ping me when it is there so that I can retry?15:59
mandelkenvandine, I'll take the dog for a walk to waste some time :)16:00
kenvandinemandel, will do!16:00
sil2100jibel: that's strange, it implies the custom db wasn't generated yet16:00
mandelkenvandine, perfect, thx!16:00
kenvandineprobably an hour or so16:00
sil2100cwayne_: could you check the pastebin jibel posted? It looks strange that this directory doesn't exist16:00
jibelsil2100, it's skipped because build time < timestamp of /custom/etc/dconf/db/custom16:01
pmcgowanaha16:01
sil2100jibel: well, stat can't find stat: cannot stat '/custom/etc/dconf/db/custom': No such file or directory16:01
sil2100And this file should be there16:02
sil2100As that's the compiled dconf database16:02
jibelright in that case dconf_mtime is 016:02
cwayne_that doesn't make sense.. since the scope favorites are properly set, which is also in that dconf db16:03
sil2100jibel: could you check if you have /custom/etc/dconf/db/custom on your device now?16:04
sil2100I'm sure you do tho...16:04
jibelsil2100, it's there16:05
jibelsil2100, why is the upstart job executed twice?16:05
jibelsil2100, you cannot have both updating and skipping16:05
jibelsil2100, I removed the file and ran the job and the apps are there16:06
jibelsil2100, is it running too early16:06
jibel?16:06
sil2100hm, maybe, but I thought it was actually ran after the upgrade finished, on first boot after upgrade16:07
sil2100cwayne_: ^ ?16:07
sil2100cwayne_: (sorry for taking your time, but you're the most experienced custom tarball guy around ;) )16:07
cwayne_sil2100, no worries :)  it should run on boot after the upgrade, let me try and poke around and figure out why its not16:09
cwayne_what's even weirder is that my arale seems to have worked perfectly btw...16:09
jibelcwayne_, yeah if you upgraded in rc-proposed it works fine but not on rc16:10
sil2100Mine seemed to work fine on rc-proposed16:10
cwayne_hm16:10
sil2100Maybe some race condition when trying to rebuild the dconf database?16:10
sil2100Doesnt' look like it16:11
cwayne_it almost seems to me like the build_id wasn't copied right or something16:12
sil2100cwayne_: to the custom tarball, or during upgrade?16:13
sil2100jibel: actually, maybe the first line is from your fresh flash to #2, and the second one (the skipped part) is for the upgrade to #416:17
jibelsil2100, yes, that's what I'm checking16:17
sil2100jibel: then it would indeed make sense that the file was not there... and maybe cwayne is right saying that there's something wrong with the build_id16:17
sil2100And it skipped the upgrade16:17
jibelexactly, that's my guess16:17
jibelI'll confirm in a minute if the tarball ever transfers16:18
kgunntrainguards not sure what's happening, but seeing an issue with citrain tool on mx4 wily16:20
kgunnhttps://pastebin.canonical.com/135360/16:20
kgunnit adds the ppa, does the apt update, but seems to fail the install part16:20
sil2100kgunn: hm, a downgrade? Maybe it's indeed missing the right --force-yes flags now, not sure if it's written to handle this case wll16:21
sil2100*well16:21
sil2100robru: &16:21
sil2100robru: ^16:21
sil2100(ugh)16:22
* kgunn asks mir guys why u-s-c is a downgrade in //16:22
cwayne_sorry, think i got booted from irc for awhile16:29
sil2100uh16:30
sil2100:)16:30
sil2100cwayne_: http://paste.ubuntu.com/11883467/ <- in case you missed those16:30
fgintherAlbertA, thanks for getting back to me, the jobs have been updated.16:32
jibelsil2100, so when I flash 2 dconf db is created, I saved the build_id and will upgrade16:32
sil2100jibel: ok! Thanks, let's see what'll happen with the build_id...16:33
cwayne_sil2100, ah yes, I did miss all that :)16:33
cwayne_stupid xchat16:33
kenvandinesil2100, don't forget my question :)16:33
sil2100kenvandine: ok, reading up now! :)16:34
kenvandinemandel, merged, rebuild away!16:34
rvrjamesh: Hi16:34
sil2100kenvandine: ok, the answer is yes :) That's the only way to go with dputs16:35
rvrjamesh: I'm failing silo 10. With 250 png's, I see no thumbnails in gallery-app.16:35
sil2100kenvandine: wait, actually...16:35
kenvandinecool, just making sure i didn't have to wait for it to land in wily16:35
sil2100kenvandine: depends on what kind of package we're talking about, since synces work only for CI Train versioned packages16:35
kenvandinesync of libqofono16:36
sil2100kenvandine: for others you'd have to do a manual upload yourself, as we can't guess the version format16:36
kenvandinein silo 22 for wily16:36
kenvandineok16:36
kenvandineso i should upload like 0ubuntu0.1 ?16:36
kenvandineso it's less than wily?16:36
sil2100kenvandine: yeah, you'll have to figure out some versioning... I usually append something 'overlayish' there, since I'm worried that I'll get in conflict with SRUs16:37
sil2100But 0ubuntu0.1 sounds fineish16:37
kenvandinelike?16:37
kenvandineok16:37
jibelsil2100, does it fail because #2 has been flashed after the timestamp in build_id?16:42
jibelsil2100, so the dconf db is newer than build_id?16:42
jibeland not updated16:43
sil2100jibel: hah, it makes sense... this would be a big bug in the custom dconf updater then16:44
jibelsil2100, it probably never worked16:44
sil2100jibel: I suppose that explains why it worked for us on rc-proposed16:44
sil2100Yeah16:44
sil2100It works if you don't go back in history16:44
sil2100cwayne_: ^16:44
sil2100jibel: good catch16:44
jibelsil2100, it won't work for someone who buy a retail phone with factory image lets say OTA1 and upgrade16:45
jibelsil2100, however next ota would fix it because the build_id would become newer than the dconf db16:47
sil2100The sad thing is... it's a bug on the rootfs, as the upstart job is not part of the custom tarball16:48
jibelsil2100, , instead of doing a stat on the dconf db maybe a flag with a copy of the build id corresponding to when the db has been updated would fix the problem.16:48
sil2100So if we want to fix this, we need to make a snapshot of the old OTA-5 image candidate16:49
jibelnice16:49
sil2100pmcgowan: ^16:50
jibelpmcgowan,16:50
jibel:)16:50
sil2100It's an old problem, but this time it might cause trouble16:50
robrukgunn: what version of the citrain tool are you using? vivid version, wily version?16:50
sil2100robru: kgunn said it was the wily version16:51
robrusil2100: kgunn: looks like he said his phone was wily, I mean is he running wily or vivid on his host machine16:52
pmcgowansil2100, jibel so whats the fix exactly change the logic on when to update?16:54
jibelpmcgowan, yes it's comparing the build_id to the last access time of the dconf db, so if the db is created after build_id it will not be updated on next upgrade16:58
pmcgowanjibel, so why is the current db later than the build_id17:02
sil2100pmcgowan: since the db is generated after flashing17:03
pmcgowanah so never worked17:03
sil2100So it has the image flash date timestamp...17:03
sil2100It works in the theoretical case where someone had OTA-4 from the beginning and now upgrades to OTA-517:03
sil2100Since then the db is generated in the OTA time, so earlier than the new custom tarball17:04
pmcgowansil2100, so if I updated to ota4, I update to ota5 ok17:04
pmcgowanbut if I flash ota4, I cannot update to oat5 ok17:05
pmcgowan?17:05
sil2100pmcgowan: it depends when you got ota417:05
pmcgowanstill confused then17:05
pmcgowanoh I see17:05
pmcgowanif I get ota4 after ota5 build17:05
pmcgowanthats busted17:05
sil2100pmcgowan: if you got ota4 at least 2 weeks ago, it's fine... but if you upgraded/flashed to ota4 in the last 1-2 weeks, you're broken17:05
jibelexactly17:05
pmcgowanwhy check at all17:05
sil2100Yes17:05
pmcgowanshould it just update always?17:06
sil2100pmcgowan: well, it's an upstart job that's running on every boot17:06
sil2100pmcgowan: so it can't update the db on every boot as it's not required... in the best case it should only update when there's smoething to update17:06
jibelpmcgowan, a solution would be to save the buildid against which the db was rebuilt17:06
pmcgowanok17:07
jibelinstead of comparing it to the timestamp of a file dynamically created17:07
pmcgowanright17:07
pmcgowanand thats in the upstart stuff in rootfs17:07
sil2100We need ubuntu-touch-customization-hooks upgraded in this case...17:07
pmcgowansil2100, so we need to snapshot and poke17:08
sil2100Yeah, I'll prepare the snapshot17:08
sil2100The problem was... davmor2_ had a different case in his logs17:08
sil2100And this wasted some of my time, as he didn't have the override in place17:08
sil2100For unknown reasons17:08
jibelsil2100, I verified if I force the execution of the job the missing favorite apps appear17:09
sil2100Since this was his custom.key after 2 -> 4 upgrade:17:09
sil2100http://paste.ubuntu.com/11878074/17:09
sil2100jibel: you mean, force the dconf update in custom-dconf-update.conf and then upgrade?17:10
jibelsil2100, true, I've the same problem now17:10
jibelsil2100, during previous test the dconf keys were ok17:11
jibeland now it's like davmor2_17:11
jibel????17:11
sil2100huh?17:11
sil2100WTH17:11
sil2100jibel: could you pastebin the logs? Both the system-image ones and the one from recovery17:11
jibelsil2100, http://paste.ubuntu.com/11883663/ the keys17:12
jibelsil2100, that's ok, it's the wrong file in the pastebin17:14
sil2100Aah!17:14
sil2100dconf instead of dconf_source17:14
sil2100Yeah, ok, missed that when I checked logs from davmor2_17:14
sil2100Ok, so it was a red herring17:15
jibelphew, don't do that again, it's sunny nearly 7:30 and I'd like to go swimming :)17:15
sil2100Go go ;)17:16
sil2100I need to finish up some other things and then prepare the snapshot PPA17:16
jibelbbl17:18
kenvandinemandel, i went ahead and kicked a rebuild of silo 917:19
sil2100pmcgowan: preparing the snapshot17:24
pmcgowansil2100, cwayne who can we assign that bug to17:27
sil2100Not sure who is the current maintainer of ubuntu-touch-customization-hooks - is that penk?17:28
sil2100Looks like another longer work day for me ;)17:33
mandelkenvandine, great17:44
sil2100kenvandine, robru, Mirv: could you not publish anything for a moment?18:05
sil2100I don't want to confuse LP during the copy18:05
kenvandinesure18:05
sil2100Thanks18:05
cwaynesil2100: i guess its penk now, yeah18:05
robrusil2100: alright18:09
sil2100pmcgowan: copying to the snapshot now...18:11
pmcgowansil2100, didnt seb128 log a bug about the Display results string not being translated? I cannot find it now18:23
kgunnrobru: sil2100 actually, my mistake at least on ppa with phone...i flashed rc-proposed, meant to flash devel18:30
kgunnso i think nvmd18:30
robrukgunn: if you have problems, best to try the version of citrain tool in lp:phablet-tools, it has some fixes that aren't released in vivid.18:31
kgunnack18:31
kgunni think it was me for the moment18:31
=== davmor2_ is now known as davmor2
davmor2sil2100: just got back from the hospital did you sort it all out in the end?18:42
pmcgowandavmor2, the update thing? yes just working out the best fix18:51
robrusil2100: just noticed silo 45 waiting to publish, let me know when it's safe18:52
davmor2pmcgowan: yeah just caught up on the bug email from it just a database timestamp that is mad18:52
sil2100robru: one more minute :)19:01
robruboiko: remember you can assign your own silos now ;-)19:02
boikorobru: oh, I totally forgot, I thought it was only for reconfiguring, cool! :)19:02
robruboiko: yeah there's a buffer at 5 silos, if there's only 5 free silos then you need a trainguard to greenlight it but generally it's open season on silos.19:03
boikorobru: nice!19:04
robruboiko: there'll be a more formal announcement about this when the spreadsheet replacement goes live, Real Soon Now19:04
boikorobru: and I still didn't get the time to test it, shame on me :-S19:04
robruboiko: no worries, I got some great feedback already and I think we're coming in for a strong finish here.19:05
boikogreat!19:06
sil2100robru, kenvandine, Mirv: ok, things seem to look fine19:06
sil2100robru, kenvandine, Mirv: you can land now19:07
kenvandinecool, thx19:07
robrusil2100: thanks19:08
robrubah19:09
pmcgowanjibel, , didnt someone log a bug about the "Display results for X" string not being translated for scopes? I cannot find it now19:20
jibelpmcgowan, I remember seb128 mentioned it.19:22
jibelI am not sure there is a bug, let me check19:22
pmcgowanjibel, kyle entered one but i thought it was already in19:23
jibelI cannot find anything from seb19:26
jibelpmcgowan, nope, all I found are the bugs the testers reported yesterday and that kyle marked as duplicates.19:31
pmcgowanjibel, ok thanks, will use that one then19:31
seb128jibel, pmcgowan, the one I mentioned was https://translations.launchpad.net/unity-scopes-shell/trunk/+pots/unity-plugin-scopes/es/1/+translate19:36
seb128that was not advertized to translators, nobody knows it's to translate I think19:37
pmcgowanseb128, what do we do to trigger that?19:37
seb128pmcgowan, "that"?19:37
seb128let people know it's to translate19:38
seb128usually email ubuntu-translators@ with a pointer to the new string19:38
seb128also check with dpm that that template priority is high enough that it's listed as an important templates for translators19:38
pmcgowanseb128, how do I check that priority19:40
seb128pmcgowan, it's in https://translations.launchpad.net/unity-scopes-shell/trunk/+pots/unity-plugin-scopes/+edit19:40
seb128that one apparently has 019:41
pmcgowanheh so no wonder19:41
pmcgowanlets bump it19:41
seb128pmcgowan, also not that dialer-app's template was not update so the new "flight mode" dialog added for ota5 is not translated/translatable...19:42
seb128yet another translation fail :-/19:42
pmcgowanit is also prioirty 019:42
pmcgowansince I just checked it19:42
seb128yeah, I'm unsure if that's where dpm change those19:42
pmcgowanok will wait for him to weigh in19:43
seb128pmcgowan, there is https://wiki.ubuntu.com/Translations/Phone which lists other scope sources but not the shell one19:44
seb128pmcgowan, jibel, I think the string in the video/music is another issue, that's coming from the media scope19:53
seb128bug #1472236 which has a merge request to update the template for a week19:53
ubot5bug 1472236 in Unity Media Scanner Scope ""Nothing here yet" is not translated" [High,Confirmed] https://launchpad.net/bugs/147223619:53
seb128pmcgowan, jibel ^19:54
kyrofacihelp: I have a package that's running in jenkins and autolanding. I need the configuration changed so that I can land it in the archives. What do I do?19:54
fgintherkyrofa, is this to move a package into the ci-train world?19:55
fgintherkyrofa, and what package is it?19:55
kyrofafginther, I'm a bit new to it, but yes I believe so (that's only way to get it into the archives, no?)19:56
kyrofafginther, unity-scope-snappy19:56
kyrofafginther, ci-train is the silos and whatnot?19:56
fgintherkyrofa, yes. ci-train == silos and path to the archive19:57
fgintherkyrofa, on our end, we need to make a config change to stop autolanding of MPs into trunk, the rest is up to you to work with the train folks19:58
kyrofafginther, very good. Would you like that request via email, or is it an easy change to make?19:59
fgintherkyrofa, I have all I need from this conversation, should have it ready by EOD20:00
kyrofafginther, awesome, thanks!20:00
slangaseksil2100: hey, so regarding the gcc5 silo; I understood from our discussion that you told me I could fill out the spreadsheet with just some representative packages listed in 'additional source packages to land', but not have to list all of them, is that right?20:27
slangaseksil2100: robru is telling me that large parts of the train are going to be uncooperative with this20:27
sil2100slangasek: all the list is needed to publish it, but to assign the silo only a few were necessary20:28
sil2100It was for silo assignment20:28
slangaseksil2100: ah, I see.  So is there any reason that we as core-devs couldn't/shouldn't bypass the publish job and just use copy-package directly?  which is going to be simpler than adding 1000 package names to the spreadsheet box20:29
sil2100slangasek: no reason, I guess that's much saner that way20:29
slangasekok20:29
sil2100e.g. copy-package20:29
robruslangasek: well if you bypass the publish job, other silos won't be marked dirty20:34
robrusil2100: slangasek anyway i approve of the idea of making the train infer packages based on ppa contents, but that'll take some work and other things are priorities now20:36
slangasekrobru: isn't the train supposed to figure out on its own when someone has done a direct upload to the archive?20:54
slangaseksorry that's a rhetorical question.  it is supposed to figure out on its own ;)20:55
slangasekbut does that not have the effect of marking silos as dirty?20:55
robruslangasek: i don't know what train you've been using all this time. Our train is a dog that requires constant manual prodding and babysitting. Nothing is ever automatic21:02
robruslangasek: oh you said archive21:02
robruslangasek: yeah at publish time it'll complain21:02
slangaseks/complain/fail/, I hope21:03
robruslangasek: the point of marking dirty is that silo owners get warned before publishing21:03
slangasekyes21:03
robruslangasek: yeah fail21:03
robruslangasek: are you planning on merging everything back to trunks manually, too?21:04
slangasekrobru: um, no, that's the thing that the train is supposed to have been taking care of automatically for us21:04
slangasekrobru: direct uploads to the archive by core-devs are supposed to be automatically picked up by the train21:05
robruslangasek: on what planet?21:05
robruSurely not this one21:05
slangaseknow, maybe "by the train" is actually "by the next lander who tries to publish the package and gets told to go merge the thing"21:05
robruslangasek: yeah, that. The train offers no help there, landers get to keep the pieces21:06
slangasekok21:06
robruslangasek: please file some bugs. I'd love to streamline these pain points after I'm done with bileto21:07
slangasekrobru: well, most of this is half-formed impressions I have of how things were supposed to work, not actionable bugs21:07
slangasekbut I'll try to correct that21:08
robruslangasek: well "train should resync trunk for you" is an actionable feature request i agree with21:08
robruslangasek: also "train should infer ppa contents" is another good one21:08
robruslangasek: i mean, that would be an amazing world to live in. I'm shocked you thought those things existed already21:09
slangasekhaha21:09
=== salem_ is now known as _salem

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