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

=== chihchun_afk is now known as chihchun
=== chihchun is now known as chihchun_afk
Mirvanpok: did you get what you needed to the 053?05:23
Mirvanpok: answer seems to be no, so copying. also, reconfiguring the silo the claim all of them are manual uploads, since it used to be dual landing for all and you want to continue doing dual landings (you can't now use the same MP:s for the vivid landing)05:23
=== ev_ is now known as ev
Mirvanpok: or hmm, maybe that current line in there is good enough, but it was not reconfigured after the line was changed05:24
=== salem_ is now known as _salem
Mirvmichi: hey! you could test on wily too, silo 021 has the same accessibility fix for wily. I think it'd be nice to see how it behaves in the exact thumbnailer scenario.05:50
michiMirv: OK, I’ll have a look.05:50
michiUnfortunately, I don’t know how to install the new thumbnailer from a Jenkins build.05:50
michiJenkins devel-ci still builds with the old version number.05:51
michiI’ll talk to James about it later today.05:51
Mirvmichi: so the build from the silo 10 workarounds the issue ie is not good for testing it? can you give me the jenkins url? I believe if you can download the .deb:s from there and push them to device, you can dpkg -i *.deb them05:53
Mirvmichi: I'm not otherwise in a hurry, but I'll be away for two weeks after today so if you want it in, I'd rather do it sooner than later today ;)05:54
MirvI've already autopilot tested the vivid silo to have no regressions otherwise05:54
michiMirv: No, I added our own work-around for the time being.05:54
michiTo test whether it’ll work with the new network access manager, I need to build a new thumbnailer with the work-around removed and some extra trace.05:54
=== chihchun_afk is now known as chihchun
Mirvmichi: ok05:55
michiBut I can’t get the package that Jenkins builds for Arm onto the device right now because of the version going backwards.05:55
Mirvmichi: dpkg -i forces even a downgrade05:55
michiCool, I’ll try that, thanks!05:56
Mirvjust adb push each .deb to the /home/phablet , then adb shell and dpkg -i *.deb05:56
Mirvyou're welcome05:58
anpokMirv: yeah I wasnt sure yesterday then ended my day..06:30
anpokMirv: because of gtk+3.006:30
anpokwe are on 3.14 on vivd, and 3.16 on wily, I wasnt sure how to configure sync for all the others, but manual upload for gtk+3.1406:31
=== chihchun is now known as chihchun_afk
Mirvanpok: I'm actually not 100% sure either how it should be done :) but it's now all "manual" uploads, and the watch_only build is running so hopefully it should soon be ready to test06:44
tsdgeosMirv: nice :)07:08
Mirvtsdgeos: you're welcome :)07:33
Mirvanpok: ah, 053 would need qtmir-gles and qtubuntu-gles still..07:34
Mirvanpok: I can handle those too07:34
Mirvanpok: or, hmm, they are outdated in 053, should they be the same version as wily has in 004? they don't seem to have vivid specific branches?07:35
Mirvanpok: correction, qtubuntu is up-to-date, qtmir in 004 only has your comment change so it does not matter07:36
Mirvanpok: -gles packages building for vivid now, watch https://ci-train.ubuntu.com/job/ubuntu-landing-053-1-build/11/console07:38
seb128hum07:39
seb128did people notice that the mir update is blocked in wily-proposed due to boottest regressions?07:41
seb128https://jenkins.qa.ubuntu.com/job/wily-boottest-mir/lastBuild/console07:41
seb128the logs don't have much details07:41
MirvI'm not sure if the boottest is deemed to be trustworthy nowadays or not, but I can rerun it now to see if it persists07:44
seb128yeah07:45
seb128the thing is that it failed for all the packages in the set07:46
seb128e.g07:46
seb128https://jenkins.qa.ubuntu.com/job/wily-boottest-qtmir/lastBuild/console07:46
seb128that one has a "ERROR: timed out waiting for Unity greeter"07:46
Mirvanpok: ^ you should probably be interested in that wily mir problem, whether there's a real problem07:47
Mirvanpok: you could probably update to wily-proposed on device to see07:47
jibelseb128, actually there are lot of boottest failures http://paste.ubuntu.com/11891679/ is anyone looking at the results?07:51
jibelfor exmaple lxc-android-config should be whitelisted, it cannot be installed directly07:52
=== marcusto_ is now known as marcustomlinson
jibelseb128, and when tests fail the log are not useful to do any diagnostics, eg. ubunut-system-settings-online-account ... Killed without further info07:53
jibellike mir07:54
seb128jibel, yeah, that's what I said "it failed for all the packages in the set"07:57
seb128that "lot" is just the new mir landing07:58
anpokMirv: will have a look08:02
jibelMirv, I re-ran all non-mir or qt boottest failures ie. pay-service platform-api thumbnailer trust-store ubuntu-app-launch ubuntu-system-settings-online-accounts08:24
jibelMirv, lxc-android-config must be whitelisted, it  must be installed from recovery08:24
jibelMirv, and the thumbnailer seems to be a real dependency issue in Wily08:25
jibeljamesh, ^08:25
jameshjibel: what do you mean by "a real dependency"?08:28
Mirvjibel: ok08:28
anpokso the boot test fails because it attempts to upgrade lxc?08:28
jameshreal dependency issue.  Sorry08:28
jameshif this is libleveldb1, won't that be fixed when the next image gets rolled?08:29
anpokjibel: btw pay-service ubuntu-app-launch ubuntu-system-settings-online-accounts are all part of the mir update.08:29
jibeljamesh, in the log of https://jenkins.qa.ubuntu.com/job/wily-boottest-thumbnailer/lastBuild/ there is this error at the end08:29
jibelThe following packages have unmet dependencies:08:29
jibel thumbnailer-service : Conflicts: libthumbnailer0 but 1.3+15.04.20150312-0ubuntu1 is to be installed08:29
jibelanpok, ok08:29
jameshjibel: we shouldn't have any libthumbnailer0 now.  That package was removed08:30
anpokMirv: just read the logs above.. thanks for cleaning up my mess.08:31
Mirvanpok: yes, the 053 seems to be intact for testing now. you're welcome.08:31
jameshjibel: I believe the conflicts/replaces headers are correct (I applied the fixes infinity gave me)08:31
Mirvoh, I noticed only now that sil2100 had cancelled the hangou08:31
Mirvt08:31
anpokis there a way to manually upgrade without touching lxc-android-config?08:31
sil2100Mirv: yeah, not much to discuss08:32
Mirvanpok: what I do usually is just to dist-upgrade, then when it fails run sudo dpkg --configure -a08:32
ogra_hmpf08:36
ogra_none of the buttons in my indicators work on arale ...08:37
ogra_(i.e. tapping on battery settings in the indicator doesnt open anything)08:37
ogra_is anyone else seeing that ?08:37
* ogra_ is on r52 on rc-proposed08:38
ogra_err08:38
ogra_r6208:38
ogra_updated 1h ago08:38
jibelogra_, it works on r6208:38
ogra_hmpf08:38
ogra_i wonder whats wrong with my device then08:39
jibelthey all work08:39
anpokMirv: so it boots here after dist-upgrading.. so this was really just thumbnailer and lxc?08:40
* ogra_ reboots, my spread also only shows shadows instead of app screenshots again 08:41
jameshjibel: I'm still not sure what that build log is trying to do.08:45
Mirvanpok: well if you're dist-upgrading after flashing today morning's image, there's only so much new there is08:45
jibelMirv, can you help on the thumbnailer boottest failure, I am not sure either how boottest installs packages.08:46
jibelcihelp ^08:49
psivaajibel: let me take a look08:49
ogra_sil2100, seems i386 failed to build for the last vivid image build08:58
* sil2100 checks the logs09:07
sil2100hm, dep issues, unity8 couldn't be installed09:09
Mirvjibel: I don't find anything that would depend on the libthumbnailer0 with the new packages09:19
Mirvbut maybe psivaa can find something more out09:23
psivaastill digging, all devices being occupied does not help speed up :)09:23
jibelogra_, how do you reproduce the "shadow effect"? I never saw it09:30
ogra_jibel, i simply use the device09:30
ogra_it starts happening after a few hours ... and gets worse over time09:31
jibelogra_, me too :) any specific use of the device?09:31
jibelhm09:31
ogra_jibel, no, i have my usual 5 apps open, nothing fancy09:32
ogra_seems it is worse if the browser is open alongside09:32
=== chihchun_afk is now known as chihchun
=== chihchun is now known as chihchun_afk
sil2100Oh09:44
psivaajibel: Mirv: i don't think we could make libthumbnailer0 work with boottest as it's currently setup,10:01
psivaathis is due to the fact that its  ubuntu-touch/devel-proposed/krillin.en vivid being the base image where the boottests are run10:02
psivaaand the fact that we're trying to install wily version of thumbnailer-service as part of the testrun, which conflicts with libthumbnailer010:03
psivaahttp://paste.ubuntu.com/11892053/10:03
psivaaSo, thumbnailer(wily) -> installs thumbnailer-service(wily) on vivid base which already has thumbnailer0, which is conflicting10:04
psivaas/thubnailer0/libthumbnailer010:05
jameshpsivaa: thumbnailer-service should be replacing everything we had in libthumbnailer0, and there are no further dependencies10:07
jameshfurther dependencies on that package10:07
sil2100Mirv: interesting... I'm looking into the reason why our last i386 image didn't build correctly10:11
jameshpsivaa: if the test is actively trying to install libthumbnailer0, then that sounds like a problem with the test.10:11
sil2100Mirv: and this might also be related to the thumbnailer landing, but hm, the error is a bit strange10:13
sil2100Mirv: the shlibs:Depends on thumbnailer generated something really strange10:14
sil2100Mirv: qtdeclarative5-ubuntu-thumbnailer0.1 has such a dep currently: libqt5quick5 (>= 5.4.1-1ubuntu7) | libqt5quick5-gles (>= 5.4.1-1ubuntu7) <- first, not sure why shlibs is suddenly depping on the exact version number, and why did it mark requiring 5.4.1-1ubuntu7 for -gles if gles is currently one rev behind (5.4.1-1ubuntu6)10:15
sil21005.4.1-1ubuntu7 does not and never existed for the -gles version10:18
Mirvsil2100: eh..10:25
Mirvsil2100: is the i386 image an emulator image? that could mean that we should not allow the versions to go out of sync, since the .symbols file might declare the dependency like that10:26
sil2100Ah... right, yeah10:26
Mirvsil2100: oh, oh... this is the first time ever this is happening, and the reason is that in ubuntu7 we added backported feature from Qt 5.6 which the new thumbnailer is using10:26
sil2100I thought we generally avioided depping on particular -0ubuntu versions10:26
Mirvsil2100: this is packaging automagically doing the correct thing... well, almost, the gles should not be like that10:27
sil2100Ok, that explains it10:27
Mirvsil2100: so I think we need to do no-op gles build bumping the version nuumber10:27
Mirvsil2100: siloing10:27
sil2100Mirv: yes, certainly10:27
sil2100Thanks :)10:27
sil2100Generally I hate depping on ubuntu versions, but in the case of Qt well... I guess there's nothing better one can do10:27
cwaynesil2100: heya10:30
sil2100cwayne: hey!10:30
Mirvsil2100: that's not happening in general - but here it is since ubuntu7 version specifically added new symbols that thumbnailer is now using10:30
cwaynesil2100: any idea whats going on with importing images? the last arale custom tar that was built still hasn't shown up in meizu.en-proposed10:31
sil2100cwayne: oh? Still? Let me check the config and the s-i server10:31
sil2100One moment10:31
Mirvsil2100: generally packages don't add new features in ubuntuX versions :)10:32
sil2100Mirv: yeah, that's what I expected and scratched my head about ;)10:36
sil2100But yeah, this is a special case10:37
sil2100hmmm10:45
sil2100Ah!10:45
sil2100I see a typo in the config10:45
sil2100cwayne: ^10:45
cwaynehuh, how did it ever work then i wonder10:46
sil2100cwayne: not sure, it shouldn't have worked in the past, not for meizu.en-proposed10:46
cwaynelol10:48
sil2100Strange that the jenkins job urls are different there10:49
sil2100cwayne: anyway fixed now10:49
sil2100Let's wait for another importer run10:49
Mirvsil2100: ^ 008 built, is it possible to test it with the image similar to how you debugged it10:54
sil2100Mirv: I can try, I debugged it on my chroot, still have it open10:55
sil2100I'll just add your PPA to sources10:55
Mirvsil2100: hmm, the publisher didn't yet run though. build finished 6 minutes ago so 4-9 to go.10:55
Mirvsil2100: thanks10:55
sil2100Ok, I'll prepare everything in the meantime10:56
Mirvsil2100: ok now it should be done10:58
sil2100uh11:03
sil2100Mirv: still a problem11:03
sil2100Mirv: it needs to be 5.4.1-1ubuntu7 not 5.4.1-0ubuntu711:03
sil2100It looks like the non-gles version was a debian -1, so the -gles one needs  that too11:04
sil2100So, not -0ubuntu7 but -1ubuntu7 (didn't notice that originally)11:04
psivaajamesh: The test does try to install libthumbnailer0, qtdeclarative5-ubuntu-thumbnailer0.1, thumbnailer-common and thumbnailer-service11:08
psivaajamesh: this is because libthumbnailer0 is already an installed package due to the base image being vivid11:08
psivaajamesh: please take a look at lines 155,162 and 163 in http://bazaar.launchpad.net/~canonical-ci-engineering/ubuntu-touch-boottest/trunk/view/head:/boottest.sh11:09
sil2100Mirv: regarding silo 006 - we need to make sure it's also released to wily11:18
Mirvsil2100: ouch... so I must lie about the package being in Debian while it isn't11:20
sil2100:<11:20
Mirvok then11:20
jameshpsivaa: so that test has no chance of ever succeeding if we ever merge two binary packages (like we did for thumbnailer)11:23
psivaajamesh: right, with this way we wont have thumbnailer passing :/11:24
psivaaMirv: jibel: not sure if you noticed, the majority of the boottest failures (other than thumbnaier) are due to ''ERROR: timed out waiting for Unity greeter'11:37
psivaaone possible cause as pitti suspected could be the new Mir11:38
Mirvpsivaa: I understood anpok tried testing it already (or well, at least he did test the silo that landed last night)11:39
anpokpsivaa: I took todays devel-proposed image and upgrade to wily-proposed11:40
anpok*upgraded11:40
anpokboots fine11:40
psivaaanpok: is this the base image that you used, just to confirm, http://paste.ubuntu.com/11892361/11:42
anpoki used mako version 25811:43
anpokversion_detail: ubuntu=20150717,device=20150708,custom=20150717,version=25811:44
anpokpsivaa: ok comparing to boottest - I bootstrapped but then just I dist-upgraded11:47
anpok& updated..11:47
sil2100Mirv: testing!11:48
Mirvsil2100: ok, try again, silo is ready11:48
Mirvsil2100: heh11:48
Mirvgood timing11:48
karniping trainguards -- I wanted to make you aware that last thumbnailer changes have broken Telegram, and the app will not start in rc-proposed11:48
karniI've contacted #unity-api team11:48
karniWe dynamically link with libthumbnailer.so, which seems to be gone from the system11:48
Mirvjamesh: ^11:49
karnihttp://paste.ubuntu.com/11892354/11:49
sil2100Mirv: works!11:49
Mirvsil2100: \o/11:49
karniyes, I've pinged jamesh about it11:49
Mirvsil2100: publishing11:49
karniwaiting for his response11:49
psivaaanpok: ack, but i'd do a test on krillin to confirm, the fact that mako successfully booting does not confirm that it will boot with krillin11:50
anpokpsivaa: yup switching devices now..11:50
rvrsil2100: Hi. In silo 7, dashboard says "caught signal 15, aborting". What does it mean?11:51
greybackrvr: it means I cancelled the build11:52
rvrgreyback: So, is it ready for testing or not?11:52
greybackrvr: sadly no, I need to rebuild it and test it once mir in silo 4 lands11:52
sil2100greyback: uh, remember that cancelling a job before it finished preparing the packages is VERY risky11:53
sil2100By risky I mean in certain cases it can lead to the silo being broken11:53
sil2100Only abort when packages are prepared11:53
rvrgreyback: Ok, removing the trello card11:54
greybacksil2100: it was a pretty quick cancel11:54
=== tvoss is now known as tvoss|test
greyback*sigh* that has been sitting there for days11:54
=== tvoss|test is now known as tovss
=== tovss is now known as tvoss
greybacksil2100: but noted, I shall avoid doing so in future11:55
seb128hum12:02
seb128Mirv, jibel, so that mir update/boottest regression, I think it's real12:02
seb128I tried to install the new mir here on my n7 which is on wily12:02
seb128and it has the ubuntu log with 4 dots splash (new, looks nice!) but unity8 never shows and apport triggers on boot for unity8-dash12:03
jibelanpok, ^12:05
anpokyes seeing that.. do we have startup logs from unity8-dash/12:06
jibelseb128, good that boottest caught it. Thanks for the verification.12:06
seb128yw!12:06
seb128also the mir transition is incomplete12:06
seb128 url-dispatcher : Depends: libmirclient8 (>= 0.13.2+15.10.20150605) but it is not going to be installed12:07
seb128ubuntu-push-client as well12:08
seb128ciborium12:09
=== psivaa is now known as psivaa-lunch
kyrofatrainguards: I just added another branch (same project) to my spreadsheet item. Do I need to do anything else to get that new branch into my silo?12:52
Mirvkyrofa: the silo needs to be reconfigured to include it12:55
Mirvkyrofa: since I'm not sure if you can do it, I just reconfigured it for you. now it should work/build fine.12:56
=== tedg is now known as ted
anpokseb128: there was an update to gtk-3.0 - in the mean time - do we have to upload a new source package to silo-004?12:57
kyrofaOkay, thanks Mirv!12:57
seb128anpok, no, the silo landed in wily-proposed it's not needed anymore, right?12:57
anpokseb128: ah ok so gtk+3.0 3.16.5.-1ubuntu2 was built again libmirclient9 and contains the deprecation free mir platform patches13:00
anpok+?13:00
anpokseb128: silo-004 now has url-dispatcher13:01
seb128anpok, updating the silo doesn't make sense since it landed to distro already, no?13:01
seb128anpok, and yes, the gtk upload was to fix an issue with the silo version13:01
Mirvseb128: the silo can be republished to fix proposed migrations, since it's only emptied if the migration succeeds13:04
anpokseb128: just thought we need a rebuilt url-dispatcher package to resolve the problem..13:04
Mirvbut in this case one might to fix archives manually since the fixes are also manual uploads to the silo13:04
seb128Mirv, wouldn't it be more efficient to just upload the extra rebuild directly to the archive?13:04
Mirvseb128: yes, exactly13:04
Mirvbut if they are built in the silo, one can also copy-package those to the archives13:05
anpok(and there is silo-053 which needs it too)13:05
=== _salem is now known as salem_
=== ted is now known as tedg
greybacksil2100: heh you were right, I screwed up silo7 by cancelling a build. Do I need to clean & start again?13:30
sil2100greyback: might be the easiest way, if that's not a problem for you13:31
greybacksil2100: looks like nothing is easy https://ci-train.ubuntu.com/job/ubuntu-landing-007-3-merge-clean/42/console13:33
sil2100Yeah, that's normal... it's freed now, this is normal when the config file got erased/corrupted13:33
sil2100Re-assign and it should be good13:33
greybacksil2100: cool, ta13:34
=== psivaa-lunch is now known as psivaa
pmcgowancan silo 2 be marked as passed13:48
kyrofatrainguards: dh-exec .install files aren't getting multiarch variables in my silo, but it works in my local pbuilder. What's wrong?13:48
sil2100pmcgowan: did QA sign it off?13:48
pmcgowanthey did13:48
pmcgowanacc to trello yesterday13:48
sil2100hm, someone forgot to switch it then13:49
sil2100jibel, davmor2: setting the silo as passed13:49
cwaynesil2100: anyone in qa available to help test the latest arale custom + silo 35?13:59
cwaynei broke my arale at the worst possible time :(13:59
sil2100jibel, davmor2: ^ do you have anyone that could help? ^14:00
davmor2jibel: I can take it14:02
davmor2jibel: that way cwayne only owes one person drinks for the rest of their lives ;)14:03
cwayne:)14:03
cwaynedavmor2: so, the steps to test: 1) install rc rev 2 on arale14:05
cwayne2) favorite/unfavorite some scopes14:05
cwayne3) switch channel to ubuntu-touch/rc-proposed/meizu.en-proposed14:05
cwayne4) install ubuntu-touch-customization-hooks from silo 3514:05
davmor2cwayne: sure on it14:06
cwaynedavmor2: <314:06
davmor2cwayne: that's fine I never have to buy a drink again eva ;)14:07
cwaynedavmor2: that is correct14:07
cwaynealthough penk will owe those to me since this isn't my tarball anymore :P14:07
davmor2cwayne: who requested the testing, Didn't see penk nick there once :P14:08
cwaynedavmor2: lol14:08
pmcgowansil2100, silo 6 can publish14:10
sil2100pmcgowan: I know, need to discuss that first14:10
sil2100pmcgowan: it's a direct upload to vivid, need to make sure those changes are staged for wily too14:10
sil2100It was a request from slangasek and awe_ mentioned he can start doing that post-OTA-514:10
pmcgowansil2100, ok14:11
sil2100Will publish once I have the situation cleared out14:11
awe_sil2100, I don't really see the context in the scrollback?14:12
pmcgowanawe_, silo 6 is network manager change14:13
pmcgowanbut its vivid only?14:14
sil2100awe_: you weren't around when it got ready for publish - waiting for Steve's comment on if I can simply push it normally to vivid14:14
awe_because (a) we forked NM due to the desktop routing change which I didn't want to accept14:14
sil2100Since there's no silo/request with the same change in wily14:15
awe_and (b) I focused on getting everything landed for the phone first14:15
awe_pmcgowan, sil2100 and I discussed this.  I'm currently working on landing all of the changes in wily now14:15
awe_as separate landings14:15
* awe_ is editing .patch files as we speak14:15
sil2100awe_: ok, so you want this to still go in and then you'll land it with all the others for wily, right?14:16
awe_yes14:16
awe_but go into the overlay PPA14:16
awe_not vivid itself14:16
awe_did I get the citrain fields wrong?14:16
sil2100awe_: I suppose it's fine, remember our kind request to at least get the silo for wily with each vivid-overlay landing once you sync it up14:17
sil2100The release team doesn't like when we land things in overlay first, it introduces the risk of the delta between devel and stable14:17
awe_sil2100, I don't like shipping phones with unstable code14:18
awe_I put my efforts on supporting devices we'd shipped, and explained myself in depth14:18
awe_this should have zero impact on desktop14:19
sil2100Right, and we're thankful for that, but we need to make sure that everything that lands to the stable devices also lands to the devel ones14:20
sil2100Otherwise, once we finally switch sometime in the future to the new series, we don't miss any fixes - and this already happened the last time for multiple projects14:21
sil2100So the release team is really cautious here14:21
kyrofatrainguards: I'm having some trouble in silo 11. My dh-exec .install files aren't getting $DEB_HOST_MULTIARCH defined... and I'm not sure why. It works locally14:25
sil2100awe_: did cyphermox take a look at those changes? Asking since this would mean it's already been reviewed from the packaging POV14:26
sil2100kyrofa: hm, let me take a look if it's something we can help with14:26
kyrofasil2100, thanks. I can do it in override_dh_auto_install, but the debian wiki suggested dh-exec (https://wiki.debian.org/Multiarch/Implementation#Dynamic_debian.2F.2A_files)14:27
awe_sil2100, it was approved by abeato_ only14:28
awe_sil2100, as for the packaging, as NM is a packaging only branch, that's all I modified.  I added a new patch, and corresponding changelog entries14:30
sil2100awe_: yeah, thinking how to proceed with that, last time I just published it as it's nothing more than like publishing a code-only-change, but...14:30
sil2100Our agreement with the release team is strange14:30
sil2100Ok, I'll take it on me then14:31
awe_sil2100, what should I have done differently?14:32
sil2100awe_: everything fine from your side, although I would prefer cyphermox to be aware of the changes, it was more of if I should find a core-dev to approve it first or not...14:32
awe_if I always get a core-dev to review, would that smooth this out next time?  That seems odd, given that I'm landing in the overlay PPA, but if that's the requirement, so be it14:32
davmor2cwayne: should that of fixed the issues with only seeing 6 icons if so fail, Does it need to be installed during the install of the upgrade?14:57
cwayne_oh shit i think i forgot to rebuild the package with scott's latest fix14:58
cwayne_sorry davmor2, ill ping you once i get it rebuilt15:00
kyrofasil2100, have you had a change to take a look at the dh-exec stuff in silo 11 yet?15:15
sil2100kyrofa: looking, but in a meeting still so it's hard to concentrate15:16
sil2100But I see what you mean15:17
kyrofasil2100, heh, no problem :)15:17
kyrofasil2100, it's not some sort of security thing, is it? Since the .install files are executable?15:18
kgunnrobru: so, anpok (who's missing from irc atm) updated silo4 due to getting stuck in proposed....has now seemed to correct the silo, can you attempt to pub again?15:30
kgunncamako: ^15:30
rvrmzanetti: ping15:31
mzanettihi victor15:35
mzanettirvr, ^15:35
rvrmzanetti: Hey15:36
rvrmzanetti: I'm testing silo 4815:36
rvrmzanetti: I have a problem with the "start" gesture/Launcher button15:36
mzanettihmm15:37
mzanettiwhat issue=15:37
mzanetti?15:37
rvrmzanetti: Without the silo, when I'm on the news scope, pressing the "start" makes the Dash go back to the first scope15:37
rvre.g. Today15:37
rvrmzanetti: With the silo, doesn't do anything15:37
mzanettiI did think there's something weird when I tested it... but tsdgeos convinced me it was good as it is :)15:38
mzanettilet me verify15:38
tsdgeosrvr: mzanetti: ok that's bad and should not have regressed15:38
mzanettiindeed15:38
mzanettiit seems to behave differently15:39
mzanettiyeah... bug... I guess that means failing the silo :/15:39
rvrYup15:39
tsdgeosmeh :/15:39
mzanettisorry rvr15:39
tsdgeosthrow away that branch15:39
tsdgeosand create unittest15:39
popeykarni: is there a bug for broken telegram / thumbnailer wencan point people to?15:40
karniyes, 1 sec15:40
karnipopey: https://bugs.launchpad.net/libqtelegram/+bug/147569115:41
ubot5Ubuntu bug 1475691 in libqtelegram "Telegram broken, old thumbnailer library discarded" [Critical,Triaged]15:41
mzanettirvr, I'll drop that branch from the silo and rebuild the rest as it is, ok?15:41
rvrmzanetti: Ok15:41
popeykarni: thanks15:44
davmor2cwayne: relocating to the caravan back in 40 minutes-ish15:51
cwayne_davmor2, ack15:54
sil2100kyrofa: hm, I wouldn't do it in this way for sure16:07
kyrofasil2100, how come?16:09
sil2100One moment16:13
sil2100kyrofa: so generally the recommended way is to make the build system take care of building/installing the binaries in the right multiarch directory and then just ask packaging to install them to their respective ones in the system16:17
kyrofasil2100, dh-golang doesn't do that. The go idioms have no way to do that. I have to do it by hand, one way or another16:19
sil2100kyrofa: ouch, ok, this changes the situation - ok, we can do it differently16:19
sil2100Sadly I'm a bit overloaded with work right now16:20
kyrofasil2100, I can add a Makefile rule to copy binaries around, but that's really the same thing16:20
sil2100Could you try poking some core-devs for advice here?16:20
cwayne_davmor2, so package should be ready whenever youre back16:20
kyrofasil2100, I'd be happy to-- any recommendations?16:20
sil2100kyrofa: I would say poking slangasek, ogra_, seb128 or infinity - not sure which one of them would have some free cycles :)16:22
kyrofasil2100, alright, thanks!16:22
slangaseksil2100, kyrofa: I would not expect there to be any multiarch directories that are relevant to golang.  this is silo 11?16:32
* sil2100 has no experience with golang16:33
kyrofaslangasek, indeed it is. I'm just trying to place a unity scope in the right multiarch place16:33
kyrofaslangasek, but the go tools don't support installing anywhere other than $GOPATH/bin, and dh-golang straight-up copies binaries to /usr/bin, so I wrote .install files to move them to the right spot16:34
slangasekkyrofa: what's the right multiarch place, in this context?16:36
kyrofaslangasek, /usr/lib/${DEB_HOST_MULTIARCH}/unity-scopes16:37
slangasekok16:37
slangasekso I think it's fine to use dh-exec for this, and move the file from /usr/bin to /usr/lib/${DEB_HOST_MULTIARCH}/unity-scopes in the .install16:38
kyrofaslangasek, it works fine on my local pbuilder, but in the silo it creates a directory named literally "${DEB_HOST_MULTIARCH}"16:38
slangasekah16:39
slangasekkyrofa: is the executable bit of the .install file represented in your branch?16:39
slangasekor is this a source upload?16:39
kyrofaslangasek, indeed it is represented16:41
kyrofaslangasek, I was wondering if it was some kind of protection in the silo that disallowed execution16:41
slangaseknot "protection", just "bug"16:42
kyrofaslangasek, if you're curious: lp:~kyrofa/unity-scope-snappy/improve_debs16:42
kyrofaslangasek, heh :)16:42
kyrofaslangasek, so I can obviously do this in debian/rules, just not nearly as slickly16:43
slangasekkyrofa: actually, the problem is that the package doesn't declare itself to be source format 3.016:43
slangasekso there's no way to represent this executable bit on a round trip into a .dsc and back16:43
kyrofaslangasek, hmm. I was specifically asked to remove that :P16:44
slangasekby whom? :)16:44
slangasekkyrofa: you'll want to create debian/source/format with contents '3.0 (quilt)', build a source package, unpack it again, and test the build - that should let you verify that the source package is being generated correctly16:45
kyrofaslangasek, robru asked me to drop debian/source entirely16:46
slangasekkyrofa: ok; robru is mistaken on this :)16:47
kyrofaslangasek, okay, initially I had 3.0 (native) with a version number of 0.1.0 (no -0ubuntu1). I should do quilt instead?16:47
slangasekkyrofa: ah - yes, 3.0 (native) is wrong because this isn't a native package (native == no separate upstream and Ubuntu parts)16:48
slangasekkyrofa: 3.0 (quilt) is the right thing here16:48
kyrofaslangasek, alright. I'm a bit confused by that though. This is a Canonical project, for Ubuntu Personal. Can you explain how the upstream and Ubuntu parts are separate in this case?16:49
slangasekno but I can handwave furiously16:50
kyrofaslangasek, (I'm not a packaging pro, as you may have gathered :)16:50
slangasekkyrofa: the fact is, we use non-native version numbers for all of these packages, and the train autogenerates the upstream tarballs; so they're non-native packages in that sense, and also in the sense that any Ubuntu developer can upload a -0ubuntu2 revision to the archive using the same tarball16:51
kyrofaslangasek, ohhhh16:51
kyrofaslangasek, okay, I've gotcha :)16:51
slangasekso we just want to be consistent with that, even if the distinction between native and non-native is somewhat arbitrary16:51
kyrofaslangasek, fixing now!16:52
kyrofaslangasek, thank you very much16:52
slangasekkyrofa: no prob16:53
kyrofaslangasek, in order to test that out locally then, I'll need to create an upstream tarball?17:00
slangasekkyrofa: you should be able to download the existing one from the ppa17:01
slangasek(in order to not have to reproduce the train's own tarball synthesis)17:01
dobeyhmm17:03
dobeykyrofa: if you use 3.0 (native) you don't need an upstream tarball17:03
dobeyslangasek: my recommendation here is to use 3.0 (native) and a proper native version string in debian/changelog17:04
dobeyslangasek: it is a native package, because there are no separate upstream and ubuntu parts17:05
slangasekdobey: that is an option, but I don't like native packages in general and I'm not sure how the train would handle that17:05
slangasekthere certainly are17:05
robruslangasek: what? we have guidelines on this we've been using for a couple years now: https://wiki.ubuntu.com/DailyRelease/InlinePackaging (this is even since pre-train days)17:05
dobeywhat is the separate ubuntu part?17:05
dobeyrobru: those guidelines are ill-informed17:05
slangasekdobey: the debian/ directory is maintained by the Ubuntu developers, not by upstream17:06
dobeyslangasek: it is maintained in the upstream source tree17:06
slangaseksometimes17:06
dobeyin this specific case17:06
dobey(for most things landing via ci train, even)17:07
slangasekthe packaging changes are owned by the Ubuntu developers, not by the upstream developers (thus Ubuntu dev sign-off is required for any changes); and sometimes Ubuntu changes land in the archive without being landed in the upstream trunk17:07
slangasekso no, not native17:07
dobeythen someone needs to fix dpkg to support something that isn't native, but which isn't ubuntu either. because these things are somewhere in the middle, by that argument17:07
slangasekrobru: well, inasmuch as those guidelines are incompatible with dh-exec, the guidelines are wrong.  Is there a reason that 3.0 (quilt) would be unsupported by the train?17:07
robrudobye: slangasek: train explicitely requires debian/ in the upstream trunk, we don't support anything else17:07
slangasekdobey: nope, this is non-native.17:08
dobeythe upstream source tree is the canonical debian/ directory.17:08
dobeytherefore it is native17:08
slangasekno, it's not17:08
slangasekit's not canonical, and it's not native17:08
dobeyany changes uploaded directly to the archive, outside of that, would be non-native17:08
slangasekthe canonical debian/ directory is whatever goes into the archive17:08
robruslangasek: the idea is that the train only works on canonical-owned projects so there just shouldn't be any quilt patches at all.. they should all be upstreamed17:08
slangasekyeah, we don't flip-flop packages between native and non-native on each upload17:08
slangasekrobru: I'm not talking about quilt patches here17:08
slangasekthat's the format name; it's not required that there be any quilt patches in the debian directory17:09
dobeyit is native, but whatever17:09
robruslangasek: IIRC dobey hacked in support for native packages, but the version-generating feature doesn't work as well. definitely non-native is the way to go to be a first class citizen in train land.17:11
dobeyyes, native packages work in the system17:12
dobeyrobru: version-generation works fine with native17:12
slangasekrobru: I agree; which means in this case it needs to be 3.0 (quilt) because that's the non-native package format that allows representing executable bits in debian17:12
robruslangasek: alright17:14
davmor2cwayne: how we doing?17:15
slangasekrobru: ok. so as long as the train isn't going to choke on 3.0 (quilt) at the source prep stage, I think that's the way forward17:15
dobey:/17:18
robruslangasek: sounds fine then. Indeed the 'delete debian/source' instruction is in the context of "now we're upstreaming all the patches"17:20
kyrofatrainguards: I'm getting a "dependency wait timeout" for arm64 and ppc in silo 11. How do I debug that?17:24
robrukgunn: anpok: need this top-approved: https://code.launchpad.net/~mir-team/url-dispatcher/mir-release-0.14.0/+merge/26295317:26
davmor2cwayne: just got the message thanks trying now17:26
dobeykyrofa: golang-go.tools isn't built on those platforms currently it seems17:26
slangasekkyrofa: not sure about the 'timeout', but dependency wait is expected here because the package build-depends on toolchain bits that don't exist on those architectures; the problem is ignorable17:26
robruslangasek: if it's ignorable then why did the train explode on it? that means there's a regression from distro.17:27
kyrofaslangasek, ah, okay. Yeah I'd expect a better error, haha :) . Okay, ignoring!17:27
camakorobru, I top-approved it17:28
camakokgunn, anpok ^17:28
dobeyhmm, so it failed to build on those archs in vivid17:28
dobeyand it hasn't been updated in ubuntu since then17:28
slangasekrobru: unity-scope-snappy isn't in the distro yet, so it can't be a regression17:28
slangasekrobru: (I checked this before opening my mouth :)17:28
dobeyhmm, and there's not a new version in debian either17:29
robrukyrofa: why are you rebuilding?17:30
kyrofarobru, I just pushed up the debian/source/format. I'd like real packages built :P17:30
robrukyrofa: ok sorry I'm just trying to catch up here17:31
kyrofarobru, oh you're good. Yeah, with the dh-exec files not being executed correctly I ended up with packages using variable names as directory names, haha17:32
robrukyrofa: slangasek: ok yes so in this case since there is no existing release in ubuntu, train default is to watch all arches, so that's why it's erroring on this ignorable problem. it'll keep happening every time you rebuild until finally there's a release, then the *next* silo you do for this package will watch the right arches correctly.17:33
kyrofarobru, good to know!17:33
kyrofarobru, thank you :)17:33
robrukyrofa: there may be other issues you run into, generally speaking the train isn't good at building brand-new packages, there's a bunch of code paths that check distro in order to know what to do/expect.17:34
robrukyrofa: you're welcome17:34
kyrofarobru, ah, happy to exercise them!17:34
robrukyrofa: but yeah once you get that first release out the door, all subsequent ones should go a lot smoother17:35
robrukyrofa: keep an eye on the PPA for now, the depwait timeout is something like 2 hours, so you can save yourself 2 hours of wait time by ignoring the train dashboard status and going right to the source.17:35
kyrofarobru, honestly everything I've hit so far has been my own lack of debian packaging knowledge17:35
robrukyrofa: and my bad advice ;-)17:35
kyrofarobru, had you not said anything I wouldn't have learned what I learned today :)17:36
robrukyrofa: ha, you're welcome then :-P17:36
kyrofarobru, ;)17:37
cjwatsonrobru: depwait timeout> one hour rather than two (and a cron job rather than a timeout)17:59
robrucjwatson: you're talking lp side. I'm talking in the train. When the train is polling the PPA build states, it gives up after 2 hours.17:59
robru2 hours of depwait anyway. any other state it'll happily poll forever.17:59
cjwatsonoh right, fair enough17:59
cwayne_davmor2, any luck?18:15
davmor2installing the silo now cwayne18:19
cwayne_kk18:21
davmor2cwayne: I haz 8 count them 8 Icons Woohoo!!!!!!!!18:26
davmor2cwayne_: 8 icons and the modifications are still in place too \o/18:28
davmor2jibel, robru: ^ do we need to retest or should we just push it through?18:29
robrudavmor2: what silo? what's going on?18:29
robrudavmor2: generally speaking a rebuild requires a retest, unless it's a totally trivial change, then a quick smoketest should suffice.18:30
davmor2robru: silo 35 and a custom tarball for the fix for the 8 icons on upgrade for ota518:30
robrudavmor2: custom tarball changes? that sounds risky ;-) I'd retest18:31
robrudavmor2: maybe not the full test suite but make sure it's actually fixing the issue.18:31
davmor2robru: yeah I'm particularly concerned as cwayne forgot to build the image with the fix in D'oh :)18:31
robrudavmor2: yeah I think a retest is in order ;-)18:32
cwayne_+1, because I'm an idiot :)18:34
cwayne_sorry, been like a year since i'd done an MP based landing instead of just a custom tar18:35
davmor2cwayne_: why the tail?18:39
cwayne_?18:39
davmor2cwayne_: you have an _ and there is a cwayne too just wondered why ;)18:40
cwayne_davmor2, ah, cus im on my laptop downstairs but i left my desktop on upstairs18:41
cwayne_and i never setup an irc proxy18:41
davmor2cwayne: then set one up muppet boy you do nothing else with your day now you don't build the images ;)18:42
davmor2cwayne_: too^18:42
cwayne_lol18:42
davmor2cwayne_: so mark it passed I don't know what the plan is to get them into the staging image though we would need sil2100 for that I assume unless robru knows how to do it :)18:46
robrudavmor2: well I can hit publish on the silo, but I'm not up to speed on custom tarballs or building images.18:49
cwayne_id say we should wait for sil then18:49
robrucwayne: that'll be, like 12ish hours...18:49
robrucwayne: I mean next week18:49
cwayne_well, we generally dont push custom tars without his +1, and this landing should go alongside a custom tar18:50
cwayne_so if we have to wait for monday, i guess it is what it is..18:50
cwayne_davmor2, thoughts?18:50
davmor2robru: this has to land in the image for ota 5 for arale so it's not a normal landing I don't think18:50
robrucwayne: ok, I'm going to mark it not tested so I don't forget and accidentally publish it then. follow up with sil on monday18:50
cwayne_robru, sounds reasonable, thanks18:51
robrudavmor2: are you saying it's urgent then? I thought ota5 was just delayed18:51
davmor2robru: I think it needs some wrangling,  No urgent to test so it's ready for Monday that is achieved18:51
cwayne_yeap18:52
cwayne_so we should be all set18:52
cwayne_for today i mean18:52
cwayne_thanks a lot for testing davmor218:52
davmor2cwayne: is there someone we can ping in EU timezone to push the button on the tarball?18:53
robrudavmor2: ok great, sorry I don't know more about custom tarballs18:53
cwayne_davmor2, well penk could monday18:53
robrudavmor2: sil is EU ;-)18:53
cwayne_since it is his now anyway :)18:53
davmor2robru: no worries I'll ping sil2100 after :)18:53
robruqbot no19:01
kyrofatrainguards: I just added a few new branches to line 74 of the spreadsheet (same project). Can I get silo 11 reconfigured to use them?19:01
kyrofatrainguards: I don't believe I can do this myself-- please correct me if that's wrong19:02
robrukyrofa: you can do it yourself. the rules on this have changed recently and probably haven't been updated yet19:02
kyrofarobru, ah, nice! How do I do that?19:03
robrukyrofa: first click on any cell in your row. then at the top there's a menu "Landing tools > Assign/Reconfigure"19:03
davmor2robru: sil2100 left you a cryptic note on the silo 20150717/robru: This is QA approved by davmor, but needs to land in coordination with a custom tarball, publish later so definitely over to silo2100 :)19:07
robrudavmor2: no I just wrote that myself.19:08
davmor2robru: ah okay19:08
robrudavmor2: the date/name at the start of those notes indicates who wrote it and when19:08
robrudavmor2: that was just there to indicate it was testing pass, but I officially set the silo to not testing pass so that the dashboard wouldn't burn a hole in my eyes with a big temping "PUBLISH THIS" neon sign19:09
davmor2robru: oops19:09
kyrofarobru, awesome, thank you, it works! :)19:10
robrukyrofa: you're welcome!19:10
taiebotFate as decided i will not buy an MX4 :'(. Wanted to top up my paypal account to pay for the new phone. Got the call for my bank to validate the transaction but my Nexus 4 running UT refused to take the call.19:12
taiebotOups wrong channel19:12
kyrofataiebot, yeah, I learned the "cihelp" doesn't get your questions answered in other channels, too19:14
sil2100davmor2, cwayne: I'll copy over the fix to the snapshot and try to kick an image19:20
sil2100davmor2, cwayne: from my POV the new custom tarball can be freely published to the rc-proposed channel19:20
sil2100davmor2, cwayne: are the krillin and vegetahd ones ready as well?19:20
sil2100I just need to finish something up and I'll get right to it19:20
davmor2sil2100: awesome dude, wasn't sure if there was anything special needed19:21
salem_robru, hey, as boiko is out, would you trigger a rebuild in silo 44 for me?19:22
davmor2mzanetti: what happened to greybacks silo 007?19:23
robrusalem_: you should be able to trigger builds, can't you?19:43
salem_robru, I tried, but it seems I have no permission19:43
salem_robru, "tiagosh is missing the Job/Build permission"19:43
robrusalem_: what's your launchpad id?19:44
salem_robru, tiagosh19:45
robrusalem_: ok, I added you. if you log out of jenkins, log back in, make sure during SSO you check off the lp teams, then log back in and you should be able to build19:45
salem_robru, awesome, thank you!19:48
robrusalem_: you're welcome19:49
kyrofatrainguards: My build logs suddenly look like this: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-011/+build/7665329 . Is that normal?19:54
kyrofatrainguards: Meanwhile my silo just continually says "Currently building..."19:55
robrukyrofa: I've never seen this before19:55
robrumaybe cjwatson knows ^^19:56
kyrofarobru, it's happened twice now-- I canceled the job and restarted it, and it happened again19:56
robrukyrofa: yeah don't do that19:56
robrukyrofa: "cancelling the job" doesn't have any effect on what's happening in the PPA.19:57
kyrofarobru, oops19:57
robrukyrofa: just let it sit for a bit. cjwatson mentioned the other day he was making some changes to the builders and there was a hiccup similar to this. this could be related.19:57
robrukyrofa: last time, the build log said finished while lp said it was still building. what I've never seen before is the weird unicode errors in the log19:58
kyrofarobru, yeah... suspicious indeed. Alright, I'll give it a breather19:59
kgunncamako: looks like we've still got an issue ?20:11
kgunnhttp://people.canonical.com/~platform/citrain_dashboard/#?q=ubuntu%2Flanding-00420:11
kgunncamako: ah...maybe just issue with device ?20:12
kgunnhttps://jenkins.qa.ubuntu.com/job/wily-boottest-mir/lastBuild/artifact/results/log/*view*/20:12
camakokgunn yea looks like it20:26
kgunnrobru: ^ am i reading that correct ?20:27
robrukgunn: yeah boottest is known to be flaky20:29
robrucihelp: looks like almost all of these packages: http://people.canonical.com/~platform/citrain_dashboard/#?q=ubuntu%2Flanding-004 are stuck in proposed due to boottest, can somebody investigate?20:29
robrukgunn: actually something weird there, xorg-server doesn't look like it published, do you know what's up with that?20:29
* kgunn looks20:29
robrukgunn: weird, the version from the PPA is in -proposed, but the train seems to be misreporting that it didn't publish. never seen that before20:31
robrukgunn: https://ci-train.ubuntu.com/job/ubuntu-landing-004-2-publish/71/artifact/packagelist_rsync_landing-004-wily/*view*/ here's the manifest even showing it publishing along with everything else20:32
robrukgunn: so I guess don't worry too much, but this will prevent the silo from auto-merging, we may have to manually poke the merge job once the migration completes. ping me if you notice the status change to only mention that xorg-server hasn't been published (and not mentioning anything else)20:33
kgunnrobru: got it...20:33
balloonscihelp, can you disable utopic builds for sudoku app? sudoku-app-ci and sudoku-app-ci-autolanding20:52
josephtballoons: it looks like the utopic build is the only one, is that okay?20:55
balloonsjosepht, I see generic-mediumtests-utopic being run for it, as well as sudoku-app-utopic. You can keep sudoku-app-vivid20:55
balloonsthe framework requires vivid now essentially, so no more utopic can be run20:56
josephtballoons: I've pushed an MP for disabling the job in cu2d-config.  It will likely be Monday before it lands.21:03
boikorobru: could you please trigger an amd64 wily build of telephony-service on silo 43?21:19
boikorobru: trying to identify if the failure is a transient one or a real failure21:19
robruboiko: sure21:21
boikorobru: thanks21:22
robruboiko: you're welcome21:23
cjwatsonrobru: those are unicode but they aren't errors - that's just sbuild's box drawing, not rendered well here21:24
cjwatsonkyrofa: almost certainly your build process has left something around on failure that for some reason we aren't managing to clean up correctly.  I've cancelled the build21:24
cjwatson(build, not job)21:25
cjwatsonkyrofa: you should be able to see the full build log now21:25
robrucjwatson: ah, thanks for checking that21:26
cjwatsonit's a bit odd that it didn't kill itself correctly, but I'm not investigating in that much detail on a Friday night :)21:26
cjwatsonkyrofa: anyway there seems to be a missing Build-Depends: python3-requests or similar here, so maybe that will be enough to get things going properly21:27
kyrofacjwatson, thanks for taking care of that! You're right, I forgot that dep22:18
=== salem_ is now known as _salem
boikorobru: coupd you please get libphonumber source package copied over from this ppa: https://launchpad.net/~boiko/+archive/ubuntu/source-uploads/+packages to silo 44?23:35
robruboiko: one sec23:35
boikoah, source packages not supported in dual landings, hmm :/23:36
robruboiko: oh yeah right. you need to either do a wily landing and then later do a sync back to vivid landing, or make an MP for this package23:37
boikorobru: ok, I will check with _salem on monday how we want to do that, thanks anyway23:38
robruboiko: you're welcome!23:39

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