# The form data below was edited by perforce # Perforce Workshop Jobs # # Job: The job name. 'new' generates a sequenced job number. # # Status: Job status; required field. There is no enforced or # promoted workflow for transition of jobs from one # status to another, just a set of job status values # for users to apply as they see fit. Possible values: # # open - Issue is available to be worked on. # # inprogress - Active development is in progress. # # blocked - Issue cannot be implemented for some reason. # # fixed - Fixed, optional status to use before closed. # # closed - Issue has been dealt with definitively. # # punted - Decision made not to address the issue, # possibly not ever. # # suspended - Decision made not to address the issue # in the immediate future, but noting that it may # have some merit and may be revisited later. # # duplicate - Duplicate of another issue that. # # obsolete - The need behind the request has become # overcome by events. # # Project: The project this job is for. Required. # # Severity: [A/B/C] (A is highest) Required. # # ReportedBy The user who created the job. Can be changed. # # ReportedDate: The date the job was created. Automatic. # # ModifiedBy: The user who last modified this job. Automatic. # # ModifiedDate: The date this job was last modified. Automatic. # # OwnedBy: The owner, responsible for doing the job. Optional. # # Description: Description of the job. Required. # # DevNotes: Developer's comments. Optional. Can be used to # explain a status, e.g. for blocked, punted, # obsolete or duplicate jobs. May also provide # additional information such as the earliest release # in which a bug is known to exist. # # Component: Projects may use this optional field to indicate # which component of the project a givenjob is associated # with. # # For the SDP, the list of components is defined in: # //guest/perforce_software/sdp/tools/components.txt # # Type: Type of job [Bug/Feature]. Required. # # Release: Release in which job is intended to be fixed. Job: job000740 Status: open Project: perforce_software-p4python Severity: C ReportedBy: akwan ReportedDate: 2018/10/29 15:58:05 ModifiedBy: perforce ModifiedDate: 2019/02/19 10:51:39 OwnedBy: akwan Description: check_ssl() fails to support LibreSSL on OSX. Currently running OSX 10.14 (Mojave) with python 3.7.0 ``` $ pip install p4python Collecting p4python Using cached https://files.pythonhosted.org/packages/37/2f/ae9214f6b08bde402d88a9cdf6faf307cfbe50fee04aeb4b15f89bf09fcd/p4python-2017.2.1615960.tar.gz Complete output from command python setup.py egg_info: Attempting to load API from ftp.perforce.com Loaded API into /var/folders/3n/6jmv45nx3q78_n6rjk4cqtjrfmt6lc/T/p4api-2017.2.1611521 **************************************************** Cannot match OpenSSL Version string 'LibreSSL 2.6.4 ' **************************************************** *********************************************** ** Cannot build P4Python without SSL support ** *********************************************** ``` DevNotes: Type: Bug