artiq-fast: pin nixpkgs, use in artiq-board-generated+artiq-full #49

Open
astro wants to merge 1 commits from astro/nix-scripts:pin-nixpkgs into master
astro commented 7 months ago

Fixes gitea issue #31

Unfortunately, I was not able to access <nixpkgs>/.git for the same trick we use to pin artiqSrc and sinaraSystemsSrc. Therefore the pinning is static.

Fixes gitea issue #31 Unfortunately, I was not able to access `<nixpkgs>/.git` for the same trick we use to pin `artiqSrc` and `sinaraSystemsSrc`. Therefore the pinning is static.
astro added 1 commit 7 months ago
Owner

If we're doing it that way (but I'm not sure that's the best way), then the hydra nixpkgs input should be removed.
Wouldn't flakes fix this in a better way?

If we're doing it that way (but I'm not sure that's the best way), then the hydra nixpkgs input should be removed. Wouldn't flakes fix this in a better way?
Poster

If we're doing it that way (but I'm not sure that's the best way), then the hydra nixpkgs input should be removed.

That runs except for the initial pkgs.fetchgit to fetch the pinned nixpkgs. buitins.fetchGit is not available in restricted mode.

Wouldn't flakes fix this in a better way?

I'm playing with flakes excessively these weeks. hydra-unstable exhibits random regressions again...

> If we're doing it that way (but I'm not sure that's the best way), then the hydra nixpkgs input should be removed. That runs except for the initial `pkgs.fetchgit` to fetch the pinned nixpkgs. `buitins.fetchGit` is not available in restricted mode. > Wouldn't flakes fix this in a better way? I'm playing with flakes excessively these weeks. hydra-unstable exhibits random regressions again...
This pull request has changes conflicting with the target branch.
artiq-fast/default.nix
artiq-full.nix
Sign in to join this conversation.
No reviewers
No Label
No Milestone
No Assignees
2 Participants
Notifications
Due Date

No due date set.

Dependencies

This pull request currently doesn't have any dependencies.

Loading…
There is no content yet.