pak::pkg_install("git::https://hooli.local/foo/bar.git") # website with self-issued certificate
with
Error:
! error in pak subprocess
Caused by error:
! Could not solve package dependencies:
* git::https://hooli.local/foo/bar.git: ! pkgdepends resolution error for git::https://hooli.local/foo/bar.git.
Caused by error:
! Failed to download DESCRIPTION from git repo at <https://hooli.local/foo/bar.git>.
Caused by error in `(function (e) …`:
! SSL certificate problem: unable to get local issuer certificate
Type .Last.error to see the more details.
I have placed the self-issued certificate into /etc/ssl/certs and then run sudo update-ca-certificates.
I've also set options(async_http_cainfo = "/etc/ssl/certs") in my .Rprofile to override the certificates that pak ships with.
This is hard to debug, because I don't have ready access to a share-able website with a self-issued certificate, and I know this is usually/probably a user issue.
It's odd however, that curl otherwise works, but pak doesn't, even options(async_http_cainfo = "/etc/ssl/certs").
Is there any other way in which pak and curl calls still differ when this option is set?
this works:
this fails:
with
this works:
this works:
I have placed the self-issued certificate into
/etc/ssl/certs
and then runsudo update-ca-certificates
.I've also set
options(async_http_cainfo = "/etc/ssl/certs")
in my.Rprofile
to override the certificates that pak ships with.This is hard to debug, because I don't have ready access to a share-able website with a self-issued certificate, and I know this is usually/probably a user issue.
It's odd however, that
curl
otherwise works, but pak doesn't, evenoptions(async_http_cainfo = "/etc/ssl/certs")
. Is there any other way in which pak andcurl
calls still differ when this option is set?