00cecf2731
Includes the following version changes: - skalibs: 2.10.0.1 -> 2.10.0.2 - execline: 2.7.0.0 -> 2.8.0.0 - s6-networking: 2.4.0.0 -> 2.4.1.0 - s6-linux-init: 1.0.6.0 -> 1.0.6.1 - s6: 2.10.0.0 -> 2.10.0.2 Upstream maintainer notes: ------------------------------------------------------------ Mon, 15 Feb 2021 19:50:14 +0000 Hello, New versions of some of the skarnet.org packages are available. skalibs-2.10.0.2: bugfixes execline-2.8.0.0: major version bump, but few and low-impact changes s6-2.10.0.2: bugfixes s6-linux-init-1.0.6.1: bugfixes s6-networking-2.4.1.0: minor version bump Some details: * execline-2.8.0.0 ---------------- - The if program now propagates its child's exit code by default if it exits. - The backtick program's -i behaviour (exit on child failure or presence of a null character in its output) is now the default. Other behaviours in case of child failure can be obtained via -I, -x or -D options; -x is the new one. - These changes are compatible with all the common uses of if and backtick, but break compatibility in edge cases, which is why a major version bump is required. This has nothing in common with the previous major version bump, which had massive changes all over the place; this one should go smoothly, and will only impact very specific uses of backtick. execline now has man pages, thanks to the untiring flexibeast! The repository can be found here: https://github.com/flexibeast/execline-man-pages Please allow some time for the man pages to be updated to reflect the current HTML documentation. Currently, the man pages document execline-2.7.0.1; they are accurate for 2.8.0.0 except for the if and backtick changes. * s6-linux-init-1.0.6.1 --------------------- - Bugfixes. - When s6-linux-init is built with utmps, the default utmp user for s6-linux-init-maker was set to "utmp". That was a bug: now, by default, s6-linux-init-maker does not create the utmp services if the -U option is not given. If you used s6-linux-init-maker without the -U option and still need the utmps services, you should explicitly set "-U utmp". https://skarnet.org/software/s6-linux-init/ git://git.skarnet.org/s6-linux-init * s6-networking-2.4.1.0 --------------------- - Bugfixes (nothing security-related). - It is now possible to define a maximum amount of time spent in the TLS handshake no matter how s6-networking has been built. (The -K option has been implemented for the libtls backend.) - When SNI has been required, the TLS-related binaries now export the SSL TLS SNI SERVERNAME option to their application; the variable contains the relevant server name. https://skarnet.org/software/s6-networking/ git://git.skarnet.org/s6-networking s6-networking has man pages as well: https://github.com/flexibeast/s6-networking-man-pages Enjoy, Bug-reports welcome. -- Laurent ------------------------------------------------------------ Copied from: http://skarnet.org/cgi-bin/archive.cgi?1:mss:1535:202102:lpehbljhhcpaopbnkkbf |
||
|---|---|---|
| .github | ||
| doc | ||
| lib | ||
| maintainers | ||
| nixos | ||
| pkgs | ||
| .editorconfig | ||
| .gitattributes | ||
| .gitignore | ||
| .version | ||
| 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
- IRC - #nixos on freenode.net
- NixOS Weekly
- Community-maintained wiki
- Community-maintained list of ways to get in touch (Discord, Matrix, Telegram, other IRC channels, 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 20.09 release
- Tests for unstable/master
- Tests for the NixOS 20.09 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 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.