-
Notifications
You must be signed in to change notification settings - Fork 331
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
Cannot devenv shell
in fresh project
#1071
Labels
bug
Something isn't working
Comments
Can you post your |
@shyim yep!
|
can you try changing |
Worked: ⌚️8:29:03 📂~/trash/devenv-test
$> cat devenv.yaml ~/trash/devenv-test
# inputs:
# nixpkgs:
# url: github:cachix/devenv-nixpkgs/rolling
inputs:
nixpkgs:
url: github:NixOS/nixpkgs/nixpkgs-unstable
# If you're using non-OSS software, you can set allowUnfree to true.
# allowUnfree: true
# If you're willing to use a package that's vulnerable
# permittedInsecurePackages:
# - "openssl-1.1.1w"
# If you have more than one devenv you can merge them
#imports:
# - ./backend
⌚️8:29:13 📂~/trash/devenv-test
$> devenv shell ~/trash/devenv-test
• Building shell ...
• Failed to get cachix caches due to evaluation error
✔ Building shell in 28.0s.
• Entering shell
✨ devenv 1.0.1 is out of date. Please update to 1.0.2: https://devenv.sh/getting-started/#installation
hello from devenv
git version 2.44.0
fatal: not a git repository (or any of the parent directories): .git
⌚08:30:02 📁~/trash/devenv-test 🌵
nix shell> |
Seems like something weird with the devenv rolling nixpkgs version. But that's temporary and will be changed when the Python fixes are merged 🤔 |
This will get fixed with cachix/devenv-nixpkgs#1 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
running
devenv init
thendevenv shell
in an empty directory fails after trying to build for 45 minutes.To reproduce
Here's the full shell output of what i did:
Version
$> devenv version devenv 1.0.1 (aarch64-darwin)
Installed via nix-darwin on MacOS 14.1.1
The text was updated successfully, but these errors were encountered: