Frederik Rietdijk
Frederik Rietdijk
This is about the evaluation of NixOS tests, not actually building (that is, running) them. Building them is nice, but heavy. Evaluating them is necessary.
The issue template nowadays includes an attribute field.
This is now especially interesting with the introduction of CVE reporting by @r-ryantm https://discourse.nixos.org/t/nixpkgs-update-partners-with-serokell-and-nlnet-to-add-cve-reporting/3577/5
If ofborg can also use the commit titles, then I don't think we need to complicate the part that detects based on files. In that case it is related to...
First, Nixpkgs would need to adopt such a tag. We actually have one already that could be used `3.skill: trivial`.
how about something like `@grahamcofborg allbuilds` that would build all the rebuilds?
Quoting @LnL7 > Definitively, however in it's current form it's not really possible to use a different version depending on the target branch so changing it there would apply to...
Something like the following? ```nix $ cat default.nix let nixpkgs = fetchTarball "channel:nixos-20.03"; pkgs = import nixpkgs {}; minver = import (fetchTarball "channel:nixos-19.09") {}; # Should import minver.nix for this...
`nixpkgs` here would be the current Nixpkgs. Aside from that, it is the same as how the metrics job functions. If we do it inside Nixpkgs, we should also package...
> If you know that you have a ninja installed globally as a C++ command-line utility, maybe you can just package dummy metadata for it to satisfy meson-python? I was...