[00:09] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/2106 Successfully built
[03:47] -queuebot:#ubuntu-ci-eng- jbicha, https://bileto.ubuntu.com/#/ticket/2109 Preparing packages
[03:47] -queuebot:#ubuntu-ci-eng- jbicha, https://bileto.ubuntu.com/#/ticket/2109 zesty/indicator-application: Failed to commit https://code.launchpad.net/~jbicha/indicator-application/dont-show-in-startup-applications. You must supply either a Commit Message on your MP, or a custom debian/changelog entry
[03:48] -queuebot:#ubuntu-ci-eng- jbicha, https://bileto.ubuntu.com/#/ticket/2109 Preparing packages
[04:13] -queuebot:#ubuntu-ci-eng- jbicha, https://bileto.ubuntu.com/#/ticket/2109 Pending binary packages
[04:16] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/2081 QA Signoff: Ready
[04:32] -queuebot:#ubuntu-ci-eng- jbicha, https://bileto.ubuntu.com/#/ticket/2109 Successfully built
[05:21] -queuebot:#ubuntu-ci-eng- jbicha, https://bileto.ubuntu.com/#/ticket/2109 QA Signoff: Ready
[05:30] -queuebot:#ubuntu-ci-eng- jbicha, https://bileto.ubuntu.com/#/ticket/2109 Publishing packages
[05:31] -queuebot:#ubuntu-ci-eng- jbicha, https://bileto.ubuntu.com/#/ticket/2109 Publish failed: Bad merges
[05:51] -queuebot:#ubuntu-ci-eng- jbicha, https://bileto.ubuntu.com/#/ticket/2109 Successfully built
[06:21] -queuebot:#ubuntu-ci-eng- dobey, https://bileto.ubuntu.com/#/ticket/2100
[06:21] -queuebot:#ubuntu-ci-eng- mterry, https://bileto.ubuntu.com/#/ticket/1679
[06:21] -queuebot:#ubuntu-ci-eng- alex-abreu, https://bileto.ubuntu.com/#/ticket/1640
[06:21] -queuebot:#ubuntu-ci-eng- tiagosh boiko rmescandon bfiller, https://bileto.ubuntu.com/#/ticket/1319
[06:22] -queuebot:#ubuntu-ci-eng- ltinkl, https://bileto.ubuntu.com/#/ticket/2080
[06:24] <robru> Heh
[06:41] -queuebot:#ubuntu-ci-eng- dobey, https://bileto.ubuntu.com/#/ticket/2100 Successfully built
[06:42] -queuebot:#ubuntu-ci-eng- mterry, https://bileto.ubuntu.com/#/ticket/1679 Needs rebuild due to new commits (zesty/lightdm, zesty/ubuntu-touch-session, zesty/unity8). Successfully built (vivid/gsettings-ubuntu-touch-schemas, vivid/lightdm, vivid/ubuntu-touch-session, vivid/unity8, vivid/unity8-desktop-session, xenial/gsettings-ubuntu-touch-schemas, xenial/lightdm, xenial/ubuntu-touch-session, xenial/unity8, xenial/unity8-desktop-session, zesty/gsettings-ubuntu-touch-sch
[06:42] -queuebot:#ubuntu-ci-eng- tiagosh boiko rmescandon bfiller, https://bileto.ubuntu.com/#/ticket/1319 Failed to build (vivid/messaging-app, vivid/telephony-service, xenial/telephony-service, zesty/history-service, zesty/telephony-service). Successfully built (vivid/dialer-app, vivid/history-service, vivid/telepathy-ofono, xenial/dialer-app, xenial/history-service, xenial/messaging-app, xenial/telepathy-ofono, zesty/dialer-app, zesty/messaging-app, zesty/telepathy-ofono)
[06:43] -queuebot:#ubuntu-ci-eng- alex-abreu, https://bileto.ubuntu.com/#/ticket/1640 Cancelled build (xenial/content-hub, yakkety/content-hub). Successfully built (vivid/content-hub)
[06:43] -queuebot:#ubuntu-ci-eng- marcustomlinson, https://bileto.ubuntu.com/#/ticket/2110 Preparing packages
[06:45] -queuebot:#ubuntu-ci-eng- ltinkl, https://bileto.ubuntu.com/#/ticket/2080 Successfully built
[06:46] -queuebot:#ubuntu-ci-eng- marcustomlinson, https://bileto.ubuntu.com/#/ticket/2110 zesty/unity-scopes-shell: Failed to branch https://code.launchpad.net/~mterry/unity-scopes-shell/snap-root
[06:49] <marcustomlinson> trainguards: help ^ "zesty/unity-scopes-shell: Failed to branch https://code.launchpad.net/~mterry/unity-scopes-shell/snap-root"
[06:50] <robru> marcustomlinson: did you read the log?
[06:50] <marcustomlinson> robru: yeah, reading it again
[06:51] -queuebot:#ubuntu-ci-eng- marcustomlinson, https://bileto.ubuntu.com/#/ticket/2110 Ready to build
[06:51] <robru> marcustomlinson: actually hmm. The log says it's not a branch, but it loads in the browser...
[06:51] <marcustomlinson> robru: yeah
[06:52] <robru> marcustomlinson: i dunno, try it again
[06:53] <marcustomlinson> k :)
[06:53] -queuebot:#ubuntu-ci-eng- marcustomlinson, https://bileto.ubuntu.com/#/ticket/2110 Preparing packages
[06:54] <marcustomlinson> robru: ok seems to be working now
[06:55] <robru> marcustomlinson: race condition maybe? Is the branch super new?
[06:55] <marcustomlinson> robru: no
[06:55] <robru> marcustomlinson: weird, i dunno. I guess transient lp issue
[06:56] <marcustomlinson> robru: yeah np, thanks :)
[06:56] <robru> marcustomlinson: you're welcome!
[07:12] -queuebot:#ubuntu-ci-eng- marcustomlinson, https://bileto.ubuntu.com/#/ticket/2110 Currently building (vivid/unity-scopes-api, vivid/unity-scopes-shell, xenial/unity-scopes-shell, zesty/unity-scopes-api, zesty/unity-scopes-shell). Failed to build (xenial/unity-scopes-api)
[07:32] -queuebot:#ubuntu-ci-eng- marcustomlinson, https://bileto.ubuntu.com/#/ticket/2110 Failed to build (xenial/unity-scopes-api, zesty/unity-scopes-api). Pending binary packages (vivid/unity-scopes-shell, xenial/unity-scopes-shell, zesty/unity-scopes-shell). Uploading build (vivid/unity-scopes-api)
[07:39] <oSoMoN> sil2100, jibel, good morning! can the status of https://bileto.ubuntu.com/#/ticket/2107 be overridden so that it gets into QA’s queue? it’s fixing the landing of silo 1919 where the xenial+overlay packages were dropped
[07:41] <sil2100> oSoMoN: switched the silo to xenial-only
[07:41] <sil2100> Since zesty is not needed there
[07:42] <sil2100> oSoMoN: I guess we can just publish this
[07:42] -queuebot:#ubuntu-ci-eng- oSoMoN, https://bileto.ubuntu.com/#/ticket/2107 QA Signoff: Required
[07:42] <oSoMoN> sil2100, wouldn’t that make it a candidate for SRU, instead of targetting the stable overlay PPA?
[07:43] <sil2100> No, you can then switch the target to the overlay
[07:44] <sil2100> Single landings have a target field, you can decide whether to SRU or go to the overlay
[07:44] <sil2100> I guess this was already tested for xenial when davmor2 was signing off the original silo
[07:45] <sil2100> Publishing
[07:46] <oSoMoN> sil2100, thanks
[07:46] <oSoMoN> I hadn’t noticed the "Destination" field, it’s quite handy
[07:46] -queuebot:#ubuntu-ci-eng- oSoMoN, https://bileto.ubuntu.com/#/ticket/2107 Publishing packages
[07:52] -queuebot:#ubuntu-ci-eng- marcustomlinson, https://bileto.ubuntu.com/#/ticket/2110 Failed to build (xenial/unity-scopes-api, zesty/unity-scopes-api). Pending binary packages (vivid/unity-scopes-api, vivid/unity-scopes-shell, xenial/unity-scopes-shell, zesty/unity-scopes-shell)
[08:07] -queuebot:#ubuntu-ci-eng- oSoMoN, https://bileto.ubuntu.com/#/ticket/2107 Release pocket
[08:32] -queuebot:#ubuntu-ci-eng- marcustomlinson, https://bileto.ubuntu.com/#/ticket/2110 Failed to build (xenial/unity-scopes-api, zesty/unity-scopes-api). Successfully built (vivid/unity-scopes-api, vivid/unity-scopes-shell, xenial/unity-scopes-shell, zesty/unity-scopes-shell)
[09:16] -queuebot:#ubuntu-ci-eng- oSoMoN, https://bileto.ubuntu.com/#/ticket/2111 Preparing packages
[09:33] -queuebot:#ubuntu-ci-eng- oSoMoN, https://bileto.ubuntu.com/#/ticket/2111 Pending binary packages
[09:52] -queuebot:#ubuntu-ci-eng- oSoMoN, https://bileto.ubuntu.com/#/ticket/2111 Successfully built
[10:24] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/2106 Preparing packages
[10:33] -queuebot:#ubuntu-ci-eng- jbicha, https://bileto.ubuntu.com/#/ticket/2109 Publishing packages
[10:34] -queuebot:#ubuntu-ci-eng- jbicha, https://bileto.ubuntu.com/#/ticket/2109 Publish failed: Bad merges
[10:36] <jbicha> good morning, could I get a review of https://code.launchpad.net/~jbicha/indicator-application/dont-show-in-startup-applications/+merge/309526
[10:49] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/2106 Successfully built
[10:51] -queuebot:#ubuntu-ci-eng- jbicha, https://bileto.ubuntu.com/#/ticket/2109 Successfully built
[11:27] <davmor2> sil2100: have you not added zesty to the phablet-tools ppa yet?
[11:40] -queuebot:#ubuntu-ci-eng- jgdx, https://bileto.ubuntu.com/#/ticket/2066 Publishing packages
[11:45] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/2106 Preparing packages
[11:45] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/2103 Needs rebuild due to new commits (zesty/unity8). Successfully built (vivid/qmenumodel, vivid/ubuntu-settings-components, vivid/unity8, xenial/qmenumodel, xenial/ubuntu-settings-components, xenial/unity8, zesty/qmenumodel, zesty/ubuntu-settings-components)
[11:48] -queuebot:#ubuntu-ci-eng- jgdx, https://bileto.ubuntu.com/#/ticket/2066 Proposed pocket (zesty/ubuntu-system-settings). Release pocket (vivid/ubuntu-system-settings, xenial/ubuntu-system-settings)
[12:01] -queuebot:#ubuntu-ci-eng- kenvandine jgdx, https://bileto.ubuntu.com/#/ticket/2078 Destination version missing from changelog (zesty/ubuntu-system-settings). Successfully built (vivid/ubuntu-system-settings, xenial/ubuntu-system-settings)
[12:04] -queuebot:#ubuntu-ci-eng- jgdx, https://bileto.ubuntu.com/#/ticket/1721 Destination version missing from changelog (zesty/ubuntu-system-settings). Failed to build (vivid/ubuntu-system-settings). Needs rebuild due to new commits (zesty/ubuntu-settings-components). Successfully built (vivid/ubuntu-settings-components, xenial/ubuntu-settings-components, xenial/ubuntu-system-settings)
[12:06] -queuebot:#ubuntu-ci-eng- kenvandine jgdx, https://bileto.ubuntu.com/#/ticket/2078 Preparing packages
[12:19] -queuebot:#ubuntu-ci-eng- Cimi, https://bileto.ubuntu.com/#/ticket/2050 Preparing packages
[12:28] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/2106 Successfully built
[12:42] -queuebot:#ubuntu-ci-eng- tiagosh boiko rmescandon bfiller, https://bileto.ubuntu.com/#/ticket/1319 Failed to build (vivid/messaging-app, vivid/telephony-service, xenial/telephony-service, zesty/history-service, zesty/telephony-service). Needs rebuild due to new commits (zesty/telepathy-ofono). Successfully built (vivid/dialer-app, vivid/history-service, vivid/telepathy-ofono, xenial/dialer-app, xenial/history-service, xenial/messaging-app, xenial/telepathy-ofono, zest
[12:55] -queuebot:#ubuntu-ci-eng- Cimi, https://bileto.ubuntu.com/#/ticket/2050 Successfully built
[13:01] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/2106 Preparing packages
[13:01] -queuebot:#ubuntu-ci-eng- kenvandine jgdx, https://bileto.ubuntu.com/#/ticket/2078 Destination version missing from changelog (zesty/ubuntu-system-settings). Successfully built (vivid/ubuntu-system-settings, xenial/ubuntu-system-settings)
[13:05] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/2103 Successfully built
[13:25] <Elleo> trainguards: are there any known issues with autopkg tests on xenial? the url-dispatcher tests timed out on 3 architectures on xenial for this silo: https://bileto.ubuntu.com/#/ticket/2033
[13:30] <sil2100> Elleo: I don't know anything about the machines having some issues per se, but britney is under heavy load since yesterday basically as far as the number of running tests is concernet
[13:30] <sil2100> *concerned
[13:30] <sil2100> But not sure if that could cause such timeout issues
[13:32] -queuebot:#ubuntu-ci-eng- andreas-pokorny, https://bileto.ubuntu.com/#/ticket/2084 Publishing packages
[13:33] <Elleo> sil2100: ah, I guess that might be it; nothing in the branch being tested should have an effect on the url dispatcher tests, and they pass on other architectures/distributions
[13:33] <Elleo> sil2100: plus they took a really long time to finish, they started running last night :/
[13:34] <Elleo> sil2100: is it worth kicking those tests off again now?
[13:42] <sil2100> I can retry them, but not sure when they get to be finished actually
[13:42] <sil2100> I pushed a new package to -proposed yesterday and still didn't get all tests run
[13:44] <Elleo> perhaps we need some sort of queue system for autopkg tests, so the system load remains reasonable when there's a lot of tests ready to run, instead of running them all concurrently
[13:45] -queuebot:#ubuntu-ci-eng- andreas-pokorny, https://bileto.ubuntu.com/#/ticket/2084 Release pocket
[13:57] <dobey> Elleo: there is a queue
[13:58] <Elleo> oh, maybe it needs tweaking then if its getting into a situation with such heavy load?
[13:59] <dobey> i don't know what the host hardware is like, but afaik the tests are run in virtualization. i guess on some archs that can end up with resource conflicts, but unless the host is getting destroyed, things should be fine
[13:59] -queuebot:#ubuntu-ci-eng- tiagosh boiko rmescandon bfiller, https://bileto.ubuntu.com/#/ticket/1319 Preparing packages
[14:00] <dobey> but yes, the infrastructure has always had issues meeting demand
[14:00] <dobey> you'd need to talk to pitti i guess
[14:00] <kenvandine> rvr, silo 2066 which was published a little bit ago has been switched back to ready for QA in bileto
[14:00] <kenvandine> rvr, i suspect maybe because of britney?
[14:01] <rvr> kenvandine: Let me check
[14:01] <dobey> i guess if url-dispatcher tests are timing out there are some serious issues, possibly in the tests themselves though
[14:01] <kenvandine> rvr, it must have been qa approved and still had tests running
[14:02] <rvr> Yeah, it was approved 2016-10-26 17:43:40 +0100 (davmor2) qa_signoff: Approved
[14:03] <rvr> davmor2: Can you set https://bileto.ubuntu.com/#/ticket/2066 again as approved?
[14:04] -queuebot:#ubuntu-ci-eng- pitti Trevinho, https://bileto.ubuntu.com/#/ticket/2101 Release pocket
[14:04] <davmor2> done
[14:05] -queuebot:#ubuntu-ci-eng- jgdx, https://bileto.ubuntu.com/#/ticket/2066 QA Signoff: Approved
[14:09] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/2106 Successfully built
[14:14] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/1951 Needs rebuild due to new commits
[14:22] -queuebot:#ubuntu-ci-eng- tiagosh boiko rmescandon bfiller, https://bileto.ubuntu.com/#/ticket/1319 Failed to build (vivid/messaging-app, vivid/telephony-service, xenial/telepathy-ofono, xenial/telephony-service, zesty/history-service, zesty/telephony-service). Successfully built (vivid/dialer-app, vivid/history-service, vivid/telepathy-ofono, xenial/dialer-app, xenial/history-service, xenial/messaging-app, zesty/dialer-app, zesty/messaging-app, zesty/telepathy-ofono)
[14:35] -queuebot:#ubuntu-ci-eng- andyrock, https://bileto.ubuntu.com/#/ticket/2112 Dependency wait (vivid/unity8, xenial/unity8, zesty/unity8). Successfully built (vivid/unity-api, xenial/unity-api, zesty/unity-api)
[14:39] -queuebot:#ubuntu-ci-eng- bzoltan, https://bileto.ubuntu.com/#/ticket/2069 QA Signoff: Approved
[14:54] <AlbertA_> cjwatson: I'm getting this failure trying to build a snap: https://launchpadlibrarian.net/291187751/buildlog_snap_ubuntu_yakkety_arm64_mir-kiosk_BUILDING.txt.gz
[15:14] -queuebot:#ubuntu-ci-eng- andyrock, https://bileto.ubuntu.com/#/ticket/2112 Successfully built
[15:14] <AlbertA_> sil2100: Would you know who can fix such issues like above ^
[15:14] -queuebot:#ubuntu-ci-eng- dobey, https://bileto.ubuntu.com/#/ticket/2113 Successfully built
[15:30] -queuebot:#ubuntu-ci-eng- pete-woods, https://bileto.ubuntu.com/#/ticket/2073 Preparing packages
[15:44] -queuebot:#ubuntu-ci-eng- alan-griffiths, https://bileto.ubuntu.com/#/ticket/2114 Preparing packages
[15:45] -queuebot:#ubuntu-ci-eng- alan-griffiths, https://bileto.ubuntu.com/#/ticket/2114 zesty/miral: Failed to commit https://code.launchpad.net/~alan-griffiths/miral/0.3. You must supply either a Commit Message on your MP, or a custom debian/changelog entry
[15:47] -queuebot:#ubuntu-ci-eng- alan-griffiths, https://bileto.ubuntu.com/#/ticket/2114 Preparing packages
[15:56] -queuebot:#ubuntu-ci-eng- pete-woods, https://bileto.ubuntu.com/#/ticket/2073 Failed to build (xenial/indicator-network, zesty/indicator-network). Pending binary packages (vivid/indicator-network). Successfully built (vivid/gmenuharness, xenial/gmenuharness, zesty/gmenuharness)
[15:56] -queuebot:#ubuntu-ci-eng- alan-griffiths, https://bileto.ubuntu.com/#/ticket/2114 Failed to build
[15:58] -queuebot:#ubuntu-ci-eng- alan-griffiths, https://bileto.ubuntu.com/#/ticket/2114 Preparing packages
[16:03] -queuebot:#ubuntu-ci-eng- alan-griffiths, https://bileto.ubuntu.com/#/ticket/2115 Preparing packages
[16:16] -queuebot:#ubuntu-ci-eng- pete-woods, https://bileto.ubuntu.com/#/ticket/2073 Failed to build (xenial/indicator-network, zesty/indicator-network). Successfully built (vivid/gmenuharness, vivid/indicator-network, xenial/gmenuharness, zesty/gmenuharness)
[16:17] -queuebot:#ubuntu-ci-eng- alan_g, https://bileto.ubuntu.com/#/ticket/2115 Pending binary packages
[16:27] -queuebot:#ubuntu-ci-eng- pete-woods, https://bileto.ubuntu.com/#/ticket/2073 Preparing packages
[16:30] -queuebot:#ubuntu-ci-eng- pete-woods, https://bileto.ubuntu.com/#/ticket/2073 xenial/gmenuharness: debdiff failed: see log for details
[16:36] -queuebot:#ubuntu-ci-eng- pete-woods, https://bileto.ubuntu.com/#/ticket/2073 Failed to build (xenial/indicator-network, zesty/indicator-network). Pending binary packages (vivid/gmenuharness, zesty/gmenuharness). Successfully built (vivid/indicator-network). Uploading build (xenial/gmenuharness)
[16:37] -queuebot:#ubuntu-ci-eng- alan_g, https://bileto.ubuntu.com/#/ticket/2115 Successfully built
[16:42] <jbicha> trainguards: could I get a review of https://code.launchpad.net/~jbicha/indicator-application/dont-show-in-startup-applications/+merge/309526
[16:43] <robru> jbicha: Hmmmmmmm? I don't know anything about indicators. Surely you want an indicator developer?
[16:45] <jbicha> robru: who do you recommend I ping then?
[16:45] <dobey> hmm i don't know if we land that via ci train anyway
[16:46] <jbicha> also, I'd like to get this fix into yakkety and xenial for regular Desktop users; what's the procedure for that?
[16:46] <dobey> tedg: ^^ how do indicator-application things get merged?
[16:47] <robru> jbicha: https://launchpad.net/~indicator-applet-developers/+members#active I'd look for one of the admins, indeed tedg should be around
[16:47] <jbicha> ok, he was pinged twice so I'll wait :)
[16:49] <robru> jbicha: if you want a yakkety and xenial sru you need a separate ticket for each, the current machinery for targeting multiple series hard-codes the overlay ppa
[16:49] <dobey> he might be gone already. he said he had to leave early today, so i think he's taking a half day
[16:50] <jbicha> robru: ok I see now, thanks
[16:51] <dobey> jbicha, robru: well, that's not entirely true
[16:51] <jbicha> except I'm confused about how xenial works
[16:51] <robru> dobey: jbicha: indicator-application was released with bileto just once before https://code.launchpad.net/~ted/indicator-application/systemd-unit/+merge/300336
[16:51] <dobey> a couple times, yeah
[16:52] <dobey> yakkety is the odd man out now, since we don't have any way to do z+y+x in ci train in a single ticket
[16:53] <robru> jbicha: as far as bileto is concerned all you need is to have a different target "trunk" for each series. Your MPs can't all target same series because the generated changelogs will conflict
[16:53] <robru> dobey: ci train? What's that? :-P
[16:53] <dobey> robru: it's missing a car
[16:54] <jbicha> hmm, I think we'd need someone on the indicator team to create those branches then
[16:54] <robru> I could add z+y+x if you felt it would be useful but it would be hardcoded as zesty with yakkety overlay and xenial overlay, it wouldn't do srus
[16:55] <dobey> robru: well, the binaries can be copied from overlays to y-proposed and x-proposed for the updates
[16:55] <jbicha> I'm concerned about version numbering, it wouldn't be right for yakkety to have a later/higher version number than zesty…
[16:55] -queuebot:#ubuntu-ci-eng- pete-woods, https://bileto.ubuntu.com/#/ticket/2073 Failed to build (xenial/indicator-network, zesty/indicator-network). Pending binary packages (vivid/gmenuharness, xenial/gmenuharness, zesty/gmenuharness). Successfully built (vivid/indicator-network)
[16:55] <dobey> because even when not landing to ovleray the PPA still gets built against it anyway no?
[16:56] <robru> dobey: no i fixed that with ephemerals, it only adds overlay when the target is overlay
[16:56] <dobey> well, when /any/ target is overlay
[16:57] <dobey> since that can't be speified per series
[16:57] <robru> dobey: right but building with "zesty overlay"is harmless because there's nothing in there
[16:57] <dobey> robru: right, but ideally the list of targets would be checkboxes, and i could specify overlay or not for each target
[16:58] <dobey> but alas :)
[16:58] <robru> dobey: but yeah you wouldn't want to build a xenial SRU with the overlay
[16:58] <robru> dobey: yeah it's on my list to make that more flexible.
[16:59] <dobey> and all the non-trunk branches for i-application are not up to date with reality in archive/overlay anyway, so this would be a fair bit more work than just making new MPs for the other branch targets
[16:59] <robru> dobey: snap support is the latest craze though
[17:00] <dobey> i really don't like how ted has been creating all these branches at the beginning of cycles for this stuff
[17:00] <robru> dobey: well it's trivial to copy the main trunk to a new name, just a question of who has permission to create those branches
[17:00] <dobey> especially when they never get cleaned up
[17:01] <dobey> it's a difficult mess
[17:15] -queuebot:#ubuntu-ci-eng- pete-woods, https://bileto.ubuntu.com/#/ticket/2073 Failed to build (xenial/indicator-network, zesty/indicator-network). Successfully built (vivid/gmenuharness, vivid/indicator-network, xenial/gmenuharness, zesty/gmenuharness)
[17:32] <sil2100> bzoltan, zsombi: hey, why did you start skipping arm64 tests in the UITK?
[17:32] <sil2100> bzoltan, zsombi: I see no mention of why in the changelog, no bug or anything
[17:32] <bzoltan> sil2100:  It was a temporary thing because there were some tools crashing on arm64
[17:33] -queuebot:#ubuntu-ci-eng- pete-woods, https://bileto.ubuntu.com/#/ticket/2073 Preparing packages
[17:33] <bzoltan> sil2100:  it could be turned on with the next releas
[17:36]  * tedg was at lunch
[17:39] <tedg> jbicha: Why do we need that? Why shouldn't one be able to see it in startup applications?
[17:40] <jbicha> tedg: it's long-standing practice to hide "system" services from Startup Applications
[17:40] <jbicha> because we don't want users to accidentally disable things they shouldn't
[17:40] <tedg> jbicha: Eh, okay. Seems an odd practice.
[17:43] <jbicha> it looks like we started it for precise
[17:44] <jbicha> the Startup Applications app is from gnome-session and GNOME dropped it there but we patch it back in
[17:46] <jbicha> https://blueprints.launchpad.net/ubuntu/+spec/desktop-o-startup-applications
[17:55] -queuebot:#ubuntu-ci-eng- pete-woods, https://bileto.ubuntu.com/#/ticket/2073 Failed to build (zesty/indicator-network). Pending binary packages (vivid/indicator-network, xenial/indicator-network). Successfully built (vivid/gmenuharness, xenial/gmenuharness, zesty/gmenuharness)
[18:02] -queuebot:#ubuntu-ci-eng- tiagosh boiko rmescandon bfiller, https://bileto.ubuntu.com/#/ticket/1319 Failed to build (vivid/messaging-app, vivid/telephony-service, xenial/telepathy-ofono, xenial/telephony-service, zesty/history-service, zesty/telephony-service). Needs rebuild due to new commits (zesty/messaging-app). Successfully built (vivid/dialer-app, vivid/history-service, vivid/telepathy-ofono, xenial/dialer-app, xenial/history-service, xenial/messaging-app, zesty/
[18:07] <dobey> tedg: does it really matter since it's started by systemd anyway?
[18:07] <dobey> the .desktop file in xdg autostart seems a bit superfluous no?
[18:08] <tedg> dobey: Yes, but legacy reasons... we have an xdg autostart, with an overide in the Upstart directory. Which has an override. Which has a systemd service.
[18:08] <tedg> dobey: We support ALL the init systems.
[18:08] <dobey> that is awful
[18:09] <tedg> I think once we get to systemd everywhere we can just start cleaving the other solutions.
[18:09] <dobey> so now :)
[18:09] <tedg> Not yet, U8 still isn't there.
[18:09] <dobey> eh, indicator-application doesn't work under u8 anyway does it?
[18:10] <tedg> Eh, no, but I'd be for dropping them all at once.
[18:10] <tedg> (all the indicators)
[18:15] -queuebot:#ubuntu-ci-eng- pete-woods, https://bileto.ubuntu.com/#/ticket/2073 Failed to build (zesty/indicator-network). Successfully built (vivid/gmenuharness, vivid/indicator-network, xenial/gmenuharness, xenial/indicator-network, zesty/gmenuharness)
[18:42] -queuebot:#ubuntu-ci-eng- tiagosh boiko rmescandon bfiller, https://bileto.ubuntu.com/#/ticket/1319 Failed to build (vivid/messaging-app, vivid/telephony-service, xenial/telepathy-ofono, xenial/telephony-service, zesty/telephony-service). Needs rebuild due to new commits (zesty/history-service, zesty/messaging-app). Successfully built (vivid/dialer-app, vivid/history-service, vivid/telepathy-ofono, xenial/dialer-app, xenial/history-service, xenial/messaging-app, zesty/
[19:38] <dobey> robru: btw, should bileto do a rebase and squash commits to use the commit message from the MP when merging git requests?
[19:39] <robru> dobey: Hmmmmmmm, why do you think that? Isn't it better to preserve the input commits?
[19:40] <dobey> robru: because git doesn't merge them as sub-commits like bzr does
[19:41] <dobey> so the commits get a bit messy if the branch in the MP wasn't already squashed :-/
[19:42] <robru> dobey: technically both git and bzr treat them exactly the same, it's just that bzr hides them by default and git shows them by default. If you just don't want to see them, do "git log --first-parent" or something like that
[19:43] <robru> dobey: file a bug
[19:43] <dobey> robru: that doesn't fix the display in launchpad. and no they aren't exactly the same. in bzr when you merge another branch in, you then have to commit it, which creates a new parent commit. in git the commits are just copied in on merge
[19:43] <dobey> as i understand it anyway
[19:44] <robru> dobey: in bileto git we explicitly skip the auto merge then make a manual merge with the custom commit message, so treating it a lot like bzr.
[19:44] <dobey> huh
[19:44] <dobey> weird
[19:46] <dobey> oh but you're not squashing the commits. so they show up when looking on code browser
[19:47] <robru> dobey: https://git.launchpad.net/bileto/tree/scripts/vcs.sh#n441 right
[19:48] <dobey> and it's using whomever proposed the MP as the author for that commit?
[19:49] <dobey> or i guess git doesn't like passing multiple authors to commit?
[19:49] <robru> dobey: no, it inspects the committers of the unmerged commits to use as the author of the merge commit
[19:49] <robru> dobey: yeah git seems to only let you specity --author once so I just shoehorn them all into one
[19:50] <dobey> even then it seems it might only use the first one
[19:50] <dobey> https://git.launchpad.net/unity-scope-snappy/commit/?id=5c48965f4132a5340e38ab886097e979f971ed67
[19:50] <dobey> at least that's how this commit appears
[19:51] <robru> dobey: not clear to me if the git web ui is just truncating the display or if the real commit only takes the first one. you can see right there in the code that it lists all committers, comma separates them, and then shoves the whole value into --author="$authors"
[19:52] <dobey> yeah i see the script does that
[19:54] <dobey> git log only shows the one
[19:54] <dobey> so i guess it truncated on the commit
[19:55] <robru> damn
[19:57] <robru> dobey: anyway I already raised your concern with steve when I was writing the code and he requested it behave this way for feature parity with bzr. if enough people vote for squashing behavior I could change it but you'll have to appeal to steve. I know I personally prefer squashing in my projects ;-)
[19:57] <dobey> steve as in slangasek ?
[19:59] <dobey> robru: well, maybe launchpad just needs to be fixed to show --first-parent or whatever instead of everything, like it does for bzr
[20:00] <dobey> (or really, git needs to be changed to do that by default, but *sigh*)
[20:00] <robru> dobey: I suppose that's also possible, file a bug against launchpad ;-)
[20:02] <dobey> not sure what to do about the author thing
[20:21] <robru> dobey: well instead of using a comma I could make it say "Name and Name and Name and Name" and then git couldn't possibly truncate it ;-)
[20:22] <dobey> that would be incredibly awful
[20:24] <robru> ¯\_(ツ)_/¯
[20:26] <dobey> some weird thing inside the long commit would be better. but meh. it's at least a little less annoying than the history thing
[20:28] <robru> hmm
[20:46] <dobey> hmm, now i need to figure out how best to get snapd-glib in xenial overlay
[20:47] <robru> dobey: what's the issue? trying to decide between dual landing or having separate branches per series?
[20:48] <dobey> no, it's not my project, and it's not landed via ci train
[20:48] <dobey> the issue is it's not in xenial and i need to use it to do my work :)
[20:49] <dobey> and rober ancell is not back until monday i guess
[20:49] <dobey> well, saturday for him now anyway, but still
[20:50] <dobey> i guess i could copy the yakkety version and append ~16.04.1 onto it or something, and shove that in a silo
[21:15] <dobey> robru: can you copy snapd-glib source from https://launchpad.net/~unity-api-team/+archive/ubuntu/dev-build-4/+packages into silo 2116 please?
[21:15] -queuebot:#ubuntu-ci-eng- dobey, https://bileto.ubuntu.com/#/ticket/2116 No packages are being considered! If you are preparing sources manually, please upload them to the PPA now
[21:18] <robru> dobey: sure
[21:25] -queuebot:#ubuntu-ci-eng- dobey, https://bileto.ubuntu.com/#/ticket/2116 Preparing packages
[21:26] <dobey> i guess nobody is around to publish though
[21:36] -queuebot:#ubuntu-ci-eng- dobey, https://bileto.ubuntu.com/#/ticket/2116 Successfully built
[22:03] -queuebot:#ubuntu-ci-eng- dobey, https://bileto.ubuntu.com/#/ticket/2116 QA Signoff: Ready
[22:59] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/2117 Successfully built
[23:00] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/2118 Successfully built