This fixes an impurity in nix-index: Previously it would take the nix-env
binary from the users PATH. I discovered this while trying to run nix-index in a
systemd service, which by default doesn't have nix-env in its path. The
errors it threw were not informative at all and it took me hours to
finally figure out the reason.
- use nix build instead of nix-build
- writes per-build log in the current working directory
- symlinks the builds in the current working directory
- detects & deduplicates build aliases
- markdown reports
- filter builds by regex
- generate nix expression files that can be build by the user
To make updating large attribute sets faster, the update scripts
are now run in parallel.
Please note the following changes in semantics:
- The string passed to updateScript needs to be a path to an executable file.
- The updateScript can also be a list: the tail elements will then be passed
to the head as command line arguments.
* bunny: init at 1.1
Motivation for this change
Pretty useful not to have to think about what system you're on when
doing basic (un)installation tasks.
* Fixed typo
Cargo.nix was generated from cargo-download 0.1.1 with this patch
applied, which was necessary to not confuse carnix about the version
being different between Cargo.toml and Cargo.lock.
See https://github.com/Xion/cargo-download/pull/3.
From 5efd4cf11ff9d5042712303404169016b1e05c33 Mon Sep 17 00:00:00 2001
From: Alyssa Ross <hi@alyssa.is>
Date: Thu, 26 Jul 2018 21:19:06 +0200
Subject: [PATCH] Fix Cargo.lock
Running `cargo build` on a clean checkout produces a diff in Cargo.lock,
because it wasn't updated after the version number was bumped.
After this commit, `cargo build` should no longer produce a modified
working tree.
---
Cargo.lock | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Cargo.lock b/Cargo.lock
index cc7357c..c384dc1 100644
--- a/Cargo.lock
+++ b/Cargo.lock
@@ -76,7 +76,7 @@ dependencies = [
[[package]]
name = "cargo-download"
-version = "0.1.0"
+version = "0.1.1"
dependencies = [
"ansi_term 0.9.0 (registry+https://github.com/rust-lang/crates.io-index)",
"clap 2.27.1 (registry+https://github.com/rust-lang/crates.io-index)",
--
2.17.1
This causes collisions between the build outputs of `nix` when building
in an environment with `nix1.perl-bindings` and `nix`:
```
collision between `/nix/store/aa4rrcj7dg2xj4rfkiclcmp745ibqng0-nix-2.0.4/lib/libnixstore.so' and `/nix/store/sp0sdi4bll80h58big1iy8kkh3qqxpw2-nix-1.11.16/lib/libnixstore.so'
builder for '/nix/store/wgbccin107lhm8cv9imnnvkx1j2pgibc-hydra-perl-deps.drv' failed with exit code 25
```
Unlike on linux these are not namespaced per user so this will cause
build failures if /tmp/nix-test was not removed by a previous build if
the nixbld user id doesn't match by accident. Nix already creates a
unique tempdir for builds so we can use that instead.
Fixes#44172
This makes the command ‘nix-env -qa -f. --arg config '{skipAliases =
true;}'’ work in Nixpkgs.
Misc...
- qtikz: use libsForQt5.callPackage
This ensures we get the right poppler.
- rewrites:
docbook5_xsl -> docbook_xsl_ns
docbook_xml_xslt -> docbook_xsl
diffpdf: fixup
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/createrepo_c/versions.
These checks were done:
- built on NixOS
- /nix/store/japb72abhyigv3na7jb2jnslg4m5lvks-createrepo_c-0.11.0/bin/createrepo_c passed the binary check.
- /nix/store/japb72abhyigv3na7jb2jnslg4m5lvks-createrepo_c-0.11.0/bin/mergerepo_c passed the binary check.
- /nix/store/japb72abhyigv3na7jb2jnslg4m5lvks-createrepo_c-0.11.0/bin/modifyrepo_c passed the binary check.
- /nix/store/japb72abhyigv3na7jb2jnslg4m5lvks-createrepo_c-0.11.0/bin/sqliterepo_c passed the binary check.
- 4 of 4 passed binary check by having a zero exit code.
- 0 of 4 passed binary check by having the new version present in output.
- found 0.11.0 with grep in /nix/store/japb72abhyigv3na7jb2jnslg4m5lvks-createrepo_c-0.11.0
- directory tree listing: https://gist.github.com/58f40cce4b69dd806f345f13d65833cb
- du listing: https://gist.github.com/4f61dce7f9bacb5093fb7cec50712fc1
* treewide: http -> https sources
This updates the source urls of all top-level packages from http to
https where possible.
* buildtorrent: fix url and tab -> spaces
This adds a best-effort hack to run AppImages, which currently don't
work out-of-the-box on NixOS. This is not preferable to using packaged
applications, but may help users if the application they want to run
is not in nixpkgs.
It uses the package list from the Steam chroot, but without Steam
packages.
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/pacman/versions.
These checks were done:
- built on NixOS
- /nix/store/mgfrpaqbzbby4qy7wxj20h6dx0dh1sqz-pacman-5.1.0/bin/repo-add passed the binary check.
- /nix/store/mgfrpaqbzbby4qy7wxj20h6dx0dh1sqz-pacman-5.1.0/bin/makepkg passed the binary check.
- /nix/store/mgfrpaqbzbby4qy7wxj20h6dx0dh1sqz-pacman-5.1.0/bin/pacman-db-upgrade passed the binary check.
- /nix/store/mgfrpaqbzbby4qy7wxj20h6dx0dh1sqz-pacman-5.1.0/bin/pacman-key passed the binary check.
- /nix/store/mgfrpaqbzbby4qy7wxj20h6dx0dh1sqz-pacman-5.1.0/bin/pkgdelta passed the binary check.
- /nix/store/mgfrpaqbzbby4qy7wxj20h6dx0dh1sqz-pacman-5.1.0/bin/repo-elephant passed the binary check.
- /nix/store/mgfrpaqbzbby4qy7wxj20h6dx0dh1sqz-pacman-5.1.0/bin/repo-remove passed the binary check.
- /nix/store/mgfrpaqbzbby4qy7wxj20h6dx0dh1sqz-pacman-5.1.0/bin/vercmp passed the binary check.
- Warning: no invocation of /nix/store/mgfrpaqbzbby4qy7wxj20h6dx0dh1sqz-pacman-5.1.0/bin/testpkg had a zero exit code or showed the expected version
- Warning: no invocation of /nix/store/mgfrpaqbzbby4qy7wxj20h6dx0dh1sqz-pacman-5.1.0/bin/cleanupdelta had a zero exit code or showed the expected version
- /nix/store/mgfrpaqbzbby4qy7wxj20h6dx0dh1sqz-pacman-5.1.0/bin/pacman passed the binary check.
- /nix/store/mgfrpaqbzbby4qy7wxj20h6dx0dh1sqz-pacman-5.1.0/bin/pacman-conf passed the binary check.
- /nix/store/mgfrpaqbzbby4qy7wxj20h6dx0dh1sqz-pacman-5.1.0/bin/makepkg-template passed the binary check.
- 11 of 13 passed binary check by having a zero exit code.
- 0 of 13 passed binary check by having the new version present in output.
- found 5.1.0 with grep in /nix/store/mgfrpaqbzbby4qy7wxj20h6dx0dh1sqz-pacman-5.1.0
- directory tree listing: https://gist.github.com/61f365ecd9146adf48fc68403568904d
- du listing: https://gist.github.com/391d88c911aeda73c0cd89f80ced8ce2
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/packagekit/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/lxwq08kfybd0zlg06xk0zj606nlpk3bn-packagekit-1.1.10/bin/pkcon -h’ got 0 exit code
- ran ‘/nix/store/lxwq08kfybd0zlg06xk0zj606nlpk3bn-packagekit-1.1.10/bin/pkcon --help’ got 0 exit code
- ran ‘/nix/store/lxwq08kfybd0zlg06xk0zj606nlpk3bn-packagekit-1.1.10/bin/pkmon -h’ got 0 exit code
- ran ‘/nix/store/lxwq08kfybd0zlg06xk0zj606nlpk3bn-packagekit-1.1.10/bin/pkmon --help’ got 0 exit code
- found 1.1.10 with grep in /nix/store/lxwq08kfybd0zlg06xk0zj606nlpk3bn-packagekit-1.1.10
- directory tree listing: https://gist.github.com/1d641323594032d2e935bd1e088bf409
The isSeccomputable flag treated Linux without seccomp as just a
normal variant, when it really should be treated as a special case
incurring complexity debt to support.
Semi-automatic update. These checks were performed:
- built on NixOS
- ran `/nix/store/cjkfm1v60ykkmnqbpwc5ikhrrghklj1n-mynewt-newt-1.3.0-bin/bin/newt -h` got 0 exit code
- ran `/nix/store/cjkfm1v60ykkmnqbpwc5ikhrrghklj1n-mynewt-newt-1.3.0-bin/bin/newt --help` got 0 exit code
- ran `/nix/store/cjkfm1v60ykkmnqbpwc5ikhrrghklj1n-mynewt-newt-1.3.0-bin/bin/newt help` got 0 exit code
- ran `/nix/store/cjkfm1v60ykkmnqbpwc5ikhrrghklj1n-mynewt-newt-1.3.0-bin/bin/newt version` and found version 1.3.0
- ran `/nix/store/cjkfm1v60ykkmnqbpwc5ikhrrghklj1n-mynewt-newt-1.3.0-bin/bin/newtmgr -h` got 0 exit code
- ran `/nix/store/cjkfm1v60ykkmnqbpwc5ikhrrghklj1n-mynewt-newt-1.3.0-bin/bin/newtmgr --help` got 0 exit code
- ran `/nix/store/cjkfm1v60ykkmnqbpwc5ikhrrghklj1n-mynewt-newt-1.3.0-bin/bin/newtmgr help` got 0 exit code
- found 1.3.0 with grep in /nix/store/cjkfm1v60ykkmnqbpwc5ikhrrghklj1n-mynewt-newt-1.3.0-bin
- found 1.3.0 in filename of file in /nix/store/cjkfm1v60ykkmnqbpwc5ikhrrghklj1n-mynewt-newt-1.3.0-bin
cc "@pjones @ehmry @lethalman"
This reverts commit 695027f61c.
We really can't have "nix-env -i nix" *not* upgrade nixUnstable to a
newer nixStable. For instance, it would cause "nix upgrade-nix" to
produce a user environment with collisions.
as discussed in bed3695848
Different names make it easier for the users to notice updates to Nix stable,
and to have Nix stable and unstable simultaneously.
This reverts commit bed3695848.
This commit effectively makes it impossible to upgrade to nixUnstable
with nix-env without mucking about with priorities, as you can't
uninstall the old nix transactionally with the new nix and if you
uninstall the old one first you no longer have nix at your disposal to
install the new one.
This reverts commit 9711aac642.
One should depend on
- `stdenv.cc.bintools`: for executables at build time
- `libbfd` or `libiberty`: for those libraries
- `targetPackages.cc.bintools`: for exectuables at *run* time
- `binutils`: only for specifically GNU Binutils's executables, regardless of
the host platform, at run time.
Main change: glibc: 2.25-x -> 2.26-y, containing security fixes,
and various features and deprecations. Unfortunately, some of the
latter still cause (transitively) a couple hundred newly failing jobs.
I'm not delaying anymore, so that we have the security fix on master.
I mainly patched gcc, llvm and icu, but I can't fix everything...
