Skip to content

Conversation

@Cluyverth
Copy link

Adding my personal NUR repository, cluyverth/nur-packages, which currently includes the package for the Helium Browser (v0.6.7.1) and will be used for other personal/community Nix derivations.


  • [ x ] I ran ./bin/nur format-manifest after updating repos.json (We will use the same script in github actions to make sure we keep the format consistent)
  • [ x ] By including this repository in NUR, I confirm that any copyrightable content in the repository (other than built derivations or patches, if applicable) is licensed under the MIT license
  • [ x ] I confirm that meta.license and meta.sourceProvenance have been set correctly for any derivations for unfree or not built from source packages

Additionally, the following points are recommended:

  • [ x ] All applicable meta fields have been filled out. See https://nixos.org/manual/nixpkgs/stable/#sec-standard-meta-attributes for more information. The following fields are particularly helpful and can always be filled out:
    • [ x ] meta.description, so consumers can confirm that that your package is what they're looking for
    • [ x ] meta.license, even for free packages
    • [ x ] meta.homepage, for tracking and deduplication
    • [ x ] meta.mainProgram, so that nix run works correctly

@Cluyverth Cluyverth force-pushed the add-cluyverth-repo branch 9 times, most recently from 1476fee to d30cc7f Compare November 21, 2025 15:00
@Cluyverth
Copy link
Author

Hello!

I am submitting my repository cluyverth/nur-packages to the list.

While debugging my submission, I noticed that the CI logs were flooded with fatal errors from other repositories (such as bandithedoge triggering restricted mode violations). This "noise" made it extremely difficult to pinpoint the issues in my own build.

To make the logs readable and the tests clearer, I took the liberty of removing these failing repositories in a separate commit.

Note to maintainers: Since I separated the changes, if you prefer not to remove the other repositories at this time, please feel free to only merge/cherry-pick the commit that adds cluyverth and ignore the cleanup commit.

Thanks!

@Cluyverth Cluyverth closed this Nov 22, 2025
@Cluyverth Cluyverth reopened this Nov 22, 2025
@Cluyverth
Copy link
Author

Whoops, sorry about that! I accidentally closed this PR by mistake (missclick). Reopening it now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant