summaryrefslogtreecommitdiffstats
path: root/pkgs/build-support
AgeCommit message (Collapse)Author
2021-01-15Merge branch 'master' into staging-nextJan Tojnar
2021-01-15dockerTools: typoRobert Hensing
Italian.
2021-01-15Merge master into staging-nextgithub-actions[bot]
2021-01-15dockerTools: fix build (#109420)Milan
2021-01-14Merge branch 'master' into staging-nextJan Tojnar
2021-01-13treewide: emacsPackages -> emacs.pkgs & emacsWithPackages -> ↵adisbladis
emacs.pkgs.withPackages The previous names are now aliases and shouldn't be used anywhere inside nixpkgs.
2021-01-12Merge master into staging-nextgithub-actions[bot]
2021-01-12Merge pull request #109050 from xaverdh/rust-writerLassulus
writers: add writeRust and deduplicate binary stripping
2021-01-12Merge pull request #109030 from xaverdh/modules-closure-ignore-missing-firmwareJörg Thalheim
nixos/modules-closure.sh: don't fail if firmware is missing
2021-01-12writers: add test for rustDominik Xaver Hörl
2021-01-12writers: add rustDominik Xaver Hörl
2021-01-11writers: deduplicate binary stripping logicDominik Xaver Hörl
2021-01-11Merge master into staging-nextgithub-actions[bot]
2021-01-11fetchgit: add lfs supportJonathan Ringer
2021-01-11nixos/modules-closure.sh: don't fail if firmware is missingDominik Xaver Hörl
Since fdf32154fc90698ef72ffa96ef39d920e1b9c951, we no longer allow missing modules in the initrd. Unfortunately since before this commit, the modules-closure script would also fail on missing firmware, which is a very common case (e.g. xhci-pci.ko.xz lists renesas_usb_fw.mem as dependent firmware). Fix this by only issuing a warning instead.
2021-01-11Merge branch 'master' into staging-nextJan Tojnar
2021-01-11treewide: with stdenv.lib; in meta -> with lib;Profpatsch
Part of: https://github.com/NixOS/nixpkgs/issues/108938 meta = with stdenv.lib; is a widely used pattern. We want to slowly remove the `stdenv.lib` indirection and encourage people to use `lib` directly. Thus let’s start with the meta field. This used a rewriting script to mostly automatically replace all occurances of this pattern, and add the `lib` argument to the package header if it doesn’t exist yet. The script in its current form is available at https://cs.tvl.fyi/depot@2f807d7f141068d2d60676a89213eaa5353ca6e0/-/blob/users/Profpatsch/nixpkgs-rewriter/default.nix
2021-01-10Merge staging-next into stagingFrederik Rietdijk
2021-01-10Merge master into staging-nextFrederik Rietdijk
2021-01-10Merge pull request #107958 from ztzg/x-16304-ubuntu-determinismJörg Thalheim
vmTools.debClosureGenerator: Fix non-determinism in dependency graph
2021-01-09Merge staging-next into stagingFrederik Rietdijk
2021-01-09Merge branch 'master' into staging-nextMichael Weiss
Manually resolved a conflict in pkgs/development/libraries/libbladeRF/default.nix.
2021-01-09coqPackages: refactorCyril Cohen
2021-01-08Merge staging-next into staginggithub-actions[bot]
2021-01-08Merge master into staging-nextgithub-actions[bot]
2021-01-08defaultCrateOverrides: override crates necessary for building sequoiaJustin Humm
See https://git.sr.ht/~erictapen/sequoia for a flake using these overrides.
2021-01-08defaultCrateOverrides: pkgconfig -> pkg-configJustin Humm
2021-01-08Merge pull request #108581 from roberth/dockerTools-don't-apologizeDaniël de Kok
dockerTools: Don't apologize
2021-01-08Merge staging-next into staginggithub-actions[bot]
2021-01-08Merge master into staging-nextgithub-actions[bot]
2021-01-08emacs: fix accidental double wrapper (Darwin)Alyssa Ross
This was already fixed on non-Darwin, but the fix missed that it was also reintroduced for the Darwin code path at the same time. Fixes: dd5d2482c9d ("emacs: Fix accidental double wrapping")
2021-01-07Merge branch 'staging-next' into stagingJan Tojnar
2021-01-07Merge branch 'master' into staging-nextJan Tojnar
https://github.com/NixOS/nixpkgs/commit/b04fc593e7b55fe1f74421b11589f12a339c92e2 seems to have accidentally changed mkDerivation function for dfilemanager and solarus-quest-editor so I have reverted that here.
2021-01-07Merge pull request #108081 from ↵Sandro
SuperSandro2000/silence-file-format-not-recognized setup-hooks/strip: silence 'File format not recognized' errors again
2021-01-06dockerTools: Don't apologizeRobert Hensing
Warning about future breaking changes is wrong. - It suggests that the maintainers don't value backwards compatibility. They do. - It implies that other parts of Nixpkgs won't ever break. They will. - It implies that a well-defined "public" interface exists. It doesn't. - If the reasons above didn't apply, it should have been in the manual instead. Breaking changes will come, especially to the interface. That can be the only way we can make progress without breaking the image _contents_. I don't think dockerTools is any different from most of Nixpkgs in these regards.
2021-01-05Merge pull request #108416 from srhb/streamlayeredimage-symlinked-storepathsRobert Hensing
dockerTools: Fix streamLayeredImage for symlinks
2021-01-04dockerTools: Test buildLayeredImage with symlinksSarah Brofeldt
This exercises layer creation in face of store path symlinks, ensuring they are not dereferenced, which can lead to broken layer tarballs
2021-01-04dockerTools: Fix streamLayeredImage for symlinksSarah Brofeldt
When archiving `/nix/store/foo` and `foo` is itself a symlink, we must not traverse the symlink target, but archive the `foo` symlink itself
2021-01-03Merge staging-next into staginggithub-actions[bot]
2021-01-03Merge pull request #107715 from NixOS/revert-106172-nix-gitignore-perfKevin Cox
Reverts https://github.com/NixOS/nixpkgs/pull/106172 ef3ed45c1240197b721f38a01ec48e7dc6e7c179 This change causes issues with negative patterns. Reverting now until those can be resolved.
2021-01-02Merge pull request #106954 from r-burns/randomseedAndreas Rammhold
[staging] stdenv: trim random seed to avoid reference cycles
2021-01-02setup-hooks/strip: silence 'File format not recognized' errors againSandro Jäckel
This got lost in e4d17dc558f61f8565df025fa46de7035c4a1d93.
2020-12-31Merge staging-next into stagingFrederik Rietdijk
2020-12-31buildRustPackage: add `cargoHash` for SRI hashes of vendored depsDaniël de Kok
`buildRustPackage` currently accepts `cargoSha256` as a hash for vendored dependencies. This change adds `cargoHash` which accepts SRI hashes, setting `outputHashAlgo` to `null`. The hash mismatch message still uses `cargoSha256` as an example, which it probably should until we completely switch to SRI hashes.
2020-12-30Merge staging-next into staginggithub-actions[bot]
2020-12-30vmTools.debClosureGenerator: Fix non-determinism in dependency graphDamien Diederen
By default, Perl versions since 5.8.1 use randomization to make hashes resistant to complexity attacks. That randomization makes building VM images such as ubuntu1804x86_64 non-deterministic because the (imported) derivations built by deb/deb-closure.pl are not stable. This can easily be observed by repeating the following sequence of commands and noting the path of the image's .drv: nix-instantiate -E '(import <nixpkgs> {}).vmTools.diskImageFuns.ubuntu1804x86_64 {}' nix-store --delete /nix/store/*ubuntu-18.04-bionic-amd64.nix One source of non-determinism is the handling of Provides/Replaces, which depends on the order of iteration over %packages. Here is a diff showing the corresponding change in output: >>> awk -virtual awk: using original-awk - original-awk: libc6 (>= 2.14) +virtual awk: using mawk + mawk: libc6 (>= 2.14) - mawk: libc6 (>= 2.14) ->>> libc6 This patch sorts packages by name for Provides/Replaces processing, which seems to result in stable output. (If the above turns out not to be sufficient, one could also set the PERL_HASH_SEED and PERL_PERTURB_KEYS environment variables, documented in 'perlrun', to disable Perl's built-in randomization. Complexity attacks are not an issue as we control and trust all inputs.)
2020-12-27buildFhsUserenv: don't downgrade root userJörg Thalheim
2020-12-27bintools-wrapper: skip dynamic linker for static binariesJörg Thalheim
2020-12-27Revert "nix-gitignore: Optimise performance"Kevin Cox
2020-12-25autoPatchelf: add comment why ignore failing ldd/sedDavHau