Getting an issue from composer_manager_sa recently when running `drush composer-manager update`:
exception 'SensioLabs\Security\Exception\RuntimeException' with [error]
message 'An error occurred: SSL certificate problem: unable to get
local issuer certificate.' in
[drupal site root]/sites/all/composer/vendor/sensiolabs/security-checker/SensioLabs/Security/SecurityChecker.php:102
Far as I can tell, it has to do with [this change introduced by sensiolabs](https://github.com/sensiolabs/security-checker/issues/75). It looks like the author has introduced a fix, but it's for a recent version of the package.
Comment | File | Size | Author |
---|---|---|---|
#4 | security_checker_sa_issue-2865837-3.patch | 534 bytes | aron.beal |
Comments
Comment #2
aron.beal CreditAttribution: aron.beal as a volunteer commentedFollowing patch applies the change to composer_manager_sa composer.json file recommended at the bottom of the [issue thread](https://github.com/sensiolabs/security-checker/issues/75). Appears to work.
Comment #3
aron.beal CreditAttribution: aron.beal as a volunteer commentedBetter version (-2) patch uploaded. They've merged the PR directly into a branch, so no need to go to an external repo.
Comment #4
aron.beal CreditAttribution: aron.beal as a volunteer commentedAdded a third patch. The PR is now folded into the 4.0.4 tagged release of the composer module, so it is no longer necessary to use composer aliasing. I don't know if the change will be folded into the 2.x branch (which CM uses), so this patch is still relevant.
Comment #5
aron.beal CreditAttribution: aron.beal as a volunteer commentedUpdate with this: the inclusion of the newer version causes a drush conflict. Security-manager requires a version of symfony console from Symfony 3, which drush (at least the 8.1.x branch) is incompatible with (see [here](https://github.com/drush-ops/drush/pull/2477)).
Not sure what the best path is forward at this point. Patcher beware - this *will* fix the module, but may break your drush. Might be easier to do the SA process separately, and leave composer_manager_sa disabled if you use this patch and run into this issue.
Comment #6
jacob.embree CreditAttribution: jacob.embree at St. Louis Integration commentedMarking "Needs work" because of the warning in #5.
Comment #7
markhalliwell