GitHub user tonybaloney opened a pull request:

    https://github.com/apache/libcloud/pull/771

    Add default cert-CA path for SuSE based distributions

    ## Add default cert-CA path for SuSE based distributions
    
    ### Description
    
    Refer to https://github.com/saltstack/salt/issues/32743 on details for the 
issue
    
    ### Checklist (tick everything that applies)
    
    - [ ] [Code 
linting](http://libcloud.readthedocs.org/en/latest/development.html#code-style-guide)
 (required, can be done after the PR checks)
    - [ ] Documentation
    - [ ] [Tests](http://libcloud.readthedocs.org/en/latest/testing.html)
    - [ ] 
[ICLA](http://libcloud.readthedocs.org/en/latest/development.html#contributing-bigger-changes)
 (required for bigger changes)


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/DimensionDataCBUSydney/libcloud trunk

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/libcloud/pull/771.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #771
    
----
commit f720abd9f3f5b5053bdaf341b91683ae730f2bf8
Author: anthony-shaw <anthonys...@apache.org>
Date:   2016-04-13T12:16:42Z

    Merge remote-tracking branch 'origin/trunk' into trunk

commit 69b5f8d878dad190d014a0048ccc6a6b9d6d6402
Author: anthony-shaw <anthonys...@apache.org>
Date:   2016-04-21T04:59:38Z

    Added cert path for suse

commit 488f0ddeb51310ca426a94803a74652c0149b27b
Author: anthony-shaw <anthonys...@apache.org>
Date:   2016-04-21T05:00:27Z

    Merge remote-tracking branch 'origin/trunk' into trunk

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to