[00:30] -queuebot:#ubuntu-ci-eng- michi, jamesh, https://bileto.ubuntu.com/#/ticket/2149 Preparing packages
[00:51] -queuebot:#ubuntu-ci-eng- michi, jamesh, https://bileto.ubuntu.com/#/ticket/2149 Dependency wait (zesty/storage-framework). Failed to build (zesty/mcloud). Pending binary packages (vivid/mcloud, xenial/mcloud). Successfully built (vivid/storage-framework, xenial/storage-framework)
[01:11] -queuebot:#ubuntu-ci-eng- michi, jamesh, https://bileto.ubuntu.com/#/ticket/2149 Dependency wait (zesty/storage-framework). Failed to build (zesty/mcloud). Successfully built (vivid/mcloud, vivid/storage-framework, xenial/mcloud, xenial/storage-framework)
[01:21] -queuebot:#ubuntu-ci-eng- michi, jamesh, https://bileto.ubuntu.com/#/ticket/2149 Preparing packages
[01:30] -queuebot:#ubuntu-ci-eng- jbicha, https://bileto.ubuntu.com/#/ticket/2158 Preparing packages
[01:31] -queuebot:#ubuntu-ci-eng- michi, jamesh, https://bileto.ubuntu.com/#/ticket/2149 Currently building (vivid/mcloud, xenial/mcloud). Dependency wait (zesty/storage-framework). Failed to build (zesty/mcloud). Successfully built (vivid/storage-framework, xenial/storage-framework)
[01:40] -queuebot:#ubuntu-ci-eng- michi, jamesh, https://bileto.ubuntu.com/#/ticket/2149 Preparing packages
[01:40] -queuebot:#ubuntu-ci-eng- jbicha, https://bileto.ubuntu.com/#/ticket/2158 Currently building (zesty/nux). Failed to build (zesty/unity)
[02:00] -queuebot:#ubuntu-ci-eng- jbicha, https://bileto.ubuntu.com/#/ticket/2158 Failed to build (zesty/unity). Pending binary packages (zesty/nux)
[02:02] -queuebot:#ubuntu-ci-eng- michi, jamesh, https://bileto.ubuntu.com/#/ticket/2149 Preparing packages
[02:20] -queuebot:#ubuntu-ci-eng- jbicha, https://bileto.ubuntu.com/#/ticket/2158 Failed to build (zesty/unity). Successfully built (zesty/nux)
[02:21] -queuebot:#ubuntu-ci-eng- jbicha, https://bileto.ubuntu.com/#/ticket/2158 Preparing packages
[02:31] -queuebot:#ubuntu-ci-eng- michi, jamesh, https://bileto.ubuntu.com/#/ticket/2149 Dependency wait (zesty/mcloud, zesty/storage-framework). Pending binary packages (vivid/mcloud, xenial/mcloud). Successfully built (vivid/storage-framework, xenial/storage-framework)
[02:51] -queuebot:#ubuntu-ci-eng- michi, jamesh, https://bileto.ubuntu.com/#/ticket/2149 Dependency wait (zesty/mcloud, zesty/storage-framework). Successfully built (vivid/mcloud, vivid/storage-framework, xenial/mcloud, xenial/storage-framework)
[03:20] -queuebot:#ubuntu-ci-eng- jbicha, https://bileto.ubuntu.com/#/ticket/2158 Pending binary packages (zesty/unity). Successfully built (zesty/nux)
[03:40] -queuebot:#ubuntu-ci-eng- jbicha, https://bileto.ubuntu.com/#/ticket/2158 Successfully built
[05:20] -queuebot:#ubuntu-ci-eng- marcustomlinson, https://bileto.ubuntu.com/#/ticket/2110 Preparing packages
[05:33] -queuebot:#ubuntu-ci-eng- marcustomlinson, https://bileto.ubuntu.com/#/ticket/2110 Currently building (vivid/unity-scopes-shell, xenial/unity-scopes-shell). Failed to build (zesty/unity-scopes-shell). Successfully built (vivid/unity-scopes-api, xenial/unity-scopes-api, zesty/unity-scopes-api)
[05:40] -queuebot:#ubuntu-ci-eng- marcustomlinson, https://bileto.ubuntu.com/#/ticket/2110 Preparing packages
[05:53] -queuebot:#ubuntu-ci-eng- marcustomlinson, https://bileto.ubuntu.com/#/ticket/2110 Currently building (vivid/unity-scopes-shell, xenial/unity-scopes-shell). Failed to build (zesty/unity-scopes-shell). Successfully built (vivid/unity-scopes-api, xenial/unity-scopes-api, zesty/unity-scopes-api)
[06:13] -queuebot:#ubuntu-ci-eng- marcustomlinson, https://bileto.ubuntu.com/#/ticket/2110 Failed to build (zesty/unity-scopes-shell). Successfully built (vivid/unity-scopes-api, vivid/unity-scopes-shell, xenial/unity-scopes-api, xenial/unity-scopes-shell, zesty/unity-scopes-api)
[06:28] <jamesh> trainguards: hi.  My silo is currently blocked because the the zesty/s390x builds are in dep-wait state: https://bileto.ubuntu.com/#/ticket/2149
[06:28] <jamesh> trainguards: What can we do to unblock it?
[06:30] <jamesh> from the look of it, the problem is caused by one of our dependencies intentionally breaking the s390x build: https://code.launchpad.net/~mardy/ubuntu-system-settings-online-accounts/upstart-dep/+merge/307151, which got approved and landed
[06:30] <robru> jamesh: you need to get an archive admin to delete the s390x binaries so that bileto stops caring about that arch.
[06:31] <jamesh> (the annoying thing is that the above ubuntu-system-settings-online-accounts change only prevented the package building on zesty/s390x: it is still being built on xenial/s390x
[06:31] <jamesh> so it only seems to be causing us pain
[07:23] <Mirv> jamesh: if it's properly blocked now, indeed ask for binary removals on #ubuntu-release from zesty
[08:24] -queuebot:#ubuntu-ci-eng- mardy, https://bileto.ubuntu.com/#/ticket/2016 Preparing packages
[08:30] -queuebot:#ubuntu-ci-eng- Mirv, https://bileto.ubuntu.com/#/ticket/1983 Abandoning ticket
[08:32] -queuebot:#ubuntu-ci-eng- Mirv, https://bileto.ubuntu.com/#/ticket/1964 Merging branches
[08:38] -queuebot:#ubuntu-ci-eng- mardy, https://bileto.ubuntu.com/#/ticket/2016 Failed to build (vivid/online-accounts-api). Pending binary packages (xenial/online-accounts-api, zesty/online-accounts-api). Successfully built (vivid/libaccounts-glib, vivid/libaccounts-qt, xenial/libaccounts-glib, xenial/libaccounts-qt, zesty/libaccounts-glib, zesty/libaccounts-qt)
[08:58] -queuebot:#ubuntu-ci-eng- mardy, https://bileto.ubuntu.com/#/ticket/2016 Failed to build (vivid/online-accounts-api). Successfully built (vivid/libaccounts-glib, vivid/libaccounts-qt, xenial/libaccounts-glib, xenial/libaccounts-qt, xenial/online-accounts-api, zesty/libaccounts-glib, zesty/libaccounts-qt, zesty/online-accounts-api)
[09:05] -queuebot:#ubuntu-ci-eng- mardy, https://bileto.ubuntu.com/#/ticket/2016 Preparing packages
[09:18] -queuebot:#ubuntu-ci-eng- mardy, https://bileto.ubuntu.com/#/ticket/2016 Failed to build (vivid/online-accounts-api). Pending binary packages (xenial/online-accounts-api). Successfully built (vivid/libaccounts-glib, vivid/libaccounts-qt, xenial/libaccounts-glib, xenial/libaccounts-qt, zesty/libaccounts-glib, zesty/libaccounts-qt, zesty/online-accounts-api)
[09:38] -queuebot:#ubuntu-ci-eng- mardy, https://bileto.ubuntu.com/#/ticket/2016 Failed to build (vivid/online-accounts-api). Successfully built (vivid/libaccounts-glib, vivid/libaccounts-qt, xenial/libaccounts-glib, xenial/libaccounts-qt, xenial/online-accounts-api, zesty/libaccounts-glib, zesty/libaccounts-qt, zesty/online-accounts-api)
[09:42] -queuebot:#ubuntu-ci-eng- mardy, https://bileto.ubuntu.com/#/ticket/2016 Preparing packages
[09:44] -queuebot:#ubuntu-ci-eng- mardy, https://bileto.ubuntu.com/#/ticket/2016 vivid/libaccounts-glib: Failed to download DSC file https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/2016.1/+files/libaccounts-glib_1.23+15.04.20161104-0ubuntu1.dsc
[09:47] -queuebot:#ubuntu-ci-eng- mardy, https://bileto.ubuntu.com/#/ticket/2016 Preparing packages
[09:49] -queuebot:#ubuntu-ci-eng- mardy, https://bileto.ubuntu.com/#/ticket/2016 vivid/libaccounts-glib: Failed to download DSC file https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/2016.1/+files/libaccounts-glib_1.23+15.04.20161104-0ubuntu1.dsc
[10:18] -queuebot:#ubuntu-ci-eng- mardy, https://bileto.ubuntu.com/#/ticket/2016 Failed to build (vivid/online-accounts-api). Successfully built (vivid/libaccounts-glib, vivid/libaccounts-qt, xenial/libaccounts-glib, xenial/libaccounts-qt, xenial/online-accounts-api, zesty/libaccounts-glib, zesty/libaccounts-qt, zesty/online-accounts-api)
[10:24] <Saviq> sil2100, can you please ♻ http://people.canonical.com/~ubuntu-archive/proposed-migration/zesty/update_excuses.html#unity8 - seems there was some dependency issue when it tried to test
[10:32] <Saviq> sil2100, or if you could force-finalize https://bileto.ubuntu.com/#/ticket/2081
[10:32] <Saviq> trainguards, or any of you guys ↑
[10:34] <sil2100> On it!
[10:35] <Saviq> tx
[10:36] <Trevinho> oh, I was about to ask the same :-)
[11:02] -queuebot:#ubuntu-ci-eng- sil2100, https://bileto.ubuntu.com/#/ticket/2159 Preparing packages
[11:03] -queuebot:#ubuntu-ci-eng- sil2100, https://bileto.ubuntu.com/#/ticket/2159 No packages are being considered! If you are preparing sources manually, please upload them to the PPA now
[11:56] -queuebot:#ubuntu-ci-eng- mardy, https://bileto.ubuntu.com/#/ticket/2016 Preparing packages
[12:06] -queuebot:#ubuntu-ci-eng- abeato, https://bileto.ubuntu.com/#/ticket/2147 QA Signoff: Ready
[12:17] -queuebot:#ubuntu-ci-eng- tiagosh boiko rmescandon bfiller, https://bileto.ubuntu.com/#/ticket/1319 Generating diffs
[12:18] -queuebot:#ubuntu-ci-eng- mardy, https://bileto.ubuntu.com/#/ticket/2016 Failed to build (vivid/online-accounts-api). Successfully built (vivid/libaccounts-glib, vivid/libaccounts-qt, xenial/libaccounts-glib, xenial/libaccounts-qt, xenial/online-accounts-api, zesty/libaccounts-glib, zesty/libaccounts-qt, zesty/online-accounts-api)
[12:22] <Elleo> trainguards: is it known that unity-scope-click and unity8 tests don't work on xenial due to dependency problems?
[12:23] -queuebot:#ubuntu-ci-eng- tiagosh boiko rmescandon bfiller, https://bileto.ubuntu.com/#/ticket/1319 Successfully built
[12:28] <Mirv> Elleo: I don't think, I don't know why that would happen as everything should at least double land (to xenial + zesty) and in most changes triple land
[12:33] -queuebot:#ubuntu-ci-eng- greyback, https://bileto.ubuntu.com/#/ticket/2160 QA Signoff: N/A
[12:40] <Elleo> Mirv: I'm getting these failures on all xenial platforms<EMAIL_ADDRESS>[12:40] <Elleo> Mirv: looks like it's maybe caused by oxide?
[12:40] <Elleo> oSoMoN: did you mention something about issues with oxide and landings on Friday?
[12:42] <oSoMoN> Elleo, yes but they should be solved now
[12:43] <Elleo> oSoMoN: solved as of when? these tests ran this morning
[12:44] <oSoMoN> Elleo, in theory as of Friday evening, let me have a closer look at your failure
[12:44] <Elleo> oSoMoN: thanks
[12:47] <oSoMoN> Elleo, the stable phone overlay has oxide-qt 1.18.3-0ubuntu<IP_ADDRESS>+overlay1, but it looks like pkgProblemResolver is only considering 1.18.3-0ubuntu<IP_ADDRESS> (from xenial-updates), I wonder why
[12:49] <Elleo> ah :/
[12:49] -queuebot:#ubuntu-ci-eng- mardy, https://bileto.ubuntu.com/#/ticket/2016 Preparing packages
[12:56] -queuebot:#ubuntu-ci-eng- alan_g, https://bileto.ubuntu.com/#/ticket/2155 Publishing packages
[12:57] -queuebot:#ubuntu-ci-eng- jbicha, https://bileto.ubuntu.com/#/ticket/2158 Publishing packages
[12:58] -queuebot:#ubuntu-ci-eng- jbicha, https://bileto.ubuntu.com/#/ticket/2158 Publish failed: Bad merges
[12:58] -queuebot:#ubuntu-ci-eng- mardy, https://bileto.ubuntu.com/#/ticket/2016 Currently building (xenial/online-accounts-api, zesty/online-accounts-api). Failed to build (vivid/online-accounts-api). Successfully built (vivid/libaccounts-glib, vivid/libaccounts-qt, xenial/libaccounts-glib, xenial/libaccounts-qt, zesty/libaccounts-glib, zesty/libaccounts-qt)
[12:59] <Elleo> trainguards: ^ any idea why that might be the case?
[13:00] <jbicha> trainguards: could I get a review of https://code.launchpad.net/~jbicha/nux/dont-build-depend-on-libglew/+merge/310157
[13:02] -queuebot:#ubuntu-ci-eng- mardy, https://bileto.ubuntu.com/#/ticket/2016 Preparing packages
[13:03] <jbicha> Trevinho: ^
[13:03] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/2081 Release pocket
[13:09] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/2106 Failed to build (xenial/unity8). Needs rebuild due to new commits (zesty/qmenumodel, zesty/unity8). Successfully built (vivid/qmenumodel, vivid/ubuntu-settings-components, vivid/unity8, xenial/qmenumodel, xenial/ubuntu-settings-components, zesty/ubuntu-settings-components)
[13:14] -queuebot:#ubuntu-ci-eng- andyrock, https://bileto.ubuntu.com/#/ticket/2112 Needs rebuild due to new commits (zesty/unity8). Successfully built (vivid/unity-api, vivid/unity8, xenial/unity-api, xenial/unity8, zesty/unity-api)
[13:14] -queuebot:#ubuntu-ci-eng- tedg mterry, https://bileto.ubuntu.com/#/ticket/2129 Failed to build (xenial/ubuntu-app-launch, xenial/url-dispatcher, zesty/unity-scopes-shell, zesty/url-dispatcher). Needs rebuild due to new commits (zesty/indicator-network, zesty/unity8). Ready to build (xenial/unity8-desktop-session, zesty/unity8-desktop-session). Successfully built (xenial/indicator-application, xenial/indicator-bluetooth, xenial/indicator-datetime, xenial/indicator-locat
[13:16] -queuebot:#ubuntu-ci-eng- ltinkl, https://bileto.ubuntu.com/#/ticket/2132 Failed to build (xenial/unity8). Needs rebuild due to new commits (zesty/unity8). Successfully built (vivid/indicator-power, vivid/unity8, xenial/indicator-power, zesty/indicator-power)
[13:17] -queuebot:#ubuntu-ci-eng- Cimi, https://bileto.ubuntu.com/#/ticket/2050 Needs rebuild due to new commits (zesty/unity8). Successfully built (vivid/unity8, xenial/unity8)
[13:17] -queuebot:#ubuntu-ci-eng- alan_g, https://bileto.ubuntu.com/#/ticket/2155 Proposed pocket (zesty/miral). Release pocket (xenial/miral)
[13:18] -queuebot:#ubuntu-ci-eng- mardy, https://bileto.ubuntu.com/#/ticket/2016 Failed to build (vivid/online-accounts-api). Pending binary packages (xenial/online-accounts-api, zesty/online-accounts-api). Successfully built (vivid/libaccounts-glib, vivid/libaccounts-qt, xenial/libaccounts-glib, xenial/libaccounts-qt, zesty/libaccounts-glib, zesty/libaccounts-qt)
[13:19] -queuebot:#ubuntu-ci-eng- mterry, https://bileto.ubuntu.com/#/ticket/2137 Failed to build (xenial/unity8). Needs rebuild due to new commits (zesty/unity8, zesty/unity8-desktop-session). Successfully built (vivid/unity8, vivid/unity8-desktop-session, xenial/unity8-desktop-session)
[13:19] -queuebot:#ubuntu-ci-eng- jbicha, https://bileto.ubuntu.com/#/ticket/2158 Successfully built
[13:20] -queuebot:#ubuntu-ci-eng- mardy, https://bileto.ubuntu.com/#/ticket/2016 Preparing packages
[13:24] -queuebot:#ubuntu-ci-eng- ltinkl, https://bileto.ubuntu.com/#/ticket/2132 Preparing packages
[13:25] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/2103 Failed to build (xenial/unity8). Needs rebuild due to new commits (zesty/qmenumodel, zesty/unity8). Successfully built (vivid/qmenumodel, vivid/ubuntu-settings-components, vivid/unity8, xenial/qmenumodel, xenial/ubuntu-settings-components, zesty/ubuntu-settings-components)
[13:25] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/2106 Preparing packages
[13:38] -queuebot:#ubuntu-ci-eng- mardy, https://bileto.ubuntu.com/#/ticket/2016 Failed to build (vivid/online-accounts-api). Pending binary packages (xenial/online-accounts-api, zesty/online-accounts-api). Successfully built (vivid/libaccounts-glib, vivid/libaccounts-qt, xenial/libaccounts-glib, xenial/libaccounts-qt, zesty/libaccounts-glib, zesty/libaccounts-qt)
[13:42] -queuebot:#ubuntu-ci-eng- mardy, https://bileto.ubuntu.com/#/ticket/2016 Preparing packages
[13:44] -queuebot:#ubuntu-ci-eng- mterry, https://bileto.ubuntu.com/#/ticket/2137 Preparing packages
[13:47] -queuebot:#ubuntu-ci-eng- morphis, https://bileto.ubuntu.com/#/ticket/2162 No packages are being considered! If you are preparing sources manually, please upload them to the PPA now
[13:48] -queuebot:#ubuntu-ci-eng- dobey, https://bileto.ubuntu.com/#/ticket/2122 Preparing packages
[13:58] -queuebot:#ubuntu-ci-eng- mardy, https://bileto.ubuntu.com/#/ticket/2016 Failed to build (vivid/online-accounts-api). Pending binary packages (xenial/online-accounts-api, zesty/online-accounts-api). Successfully built (vivid/libaccounts-glib, vivid/libaccounts-qt, xenial/libaccounts-glib, xenial/libaccounts-qt, zesty/libaccounts-glib, zesty/libaccounts-qt)
[14:03] -queuebot:#ubuntu-ci-eng- morphis, https://bileto.ubuntu.com/#/ticket/2162 Pending binary packages
[14:05] -queuebot:#ubuntu-ci-eng- dobey, https://bileto.ubuntu.com/#/ticket/2122 Pending binary packages (xenial/unity-scope-click, zesty/unity-scope-click). Successfully built (xenial/ubuntuone-credentials, zesty/ubuntuone-credentials)
[14:05] -queuebot:#ubuntu-ci-eng- mardy, https://bileto.ubuntu.com/#/ticket/2016 Preparing packages
[14:10] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/2106 Pending binary packages (xenial/unity8). Successfully built (vivid/qmenumodel, vivid/ubuntu-settings-components, vivid/unity8, xenial/qmenumodel, xenial/ubuntu-settings-components, zesty/qmenumodel, zesty/ubuntu-settings-components, zesty/unity8)
[14:16] -queuebot:#ubuntu-ci-eng- ltinkl, https://bileto.ubuntu.com/#/ticket/2132 Successfully built
[14:18] -queuebot:#ubuntu-ci-eng- mardy, https://bileto.ubuntu.com/#/ticket/2016 Failed to build (vivid/online-accounts-api, xenial/online-accounts-api, zesty/online-accounts-api). Successfully built (vivid/libaccounts-glib, vivid/libaccounts-qt, xenial/libaccounts-glib, xenial/libaccounts-qt, zesty/libaccounts-glib, zesty/libaccounts-qt)
[14:19] -queuebot:#ubuntu-ci-eng- mterry, https://bileto.ubuntu.com/#/ticket/2137 Successfully built
[14:21] -queuebot:#ubuntu-ci-eng- mardy, https://bileto.ubuntu.com/#/ticket/2016 Preparing packages
[14:23] -queuebot:#ubuntu-ci-eng- morphis, https://bileto.ubuntu.com/#/ticket/2162 Diff missing
[14:24] -queuebot:#ubuntu-ci-eng- dobey, https://bileto.ubuntu.com/#/ticket/2122 Successfully built
[14:28] -queuebot:#ubuntu-ci-eng- Kaleo, https://bileto.ubuntu.com/#/ticket/2008 QA Signoff: Failed
[14:30] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/2106 Successfully built
[14:35] <ChrisTownsend> ubuntu-qa: Hi!  Would it be possible to get an exception for the failing Xenial autopkgtests for https://bileto.ubuntu.com/#/ticket/2123 ?  The content-hub's url-dispatcher test is timing out for some reason and it's unrelated to our Libertine landing.
[14:37] <rvr> ChrisTownsend: Let me see
[14:37] <ChrisTownsend> rvr: Ok, thanks
[14:37] -queuebot:#ubuntu-ci-eng- alan_g, https://bileto.ubuntu.com/#/ticket/2155 Release pocket
[14:38] -queuebot:#ubuntu-ci-eng- mardy, https://bileto.ubuntu.com/#/ticket/2016 Pending binary packages (vivid/online-accounts-api, xenial/online-accounts-api). Successfully built (vivid/libaccounts-glib, vivid/libaccounts-qt, xenial/libaccounts-glib, xenial/libaccounts-qt, zesty/libaccounts-glib, zesty/libaccounts-qt, zesty/online-accounts-api)
[14:39] <dobey> kenvandine: ^^ any ideas about how to fix the content-hub thing, btw?
[14:40] -queuebot:#ubuntu-ci-eng- morphis, https://bileto.ubuntu.com/#/ticket/2162 Preparing packages
[14:40] <kenvandine> dobey, it's fixed in silo 2153
[14:40] -queuebot:#ubuntu-ci-eng- morphis, https://bileto.ubuntu.com/#/ticket/2162 vivid/aethercast: Failed to commit https://git.launchpad.net/~morphis/aethercast/+git/aethercast. You must supply either a Commit Message on your MP, or a custom debian/changelog entry
[14:40] <kenvandine> dobey, it was UAL aborting creating AppInfo for an app that wasn't installed
[14:40] <kenvandine> the apparmor stuff was misleading
[14:40] <dobey> kenvandine: ah
[14:40] <rvr> kenvandine: Ack
[14:41] <kenvandine> rvr, 2153 is ready for QA... i lander approved it before the branch to confirm the automated tests passed
[14:41] <kenvandine> rvr, the branch is approved now
[14:42] <rvr> kenvandine: Moved to ready lane
[14:42] <kenvandine> rvr, thx!
[14:44] -queuebot:#ubuntu-ci-eng- morphis, https://bileto.ubuntu.com/#/ticket/2162 Preparing packages
[14:45] -queuebot:#ubuntu-ci-eng- morphis, https://bileto.ubuntu.com/#/ticket/2162 vivid/aethercast: Failed to add changelog message
[14:46] -queuebot:#ubuntu-ci-eng- morphis, https://bileto.ubuntu.com/#/ticket/2162 Preparing packages
[14:47] -queuebot:#ubuntu-ci-eng- morphis, https://bileto.ubuntu.com/#/ticket/2162 vivid/aethercast: Failed to add changelog message
[14:47] <davmor2> ChrisTownsend: is there a reason that the tests run on libertine seem to point content hub?
[14:47] <davmor2> ChrisTownsend: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_39a8dbb93caf4ec889f8a1b7f69885db/bileto-2123-excuses/2016-11-07_13:25:01/2123_xenial_excuses.html
[14:48] <kenvandine> davmor2, the fix for that is in silo 2153 :)
[14:48] <davmor2> jibel: ^
[14:49] <davmor2> kenvandine: thanks dude
[14:49] <ChrisTownsend> davmor2: The only reason I can think of is because liblibertine is a depnedency of content-hub????
[14:50] <davmor2> kenvandine, ChrisTownsend: also do you know why there are no arm64 results?
[14:51] <ChrisTownsend> davmor2: Probably because we have to depend on Xmir now and Xmir is only built on armhf, amd65, and i386.
[14:51] <ChrisTownsend> Gah, amd64
[14:58] <ChrisTownsend> rvr: davmor2: Is my silo going to receive an exception to the unrelated failing autopkgtest and get in the QA queue?
[14:58] -queuebot:#ubuntu-ci-eng- ChrisTownsend, https://bileto.ubuntu.com/#/ticket/2123 QA Signoff: Ready
[14:58] -queuebot:#ubuntu-ci-eng- mardy, https://bileto.ubuntu.com/#/ticket/2016 Successfully built
[14:58] <rvr> ChrisTownsend: :)
[14:58] <davmor2> ChrisTownsend: rvr is looking into that I think I was just curious about the other stuff :)
[14:58] <ChrisTownsend> lol, ok, answers that
[14:59] <ChrisTownsend> rvr: davmor2: Thanks guys!
[14:59] <kenvandine> davmor2, rvr: I'm actually going to rebuild silo 2153 again with another improvement :)
[14:59] <rvr> kenvandine: Ack!
[15:01] -queuebot:#ubuntu-ci-eng- kenvandine, https://bileto.ubuntu.com/#/ticket/2153 QA Signoff: Required
[15:01] -queuebot:#ubuntu-ci-eng- kenvandine, https://bileto.ubuntu.com/#/ticket/2153 Preparing packages
[15:03] -queuebot:#ubuntu-ci-eng- morphis, https://bileto.ubuntu.com/#/ticket/2162 Diff missing (vivid/isc-dhcp). Ready to build (vivid/aethercast)
[15:05] -queuebot:#ubuntu-ci-eng- pete-woods, https://bileto.ubuntu.com/#/ticket/2073 Preparing packages
[15:09] -queuebot:#ubuntu-ci-eng- greyback, https://bileto.ubuntu.com/#/ticket/2160 Preparing packages
[15:11] <clivejo> Hi folks, is there anyone who could help with runing autotests against a LaunchPad PPA?
[15:12] <clivejo> and provide public output so that a team (Kubuntu) can see whats failing and fix it before uploading to the archive?
[15:14] <tedg> jibel: I have a silo that I'd like to get in for OTA14, but I don't have a Ubuntu Touch device to verify it works. It works on my desktop, but I'm not sure that's enough for a lander sign off. Could we add it to the QA queue anyway?
[15:14] <tedg> jibel: https://bileto.ubuntu.com/#/ticket/1886
[15:17] <dobey> clivejo: i think you need to talk to pitti about that.
[15:18] <jibel> tedg, this silos changes much more than bug 1591342
[15:18] <ubot5`> bug 1591342 in url-dispatcher (Ubuntu) "Complains about bad url on libertine scope urls" [High,In progress] https://launchpad.net/bugs/1591342
[15:18] <clivejo> where and how do I talk to pitti?
[15:18] <jibel> silo* even
[15:18] <jibel> tedg, can we have a silo with just this change for 14?
[15:18] <tedg> jibel: Yes?
[15:19] <dobey> clivejo: he's usually in #ubuntu-devel during normal EU hours
[15:19] <tedg> jibel: Why? There are a lot of other bugs that are fixed there.
[15:19] <tedg> jibel: Would really love to see them all fixed :-)
[15:19] <dobey> clivejo: really that whole conversation should probably happen in that channel
[15:19] <jibel> tedg, it's a maintenance release with just critical bug fixes and security fixes
[15:20] <jibel> tedg, I'm sure you do but I'd love to keep the numbers of changes small
[15:20] <dobey> clivejo: unless your goal is to move to using more of the CI train, rather than just getting autopkgtests run for some other PPAs that you own
[15:21] <tedg> jibel: Then we have to start maintaining branches :-/
[15:21] <clivejo> Id just like a public display of autotests run against one of our PPA's
[15:22] <clivejo> so that the team can see them and be involved in fixing them
[15:22] <clivejo> rather than leaving it to one person
[15:23] <dobey> clivejo: right. i'd suggesting pinging pitti in #ubuntu-devel and having that discussion in there then
[15:24] -queuebot:#ubuntu-ci-eng- tedg, https://bileto.ubuntu.com/#/ticket/1886 QA Signoff: N/A
[15:25] -queuebot:#ubuntu-ci-eng- greyback, https://bileto.ubuntu.com/#/ticket/2160 Dependency wait (xenial/qtmir, xenial/qtmir-gles, xenial/unity8, zesty/qtmir, zesty/qtmir-gles, zesty/unity8). Pending binary packages (xenial/unity-api). Successfully built (zesty/unity-api)
[15:29] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/2106 Preparing packages
[15:32] <dobey> wherefore art thou, britney?
[15:36] -queuebot:#ubuntu-ci-eng- pete-woods, https://bileto.ubuntu.com/#/ticket/2073 Needs rebuild due to new commits (zesty/gmenuharness). Pending binary packages (vivid/indicator-network, zesty/indicator-network). Successfully built (vivid/gmenuharness, xenial/gmenuharness, xenial/indicator-network)
[15:39] -queuebot:#ubuntu-ci-eng- morphis, https://bileto.ubuntu.com/#/ticket/2162 Preparing packages
[15:42] -queuebot:#ubuntu-ci-eng- pete-woods, https://bileto.ubuntu.com/#/ticket/2073 Preparing packages
[15:43] -queuebot:#ubuntu-ci-eng- greyback, https://bileto.ubuntu.com/#/ticket/2160 Dependency wait (xenial/qtmir, xenial/qtmir-gles, xenial/unity8, zesty/qtmir, zesty/qtmir-gles, zesty/unity8). Successfully built (xenial/unity-api, zesty/unity-api)
[15:50] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/2106 Successfully built
[15:56] -queuebot:#ubuntu-ci-eng- pete-woods, https://bileto.ubuntu.com/#/ticket/2073 Successfully built
[15:59] -queuebot:#ubuntu-ci-eng- pete-woods, https://bileto.ubuntu.com/#/ticket/2073 Preparing packages
[16:02] -queuebot:#ubuntu-ci-eng- Cimi, https://bileto.ubuntu.com/#/ticket/2050 Preparing packages
[16:03] -queuebot:#ubuntu-ci-eng- morphis, https://bileto.ubuntu.com/#/ticket/2162 Failed to build (vivid/aethercast, xenial/aethercast, zesty/aethercast). Ready to build (xenial/isc-dhcp, zesty/isc-dhcp). Successfully built (vivid/isc-dhcp)
[16:16] -queuebot:#ubuntu-ci-eng- morphis, https://bileto.ubuntu.com/#/ticket/2162 Preparing packages
[16:33] -queuebot:#ubuntu-ci-eng- tedg, https://bileto.ubuntu.com/#/ticket/1886 Preparing packages
[16:36] -queuebot:#ubuntu-ci-eng- pete-woods, https://bileto.ubuntu.com/#/ticket/2073 Failed to build (xenial/indicator-network). Successfully built (vivid/gmenuharness, vivid/indicator-network, xenial/gmenuharness, zesty/gmenuharness, zesty/indicator-network)
[16:38] -queuebot:#ubuntu-ci-eng- Elleo, https://bileto.ubuntu.com/#/ticket/2154 Diff missing (vivid/maliit-framework, vivid/presage, xenial/maliit-framework, xenial/presage, zesty/maliit-framework, zesty/presage). Successfully built (vivid/ubuntu-keyboard, xenial/ubuntu-keyboard, zesty/ubuntu-keyboard)
[16:40] <josepht> jibel: do you guys still use the CI Dashboard?
[16:43] <jibel> josepht, no
[16:43] -queuebot:#ubuntu-ci-eng- morphis, https://bileto.ubuntu.com/#/ticket/2162 Currently building (vivid/aethercast). Failed to build (zesty/aethercast). Ready to build (xenial/isc-dhcp, zesty/isc-dhcp). Successfully built (vivid/isc-dhcp, xenial/aethercast)
[16:43] <josepht> jibel: ack, thanks
[16:46] -queuebot:#ubuntu-ci-eng- tedg, https://bileto.ubuntu.com/#/ticket/2163 Preparing packages
[16:47] -queuebot:#ubuntu-ci-eng- tedg, https://bileto.ubuntu.com/#/ticket/2163 vivid/url-dispatcher: Failed to commit https://code.launchpad.net/~larryprice/url-dispatcher/appid-with-dots. You must supply either a Commit Message on your MP, or a custom debian/changelog entry
[16:47] <mterry> robru: I can't seem to search on bileto.ubuntu.com
[16:47] <mterry> robru: ah I figured out the UI
[16:48] -queuebot:#ubuntu-ci-eng- tedg, https://bileto.ubuntu.com/#/ticket/2163 Preparing packages
[16:49] -queuebot:#ubuntu-ci-eng- tedg, https://bileto.ubuntu.com/#/ticket/2163 vivid/url-dispatcher: Failed to add changelog message
[16:51] <tedg> robru: I'm not sure how to fix this, how do I release something on a vivid branch? https://bileto.ubuntu.com/log/2163/build/2/
[16:54] <robru> tedg: your vivid branch needs to actually have a vivid version number in debian/changelog
[16:54] <robru> mterry: what was the problem?
[16:58] <mterry> robru: the old search just required me to press enter.  The new search I need to click if I'm searching all or just active
[16:59] <mterry> Didn't even notice the buttons there at first
[17:00] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/2103 Abandoning ticket
[17:01] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/2146 Preparing packages
[17:01] <robru> mterry: oooooh
[17:02] <robru> mterry: will fix after breakfast
[17:03] -queuebot:#ubuntu-ci-eng- morphis, https://bileto.ubuntu.com/#/ticket/2162 Failed to build (zesty/aethercast). Ready to build (xenial/isc-dhcp, zesty/isc-dhcp). Successfully built (vivid/aethercast, vivid/isc-dhcp, xenial/aethercast)
[17:04] -queuebot:#ubuntu-ci-eng- greyback, https://bileto.ubuntu.com/#/ticket/2160 Currently building (xenial/unity8, zesty/qtmir-gles, zesty/unity8). Failed to build (xenial/qtmir, xenial/qtmir-gles, zesty/qtmir). Successfully built (xenial/unity-api, zesty/unity-api)
[17:04] -queuebot:#ubuntu-ci-eng- tedg, https://bileto.ubuntu.com/#/ticket/2163 Ready to build
[17:04] <tedg> robru: I don't have a debian/changelog, so I need one?
[17:06] <robru> tedg: no, the opposite of that. The target trunk needs to have the correct version in the changelog
[17:07] <tedg> robru: Hmm, okay. That's going to make it really hard for everyone being told they have to open custom vivid branches today.
[17:08] -queuebot:#ubuntu-ci-eng- tedg, https://bileto.ubuntu.com/#/ticket/1886 Successfully built
[17:08] <robru> tedg: it's really hard to edit one line of a changelog?
[17:08] <tedg> robru: Wouldn't you need to edit all of the versions that are setup for post vivid to match the vivid release? Or just the last?
[17:09] <tedg> It would mean, version-wise, the changelog would jump all over the place.
[17:09] <robru> tedg: just the last.
[17:10] <tedg> Okay
[17:12] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/2146 Currently building (zesty/compiz). Failed to build (zesty/unity)
[17:12] <robru> tedg: who says everybody has to branch for vivid? First I'm hearing this
[17:12] <tedg> robru: Me too, apparently all bug fixes are no longer welcome.
[17:14] -queuebot:#ubuntu-ci-eng- tedg, https://bileto.ubuntu.com/#/ticket/2163 Preparing packages
[17:14] <robru> tedg: what gives you that idea? It should be fine to continue triple landing as far as I'm aware
[17:14] <tedg> robru: Backlog, -2 hrs
[17:15] -queuebot:#ubuntu-ci-eng- kenvandine, https://bileto.ubuntu.com/#/ticket/2153 Successfully built
[17:17] -queuebot:#ubuntu-ci-eng- charles, https://bileto.ubuntu.com/#/ticket/2156 QA Signoff: Ready
[17:17] -queuebot:#ubuntu-ci-eng- Cimi, https://bileto.ubuntu.com/#/ticket/2050 Successfully built
[17:18] <robru> Huh
[17:18] <dobey> tedg: just take the current release in vivid, untar all the files into the branch for vivid, commit and push it to the vivid branch on lp. et voila
[17:20] <robru> Yeah that would do it too. But copying the zesty trunk and editing the changelog will preserve history if you care about history
[17:20] <dobey> everybody doesn't need to "branch for vivid" either
[17:20] <dobey> but new features are generally not accepted there, so it's easier to only land things to zesty+xenial
[17:21] <dobey> robru: well, my suggestion implied the branch point was the same time the last vivid release was there, and then only the changelog should really be the thing that has a diff, to sync all the vivid versions in
[17:21] <dobey> but yeah
[17:21] <dobey> ted is overreacting a bit
[17:23] -queuebot:#ubuntu-ci-eng- greyback, https://bileto.ubuntu.com/#/ticket/2160 Currently building (xenial/unity8). Failed to build (xenial/qtmir, xenial/qtmir-gles, zesty/qtmir, zesty/qtmir-gles). Successfully built (xenial/unity-api, zesty/unity-api). Uploading build (zesty/unity8)
[17:24] -queuebot:#ubuntu-ci-eng- tedg, https://bileto.ubuntu.com/#/ticket/2163 Dependency wait
[17:39] -queuebot:#ubuntu-ci-eng- marcustomlinson, https://bileto.ubuntu.com/#/ticket/2110 Preparing packages
[17:43] -queuebot:#ubuntu-ci-eng- greyback, https://bileto.ubuntu.com/#/ticket/2160 Failed to build (xenial/qtmir, xenial/qtmir-gles, zesty/qtmir, zesty/qtmir-gles). Successfully built (xenial/unity-api, xenial/unity8, zesty/unity-api, zesty/unity8)
[18:03] <dobey> come on britney, don't make me beg
[18:04] <robru> dobey: what ticket
[18:04] <dobey> robru: 2122; it's been ~2 hrs since last excuses update
[18:07] <robru> dobey: heh should see an update in just a few minutes. looks like the current runtime is 80 minutes
[18:09] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/2146 Failed to build (zesty/unity). Successfully built (zesty/compiz)
[18:11] -queuebot:#ubuntu-ci-eng- jbicha, https://bileto.ubuntu.com/#/ticket/2158 Publishing packages
[18:19] <dobey> robru: yeah looks like it finally updated just now
[18:19] <dobey> kenvandine: hey, can you ack/publish https://bileto.ubuntu.com/#/ticket/2122 ? :)
[18:20] -queuebot:#ubuntu-ci-eng- jbicha, https://bileto.ubuntu.com/#/ticket/2158 Proposed pocket
[18:21] <kenvandine> dobey, looking
[18:23] -queuebot:#ubuntu-ci-eng- dobey, https://bileto.ubuntu.com/#/ticket/2122 Publishing packages
[18:24] <dobey> kenvandine: thanks
[18:29] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/2146 Needs rebuild due to burned version number (zesty/unity). Successfully built (zesty/compiz)
[18:30] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/2146 Preparing packages
[18:34] -queuebot:#ubuntu-ci-eng- marcustomlinson, https://bileto.ubuntu.com/#/ticket/2110 Successfully built
[18:37] -queuebot:#ubuntu-ci-eng- greyback, https://bileto.ubuntu.com/#/ticket/2160 Preparing packages
[18:40] -queuebot:#ubuntu-ci-eng- charles, https://bileto.ubuntu.com/#/ticket/2138 QA Signoff: Ready
[18:44] -queuebot:#ubuntu-ci-eng- dobey, https://bileto.ubuntu.com/#/ticket/2122 Proposed pocket (zesty/ubuntuone-credentials, zesty/unity-scope-click). Release pocket (xenial/ubuntuone-credentials, xenial/unity-scope-click)
[18:55] -queuebot:#ubuntu-ci-eng- tedg mterry, https://bileto.ubuntu.com/#/ticket/2129 Currently building (zesty/unity-scopes-shell). Failed to build (xenial/ubuntu-app-launch, xenial/url-dispatcher, zesty/url-dispatcher). Needs rebuild due to new commits (zesty/indicator-network, zesty/unity8). Ready to build (xenial/unity8-desktop-session, zesty/unity8-desktop-session). Successfully built (xenial/indicator-application, xenial/indicator-bluetooth, xenial/indicator-datetime, x
[19:09] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/2146 Pending binary packages (zesty/unity). Successfully built (zesty/compiz)
[19:09] <dobey> ubuntu-qa: can we get 2100 changed to QA N/A perhaps?
[19:11] <slangasek> robru: meeting?
[19:19] <dobey> hmm, the automatic selection of "Required" or "N/A" for "QA Signoff" by bileto doesn't make any sense to me
[19:19] -queuebot:#ubuntu-ci-eng- dobey, https://bileto.ubuntu.com/#/ticket/2164 QA Signoff: N/A
[19:20] -queuebot:#ubuntu-ci-eng- jbicha, https://bileto.ubuntu.com/#/ticket/2158 Proposed pocket (zesty/unity). Release pocket (zesty/nux)
[19:29] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/2146 Successfully built
[19:30] <robru> dobey: what are you seeing? IIRC it should be 'required' only for vivid
[19:30] <robru> (triple series or if you just pick vivid overlay)
[19:31] <robru> brb
[19:31] <dobey> robru: if i pick triple or xenial only (with overlay) it is set to required, but if i pick zesty+xenial it's not
[19:33] <dobey> robru: cf silo 2100
[19:35] <dobey> (also, i wonder how to make git branches automagically disappear after they get merged)
[19:35] -queuebot:#ubuntu-ci-eng- tedg mterry, https://bileto.ubuntu.com/#/ticket/2129 Failed to build (xenial/ubuntu-app-launch, xenial/url-dispatcher, zesty/url-dispatcher). Needs rebuild due to new commits (zesty/indicator-network, zesty/unity8). Ready to build (xenial/unity8-desktop-session, zesty/unity8-desktop-session). Successfully built (xenial/indicator-application, xenial/indicator-bluetooth, xenial/indicator-datetime, xenial/indicator-location, xenial/indicator-mess
[19:43] -queuebot:#ubuntu-ci-eng- greyback, https://bileto.ubuntu.com/#/ticket/2160 Successfully built
[20:05] <robru> dobey: I think you have to delete git branches manually, they're not quite the same as bzr branches, at least insofar as how lp treats them.
[20:06] <robru> dobey: hmm so for 2100 the question is, do you think it should be qa required for zesty+xenial or do you think it should be qa n/a for xenial overlay?
[20:06] <robru> slangasek: ^^ not sure what qa behavior is desired in bileto
[20:08] <dobey> robru: i don't have a definite answer on that. i think this silo should probably be n/a (but i might be biased). mostly what i want is consistency and predictability with the field, since it's not possible for me to change the requirement directly
[20:09] <robru> dobey: yeah I agree you definitely found a bug there, I'm just not sure what the correct behavior is
[20:10] <robru> I guess we would want QA for everything that touches overlay PPA
[20:14] <dobey> well really i think ideally we want QA for everything
[20:18] <robru> dobey: slangasek: https://bugs.launchpad.net/bileto/+bug/1639933
[20:18] <ubot5`> Ubuntu bug 1639933 in Bileto ""QA Required" behavior inconsistent" [Undecided,New]
[20:20] <dobey> robru: there's another option not listed there i think: for silos that target archive for SRUs rather than overlay (ie trusty or precise for example)
[20:20] <dobey> granted, i have no idea how often bileto gets used for SRUs
[20:25] -queuebot:#ubuntu-ci-eng- kenvandine, https://bileto.ubuntu.com/#/ticket/2153 QA Signoff: Ready
[20:27] <slangasek> robru: you should ask the QA team :)
[20:29] <dobey> robru: hmm, well, considering that "only for vivid" is apparently the current design, could i get 2100 changed to N/A so i can get someone to publish it? :)
[20:30] <robru> dobey: haha OK
[20:32] -queuebot:#ubuntu-ci-eng- dobey, https://bileto.ubuntu.com/#/ticket/2100 QA Signoff: N/A
[20:32] <dobey> thanks
[20:33] <dobey> kenvandine: ^^ can you ack/publish 2100 please? :)
[20:33] <robru> dobey: you're welcome
[20:34] <kenvandine> dobey, done
[20:34] <dobey> kenvandine: awesome, thanks!
[20:34] -queuebot:#ubuntu-ci-eng- dobey, https://bileto.ubuntu.com/#/ticket/2100 Publishing packages
[20:36] <kenvandine> np
[20:42] -queuebot:#ubuntu-ci-eng- dobey, https://bileto.ubuntu.com/#/ticket/2100 Release pocket
[20:49] -queuebot:#ubuntu-ci-eng- tedg mterry, https://bileto.ubuntu.com/#/ticket/2129 Preparing packages
[21:15] -queuebot:#ubuntu-ci-eng- tedg mterry, https://bileto.ubuntu.com/#/ticket/2129 Currently building (xenial/ubuntu-app-launch). Failed to build (xenial/url-dispatcher, zesty/ubuntu-app-launch, zesty/url-dispatcher). Needs rebuild due to new commits (zesty/indicator-network, zesty/unity8). Pending binary packages (xenial/unity8-desktop-session). Successfully built (xenial/indicator-application, xenial/indicator-bluetooth, xenial/indicator-datetime, xenial/indicator-locati
[21:23] -queuebot:#ubuntu-ci-eng- greyback, https://bileto.ubuntu.com/#/ticket/2160 Needs rebuild due to new commits (zesty/unity8). Successfully built (xenial/qtmir, xenial/qtmir-gles, xenial/unity-api, xenial/unity8, zesty/qtmir, zesty/qtmir-gles, zesty/unity-api)
[21:26] <mterry> jibel: hello!  I have silo 2137 (unity8 + unity8-desktop-session fixes for snap mode) and automated tests failed because vivid doesn't have snapd -- can you manually set QA to ready?  (I don't think we care about that vivid error)
[21:26] <mterry> I don't know what we've done in past for that issue -- must happen every time with unity8-desktop-session
[21:35] -queuebot:#ubuntu-ci-eng- tedg mterry, https://bileto.ubuntu.com/#/ticket/2129 Currently building (xenial/ubuntu-app-launch). Failed to build (xenial/url-dispatcher, zesty/ubuntu-app-launch, zesty/url-dispatcher). Needs rebuild due to new commits (zesty/indicator-network, zesty/unity8). Successfully built (xenial/indicator-application, xenial/indicator-bluetooth, xenial/indicator-datetime, xenial/indicator-location, xenial/indicator-messages, xenial/indicator-network,
[21:39] <tedg> mterry: I think that unity8-desktop-session is only landing xenial+zesty
[23:04] -queuebot:#ubuntu-ci-eng- dobey, https://bileto.ubuntu.com/#/ticket/2122 Proposed pocket (zesty/unity-scope-click). Release pocket (xenial/ubuntuone-credentials, xenial/unity-scope-click, zesty/ubuntuone-credentials)
[23:20] -queuebot:#ubuntu-ci-eng- jbicha, https://bileto.ubuntu.com/#/ticket/2158 Release pocket
[23:28] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/2146 Needs rebuild due to new commits (zesty/unity). Successfully built (zesty/compiz)
[23:29] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/2146 Preparing packages
[23:36] -queuebot:#ubuntu-ci-eng- tedg mterry, https://bileto.ubuntu.com/#/ticket/2129 Failed to build (xenial/ubuntu-app-launch, xenial/url-dispatcher, zesty/ubuntu-app-launch, zesty/url-dispatcher). Needs rebuild due to new commits (zesty/indicator-network, zesty/unity8). Successfully built (xenial/indicator-application, xenial/indicator-bluetooth, xenial/indicator-datetime, xenial/indicator-location, xenial/indicator-messages, xenial/indicator-network, xenial/indicator-powe
[23:44] -queuebot:#ubuntu-ci-eng- dobey, https://bileto.ubuntu.com/#/ticket/2122 Release pocket
[23:54] -queuebot:#ubuntu-ci-eng- justinmcp, https://bileto.ubuntu.com/#/ticket/1823 This ticket must be migrated to zesty+xenial+vivid before it can be built
[23:57] -queuebot:#ubuntu-ci-eng- justinmcp, https://bileto.ubuntu.com/#/ticket/1823 Preparing packages


[16:18] <djp_> hi ubuntu-mobile maniacs !
[16:18] <djp_> is there yet a channel for Remix ?
[16:21] <djp> or is this the place ?
[16:42] <lool> djp: We don't have a channel for remix
[16:42] <lool> djp: I suspect remix people are around
[16:43] <lool> At least njpatel is :)
[16:57] <djp> a couple of things I wodering;
[16:58] <djp> will it be available for non-Atom CPUs ?
[16:58] <djp> when the anndouncement mentiones "optimized for retail" what do they mean ?
[16:59] <djp> to put on machines to sell ? or to put on machines for sales (I want the latter)
[16:59] <lool> Meeting in one minute
[16:59] <djp> when will it be ready ?
[16:59] <djp> ok
[17:00] <lool> #startmeeting
[17:00] <MootBot> Meeting started at 11:02. The chair is lool.
[17:00] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[17:00] <lool> Hi everybody; thanks for attending this week's meeting
[17:00] <lool> The agenda is at https://wiki.ubuntu.com/MobileAndEmbedded/Meeting/20080612
[17:00] <lool> I love this week's agenda
[17:00] <lool> As I read it, we have no items to revisit from last week
[17:01] <lool> Nor for this week
[17:01] <lool> So it's open agenda season!
[17:01] <lool> I'll hang around for 5 minutes or so in case anybody would like to add an agenda item
[17:01] <cgregan> should we discuss RC3?
[17:01] <lool> [topic] RC3 discussion
[17:01] <MootBot> New Topic:  RC3 discussion
[17:01] <lool> cgregan: Sure, go ahead!
[17:02]  * persia likes RC3: works better than any previous images
[17:02] <cgregan> I just wanted to say that is was built and is working great
[17:02] <cgregan> Passed all smoke tests
[17:02] <GrueMaster> where's rc2?
[17:02] <lool> Cool; same here, it works great for me
[17:02] <cgregan> Not bug free....but I'd agree with lool and persia
[17:03] <cgregan> RC2 is still up in the release area on cdimage Gruemaster
[17:03] <GrueMaster> No one notified us that it was ready.
[17:03] <lool> GrueMaster: I still see rc2 http://cdimage.ubuntu.com/moblin/releases/hardy/
[17:03] <GrueMaster> Yea, I see it now too.
[17:03] <lool> However StevenK plans some cleanup of at least the beta images soonish
[17:03] <GrueMaster> no problem there.
[17:03] <cgregan> RC3 is much better GrueMaster
[17:04] <cgregan> We believe this will become Final soon
[17:04] <GrueMaster> Will get and start testing it.
[17:04] <cgregan> There are some great VM image building instructions over with the cases on the wiki
[17:05] <cgregan> https://wiki.ubuntu.com/Testing/Cases/UMEinstall
[17:06] <cgregan> That's all I had on RC3
[17:06] <lool> Ok
[17:06] <lool> I'm currently spending my time on misc small bug fixes and on virtual-mobile-builder
[17:06] <cgregan> We should develop some method of alerting the community to new builds
[17:07] <cgregan> Can we have an action item for me?
[17:07] <lool> cgregan: I think it will make more sense when we actually spend the time to build more generic images; e.g. targetted at eepc
[17:07] <lool> cgregan: Also, marketing announces releases here
[17:07] <cgregan> Ahh
[17:07] <lool> cgregan: That said, I think you can happily take an action to talk to marketing to send announces about RC-N releases or betas
[17:08] <lool> In fact, these should be announced along the regular Ubuntu releases in the next cycle IMO
[17:08] <lool> (alpha 1, 2, 3, etc.)
[17:08] <cgregan> Will do
[17:08] <lool> [action] cgregan to talk to marketing about announcing pre-releases of UME
[17:08] <MootBot> ACTION received:  cgregan to talk to marketing about announcing pre-releases of UME
[17:08] <lool> Ok; if we're done with rc3, any other topic for today?
[17:09] <persia> cgregan: Might be worth also working with stgraber to get these as part of the ISO tracker (although these are not ISO images).
[17:09] <cgregan> Yes...there is already discussion on moving testing to ISO tracker
[17:09]  * persia likes alignment of effort
[17:10] <lool> Ok; I see no new topic on the wiki page, so I'll just take this occasion to warn people that they should be very very careful about uploads to the ppa
[17:10] <lool> The ppa is now our stable-updates testing area; once an update is tested, it will be promoted to the release archive
[17:11] <persia> lool: That's now for SRU candidates only, right?  New stuff should go into intrepid?
[17:11] <lool> persia: Exactly
[17:11] <lool> No new development or releases should happen in the hardy ppa; unless needed to fix a grave stable bug, but that's unlikely
[17:11]  * persia is willing to be a contact point for anyone having issues getting updates into intrepid (not always as uploader, but for process questions, etc.)
[17:11] <lool> Get in touch with me if you want to prepare such uploads and need guidance
[17:11] <lool> Or ask persia :)
[17:11] <bspencer> lool: there is also risk when image-creator changes.  I assume that can affect you too, tru?
[17:11] <bspencer> e
[17:12] <lool> bspencer: Where would it change?
[17:12] <lool> bspencer: We currently use the packaged image-creator which is in our ppa
[17:12] <bspencer> for example, it just changed to use autogen.sh
[17:12] <bspencer> ah, ok.
[17:12] <bspencer> no risk then
[17:12] <lool> Which has the new platforms for the release archive
[17:12] <lool> That new MIC should be targetted at intrepid now
[17:12] <lool> Not sure it was released though
[17:12] <bspencer> I haven'tused a packaged image-creator for over a yar
[17:12] <bspencer> year
[17:13] <lool> bspencer: That explains :)
[17:13] <bspencer> all our docs say to pull from the source and build/install
[17:13] <bspencer> and that the packaged one is out of date and uncertain
[17:13] <bspencer> :-\
[17:13] <lool> bspencer: All our docs say to install the package ;)
[17:13] <bspencer> cool.  glad it works actually
[17:14] <bspencer> I wasn't sure you were updating and testing with it.  Good news
[17:14] <lool> I can only use the packaged one
[17:14] <lool> It has many fixes we rely on
[17:14] <bspencer> are the platforms in the packaged version highly customizes?
[17:14] <bspencer> d
[17:14] <lool> bspencer: "highly" not really
[17:14] <lool> We add a couple of platforms
[17:14] <persia> bspencer: Sounds like a focus thing: it's likely best for upstream types to use VCS trunk directly, and for Ubuntu Mobile hackers to use the package, and push candidate changes in bug reports.
[17:14] <bspencer> well, I mean have you eliminated unused ones.
[17:14] <lool> One for mccaslin, one for menlow
[17:14] <bspencer> hardy+ppa
[17:14] <bspencer> and a new one for eeepc ?
[17:14] <lool> We didn't eliminated uneeded ones
[17:14] <lool> There's no platform for eeepc yet
[17:15] <bspencer> ok.  thx.
[17:15] <bspencer> persia: true, although we're all Ubuntu Mobile hackers (IMO)
[17:15] <lool> Another thing we change in the platforms we build against is that we drop most packages in fsets and use the ubuntu-mobile metapackage to pull things instead
[17:15] <bspencer> lool: right
[17:16] <persia> bspencer: Excellent :), although I suspect we won't all also be upstream as we grow.
[17:16] <lool> bspencer: I'm happy to work on making the packages better
[17:16] <lool> bspencer: In fact I've prepared a non-negligible number of patches for MIC
[17:16] <bspencer> lool: great
[17:16] <lool> Half of them aren't merged yet, so I wouldn't be able to move to a new MIC without rebasing them
[17:16] <bspencer> ok.  We'll do that after your UME release
[17:17] <bspencer> meaning -- we can focus on getting those things in
[17:17] <lool> That said, I would recommend you to publish packages of any app you tell users to use; that is, if you're unhappy about the age of our packages, we could of course try to fix that, or you could publish newer MIC packages in other repos
[17:17] <lool> because manually installed apps tend to break subtly with old files not being removed and generally mess up one's system
[17:18] <lool> How many times have I received bugs about crashes resulting from libs installed by the end user in /usr/local/lib  :-/
[17:18] <lool> Anyway, sorry, I'm getting offtopic :)
[17:18] <bspencer> got it
[17:18] <lool> I wish everybody a happy week then
[17:18] <lool> thanks for attending!
[17:18] <lool> #endmeeting
[17:18] <MootBot> Meeting finished at 11:21.
[17:18] <lool> djp: Back to you now
[17:19] <lool> djp: Concerning readyness, and availability; I would guess your questions are partly covered in the FAQ
[17:19] <persia> djp: Regarding architecture: the majority of code isn't actually architecture specific, although you may have some testing to do in order to verify it works on an alternate architecture (not that there are that many SPARC or PPC mobiles about)
[17:19] <lool> djp: if not, I'd be happy to complete it
[17:20] <lool> persia: technically, many bits are only enabled if arch == lpia though
[17:20] <persia> lool: True, but some of those cases are bugs
[17:21] <lool> persia: Yeah; it was a shortcut to do things like this
[17:21] <lool> And a nice shortcut, cause it is indeed much harder to do properly :)
[17:21] <persia> Very much so.
[17:22] <lool> What do you people use to push .debs to your kvm?  you publish them over http and then wget them?  push to a ppa?
[17:23] <persia> scp?
[17:23] <lool> I like being able to simply scp them, but I'm not sure I can reach my kvm
[17:23] <lool> at least I can't ping its ipv4 from my desktop
[17:23] <lool> I guess a different network backend would help
[17:23] <persia> Heh.  What are you using?  bridged?
[17:24] <lool> I think not; I'm using whatever is the default
[17:24] <lool> Let's try bridged
[17:24] <lool> i think it didn't work on my laptop, but wifi is too special
[17:24] <persia> Ah.  usermode.  You want to add iface br0 to /etc/network/interfaces
[17:25] <lool> persia: What do you pass kvm for bridged mode?
[17:27] <persia> lool: https://help.ubuntu.com/community/KVM will probably answer your next couple questions as well.
[17:31] <lool> persia: So I'm not too familiar with libvirt, but it seems either you create VMs without it and then configure each VM manually, or you create VMs with it, and then you need to use it
[17:32] <lool> Does that mean we should be using libvirt in virtual-mobile-builder by default and generate a libvirt command-line?
[17:34]  * lool needs to run out for a while
[17:34] <djp> lool: thanks for the info and the support, I'm trying to get an exiting new point of sales system built for my caffe (all FOSS, of course) and Remix looks like it might be perfect for the 800*600 touchscreens
[17:34] <persia> lool: I'm not sure.  I read that too, but am not awake enough to test much (having gotten up from a nap, and planning to sleep again in 85 minutes precludes coffee).
[17:36] <persia> djp: If you're looking at it from a PoS perspective, you'll have a bit of customisation to do anyway.  I'd recommend starting with matchbox, and seeing how much you want from the remix, from Ubuntu Mobile, and from other sources.
[17:36] <djp> lool: s/exiting/exciting
[17:37] <djp> persia: interesting.. matchbox, eh ?
[17:37] <djp> the PoS app in question is a java/swing thing
[17:37] <djp> guess that wouldn't precluse matchbox
[17:37] <djp> s/precluse/preclude
[17:38] <djp> but I don't see it as a pure appliance, as there are several other apps usefull from the register
[17:41] <persia> djp: Sure.  It's a matter of what you want to install.  Matchbox is just a window manager.
[17:41] <persia> I've only limited experience working with PoS installations, but I suspect that except for the touchscreen interface, most of the use cases are quite different.
[17:42] <persia> There's no reason you can't have a panel of some sort, perhaps with launchers for your kiosk tasks, etc. (but this gets quite off topic)
[18:00] <pmcgowan> bspencer, hey, what is the issue with having shared use of xulrunner between browser and home plugin?
[18:05] <lool> persia: I guess the page you sent me encourages moving to libvirt which will just do its things; I was happy to start vms with ./kvm-wrapper though; I also would like to keep network manager working on my ubuntu boxes, but I guess this conflicts with using bridges etc.
[18:05] <lool> vmwares manages to do it
[18:06] <persia> lool: Yeah, well, it's a matter of software maturity.  You can still configure the bridged networking without libvert.  I'll dig you up another page.
[18:10] <lool> Basically no perfect solution on http://kvm.qumranet.com/kvmwiki/Networking
[18:10] <lool> There's vde
[18:22] <persia> lool: Are you on wireless?
[18:23] <lool> persia: On the laptop, yes
[18:23] <lool> On the desktop, no; would still prefer keeping NM though
[18:23] <persia> lool: For the desktop, 3. public bridge from that page ought work, although it requires a bit of fiddling.
[18:23] <lool> The slirpvde thing allows to do basically the same thing tahn kvm hmm
[18:24] <lool> persia: Yeah, I'm used to such fiddling, but I know it's pretty much incompatible with NM then :-/
[18:24] <persia> For the laptop, you can create a fake eth0:1, and assign it some IP address, and use that (avahi-autoipd will do that for you: it's a bug for most people, but might be a feature for you)
[18:24] <lool> It looks like we don't have a transparent solution like vmware's in opensource
[18:25] <persia> Well, that's largely because we don't preload everything on the host.
[18:25] <lool> persia: Hmm you can use an alias in place of a tap?!
[18:25] <persia> vmware installs a mess of special interfaces on the host
[18:25] <lool> The kernel drivers behave differently
[18:25] <persia> Well, yes, but there are ways around that.
[18:26] <lool> For example the bridge will simply, well, be a bridge, but leave the IP address and all to your phys intf
[18:26] <persia> If we by default created 10 extra interfaces on the host for use by KVM, it would be easy.
[18:26] <lool> and the nat doesn't rely on iptables AFAIK
[18:26] <persia> You don't use the alias in place of the tap, just in the brctl line.
[18:26] <lool> Well you still wouldn't get NM support if you had a bridge
[18:27] <persia> brctl doesn't check link status, so as long as you can route, it works, and the kernel will shortcut rather than sending over the interface for localhost.
[18:27] <lool> Uh you're really adding an alias interface to a bridge
[18:27] <lool> It doesn't check it, it enforces it :)
[18:27] <persia> What?  You don't get nm support on the bridged interface, but that may not matter (hence using an alias)
[18:27] <lool> Not link status, but interface up/down-ess for sure
[18:28] <persia> Right, it only verifies the interface is up.  You don't need to connect a cable.
[18:28] <lool> It will bring the interface up if it's taken up and vice-versa
[18:28] <persia> This is frustrating for many people because they want behaviour to be controlled by link status, rather than interface status, but in your use case it's convenient.
[18:28] <lool> Bridges are cool when they work, but so ugly most of the time :-/
[18:29] <persia> Well, I guess.  I think they are always ugly, and prefer to have internal routing on virtual interfaces, but that's even messier to configure.
[18:29] <persia> (as you need an internal router, etc.)
[18:32] <lool> Oh well, I guess I'll go the full blown way, use libvirt, create a tap each time I start a VM, and route and NAT them
[18:41] <persia> lool: That's ideal, but annoying to set up.
[18:42] <lool> Definitely :-(
[19:32] <GrueMaster> davidm: ping - I'm looking at RC3, and the psb driver versions are all over the place.
[19:34] <GrueMaster> dri modules are 0016, xorg module is 0014, kernel module is 0010.
[21:22] <GrueMaster> davidm: ping - I'm looking at RC3, and the psb driver versions are all over the place.
[21:22] <GrueMaster> dri modules are 0016, xorg module is 0014, kernel module is 0010.
[21:22] <GrueMaster> what happened?
[21:25] <davidm> It is not any different then RC-2
[21:26] <GrueMaster> Unfortunately, RC2 slipped in under the radar.  I didn't know about it or RC3 until this morning's meeting.
[21:26] <GrueMaster> But RC1 had all 0014 builds of the psb driver set.  That's why my concern.
[21:48] <davidm> GrueMaster, the next kernel update release will have the latest drivers, we had to go out this way to get into the hardy upgrade tree which is a huge win long term for updates and upgrades.
[21:49] <davidm> Unless you find some critical issue we are going to go final on this and go with the upgrade later, as I told Don last night.
[21:49] <davidm> As far as I am concerned it's a release.
[22:42] <GrueMaster> amitk:  I'm downloading the -19 kernel now.  Do you know what version of the psb kernel module is in this?
[23:31] <amitk> GrueMaster: 0016
[23:32] <GrueMaster> I see that now, thanks.  Looks ok so far.  I sent you an email.


[18:45] <ibeardslee> morning
[18:47] <Atamira> morning
[18:47] <Atamira> looks like a nice day up this way
[18:50] <ibeardslee> looking nice so far down here
[18:52] <Atamira> not bad for midweek
[18:57] <chilts> morning
[18:59] <snail> morning
[19:18] <ajmitch> morning
[19:18] <ajmitch> it'd be nice if I could see something on my screen
[19:21] <Atamira> put your glasses on
[19:22] <ajmitch> it's more that the monitors face the window
[19:22] <ajmitch> & it's really nice & sunny outside
[19:26] <Atamira> ahh. thats a pain
[19:27]  * ajmitch wonders why his google+ stream is empty now :)
[22:09] <ojwb> ajmitch: probably some new social networking site is where the action is now
[22:12] <ajmitch> people are just so fickle
[22:17] <mwhudson> morning
[22:23] <ojwb> oh yes, morning
[22:54] <snail> just


[00:38] <Twelf> Hi guys/girls, I'm confused as to how to restructure my repository to allow better developer visibility into each other's branches. I have set things up like this: http://wiki.bazaar.canonical.com/SharedRepositoryLayouts#nested-style-project-branch-sub-branch
[00:39] <Twelf> If Alice creates a new feature branch in "project/alice/featureA", how can the other developers know that she created such a branch?
[00:40] <AuroraBorealis> i dont think bzr will tell you, just gotta look or something
[00:41] <Twelf> Hm yeah, this is not what I want then. Can you think of an alternate configuration (or some kind of plugin or web interface) that would make feature creation more visible?
[00:41] <AuroraBorealis> http://doc.bazaar.canonical.com/bzr.dev/en/user-reference/hooks-help.html
[00:42] <poolie> Twelf, how do you want them to be told?
[00:42] <AuroraBorealis> so it seems you just write a simple plugin
[00:43] <AuroraBorealis> and then do in python however you want them to be notified, email, whatever
[00:43] <Twelf> poolie: well, ideally, just by pulling project/alice
[00:43] <Twelf> or some bzr command I'm not aware of
[00:43] <poolie> ok i thought you meant you wanted them to be mailed or something
[00:44] <AuroraBorealis> you could have it branch to their machine by using python right?
[00:45] <Twelf> hm, I'm not sure
[00:46] <Twelf> I think I am operating under the mistaken assumption that a shared repo enables this sort of functionality
[00:49] <Twelf> maybe multi-pull in bzrtools would help
[00:51] <poolie> yes i think that's what you want
[00:51] <poolie> that will soon be built in
[00:51] <poolie> as part of
[00:51] <poolie> https://lists.ubuntu.com/archives/bazaar/2012q1/074217.html
[00:51] <AuroraBorealis> what does multi pull do
[00:52] <poolie> pulls all the branches from one repository
[00:52] <AuroraBorealis> even if they are nested ?
[00:53] <AuroraBorealis> like in that workflow twelf linked, where you have a branch that contains another branch, etc
[00:54] <poolie> in a sub directory?
[00:54] <poolie> i think it only goes down one level
[00:54] <AuroraBorealis> http://wiki.bazaar.canonical.com/SharedRepositoryLayouts#nested-style-project-branch-sub-branch
[00:54] <AuroraBorealis> i'm confused on if that workflow ^ means that every folder is its own branch or not, since bzr doesn't support that
[00:54] <AuroraBorealis> so i think feature1 and feature2 are just folders?
[00:55] <poolie> featureA will be a directory containing a .bzr/branch
[00:55] <Twelf> yep, that's what it looks like in my test
[00:56] <AuroraBorealis> so the top level directory has a 'trunk' folder too (thats not shown)?
[00:56] <AuroraBorealis> it says its a shared repo and a branch
[00:57] <Twelf> I created a shared repo at "project", and then "project/trunk", "project/alice", "project/bob", "project/bob/featureA", etc.
[00:58] <AuroraBorealis> yeah ok.
[00:58] <Twelf> I wonder if bzr_access will be compatible with the new colo stuff. I do need to restrict access for some developers to certain branches
[00:58] <AuroraBorealis> docs are slightly confusing in that regard, since it doesn't support nested branches (like svn)
[00:58] <poolie> biab
[00:58] <Twelf> thanks poolie
[07:32] <vila> hi all !
[09:12] <mgz> morning!
[09:13] <vila> morning mgz !
[09:55] <hariom> Hi, it appears that I have hit the bug where pycurl is not verifying the self signed cert. Is there any solution?
[09:57] <mgz> what version of bzr and what platform?
[09:59] <mgz> what you probably want is to install the self signed cert into your system's location for certificates
[10:01] <hariom> mgz:    bzr = 2.4; ubuntu: 10.04 LTS
[10:03] <mgz> so, try copying the .pem to /etc/ssl/certs then run update-ca-certificates
[10:03]  * mgz is just googling this
[10:25] <chmac> Can I see the history of a file if it was previously deleted, then a new file of the same name created?
[10:26] <mgz> yup.
[10:26] <mgz> ...what, you want to know how? :)
[10:26] <fullermd> Yes, although how is always the opposite of the way I want.
[10:27] <chmac> mgz: Yes please :-)
[10:28] <mgz> fullermd, please enlighten us.
[10:28] <fullermd> A number of commands can take a revision and a filename.  IME, they all lookup the fileid from the filename as of that revision, except for the ones where I want it to lookup the filename as of current and backtrack to that rev.
[10:29] <fullermd> And I think I meant "except that" there.  Dunno.  Viri stealing my brainz.
[10:29] <mgz> basically `bzr log -r<a revision the file existed> <the filename at that point>` should work
[10:30] <mgz> alternatively you can find the fileid, then use that in some places
[10:30] <fullermd> Probably have to dig through logs to find the rev where it was deleted, then do something like `log -r0..$THAT $FILE`.
[10:30] <fullermd> Or maybe ..before:$THAT, since in $THAT it's deleted.
[10:30] <fullermd> I've wished for the ability to explicitly pass fileid's to things like log/diff/etc a number of times in the past   :|
[10:32] <mgz> that might make a few things easier indeed.
[10:33] <chmac> mgz: Thanks, I'll look into it now
[10:36] <chmac> Awesome, thanks folks, I have my old my.cnf back thanks to etckeeper :-)
[10:37] <mgz> good good :)
[10:37] <mgz> hm, dulwich has a copy of the lru_cache module
[11:43] <libertas> hi, I have a conflict I've not been able to resolve: Path conflict: bin/update_bds.OTHER / <deleted>
[11:43] <libertas> the file is not there, how can I do this?
[11:49] <mgz> libertas: `bzr resolve bin/update_bds.OTHER` probably
[11:49] <mgz> though as it's an OTHER file you may have done something a little wrong during the merge, so I'd double check the diff of changes as well
[11:50] <libertas> it resolved now, strange, I guess I was inside bin/ and it wasn't doing it...
[11:50] <libertas> mgz thank you!
[11:51] <fullermd> That probably means that you deleted the file in your branch, and the branch you merged made changes to it.
[13:05] <mgz> okay, first upgrade pain, consolekit hung itself
[13:08] <fullermd> Luckily, that never happens to me.  At least, I don't think it does.  I dunno how I'd know if it did.  Or what it is...
[13:11] <mgz> I suspect freebsd saves you from such an 'upgrade'
[13:11] <fullermd> Well, as near as I can tell at a glance, it's some internal bit of gnome.  Not messing with such a thing also saves me  :p
[13:26] <crisb> can anyone recommend an approach to me regarding automatically updating a bug tracker when --fixes is specified on commit? ie should this be done at the repository side, if so how to do this from a push request?
[13:27] <crisb> i'm thinking it must be the repository side so that a public branch name is available
[15:39] <LarstiQ> crisb: trac-bzr might have some way of doing that?
[15:40] <LarstiQ> Jesdisciple: concerning your commit message, if I understood it correctly: an editor pops up, write your message, and save and quit the editor
[15:41] <LarstiQ> crisb: so you can have a hook local when the commit happens, or in some central location that gets pushed to (smart server hook if you use that, or then cron/inotify/something like that)
[17:27] <iamben> hello sirs.  is threads support on python required unconditionally for bzr?
[17:28] <mgz> no. but we use the logging module which imports it.
[17:29] <mgz> dummythreading should be enough
[17:29] <mgz> +_
[17:32] <iamben> so this logging module can be disabled? simple "bzr init-repository --no-trees <repo-addr>" errors w/o threads support
[17:34] <mgz> python should work still provided you have the dummy_threading module
[17:34] <mgz> what's the extact error?
[17:34] <mgz> !pastebin
[17:35] <iamben> http://paste.pocoo.org/raw/548446/
[17:35] <iamben> i know that i can fix it by adding threads support, i just want to make sure my distro has their dep list correct
[17:38] <mgz> ah, that looks like our fault
[17:38] <mgz> try hacking in something like:
[17:38] <mgz> import dummy_thread
[17:38] <fome> hi, im trying to branch a package of launchpad and i allways get this error: bzr: ERROR: Revision<EMAIL_ADDRESS>not present in "Graph(StackedParentsProvider(bzrlib.repository._LazyListJoin(([CachingParentsProvider(None)], []))))".
[17:38] <fome> any idea what that means?
[17:38] <mgz> sys.modules['thread'] = dummy_thread
[17:49] <iamben> mgz: i'm no python guy but i hacked these 2 lines into /usr/lib64/python2.7/site-packages/bzrlib/bzrdir.py and it works, is that what you were thinking?
[17:49] <mgz> anywhere will do, it's a global change
[17:50] <mgz> I was thinking of the bzr script, but shows that dummy_thread is enough
[17:50] <mgz> grepping shows we only use thread.get_ident except in the smart server and testing using the smart server
[17:51] <jelmer> fome: hi
[17:51] <jelmer> fome: I think that can be avoided by disabling the up-to-date-ness check in bzr
[17:51] <iamben> mgz: /usr/bin/bzr is some kind of wrapper script on gentoo, i'll just report this and let our bzr and/or python maintainers decide what to do, thanks
[17:53] <fome> jelmer: how would i go about that?
[17:53] <iamben> mgz: is this dummy_thread module a kind of "safe fallback" that will use threads when available, or do we need to use it conditionally ONLY when threads are not wanted?
[17:54] <mgz> iamben: I'm not clear from the python documentation on who the onus to do this fallback is,
[17:54] <jelmer> fome: set launchpad.packaging_verbosity=False in the configuration
[17:54] <lifeless> iamben: I suggest you just require a threaded python
[17:54] <mgz> either every python module that uses either the thread or threading module,
[17:55] <lifeless> iamben: pretty much /every/ build of python out there that isn't on tiny embedded systems is threaded.
[17:55] <mgz> or the maintainers of python distributions that build without threading enabled
[17:55] <iamben> i'll just report with a suggestion to force threading, and mention the possibility of dummy_thread
[17:57] <jelmer> iff building without thread support is really something we want, then I'd argue this is a bug in the logging module
[17:58] <mgz> well, I think logging actually uses threading, which *does* fall back to dummy_threading correctly
[17:58] <mgz> but thread does not automatically fall back to dummy_threading
[17:58] <mgz> and a few of the smart bits import it just for get_ident (the actual smart server does want to start threads),
[17:59] <mgz> but for some reason we're pulling in enough in bzrdir to import thread in some train from there apparently
[18:01] <jelmer> hmm, odd
[18:01] <jelmer> anyway, EOD.. time for some lp hacking :)
[18:02] <mgz> that's what I'm guessing from the traceback and grepping around at any rate, I've not actually traced it
[18:03] <mgz> I need to finish bending twisted to my will first...
[18:44] <mgz> gah, that was a silly error to waste half an hour on
[19:02] <LarstiQ> mgz: twisted?
[19:04] <mgz> don't ask >_<
[19:05] <mgz> the best way I found of debugging this test was waiting the 120 seconds for the timeout
[19:05] <mgz> there was a timeout param on an object that din't actually change the duration
[19:23] <LarstiQ> mgz: d'oh
[19:27] <mgz> I think there are probably cleverer ways of doing lots of these things but I've yet to learn them
[19:28] <mgz> okay, done
[19:28] <mgz> time to head down
[19:32] <wgz> hm, now what
[19:38] <LarstiQ> wgz: should I close a bug as Inv
[19:39] <LarstiQ> alid if work somewhere else has already taking care of it?
[20:14] <wgz> LarstiQ: hm.
[20:15] <LarstiQ> s/taking/taken/
[20:15] <wgz> in this case that's probably the best option,
[20:15]  * LarstiQ was looking for a "Not For Us" option
[20:15] <wgz> as we want a record of the bug, but aren't going to be changing how we use os.listdir for this reason
[20:16]  * LarstiQ nods
[20:39] <bdmurray> I've noticed that the update-manager branch for lucid is out of date
[20:39] <bdmurray> Is there something that can be done to fix this?


[01:26] <LeoNerd> Hrmm.... My bzr-git plugin seems to be unhappy
[01:26] <LeoNerd> bzr: ERROR: exceptions.AttributeError: 'BazaarObjectStore' object has no attribute 'get_graph_walker'
[01:27] <LeoNerd> bzr on native things works fine, but can't pull or dpush a git remote
[01:43] <LeoNerd> Ah.. So I'm still running 0.6.12 out of debian, but I see there's a 0.7. I'll try that first
[01:47] <LeoNerd> Hrmmm.. so I have done  bzr co lp:bzr-git  in my  .bazaar/plugins  directory and renamed the dir to just  git
[01:47] <LeoNerd> But, still  bzr plugins  claims 0.6.12 (the debian version)
[01:51] <LeoNerd> Ohwait.. the fetched plugin code also says 0.6.12.
[01:51] <LeoNerd> https://answers.launchpad.net/bzr-git/+question/240033  <== appears to be my problem. No idea how to solve it yet :/
[01:55] <LeoNerd> Looks like Jelmer's work, only he doesn't appear to be here
[11:38] <canobi> Hi and happy hollidays! Got a question - I need a repository "mirror", and don't know if I'm on the right track. An example would describe it best, so: let's say I have a library I'm developing and keeping the code in my private central repository. However, I want this library to be accessible by outside people, and so I make another, publicly accessible repo. I also want outside people to be able to send merge requests via my outside repo, and then I would me
[11:38] <canobi> All changes would then be replicated back to outside repo so anyone can access them. Can this be done, and how?
[12:32] <mgrandi> you can just do a branch, a branch mirrors it =P
[12:33] <mgrandi> and possibly bound branches
[12:34] <mgrandi> and now its 5 am, i must sleep =P
[14:32] <canobi> \part
[16:51] <Ebe123> bzr: ERROR: Couldn't import bzrlib and dependencies.
[16:51] <Ebe123> Please check the directory containing bzrlib is on your PYTHONPATH.
[16:51] <Ebe123> Traceback (most recent call last):
[16:51] <Ebe123>   File "/usr/local/bin/bzr", line 74, in <module>
[16:51] <Ebe123>     import bzrlib
[16:51] <Ebe123> ImportError: No module named bzrlib
[16:51] <Ebe123> Help?
[16:51] <Ebe123> Hi, I'm trying to get the Bazaar GUI. I typed "bzr explorer" in Mac OS X Mavericks terminal, but got the error: "


[01:53] <rick_h_> greg-g: https://plus.google.com/u/0/116120911388966791792/posts/RCmDjwDdZj1
[01:56] <rick_h_> bah I fail https://plus.google.com/u/0/116120911388966791792/posts/XhKWQRxK7Zm
[02:39] <jjesse> greg-g, happy birthday according to google
[02:42] <greg-g> jjesse: heh, I should update that.
[02:43] <greg-g> never trust a Jan 1st bday on a social network ;)
[02:43] <greg-g> my bday is actually July 2nd
[02:43] <jjesse> i did a google search and it said "tell greg-g happy birthday"
[02:43] <jjesse> and i was pretty sure that wasn't it :)
[02:43] <greg-g> heh
[02:43] <greg-g> I wondered why I got 2 bday texts today :)
[02:49] <brousch1> greg-g: I don't suppose you'll be in MI at the end of the month? We may be having an open source philosophy meeting at GrWebDev
[02:53] <brousch1> Hm, maybe we could do remote Q&A
[02:58] <greg-g> brousch1: huh, awesome, but no, I leave on Saturday morning
[02:58] <brousch1> Darn
[03:09] <widox> greg-g: hey, Jan 1 _is_ my bday :p
[03:29] <Blazeix> widox: happy birthday :)
[03:32] <widox> Blazeix: thanks!
[03:50] <snap-l> widox: Happy Birthday!
[03:50] <snap-l> You share your birthday with the Gregorian calendar.
[12:49] <Wolfger> Happy New Year!
[13:03] <snap-l> Happy New Year to you too, Wolfger!
[13:05] <brousch> Welcome back to work!
[13:05] <rick_h_> booooooo
[13:05] <rick_h_> man, great day to drop off the boy at day care...phew
[13:06] <brousch> Bad morning?
[13:06] <brousch> My kid woke up at 5-5:30 every morning on vacation, but slept until 6 this morning
[13:07] <rick_h_> my wife had to work so I had him each morning. After going through 8 pairs of underwear/pants yesterday...glad to drop him off :)
[13:07] <brousch> ouch
[13:09] <brousch> http://i.imgur.com/P5n5r.png
[13:17] <rick_h_> lol
[13:30] <Wolfger> heh
[13:31] <Wolfger> back to work isn't so bad. Almost hitting a deer on the final mile of the long commute in wasn't fun though.
[13:31] <rick_h_> woot
[13:32] <brousch> You have deer in Detroit? I thought it was all wild dogs and squirrels
[13:32] <rick_h_> had them in our back yard twice
[13:34] <Wolfger> I'm out in Whitmore Lake today
[13:34] <Wolfger> though I have heard of deer in Detroit, never actually seen one
[13:35] <Wolfger> more squirrels than you can shake a pack of wild dogs at
[13:36] <snap-l> We have deer in the suburbs
[13:37] <Wolfger> Yes indeed. But as a native Detroiter, I seldom refer to anything North of 8 Mile as Detroit
[13:38] <Wolfger> And never to anybody from Michigan. The further away from Michigan you go, the more of the state Detroit occupies. :-D
[13:48] <brousch> I use Detroit to refer to anything East of 23 and South of (including) Flint
[13:49] <brousch> Mostly because it irritates anyone who doesn't live in Detroit proper
[14:04] <Wolfger> LOL
[14:05] <Wolfger> When I go to Japan, all of the lower peninsula is Detroit.
[14:06] <Wolfger> ...and I don't think they know the UP exists
[14:57] <greg-g> Wolfger: many americans don't know the Up exists
[14:58] <rick_h_> they're canadian wanna-bes :P
[15:18] <Wolfger> ya, eh?
[16:07] <snap-l> Oy eh
[17:06] <rick_h_> http://www.omgubuntu.co.uk/2013/01/ubuntu-product-launch-omg-google-hangout
[17:19] <jrwren> 25more minutes
[17:44] <Wolfger> do we have an inside scoop on what the announcement will be?
[17:44] <Wolfger> or is, or was? I might be a bit late in responding :-p
[17:45] <rick_h_> 15 more min
[17:49] <jrwren> oh, what? they aren't doing it on time?
[17:49] <rick_h_> 1pm isn't it?
[17:49]  * rick_h_ checks timezones again
[17:49] <jrwren> 17:45 is what it says
[17:49] <Wolfger> site says "event has passed"
[17:50] <rick_h_> http://www.ubuntu.com/ 10min
[17:50] <rick_h_> hmm, seems something confused on OMG Ubuntu
[17:50] <rick_h_> there we go
[17:50] <rick_h_> hangout is on the page now
[17:50] <rick_h_> http://www.omgubuntu.co.uk/2013/01/ubuntu-product-launch-omg-google-hangout
[17:50] <jrwren> hangout is up
[17:51] <rick_h_> oh heh, this is just OMG ubuntu chat hangout
[17:51] <jrwren> yup
[17:51] <jrwren> weak
[17:51] <rick_h_> guess I'll keep reloading the main site
[17:52] <Wolfger> hmm. can't seem to get my audio working on the laptop today.
[17:52] <Wolfger> oh well. Back to work
[18:04] <snap-l> Oh yay, a phone with Ubuntu on it.
[18:05] <snap-l> I'm not sure why I should be getting excited over this. :)
[18:07] <lmorchard> Tired : Apple keynote / Wired : Ubuntu keynote?
[18:08] <jrwren> i can't get to ubuntu.com, LOL
[18:08] <snap-l> I can't get excited over mobile
[18:09] <snap-l> I mean, I love my phone, don't get me wrong
[18:09] <jrwren> why not?
[18:09] <snap-l> and I see where this could be a smart move
[18:09] <jrwren> if enough people had open phones and we all did a mesh, we wouldn't need phone companies :p
[18:10] <snap-l> Maybe it's because I think phone companies are a bag of assholes
[18:10] <lmorchard> assholes powering pinwheels
[18:44] <rick_h_> derekv: you coming to CHC?
[18:50] <jrwren> if it is all open source, I totally want an ubuntu phone
[18:54] <brousch> They should hand them out to Canonical employees to eat their own dogfood
[18:59] <_stink_> then we steal it from them?
[18:59] <rick_h_> hah
[18:59] <Blazeix> it sounds interesting, as long as they don't try to tie it to their cloud offering
[18:59]  * rick_h_ does run a galaxy nexus though...
[18:59] <rick_h_> Blazeix: :P
[18:59] <brousch> _stink_: Yeah. Beat them up and steal their phones
[19:00] <_stink_> enlist Wolfger
[19:04] <snap-l> Heh
[19:04] <snap-l> Yeah, the OSS aspect is the most appealing to me
[19:04] <snap-l> but outside of that, Android has really captured my heart.
[19:05] <snap-l> That said, if I can program the thing without using Java, I'm all ears. ;)
[19:05] <lmorchard> Since I'm working on some B2G bugs at Mozilla, this ubuntu phone business is relevant to my interests
[19:06] <snap-l> B2G =?
[19:06] <lmorchard> FirefoxOS
[19:06] <snap-l> Ah, WebOS 2.0. ;)
[19:06] <lmorchard> Phones that boot straight into a stripped down Firefox and run web apps
[19:06] <lmorchard> Pretty much, yeah
[19:06] <snap-l> lmorchard: CHC tonight?
[19:07] <snap-l> It's not snowing like hell. ;)
[19:07] <lmorchard> Hmm, I don't think I can make it tonight :/ But, next week perhaps
[19:07] <snap-l> You're near Campbell road, right?
[19:07] <lmorchard> Maybe I can come and do show & tell with my FirefoxOS dev phone and this chromebook I shoehorned ubuntu onto
[19:08] <snap-l> If you need a ride, I'll drive.
[19:08] <lmorchard> Oh, heh, no, just got plans with the missus
[19:08] <snap-l> Ah, no worries then
[19:08] <lmorchard> I'm now at crooks & washington, so I have less excuse than ever to miss CHC
[19:08] <snap-l> I think I pass right by you
[19:09] <snap-l> I usually take 11 mile
[19:10] <lmorchard> Hmm, my evening plans may fall through, so I may yet go to CHC
[19:11] <brousch> snap-l: Kivy
[19:12] <brousch> snap-l: Don't even need Eclipse!
[19:15] <_stink_> wow
[19:15] <_stink_> neat
[19:18] <brousch> So the Ubuntu SDK uses QML (Qt modeling language)?
[19:27] <nullspace> anyone else having issues with the secs.oakland.com mirrors
[19:29] <nullspace> just switches to archive.ubuntu mirrors and there is a massive number of packages for update that I didn't get on the secs mirror, there may be more to this but this update is taking a fair bit of time to complete
[19:47] <jcastro> ping the admin
[19:47] <jcastro> maybe it's not syncing enough
[19:58] <nullspace> wow cups and openjdk-7-jre was busted
[19:58] <nullspace> I don't know who the admin is
[20:06] <jrwren> if only the ubuntu phone ui used e17 like the samsung phones :p
[20:08] <brousch> They need a command line install so you can apt-get install unity-phone or plasma-active or tiled-phone-ui-of-the-month
[20:29] <brousch> Is the Ubuntu on Nexus7 the same as Ubuntu on phones?
[20:32] <jcastro> no, ubuntu nexus is just normal ubuntu
[20:34] <snap-l> I think we should call Ubuntu on phones ibinti
[20:35] <snap-l> Aparently in Tagalog it means the calf of the leg.


[07:39] <ppisati> morgen *
[07:44]  * apw peers blearily out on the world
[07:45] <jk-> hey apw
[07:45] <jk-> and hello ppisati
[07:45] <apw> jk0 heya
[07:50] <ppisati> hey
[08:49] <apw> cnd, hey!
[08:50] <cnd> howdy!
[09:28] <cking> cnd, welcome to sunny UK
[09:36] <cnd> cking, thanks :)
[09:36] <cnd> weather seems nice here
[09:37] <cking> it's unbelievable warm for the time of year at the moment
[09:37] <cking> unbelievably even
[09:37] <cnd> heh
[10:26] <diwic> Sweden's so cold Facebook's planning it's next facility in northmost Sweden. :-)
[10:27] <diwic> cking, but currently I share your analysis, it's quite warm here as well.
[10:27] <diwic> s/it's/its
[10:36] <cking> heh
[10:39] <cking> apw, I fakeroot doesn't seem to exist on tangerine's oneiric chroots - am I going mad, or has somebody removed it recently?
[10:42] <apw> cking, checking
[10:45] <cking> methinks apw is installing it now for me
[10:45] <apw> heh whyso ?
[10:45] <cking> it's now working for me
[10:46] <apw> really now that is odd
[10:46] <cking> you messing with my mind? ;-)
[10:46] <apw> not for me
[10:47] <cking> I could never get the hang of mondays
[10:52] <apw> Picking 'linux-meta' as source package instead of 'linux'
[10:52] <apw> wtf ... why would you do that
[10:54] <apw> something is very wrong with pretty much everything to do with the chroot creation, i am applying some hammers
[10:58] <apw> bah, the damn arm cross tools again, are uninstallable
[10:58] <cking> a stick of TNT may be more appropriate
[10:58] <cking> doesn't anyone check this kind of stutff?
[11:02]  * ppisati -> reboot in Oneiric
[11:43] <diwic> apw, any idea of how we are from 3.2 merge window opened? I think I read something about Linus taking a vacation, but not for how long...?
[11:50] <apw> diwic, no more specific information than you suggested, we would expect a release 'now' really
[11:50] <apw> then i'd expect the merge window the next week
[11:50] <diwic> apw, ok
[11:51] <apw> if he vacs then yes he often shoves it in the gap, and we wait a little longer, but not much more
[11:51] <diwic> how long does he go for vacation usually?
[11:52] <cking> depends if he goes diving and runs out of oxygen
[11:52] <apw> a week normally
[11:53] <diwic> apw, so I good guess would be release this week, next week vacation, week after that would be merge window?
[11:56] <apw> yeah, he may have a longer merge window with his vac in it too, thats happened before
[11:56] <apw> but, anything not already in a maintainers tree by now, isn't likely to make it unless its a bugfix
[11:57] <diwic> but merging new features would then be accepted by the end of the merge window as well, no strict "regressions only" stuff.
[11:58] <diwic> hrm ok
[12:01] <diwic> so this practically leaves me ~1 day to finish off all new kernel features for 12.04.
[12:10] <apw> if we have 3.2 yes probabally, it is hard to know which will actually be in the release this early
[12:10] <apw> it depends more on external factors than anything else
[14:01] <brendand> sconklin - is the maverick kernel getting respun?
[14:06]  * ogasawara back in 20
[14:11] <sconklin> brendand, probably not, I think that failure turned out not to be a kernel problem.
[14:15] <brendand> sconklin - aha. should we go ahead with cert testing then?
[14:16] <brendand> sconklin - i'll get hggdh to update the bug
[14:16] <sconklin> Not until The QA status is definitively decided. I think hggdh said it was ok, but the task status and tag should be set to PASS if it is
[14:21] <hggdh> sconklin, brendand: if you are talking about bug 854092 then it is a pass from QA -- problem is at AWS
[14:21] <ubot2> Launchpad bug 854092 in kernel-sru-workflow/certification-testing "linux: 2.6.35-30.60 -proposed tracker" [Undecided,Confirmed] https://launchpad.net/bugs/854092
[14:22] <sconklin> hggdh, then in order to proceed, the tag has to be changed from a fail to a pass
[14:23] <hggdh> just did it
[14:23] <apw> (preferably with an expplanation in the bug as to why its ok to switch it)
[14:24] <hggdh> but I think this pass override should come from whoever worked on the bug, not me. In this case smb and I worked on it, so I was fully aware. But generically, an override should come from elsewhere
[14:36] <herton> hggdh: hardy was also tagged as failed, problem in the same test as maverick, is it also the same issue?
[14:40] <apw> smb is off today so he won't be commenting ....
[14:42] <hggdh> herton: indeed
[14:45] <hggdh> herton: tagged -passed
[14:45] <herton> ok thanks
[14:46] <hggdh> sconklin: we need to work out this retagging
[14:46] <hggdh> (in general)
[14:56] <sconklin> hggdh, I agree, it should be set to pass by whoever 'makes the decision', in this case smb
[14:57] <hggdh> sconklin: thank you. In this case, I explicitly asked smb about it, so we are cool
[14:58] <bjf> sconklin, not sure i entirely agree with that, QA "ownes" that stage so it should be they that makes any changes regarding it
[14:58] <bjf> sconklin, my thinking in this case is that smb, makes the case to hggdh that it should pass and hggdh should set the state and reset the tag
[14:58] <hggdh> bjf: QA owns the test, and takes a decision based on the test results. Once a bug is opened, the subject matter experts can decide
[14:59] <hggdh> bjf: this would be an override. Overrides are signed by whoever decides
[14:59] <sconklin> bjf, that was indeed my original thinking on this, that no one outside of the assigned team should be changing status or tags.
[15:00] <bjf> sconklin, that is my beliefe
[15:00] <sconklin> Because responsibility should now be delegated outside the assignee.. I think this needs further discussion so that we're all in agreement with whatever we decide to do.
[15:01] <sconklin> another problem is that almost any case where an override is required is going to be vaguely defined and impossible to anticipate in our process documentation
[15:02] <bjf> sconklin, i don't think that delegation of responsibility should be part of the process
[15:02] <hggdh> we really need to figure this out. This is not delegation, but override; an entirely different beast
[15:03] <sconklin> but we can not determine a priori who should have the ability to make an override.
[15:03] <sconklin> I do see bjf's point
[15:04] <hggdh> there is that. We can simplify by requiring the subject matter expert to formally add an entry in the bug; what I do not like is QA taking the decision without visible reason
[15:05] <hggdh> so the final decision will be from whoever owns the task
[15:06] <hggdh> but this should be made clear.
[15:06] <hggdh> In other words: explanation of why the decision can be overriden comes from the subject matter experts; final decision from the step/task owner
[15:07] <hggdh> (this actually applies to any SRU, not only kernel)
[15:09]  * apw thinks that sounds about right, we have to convince you, if we cannot do that you do not change
[15:12] <sconklin> I think that sounds right. So ultimately it is the responsibility of the asignee to complete that task, by involving subject experts as required
[15:13] <apw> to look at it the other way round, it is qa's sign off, if they are signing off they had better be happy, if we want them to be happy we'll have to work at it :)
[15:15] <hggdh> this actually should be applied to all tasks, and for success or failure
[15:16] <hggdh> sconklin: er. Should we, then, *not* complete a task if there is doubt? Or should we fail, and then override if needed?
[15:16] <sconklin> https://github.com/sickill/git-dude looks handy, although I wonder if it won't lead to excessive fetches on upstream repos
[15:17] <sconklin> If the test fails, mark it a fail and open a bug. If the outcome turns out to be wrong (i.e. a success), then go back and change it.
[15:18] <hggdh> agreed
[16:06] <gema> hggdh: I don't think anyone but QA should be changing a test case from fail to pass
[16:07] <gema> as apw  says, they should convince us :)
[16:07] <gema> sorry, I have come too late to the conversation, probably
[16:09] <hggdh> gema: I am not sure, but I accept the reasoning. And yes, I think you got in too late ;-)
[16:09] <gema> hggdh: normally when you have to change a test case from fail to pass there is more to it than that
[16:09] <gema> it is likely we'll have to do some follow up and add another test case or so
[16:10] <gema> I was just trying to understand the process based on the conversation
[16:10] <gema> not sure what changing from fail to pass means in this context, so don't mind me too much x)
[16:10] <apw> i think its important that a QA sign off is something QA stands behind, as that is where the QA 'veto' comes from, a no means no there
[16:11] <gema> apw: I agree, if I think it's a fail and you don't have a good reason why it is not a fail, I won't change it
[16:12] <gema> and you don't change just the result, I presume you change the condition that makes the test fail and re-run?
[16:22] <komputes> Does anyone see anything on this screen that might indicate why 64-bit won't boot on a Thinkpad X220? https://launchpadlibrarian.net/81019072/IMG_0749.JPG
[16:22] <komputes> Full bug here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/853085
[16:22] <ubot2> Launchpad bug 853085 in linux "general protection fault: 0000 [#1] SMP " [Undecided,Confirmed]
[16:23] <hggdh> gema: in this case, we were discussing a bug found while checking; the bug is outside the checking scope (but driven by it).
[16:24] <gema> hggdh: yep, I was looking at it now, thanks :)
[16:24] <hggdh> gema: further analysis on this (new) bug shows an issue outside the kernel -- so there is nothing to change in the test process (except now look for a new error condition)
[16:24] <gema> hggdh: I thought it was interesting to jump in because you were talking about agreeing on a process
[16:24] <gema> hggdh: so I wanted to understand the problem further
[16:24] <hggdh> k
[16:25] <gema> hggdh: understood, so the test case needs changing
[16:25] <gema> hggdh: I find pretty difficult to decide whether a test passes or fails with our current process
[16:25] <hggdh> actually, both the test conditions and the process
[16:26] <hggdh> gema: better we get back to #qa to discuss it
[16:26] <gema> hggdh: sure
[17:39] <tgardner> apw, gomeis/tangerine gcc-arm-linux-gnueabi in oneiric schroot
[17:39] <tgardner> installed in*
[17:52]  * tgardner -? lunch
[19:28]  * jjohansen -> lunch
[22:42] <jonpry> anyone notice that the ubuntu.kernel.org ppa is out of disk space?


[00:11] <adueppen> I might get to the meeting a bit late depending on when I have dinner
[00:25] <tsimonq2> ok :)
[00:58] <tsimonq2> o/
[00:58] <tsimonq2> mikeputnam1: you around?
[00:59] <tsimonq2> IvanR_: you around?
[00:59] <tsimonq2> adueppen: o/
[00:59] <adueppen> tsimonq2: ;
[00:59] <tsimonq2> lol
[01:00] <tsimonq2> #startmeeting
[01:00] <meetingology> Meeting started Sat Jan  2 01:00:55 2016 UTC.  The chair is tsimonq2. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[01:00] <meetingology> Available commands: action commands idea info link nick
[01:02] <tsimonq2> sooo is anyone around besides adueppen?
[01:02] <adueppen> tsimonq2: ping everyone
[01:02] <tsimonq2> adueppen: I already did :P
[01:02] <adueppen> oh didn't see that there
[01:02] <tsimonq2> adueppen: I already know h00k is enjoying time away
[01:03] <tsimonq2> adueppen: so anything notable you have found while using Ubuntu these past to weeks?
[01:03] <tsimonq2> *two
[01:03] <adueppen> well I'm having dinner in about 5 minutes so I won't be able to say much
[01:04] <tsimonq2> ok :)
[01:04] <tsimonq2> I really think that not many people are gonna come here, so I am just gonna end the meeting :P
[01:04] <tsimonq2> #endmeeting
[01:04] <meetingology> Meeting ended Sat Jan  2 01:04:34 2016 UTC.
[01:04] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-us-wi/2016/ubuntu-us-wi.2016-01-02-01.00.moin.txt
[01:04] <tsimonq2> ¯\_(ツ)_/¯
[01:04] <adueppen> tsimonq2: still, I did find out that you are on pretty much every single ubuntu IRC channel
[01:05] <tsimonq2> LOL
[02:14] <mikeputnam1> wasn't at a keyboard at 7pm
[02:14] <mikeputnam1> srry
[02:14] <mikeputnam1> playing Guns of Icarus on steam now
[02:14] <mikeputnam1> <3 linux
[02:15] <adueppen> mikeputnam1: it's fine, I nearly wasn't either
[02:17] <adueppen> wait mikeputnam1 what's your steam name?
[02:17] <adueppen> so I can add you as a friend
[02:18] <mikeputnam1> sgtd_
[02:18] <mikeputnam1> in guns of icarus, i'm sgtdsgtd  (name collision)
[02:19] <adueppen> mikeputnam1: the one with the ostrich as the profile picture?
[02:27] <mikeputnam1> yes