bf33c0e62e
Maintainers Notes below. ~~~ Hello, New versions of all the skarnet.org packages are available. skalibs has undergone a major update, with a few APIs having disappeared, and others having changed. Compatibility with previous versions is *not* assured. Consequently, all the rest of the skarnet.org software has undergone at least a release bump, in order to build with the new skalibs. But some packages also have new functionality added (hence, a minor bump), and others also have their own incompatible changes (hence, a major bump). The new versions are the following: skalibs-2.11.0.0 (major) nsss-0.2.0.0 (major) utmps-0.1.0.3 (release) execline-2.8.1.0 (minor) s6-2.11.0.0 (major) s6-rc-0.5.2.3 (release) s6-portable-utils-2.2.3.3 (release) s6-linux-utils-2.5.1.6 (release) s6-linux-init-1.0.6.4 (release) s6-dns-2.3.5.2 (release) s6-networking-2.5.0.0 (major) mdevd-0.1.5.0 (minor) bcnm-0.0.1.4 (release) dnsfunnel-0.0.1.2 (release) Additionally, a new package has been released: smtpd-starttls-proxy-0.0.1.0 Dependencies have all been updated to the latest versions. They are, this time, partially strict: libraries and binaries may build with older releases of their dependencies, but not across major version bumps. The safest approach is to upgrade everything at the same time. You do not need to recompile your s6-rc service databases or recreate your s6-linux-init run-images. You should restart your supervision tree after upgrading skalibs and s6, as soon as is convenient for you. Details of major and minor package changes follow. * skalibs-2.11.0.0 ---------------- - A lot of obsolete or useless functionality has been removed: libbiguint, rc4, md5, iobuffer, skasigaction, environ.h and getpeereid.h headers, various functions that have not proven their value in a while. - Some functions changed signatures or changed names, or both. - All custom types ending in _t have been renamed, to avoid treading on POSIX namespace. (The same change has not been done yet in other packages, but skalibs was the biggest offender by far.) - Signal functions have been deeply reworked. - cdb has been reworked, the API is now more user-friendly. - New functions have been added. The deletion of significant portions of code has made skalibs leaner. libskarnet.so has dropped under 190 kB on x86_64. The cdb rewrite on its own has helped reduce an important amount of boilerplate in cdb-using code. All in all, code linked against the new skalibs should be slightly smaller and use a tiny bit less RAM. https://skarnet.org/software/skalibs/ git://git.skarnet.org/skalibs * nsss-0.2.0.0 ------------ - Bugfixes. - nsss-switch wire protocol slightly modified, which is enough to warrant a major version bump. - _r functions are now entirely thread-safe. - Spawned nsssd programs are now persistent and only expire after a timeout on non-enumeration queries. This saves a lot of forking with applications that can call primitives such as getpwnam() repeatedly, as e.g. mdevd does when initially parsing its configuration file. - New nsssd-switch program, implementing real nsswitch functionality by dispatching queries to various backends according to a script. It does not dlopen a single library or read a single config file. https://skarnet.org/software/nsss/ git://git.skarnet.org/nsss * execline-2.8.1.0 ---------------- - Bugfixes. - New binary: case. It compares a value against a series of regular expressions, executing into another command line on the first match. https://skarnet.org/software/execline/ git://git.skarnet.org/execline * s6-2.11.0.0 ----------- - Bugfixes. - Some libs6 header names have been simplified. - s6-svwait now accepts -r and -R options. - s6-supervise now reads an optional lock-fd file in the service directory; if it finds one, the first action of the service is to take a blocking lock. This prevents confusion when a controller process dies while still leaving workers holding resources; it also prevents log spamming on user mistakes (autobackgrounding services, notably). - New binaries: s6-socklog, s6-svlink, s6-svunlink. The former is a rewrite of smarden.org's socklog program, in order to implement a fully functional syslogd with only s6 programs. The latter are tools that start and stop services by symlinking/unlinking service directories from a scan directory, in order to make it easier to integrate s6-style services in boot scripts for sequential service managers such as OpenRC. https://skarnet.org/software/s6/ git://git.skarnet.org/s6 * s6-networking-2.5.0.0 --------------------- - Bugfixes. - minidentd has been removed. It was an old and somehow still buggy piece of code that was only hanging around for nostalgia reasons. - Full support for client certificates. Details of the client certificate are transmitted to the application via environment variables (or via an environment string in the case of opportunistic TLS). - Full SNI support, including server-side. (That involved a deep dive into the bearssl internals, which is why it took so long.) The filenames containing secret keys and certificates for <domain> are read in the environment variables KEYFILE:<domain> and CERTFILE:<domain>. Complete client certificate and SNI support now make the TLS part of s6-networking a fully viable replacement of stunnel and other similar TLS tunneling tools. This is most interesting when s6-networking is built against bearssl, which uses about 1/9 of the resources that OpenSSL needs. https://skarnet.org/software/s6-networking/ git://git.skarnet.org/s6-networking * mdevd-0.1.5.0 ------------- - A new option to mdevd is available: -O <nlgroups>. This option makes mdevd rebroadcast uevents to a netlink group (or set of netlink groups) once they have been handled. This allows applications to read uevents from a netlink group *after* the device manager is done with them. This is useful, for instance, when pairing mdevd with libudev-zero for full udev emulation. - The * and & directives, which previously were only triggered by "add" and "remove" actions, are now triggered by *all* action types. This gives users full scripting access to any event, which can be used to implement complex rules similar to udev ones. These two changes make it possible to now build a full-featured desktop system based on mdevd + libudev-zero, without running systemd-udevd or eudev. https://skarnet.org/software/mdevd/ git://git.skarnet.org/mdevd * smtpd-starttls-proxy-0.0.1.0 ---------------------------- This new package, in conjunction with the latest s6-networking, implements the STARTTLS functionality for inetd-like mail servers that do not already support it. (Currently only tested with qmail-smtpd.) If you have noticed that sending mail to skarnet.org supports STARTTLS now, it is thanks to this little piece of software. https://skarnet.org/software/smtpd-starttls-proxy/ git://git.skarnet.org/smtpd-starttls-proxy Enjoy, Bug-reports welcome. Laurent |
||
|---|---|---|
| .github | ||
| doc | ||
| lib | ||
| maintainers | ||
| nixos | ||
| pkgs | ||
| .editorconfig | ||
| .gitattributes | ||
| .gitignore | ||
| .version | ||
| CONTRIBUTING.md | ||
| COPYING | ||
| default.nix | ||
| flake.nix | ||
| README.md | ||
Nixpkgs is a collection of over 60,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
- Discourse Forum
- Matrix Chat
- NixOS Weekly
- Community-maintained wiki
- Community-maintained list of ways to get in touch (Discord, Telegram, IRC, etc.)
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.
- Continuous package builds for unstable/master
- Continuous package builds for the NixOS 21.05 release
- Tests for unstable/master
- Tests for the NixOS 21.05 release
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:
masteris the main branch where all small contributions gostagingis branched from master, changes that have a big impact on Hydra builds go to this branchstaging-nextis 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.