-
-
Notifications
You must be signed in to change notification settings - Fork 14.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Git and SSL do not work in nix-shell #64212
Comments
Tried all fixes mentioned in #16031 and related issues no luck |
I'm only able to reproduce this if i add
|
Ah this makes some sense, the issue is I am using lorri for my project, which I am guessing was updated to do pure nix shells today or something. |
ah yep: target/lorri#98 |
Since I landed here first via a websearch of "nixpkgs git ssl github" I thought I'd say that as of today including both I.e. when I have this as my { pkgs ? import <nixpkgs> { } }:
pkgs.mkShell {
nativeBuildInputs = [
pkgs.cmake
pkgs.ninja
pkgs.clang_14
pkgs.gcc12
pkgs.cacert # git needs this to interact with github
pkgs.git
];
} Then a pure shell shows this: [nix-shell:~/notrelevant]$ env | grep crt
SYSTEM_CERTIFICATE_PATH=/nix/store/ahz1n1ykc5gjizmb3yrbbk15pv3fjrky-nss-cacert-3.80/etc/ssl/certs/ca-bundle.crt
NIX_SSL_CERT_FILE=/nix/store/ahz1n1ykc5gjizmb3yrbbk15pv3fjrky-nss-cacert-3.80/etc/ssl/certs/ca-bundle.crt
SSL_CERT_FILE=/nix/store/ahz1n1ykc5gjizmb3yrbbk15pv3fjrky-nss-cacert-3.80/etc/ssl/certs/ca-bundle.crt Related issues: NixOS/nix#795, #3382 (especially #3382 (comment)). |
Issue description
git
and allssl
related operations in nix-shellSteps to reproduce
git clone https://github.com/josephsdavid/forecastR.git
Technical details
``` - system:
"x86_64-linux"
Linux 5.1.15, NixOS, 19.09pre184452.5a7ab1963a9 (Loris)
yes
yes
nix-env (Nix) 2.2.2
"home-manager, nixpkgs-19.09pre174594.0c0954781e2"
"nixos-19.09pre184452.5a7ab1963a9, nixpkgs-19.09pre178895.9ebc6ad944c"
"home-manager, nixpkgs-19.09pre184398.d98a165de78"
/home/david/.nix-defexpr/channels/nixpkgs
The text was updated successfully, but these errors were encountered: