[01:16] <Fig> huh
[01:17] <Fig> More poeple than I expected here
[13:15] <jcastro> marcoceppi, if you could chime in on the elasticsearch-charmers issue on the list that would be <3
[13:22] <jcastro> marcoceppi, also, how can I get this to show up in the queue? https://bugs.launchpad.net/charms/+bug/1384290
[13:22] <mup> Bug #1384290: [New charm] Forgerock <Juju Charms Collection:New> <https://launchpad.net/bugs/1384290>
[13:23] <marcoceppi> jcastro: currently you have to have code attached to show up in the queue
[13:23] <marcoceppi> that's not going to work here, I'll update ingestion rules
[13:23] <jcastro> oh, the code is in github, that's why
[13:23] <marcoceppi> right
[13:33] <marcoceppi> jcastro: new rule is in place, ingest is running now
[13:33] <jcastro> <3
[13:44] <jcastro> gaughen, did you ever figure out which list to support the openstack charms on? I have someone that mailed me a question.
[14:04] <marcoceppi> Sorry not sorry about the review queue. More changes to rules were made
[14:05] <jcastro> no worries, thanks
[14:05] <jcastro> does anyone have time this morning for forgerock review round two?
[14:05] <jcastro> https://bugs.launchpad.net/charms/+bug/1384290
[14:05] <mup> Bug #1384290: [New charm] Forgerock <Juju Charms Collection:New> <https://launchpad.net/bugs/1384290>
[14:57] <marcoceppi> UGH, jcastro, this is crap
[14:57] <marcoceppi> the review queue is filed with all the stuff that we created years ago
[14:57] <marcoceppi> for charm needed
[14:57] <marcoceppi> I knew the code filter was there for a reason
[14:57] <jcastro> marcoceppi, idea
[14:58] <jcastro> alternative idea I mean
[14:58] <jcastro> put a bug # input field on the review queue, so we can just add individual ones by hand?
[14:58] <marcoceppi> sure
[14:58] <marcoceppi> that works
[14:59] <marcoceppi> got to figure out how to get rid of all these guys
[14:59] <jcastro> or maybe filter by date?
[14:59] <jcastro> anything before the last few months ignore?
[15:10] <lazyPower> marcoceppi: seems like tagging manually would be acceptable, or if there is a github repository link present - but that adds overhead to the workers since they have to parse the message body.. not sure how you feel about that.
[15:10] <marcoceppi> this method just sucks in general
[15:10] <lazyPower> there are definately drawbacks to it
[15:11] <lazyPower> would be nice if we had a way to do something like charm publish --review, that sniffs the repo and ships a review request directly to the rev queue
[15:12] <lazyPower> its api powered, and doesn't solve for the existing stuff we have open, but would be a nice feature post charm publish.
[15:13] <marcoceppi> that is what will happen
[15:13] <marcoceppi> but publish deson't exist yet
[15:21] <rbasak> sinzui: what's libgo5 (>= 4.9.1-0ubuntu1) [!amd64 !i386 !armhf]? I've not seen it before.
[15:21] <rbasak> While we're on the topic actually, where's your packaging branch? We've diverged a little bit, and I'd like to send you MPs.
[15:21] <sinzui> ah!
[15:23] <sinzui> sorry rbasak I sould have notified you of the change. That dep is to ensure arm and ppc getting get the lib we know golang needs with gcc builds
[15:24] <sinzui> rbasak, the dep is inresponse to IBM setting up new trusty machine and not accepting updates. They put new juju on it and it panicked. trusty shipped with an old version of libgo
[15:24] <rbasak> sinzui: OK, thanks. Is there a bug on this?
[15:24]  * sinzui finds it
[15:24] <rbasak> The process for the SRU isn't clear on whether I need a specific bug with independent verification for packaging fixes or not.
[15:25] <rbasak> (since Juju upstream has an exception - it's not clear to me whether that applies to packaging)
[15:25] <gaughen> jcastro, I'd use the the ubuntu-server list
[15:25] <sinzui> rbasak, https://bugs.launchpad.net/juju-core/+bug/1377325
[15:25] <mup> Bug #1377325: The ppc64/arm versions of Juju should depend on a more recent version of libgo5 <arm64> <packaging> <ppc64el> <juju-core:Fix Released by sinzui> <https://launchpad.net/bugs/1377325>
[15:26] <rbasak> sinzui: thanks! And do you have a packaging branch somewhere?
[15:26] <sinzui> rbasak, the issue would never been discovered if the machines were accepting updates
[15:26] <marcoceppi> Okay, most of the review-queue is cleaned up
[15:27] <sinzui> rbasak, https://code.launchpad.net/~juju-qa/juju-release-tools/packaging-juju-core-default
[15:27] <rbasak> Great. Thank you! I'll send you some MPs soon.
[15:52] <mbruzek> Hello juju people. Is there any reason that the Juju PPA is still named "Ensemble"?
[15:53] <mbruzek> gpg: key C8068B11: public key "Launchpad Ensemble PPA" imported
[15:53] <marcoceppi> mbruzek: that's the gpg key
[15:53] <mbruzek> sudo add-apt-repository -y ppa:juju/stable
[15:53] <marcoceppi> not the ppa
[15:53] <mbruzek> marcoceppi: OK, should we update that or no?
[15:54] <marcoceppi> The key is generated on LP at the time of creation and when the stable ppa was created it was Ensemble
[15:54] <marcoceppi> not really, it's a minor thing
[15:54] <mbruzek> ack
[15:54] <mbruzek> just noticed that
[15:54] <mbruzek> thought I would bring it up
[15:57] <marcoceppi> cool, good eye
[16:02] <marcoceppi> Okay, review queue is reset
[16:02] <marcoceppi> Adding a submit button
[16:02] <mbruzek> marcoceppi: why do the "ubuntu" charm not show up in this listing? http://manage.jujucharms.com/charms/trusty
[16:03] <mbruzek> I am trying to get a list of all the trusty charms.
[16:03] <mbruzek> I can issue charm get cs:trusty/ubuntu but I do not see it in the above listing.
[16:05] <jcastro> hey jose
[16:05] <jcastro> jose, any reason you haven't pushed owncloud to trusty?
[18:06] <marcoceppi> tvansteenburgh: 1.8.1-0ubuntu2 was just uploaded to the ppa, should resove that missing dep
[18:07] <tvansteenburgh> marcoceppi: tyvm!
[18:20] <mhall119> jcastro marcoceppi gaughen arosales are you all going to be UOS track leads for Cloud & DevOps this cycle?
[18:20] <gaughen> mhall119, sure
[18:20] <marcoceppi> mhall119: I'm at re:Invent during UOS
[18:20] <arosales> mhall119: as will jcastro
[18:21] <mhall119> marcoceppi: can you help recruit and schedule sessions leading up to UOS week?
[18:21] <arosales> mhall119: please let myself, perhaps also include randall. I'll confirm to have someone else from the Juju side
[18:22] <marcoceppi> mhall119: I can help, surely
[18:22] <mhall119> ah yes, we have rrnwexec now
[18:22] <mhall119> can you all mark youselves as attending on https://launchpad.net/sprints/uos-1411 so you're added to summit.u.c
[18:22] <mhall119> rrnwexec: want to be a track lead?
[18:23] <marcoceppi> mhall119: registered
[18:23] <mhall119> thanks everyone
[18:23] <rrnwexec> mhall119: if that's ok with Antonio, sure. my domain is IBM/Power though, so jorge may be a better lead
[18:24]  * mhall119 notices that jcastro is the only one who didn't reply, slacker