/srv/irclogs.ubuntu.com/2016/05/02/#ubuntu-ci-eng.txt

=== blr_ is now known as blr
oSoMoNMirv, is https://code.launchpad.net/~timo-jyrinki/webbrowser-app/no-change-rebuild-qt551/+merge/278928 still needed?08:15
MirvoSoMoN: sure not, it was even landed but Train/LP doesn't really know how to merge that empty MP08:16
Mirv(or maybe I did a manual upload in December, I don't remember)08:17
oSoMoNMirv, should the branch just be deleted?08:17
MirvoSoMoN:  I marked it as merged for the revision it did get merged to, it seems http://bazaar.launchpad.net/~phablet-team/webbrowser-app/trunk/revision/129308:18
oSoMoNMirv, perfect, thanks!08:18
Mirvso train handles everything but not marking the branch as merged08:18
jgdxtrainguards: hey, could anybody look at [1]? Nothing changed in trunk since last successful landing, so it's a bit puzzling why it ftbfs. [1] https://ci-train.ubuntu.com/job/ubuntu-landing-058-1-build/53/console08:23
MirvI guess no landing meeting today as sil away08:32
jibelMirv, no, the only tihng to discuss is rootfs build and silo 58 landing08:35
Mirvjibel: ok08:35
jibelMirv, for 1 we need sil or ogra_ and 2 is in progress08:35
Mirvjgdx: ok I've found something now that I'm a bit healthier. the lp:ubuntu-push/automatic branch is not based on the trunk and that's the likely cause for the problems. it at least misses all train changelog entries since last August08:44
Mirvjgdx: so maybe it's just something that needs merging once in a while08:45
Mirvjgdx: that's the only thing I've found so far, but I'm trying to make various hacks in the branch to see what could lead to success... the old changelog entry might lead it to fetch some old tarball from somewhere instead of creating new orig tarball or something08:45
jgdxMirv, I think the proper fix for that is to deprecate automatic in favor of running CI on trunk.08:47
Mirvjgdx: ok it'd seem like syncing the changelog entries would fix the issue https://ci-train.ubuntu.com/job/ubuntu-landing-023-1-build/31/console08:48
jgdxMirv, okay, let's do that08:49
Mirvjgdx: whatever works the best for you, but if you start to run in to too many problems you could consider that. SDK team for example does use a staging branch from where they land single MP to trunk.08:49
Mirvso it's not like you'd be the only one08:49
jgdxMirv, this is the change? https://code.launchpad.net/~jonas-drange/ubuntu-push/sync-chlog/+merge/29351408:51
jgdxMirv, and then I'll need to merge that into silo 58, right?08:53
Mirvjgdx: yes, that looks correct08:56
Mirvjgdx: note that I did try two other things first but I doubt they mattered, so let's try with just that08:57
jibelMirv, I don't understand the status of https://requests.ci-train.ubuntu.com/#/ticket/1241 . It has been approved and published and half landed08:57
jgdxMirv, could you give me a +1 on https://code.launchpad.net/~jonas-drange/ubuntu-push/sync-chlog/+merge/293514 ?08:58
Mirvjibel: it looks like both were published (https://ci-train.ubuntu.com/job/ubuntu-landing-001-2-publish/1/console) but account-polld was rebuilt after that09:01
jibelMirv, so should we reapprove?09:04
Mirvjibel: seems so, and train wise this kind of method works just fine, republishing works09:05
morphisMirv, jibel: do we got an image build over the weekend?09:16
jibelmorphis, no, the rootfs fails to build because the password file changed09:17
morphisoh09:17
morphisjibel: which password file?09:17
jibelmorphis, and we should get bug 1575184 fixed first09:17
ubot5bug 1575184 in Ubuntu Push Notifications "ubuntu-push is flooding dbus with NameOwnerChanged signals" [High,In progress] https://launchpad.net/bugs/157518409:17
morphisjibel: afaik that just landed09:18
jibelmorphis, it didn't the silo didn't even build09:18
morphishm, I saw a mail from citrain09:18
jibelit's empty https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-05809:19
morphisjibel: do we know why its not building?09:19
jibelmorphis, Mirv and jgdx are on it, some unmerged changes in trunk apparently09:20
morphisI see09:20
jibelmorphis, and for the rootfs https://launchpadlibrarian.net/257185922/buildlog_ubuntu_vivid_armhf_ubuntu-touch_BUILDING.txt.gz09:20
jibelscroll down to the bottom09:20
jibelThere were changes to the password database,09:20
jibelplease adjust the values in the livecd-rootfs source in the file:09:20
morphisah09:20
jibellive-build/ubuntu-touch/hooks/00-uid-gid-fix.chroot_early09:20
morphislooks like we got dhcpd as new one09:21
jgdxMirv, do you know where tarmac runs, and does it have a web view of some kind? I get nervous when it takes > 20 mins to merge automatic.09:21
oSoMoNtrainguards: when will we have triple-landings?09:21
morphisjibel: so the dhcpd addition is fine as that is coming with us having ics-dhcp now installed09:22
morphisjibel, Mirv: does any of you know if the livecd-rootfs fix from awe landed?09:32
jibelmorphis, it didn't09:33
morphishm09:33
jibelmorphis, we decided to wait until sil is back09:33
morphisok09:33
jibelmorphis, but it could land today09:33
jibelmorphis, didn't want to land on a Friday evening09:34
morphisjibel: so what are we doing with the cahnge password file?09:34
jibelmorphis, we need sil or ogra_ or slangasek09:34
morphisok09:34
jibelmorphis, we could land the livecd rootfs change at the same time09:34
jibelmorphis, Lukasz is on vacations until Wed, ogra_ seems to be offline09:35
morphisperfect ..09:36
ogra_jibel, i'm around, sorry, didnt have time to check yet09:40
jibelogra_, np we need another silo before building a new image anyway. Otherwise the phone is barely usable09:41
ogra_k09:41
jibelogra_, you usually respond instantaneously. Since you didn't I assumed you were offline :)09:42
ogra_heh09:43
Mirvjgdx: did it merge yet? but no, no direct view to tarmac.10:13
jgdxMirv, no, it didn't10:14
MirvoSoMoN: later (a few weeks), we start with vivid+xenial and get xenial in better shape.10:14
oSoMoNMirv, ok10:15
jgdxMirv, and last time tarmac failed, it took two days to report back. Not sure we have that kind of time.10:15
Mirvjgdx: what do you know about your CI system? I'm unfamiliar with the one that adds these [r=morphis] tags. I mean I could just merge it manually.10:15
Mirvjgdx: if it doesn't break anything10:15
jgdxMirv, I know nothing about it.10:16
Mirvjgdx: :)10:16
Mirvjgdx: well, let's revert the automatic branch to rev 426 if there's any problem, but I doubt there is10:17
jgdxMirv, okay dokay10:17
Mirvjgdx: ok, just try to rebuild your silo now10:18
jgdxMirv, building…10:19
Mirvjgdx: same error I see10:19
ogra_jibel, so looking at https://launchpadlibrarian.net/257185922/buildlog_ubuntu_vivid_armhf_ubuntu-touch_BUILDING.txt.gz ... the dhcpd user is wanted in the images ?10:20
jibelmorphis, ^10:20
ogra_(seems like some postinst creates it)10:20
morphisogra_: yes, we're installing ics-dhcp now10:20
ogra_ok10:20
morphisto have dhclient and dhcpd10:20
ogra_the daemon ?10:20
ogra_interesting10:21
morphisyes10:21
morphiswe need it for WiFi Direct support10:22
morphisogra_: but we're only running it on demand so the upstart job is set to manual10:22
ogra_heh, wihle we'Re at at ... i somehow broke my wifi on the M10 ... by making a BLE mouse work10:22
jgdxMirv, --exclude=.bzr* --exclude=.git* and then “the modified files are:ubuntu-push/docs/example-server/.bzrignore […]”?10:22
morphisogra_: hah :-)10:23
morphisogra_: but the BLE mouse works now?10:23
ogra_(as soon as i enable BT now i cant get any data through)10:23
ogra_do you know any ways to reset that ?10:23
ogra_morphis, i cant "unpair" it anymore ...10:24
morphisogra_: you can erase the BT state with rm -rf /var/lib/bluetooth/*10:24
morphisthen reboot10:24
morphisbut that will remove all stored state information for BT10:25
Mirvjgdx: ok, iterating, please rebuild again10:25
jgdxbuilding…10:25
Mirvjgdx: I was again able to start a build with my own branch, so it seems 2/3 of the changes I did were actually needed..10:26
Mirvjgdx: it's working!10:26
jgdxMirv, don't jinx it!!1110:27
ogra_as soon as BT is enabled and the mouse is powered it connects ...10:27
ogra_ah, thanks !10:27
ogra_/bin/echo -e 'scan on\ndiscoverable on\nagent on\ndefault-agent\npairable on\npair E2:5D:E0:E7:46:00\nquit'|bluetoothctl10:27
ogra_thats what i used ...10:27
ogra_microsoft designer mouse ...10:27
ogra_jibel, hmm, did sil not upload the livecd-rootfs change for NM last week ?10:27
jibelogra_, he didn't10:27
* ogra_ still sees the olf livecd-rootfs in the overlay10:28
ogra_*old10:28
jibelogra_, we could merge it today, it's in silo 52 or you prefer to wait for lukasz?10:28
jibelsilo 42*10:29
jibelI'll approve it, there is not much to test10:29
Mirvjgdx: it's building. BUT. the build is failing on vivid.10:30
Mirvjgdx: succeeding on xenial.10:31
Mirvjgdx: and over there you have something that unfortunately doesn't look any less mysterious at first sight than your previous problem... what on earth is that "cp: cannot stat ‘debian/tmp/=>’: No such file or directory"10:32
jgdxMirv, where do you see that? What's the failure10:32
Mirvjgdx: in your silo, expanding the lines https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-058/+packages10:32
Mirvjgdx: some test failures also on xenial. it's like the world would have exploded between your last landing in March and now. since your new landing is as simple as it is...10:33
jgdxMirv, some of the tests have always been flaky10:36
jgdxbut yeah, this is worse than usual10:36
=== ogra_` is now known as ogra_
jgdxMirv, Samuele, who previously worked on u-p, will take a look later today. I'm no deb packaging expert, so I can't effectively debug the debian/tmp issue, but will take a look at making the tests less flaky.11:04
jgdx… will also try to escalate this issue a bit11:05
Mirvjgdx: it's as if a file named "=>" would be tried to be installed11:05
Mirvjgdx: well, it seems in ubuntu-push-client.install there is a line "usr/bin/ubuntu-push => /usr/lib/ubuntu-push-client/ubuntu-push-client" which is then probably erronous or some new feature that was not available in vivid11:06
Mirvjgdx: I just have zero idea how the 0310.2 was able to build and publish in March with all that stuff11:06
jgdxMirv, yeah, how to rationally explain that?11:08
Mirvjgdx: well, I guess it's not wrong then but maybe there's a new hidden problem elsewhere so that after build the files are not where they should be. I mean, checking the source https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/stable-phone-overlay/+sourcepub/6201985/+listing-archive-extra it also had ">=" lines in .install files and the overlay can't regress like that to not support the synta11:13
Mirvx so it must be something else11:13
jgdxMirv, builds fine on xenial+stable overlay btw11:23
jgdxscratch that for now, I have pending updates.11:26
jgdxMirv, xenial+overlay builds fine. Are there any special parameters to those LP builds? If only I could reproduce locally12:01
jibelrenatu, silo 1 re-approved12:03
Mirvjgdx: the only special ones are the custom lines in debian/rules12:03
renatujibel, thanks12:03
Mirvjgdx: override_dh_auto_build for building and override_dh_auto_test  for running the tests12:04
Mirvjgdx: usually you can think of dh_auto_build as "make" and dh_auto_test as "make check", but there might be more to it12:04
Mirvespecially as build system golang is used12:04
jgdxMirv, so it's substantially different from my running $ bzr bd12:06
Mirvjgdx: no, not of couse since bzr bd runs the debian packaging so it's exactly the same. then the differences only come down to system environment between builders (only install compiler and minimum amount of build dependencies) and your machine (full desktop machine)12:08
alexabreutrainguards could you publish silo 29? I am not authorized bc of package changes12:09
jgdxMirv, okay, thx. Will set up a lxc and do some digging12:09
ogra_jibel: i just uploaded http://paste.ubuntu.com/16188132/ to the overlay ... tell me if there are still issues with the next build12:09
jgdxs/lxc/schroot12:10
Mirvalexabreu: done.12:13
alexabreuMirv, thank you :)12:13
=== _salem is now known as salem_
jgdxMirv, u-p builds fine on a minimal xenial chroot. Is this infra?13:04
jgdxtrainguards: hey, could the build env in silo 58 be bad? Is there a way to reset it?13:22
dobeyjgdx: does your chroot use -proposed?13:26
dobeyjgdx: and why does it fail on all archs on vivid?13:27
jgdxdobey, hey i'm asking the questions here13:28
jgdxchroot does not use proposed13:28
jgdxdobey, that's what we're trying to figure out13:28
dobeyjgdx: silo has proposed, and the stable-phone-ovrlay ppa13:29
dobeybut i'm not sure proposed is the issue here, given all the archs fail on vivid13:29
jgdxdobey, on vivid there's that funky cp: cannot stat ‘debian/tmp/=>’: No such file or directory error13:30
jgdxI'm building a vivid chroot to repro13:30
dobeyjgdx: oh that looks like a bug in debian/*.install or something13:31
dobeyor maybe in debian/rules13:31
om26ertrainguards Hi! I see there are 147 updates since last upgrade. Can we make an exception and publish a new image today ?13:39
om26er(rc-proposed)13:40
charlesondra, any news on https://trello.com/c/gzf3hdwh/3111-1299-ubuntu-landing-035-indicator-display-charles-ondra ?13:41
jibelom26er, it doesn't build and don't want to build one before silo 58 lands13:43
om26erjibel, silo 58, hmm, I have that on my desktop as well. Probably related to Libertine ?13:45
jibelom26er, I doubt you have silo 58 on your desktop it fails to build.13:45
jibelom26er, https://requests.ci-train.ubuntu.com/#/silo/05813:46
om26erjibel, I added it a week ago following[1] and at that time it had libertine in it. I see now it has ubuntu-push.[1] https://wiki.ubuntu.com/Touch/Libertine13:47
om26erChrisTownsend, ^you might want to update https://wiki.ubuntu.com/Touch/Libertine the ppa part is obsolete now.13:49
ChrisTownsendom26er: Ok, thanks for the reminder.13:50
jgdxdobey, right, how would I create a proposed chroot? I can't get the build to fail on vivid+overlay13:53
dobeyjgdx: just edit /etc/apt/sources.list and for all the xenial-updates entries, copy them and replace xenial-updates with xenial-proposed14:01
Mirvjgdx: 058 seems normal by all accounts. if you were testing xenial, note that amd64 did pass but armhf and i386 failed (could be retried). if you were testing vivid-proposed, then that's still a big question mark.14:02
Mirvom26er: there's a problem with image build, that's why there are many updates since last image build that was last week14:02
om26erMirv, thanks, I will wait for things to settle, for now 'apt upgrade' will do :)14:03
Mirvjgdx: also the same failures happened in my test silo 02314:05
Mirvjgdx: ok you should probably really consult the packager of the package but if you take the two changes at the bottom: https://code.launchpad.net/~timo-jyrinki/ubuntu-push/test_ignore_file_removal/+merge/293511 (.install files) also vivid seems to compile. it seems the usr/bin/ubuntu-push and usr/bin/dev files are already there so they can be just "included". I don't know if they the intended symlinks14:15
Mirvor what, and what exactly got broken but the ">= /usr/bin/..." parts seem unneeded.14:15
Mirvjgdx: and the xenial errors seem a bit flaky at least.14:15
jgdxMirv, they are flaky and I've asked Samuele to look at why those test fail like that. IIRC he fixed them once, maybe he can fix them twice.14:16
jgdxMirv, and as for consulting the packager, I'm trying but no one's answering right now.14:17
slangasekjibel: sorry, you highlighted me but I don't have the context. what do you need? "change password file"?14:18
Mirvjgdx: ok, then just take the two .install files changes from my MP and include them in your silo, build and check the end results after a hopefully successful build(s)14:18
jibelslangasek, that's fine, ogra_ took care of it. touch image faied to build because the password file changed.14:18
slangaseko14:18
slangasekok14:18
jgdxMirv, okay, let's try that14:21
jgdxMirv, from r430 and r429, right?14:23
Mirvjgdx: yes, but maybe easier just staring at the bottom of the MP page and apply manually just those two14:23
Mirvand ignore the debian/rules changes14:24
charlesondra, any news on https://trello.com/c/gzf3hdwh/3111-1299-ubuntu-landing-035-indicator-display-charles-ondra ?14:24
jgdxMirv, yeah, will do it manually14:25
dobeyjgdx: you just need to remove the "=>" in the .install files14:25
dobeyjgdx: i think you still want "dev" to be installed as ubuntu-push-dev-server and "ubuntu-push" to be installed as /usr/lib/ubuntu-push-client/ubuntu-push-client14:25
dobeyerr14:26
dobeyMirv: ^^14:26
Mirvdobey: the thing is that something is already installed as those two files even after removing the >=, so maybe it's the build environment handling that manually. I'm just debugging by staring at vivid PPA error messages.14:27
dobeyMirv: that MP of yours is just all wrong :)14:27
Mirvdobey: it's not MP but a hack testing ground14:27
Mirvto get vivid building14:27
Mirvdobey: I was wondering what was wrong with the ">=" syntax and tested making the symlink manually, then noticed I couldn't create symlinks because the files were already there, etc14:28
dobeyi don't understand why => is there at all14:28
Mirvdobey: and source/format is supposed to not be included in train packages so that was needed to be removed too to fix the earlier build failure we got before getting these14:29
Mirvdobey: yes, and apparently the packager is not reachable for comment right now14:29
dobeythe source/format is fine14:29
Mirvdobey: it's not, since it failed to build before removing it due to train failing to create the source package14:29
Mirvhttps://ci-train.ubuntu.com/job/ubuntu-landing-058-1-build/54/console14:30
dobeyMirv: but it's impossible to see the output file from /tmp/ in jenkins14:31
dobeyMirv: that sounds to me like the source/format is a scapegoat :)14:32
fgintherrenatu, https://code.launchpad.net/~renatofilho/indicator-datetime/notify-missing-alarm/+merge/292270 is still failing after adding the overlay ppa. However, this project is being built against wily, should it be vivid instead?14:33
Mirvdobey: if you want to delay the release further feel free to uncommit the source/format removal and find the real cause for train not being able to upload packages to the PPA :)14:34
Mirvdobey: sure I'd be interested in knowing what an earth suddenly start the complaints about .bzrignore/.gitignore under a subdir while it just used to work before14:34
renatucharles, tedg ^^^14:34
dobeyMirv: well when did it get added? there have clearly been releases of ubuntu-push before14:34
renatufginther, I am not the maintainer of this project,  but  I believe that charles or tedg  cal answer that14:35
Mirvdobey: there's 0 delta between successful March release of ubuntu-push and this that failed today in multiple ways, including train not being able to build a source package and install phase failing on vivid14:35
jgdxMirv, should I continue with the changes to .install files? Do we know what creates the correctly named binaries?14:42
Mirvjgdx: I'd build them, install the vivid versions and check manually what the ls -l /usr/bin/ubuntu-push is14:44
Mirvjgdx: no idea, it's not the packaging doing anything, it's the ubuntu-push's own build system14:44
Mirvwhen the packaging comes into the picture the files are already there14:45
Mirv(...nowadays?)14:45
jgdxokay :)14:45
Mirvjgdx: the whole problem set of ubuntu-push you've faced today is... weird. since vivid is stale, nothing changes there and now multiple problems. I could see train having changed mandating the source build issues, but no idea about this last problem.14:46
jgdxMirv, go/nogo? https://code.launchpad.net/~jonas-drange/ubuntu-push/fix-dot-install/+merge/29353814:48
Mirvjgdx: the automatic branch already has the format removal, otherwise ok14:49
Mirvand probably it doesn't hurt14:49
jgdxmerges cleanly locally, so let's try14:49
Mirvok14:49
jgdxMirv, thanks for everything so far. Goes for you too dobey14:50
jgdxMirv, built on vivid now14:56
jgdxand on xenial, at least for amd6414:56
dobey:(14:57
dobeythe .install changes are wrong14:58
dobeyjgdx: maybe it needs to be "debian/tmp/usr/bin/ubuntu-push /usr/lib/ubuntu-push-client/ubuntu-push-client"15:03
dobeyand similarly for the dev thing15:03
dobey"debian/tmp/dev /usr/bin/ubuntu-push-dev-server"15:03
jgdxdobey, so the binary's going to be installed incorrectly/not at all15:06
dobeyjgdx: incorrectly according to that MP15:06
jgdxconfirmed, okay, let's try dropping the => ?15:10
=== chihchunl is now known as chihchun
dobeyjgdx: that might work, but i'm not entirely sure15:10
dobeyif not, i think you need to prefix each line with debian/tmp/15:11
jgdxdobey, it moves the binary to the correct folder, but does not rename it15:22
dobeyah, maybe that's why the => was needed. hmm15:24
dobeymaybe it would be better to mv things in debian/rules instead then. hmm15:25
=== Trevinho_ is now known as Trevinho
pmcgowanjgdx, dobey you guys have the push thing under control?15:47
jibelslangasek, can you disable automated builds of ubuntu-touch/vivid ? Next image will be broken.17:15
jibelpmcgowan, ^ until we have a fix for ubuntu-push17:15
pmcgowanindeed17:15
pmcgowanjibel, no solution yet I guess then17:15
jibelpmcgowan, there is a solution, but there are still issues with the packaging in vivid17:16
pmcgowanjibel, ?17:16
jibelpmcgowan, whne I install the silo I've files installed under /usr/lib/${DEB_HOST_MULTIARCH}/ubuntu-app-launch/push-helper17:17
jibelit doesn't look right17:17
jibelthis is the whole name of the directory, like a variable substitution didn't happen17:18
pmcgowanthats odd and seem unrelated to the changes17:18
jibelpmcgowan, I compared to previous version and it is definitely not there.17:19
jibelso something changed in the build17:19
pmcgowanmaybe kenvandine can look at it17:21
kenvandineodd17:21
kenvandinethat is a common convention, and should work17:22
kenvandineoh... wait is that in the .install file?17:22
kenvandinejibel, ^^17:22
kenvandinei guess that's before the .install actually17:23
kenvandinesomething is setting the install path without evaluating the variable17:23
kenvandinejibel, got a link to the build?17:24
pmcgowanthis? https://requests.ci-train.ubuntu.com/#/ticket/134317:24
jibelkenvandine, this silo https://requests.ci-train.ubuntu.com/#/silo/05817:26
kenvandine-rw-r--r-- root/root        47 2016-05-02 15:20 ./usr/lib/${DEB_HOST_MULTIARCH}/ubuntu-app-launch/push-helper/exec-tool17:26
kenvandineugh17:26
slangasekjibel: ubuntu-touch/vivid> disabled... though that really shouldn't be necessary?17:32
dobeyjibel: next image will be broken how?17:34
dobeyjibel: it's already broken in the overlay ppa?17:34
jibeldobey, yes if you update all the packages. dbus flooded with NameOwnerChanged signals17:35
jibelthe device becomes unresponsive, and lot a things start crashing (scopes, unity8, ...)17:36
jibelslangasek, thanks17:36
dobeyjibel: all signals for the same dbus name?17:36
jibeldobey, this is bug 157518417:36
ubot5bug 1575184 in Ubuntu Push Notifications "ubuntu-push is flooding dbus with NameOwnerChanged signals" [High,In progress] https://launchpad.net/bugs/157518417:36
slangasekjibel: so why turning the build on and off instead of just letting it build and be broken?  We're not hurting for build capacity, and broken images should be trapped farther down the line because we don't always know in advance they're broken17:37
dobeyoh hmm17:37
jibelslangasek, it'll also break CI17:37
jibeland be a major problem for everyone trying to land something17:38
slangasekwhy does the CI depend on the latest image being good, instead of the CI *blocking* an image that isn't good?17:38
dobeywell the package shouldn't have landed17:38
jibelright, and we have nothing to block an rc-proposed image17:39
dobeyso i guess the real question is, why did QA not block it?17:39
jibelexactly, I'll have an answer.17:42
jibelthe other option is to revert nm 1.2 ...17:44
ogra_if your build fails it wont end up in rc-proposed17:49
ogra_(obviously)17:50
dobeyuhm17:52
dobeyoh, nm 1.2 is what broke the world17:52
dobeyerr, or gdbus17:55
ogra_is that due to the missing changes in livecd-rootfs ?17:55
ogra_(the dropping of the pkcon and NM hacks)17:56
dobeynot sure what hack you mean, but i don't think so17:57
dobeyappears dbus-glib was happy with lowercase "state" but gdbus (which nm 1.2 uses) isn't17:58
dobeybut that doesn't explain the build issues17:58
ogra_dobey: there are some hacks in livecd-rootfs that put a policykit file in place for NM and also mangle NMs dbus config18:12
ogra_they were supposed to be removed when the new nm lands18:12
dobeyogra_: ah. that could be related, but if the string case on the property matters here, i guess it won't fix things18:13
dobeyogra_: since new nm is landed though, perhaps we could first drop those bits and test to see if it helps?18:13
ogra_http://bazaar.launchpad.net/~ubuntu-core-dev/livecd-rootfs/trunk/view/head:/live-build/ubuntu-touch/hooks/45-add-sudo-group-nm.chroot18:14
dobeyhmm, i guess not having those changes won't fix the issue at hand18:15
morphisogra_: the property case is relevant18:29
morphisthe integration of gdbus in nm got more strict18:29
morphisjgdx: do you got the silo setup for the ubuntu-push fix?18:39
jgdxmorphis, yeah, but it's not building18:40
morphiswhy that?18:41
jgdxdh-exec fails to move a file on vivid18:42
morphisjgdx: in the silo it looks like it has builded18:43
jgdxmorphis, it built when we dropped the dh_exec rename, but we then had binaries in the wrong locations18:44
jgdxwith the wrong names18:44
morphisjgdx: any idea why this all happened? how did you land ubuntu-push before?18:44
jgdxmorphis, absolutely no idea and when we landed u-p in march there was nothing to it18:45
pmcgowanmorphis, jgdx it worked when built locally by kenvandine and dobey18:45
pmcgowanseems something wrong in the overlay?18:45
jgdxpmcgowan, I've built u-p locally in every configuration (vivid-proposed, vivid, xenial, xenial-proposed) without issue18:45
jgdxi've built it on vivid+overlay too18:45
jgdxmaybe the train's outta whack18:45
kenvandinei'm working on setting up sbuild for vivid-armhf + overlay18:46
kenvandineto try it in sbuild18:46
jgdxkenvandine, thx18:46
pmcgowanjgdx, why did you need to change the install file?18:47
dobeypmcgowan: no, not the overlay18:47
pmcgowandobey, oh sorry whats the theory?18:48
jgdxpmcgowan, to test a theory of Mirv's18:48
kenvandinepmcgowan, i don't think we have a theory yet18:49
dobeypmcgowan: solar flares?18:49
kenvandinei'm trying to match the build env of the ppa with sbuild18:49
kenvandineto see18:49
jgdxkenvandine, here's the vivid build failure from 2 secs ago: https://launchpadlibrarian.net/257565248/buildlog_ubuntu-vivid-amd64.ubuntu-push_0.68+15.04.20160502.4-0ubuntu1_BUILDING.txt.gz18:49
dobeycjwatson: ^^ did anything change in launchpad builder configs recently that would screw with dh-exec on vivid silo builds perhaps?18:49
kenvandinei haven't seen that failure yet18:49
jgdxcp -a debian/tmp/=> debian/ubuntu-push-client//usr/lib/ubuntu-push-client/ubuntu-push-client/18:50
dobeyjgdx: you dropped the dotinstall mp?18:50
jgdxdobey, yeah, didn't get anywhere18:50
kenvandinejgdx, earlier the package was building in the ppa just installing the helper in the wrong path18:50
dobeyyeah, when i built locally i realized that was unrelated to whatever is going on18:50
jgdxkenvandine, not just the helper, the u-p binary as well18:50
dobeyand since we shouldn't land things direct to trunk there, figured i'd comment and disapprove it :)18:51
kenvandineso this isn't right? /usr/lib/ubuntu-push-client/ubuntu-push-client/ubuntu-push18:51
dobeykenvandine: no18:51
jgdxno, needs to be …/ubuntu-push-client18:51
kenvandineok, i'm not even thinking about that yet18:51
kenvandinethis is what has me freaking out /usr/lib/${DEB_HOST_MULTIARCH}/ubuntu-app-launch/push-helper/exec-tool18:51
dobeykenvandine: don't freak out about that18:52
dobeykenvandine: it's the same issue18:52
kenvandinelets hope :)18:52
dobeyie, a problem with dh-exec18:52
kenvandine./usr/lib/ubuntu-push-client/ubuntu-push-client18:52
kenvandineis what i get locally18:52
kenvandineso both are good locally18:52
dobeyyes18:52
kenvandinebut dh-exec with sbuild for arch=armhf18:53
kenvandinei think specifically18:53
dobeyno18:53
dobeyit's failing on all archs18:53
kenvandinethe amd64 build was fine18:53
dobeyno18:53
kenvandinein the ppa18:53
jgdxon vivid all arch, Ken18:53
dobeythe amd64 build is the fialure that jgdx just linked :)18:53
dobeyfailure18:54
kenvandineoh... right18:54
kenvandineignore me :)18:54
kenvandinei had downloaded the deb to check earlier18:54
dobeyyeah, that was when the hack MP was also in the silo, and had the wrong paths18:54
jgdxso reading [1] makes me think that the .install file is altered or misinterpreted somehow [1] http://manpages.ubuntu.com/manpages/trusty/man1/dh-exec-install.1.html18:54
jgdxcp -a debian/tmp/=> should really be cp -a debian/temp/ubuntu-push18:55
jgdxs/temp/tmp18:55
dobeywell, and usr/bin/ubuntu-push18:56
dobeynot just ubuntu-push18:56
jgdxright18:56
dobeythe issue is that it seems dh-exec is not being run at all18:56
dobeybut why, i have no idea18:56
jgdxaccording to the doc, this is dh-exec's internal implementation of => at work18:56
jgdxit uses debian/tmp as a temporary folder to do the rename18:57
jgdxso, we should try to build some deb on vivid that utilizes =>18:57
dobeyjgdx: debian/tmp/ is where files are installed to when you have multiple binary packages defined18:57
jgdxhm okay18:57
dobeyjgdx: add "export DH_VERBOSE=1" to debian/rules in a second MP, and rebuild with that, to test. should spew a lot more info in the log18:58
dobeymaybe then we can see what is (or rather, is not) happening18:59
jgdxi'm really off now, can you possibly do it?19:00
jgdxor kenvandine ^?19:00
dobeykenvandine: ^^ can you do that?19:00
kenvandinesure19:02
kenvandinedobey, jgdx: building19:09
dobeyi'm busy trying to fix purchasing stuffs :)19:09
kenvandinedobey, jgdx: i have a workaround (hack) that i think will fix it19:36
kenvandinebuilding in the ppa now19:36
dobeykenvandine: what hack?19:36
kenvandine+mkdir -p debian/tmp/usr/lib/ubuntu-push-client/19:37
kenvandine+mv debian/tmp/usr/bin/ubuntu-push debian/tmp/usr/lib/ubuntu-push-client/ubuntu-push-client19:37
kenvandinein debian/rules19:37
kenvandinethese hacks used to be pretty common back in the day :)19:37
dobeykenvandine: that doesn't fix the problem though19:37
kenvandinei think it does19:37
kenvandinethat and a change to the .install file19:37
dobeykenvandine: well, you can drop the => and just list the file, but then you have the ${DEB_HOST_MULTIARCH} issue because dh-exec isn't running19:37
kenvandineno, that still runs19:38
dobeyreally?!19:38
kenvandinejust wait 5 minutes for the ppa build :)19:39
* dobey looks for a bottle of rum and finds a barren shelf19:39
dobeykenvandine: i doubt it'll work :)19:39
kenvandineso little faith19:39
kenvandinehttps://code.launchpad.net/~ken-vandine/ubuntu-push/verbose/+merge/29356219:40
dobeyone faith is enough.19:40
kenvandinedobey, i think it worked... now we need the same fix for ubuntu-push-dev-server19:42
kenvandineit got further :)19:42
dobeywell sure it got further19:42
dobeybut i was right :)19:42
dobeycp -a ./debian/exec-tool debian/ubuntu-push-client//usr/lib/\${DEB_HOST_MULTIARCH}/ubuntu-app-launch/push-helper/19:43
dobeylet it be known that kenvandine owes me rum19:43
kenvandinewtf!19:44
kenvandinebut it was still using dh-exec19:44
kenvandinemaybe we should kill dh-exec in here :)19:45
dobeywell it's not using dh-exec, obviously19:47
dobeybut why19:47
dobeywell if golang wasn't insane, we wouldn't need dh-exec there i guess19:47
kenvandinethat was my next question... why are we using it19:48
dobeybut yeah, either need dh-exec, or scripting in override_dh_install19:48
kenvandineall my years of packaging and i've never needed it19:48
dobeykenvandine: you're used to build syztems that make sense for system integration19:48
kenvandineindeed19:48
dobeygolang is the hipster kid sitting on a front porch of an abandoned house in detroit, shouting at pigeons to get off the lawn19:49
kenvandinelol19:50
=== kalikiana_ is now known as kalikiana
=== FourDollars_ is now known as FourDollars
=== blr_ is now known as blr
cjwatsondobey: basically any time people blame the builders, they're wrong, and it's not a builder change here :)21:25
dobeycjwatson: wasn't blaming. just trying to figure wtf is going on that would cause a package with no changes to debian/ which built fine 6 weeks ago, to not build fine today21:26
cjwatsondobey: the problem is that this source package uses format 1.0, and that source format doesn't preserve the executable bit on files added by the .diff.gz.  The two possible fixes are (a) switch to source format 3.0 (quilt) or (b) add chmod +x debian/whatever.install in debian/rules before dh_install is called21:26
cjwatsondobey: I bet the previous version of the package came out as 3.0 (quilt), i.e. with a .debian.tar.gz or similar21:27
dobeyoh21:27
dobeyyeah, ok that makes sense21:27
dobeyso it's the removal of debian/source which broke it21:27
dobeykenvandine, Mirv: ^^21:27
cjwatsonit was removed?  er, yeah, that would very much do it :)21:27
cjwatsonthat sounds like pointing gun at own foot territory21:28
dobeyyeah, something about "packages in ci train shouldn't do that"21:28
cjwatsonsigh21:28
dobeywhich to me is wrong21:28
cjwatsonI agree with you; that is a ridiculous policy :)21:28
cjwatsonperfectly reasonable to use features of 3.0 (quilt), even if you aren't actually using any quilt patches21:29
dobeybut anyway, it's quite late for you, and high time for me to go to the pub :)21:29
dobeyindeed21:29
=== salem_ is now known as _salem
=== _salem is now known as salem_
=== salem_ is now known as _salem
=== _salem is now known as salem_
=== lan3y is now known as Laney
=== salem_ is now known as _salem
=== _salem is now known as salem_
=== salem_ is now known as _salem
Guest_86446Allah is doing22:56
Guest_86446sun is not doing Allah is doing22:57
Guest_86446moon is not doing Allah is doing22:57
Guest_86446stars are not doing Allah is doing23:00
Guest_86446planets are not doing Allah is doing23:00

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