14:30:00 #startmeeting Pulp Triage 2017-03-14 14:30:00 !start 14:30:00 Meeting started Tue Mar 14 14:30:00 2017 UTC and is due to finish in 60 minutes. The chair is bizhang. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:30:00 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:30:00 The meeting name has been set to 'pulp_triage_2017_03_14' 14:30:00 #info bizhang has joined triage 14:30:00 bizhang has joined triage 14:30:05 #info smyers has joined triage 14:30:05 !here 14:30:05 smyers has joined triage 14:30:21 #info mhrivnak has joined triage 14:30:21 !here 14:30:21 mhrivnak has joined triage 14:30:22 The triagers list gets wiped on start, so you'll need to re-"!here", dalley 14:30:35 lame :/ 14:30:36 !here 14:30:36 #info dalley has joined triage 14:30:37 dalley has joined triage 14:30:40 !next 14:30:42 2 issues left to triage: 2631, 2633 14:30:42 #topic Make a testing environment for long-term testing of Pulp performance - http://pulp.plan.io/issues/2631 14:30:43 Pulp Issue #2631 [NEW] (unassigned) - Priority: Normal | Severity: Medium 14:30:44 #info dkliban has joined triage 14:30:44 !here 14:30:44 Make a testing environment for long-term testing of Pulp performance - http://pulp.plan.io/issues/2631 14:30:45 dkliban has joined triage 14:30:50 Hilarious consequence of using meetbot to handle the logging. The triage bot doesn't know meetbot's state 14:31:07 i think we can accept this one as is 14:31:13 Looks like a task. 14:31:13 and it's a Task actually 14:31:15 But it's a task, not an issue 14:31:20 I think we agree :) 14:31:20 #idea Proposed for #2631: covert to task 14:31:20 !propose other covert to task 14:31:20 Proposed for #2631: covert to task 14:31:29 #agreed covert to task 14:31:29 !accept 14:31:29 Current proposal accepted: covert to task 14:31:31 1 issues left to triage: 2633 14:31:31 #topic Pulp Debian Errors - http://pulp.plan.io/issues/2633 14:31:32 Pulp Issue #2633 [NEW] (unassigned) - Priority: Normal | Severity: Medium 14:31:33 Pulp Debian Errors - http://pulp.plan.io/issues/2633 14:31:56 I think this is a user environment issue, I can follow up with the reporter and close 14:32:26 !propose other needsinfo, bizhang will follow up 14:32:26 #idea Proposed for #2633: needsinfo, bizhang will follow up 14:32:27 Proposed for #2633: needsinfo, bizhang will follow up 14:32:48 Does pulp_deb work at al in its current form? convert to task "delete pulp_openstack and pulp_deb to prevent false hope"? 14:33:55 Not sure if it works at all. 14:34:59 I'm not sure about deleting it, but perhaps making it more clear that it's unreleased and needs development work would be a good idea. 14:35:43 it's pretty clear on the github page: https://github.com/pulp/pulp_deb 14:35:44 Title: GitHub - pulp/pulp_deb: Experimental Project to seed Pulp support for Debian repositories (at github.com) 14:35:50 "This is a currently NON FUNCTIONAL, experimental project for supporting Debian repositories within Pulp." 14:36:01 Fair enough. :) 14:36:14 Work for me, maybe just link that and NOTABUG? 14:36:19 I assumed the user wanted to get the dev environment for it up and running to help out :) 14:36:19 I guess WONTFIX is also fine 14:36:43 +1 bizhang follow up on it being an environmental problem. 14:37:11 !accept 14:37:11 Current proposal accepted: needsinfo, bizhang will follow up 14:37:11 #agreed needsinfo, bizhang will follow up 14:37:12 No issues to triage. 14:37:13 The issue is "ImportError: No module named devel", which does seem to be environmental. 14:37:24 !end 14:37:24 #endmeeting