* use attrname in log messages instead of github handle
* don't remove users simply for empty github handles, if their user
still exists (prevents #259555)
This will allow buliding bootstrap tools for platforms with
non-default libcs, like *-unknown-linux-musl.
This gets rid of limitedSupportSystems/systemsWithAnySupport. There
was no need to use systemsWithAnySupport for supportDarwin, because it
was always equivalent to supportedSystems for that purpose, and the
only other way it was used was for determining which platforms to
build the bootstrap tools for, so we might as well use a more explicit
parameter for that, and then we can change how it works without
affecting the rest of the Hydra jobs.
Not affecting the rest of the Hydra jobs is important, because if we
changed all jobs to use config triples, we'd end up renaming every
Hydra job. That might still be worth thinking about at some point,
but it's unnecessary at this point (and would be a lot of work).
I've checked by running
nix-eval-jobs --force-recurse pkgs/top-level/release.nix
that the actual bootstrap tools derivations are unaffected by this
change, and that the only other jobs that change are ones that depend
on the hash of all of Nixpkgs. Of the other jobset entrypoints that
end up importing pkgs/top-level/release.nix, none used the
limitedSupportedSystems parameter, so they should all be unaffected as
well.
The nixpkgs documentation mentions how to update out of tree plugins but
one problem is that it requires a nixpkgs clone.
This makes it more convenient.
I've had the need to generate vim plugins and lua overlays for other
projects unrelated to nix and this will make updates easier (aka just
run `nix run nixpkgs#vimPluginsUpdater -- --proc=1` or with the legacy commands:
`nix-shell -p vimPluginsUpdater --run vim-plugins-updater`.
I added an optional "nixpkgs" argument to command line parser, which is the path
towards a nixpkgs checkout. By default the current folder.
update-luarocks-packages: format with black
qyliss confirmed this
Haven't seen ericson2314 do maint work on it, and he'd tell me if he wanted to.
Co-authored-by: Silvan Mosberger <github@infinisil.com>
The module system isn't about NixOS, so for consistent messaging,
I'd like to rename this.
If some of you would like to be in a team responsible for NixOS'
_use_ of the module system, that would be great, but for consistency
it should be a separate team.
Note that this attribute isn't used anywhere - only generically at
release time for the status update pings.
and drop package maintainership for removed maintainers.
PlayerNameHere is now known on github as dixslyf. Editing maintainer-list.nix…
Borlaag likely deleted their github account
bhootjb is now known on github as jyssh. Editing maintainer-list.nix…
IvanMalison is now known on github as colonelpanic8. Editing maintainer-list.nix…
jonnybolton is now known on github as jonnynightingale. Editing maintainer-list.nix…
ee2500 likely deleted their github account
lethalman is now known on github as lucabrunox. Editing maintainer-list.nix…
theHedgehog0 is now known on github as pyrox0. Editing maintainer-list.nix…
maddiethecafebabe likely deleted their github account
nebulka1 likely deleted their github account
christianharke is now known on github as rake5k. Editing maintainer-list.nix…
razvan-flavius-panda is now known on github as freeman42x. Editing maintainer-list.nix…
joscha has no github handle
RichterOliver is now known on github as ORichterSec. Editing maintainer-list.nix…
DomesticMoth is now known on github as asciimoth. Editing maintainer-list.nix…
pjbarnoy is now known on github as waaamb. Editing maintainer-list.nix…
