When modSha256 is null, disable the nix sandbox instead of using a
fixed-output derivation. This requires the nix-daemon to have
`sandbox = relaxed` set in their config to work properly.
Because the output is (hopefully) deterministic based on the inputs,
this should give a reproducible output. This is useful for development
outside of nixpkgs where re-generating the modSha256 on each mod.sum
changes is cumbersome.
Don't use this in nixpkgs! This is why null is not the default value.
This is required to run `travis console` but is not part of the upstream
dependency list. Upstream is also not compatible with pry 0.12+ and
breaks with this error `uninitialized constant Pry::SIMPLE_PROMPT`.
Fixes#73238
There were two issues:
* builtins.getEnv was called deep into the nixpkgs tree making it hard
to discover. This is solved by moving the call into
pkgs/top-level/impure.nix
* when the config was explicitly set by the user to false, it would
still try and load the environment variable. This meant that it was
not possible to guarantee the same outcome on two different systems.
One issue with cargoSha256 is that it's hard to detect when it needs to
be updated or not. It's possible to upgrade a package and forget to
update cargoSha256 and run with old versions of the program or
libraries.
This commit introduces `verifyCargoDeps` which, when enabled, will check
that the Cargo.lock is not out of date in the cargoDeps by comparing it
with the package source.
Because the gemdir was referenced on the derivation, it would cause the
whole gemdir to get added to the store, which would in turn force the
derivation to be rebuilt whenever unrelated folder files would change.
Create new categories for the issues:
* Bug report
* Packaging request
* Security
Add metadata information to the issues so that we may match issues to
maintainers using a bot in the future.
The old `.github/ISSUE_TEMPLATE.md` is being used by the "Open a regular
issue." link.
The team behind ksonnet was aquired by VMware, and they decided to end
work on ksonnet:
From https://blogs.vmware.com/cloudnative/2019/02/05/welcoming-heptio-open-source-projects-to-vmware:
> Prior to the acquisition, Heptio had been shifting focus and resources
> away from ksonnet; with the acquisition, we felt it was the right time
> to rethink our investment in ksonnet. As a result, work on ksonnet will
> end and the GitHub repositories will be archived. It’s extremely
> difficult to step back from a project we have worked so hard on, but
> we’re excited about our new ideas and vision for changing how developers
> experience the Kubernetes and cloud native ecosystems.
Package attrs should map to the pname. It's confusing otherwise.
pkg-config is also the name used by most distributions:
Debian, Homebrew, Guix, OpenSuse
other distributions like FreeBSD ports, Fedora and Arch Linux call it
"pkgconf"
Waiting a few releases to make a tree-wide change to make it easier to
back-port things.
We need the latest gox to support the latest go releases better.
Unfortunately the author doesn't seem interesting in making new releases
(1y already since the last release).
Encouraging to put container elements on their own lines to minimize
diffs, merge conflicts and making re-ordering easier.
Nix doesn't suffer the restrictions of other languages where commas are
used to separate list items.
providers are already compiled independently so we don't need Hydra to
follow terraform_MAJ_MIN_full to have them all compiled.
Instead of having to create two aliases per release, add a "full"
passthru for that common use-case.
Eg:
terraform_0_11_full -> terraform_0_11.full
On Linux the `$TMPDIR` is `/build`. The TMPDIR audit looks for `$TMPDIR`
in the build output, which will then fail with packages like
/buildkite-agent.
This fixes the heuristic to look for `$TMPDIR/` instead.
zimbatm