| Age | Commit message (Collapse) | Author |
|---|
|
A partner of builtins.getContext, useful for the same reasons.
|
|
This can be very helpful when debugging, as well as enabling complex
black magic like surgically removing a single dependency from a
string's context.
|
|
Previously, plain derivation paths in the string context (e.g. those
that arose from builtins.storePath on a drv file, not those that arose
from accessing .drvPath of a derivation) were treated somewhat like
derivaiton paths derived from .drvPath, except their dependencies
weren't recursively added to the input set. With this change, such
plain derivation paths are simply treated as paths and added to the
source inputs set accordingly, simplifying context handling code and
removing the inconsistency. If drvPath-like behavior is desired, the
.drv file can be imported and then .drvPath can be accessed.
This is a backwards-incompatibility, but storePath is never used on
drv files within nixpkgs and almost never used elsewhere.
|
|
Issue #2623.
|
|
|
|
|
|
This reverts commit e8b0efdcc9d6329b299937790360cac8b9b256c9.
|
|
This reverts commit 80f464d9d72839841422f75e78ce725365cc3d71.
|
|
EvalState::resetFileCache: clear parse cache as well as eval cache
|
|
remove some dead code in nix/repl.cc
|
|
Escape square brackets in configure.ac
|
|
This patch attempts to solve the regression introduced in e8b0efdc
(#2607).
|
|
Update nlohmann-json 3.0.1 -> 3.5.0
|
|
Remove some bashisms from configure.ac
|
|
[Needs testing and review] Remove dead code
|
|
The manual reference was commented out, and the sole reference to this
program other than the configure script. Removed both.
|
|
|
|
|
|
|
|
Fixes #2546.
(at least the basic reproduction I've been testing)
|
|
"configure.ac" is used to generate "configure", which is supposed to be
run with /bin/sh (as suggested by the shebang line of "configure"). As a
result it is a good idea to remove any /bin/sh-incompatible syntax from
configure.ac. Otherwise, systems that do not use Bash as their /bin/sh
are unable to run "configure" due to syntax errors.
|
|
Fixes a static analyzer warning:
Expression 'isDrv' is always false.
Fixes: 3beb6f6e7 ('Show derivations more concisely')
|
|
https://github.com/nlohmann/json/releases/tag/v3.5.0
|
|
```
$ curl -L
"https://github.com/nlohmann/json/releases/download/v3.4.0/json.hpp" -o
src/nlohmann/json.hpp
```
|
|
nix-store: remove debugging print
|
|
tests/fetchurl: fix after changing default hash from 512 to 256
|
|
|
|
|
|
Clarify nix-instantiate --read-write-mode
|
|
|
|
SRI hashes (https://www.w3.org/TR/SRI/) combine the hash algorithm and
a base-64 hash. This allows more concise and standard hash
specifications. For example, instead of
import <nix/fetchurl.nl> {
url = https://nixos.org/releases/nix/nix-2.1.3/nix-2.1.3.tar.xz;
sha256 = "5d22dad058d5c800d65a115f919da22938c50dd6ba98c5e3a183172d149840a4";
};
you can write
import <nix/fetchurl.nl> {
url = https://nixos.org/releases/nix/nix-2.1.3/nix-2.1.3.tar.xz;
hash = "sha256-XSLa0FjVyADWWhFfkZ2iKTjFDda6mMXjoYMXLRSYQKQ=";
};
In fixed-output derivations, the outputHashAlgo is no longer mandatory
if outputHash specifies the hash (either as an SRI or in the old
"<type>:<hash>" format).
'nix hash-{file,path}' now print hashes in SRI format by default. I
also reverted them to use SHA-256 by default because that's what we're
using most of the time in Nixpkgs.
Suggested by @zimbatm.
|
|
docs: add missing prerequisites: brotli, boost, libseccomp
|
|
nix repl: don't create result symlinks
|
|
probably typo
|
|
|
|
...at least MSVC unable to compile this
|
|
|
|
libstore: improve hash mismatch error messages
|
|
Use the same output ordering and format everywhere.
This is such a common issue that we trade the single-line error message for
more readability.
Old message:
```
fixed-output derivation produced path '/nix/store/d4nw9x2sy9q3r32f3g5l5h1k833c01vq-example.com' with sha256 hash '08y4734bm2zahw75b16bcmcg587vvyvh0n11gwiyir70divwp1rm' instead of the expected hash '1xzwnipjd54wl8g93vpw6hxnpmdabq0wqywriiwmh7x8k0lvpq5m'
```
New message:
```
hash mismatch in fixed-output derivation '/nix/store/d4nw9x2sy9q3r32f3g5l5h1k833c01vq-example.com':
wanted: sha256:1xzwnipjd54wl8g93vpw6hxnpmdabq0wqywriiwmh7x8k0lvpq5m
got: sha256:08y4734bm2zahw75b16bcmcg587vvyvh0n11gwiyir70divwp1rm
```
|
|
https://hydra.nixos.org/build/85827920
|
|
nar-info-disk-cache: include ca in the cache entries
|
|
Without this information the content addressable state and hashes are
lost after the first request, this causes signatures to be required for
everything even tho the path could be verified without signing.
|
|
|
|
s3: make scheme configurable
|
|
|
|
This enables using for http for S3 request for debugging or
implementations that don't have https configured. This is not a problem
for binary caches since they should not contain sensitive information.
Both package signatures and AWS auth already protect against tampering.
|
|
Solve hg "abandoned transaction" issue
|
|
|
|
|
|
|
