Commit
For security reasons niv should not initialize with a potentially outdated nixpkgs, that won't receive updates when even when the user calls `niv update`.
- Loading branch information
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,12 +1,12 @@ | ||
{ | ||
"branch": "release-21.05", | ||
"branch": "nixos-unstable", | ||
"description": "Nix Packages collection", | ||
"homepage": "", | ||
"homepage": null, | ||
"owner": "NixOS", | ||
"repo": "nixpkgs", | ||
"rev": "5f244caea76105b63d826911b2a1563d33ff1cdc", | ||
"sha256": "1xlgynfw9svy7nvh9nkxsxdzncv9hg99gbvbwv3gmrhmzc3sar75", | ||
"rev": "6c43a3495a11e261e5f41e5d7eda2d71dae1b2fe", | ||
This comment has been minimized.
Sorry, something went wrong.
This comment has been minimized.
Sorry, something went wrong.
nmattia
Owner
|
||
"sha256": "16f329z831bq7l3wn1dfvbkh95l2gcggdwn6rk3cisdmv2aa3189", | ||
"type": "tarball", | ||
"url": "https://github.com/NixOS/nixpkgs/archive/5f244caea76105b63d826911b2a1563d33ff1cdc.tar.gz", | ||
"url": "https://github.com/NixOS/nixpkgs/archive/6c43a3495a11e261e5f41e5d7eda2d71dae1b2fe.tar.gz", | ||
"url_template": "https://github.com/<owner>/<repo>/archive/<rev>.tar.gz" | ||
} |
rolling release, but old commit? I'm new to
niv
today and I was expecting a latest commit but discovered that it's actually not after looking up the commit. (since it'snixos-unstable
, expectations might be set to the latest commit instead of an fixed old commit)this can be mitigated by manually running
niv update nixpkgs
but it would be nice that the latest commit is being used by default.(end of thinking out loud...)