Jonathan Ringer

> IMO, "fetchers for version-controlled repositories" would be a suitable target. This includes fetchers based on specific version control systems (e.g. fetchcvs, fetchsvn, fetchgit, fetchhg, fetchbzr, etc.) and fetchers based...

@oxij I would like to nominate you as a shepherd, looks like you've thought about this longer than I've been involved in nixpkgs. I like your addition of a lib...

This seems to be aligned with a similar attempt of mine https://github.com/NixOS/rfcs/pull/114 from 2021. The goal has been moved from "these are acceptable behaviors in this CoC" (114) to "these...

Hey shepherds, even if implementation is still ongoing, you can move this into FCP. The implementation doesn't need to be completed before this RFC has been merged. Seems like there's...

maybe the nix tooling should warn if a flake input is a tag? Then again, some flakes may just provide utility functions (e.g. `numtide-flakeutils`). And Tagging would actually make sense

Well, it's the 11th hour, and I think for the 21.05 release, I will follow the steps as laid out before me. For the next release we can be more...

From the hydra side, I don't think this will be much of an issue: ``` version = fileContents ../.version; versionSuffix = (if stableBranch then "." else "beta") + "${toString (nixpkgs.revCount...

For sustainability, we should probably have an automated pipeline, which can be launched by release-managers. Just need an admin to add the secrets

you can click on "details" related to the check, and it will give you some output: ``` cannot import '/nix/store/c4adan2iicfjxyrkj8w0nywzdvf5x7ja-nvim-typescript-rplugin.nix', since path '/nix/store/psm7wwifgn8sik1i1yxafnrxagrzjshm-nvim-typescript-rplugin.nix.drv' is not valid, at /var/lib/ofborg/checkout/repo/38dca4e3aa6bca43ea96d2fcc04e8229/mr-est/packet-spot-eval-2/lib/customisation.nix:119:45 ```

yea, a derivation was being passed to `callPackage`, made a suggestion: https://github.com/NixOS/nixpkgs/pull/89553#discussion_r441698442