3
0
Fork 0
forked from mirrors/nixpkgs
Nix Packages collection
Go to file
volth fd1ac66836 perlPackages.HTTPDaemon: 6.04 -> 6.01
This undoes 6fb0e7a4e0
The only problem with 6.04 is: it got new dependencies which fail to cross-compile.
Failure to cross-compile HTTP::Deamon leads to failure of LWP and XML::Parser, which are used in switch-to-configuration.pl
Thus upgrade HTTPDaemon from 6.01 to 6.04 broke cross-compilation of whole system closures.
2019-04-26 00:43:41 +00:00
.github CODEOWNERS: add myself to files related to the hardened profile 2019-04-18 16:49:53 +02:00
doc python-docs: typo 2019-04-23 10:37:10 +01:00
lib Merge pull request #56555 from matthewbauer/wasm 2019-04-23 22:44:33 -04:00
maintainers Merge pull request #58994 from zookatron/sublime-merge 2019-04-24 09:21:07 -04:00
nixos Merge staging into staging-next 2019-04-24 18:38:11 +02:00
pkgs perlPackages.HTTPDaemon: 6.04 -> 6.01 2019-04-26 00:43:41 +00:00
.editorconfig
.gitattributes
.gitignore
.version
COPYING COPYING: include 2019 2019-03-18 19:55:33 -07:00
default.nix
README.md

logo

Code Triagers Badge

Nixpkgs is a collection of packages for the Nix package manager. It is periodically built and tested by the Hydra build daemon as so-called channels. To get channel information via git, add nixpkgs-channels as a remote:

% git remote add channels https://github.com/NixOS/nixpkgs-channels.git

For stability and maximum binary package support, it is recommended to maintain custom changes on top of one of the channels, e.g. nixos-18.09 for the latest release and nixos-unstable for the latest successful build of master:

% git remote update channels
% git rebase channels/nixos-18.09

For pull requests, please rebase onto nixpkgs master.

NixOS Linux distribution source code is located inside nixos/ folder.

Communication:

Note: MIT license does not apply to the packages built by Nixpkgs, merely to the package descriptions (Nix expressions, build scripts, and so on). 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.