| Age | Commit message (Collapse) | Author |
|---|
|
In particular, this disallows attribute names containing dots or
starting with dots. Hydra already disallowed these. This affects the
following packages in Nixpkgs master:
2048-in-terminal
2bwm
389-ds-base
90secondportraits
lispPackages.3bmd
lispPackages.hu.dwim.asdf
lispPackages.hu.dwim.def
Closes #1342.
|
|
nix-channel: error out if direct tarball unpack fails.
|
|
|
|
|
|
http://hydra.nixos.org/build/51569816
|
|
|
|
These are no longer used anywhere.
|
|
|
|
This dumps the entire Nix configuration, including all options that
have default values.
|
|
This makes all config options self-documenting.
Unknown or unparseable config settings and --option flags now cause a
warning.
|
|
|
|
|
|
|
|
The typical use is to inherit Config and add Setting<T> members:
class MyClass : private Config
{
Setting<int> foo{this, 123, "foo", "the number of foos to use"};
Setting<std::string> bar{this, "blabla", "bar", "the name of the bar"};
MyClass() : Config(readConfigFile("/etc/my-app.conf"))
{
std::cout << foo << "\n"; // will print 123 unless overriden
}
};
Currently, this is used by Store and its subclasses for store
parameters. You now get a warning if you specify a non-existant store
parameter in a store URI.
|
|
|
|
|
|
|
|
Process nix.conf options in "new" commands, add test
|
|
It's very unlikely a path ending in .tar.gz is a directory
Fixes #1318
|
|
Default to 5 download retries
|
|
We've observed it failing downloads in the wild and retrying the same URL
a few moments later seemed to fix it.
|
|
This should help certain downloaders that don't request anything special
for the number of retries, like nix-channel.
|
|
Also, possible fix for #1310 on 32-bit systems.
|
|
Using the empty string is likely to be ambiguous in some contexts.
|
|
Without this (minor) change, the options set using "--option"
or read from nix.conf were parsed but not used.
|
|
|
|
This provides a significant speedup, e.g. 64 s -> 12 s for
nix-build --dry-run -I nixpkgs=channel:nixos-16.03 '<nixpkgs/nixos/tests/misc.nix>' -A test
on a cold local and CloudFront cache.
The alternative is to use lots of concurrent daemon connections but
that seems wasteful.
|
|
|
|
|
|
This is useless because the client also caches path info, and can
cause problems for long-running clients like hydra-queue-runner
(i.e. it may return cached info about paths that have been
garbage-collected).
|
|
E.g. you can now redirect /etc/resolv.conf to a different file.
|
|
Not every distribution uses nscd.
|
|
This fixes "No such file or directory" when opening /dev/ptmx
(e.g. http://hydra.nixos.org/build/51094249).
The reason appears to be some changes to /dev/ptmx / /dev/pts handling
between Linux 4.4 and 4.9. See
https://patchwork.kernel.org/patch/7832531/.
The fix is to go back to mounting a proper /dev/pts instance inside
the sandbox. Happily, this now works inside user namespaces, even for
unprivileged users. So
NIX_REMOTE=local?root=/tmp/nix nix-build \
'<nixpkgs/nixos/tests/misc.nix>' -A test
works for non-root users.
The downside is that the fix breaks sandbox builds on older kernels
(probably pre-4.6), since mounting a devpts fails inside user
namespaces for some reason I've never been able to figure out. Builds
on those systems will fail with
error: while setting up the build environment: mounting /dev/pts: Invalid argument
Ah well.
|
|
|
|
|
|
|
|
|
|
Execute a given program with the (optional) given arguments as the
user running the evaluation, parsing stdout as an expression to be
evaluated.
There are many use cases for nix that would benefit from being able to
run arbitrary code during evaluation, including but not limited to:
* Automatic git fetching to get a sha256 from a git revision
* git rev-parse HEAD
* Automatic extraction of information from build specifications from
other tools, particularly language-specific package managers like
cabal or npm
* Secrets decryption (e.g. with nixops)
* Private repository fetching
Ideally, we would add this functionality in a more principled way to
nix, but in the mean time 'builtins.exec' can be used to get these
tasks done.
The primop is only available when the
'allow-unsafe-native-code-during-evaluation' nix option is true. That
flag also enables the 'importNative' primop, which is strictly more
powerful but less convenient (since it requires compiling a plugin
against the running version of nix).
|
|
These were generated by a legacy tool.
|
|
|
|
Fixes #1285.
|
|
|
|
|
|
This is consistent with the behaviour of the old
download-from-binary-cache substituter.
|
|
This corresponds to the NixOS default.
|
|
Fixes #1283.
|
|
|
|
NixOps needs this.
|
|
|
|
nix-shell/pure: keep environment variable SHLVL
|
