Nixtamal: Fulfilling input pinning for Nix

Announcements
41

Definitely put a cookbook entry for it if that would be easy and/or fun!

1 Like
42

Good question what you want a cooldown relative to. One could argue for «the older commit of master 7 days ago and nixos-unstable now».

43

This does not guarantee that the choosen commit has been tested and verified by hydra. It might be a commit that is unbootable!

2 Likes
44

True, recently nixos-unstable has been about 7 days behind anyhow with Hydra builds.

45

I’ve recently tried this tool for finding out which nearest commit is in the public cache:
blitz/hydrasect: The tool that makes bisecting nixpkgs pleasant

46

Commits being “cached” is not the same as “commits being tested by hydra to ensure that neither the succesfully built kernel, boot loader, nor whatever important thing is faulty”.

47

Oh, I didn’t think of that. If we had Arbitrary reactions in Discourse I’d have reacted with :thinking: to that.

1 Like
48

Thanks @NobbZ I edited my comment to include a ‘disclaimer’.

Luckily I was not planning to use this anyway :smiley:

But I guess one would not have a hard time to fetch a build that works from Hydra, instead of Github with a similar solution.

To avoid derailing @toastal’s topic any further, I’ll leave it at that. The main takeaway seems to be: just let the input pinner do the input pinning.

1 Like
49

If anyone wants to know how to use multiple versions of Nixpkgs with Nixtamal: Using multiple version of Nixpkgs | Nixtamal

3 Likes
50

Nixtamal 1.8.0 released

  • NEW: Blueprints

    nixtamal set-up --blueprint BLUEPRINT, along with the basic setup, makes a default file structure + a demo package. Supported options are release & release-split for release.nix-style setups. A --blueprint release would make:

    ├── nix
│   ├── overlay
│   │   ├── default.nix
│   │   └── development.nix
│   ├── package
│   │   ├── demo.nix
│   │   └── dev-shell.nix
│   └── tamal
│       ├── default.nix
│       ├── lock.json
│       └── manifest.kdl
├── default.nix
├── release.nix
└── shell.nix

    where users can now have a basic working framework to build on as well as just being able to run nix-build release.nix -A demo

    I had gotten a lot of questions about how to set up / structure a classic Nix project, so now there’s a command you can build on.

  • Nixtamal subcommand manpages now shipped

  • lock/refresh now primes the silo if missing

4 Likes