about summary refs log tree commit diff
AgeCommit message (Collapse)AuthorFilesLines
2019-06-16 Hopefully fix macOS testsEelco Dolstra1-4/+6
2019-06-16 Set $TERMEelco Dolstra1-0/+3
2019-06-16 Run builds in a pseudo-terminalEelco Dolstra1-8/+46
This allows many programs (e.g. gcc, clang, cmake) to print colorized log output (assuming $TERM is set to a value like "xterm"). There are other ways to get colors, in particular setting CLICOLOR_FORCE, but they're less widely supported and can break programs that parse tool output.
2019-06-16 Style fixEelco Dolstra1-1/+1
2019-06-15 nix: Add -L alias for --print-build-logsEelco Dolstra1-0/+1
2019-06-15 Fix test failures when $TMPDIR changesEelco Dolstra4-10/+8
(cherry picked from commit c38c726eb5d447c7e9d894d57cd05ac46c173ddd)
2019-06-15 nix: Support -j flagEelco Dolstra2-4/+9
2019-06-15 Merge pull request #2931 from NinjaTrappeur/nin-add-warning-setting-untrustedGraham Christensen1-1/+1
Daemon: warn when an untrusted user cannot override a setting
2019-06-15 Daemon: warn when an untrusted user cannot override a settingFélix Baylac-Jacqué1-1/+1
In a daemon-based Nix setup, some options cannot be overridden by a client unless the client's user is considered trusted. Currently, if an untrusted user tries to override one of those options, we are silently ignoring it. This can be pretty confusing in certain situations. e.g. a user thinks he disabled the sandbox when in reality he did not. We are now sending a warning message letting know the user some options have been ignored. Related to #1761.
2019-06-04 Merge pull request #2918 from JorisE/patch-1Eelco Dolstra1-1/+1
Minor typo
2019-06-04 Minor typoJorisE1-1/+1
2019-06-01 Fix segfault in builtin fetchurl with hashed mirrors + SRI hashesEelco Dolstra2-1/+6
2019-06-01 Merge pull request #2910 from worldofpeace/fundingEelco Dolstra1-0/+3
Add .github/FUNDING.yml
2019-05-31 Add .github/FUNDING.ymlworldofpeace1-0/+3
2019-05-31 Merge pull request #2905 from ln-nl/patch-1Eelco Dolstra1-1/+1
release-common: fix build with `config.allowAliases = false`
2019-05-30 release-common: fix build with `config.allowAliases = false`ln-nl1-1/+1
```sh > nix build -f release.nix build.x86_64-linux error: undefined variable 'docbook5_xsl' at /vcs/nix/release-common.nix:45:7 ```
2019-05-30 Merge pull request #2892 from johannes-climacus/masterEelco Dolstra1-4/+4
Replace `type` with `command -v` in install script
2019-05-29 Replace `type` with `command -v` in install scriptJohannes Climacus1-4/+4
In POSIX sh, `type` is undefined. cf. https://pubs.opengroup.org/onlinepubs/9699919799/utilities/command.html#tag_20_22_04
2019-05-29 Enable more fromTOML testsEelco Dolstra2-17/+15
cpptoml now parses almost all examples from the spec.
2019-05-29 Fix eval-okay-fromTOML testEelco Dolstra1-1/+1
Turns out we were mis-parsing single-quoted attributes, e.g. 'key2'.
2019-05-29 bump cpptoml to v0.1.1Ding Xiang Fei1-179/+390
2019-05-28 Iterate over referencesEelco Dolstra1-6/+6
2019-05-28 Merge branch 'attrPaths' of https://github.com/NinjaTrappeur/nixEelco Dolstra7-3/+46
2019-05-22 Merge pull request #2880 from Ma27/document-optional-attrs-with-at-patternEelco Dolstra1-1/+19
doc: clarify that optional attrs in a function argument will be ignored unless specified
2019-05-21 doc: clarify that optional attrs in a function argument will be ignored ↵Maximilian Bosch1-1/+19
unless specified In `args@{ a ? 1 }: /* ... */` the value `a` won't be a part of `args` unless it's specified when calling the function, the default value will be ignored in this case. My personal point of view is that this behavior is a matter of taste, at least I was pretty sure that unmatched arguments will be a part of `args@` while debugging some Nix code last week. I decided to add a warning to the docs which hopefully reduces the confusion of further Nix developers who thought the same about `args@`.
2019-05-21 Merge pull request #2800 from flokli/progress-bar-hide-unknown-expectedEelco Dolstra1-4/+11
progress-bar: hide expected if expected is 0 (unknown)
2019-05-21 Merge pull request #2812 from matthewbauer/fix-nix-scriptsEelco Dolstra2-8/+2
Sync NIX_PROFILES between single-user and multi-user modes
2019-05-17 fetchGit -> fetchTarballEelco Dolstra2-2/+2
(cherry picked from commit cbfdea685764bf66443a999e672656c54289b8c9)
2019-05-17 docs: describe $IN_NIX_SHELL values (#2796)Vladimír Čunát1-1/+2
See commit 1bffd83e1a9
2019-05-15 Don’t set NIX_REMOTE=daemon in daemon profileMatthew Bauer1-6/+0
This is now autodetected. There is no need to put it in the profile.
2019-05-15 Sync NIX_PROFILES between single-user and multi-user modesMatthew Bauer1-2/+2
When we are in single user mode, we still want to have access to profiles. This way things in Nixpkgs that rely on them getting set accurately are done in both cases. The point where I hit this is with using aspell which looks in NIX_PROFILES: https://github.com/NixOS/nixpkgs/blob/master/pkgs/development/libraries/aspell/default.nix Before this patch, NIX_PROFILES was never set in single user mode! This corrects that.
2019-05-15 Merge pull request #2810 from NixOS/print-build-logsEelco Dolstra4-13/+39
nix: Add --print-build-logs flag
2019-05-15 nix: Add --print-build-logs flagEelco Dolstra4-13/+39
This causes 'nix' to print build log output to stderr rather than showing the last log line in the progress bar. Log lines are prefixed by the name of the derivation (minus the version string), e.g. binutils> make[1]: Leaving directory '/build/binutils-2.31.1' binutils-wrapper> unpacking sources binutils-wrapper> patching sources ... binutils-wrapper> Using dynamic linker: '/nix/store/kr51dlsj9v5cr4n8700jliyz8v5b2q7q-bootstrap-stage0-glibc/lib/ld-linux-x86-64.so.2' bootstrap-stage2-gcc-wrapper> unpacking sources ... linux-headers> unpacking sources linux-headers> unpacking source archive /nix/store/8javli69jhj3bkql2c35gsj5vl91p382-linux-4.19.16.tar.xz
2019-05-15 nix-profile: Add all channels to $NIX_PATHEelco Dolstra1-4/+3
Fixes #2709.
2019-05-15 Fix shellcheck errorEelco Dolstra1-1/+1
https://hydra.nixos.org/build/93359951
2019-05-13 Merge pull request #2802 from LnL7/fix-needs-hashrewriteEelco Dolstra2-12/+19
build: move needsHashRewrite initialization to startBuilder
2019-05-12 Merge pull request #2798 from grahamc/diff-hookEelco Dolstra6-17/+338
build: run diff-hook under --check and document diff-hook
2019-05-12 runProgram: Uncomment chdir supportGraham Christensen1-2/+2
2019-05-12 build: make needsHashRewrite a methodDaiderd Jordan1-12/+16
2019-05-12 handleDiffHook: stop passing allowVforkGraham Christensen1-3/+1
2019-05-12 Clarify where output from the diff hook goes.Graham Christensen1-4/+5
2019-05-12 runProgram: support gid, uid, chdirGraham Christensen3-24/+32
2019-05-12 chdir, setgroupsGraham Christensen1-0/+4
2019-05-12 diff hook: execute as the build user, and pass the temp dirGraham Christensen5-28/+51
2019-05-12 build: run diff-hook under --check and document diff-hookGraham Christensen4-16/+303
2019-05-12 build: add test for sandboxed --checkDaiderd Jordan1-0/+3
2019-05-12 build: move needsHashRewrite initialization to startBuilderDaiderd Jordan1-7/+7
The value of useChroot is not set yet in the constructor, resulting in hash rewriting being enabled in certain cases where it should not be. Fixes #2801
2019-05-11 progress-bar: hide expected if expected is 0 (unknown)Florian Klink1-4/+11
Sometimes, "expected" can be "0", but in fact means "unknown". This is for example the case when downloading a file while the http server doesn't send the `Content-Length` header, like when running `nix build` pointing to a nixpkgs checkout streamed from GitHub: ⇒ nix build -f https://github.com/NixOS/nixpkgs/archive/master.tar.gz hello [1.8/0.0 MiB DL] downloading 'https://github.com/NixOS/nixpkgs/archive/master.tar.gz' In that case, don't show that weird progress bar, but only the (slowly increasing) downloaded size ("done"). ⇒ nix build -f https://github.com/NixOS/nixpkgs/archive/master.tar.gz hello [1.8 MiB DL] downloading 'https://github.com/NixOS/nixpkgs/archive/master.tar.gz' This commit also updates fmt calls with three numbers (when something is currently 'running' too) - I'm not sure if this can be provoked, but showing "0" as expected doesn't make any sense, as we're obviously doing more than nothing.
2019-05-08 nix-shell: Don't absolutize '-p' expressionsEelco Dolstra1-5/+7
This prevents spurious syscalls like 25011 lstat("/home/eelco/with import <nixpkgs> { }; (pkgs.runCommandCC or pkgs.runCommand) \"shell\" { buildInputs = [ (hello) ]; } \"\"", 0x7ffe9c67f580) = -1 ENOENT (No such file or directory)
2019-05-08 Merge pull request #2594 from LnL7/darwin-10.12.6Graham Christensen1-3/+5
installer: update macOS version check to 10.12.2
generated by cgit-pink 1.4.1 (git 2.44.2) at 2024-09-19T20·49+0000