kicad-developers team mailing list archive

[Mark Roszko <mark.roszko@xxxxxxxxx>]

Ah yes I was planning on fixing that warning, its silly noise.



That cacert problem is interesting, though generally troubleshootable

It generally looks for a "cacert" file in the program's folder and
then PATH unless we specify it explicitly (usually no point as Linux
has it as a system package)
In a Windows distribution of kicad we would just have to copy cacert
to the kicad bin which is fine.

You can try
pacman -S ca-certificates
or
pacman -S mingw-w64-x86_64-ca-certificates

(since I get confused by the package paths and ugh it gets confusing
between shells).


Are you able to invoke a curl HTTPS connection in the shell?
curl https://www.google.com