14:34:39 #startmeeting Pulp Triage 2017-03-17 14:34:39 #info bizhang has joined triage 14:34:39 !start 14:34:39 Meeting started Fri Mar 17 14:34:39 2017 UTC and is due to finish in 60 minutes. The chair is bizhang. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:34:39 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:34:39 The meeting name has been set to 'pulp_triage_2017_03_17' 14:34:39 bizhang has joined triage 14:35:40 !here 14:35:40 #info dalley has joined triage 14:35:40 dalley has joined triage 14:36:01 #info bmbouter has joined triage 14:36:01 !here 14:36:01 bmbouter has joined triage 14:36:49 !next 14:36:50 3 issues left to triage: 2637, 2639, 2642 14:36:51 #topic Debian dependencies represented in pulp - http://pulp.plan.io/issues/2637 14:36:51 Debian Support Issue #2637 [NEW] (mihai.ibanescu@gmail.com) - Priority: Normal | Severity: Medium 14:36:52 Debian dependencies represented in pulp - http://pulp.plan.io/issues/2637 14:38:37 I'm not sure what our next step for this issue is 14:39:56 smyers, you probably know the most about debian packaging, do you want to work with misa on this? 14:41:53 will this result in a change to platform? 14:42:08 it's filed as an issue but I'm not sure what the defect is 14:42:42 the way I read it it's looking for feedback on the design of the plugin 14:43:32 maybe it should be a task instead? 14:44:12 let's skip it for now and triage when the right people are here 14:44:13 !skip 14:44:15 2 issues left to triage: 2639, 2642 14:44:15 #topic Upgrade to 1.2.1 beta fails on fedora 24 - http://pulp.plan.io/issues/2639 14:44:16 OSTree Support Issue #2639 [NEW] (unassigned) - Priority: Normal | Severity: Medium 14:44:17 Upgrade to 1.2.1 beta fails on fedora 24 - http://pulp.plan.io/issues/2639 14:44:27 bizhang: +1 to that 14:44:54 this seems like sev should be high 14:45:06 because if you are on F24 you cannot use pulp 14:45:21 you cannot use ostree 14:45:31 oh yes ty 14:46:58 But Just make sure you get to comment 2, I'm not sure at this point if you can upgrade to ostree 2.12.2 in any fedora right now 14:47:47 would this block release 2.12.2? 14:47:50 I think we can decide that we need to know that before continuing, or accept that if it's broken in f24 it's probably broken in f25 and we should fix it 14:48:11 do we block releases on plugin issues? 14:48:48 I'm not sure that we have a precedent here. I still don't know why this didn't happen for upgrades to <=2.12.1 14:48:54 agreed 14:49:19 we need to be able to continue to release so maybe this should go on a sprint? 14:49:53 Yeah, given that it's a fix to a plugin, we could potentially fix the packaging and release ostree 1.2.1-2 after the fact 14:49:56 and ostree-only hotfix 14:49:58 an 14:51:02 !propose other normal/normal add to sprint 14:51:02 #idea Proposed for #2639: normal/normal add to sprint 14:51:03 Proposed for #2639: normal/normal add to sprint 14:51:33 Works for me, and I think maybe this gets to be a line item for the next team meeting? 14:51:49 sounds good, I'll add it to the etherpad 14:52:05 #agreed normal/normal add to sprint 14:52:05 !accept 14:52:05 Current proposal accepted: normal/normal add to sprint 14:52:07 #topic --auth-ca parameter on repo creation not working - http://pulp.plan.io/issues/2642 14:52:07 1 issues left to triage: 2642 14:52:08 RPM Support Issue #2642 [NEW] (unassigned) - Priority: Normal | Severity: Medium 14:52:09 --auth-ca parameter on repo creation not working - http://pulp.plan.io/issues/2642 14:52:18 I can take care of that if you want to stay focused on triage, just lemme know 14:53:23 smyers, saw your message after I updated the pad :) 14:53:30 cool 14:55:34 As mentioned in the issue, this issue stems from a discussion on pulp-list that we haven't yet engaged in. I wonder if there's maybe no bug here, and we're just missing something in the docs about setting this up? 14:56:01 I'm not sure what to propose for triage 14:56:37 elyezer++ 14:56:37 elyezer's karma is now 122 14:57:11 !propose other needsinfo bizhang will test --auth-ca command 14:57:11 #idea Proposed for #2642: needsinfo bizhang will test --auth-ca command 14:57:12 Proposed for #2642: needsinfo bizhang will test --auth-ca command 14:57:27 works for me 14:57:31 !accept 14:57:31 #agreed needsinfo bizhang will test --auth-ca command 14:57:31 Current proposal accepted: needsinfo bizhang will test --auth-ca command 14:57:33 No issues to triage. 14:57:50 smyers, what should we do for https://pulp.plan.io/issues/2637 14:57:52 Title: Issue #2637: Debian dependencies represented in pulp - Debian Support - Pulp (at pulp.plan.io) 14:59:16 I'm reading it as needing feedback on pulp_deb design, should we convert it to a task? 14:59:27 Not sure. I think it's low prio/low sev, and that we'll be seeing a PR from misa about it if it isn't already posted 14:59:47 !issue 2637 14:59:48 #topic Debian dependencies represented in pulp - http://pulp.plan.io/issues/2637 14:59:48 Debian Support Issue #2637 [NEW] (mihai.ibanescu@gmail.com) - Priority: Normal | Severity: Medium 14:59:49 Debian dependencies represented in pulp - http://pulp.plan.io/issues/2637 14:59:55 #idea Proposed for #2637: Priority: Low, Severity: Low 14:59:55 !propose triage low low 14:59:55 I think the feedback's already been gotten, that's about implementing it in pulp_deb 14:59:55 Proposed for #2637: Priority: Low, Severity: Low 15:00:39 would it make more sense as a story? 15:00:59 Yeah, I was just thinking about that. Probably yes. 15:01:17 #idea Proposed for #2637: low/low convert to story 15:01:17 !propose other low/low convert to story 15:01:17 Proposed for #2637: low/low convert to story 15:01:24 But maybe it's a task, maybe it's a refactor assuming pulp's output doesn't change. 15:01:31 Story seems fine 15:01:42 cool 15:01:44 #agreed low/low convert to story 15:01:44 !accept 15:01:44 Current proposal accepted: low/low convert to story 15:01:45 No issues to triage. 15:01:46 #endmeeting 15:01:46 !end