Nix Packages collection & NixOS
Go to file
Sebastián Mancilla 70b3662a67 shogun: disable broken test
Shogun has been broken for a while [0].

Looks like the latest update to openblas, by f07a0615ea (openblas:
0.3.20 -> 0.3.21, 2022-08-10), broke the `libshogun-mathematics_lapack`
example. It calculates the eigenvectors for a matrix, but the assertions
now fail:

    compute_eigenvectors
    A=[
    [       -0.500000000000000111,  0.707106781186547351,   0.5],
    [       0.707106781186547351,   1.04083408558608426e-16,        0.707106781186547129],
    [       -0.499999999999999722,  -0.707106781186547462,  0.5]
    ]
    eigenvalues=[-1.41421356237309492,1.04083408558608426e-17,1.41421356237309492]
    terminate called after throwing an instance of 'shogun::ShogunException'

The darwin build output shows a bit more detail:

    assertion is_equal(A(0,0), 0.5, eps) failed in void test_ev()
    file /tmp/nix-build-shogun-6.1.4.drv-0/source/examples/undocumented/libshogun/mathematics_lapack.cpp
    line 49

Disable the test to fix the build, although the results seem "correct".
It appears that openblas now calculates values with slightly less
precision, thus the assertion fails due to the expected epsilon.

[0]: https://hydra.nixos.org/build/194671473
2023-05-21 22:34:01 -04:00
.github github/CODEOWNERS: drop nbp 2023-05-14 14:11:54 +00:00
doc doc/python: remove usages of fetchPypi aliases 2023-05-21 11:28:13 -04:00
lib lib: fix typos 2023-05-19 22:09:24 -04:00
maintainers maintainers: update email for emilytrau 2023-05-22 09:46:31 +10:00
nixos Merge pull request #233245 from teutat3s/zhf/fix-prometheus-exporter-domain 2023-05-21 22:05:56 +02:00
pkgs shogun: disable broken test 2023-05-21 22:34:01 -04:00
.editorconfig lib.toPlist: keep test output in external files for their tab indents 2023-03-27 19:25:52 +02:00
.git-blame-ignore-revs git-blame-ignore-revs: fix commit hash 2022-08-25 12:13:09 +02:00
.gitattributes .gitattributes: fix typo 2023-05-01 12:30:00 +02:00
.gitignore gitignore: add emacs "swap files" 2022-10-31 18:00:22 +01:00
.mailmap mailmap: cleanup shortlog stats for nixos-22.11 release 2022-12-02 13:01:53 +01:00
.version 23.05 is Stoat 2022-11-21 21:22:27 +01:00
CONTRIBUTING.md CONTRIBUTING.md: Clarify guidelines for meta.description 2023-04-24 12:44:11 +00:00
COPYING COPYING: 2022 -> 2023 2023-01-01 13:23:08 +02:00
default.nix
flake.nix nixosModules.pkgsReadOnly: init 2023-05-10 15:55:09 +02:00
README.md Release NixOS 22.11 2022-11-30 11:52:38 +01:00

NixOS logo NixOS logo

Contributors badge Open Collective supporters

Nixpkgs is a collection of over 80,000 software packages that can be installed with the Nix package manager. It also implements NixOS, a purely-functional Linux distribution.

Manuals

  • NixOS Manual - how to install, configure, and maintain a purely-functional Linux distribution
  • Nixpkgs Manual - contributing to Nixpkgs and using programming-language-specific Nix expressions
  • Nix Package Manager Manual - how to write Nix expressions (programs), and how to use Nix command line tools

Community

Other Project Repositories

The sources of all official Nix-related projects are in the NixOS organization on GitHub. Here are some of the main ones:

  • Nix - the purely functional package manager
  • NixOps - the tool to remotely deploy NixOS machines
  • nixos-hardware - NixOS profiles to optimize settings for different hardware
  • Nix RFCs - the formal process for making substantial changes to the community
  • NixOS homepage - the NixOS.org website
  • hydra - our continuous integration system
  • NixOS Artwork - NixOS artwork

Continuous Integration and Distribution

Nixpkgs and NixOS are built and tested by our continuous integration system, Hydra.

Artifacts successfully built with Hydra are published to cache at https://cache.nixos.org/. When successful build and test criteria are met, the Nixpkgs expressions are distributed via Nix channels.

Contributing

Nixpkgs is among the most active projects on GitHub. While thousands of open issues and pull requests might seem a lot at first, it helps consider it in the context of the scope of the project. Nixpkgs describes how to build tens of thousands of pieces of software and implements a Linux distribution. The GitHub Insights page gives a sense of the project activity.

Community contributions are always welcome through GitHub Issues and Pull Requests. When pull requests are made, our tooling automation bot, OfBorg will perform various checks to help ensure expression quality.

The Nixpkgs maintainers are people who have assigned themselves to maintain specific individual packages. We encourage people who care about a package to assign themselves as a maintainer. When a pull request is made against a package, OfBorg will notify the appropriate maintainer(s). The Nixpkgs committers are people who have been given permission to merge.

Most contributions are based on and merged into these branches:

  • master is the main branch where all small contributions go
  • staging is branched from master, changes that have a big impact on Hydra builds go to this branch
  • staging-next is branched from staging and only fixes to stabilize and security fixes with a big impact on Hydra builds should be contributed to this branch. This branch is merged into master when deemed of sufficiently high quality

For more information about contributing to the project, please visit the contributing page.

Donations

The infrastructure for NixOS and related projects is maintained by a nonprofit organization, the NixOS Foundation. To ensure the continuity and expansion of the NixOS infrastructure, we are looking for donations to our organization.

You can donate to the NixOS foundation through SEPA bank transfers or by using Open Collective:

License

Nixpkgs is licensed under the MIT License.

Note: MIT license does not apply to the packages built by Nixpkgs, merely to the files in this repository (the Nix expressions, build scripts, NixOS modules, etc.). It also might not apply to patches included in Nixpkgs, which may be derivative works of the packages to which they apply. The aforementioned artifacts are all covered by the licenses of the respective packages.