[10:31] -queuebot:#ubuntu-ci-eng- ltinkl, https://bileto.ubuntu.com/#/ticket/2132 Preparing packages
[11:16] -queuebot:#ubuntu-ci-eng- ltinkl, https://bileto.ubuntu.com/#/ticket/2132 Needs rebuild due to new commits (zesty/ubuntu-system-settings). Successfully built (vivid/indicator-power, vivid/ubuntu-settings-components, vivid/ubuntu-system-settings, vivid/unity8, xenial/indicator-power, xenial/ubuntu-settings-components, xenial/ubuntu-system-settings, xenial/unity8, zesty/indicator-power, zesty/ubuntu-settings-components, zesty/unity8)
[11:32] -queuebot:#ubuntu-ci-eng- ltinkl, https://bileto.ubuntu.com/#/ticket/2132 Preparing packages
[11:44] -queuebot:#ubuntu-ci-eng- alf__, https://bileto.ubuntu.com/#/ticket/2221 Preparing packages
[11:45] -queuebot:#ubuntu-ci-eng- alf__, https://bileto.ubuntu.com/#/ticket/2221 zesty/repowerd: Failed to tag release
[11:48] -queuebot:#ubuntu-ci-eng- alf__, https://bileto.ubuntu.com/#/ticket/2221 Preparing packages
[12:02] -queuebot:#ubuntu-ci-eng- alf__, https://bileto.ubuntu.com/#/ticket/2221 Successfully built
[12:17] -queuebot:#ubuntu-ci-eng- ltinkl, https://bileto.ubuntu.com/#/ticket/2132 Pending binary packages (zesty/ubuntu-system-settings). Successfully built (vivid/indicator-power, vivid/ubuntu-settings-components, vivid/ubuntu-system-settings, vivid/unity8, xenial/indicator-power, xenial/ubuntu-settings-components, xenial/ubuntu-system-settings, xenial/unity8, zesty/indicator-power, zesty/ubuntu-settings-components, zesty/unity8)
[12:33] -queuebot:#ubuntu-ci-eng- mzanetti, https://bileto.ubuntu.com/#/ticket/2150 Failed to build (zesty/unity-api). Needs rebuild due to new commits (zesty/unity8). Successfully built (vivid/unity-api, vivid/unity8, xenial/unity-api, xenial/unity8)
[12:36] -queuebot:#ubuntu-ci-eng- ltinkl, https://bileto.ubuntu.com/#/ticket/2132 Successfully built
[12:39] -queuebot:#ubuntu-ci-eng- mzanetti, https://bileto.ubuntu.com/#/ticket/2150 Preparing packages
[12:52] -queuebot:#ubuntu-ci-eng- mzanetti, https://bileto.ubuntu.com/#/ticket/2150 Currently building (vivid/unity8, xenial/unity8, zesty/unity8). Failed to build (zesty/unity-api). Successfully built (vivid/unity-api, xenial/unity-api)
[12:57] -queuebot:#ubuntu-ci-eng- jgdx, https://bileto.ubuntu.com/#/ticket/2194 Needs rebuild due to new commits (zesty/ubuntu-system-settings). Successfully built (vivid/ubuntu-system-settings, vivid/ubuntu-themes, xenial/ubuntu-system-settings, xenial/ubuntu-themes, zesty/ubuntu-themes)
[12:57] -queuebot:#ubuntu-ci-eng- ChrisTownsend, https://bileto.ubuntu.com/#/ticket/2215 QA Signoff: Approved
[12:57] -queuebot:#ubuntu-ci-eng- tedg mterry, https://bileto.ubuntu.com/#/ticket/2129 Failed to build (xenial/ubuntu-app-launch). Needs rebuild due to new commits (zesty/mediaplayer-app, zesty/ubuntu-app-launch, zesty/ubuntu-system-settings). Successfully built (xenial/address-book-app, xenial/address-book-service, xenial/indicator-application, xenial/indicator-bluetooth, xenial/indicator-datetime, xenial/indicator-keyboard, xenial/indicator-location, xenial/indicator-message
[13:12] -queuebot:#ubuntu-ci-eng- mzanetti, https://bileto.ubuntu.com/#/ticket/2150 Failed to build (zesty/unity-api). Pending binary packages (vivid/unity8, xenial/unity8, zesty/unity8). Successfully built (vivid/unity-api, xenial/unity-api)
[13:27] -queuebot:#ubuntu-ci-eng- jgdx, https://bileto.ubuntu.com/#/ticket/2194 Preparing packages
[13:33] -queuebot:#ubuntu-ci-eng- mzanetti, https://bileto.ubuntu.com/#/ticket/2150 Failed to build (zesty/unity-api). Successfully built (vivid/unity-api, vivid/unity8, xenial/unity-api, xenial/unity8, zesty/unity8)
[13:45] -queuebot:#ubuntu-ci-eng- charles, https://bileto.ubuntu.com/#/ticket/2188 QA Signoff: Approved
[14:22] -queuebot:#ubuntu-ci-eng- tiagosh boiko rmescandon bfiller, https://bileto.ubuntu.com/#/ticket/1319 Pending binary packages (vivid/nuntium). Ready to build (xenial/nuntium, zesty/nuntium). Successfully built (vivid/dialer-app, vivid/gsettings-ubuntu-touch-schemas, vivid/history-service, vivid/messaging-app, vivid/telepathy-ofono, vivid/telepathy-qt, vivid/telephony-service, xenial/dialer-app, xenial/gsettings-ubuntu-touch-schemas, xenial/history-service, xenial/messagi
[14:23] <ChrisTownsend> #ubuntu-qa: Hi!  I wanted to give a heads up that I have yet one more change for the already approved https://bileto.ubuntu.com/#/ticket/2123.  This time, it's a one line change in debian/control to fix a Breaks/Replaces versioning issue.
[14:23] <ChrisTownsend> I can't fix it in anther landing because this landing is stuck in -proposed due to the issue.
[14:33] <rvr> ChrisTownsend: :-/
[14:33] <ChrisTownsend> rvr: Yeah, I know
[14:33] <ChrisTownsend> rvr: This thing has been a pain
[14:34] <rvr> ChrisTownsend: I'll take a look after I finish with the current silo
[14:35] <ChrisTownsend> rvr: Well, it'll be a bit.  I still need to commit the change, rebuild, and then let autopkgtest's run.
[14:35] <rvr> ChrisTownsend: Ok, let me know when it's ready
[14:35] <ChrisTownsend> rvr: Ok, thanks!
[14:37] -queuebot:#ubuntu-ci-eng- jgdx, https://bileto.ubuntu.com/#/ticket/2194 Needs rebuild due to new commits (zesty/ubuntu-system-settings). Successfully built (vivid/ubuntu-system-settings, vivid/ubuntu-themes, xenial/ubuntu-system-settings, xenial/ubuntu-themes, zesty/ubuntu-themes)
[14:40] -queuebot:#ubuntu-ci-eng- tedg mterry, https://bileto.ubuntu.com/#/ticket/2129 Preparing packages
[14:42] -queuebot:#ubuntu-ci-eng- ChrisTownsend, https://bileto.ubuntu.com/#/ticket/2123 QA Signoff:
[14:42] -queuebot:#ubuntu-ci-eng- ChrisTownsend, https://bileto.ubuntu.com/#/ticket/2123 Preparing packages
[14:52] -queuebot:#ubuntu-ci-eng- ChrisTownsend, https://bileto.ubuntu.com/#/ticket/2215 Publishing packages
[15:04] -queuebot:#ubuntu-ci-eng- tiagosh boiko rmescandon bfiller, https://bileto.ubuntu.com/#/ticket/1319 Diff missing (vivid/nuntium, xenial/nuntium, zesty/nuntium). Successfully built (vivid/dialer-app, vivid/gsettings-ubuntu-touch-schemas, vivid/history-service, vivid/messaging-app, vivid/telepathy-ofono, vivid/telepathy-qt, vivid/telephony-service, xenial/dialer-app, xenial/gsettings-ubuntu-touch-schemas, xenial/history-service, xenial/messaging-app, xenial/telepathy-ofo
[15:05] -queuebot:#ubuntu-ci-eng- ChrisTownsend, https://bileto.ubuntu.com/#/ticket/2123 Destination version missing from changelog (zesty/libertine). Successfully built (xenial/libertine)
[15:09] <ChrisTownsend> trainguards: Is "Destination version missing from changelog (zesty/libertine)." something to worry about in https://bileto.ubuntu.com/#/ticket/2123 ?
[15:10] <sil2100> ChrisTownsend: yeah, in this case it does - it means the previously released libertine didn't migrate yet
[15:10] <sil2100> So it's possibly not merged to trunk
[15:11] <ChrisTownsend> sil2100: Right, but it's stuck in proposed and has an issue.
[15:11] <ChrisTownsend> sil2100: Do I need it to be rejected first?
[15:12] <ChrisTownsend> sil2100: It's unclear to me how we fix an issue when a release is stuck in proposed.
[15:15] <sil2100> Ah, so you want it to be overriden?
[15:15] <ChrisTownsend> sil2100: Yes.
[15:15] <ChrisTownsend> sil2100: Both in overlay and archive.
[15:15] <sil2100> ChrisTownsend: so you're re-using the same silo then?
[15:16] <sil2100> If that's the case then I think you can safely ignore this warning
[15:16] <ChrisTownsend> sil2100: Well, I did that because I needed to fix up the release branch and since it wasn't merged, I just re-used the silo.
[15:16] -queuebot:#ubuntu-ci-eng- ChrisTownsend, https://bileto.ubuntu.com/#/ticket/2215 xenial/unity8-desktop-session: Failed to fetch https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/2215/+files/unity8-desktop-session_1.0.13+16.04.20161118-0ubuntu1_source.changes
[15:17] <ChrisTownsend> Good grief, what does that mean????
[15:18] <ChrisTownsend> Man, bileto is hating on me today...
[15:19] <ChrisTownsend> sil2100: Are you able to override the issue on https://bileto.ubuntu.com/#/ticket/2123 so I can get autopkgtest's to run?
[15:19] -queuebot:#ubuntu-ci-eng- tedg mterry, https://bileto.ubuntu.com/#/ticket/2129 Currently building (xenial/ubuntu-system-settings, zesty/ubuntu-system-settings). Failed to build (zesty/ubuntu-app-launch). Successfully built (xenial/address-book-app, xenial/address-book-service, xenial/indicator-application, xenial/indicator-bluetooth, xenial/indicator-datetime, xenial/indicator-keyboard, xenial/indicator-location, xenial/indicator-messages, xenial/indicator-network, xen
[15:21] -queuebot:#ubuntu-ci-eng- ltinkl, https://bileto.ubuntu.com/#/ticket/2132 Preparing packages
[15:31] -queuebot:#ubuntu-ci-eng- renatofilho, https://bileto.ubuntu.com/#/ticket/2213 Preparing packages
[15:37] -queuebot:#ubuntu-ci-eng- ChrisTownsend, https://bileto.ubuntu.com/#/ticket/2215 Release pocket
[15:39] -queuebot:#ubuntu-ci-eng- tedg mterry, https://bileto.ubuntu.com/#/ticket/2129 Failed to build (zesty/ubuntu-app-launch). Needs rebuild due to new commits (zesty/ubuntu-system-settings). Successfully built (xenial/address-book-app, xenial/address-book-service, xenial/indicator-application, xenial/indicator-bluetooth, xenial/indicator-datetime, xenial/indicator-keyboard, xenial/indicator-location, xenial/indicator-messages, xenial/indicator-network, xenial/indicator-pow
[15:54] <mterry> robru: does this behavior make any sense to you: bug 1642350 ?
[15:54] <ubot5`> bug 1642350 in Snapcraft "webbrowser-app silently being excluded from stage-packages" [Undecided,New] https://launchpad.net/bugs/1642350
[15:54] <mterry> robru: I'm guessing it's snapcraft side (the fact that it's silent certainly is a bug), but maybe there's something weird about the script that builds the snap too?
[15:56] -queuebot:#ubuntu-ci-eng- renatofilho, https://bileto.ubuntu.com/#/ticket/2213 Failed to build (vivid/camera-app, xenial/camera-app, zesty/camera-app). Pending binary packages (vivid/mediaplayer-app, xenial/mediaplayer-app, zesty/mediaplayer-app). Successfully built (vivid/address-book-app, vivid/address-book-service, vivid/dialer-app, vivid/gallery-app, vivid/messaging-app, xenial/address-book-app, xenial/address-book-service, xenial/dialer-app, xenial/gallery-app, xe
[15:59] -queuebot:#ubuntu-ci-eng- tiagosh boiko rmescandon bfiller, https://bileto.ubuntu.com/#/ticket/1319 Generating diffs
[16:00] -queuebot:#ubuntu-ci-eng- jgdx, https://bileto.ubuntu.com/#/ticket/2194 Preparing packages
[16:05] -queuebot:#ubuntu-ci-eng- tiagosh boiko rmescandon bfiller, https://bileto.ubuntu.com/#/ticket/1319 Diff missing (vivid/nuntium, xenial/nuntium, zesty/nuntium). Successfully built (vivid/dialer-app, vivid/gsettings-ubuntu-touch-schemas, vivid/history-service, vivid/messaging-app, vivid/telepathy-ofono, vivid/telepathy-qt, vivid/telephony-service, xenial/dialer-app, xenial/gsettings-ubuntu-touch-schemas, xenial/history-service, xenial/messaging-app, xenial/telepathy-ofo
[16:16] -queuebot:#ubuntu-ci-eng- ltinkl, https://bileto.ubuntu.com/#/ticket/2132 Successfully built
[16:17] -queuebot:#ubuntu-ci-eng- renatofilho, https://bileto.ubuntu.com/#/ticket/2213 Failed to build (vivid/camera-app, xenial/camera-app, zesty/camera-app). Successfully built (vivid/address-book-app, vivid/address-book-service, vivid/dialer-app, vivid/gallery-app, vivid/mediaplayer-app, vivid/messaging-app, xenial/address-book-app, xenial/address-book-service, xenial/dialer-app, xenial/gallery-app, xenial/mediaplayer-app, xenial/messaging-app, zesty/address-book-app, zesty
[16:18] <ChrisTownsend> sil2100: So, any way to override bileto for https://bileto.ubuntu.com/#/ticket/2123 so I can move on and get automated tests to run?  If I set Lander Signoff to Approved, it doesn't accept it.
[16:23] -queuebot:#ubuntu-ci-eng- renatofilho, https://bileto.ubuntu.com/#/ticket/2213 Preparing packages
[16:23] -queuebot:#ubuntu-ci-eng- tiagosh boiko rmescandon bfiller, https://bileto.ubuntu.com/#/ticket/1319 Successfully built
[16:27] -queuebot:#ubuntu-ci-eng- tiagosh boiko rmescandon bfiller, https://bileto.ubuntu.com/#/ticket/1319 Preparing packages
[16:33] -queuebot:#ubuntu-ci-eng- Wellark charles seb128, https://bileto.ubuntu.com/#/ticket/1649 DONE queue
[16:33] -queuebot:#ubuntu-ci-eng- Elleo, https://bileto.ubuntu.com/#/ticket/2200 QA Signoff: Approved
[16:36] -queuebot:#ubuntu-ci-eng- renatofilho, https://bileto.ubuntu.com/#/ticket/2213 Currently building (vivid/history-service, zesty/history-service). Failed to build (vivid/camera-app, xenial/camera-app, zesty/camera-app). Pending binary packages (xenial/history-service). Successfully built (vivid/address-book-app, vivid/address-book-service, vivid/dialer-app, vivid/gallery-app, vivid/mediaplayer-app, vivid/messaging-app, xenial/address-book-app, xenial/address-book-servic
[16:37] <sil2100> ChrisTownsend: just finished a meeting, let me take a look
[16:43] -queuebot:#ubuntu-ci-eng- tiagosh boiko rmescandon bfiller, https://bileto.ubuntu.com/#/ticket/1319 Pending binary packages (vivid/messaging-app, xenial/messaging-app, zesty/messaging-app). Successfully built (vivid/dialer-app, vivid/gsettings-ubuntu-touch-schemas, vivid/history-service, vivid/nuntium, vivid/telepathy-ofono, vivid/telepathy-qt, vivid/telephony-service, xenial/dialer-app, xenial/gsettings-ubuntu-touch-schemas, xenial/history-service, xenial/nuntium, xen
[16:56] -queuebot:#ubuntu-ci-eng- renatofilho, https://bileto.ubuntu.com/#/ticket/2213 Failed to build (vivid/camera-app, xenial/camera-app, zesty/camera-app). Needs rebuild due to new commits (zesty/history-service). Successfully built (vivid/address-book-app, vivid/address-book-service, vivid/dialer-app, vivid/gallery-app, vivid/history-service, vivid/mediaplayer-app, vivid/messaging-app, xenial/address-book-app, xenial/address-book-service, xenial/dialer-app, xenial/gallery
[16:57] -queuebot:#ubuntu-ci-eng- jgdx, https://bileto.ubuntu.com/#/ticket/2194 Successfully built
[17:03] -queuebot:#ubuntu-ci-eng- tiagosh boiko rmescandon bfiller, https://bileto.ubuntu.com/#/ticket/1319 Successfully built
[17:04] <sil2100> ChrisTownsend: I think we need robru here
[17:05] <sil2100> robru: hey! Is there any possibility to override the warning from silo https://bileto.ubuntu.com/#/ticket/2123 ?
[17:05] <sil2100> robru: since we need to overwrite the version that's in -proposed as it's broken
[17:05] <sil2100> robru: this should be a valid case btw.
[17:10] <ChrisTownsend> sil2100: Ok, thanks.  Will wait on robru's response:)
[17:17] <robru> sil2100: ChrisTownsend: why don't you just put the destination version in your changelog? I don't think that message can be overridden, no
[17:18] <robru> mterry: huh, no idea.
[17:21] <ChrisTownsend> robru: I guess I don't understand.  Why do I have to specify that?  What would it be looking for?
[17:23] <robru> ChrisTownsend: this check is preventing you from accidentally reverting a release from a different ticket. Typically it happens when you have the same package on two tickets, if you publish both, the second one will revert the first one.
[17:24] <robru> ChrisTownsend: so what you need to do is take the debian/changelog from -proposed and include it in your release so that it's sees the same version numbers there and doesn't think you're reverting anything
[17:25] <ChrisTownsend> robru: Ugh, this is the same release.  So basically you are saying I need to hack up the changelog to work around this.
[17:25] <ChrisTownsend> robru: But I see the logic of why this is being prevented.
[17:27] <robru> ChrisTownsend: https://bileto.ubuntu.com/log/2123/status/1511/ it gives the full diff of what it thinks it's missing
[17:29] <ChrisTownsend> robru: Ok, thnaks
[17:29] <ChrisTownsend> thanks even
[17:40] <ChrisTownsend> robru: This is what I think I should do: http://pastebin.ubuntu.com/23512607/
[17:41] <ChrisTownsend> robru: Do I keep 'zesty' there or revert it to UNRELEASED and let bileto fill it in?
[17:44] <robru> ChrisTownsend: Hmmmmmmm...
[17:45] <robru> ChrisTownsend: I'm not sure if that will work
[17:46] <ChrisTownsend> robru: Ok:)
[17:47] <robru> ChrisTownsend: you're better off creating a new entry after that entry that explains what you're fixing
[17:48] <ChrisTownsend> robru: Ok, I wondered if that's what I needed.
[17:48] <robru> ChrisTownsend: if you leave it as is it might just clobber that version and then give you the same error, I can't remember quite how that code works
[17:48] <ChrisTownsend> robru: Thanks
[17:49] <robru> ChrisTownsend: you're welcome
[17:50] <ChrisTownsend> robru: Oh, one last question, would I put the 1.4.3-0ubuntu1 version and UNRELEASED distro in for the new stanza?
[17:50] <robru> ChrisTownsend: yeah, it'll clobber the UNRELEASED version with the version number it generates.
[17:51] <ChrisTownsend> robru: Ok, so safe to ignore the dch warning of a lesser version then, right?
[17:51] <robru> ChrisTownsend: yeah
[17:51] <ChrisTownsend> robru: Ok, great, thanks!
[17:51] <robru> ChrisTownsend: you're welcome
[17:57] -queuebot:#ubuntu-ci-eng- ChrisTownsend, https://bileto.ubuntu.com/#/ticket/2123 Preparing packages
[18:07] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/2195 QA Signoff: Approved
[18:24] -queuebot:#ubuntu-ci-eng- ChrisTownsend, https://bileto.ubuntu.com/#/ticket/2123 Failed to build (zesty/libertine). Successfully built (xenial/libertine)
[18:30] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/2208 Preparing packages
[18:50] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/2208 Failed to build (zesty/libappindicator). Successfully built (zesty/appmenu-qt5, zesty/sni-qt)
[18:51] <ChrisTownsend> trainguards: Hi, could you retry https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/2123/+build/11235505 please?  That was not failing before, but claims it's due to the libcontent-hub-dev dependency.  Maybe it's a transient issue???
[18:55] <Saviq> mterry, hey, can you publish https://bileto.ubuntu.com/#/ticket/2195 please?
[18:55] <mterry> looking
[18:57] <sil2100> ChrisTownsend: done
[18:57] <ChrisTownsend> sil2100: Thanks
[18:58] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/2195 Publishing packages
[18:59] <mterry> Saviq: done
[18:59] <Saviq> mterry, thanks! Trevinho ↑
[19:00] <Trevinho> Saviq: yeah, noticed... thanks mterry ! :-)
[19:04] <Saviq> robru, uh oh https://bileto.ubuntu.com/log/2195/publish/1/ ?
[19:05] -queuebot:#ubuntu-ci-eng- ChrisTownsend, https://bileto.ubuntu.com/#/ticket/2123 Destination version missing from changelog (zesty/libertine). Successfully built (xenial/libertine)
[19:05] <ChrisTownsend> robru: Still didn't work:(  ^^^^^
[19:06] <robru> ChrisTownsend: Saviq: sorry in meeting
[19:07] <ChrisTownsend> robru: Ok
[19:09] -queuebot:#ubuntu-ci-eng- renatofilho, https://bileto.ubuntu.com/#/ticket/2213 Preparing packages
[19:11] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/2208 Needs rebuild due to new commits (zesty/libappindicator). Successfully built (zesty/appmenu-qt5, zesty/sni-qt)
[19:17] <mterry> Saviq: I've seen that error before -- we need to wait and see what gets published -- and maybe publish the silo again
[19:17] <Saviq> mterry, we can probably just publish again, still might be interesting to see what's the problem - from the looks of it, it's a launchpad/archive issue (malformed JSON somewhere)
[19:18] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/2195 Release pocket (vivid/indicator-datetime, vivid/qmenumodel, vivid/ubuntu-settings-components, vivid/ubuntu-system-settings, vivid/unity8, xenial/indicator-datetime, xenial/qmenumodel, xenial/ubuntu-settings-components, xenial/ubuntu-system-settings, xenial/unity8). Successfully built (zesty/indicator-datetime, zesty/qmenumodel, zesty/ubuntu-settings-components, zesty/ubuntu-system-settings, zes
[19:19] <Saviq> OTOH it looks like maybe it published everything (15 entries re: copying/requesting copy)
[19:19] <Saviq> let's see
[19:23] <robru> Saviq: yeah that's a failure of launchpad to respond to the copy request. harmless to publish again
[19:24] <robru> but maybe wait for the status to update to see if it missed anything
[19:24] <Saviq> robru, wonder if we could catch and retry?
[19:25] <robru> Saviq: yeah file a bug I guess, I'm not sure where would be the best place to do the catch & retry because *all* lp api calls are subject to this and one thing I don't want to do is litter the catch & retry *everywhere* in the code, but not clear to me that there's a sensible central place to do it from.
[19:25] <mterry> Imma publish again.  Looks like only xenial+vivid got the update
[19:26] <Saviq> robru, right, makes sense
[19:26] <robru> ChrisTownsend: looking now. I think the diff is cached or something. your branch looked good to me before...
[19:26] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/2195 Publishing packages
[19:26] <ChrisTownsend> robru: Ok, thanks
[19:29] <Saviq> robru, bug #1643672
[19:29] <ubot5`> bug 1643672 in Bileto "Bileto could be more persistent when doing HTTP calls" [Undecided,New] https://launchpad.net/bugs/1643672
[19:29] <robru> Saviq: ok thanks
[19:30] <robru> ChrisTownsend: yeah the diff is cached, I need to escalate to webops to clear that out
[19:30] <ChrisTownsend> robru: Ack, thanks again
[19:32] <robru> ChrisTownsend: you're welcome. actually... actually I think there's a way around this.
[19:32] <robru> (just digging into code)
[19:32] <ChrisTownsend> Oh?
[19:33] -queuebot:#ubuntu-ci-eng- charles, https://bileto.ubuntu.com/#/ticket/2188 QA Signoff:
[19:33] -queuebot:#ubuntu-ci-eng- charles, https://bileto.ubuntu.com/#/ticket/2188 Destination version missing from changelog (zesty/indicator-datetime). Successfully built (xenial/indicator-application, xenial/indicator-bluetooth, xenial/indicator-datetime, xenial/indicator-location, xenial/indicator-messages, xenial/indicator-power, xenial/indicator-printers, xenial/indicator-session, xenial/indicator-sound, xenial/indicator-transfer, zesty/indicator-application, zesty/indic
[19:33] <charles> grr
[19:33] <robru> ChrisTownsend: what you should do is commit the changelog entry for 1.4.3+17.04.20161118.1-0ubuntu1 directly to *trunk* (not in your MP), then rebase your MP on that. that'll fool it into thinking that the destination version was merged to trunk.
[19:34] -queuebot:#ubuntu-ci-eng- mzanetti, https://bileto.ubuntu.com/#/ticket/2150 Destination version missing from changelog (zesty/unity8). Failed to build (zesty/unity-api). Successfully built (vivid/unity-api, vivid/unity8, xenial/unity-api, xenial/unity8)
[19:34] <ChrisTownsend> robru: That sounds evil, but whatever works:)
[19:35] <robru> ChrisTownsend: yeah we used to have lots of problems with conflicting tickets released in parallel so the protections against that became quite aggressive...
[19:36] <robru> ChrisTownsend: another option would be deleting the package from -proposed but that would require an archive admin, committing to trunk is something you can do yourself at least
[19:36] -queuebot:#ubuntu-ci-eng- ltinkl, https://bileto.ubuntu.com/#/ticket/2132 Destination version missing from changelog (zesty/ubuntu-settings-components, zesty/ubuntu-system-settings, zesty/unity8). Successfully built (vivid/indicator-power, vivid/ubuntu-settings-components, vivid/ubuntu-system-settings, vivid/unity8, xenial/indicator-power, xenial/ubuntu-settings-components, xenial/ubuntu-system-settings, xenial/unity8, zesty/indicator-power)
[19:37] -queuebot:#ubuntu-ci-eng- renatofilho, https://bileto.ubuntu.com/#/ticket/2213 Failed to build (vivid/camera-app, xenial/camera-app, zesty/camera-app). Needs rebuild due to new commits (zesty/address-book-app, zesty/history-service). Successfully built (vivid/address-book-app, vivid/address-book-service, vivid/dialer-app, vivid/gallery-app, vivid/history-service, vivid/mediaplayer-app, vivid/messaging-app, xenial/address-book-app, xenial/address-book-service, xenial/di
[19:37] <ChrisTownsend> robru: I already asked an AA and they told me they weren't going to do it because it's completely supported to supersede the package in proposed.  So I'm going your route:)
[19:38] -queuebot:#ubuntu-ci-eng- jgdx, https://bileto.ubuntu.com/#/ticket/2194 Destination version missing from changelog (zesty/ubuntu-system-settings). Successfully built (vivid/ubuntu-system-settings, vivid/ubuntu-themes, xenial/ubuntu-system-settings, xenial/ubuntu-themes, zesty/ubuntu-themes)
[19:38] -queuebot:#ubuntu-ci-eng- tedg mterry, https://bileto.ubuntu.com/#/ticket/2129 Destination version missing from changelog (zesty/indicator-datetime). Failed to build (zesty/ubuntu-app-launch). Needs rebuild due to new commits (zesty/ubuntu-system-settings). Successfully built (xenial/address-book-app, xenial/address-book-service, xenial/indicator-application, xenial/indicator-bluetooth, xenial/indicator-datetime, xenial/indicator-keyboard, xenial/indicator-location, xe
[19:39] -queuebot:#ubuntu-ci-eng- Saviq, https://bileto.ubuntu.com/#/ticket/2197 Destination version missing from changelog (zesty/unity8). Successfully built (vivid/unity8, xenial/unity8)
[19:41] <robru> ChrisTownsend: yeah this used to work better, I'm not quite sure how it got this way... it's been a long time since i touched the code in question, I'm not sure why nobody had this problem sooner
[19:41] <robru> I'll file a bug
[19:41] <ChrisTownsend> robru: I guess I'm lucky:)  Any ways, thanks for your help on this...about to commit and push the rebased branch and will rebuild.
[19:42] <robru> ChrisTownsend: you're welcome
[19:43] -queuebot:#ubuntu-ci-eng- jgdx, https://bileto.ubuntu.com/#/ticket/2140 Destination version missing from changelog (zesty/ubuntu-system-settings). Successfully built (vivid/qtmir, vivid/qtmir-gles, vivid/ubuntu-system-settings, xenial/qtmir, xenial/qtmir-gles, xenial/ubuntu-system-settings, zesty/qtmir, zesty/qtmir-gles)
[19:45] -queuebot:#ubuntu-ci-eng- ChrisTownsend, https://bileto.ubuntu.com/#/ticket/2123 Preparing packages
[19:46] <robru> ChrisTownsend: https://bugs.launchpad.net/bileto/+bug/1643676
[19:46] <ubot5`> Ubuntu bug 1643676 in Bileto "Rebuilding after publication has regressed" [Medium,Triaged]
[19:47] -queuebot:#ubuntu-ci-eng- Cimi, https://bileto.ubuntu.com/#/ticket/2202 Destination version missing from changelog (zesty/unity8). Successfully built (vivid/unity8, xenial/unity8)
[19:48] <ChrisTownsend> robru: Great, thanks
[19:48] -queuebot:#ubuntu-ci-eng- renatofilho, https://bileto.ubuntu.com/#/ticket/2213 Preparing packages
[19:48] <robru> ChrisTownsend: you're welcome
[19:58] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/2195 Proposed pocket (zesty/indicator-datetime, zesty/qmenumodel, zesty/ubuntu-settings-components, zesty/ubuntu-system-settings, zesty/unity8). Release pocket (vivid/indicator-datetime, vivid/qmenumodel, vivid/ubuntu-settings-components, vivid/ubuntu-system-settings, vivid/unity8, xenial/indicator-datetime, xenial/qmenumodel, xenial/ubuntu-settings-components, xenial/ubuntu-system-settings, xenial/
[20:05] -queuebot:#ubuntu-ci-eng- ChrisTownsend, https://bileto.ubuntu.com/#/ticket/2123 Successfully built
[20:17] -queuebot:#ubuntu-ci-eng- renatofilho, https://bileto.ubuntu.com/#/ticket/2213 Failed to build (vivid/camera-app, xenial/camera-app, zesty/camera-app). Needs rebuild due to new commits (zesty/address-book-app, zesty/gallery-app, zesty/history-service). Successfully built (vivid/address-book-app, vivid/address-book-service, vivid/dialer-app, vivid/gallery-app, vivid/history-service, vivid/mediaplayer-app, vivid/messaging-app, xenial/address-book-app, xenial/address-book
[20:19] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/2195 Proposed pocket (zesty/qmenumodel, zesty/ubuntu-settings-components, zesty/ubuntu-system-settings, zesty/unity8). Release pocket (vivid/indicator-datetime, vivid/qmenumodel, vivid/ubuntu-settings-components, vivid/ubuntu-system-settings, vivid/unity8, xenial/indicator-datetime, xenial/qmenumodel, xenial/ubuntu-settings-components, xenial/ubuntu-system-settings, xenial/unity8, zesty/indicator-da
[20:24] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/2208 Preparing packages
[20:41] <robru> kenvandine: can you republish https://bileto.ubuntu.com/#/ticket/2123 with the latest packaging fix?
[20:42]  * kenvandine looks
[20:43] -queuebot:#ubuntu-ci-eng- jgdx, https://bileto.ubuntu.com/#/ticket/2140 Successfully built
[20:43] <kenvandine> robru, done
[20:43] <robru> kenvandine: thanks
[20:44] -queuebot:#ubuntu-ci-eng- ChrisTownsend, https://bileto.ubuntu.com/#/ticket/2123 Publishing packages
[20:44] <robru> ugh
[20:45] -queuebot:#ubuntu-ci-eng- ChrisTownsend, https://bileto.ubuntu.com/#/ticket/2123 Publish failed: Destination version missing from changelog
[20:46] -queuebot:#ubuntu-ci-eng- Cimi, https://bileto.ubuntu.com/#/ticket/2202 Successfully built
[20:47] <robru> kenvandine: will you be around for a bit? I can fix that, will need you to publish again in about 15 mins.
[20:47] <kenvandine> robru, sure
[20:51] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/2208 Failed to build (zesty/libappindicator). Successfully built (zesty/appmenu-qt5, zesty/sni-qt)
[20:52] -queuebot:#ubuntu-ci-eng- mzanetti, https://bileto.ubuntu.com/#/ticket/2150 Failed to build (zesty/unity-api). Successfully built (vivid/unity-api, vivid/unity8, xenial/unity-api, xenial/unity8, zesty/unity8)
[20:56] -queuebot:#ubuntu-ci-eng- ltinkl, https://bileto.ubuntu.com/#/ticket/2132 Successfully built
[20:57] -queuebot:#ubuntu-ci-eng- jgdx, https://bileto.ubuntu.com/#/ticket/2194 Successfully built
[20:58] -queuebot:#ubuntu-ci-eng- tedg mterry, https://bileto.ubuntu.com/#/ticket/2129 Destination version missing from changelog (zesty/indicator-datetime). Needs rebuild due to new commits (zesty/ubuntu-app-launch, zesty/ubuntu-system-settings). Successfully built (xenial/address-book-app, xenial/address-book-service, xenial/indicator-application, xenial/indicator-bluetooth, xenial/indicator-datetime, xenial/indicator-keyboard, xenial/indicator-location, xenial/indicator-mes
[20:58] -queuebot:#ubuntu-ci-eng- Saviq, https://bileto.ubuntu.com/#/ticket/2197 Successfully built
[20:59] -queuebot:#ubuntu-ci-eng- tedg mterry, https://bileto.ubuntu.com/#/ticket/2129 Preparing packages
[21:01] <robru> kenvandine: ok please publish again
[21:01] <robru> mterry: sorry did you figure out that stage-package issue? sounded like a bug in lp to me, bileto doesn't touch stage-packages at all
[21:02] <mterry> robru: no.  I mean, I *think* the failure would be at least partly in snapcraft.  Since it doesn't even mention a failure to get the package at all...  (Or a log-capturing error on bileto's part maybe...)
[21:02] <kenvandine> robru, same thing
[21:03] -queuebot:#ubuntu-ci-eng- ChrisTownsend, https://bileto.ubuntu.com/#/ticket/2123 Publishing packages
[21:03] <robru> mterry: no bileto doesn't touch the build log at all, it's entirely in lp
[21:03] <robru> kenvandine: but but...
[21:03] <mterry> robru: well fine, but my point is I blame snapcraft  :)
[21:03] <robru> kenvandine: I think you're looking at a cached page, it's still running here
[21:04] <kenvandine> hmmm
[21:04] <kenvandine> it opened a new tab
[21:04] -queuebot:#ubuntu-ci-eng- jgdx, https://bileto.ubuntu.com/#/ticket/2140 Destination version missing from changelog (zesty/ubuntu-system-settings). Successfully built (vivid/qtmir, vivid/qtmir-gles, vivid/ubuntu-system-settings, xenial/qtmir, xenial/qtmir-gles, xenial/ubuntu-system-settings, zesty/qtmir, zesty/qtmir-gles)
[21:04] <kenvandine> and i clicked ack and publish...
[21:04] <robru> kenvandine: says it worked
[21:04] <kenvandine> great then :)
[21:04] <robru> kenvandine: ok thanks
[21:04] <kenvandine> np
[21:06] -queuebot:#ubuntu-ci-eng- Cimi, https://bileto.ubuntu.com/#/ticket/2202 Destination version missing from changelog (zesty/unity8). Successfully built (vivid/unity8, xenial/unity8)
[21:09] -queuebot:#ubuntu-ci-eng- tedg, https://bileto.ubuntu.com/#/ticket/2105 Failed to build (xenial/ubuntu-app-launch). Needs rebuild due to new commits (zesty/ubuntu-app-launch)
[21:13] -queuebot:#ubuntu-ci-eng- mzanetti, https://bileto.ubuntu.com/#/ticket/2150 Destination version missing from changelog (zesty/unity8). Failed to build (zesty/unity-api). Successfully built (vivid/unity-api, vivid/unity8, xenial/unity-api, xenial/unity8)
[21:15] -queuebot:#ubuntu-ci-eng- ltinkl, https://bileto.ubuntu.com/#/ticket/2132 Destination version missing from changelog (zesty/ubuntu-settings-components, zesty/ubuntu-system-settings, zesty/unity8). Successfully built (vivid/indicator-power, vivid/ubuntu-settings-components, vivid/ubuntu-system-settings, vivid/unity8, xenial/indicator-power, xenial/ubuntu-settings-components, xenial/ubuntu-system-settings, xenial/unity8, zesty/indicator-power)
[21:17] -queuebot:#ubuntu-ci-eng- renatofilho, https://bileto.ubuntu.com/#/ticket/2213 Preparing packages
[21:18] -queuebot:#ubuntu-ci-eng- jgdx, https://bileto.ubuntu.com/#/ticket/2194 Destination version missing from changelog (zesty/ubuntu-system-settings). Successfully built (vivid/ubuntu-system-settings, vivid/ubuntu-themes, xenial/ubuntu-system-settings, xenial/ubuntu-themes, zesty/ubuntu-themes)
[21:19] -queuebot:#ubuntu-ci-eng- Saviq, https://bileto.ubuntu.com/#/ticket/2197 Destination version missing from changelog (zesty/unity8). Successfully built (vivid/unity8, xenial/unity8)
[21:19] -queuebot:#ubuntu-ci-eng- attente kenvandine, https://bileto.ubuntu.com/#/ticket/2178 Needs rebuild due to new commits (zesty/content-hub). Successfully built (vivid/content-hub, xenial/content-hub)
[21:24] -queuebot:#ubuntu-ci-eng- ChrisTownsend, https://bileto.ubuntu.com/#/ticket/2123 Proposed pocket (zesty/libertine). Release pocket (xenial/libertine)
[21:28] <robru> kenvandine: http://people.canonical.com/~ubuntu-archive/proposed-migration/zesty/update_excuses.html#libertine this doesn't look any better than it did before, do you know the situation here?
[21:35] -queuebot:#ubuntu-ci-eng- attente kenvandine, https://bileto.ubuntu.com/#/ticket/2178 Preparing packages
[21:36] -queuebot:#ubuntu-ci-eng- attente kenvandine, https://bileto.ubuntu.com/#/ticket/2178 zesty/content-hub: Failed to merge https://code.launchpad.net/~attente/content-hub/content-hub-glib
[21:37] -queuebot:#ubuntu-ci-eng- renatofilho, https://bileto.ubuntu.com/#/ticket/2213 Failed to build (vivid/camera-app, xenial/camera-app, zesty/camera-app). Needs rebuild due to new commits (zesty/address-book-app, zesty/history-service). Pending binary packages (vivid/gallery-app, xenial/gallery-app). Successfully built (vivid/address-book-app, vivid/address-book-service, vivid/dialer-app, vivid/history-service, vivid/mediaplayer-app, vivid/messaging-app, xenial/address-bo
[21:49] -queuebot:#ubuntu-ci-eng- attente kenvandine, https://bileto.ubuntu.com/#/ticket/2178 Preparing packages
[21:50] -queuebot:#ubuntu-ci-eng- attente kenvandine, https://bileto.ubuntu.com/#/ticket/2178 zesty/content-hub: Failed to branch https://code.launchpad.net/~attente/content-hub/content-hub-glib
[21:51] -queuebot:#ubuntu-ci-eng- attente kenvandine, https://bileto.ubuntu.com/#/ticket/2178 Preparing packages
[21:52] -queuebot:#ubuntu-ci-eng- attente kenvandine, https://bileto.ubuntu.com/#/ticket/2178 zesty/content-hub: Failed to merge https://code.launchpad.net/~attente/content-hub/content-hub-glib
[21:55] -queuebot:#ubuntu-ci-eng- attente kenvandine, https://bileto.ubuntu.com/#/ticket/2178 Preparing packages
[21:55] -queuebot:#ubuntu-ci-eng- attente kenvandine, https://bileto.ubuntu.com/#/ticket/2178 zesty/content-hub: Failed to merge https://code.launchpad.net/~attente/content-hub/content-hub-glib
[21:56] -queuebot:#ubuntu-ci-eng- attente kenvandine, https://bileto.ubuntu.com/#/ticket/2178 Preparing packages
[21:57] -queuebot:#ubuntu-ci-eng- renatofilho, https://bileto.ubuntu.com/#/ticket/2213 Failed to build (vivid/camera-app, xenial/camera-app, zesty/camera-app). Needs rebuild due to new commits (zesty/address-book-app, zesty/history-service). Successfully built (vivid/address-book-app, vivid/address-book-service, vivid/dialer-app, vivid/gallery-app, vivid/history-service, vivid/mediaplayer-app, vivid/messaging-app, xenial/address-book-app, xenial/address-book-service, xenial/di
[22:18] -queuebot:#ubuntu-ci-eng- tedg mterry, https://bileto.ubuntu.com/#/ticket/2129 Destination version missing from changelog (zesty/indicator-datetime). Failed to build (xenial/ubuntu-app-launch, zesty/ubuntu-app-launch). Needs rebuild due to new commits (zesty/ubuntu-system-settings). Successfully built (xenial/address-book-app, xenial/address-book-service, xenial/indicator-application, xenial/indicator-bluetooth, xenial/indicator-datetime, xenial/indicator-keyboard, xen
[22:19] -queuebot:#ubuntu-ci-eng- attente kenvandine, https://bileto.ubuntu.com/#/ticket/2178 Currently building (vivid/content-hub). Failed to build (xenial/content-hub, zesty/content-hub)
[22:32]  * tsimonq2 looks around for Mirv
[22:34] <tsimonq2> Ah I see, I see his away message.
[22:40] -queuebot:#ubuntu-ci-eng- attente kenvandine, https://bileto.ubuntu.com/#/ticket/2178 Failed to build (xenial/content-hub, zesty/content-hub). Successfully built (vivid/content-hub)
[23:02] -queuebot:#ubuntu-ci-eng- tedg mterry, https://bileto.ubuntu.com/#/ticket/2129 Preparing packages
[23:38] -queuebot:#ubuntu-ci-eng- tedg mterry, https://bileto.ubuntu.com/#/ticket/2129 Destination version missing from changelog (zesty/indicator-datetime). Needs rebuild due to new commits (zesty/ubuntu-system-settings). Successfully built (xenial/address-book-app, xenial/address-book-service, xenial/indicator-application, xenial/indicator-bluetooth, xenial/indicator-datetime, xenial/indicator-keyboard, xenial/indicator-location, xenial/indicator-messages, xenial/indicator-n


[01:04] <cherylj> thanks, wallyworld.  Given that we want 1.25.0 asap, do you think it could reasonably be done soon?  or should we aim for it in 1.25.1?
[01:05] <wallyworld> cherylj: it can go in 1.25.1 - it's been broken for a while AFAIK. so let's not hold up 1.25 for it, but i'd like to think 1.25.1 will appear not too long after
[01:05] <cherylj> wallyworld: sounds good, thanks!
[01:09] <lazyPower> :O
[01:09] <lazyPower> update-status hook isn't a myth!
[01:15] <perrito666> lazyPower: it better not
[01:15] <perrito666> we should settle for one of the englishes in the code
[01:16] <lazyPower> perrito666, i heard about it in seattle, but called schenanigans
[01:16] <lazyPower> i'm on a build of 1.25-beta2 and its in here
[01:16] <perrito666> grep -ri authorized | wc -l
[01:16] <perrito666> 997
[01:16] <perrito666> grep -ri authorised | wc -l
[01:16] <perrito666> 200
[01:16] <perrito666> lazyPower: it better be, I put it there
[01:55] <thumper> perrito666: english vs american
[01:56] <perrito666> thumper: they both sound foreign to me :p
[01:56] <thumper> :)
[01:58] <natefinch> pretty sure America invented English
[01:59] <perrito666> My brain reads juju comments and code with the BBC narrator voice so I presume it is uk version :p
[01:59] <natefinch> lol
[02:06] <perrito666> ok brain coredumped, see some of you tomorrow
[02:39] <axw> dpb1: don't suppose you still have the env for https://bugs.launchpad.net/juju-core/+bug/1491688? and can I get access? I haven't had any luck reproducing it, and the logs aren't very illuminating
[02:39] <mup> Bug #1491688: all-machine logging stopped, x509: certificate signed by unknown authority <landscape> <logging> <rsyslog> <sts> <juju-core:Triaged> <juju-core 1.24:In Progress by axwalk> <juju-core 1.25:Triaged> <https://launchpad.net/bugs/1491688>
[02:53] <thumper> axw: I have that locally with 1.24.6
[02:54] <axw> thumper: orly? did you have to do something special?
[02:54] <thumper> start two local providers
[02:54] <thumper> it fucks up all the logs
[02:54] <thumper> it used to work
[02:54] <axw> interesting
[02:54] <axw> I'll try that
[02:55] <thumper> the lxd provider will fix this...
[02:55]  * thumper can't wait
[02:55] <natefinch> we should just warn people about the problems of running more than zero local providers
[02:55] <axw> thumper: pretty sure LS is using MAAS though...
[02:55] <thumper> yeah...
[02:55] <natefinch> and yes, the lxd provider is amazing
[02:55] <thumper> I'm guessing that this isn't necessarily the same problem
[02:55] <axw> I want it nowwwww
[02:55] <natefinch> a little slow, though
[02:55] <thumper> natefinch: plz make tools work properly with local streams
[02:56] <thumper> slow
[02:56] <thumper> ?
[02:56] <axw> natefinch: the OpenStack on LXD demo wayne did was pretty sweet
[02:56] <thumper> agreed
[02:56] <natefinch> bootstrapping takes like twice as long as the local provider
[02:56] <natefinch> axw: yeah, that demo was pretty killer
[02:57] <natefinch> honestly, just bootstrapping without it asking for a sudo password kind of rocks my world... not to mention the fact it doesn't crap all over my local machine
[02:57] <thumper> natefinch: hah...
[02:57] <thumper> well that isn't really surprising
[02:57] <thumper> local bootstrap isn't starting a machine
[02:57] <natefinch> right
[02:57] <thumper> it is just shitting on our local machine
[02:58] <natefinch> what amazed me the most was how easy it was to write the provider.  They really did well with lxd
[03:07] <dpb1> axw: I don't, and it wasn't seen with doing anything funky (like two local providers).  But, if you all can't repro, I totally understand (I certainly can't at will).  I've seen it a total of twice.
[03:08] <axw> dpb1: ok, no worries. I'll keep looking anyway
[03:22] <natefinch> what's the right way to convert from a unit ID to a unit tag?  I'm getting unit ids back from a strings watcher and I've been told I have to pass Tags through the API.
[03:23] <natefinch> names.NewUnitTag looks likely, but it panics if I pass it an invalid id (which is gobsmackingly horrible, btw)
[03:24]  * thumper looks
[03:24] <thumper> natefinch: what do you have?
[03:24] <thumper> service/3 ?
[03:24] <natefinch> yeah
[03:25] <thumper> names.NewUnitTag should work
[03:25]  * thumper looks at the tests
[03:25] <natefinch> but it panics... which means I have to check the ids before I pass it into the function, and then that function itself rechecks the ids, which is dumb
[03:25] <thumper> natefinch: 	c.Assert(names.NewUnitTag("wordpress/2").String(), gc.Equals, "unit-wordpress-2")
[03:25] <thumper> yes, you have to check
[03:26] <thumper> names.IsValidUnit
[03:26] <thumper> all the New*Tag methods panic on invalid input
[03:26] <natefinch> that's horrible
[03:26] <thumper> because they are generally used where checking errors is a PITA
[03:26] <thumper> no... it is a valid pattern
[03:26] <thumper> most places, you know you are dealing with valid names
[03:27] <thumper> sometimes, like user input, you need to validate
[03:28] <natefinch> it's a house of cards waiting for someone to feed the wrong string into the wrong function at some point and the whole thing blows up in production because someone didn't want to check an error.
[03:28] <thumper> I disagree
[03:28] <thumper> but I can see your point of view
[03:28] <natefinch> ditto :)
[03:28] <thumper> so...
[03:29] <thumper> given that you have a valid unit name, why is it failing?
[03:29] <thumper> perhaps you don't have what you think you have
[03:29] <natefinch> I'mwriting an api client.  It takes a list of strings it hopes are ids. It shouldn't assume someone's not going to do the wrong thing
[03:29]  * thumper looks at unit id
[03:30] <thumper> agreed, the client (and the server) need to validate
[03:30] <natefinch> for example, my test passed in an invalid id, and the code panicked.  Sure, I could not do that, but that seems silly
[03:31] <thumper> right, so validate
[03:31] <natefinch> right
[03:32] <thumper> IIRC the general use case for creating tags using the New*Tag methods was tests
[03:32] <thumper> at the time they were written
[03:32] <thumper> and panicing in tests is fine
[03:32] <thumper> perhaps we should create a new class of functions
[03:32] <thumper> that validate and return (tag, error)
[03:33] <thumper> however, the line count will be approx the same as currently
[03:33] <natefinch> it just irks me to call IsValidUnit twice
[03:33] <thumper> it is my expectation that if I'm calling a function that doesn't return an error, I should check theinput
[03:33] <thumper> you don't
[03:33] <thumper> do you?
[03:34] <natefinch> I assume a function that doesn't return an error can't fail
[03:34] <thumper> well...
[03:34] <thumper> or it panics
[03:34] <thumper> because Go
[03:34] <natefinch> well... except that in general you never panic unless THE WORLD HAS COME TO AN END.  Not because johhnny passed in "foo"
[03:35] <natefinch> so, I don't call IsValidUnit twice, but I call it once and then NewUnitTag calls it once
[03:35] <thumper> / NewUnitTag returns the tag for the unit with the given name.
[03:35] <thumper> / It will panic if the given unit name is not valid.
[03:36] <natefinch> trivia - the panic was added on the day I joined canonical (though not by me)
[03:36] <thumper> :)
[03:36] <thumper> magic
[03:37] <natefinch> And yes, I am glad that the comment states it panics. That's at least better than blindsiding someone.
[03:38] <thumper> boo yeah - have a panic
[03:38] <thumper> not as nice as a picnic
[03:38] <thumper> but close enough
[03:39] <natefinch> ha
[03:46] <axw> wallyworld: I really don't know what's up with the rsyslog bug. I can't reproduce it, and injecting errors into the rsyslog worker shows that it does recover from errors writing certs to state
[03:47] <axw> wallyworld: rsyslog looks unhealthy in the env, because it's repeating machine-0's logs in all-machines.log
[03:47] <wallyworld> axw: hmmm. mark as incomplete and ask for steps to repro? or access to an env with the problem so it can be investigated
[03:47] <axw> wallyworld: ok
[03:47] <wallyworld> ty for looking
[03:49] <axw> menn0: what ever happened to the logging-in-state feature branch? is that still happening?
[03:52] <menn0> axw: it's been merged for a long time
[03:53] <menn0> axw: but it's still behind a feature flag
[03:53] <axw> menn0: ah
[03:53] <axw> menn0: any particular reason why it's not enabled by default?
[03:53] <menn0> axw: it also gets activated if the "jes" feature flag is turned on
[03:53] <axw> I see
[03:53] <axw> menn0: so it will be soon then I guess?
[03:53] <menn0> axw: to be honest, I don't know when
[03:53] <axw> (on by default)
[03:54] <axw> mk
[03:54] <menn0> axw: some people had concerns about logging to mongodb
[03:54] <menn0> axw: performance related mainly
[03:54] <menn0> axw: let me bring it up on the list
[03:58] <thumper> menn0: I don't think it is in 1.24 is it?
[03:58] <wallyworld> axw: small corner case fix please http://reviews.vapour.ws/r/2955/
[04:01]  * menn0 checks
[04:04] <menn0> thumper, axw: it's in 1.25 but not 1.24
[04:05] <menn0> there's bits of it there in 1.24 but it wasn't complete nor wired in at that stage
[04:05] <axw> menn0: ok. was mainly just curious what the plan was for enabling it
[04:05] <axw> thanks
[04:06] <menn0> axw: I'll email the list about getting it turned on by default for 1.26
[04:09] <natefinch> menn0: do we need the EnvUUID field in new mongo docs?  William said in a review that he thought we didn't, but to check with you.
[04:10] <menn0> natefinch: no they're not necessary any more
[04:10] <menn0> the multi-env DB layer will automatically add them
[04:11] <menn0> I have a personal tech debt item to go and remove them from all our structs (and all the place they're set)
[04:11] <menn0> even if a document struct has an EnvUUID field you can just leave out setting it in the code that creates them
[04:11] <menn0> it'll still get added
[04:11] <menn0>  /populated
[04:21] <natefinch> menn0: thanks
[04:24] <menn0> natefinch: np
[04:24] <menn0> natefinch: let me know if you find that any aspect of this doesn't work how I've just described
[04:25] <natefinch> menn0: will do
[04:37] <wallyworld> axw: with the test it would be either a big cut and paste or a bit of refactoring all for a corner case where the method being used is tested extensively elsewhere. i can do it if you insist :-)
[04:48] <wallyworld> axw: another small one sorry http://reviews.vapour.ws/r/2956/
[06:57] <frobware> dimitern, running 10 mins late...
[07:03] <dimitern> frobware, that's ok, I'm finishing my HW list here, will join ~5m
[09:02] <dooferlad> dimitern: hangout?
[09:02] <dimitern> omw
[09:34] <voidspace> dimitern: frobware: I see that AWS "space discovery" is still listed as a deliverable, even after our conversation with William last week when we said it shouldn't be done
[09:44] <dimitern> voidspace, that depends on "shared spaces by default" or not
[09:45] <voidspace> dimitern: yes, and the agreement in discussion with fwreade was that we should *not* do shared spaces by default
[09:45] <voidspace> dimitern: because of the unnecessary pain that it brings
[09:45] <dimitern> voidspace, I know, but that's not approved yet by jam or rick
[09:46] <dimitern> voidspace, I'd like it if we don't share by default, but mark seemed keen on the idea
[09:47] <voidspace> dimitern: listing it as a deliverable seems like a bad idea (very)
[09:47] <voidspace> you're boxing us into a corner
[09:49] <dimitern> voidspace, even if we go with "not shared by default", there is still value in having discover + filters
[09:49] <voidspace> dimitern: how is discover different from list then?
[09:50] <dimitern> voidspace, discover lists spaces which are pre-existing on the cloud, but not yet known to (or usable by) juju
[09:51] <voidspace> dimitern: but if you don't have shared spaces then there won't be pre-existing spaces
[09:51] <dimitern> voidspace, i.e. you can import these (idempotently)
[09:51] <voidspace> because as soon as you can share spaces (import them) then the can of worms is open
[09:51] <voidspace> and you can't delete / rename them or move subnets
[09:51] <dimitern> voidspace, well, "not sharing by default" does not exclude "being able to share spaces at all"
[09:52] <voidspace> which is why we agreed not to do it
[09:56] <dimitern> voidspace, how about openstack, azure?
[09:56] <dimitern> voidspace, for maas "shared by default" and "no creation" is clear
[09:57] <voidspace> dimitern: I'm talking about AWSD
[09:57] <voidspace> *AWS
[09:57] <mup> Bug #1508392 opened: Clearer error message when servicename instead of unitname <juju-core:New> <https://launchpad.net/bugs/1508392>
[09:57] <voidspace> you have listed space discovery as a 16.04 deliverable for AWS, despite discussion with fwreade saying we shouldn't do it
[10:01] <dimitern> voidspace, we have to do auto-discovery at bootstrap to figure out where to put the apiserver, and to allow bootstrapping into a space
[10:02] <voidspace> dimitern: not if we don't have shared spaces
[10:02] <voidspace> dimitern: because there won't be a pre-existing space, so we'll create the necessary infrastructure at bootstrap
[10:05] <voidspace> dimitern: it *does* mean we don't have feature parity between AWS / MAAS for spaces
[10:05] <dimitern> voidspace, that's one of the options
[10:05] <dimitern> voidspace, let's have a call with jam about this, ideally also with rick
[10:05] <dimitern> frobware, ^^ ?
[10:05] <dimitern> we need to clarify this ASAP
[10:06] <voidspace> heh
[10:12] <jam> dimitern: voidspace: if the user has to set up the spaces in order for anything to work at all (which they do today), then it seems to make sense to discover them without having to have a bunch of steps. I don't think it is a prereq for January, though.
[10:13] <dimitern> jam, not for jan, we're discussing later, until 16.04
[10:14] <voidspace> jam: they set them up through juju
[10:15] <voidspace> jam: so they don't have to set them up in EC2 as a pre-requisite
[10:15] <voidspace> jam: they only configure them through juju
[10:17] <voidspace> jam: having spaces discoverable (i.e. potentially shareable between environments) means that you can't safely delete or rename a space (can't fix typos) and you can't delete subnets or move them between spaces (so you have to assign a subnet to a space at subnet creation)
[10:17] <voidspace> jam: all of which is a horrible UX
[10:17] <voidspace> jam: not to mention that if you have different teams sharing a substrate (amazon account) with different environments they will see each others spaces
[10:18] <jam> voidspace: if you have different teams sharing an amazon account you see everyone's stuff anyway
[10:18] <jam> hence the *shared account*
[10:18] <voidspace> jam: and old spaces/subnets from old environments will hang around for ever
[10:18] <voidspace> jam: not with juju - you just see your environment
[10:19] <voidspace> jam: a much better model, both for implementation and for UX, is private (to the environment) spaces by default, with explicitly global spaces for sharing
[10:19] <voidspace> jam: with the added benefit that "explicitly global" doesn't need to be done initially (yay scope reduction) and can be added later
[10:29] <jam> voidspace: so I wouldn't focus too much on things beyond January at this point, but I'd also note that if we aren't handling routing between subnets, etc, then the user still has to go to the console to do anything.
[10:29] <jam> I do agree with some of your points about shared-on-request
[10:30] <voidspace> jam: dimitern: the strongest argument for not promising it is that if we don't do it we can always add it - but as soon as we add it we have to support it for ever
[10:30] <voidspace> jam: dimitern: so really, let's not promise it or do it until we're clear about the implications
[10:31] <voidspace> jam: (it's currently listed as a 16.04 deliverable in the draft doc - which is why I'm bringing it up now)
[10:40] <dimitern> frobware, voidspace, jam, I agree to drop it, but it should be replaced with an entry about modeling the shared (global/local) aspect of spaces/subnet and how does it affect the CLI commands
[10:40] <dimitern> (i.e. make sure we can do it later properly)
[10:41] <voidspace> well yes we should document what we do...
[13:39] <TheMue> dimitern: backported latest doc changes to 1.25, mind a quick look at http://reviews.vapour.ws/r/2961/ ? thx
[13:40] <dimitern> TheMue, sure, will do shortly
[13:40] <TheMue> dimitern: great
[15:01] <mup> Bug #1508498 opened: JUJU bootstrap fails first time every time <juju-core:New> <https://launchpad.net/bugs/1508498>
[15:04] <mup> Bug #1508498 changed: JUJU bootstrap fails first time every time <juju-core:New> <https://launchpad.net/bugs/1508498>
[15:06] <dimitern> TheMue, reviewed
[15:06] <dimitern> sorry it took so long
[15:06] <TheMue> dimitern: thx
[15:13] <mup> Bug #1508498 opened: JUJU bootstrap fails first time every time <juju-core:New> <https://launchpad.net/bugs/1508498>
[15:34] <alexisb> wwitzel3, can you refresh my memory on what is happening the first week of feb w/ the eco team
[15:34] <alexisb> I see your travel request
[15:34] <rick_h_> alexisb: fosdem charmers summit party time!
[15:34] <katco> alexisb: the 1st rule of charmers summit is you talk about charmers summit ALL THE TIME.
[15:35] <marcoceppi> ALL THE TIME EVERYWHERE
[15:35] <wwitzel3> lol
[15:35] <katco> woo woo
[15:35] <mgz> fosdem fosdem
[15:35] <katco> hypetrain
[15:35] <wwitzel3> do I even need to say anything at this point?
[15:35] <alexisb> :)
[15:35] <marcoceppi> fosdem, cfgmgmtcamp, and http://summit.juju.solutions
[15:35] <rick_h_> wwitzel3: jsut 'pretty please'? :P
[15:36] <wwitzel3> rick_h_: :)
[15:37] <alexisb> wwitzel3, seems I am a good spot to ask for bribes ;)
[15:40] <wwitzel3> alexisb: haha
[16:14] <voidspace> frobware: so I've done a 1.22 -> 1.24 upgrade with ignore-machine-addresses=true and failed to reproduce that issue
[16:14] <voidspace> frobware: trying some other configurations
[17:05] <katco> ericsnow: natefinch: wwitzel3: http://reviews.vapour.ws/r/2963/
[17:12] <natefinch> katco: are those first two tests going to compile?
[17:12] <katco> natefinch: tests run
[17:12] <natefinch> katco: workload.Info doesn't ahve a Workload field anymore, does it?
[17:13] <wwitzel3> katco: looking
[17:13] <katco> natefinch: hm. no it does not
[17:13] <katco> natefinch: doh... didn't run those tests
[17:14] <natefinch> katco: oh good, I was hoping this wasn't some wacky like embedding thing where it works both ways
[17:34] <sinzui> cherylj: bug 1465317 just came up in #ubuntu-devel. Ubuntu just learned about series X and the dep8 tests failed. They have fixed a test to avoid the panic, but they are nontheless concerned about Juju's insistence on knowing every version of every OS.
[17:34] <mup> Bug #1465317: Wily osx win: panic: osVersion reported an error: Could not determine series <osx> <packaging> <wily> <windows> <juju-core:In Progress by dave-cheney> <juju-core 1.24:Triaged> <juju-core 1.25:Triaged> <juju-release-tools:Fix Released by sinzui> <https://launchpad.net/bugs/1465317>
[17:35] <cherylj> sinzui: I was just looking at that bug.  I see that it's in progress, but I'm not convinced that dave is actually working it.
[17:36] <cherylj> I asked for an update, but I'll also talk with him directly in the onyx standup today
[17:36] <katco> ericsnow: natefinch: wwitzel3: updatedf
[17:38] <sinzui> cherylj: I saw. I think we really need the issue to be fixed in 1.26. I think 1.25.1 is nice to have, I think all the next OS upgrades will involve 1.26 being the new stable
[17:39] <cherylj> sinzui: sounds reasonable.
[17:46] <mup> Bug #1508498 changed: JUJU bootstrap fails first time every time <adoption> <charmers> <cpp> <juju-core:New> <https://launchpad.net/bugs/1508498>
[17:48] <katco> yeeeeesssss: https://github.com/rmuslimov/jenkins.el
[17:49] <mup> Bug #1508498 opened: JUJU bootstrap fails first time every time <adoption> <charmers> <cpp> <juju-core:New> <https://launchpad.net/bugs/1508498>
[17:52] <mup> Bug #1508498 changed: JUJU bootstrap fails first time every time <adoption> <charmers> <cpp> <juju-core:New> <https://launchpad.net/bugs/1508498>
[17:58] <mup> Bug #1508498 opened: JUJU bootstrap fails first time every time <adoption> <charmers> <cpp> <juju-core:New> <https://launchpad.net/bugs/1508498>
[18:01] <mup> Bug #1508498 changed: JUJU bootstrap fails first time every time <adoption> <charmers> <cpp> <juju-core:New> <https://launchpad.net/bugs/1508498>
[18:02] <marcoceppi> mup: calm down
[18:02] <mup> marcoceppi: Excuse moi, parlez vous anglais?
[18:02] <marcoceppi> okay who made mup sassy
[18:53] <wwitzel3> katco: lol .. isn't there a bootloader for emacs? just switch already
[18:54] <katco> wwitzel3: lol i think there is
[18:55] <wwitzel3> there are instructions for making it pid 1
[18:55] <wwitzel3> good enough
[19:22] <katco> wwitzel3: i know you can make it your wm
[19:28] <lazypower> the day fun died and emacs won
[19:28] <wwitzel3> katco: heh, for an editor no one uses there sure are a lot of plugins and extensions for it
[19:29] <cherylj> sinzui: I was just about to ask you if that juju-local packaging bug should be sent to lxc.  You're too quick!
[19:29] <katco> wwitzel3: maybe more people use it than people think :)
[19:29] <cherylj> :)
[19:29] <katco> wwitzel3: semi-complete list: https://melpa.org/#/
[19:30] <sinzui> cherylj: :) I was helping the user in another channel
[19:30] <cherylj> ah!
[19:30] <wwitzel3> all those packages just for katco
[19:30] <katco> haha
[19:31] <katco> wwitzel3: 70k+ downloads... you should try it out (whistles) https://melpa.org/#/evil
[19:33] <natefinch> katco: http://reviews.vapour.ws/r/2814/  all tests passing
[19:33] <katco> natefinch: tal
[19:38] <jamesmillerio>   wwitzel3: Kind of random, but I think I just realized I actually know you based on your handle, hah
[19:39] <jamesmillerio> kind of crazy
[19:42] <sinzui> cherylj: I just reported bug 1508585 which is the cause the failure of the current test of 1.25
[19:42] <mup> Bug #1508585: TestUploadedToolsMetadata fails on windows and centos <blocker> <centos> <ci> <regression> <test-failure> <unit-tests> <windows> <juju-core:Incomplete> <juju-core 1.25:Triaged> <https://launchpad.net/bugs/1508585>
[19:47] <mup> Bug #1508585 opened: TestUploadedToolsMetadata fails on windows and centos <blocker> <centos> <ci> <regression> <test-failure> <unit-tests> <windows> <juju-core:Incomplete> <juju-core 1.25:Triaged> <https://launchpad.net/bugs/1508585>
[19:47] <cherylj> thanks for the heads up, sinzui
[19:50] <mup> Bug #1508585 changed: TestUploadedToolsMetadata fails on windows and centos <blocker> <centos> <ci> <regression> <test-failure> <unit-tests> <windows> <juju-core:Incomplete> <juju-core 1.25:Triaged> <https://launchpad.net/bugs/1508585>
[19:53] <mup> Bug #1508585 opened: TestUploadedToolsMetadata fails on windows and centos <blocker> <centos> <ci> <regression> <test-failure> <unit-tests> <windows> <juju-core:Incomplete> <juju-core 1.25:Triaged> <https://launchpad.net/bugs/1508585>
[19:53] <wwitzel3> jamesmillerio: yeah?
[19:54] <jamesmillerio> wwitzel3: yeah, you're Laura Tripletts friend and Jessa's husband, right?
[19:54] <wwitzel3> jamesmillerio: ahh, yeah, I know you and your wife :)
[19:55] <jamesmillerio> Niceeee, yep. I saw your wedding pictures go over my FB feed a few days ago so your name was fresh in my head. Saw you in here and there are only so many witzel's out there, haha.
[20:05] <katco> i am fairly certain that wwitzel3 is actually a golden retriever who has no idea what he's doing.
[20:06] <katco> like 20% sure.
[20:06] <wwitzel3> 20% seems low
[20:07] <katco> well. i'm also unsure of what i'm doing.
[20:07] <wwitzel3> I'm 100% sure that I'm unsure
[20:07] <wwitzel3> ;)
[20:08] <katco> i... uh... i... yeah.
[20:08] <katco> maybe.
[20:17] <mup> Bug #1508595 opened: revisit use of networks in AddService code <tech-debt> <juju-core:New> <https://launchpad.net/bugs/1508595>
[20:30] <natefinch> katco: so.... now what?
[20:31] <natefinch> katco: what can I do to help with our demos, now that we've finally reached a more or less stopping point for this bug?
[20:31] <katco> natefinch: wwitzel3: ping, you need help with lxd?
[20:34] <thumper> can I add any surity?
[20:34] <thumper> but I know I don't know what you are doing
[20:35] <katco> thumper: surity?
[20:35] <thumper> sureity?
[20:35] <natefinch> sureitude
[20:35] <thumper> damn english
[20:35] <katco> thumper: lol
[20:36] <thumper> sureness
[20:36] <katco> thumper: no i don't think so, just trying to find the next best thing for nate to work on
[20:37] <katco> natefinch: you could start working on feature tests for payloads
[20:38] <natefinch> katco: I can do that.
[20:39] <natefinch> katco: I'll start working on that tonight.
[20:39] <katco> natefinch: kk
[20:39] <natefinch> gotta run, back in a while
[21:13] <cherylj> can I get a review for the 1.25 blocker?  http://reviews.vapour.ws/r/2965/
[21:18] <katco> cherylj: lgtm
[21:18] <cherylj> katco: thanks!
[21:57] <wwitzel3> katco: you got a shipit
[21:58] <katco> wwitzel3: ty. 1.25 is blocked atm
[22:29] <perrito666> can anyone thing a way to check the size of all collections on a mongo db?
[22:37] <perrito666> thumper: seems that you are not the only one thinking the way you do about english http://img-9gag-fun.9cache.com/photo/aDmPrnO_700b.jpg
[23:04] <alexisb> anastasiamac, cherylj I will be late
[23:04] <anastasiamac> alexisb: k :) we r there
[23:21] <menn0> wallyworld: ping
[23:30] <wallyworld> menn0: sorry, in standup, give me 5
[23:34] <menn0> wallyworld: no rush


[08:32] <zzarr> hello anpok
[08:33] <anpok> hi
[08:33] <zzarr> anpok, here are the ump libs http://malideveloper.arm.com/resources/drivers/open-source-mali-gpus-ump-user-space-drivers-source-code-2/
[08:34] <zzarr> (or lib/code)
[08:36] <zzarr> anpok, are there sufficient code to write a Mir driver?
[08:38] <zzarr> anpok, other whys it looks like it's possible to use the android driver (I think that the kernel driver may be the same for both X and Android drivers, if I haven't misunderstood )
[11:32] <anpok> yes kernel side is the same, I did look into UMP User Space Drivers r4p0-00rel1
[11:32] <anpok> and there was no mentioning on how to get egl/glesv2 to render to an ump handle
[11:32] <anpok> zzar: that would be the problem to be solves
[11:32] <anpok> *solved
[11:33] <anpok> the other stuff is helpful.. as it tells you how to transfer handles been processes which is an important piece
[11:33] <anpok> s/been/between
[11:33] <anpok> they might have an extension to setup egl with that.. i dont now.. an alternative native window handle.. maybe
[12:42] <zzarr> anpok, as I'm still new to GPU drivers, I think that the android driver is the easiest way for me
[12:43] <zzarr> anpok, is there a tutorial how to install and configure the android lxc?
[12:44] <alan_g> kgunn: I'm going through the bugs targeting 0.20 and came across bug 1528384 - what is the latest status of that? Is it fixed in 0,19,2?
[12:44] <ubot5`> bug 1528384 in Unity System Compositor "unity-system-compositor crashed with std::runtime_error in mir::compositor::CompositingFunctor::wait_until_started() from usc::MirScreen::set_screen_power_mode (mir_power_mode_on)" [Critical,In progress] https://launchpad.net/bugs/1528384
[12:44] <anpok> zzarr: look for ubunte touch porting guide.. and ask in #ubuntu-touch .. e.g. people like ogra_  or morph or ...
[12:44] <anpok> *ubuntu
[12:44]  * kgunn checks
[12:45] <zzarr> I have asked in #ubuntu-touch
[12:47] <ogra_> well, rather ondra and morphis :) ... i'm not very familiar with the GPU driver setup on the android side
[12:48] <zzarr> okey ogra_, well, I'll read the text on the internet before asking
[12:48] <zzarr> if I get stuck I'll ask
[12:49] <kgunn> alan_g: ah yeah, that landed...the reporting....and AlbertA_ has branches up for 19.2 for that nasty bug
[12:49] <kgunn> alan_g: so we're going on the hope that there's not a seperate subtle bug lurking there
[12:50] <kgunn> for the case of 0.20 you can consider it ok
[12:50] <kgunn> done
[12:51]  * alan_g wonders how to convince LP it was committed in 0.19.2
[17:10] <alan_g> alf_: You have a USC release in the pipe? (I was about create a "no-change" release for Mir-0.20.0, but does this impact?)
[17:52] <alan_g> greyback__: Saviq - in doing a Mir release do I need to do anything for qtmir-gles? (Saviq left a note that one of the steps isn't needed, but there are other I suspect it applies to.)
[17:53] <greyback__> alan_g: usually, if you're not incrementing the qtmir version number, just proposing an empty MP against lp:qtmir/gles , and adding to train, is enough
[17:53] <Saviq> alan_g, nothing in changelog needed, but you should bump the dep in debian/control
[17:54] <Saviq> alan_g, basically, anything you change in debian/ for the non-gles MP, should be changed in the -gles one
[17:54] <Saviq> it's no longer necessary to mangle debian/changelog or debian/watch
[17:55] <alan_g> OK, so as (in this case) I've just an empty MP for qtmir that covers it.
[17:56] <alan_g> Or, I need an empty one for lp:qtmir/gles too?


[05:44] <drocsid> hi i haven't been able to reset the password to my launchpad account, who do i contact?
[05:45] <lifeless> its not maintained by launchpad. there should be a support link on the bottom of login.launchpad.net/login.ubuntu.com
[05:45] <drocsid> i think they broke my login
[05:45] <drocsid> it was a long while back
[05:46] <drocsid> SSO support?
[05:46] <lifeless> yes
[05:49] <drocsid> is anybody logged onto launchpad right now? If so could you tell me the email associated with this account : https://launchpad.net/~colin.williams
[05:49] <drocsid> I don't wanna create another account if I don't have to.
[05:51] <lifeless> unless you marked it non-private, only sysadmins can see your email details
[05:51] <lifeless> don't stress about excess accounts - you can merge them together.
[05:53] <wgrant> drocsid: It's a gmail address.
[05:59] <drocsid> wgrant: can you msg it to me
[06:01] <drocsid> i lost the login to that email address long ago
[06:02] <drocsid> so does that launchpad account just sit there soiling my name now?
[06:04] <wgrant> There's no other obvious way to verify your identity.
[06:05] <lifeless> you can add new emails to the SSO account, if you can verify your identity to SSO
[06:06] <lifeless> once thats done you can log into LP with SSO
[06:32] <drocsid> that SSO thingy didnt exist when i made that launchpad account
[06:33] <drocsid> i used to be able to login to launchpad
[06:34] <drocsid> with a username and password
[06:34] <drocsid> then they made SSO and booted me, since I fogot my email
[06:34] <lifeless> all the account metadata was migrated into SSO
[06:34] <lifeless> if you know the password you should still be able to login
[06:34] <lifeless> even if you can't receive mail at the address
[06:36] <drocsid> ok got in thanks everybody. Now that I knew the email address I could login. before i could use un / pw and it worked. Now i have to use email / pw
[06:37] <lifeless> you should add your current email to both the SSO account and LP
[06:37] <lifeless> you may need support help for that.
[06:43] <drocsid> I would like to know where I can find the driver mentioned here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1119837
[06:44] <drocsid> it mentions staging, does anybody know where I can find that driver? Is there a staging repo?
[06:45] <drocsid> I can ask on lp now that I can login to my account, but maybe somebody here knows
[06:45] <wgrant> drocsid: That might be more of a question for #ubuntu-kernel
[06:45] <drocsid> thanks wgrant
[06:45] <wgrant> drocsid: btw, make sure your login email address is correct now on both launchpad.net and login.launchpad.net
[06:45] <wgrant> So you don't get locked out again
[06:46] <drocsid> wgrant: yeah i just added it, thanks


[12:31] <Scix> How can I preseed ubuntu-restriced-extras?
[16:43] <Haegin> cjwatson: hi, when preseeding an oem install should I use d-i oem-config-udeb/instructions seen true to skip the instructions on how oem installs work or have i got the syntax wrong+
[16:55] <cjwatson> Haegin: looks right
[17:00] <Haegin> cjwatson: ok, thanks, just it doesn't seem to be working. the only thing that looked odd was the 'seen true' when the other lines in the file seem to have a type, e.g. boolean or string instead of 'seen'
[17:07] <cjwatson> 'seen' is handled specially
[17:07] <cjwatson> feel free to post preseed file (remove passwords) and the installer's /var/log/syslog
[17:07] <cjwatson> I may not deal with it until I get back from holiday so the mailing list in /topic might be better than here
[20:01] <ogra> evand, do you happen to have a free session now ? we are discussion oem-config for mobile in the next session and i think having someone from the installer team here would help
[20:01] <ogra> *discussing
[20:04] <ogra> cjwatson_, or you ? ^^^
[20:05] <ogra> we are in #ubuntu-mobile
[20:08] <ogra> oh, #uds-mobile actually
[20:16] <evand> ogra: I don't sorry


[09:55] <teddy-dbear>  Morning peoples, critters and everything else
[10:00] <JonathanD> Morning.
[23:39] <swift110> hey