-
-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sort through the existing NixOS repositories to precise their status #1
Comments
I've just opened an issue in NixOps suggesting to sunset it one way or another |
This issue has been mentioned on NixOS Discourse. There might be relevant details there: https://discourse.nixos.org/t/tweag-nix-dev-update-53/39180/1 |
Update on that: I have a script to go over all the repositories where someone acknowledged the archival or no one reacted. @NixOS/admins, can someone either give me temporary admin rights or run that script (after careful review, of course) to act on it? |
@thufschmitt That team name is unfortunate, it's not what you think it is 😄 |
github.com/NixOS admins? Off the top of my head, @zimbatm, @domenkozar ? |
Thanks @infinisil @vcunat (and I don't think it's the first time I get bitten by this…) |
Just ran the script, this should do a good bit of clean-up. Thanks @zimbatm for the access |
Hi @thufschmitt - I think we should reopen https://github.com/NixOS/snapd-nix-base because it's still needed, even thought I expect changes to it will be very rare. Some context: I'm working on updating some content on the Nixpkgs manual and just came across That source mentions in these lines that it declares a base snap, which is built from https://github.com/NixOS/snapd-nix-base I think as long as |
Thanks for the info @DanielSidhion . There's apparently an official empty snap on the repository: https://snapcraft.io/bare, do you want to open a PR to Nixpkgs to replace EDIT: I didn't see that ours had a |
I spent too many hours trying to better understand the snap specs and environment and trying to come up with a patch that works, but I think that given the current snap specs, the current That is currently documented in NixOS/nixpkgs#293376 Given the current state of |
Sad thing to hear, but thanks for the investigation @DanielSidhion ! I'll keep it archived until/unless someone offers to fix the snap toolchain |
This issue has been mentioned on NixOS Discourse. There might be relevant details there: https://discourse.nixos.org/t/tweag-nix-dev-update-55/40996/1 |
Good catch. I've replaced it by patchelf (most starred repo that wasn't pinned). Happy for suggestions if folks prefer another one |
Cleaning-up the list of repositories under https://github.com/orgs/NixOS/repositories should give a pretty good first idea of what's going on in the ecosystem. I've collected the list here with a first estimation of their status. I propose that we:
For 3., the nix-community model of specifying the maintainers directly in the project description seems pretty good (except that we probably should make it a GitHub team as the official NixOS projects should have much more of a shared ownership)
The text was updated successfully, but these errors were encountered: