Adds a configure phase for packages using premake.
premakeConfigurePhase runs the correct premake version for the premake
you are using (see premake_cmd).
Some packages don’t work correctly with pie. Here I disable it for:
- busybox
- linux kernel
- kexectools
I also get rid of the Musl conditional for disabling pie in GCC and
Binutils. Some day we might want to enable PIE without Musl and it
will be useful to have the *just* work with our compiler and linkers.
These don’t like having -fPIE set for them. We should disable
hardening all the time, but in the interest of not changing hashes,
this only disables it for Musl (where it is now the default).
(cherry picked from commit a3a6884649354a660326acd68c1bd08ffd2dcfa2)
These packages should in theory work with our GCC toolchains, but
there are some definite breakages that need to be tracked down.
Comparing output of these to old gcc-arm-embedded is important.
Affected packages include:
- axolooti
- avrdudess
- opentx
- microscheme
- betaflight
- inav
- blackmagic
- simavr
- gnuk
* circleci-cli: 0.1.0 -> 0.1.2307
We are also building from source now, instead of using a pre-packaged
version. This means we need Go. Also did minor refactors.
* circleci-cli: removed unneeded dependencies
This has been not touched in 6 years. Let's remove it to cause less
problems when adding new cross-compiling infrastructure.
This also simplify gcc significantly.
Useful update-- adds support for accepting multiple files as arguments
and fixes handling of large executables (>2Gb).
While touching this, modify version to include more info.
Preserving version format previously used, although not usual style.
This bumps Hydra to the latest revision available. As Hydra doesn't have
a release model (and therefore no tags) ATM, the derivation will pin
against the actual git revision and the date of the commit in the
derivation name.
Additionally the following changes have been made:
* Dropped `postUnpack` phase. It is useful when working with the Hydra
source (and no dirty changes shall be used in `release.nix`, but is has
no use in `nixpkgs`).
* Added myself as maintainer to have more folks available in case of
future breakage.
* Implemented support for Nix 2.0 and `unstable` (currently 2.1):
Since 1672bcd230447f1ce0c3291950bdd9a662cee974 in NixOS/nix the
evaluator differentiates between `settings` and `evalSettings`.
Previously `restrictEval` in `hydra-eval-jobs.cc` has been set in
`settings`, this doesn't work anymore in Nix 2.1 and is therefore
incompatible to Nix 2.0 on an API level.
To resolve this, the flag `isGreaterNix20` parses the version string
of `pkgs.nix` and applies a patch if nix.version<=2.0.
Furthermore the Hydra build with Nix 2.1 requires `boost` as build input
which is not needed for Nix 2.0. To avoid unnecessary increase in the
closure size this library will only used as build input for
nix.version>2.0.
* Fixed the NixOS test for `hydra`:
disabled binary cache to allow sandbox builds (otherwise it would
query `cache.nixos.org` during the Hydra build inside the test).
Additionally the trivial.nix jobset required simplification (as done
in NixOS/hydra, e.g. tests/api-test.nix) as bash is not available in
the build sandbox as builder (even when adding pkgs.bash to
systemPackages).
The easiest workaround to confirm a the functionality of a jobset
without importing nixpkgs is to use the default shell /bin/sh which
is mounted from `pkgs.busybox` into the build env
(https://github.com/NixOS/nixpkgs/pull/44841#discussion_r209751972) in the
VM and a named pipe to create $out.
Closes#44044
* The ELK stack is upgraded to 6.3.2.
* `elasticsearch6`, `logstash6` and `kibana6` now come with X-Pack which is
a suite of additional features. These are however licensed under the unfree
"Elastic License".
* Fortunately they also provide OSS versions which are now packaged
under: `elasticsearch6-oss`, `logstash6-oss` and `kibana6-oss`.
Note that the naming of the attributes is consistent with upstream.
* The test `nix-build nixos/tests/elk.nix -A ELK-6` will test the OSS
version by default. You can also run the test on the unfree ELK using:
`NIXPKGS_ALLOW_UNFREE=1 nix-build nixos/tests/elk.nix -A ELK-6 --arg enableUnfree true`
In 3027bca, binutils was upgraded from 2.28.1 to 2.30. However, in 2.30,
the ldmain.c file within binutils, which the nixpkgs new-dtags.patch
file is meant to modify, was changed in such a way that the patch no
longer works. As a result, the new dtags are not actually enabled, and
binaries are built with RPATH set instead of RUNPATH, thereby preventing
LD_LIBRARY_PATH from overriding this built-in path. This change corrects
this. The patch file is no longer necessary because binutils's ldmain.c
now sets link_info.new_dtags based on the configuration flags.
This was probably not noticed immediately because, when the derivation
is built with nix-build, the fixupPhase runs patchelf --shrink-rpath.
patchelf converts any RPATH in the binary into RUNPATH (unless
--force-rpath is specified). Of course, if the binary is built without
nix-build (such as in a nix-shell), this never occurs, and any RPATH in
the binary is left in place.
Since years I'm not maintaining anything of the list below other
than some updates when I needed them for some reason. Other people
is doing that maintenance on my behalf so I better take me out but
for very few packages. Finally!
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/elfutils/versions.
These checks were done:
- built on NixOS
- /nix/store/nmml2vhzia58ji531a4q1j97rrj308yj-elfutils-0.173/bin/eu-readelf passed the binary check.
- /nix/store/nmml2vhzia58ji531a4q1j97rrj308yj-elfutils-0.173/bin/eu-nm passed the binary check.
- /nix/store/nmml2vhzia58ji531a4q1j97rrj308yj-elfutils-0.173/bin/eu-size passed the binary check.
- /nix/store/nmml2vhzia58ji531a4q1j97rrj308yj-elfutils-0.173/bin/eu-strip passed the binary check.
- /nix/store/nmml2vhzia58ji531a4q1j97rrj308yj-elfutils-0.173/bin/eu-elflint passed the binary check.
- /nix/store/nmml2vhzia58ji531a4q1j97rrj308yj-elfutils-0.173/bin/eu-findtextrel passed the binary check.
- /nix/store/nmml2vhzia58ji531a4q1j97rrj308yj-elfutils-0.173/bin/eu-addr2line passed the binary check.
- /nix/store/nmml2vhzia58ji531a4q1j97rrj308yj-elfutils-0.173/bin/eu-elfcmp passed the binary check.
- /nix/store/nmml2vhzia58ji531a4q1j97rrj308yj-elfutils-0.173/bin/eu-objdump passed the binary check.
- /nix/store/nmml2vhzia58ji531a4q1j97rrj308yj-elfutils-0.173/bin/eu-ranlib passed the binary check.
- /nix/store/nmml2vhzia58ji531a4q1j97rrj308yj-elfutils-0.173/bin/eu-strings passed the binary check.
- /nix/store/nmml2vhzia58ji531a4q1j97rrj308yj-elfutils-0.173/bin/eu-ar passed the binary check.
- /nix/store/nmml2vhzia58ji531a4q1j97rrj308yj-elfutils-0.173/bin/eu-unstrip passed the binary check.
- /nix/store/nmml2vhzia58ji531a4q1j97rrj308yj-elfutils-0.173/bin/eu-stack passed the binary check.
- /nix/store/nmml2vhzia58ji531a4q1j97rrj308yj-elfutils-0.173/bin/eu-elfcompress passed the binary check.
- /nix/store/nmml2vhzia58ji531a4q1j97rrj308yj-elfutils-0.173/bin/eu-make-debug-archive passed the binary check.
- 16 of 16 passed binary check by having a zero exit code.
- 0 of 16 passed binary check by having the new version present in output.
- found 0.173 with grep in /nix/store/nmml2vhzia58ji531a4q1j97rrj308yj-elfutils-0.173
- directory tree listing: https://gist.github.com/f0b855207a6f13446e77907717da40dd
- du listing: https://gist.github.com/1275237e95e19d1956769a304945cc37
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/sysbench/versions.
<details><summary>Version release notes (from GitHub)</summary>
* version 1.0.15
* CI/build/packaging: add Fedora 28
* CI/build/packaging: add Ubuntu Bionic
* CI/build/packaging: remove Fedora 26 (EOL)
* CI/build/packaging: remove Debian Wheezy (EOL)
* fileio: fix GH-229 (--file-fsync-freq=0 seems to prevent
fsync() at the end of the test)
* command line: improve parsing of boolean command line options
* tests: fix GH-220 (Testsuite api_sql_mysql.t failed ...)
* tests: fix GH-223 (test failure on ppc64)
* tests: fix opt_help.t to pass when the binary is not
configured with MySQL support
* MySQL driver: use it by default in DB benchmarks
</details>
These checks were done:
- built on NixOS
- /nix/store/jfyhnvp5696s1cjn64fxp5ir072m7h35-sysbench-1.0.15/bin/sysbench passed the binary check.
- 1 of 1 passed binary check by having a zero exit code.
- 1 of 1 passed binary check by having the new version present in output.
- found 1.0.15 with grep in /nix/store/jfyhnvp5696s1cjn64fxp5ir072m7h35-sysbench-1.0.15
- directory tree listing: https://gist.github.com/2d15615806f49f153b03e6495af3654b
- du listing: https://gist.github.com/6d323aaf15bf22506caed9176fe9b034
* 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
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/doclifter/versions.
These checks were done:
- built on NixOS
- Warning: no invocation of /nix/store/qzimyzp6c58i4jmqkmijzicyxzbn3j0x-doclifter-2.18/bin/manlifter had a zero exit code or showed the expected version
- /nix/store/qzimyzp6c58i4jmqkmijzicyxzbn3j0x-doclifter-2.18/bin/doclifter passed the binary check.
- 1 of 2 passed binary check by having a zero exit code.
- 1 of 2 passed binary check by having the new version present in output.
- found 2.18 with grep in /nix/store/qzimyzp6c58i4jmqkmijzicyxzbn3j0x-doclifter-2.18
- directory tree listing: https://gist.github.com/5f26018de7c8c2bbf86953b19997143a
- du listing: https://gist.github.com/b556716e68094c4f1457bbbbe6467d55
In particular, this contains Firefox-related and libgcrypt updates.
Other larger rebuilds would apparently need lots of time to catch up
on Hydra, due to nontrivial rebuilds in other branches than staging.
This fails for me:
> compressed_output.cc:320:20: error: format string is not a string literal (potentially insecure) [-Werror,-Wformat-security]
> gold_warning(_("not compressing section data: zlib error"));
> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> ./system.h:40:20: note: expanded from macro '_'
> # define _(String) gettext (String)
> ^~~~~~~~~~~~~~~~
> compressed_output.cc:320:20: note: treat the string as an argument to avoid this
> gold_warning(_("not compressing section data: zlib error"));
> ^
> "%s",
> ./system.h:40:20: note: expanded from macro '_'
> # define _(String) gettext (String)
^
Disabling format hardening should hopefully be harmless here. If it's a problem we can also make it conditional.
/cc @Ericson2314
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/elfutils/versions.
These checks were done:
- built on NixOS
- /nix/store/742pb58l3dabnraf988m4xvmccqyf85w-elfutils-0.171/bin/eu-readelf passed the binary check.
- /nix/store/742pb58l3dabnraf988m4xvmccqyf85w-elfutils-0.171/bin/eu-nm passed the binary check.
- /nix/store/742pb58l3dabnraf988m4xvmccqyf85w-elfutils-0.171/bin/eu-size passed the binary check.
- /nix/store/742pb58l3dabnraf988m4xvmccqyf85w-elfutils-0.171/bin/eu-strip passed the binary check.
- /nix/store/742pb58l3dabnraf988m4xvmccqyf85w-elfutils-0.171/bin/eu-elflint passed the binary check.
- /nix/store/742pb58l3dabnraf988m4xvmccqyf85w-elfutils-0.171/bin/eu-findtextrel passed the binary check.
- /nix/store/742pb58l3dabnraf988m4xvmccqyf85w-elfutils-0.171/bin/eu-addr2line passed the binary check.
- /nix/store/742pb58l3dabnraf988m4xvmccqyf85w-elfutils-0.171/bin/eu-elfcmp passed the binary check.
- /nix/store/742pb58l3dabnraf988m4xvmccqyf85w-elfutils-0.171/bin/eu-objdump passed the binary check.
- /nix/store/742pb58l3dabnraf988m4xvmccqyf85w-elfutils-0.171/bin/eu-ranlib passed the binary check.
- /nix/store/742pb58l3dabnraf988m4xvmccqyf85w-elfutils-0.171/bin/eu-strings passed the binary check.
- /nix/store/742pb58l3dabnraf988m4xvmccqyf85w-elfutils-0.171/bin/eu-ar passed the binary check.
- /nix/store/742pb58l3dabnraf988m4xvmccqyf85w-elfutils-0.171/bin/eu-unstrip passed the binary check.
- /nix/store/742pb58l3dabnraf988m4xvmccqyf85w-elfutils-0.171/bin/eu-stack passed the binary check.
- /nix/store/742pb58l3dabnraf988m4xvmccqyf85w-elfutils-0.171/bin/eu-elfcompress passed the binary check.
- /nix/store/742pb58l3dabnraf988m4xvmccqyf85w-elfutils-0.171/bin/eu-make-debug-archive passed the binary check.
- 16 of 16 passed binary check by having a zero exit code.
- 0 of 16 passed binary check by having the new version present in output.
- found 0.171 with grep in /nix/store/742pb58l3dabnraf988m4xvmccqyf85w-elfutils-0.171
- directory tree listing: https://gist.github.com/a9aa0114a736db7e1428e99f018ccd37
- du listing: https://gist.github.com/4fed4bdee872b7435662455c93469b5d
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/lttng-tools/versions.
These checks were done:
- built on NixOS
- /nix/store/dkn45wpwlqz4afidp3f2z9gf4a2k331a-lttng-tools-2.10.4/bin/lttng passed the binary check.
- /nix/store/dkn45wpwlqz4afidp3f2z9gf4a2k331a-lttng-tools-2.10.4/bin/lttng-crash passed the binary check.
- /nix/store/dkn45wpwlqz4afidp3f2z9gf4a2k331a-lttng-tools-2.10.4/bin/lttng-relayd passed the binary check.
- /nix/store/dkn45wpwlqz4afidp3f2z9gf4a2k331a-lttng-tools-2.10.4/bin/lttng-sessiond passed the binary check.
- 4 of 4 passed binary check by having a zero exit code.
- 2 of 4 passed binary check by having the new version present in output.
- found 2.10.4 with grep in /nix/store/dkn45wpwlqz4afidp3f2z9gf4a2k331a-lttng-tools-2.10.4
- directory tree listing: https://gist.github.com/e4d67a251f6e4d55bef4903a618d4c77
- du listing: https://gist.github.com/5a95c60b995446339306ed79d3eee027
And there's more reverts too. The previous commmit
d838afbc9376bdadb8c690eb00b425f3eeccdf2d to gnu-config finally solves
it!
This reverts commit 3ed545ab31.
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/fswatch/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/c05hlqp57zslb3imjx6m5dary3ak601d-fswatch-1.11.3/bin/fswatch -h’ got 0 exit code
- ran ‘/nix/store/c05hlqp57zslb3imjx6m5dary3ak601d-fswatch-1.11.3/bin/fswatch --help’ got 0 exit code
- found 1.11.3 with grep in /nix/store/c05hlqp57zslb3imjx6m5dary3ak601d-fswatch-1.11.3
- directory tree listing: https://gist.github.com/cc22e26348bfd98159c6519a470d3bdb
For details on the patches applied, see:
https://sources.debian.org/patches/ltrace/0.7.3-6/
Disabling '-Werror' may be a problem in the future again,
but for now keep things simple now that they're fixed.
Following legacy packing conventions, `isArm` was defined just for
32-bit ARM instruction set. This is confusing to non packagers though,
because Aarch64 is an ARM instruction set.
The official ARM overview for ARMv8[1] is surprisingly not confusing,
given the overall state of affairs for ARM naming conventions, and
offers us a solution. It divides the nomenclature into three levels:
```
ISA: ARMv8 {-A, -R, -M}
/ \
Mode: Aarch32 Aarch64
| / \
Encoding: A64 A32 T32
```
At the top is the overall v8 instruction set archicture. Second are the
two modes, defined by bitwidth but differing in other semantics too, and
buttom are the encodings, (hopefully?) isomorphic if they encode the
same mode.
The 32 bit encodings are mostly backwards compatible with previous
non-Thumb and Thumb encodings, and if so we can pun the mode names to
instead mean "sets of compatable or isomorphic encodings", and then
voilà we have nice names for 32-bit and 64-bit arm instruction sets
which do not use the word ARM so as to not confused either laymen or
experienced ARM packages.
[1]: https://developer.arm.com/products/architecture/a-profile
(cherry picked from commit ba52ae5048)
Following legacy packing conventions, `isArm` was defined just for
32-bit ARM instruction set. This is confusing to non packagers though,
because Aarch64 is an ARM instruction set.
The official ARM overview for ARMv8[1] is surprisingly not confusing,
given the overall state of affairs for ARM naming conventions, and
offers us a solution. It divides the nomenclature into three levels:
```
ISA: ARMv8 {-A, -R, -M}
/ \
Mode: Aarch32 Aarch64
| / \
Encoding: A64 A32 T32
```
At the top is the overall v8 instruction set archicture. Second are the
two modes, defined by bitwidth but differing in other semantics too, and
buttom are the encodings, (hopefully?) isomorphic if they encode the
same mode.
The 32 bit encodings are mostly backwards compatible with previous
non-Thumb and Thumb encodings, and if so we can pun the mode names to
instead mean "sets of compatable or isomorphic encodings", and then
voilà we have nice names for 32-bit and 64-bit arm instruction sets
which do not use the word ARM so as to not confused either laymen or
experienced ARM packages.
[1]: https://developer.arm.com/products/architecture/a-profile
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/strace/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/x7d4g7rvf9z43xjz7mc8c4nzwphghjj7-strace-4.22/bin/strace -h’ got 0 exit code
- ran ‘/nix/store/x7d4g7rvf9z43xjz7mc8c4nzwphghjj7-strace-4.22/bin/strace-log-merge -h’ got 0 exit code
- ran ‘/nix/store/x7d4g7rvf9z43xjz7mc8c4nzwphghjj7-strace-4.22/bin/strace-log-merge --help’ got 0 exit code
- ran ‘/nix/store/x7d4g7rvf9z43xjz7mc8c4nzwphghjj7-strace-4.22/bin/strace-log-merge help’ got 0 exit code
- found 4.22 with grep in /nix/store/x7d4g7rvf9z43xjz7mc8c4nzwphghjj7-strace-4.22
- directory tree listing: https://gist.github.com/4c8ab8738133d11c611ae7290d25d6fc
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/sysbench/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/d3633p13b97v5r5xswf85v9fxql1jv72-sysbench-1.0.14/bin/sysbench --help’ got 0 exit code
- ran ‘/nix/store/d3633p13b97v5r5xswf85v9fxql1jv72-sysbench-1.0.14/bin/sysbench --version’ and found version 1.0.14
- found 1.0.14 with grep in /nix/store/d3633p13b97v5r5xswf85v9fxql1jv72-sysbench-1.0.14
- directory tree listing: https://gist.github.com/56c18be2af370efb1c887dd27074fd4e
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/lttng-tools/versions.
These checks were done:
- built on NixOS
- ran `/nix/store/jfs54222qa6kkqs2vnf54p48ar94h6r1-lttng-tools-2.10.3/bin/lttng -V` and found version 2.10.3
- ran `/nix/store/jfs54222qa6kkqs2vnf54p48ar94h6r1-lttng-tools-2.10.3/bin/lttng --version` and found version 2.10.3
- ran `/nix/store/jfs54222qa6kkqs2vnf54p48ar94h6r1-lttng-tools-2.10.3/bin/lttng version` and found version 2.10.3
- ran `/nix/store/jfs54222qa6kkqs2vnf54p48ar94h6r1-lttng-tools-2.10.3/bin/lttng-crash -V` and found version 2.10.3
- ran `/nix/store/jfs54222qa6kkqs2vnf54p48ar94h6r1-lttng-tools-2.10.3/bin/lttng-crash --version` and found version 2.10.3
- found 2.10.3 with grep in /nix/store/jfs54222qa6kkqs2vnf54p48ar94h6r1-lttng-tools-2.10.3
- directory tree listing: https://gist.github.com/bf4b92fc08881141af11b0444ed15630
Semi-automatic update generated by https://github.com/ryantm/nix-update tools.
This update was made based on information from https://repology.org/metapackage/babeltrace/versions.
These checks were done:
- built on NixOS
- ran `/nix/store/yhd43sy0rj5fr0gwh298l959b7bmcsh8-babeltrace-1.5.5/bin/babeltrace -h` got 0 exit code
- ran `/nix/store/yhd43sy0rj5fr0gwh298l959b7bmcsh8-babeltrace-1.5.5/bin/babeltrace --help` got 0 exit code
- ran `/nix/store/yhd43sy0rj5fr0gwh298l959b7bmcsh8-babeltrace-1.5.5/bin/babeltrace -h` and found version 1.5.5
- ran `/nix/store/yhd43sy0rj5fr0gwh298l959b7bmcsh8-babeltrace-1.5.5/bin/babeltrace --help` and found version 1.5.5
- ran `/nix/store/yhd43sy0rj5fr0gwh298l959b7bmcsh8-babeltrace-1.5.5/bin/babeltrace-log -h` got 0 exit code
- ran `/nix/store/yhd43sy0rj5fr0gwh298l959b7bmcsh8-babeltrace-1.5.5/bin/babeltrace-log -h` and found version 1.5.5
- found 1.5.5 with grep in /nix/store/yhd43sy0rj5fr0gwh298l959b7bmcsh8-babeltrace-1.5.5
- directory tree listing: https://gist.github.com/d849a2026946a7542bc3e2e6a586d713
Uses the HTTPS url for cases where the existing URL has a permanent
redirect. For each domain, at least one fixed derivation URL was
downloaded to test the domain is properly serving downloads.
Also fixes jbake source URL, which was broken.
Semi-automatic update generated by https://github.com/ryantm/nix-update tools. These checks were done:
- built on NixOS
- ran `/nix/store/az3lanws83s5q26z1s03rx6z6yxphjbq-luarocks-2.4.4/bin/luarocks --help` got 0 exit code
- ran `/nix/store/az3lanws83s5q26z1s03rx6z6yxphjbq-luarocks-2.4.4/bin/luarocks help` got 0 exit code
- ran `/nix/store/az3lanws83s5q26z1s03rx6z6yxphjbq-luarocks-2.4.4/bin/luarocks --version` and found version 2.4.4
- ran `/nix/store/az3lanws83s5q26z1s03rx6z6yxphjbq-luarocks-2.4.4/bin/luarocks --help` and found version 2.4.4
- ran `/nix/store/az3lanws83s5q26z1s03rx6z6yxphjbq-luarocks-2.4.4/bin/luarocks help` and found version 2.4.4
- ran `/nix/store/az3lanws83s5q26z1s03rx6z6yxphjbq-luarocks-2.4.4/bin/luarocks-5.1 --help` got 0 exit code
- ran `/nix/store/az3lanws83s5q26z1s03rx6z6yxphjbq-luarocks-2.4.4/bin/luarocks-5.1 help` got 0 exit code
- ran `/nix/store/az3lanws83s5q26z1s03rx6z6yxphjbq-luarocks-2.4.4/bin/luarocks-5.1 --version` and found version 2.4.4
- ran `/nix/store/az3lanws83s5q26z1s03rx6z6yxphjbq-luarocks-2.4.4/bin/luarocks-5.1 --help` and found version 2.4.4
- ran `/nix/store/az3lanws83s5q26z1s03rx6z6yxphjbq-luarocks-2.4.4/bin/luarocks-5.1 help` and found version 2.4.4
- ran `/nix/store/az3lanws83s5q26z1s03rx6z6yxphjbq-luarocks-2.4.4/bin/luarocks-admin --help` got 0 exit code
- ran `/nix/store/az3lanws83s5q26z1s03rx6z6yxphjbq-luarocks-2.4.4/bin/luarocks-admin help` got 0 exit code
- ran `/nix/store/az3lanws83s5q26z1s03rx6z6yxphjbq-luarocks-2.4.4/bin/luarocks-admin --version` and found version 2.4.4
- ran `/nix/store/az3lanws83s5q26z1s03rx6z6yxphjbq-luarocks-2.4.4/bin/luarocks-admin --help` and found version 2.4.4
- ran `/nix/store/az3lanws83s5q26z1s03rx6z6yxphjbq-luarocks-2.4.4/bin/luarocks-admin help` and found version 2.4.4
- ran `/nix/store/az3lanws83s5q26z1s03rx6z6yxphjbq-luarocks-2.4.4/bin/luarocks-admin-5.1 --help` got 0 exit code
- ran `/nix/store/az3lanws83s5q26z1s03rx6z6yxphjbq-luarocks-2.4.4/bin/luarocks-admin-5.1 help` got 0 exit code
- ran `/nix/store/az3lanws83s5q26z1s03rx6z6yxphjbq-luarocks-2.4.4/bin/luarocks-admin-5.1 --version` and found version 2.4.4
- ran `/nix/store/az3lanws83s5q26z1s03rx6z6yxphjbq-luarocks-2.4.4/bin/luarocks-admin-5.1 --help` and found version 2.4.4
- ran `/nix/store/az3lanws83s5q26z1s03rx6z6yxphjbq-luarocks-2.4.4/bin/luarocks-admin-5.1 help` and found version 2.4.4
- found 2.4.4 with grep in /nix/store/az3lanws83s5q26z1s03rx6z6yxphjbq-luarocks-2.4.4
- directory tree listing: https://gist.github.com/cb3889fda28e8066faebd32a433c69d2
Semi-automatic update generated by https://github.com/ryantm/nix-update tools. These checks were done:
- built on NixOS
- Warning: no binary found that responded to help or version flags. (This warning appears even if the package isn't expected to have binaries.)
- found 2018.03.13 with grep in /nix/store/gpwn8923mppc2h6vx2rgg8q52ss2mg2l-autoconf-archive-2018.03.13
- directory tree listing: https://gist.github.com/eaaa4f78b6bd461710c33aea9e21fdea
- The patch has been applied upstream.
- LSOF_INCLUDE was referring to wrong output, this broke the build.
- Remove an unneeded legacy sed.
- Maintain, while at it.
Semi-automatic update generated by https://github.com/ryantm/nix-update tools. These checks were done:
- built on NixOS
- ran `/nix/store/pg0jpmczm1gb3rzp3qfnnjl0xfd48nqz-itstool-2.0.4/bin/itstool -h` got 0 exit code
- ran `/nix/store/pg0jpmczm1gb3rzp3qfnnjl0xfd48nqz-itstool-2.0.4/bin/itstool --help` got 0 exit code
- ran `/nix/store/pg0jpmczm1gb3rzp3qfnnjl0xfd48nqz-itstool-2.0.4/bin/itstool -v` and found version 2.0.4
- ran `/nix/store/pg0jpmczm1gb3rzp3qfnnjl0xfd48nqz-itstool-2.0.4/bin/itstool --version` and found version 2.0.4
- found 2.0.4 with grep in /nix/store/pg0jpmczm1gb3rzp3qfnnjl0xfd48nqz-itstool-2.0.4
- found 2.0.4 in filename of file in /nix/store/pg0jpmczm1gb3rzp3qfnnjl0xfd48nqz-itstool-2.0.4
Semi-automatic update generated by https://github.com/ryantm/nix-update tools. These checks were done:
- built on NixOS
- ran `/nix/store/xk5lsqw4vfa5ndqvsg23w6jblxx0js78-intel-gpu-tools-1.22/bin/igt_stats -h` got 0 exit code
- ran `/nix/store/xk5lsqw4vfa5ndqvsg23w6jblxx0js78-intel-gpu-tools-1.22/bin/igt_stats --help` got 0 exit code
- ran `/nix/store/xk5lsqw4vfa5ndqvsg23w6jblxx0js78-intel-gpu-tools-1.22/bin/igt_stats help` got 0 exit code
- ran `/nix/store/xk5lsqw4vfa5ndqvsg23w6jblxx0js78-intel-gpu-tools-1.22/bin/intel_reg --help` got 0 exit code
- ran `/nix/store/xk5lsqw4vfa5ndqvsg23w6jblxx0js78-intel-gpu-tools-1.22/bin/intel_reg help` got 0 exit code
- ran `/nix/store/xk5lsqw4vfa5ndqvsg23w6jblxx0js78-intel-gpu-tools-1.22/bin/intel_forcewaked -h` got 0 exit code
- ran `/nix/store/xk5lsqw4vfa5ndqvsg23w6jblxx0js78-intel-gpu-tools-1.22/bin/intel_firmware_decode help` got 0 exit code
- ran `/nix/store/xk5lsqw4vfa5ndqvsg23w6jblxx0js78-intel-gpu-tools-1.22/bin/intel_gpu_top -h` got 0 exit code
- ran `/nix/store/xk5lsqw4vfa5ndqvsg23w6jblxx0js78-intel-gpu-tools-1.22/bin/intel_gpu_top -h` and found version 1.22
- ran `/nix/store/xk5lsqw4vfa5ndqvsg23w6jblxx0js78-intel-gpu-tools-1.22/bin/intel_guc_logger -h` got 0 exit code
- ran `/nix/store/xk5lsqw4vfa5ndqvsg23w6jblxx0js78-intel-gpu-tools-1.22/bin/intel_guc_logger --help` got 0 exit code
- ran `/nix/store/xk5lsqw4vfa5ndqvsg23w6jblxx0js78-intel-gpu-tools-1.22/bin/intel_opregion_decode -h` got 0 exit code
- ran `/nix/store/xk5lsqw4vfa5ndqvsg23w6jblxx0js78-intel-gpu-tools-1.22/bin/intel_opregion_decode --help` got 0 exit code
- ran `/nix/store/xk5lsqw4vfa5ndqvsg23w6jblxx0js78-intel-gpu-tools-1.22/bin/intel_dump_decode help` got 0 exit code
- ran `/nix/store/xk5lsqw4vfa5ndqvsg23w6jblxx0js78-intel-gpu-tools-1.22/bin/intel_error_decode help` got 0 exit code
- ran `/nix/store/xk5lsqw4vfa5ndqvsg23w6jblxx0js78-intel-gpu-tools-1.22/bin/intel_dp_compliance -h` got 0 exit code
- ran `/nix/store/xk5lsqw4vfa5ndqvsg23w6jblxx0js78-intel-gpu-tools-1.22/bin/intel_dp_compliance --help` got 0 exit code
- ran `/nix/store/xk5lsqw4vfa5ndqvsg23w6jblxx0js78-intel-gpu-tools-1.22/bin/intel_dp_compliance -h` and found version 1.22
- ran `/nix/store/xk5lsqw4vfa5ndqvsg23w6jblxx0js78-intel-gpu-tools-1.22/bin/intel_dp_compliance --help` and found version 1.22
- ran `/nix/store/xk5lsqw4vfa5ndqvsg23w6jblxx0js78-intel-gpu-tools-1.22/bin/intel_aubdump -h` got 0 exit code
- ran `/nix/store/xk5lsqw4vfa5ndqvsg23w6jblxx0js78-intel-gpu-tools-1.22/bin/intel_aubdump --help` got 0 exit code
- found 1.22 with grep in /nix/store/xk5lsqw4vfa5ndqvsg23w6jblxx0js78-intel-gpu-tools-1.22
- found 1.22 in filename of file in /nix/store/xk5lsqw4vfa5ndqvsg23w6jblxx0js78-intel-gpu-tools-1.22
Resolved the following conflicts (by carefully applying patches from the both
branches since the fork point):
pkgs/development/libraries/epoxy/default.nix
pkgs/development/libraries/gtk+/3.x.nix
pkgs/development/python-modules/asgiref/default.nix
pkgs/development/python-modules/daphne/default.nix
pkgs/os-specific/linux/systemd/default.nix
Semi-automatic update. These checks were done:
- built on NixOS
- Warning: no binary found that responded to help or version flags. (This warning appears even if the package isn't expected to have binaries.)
- found 1.0 with grep in /nix/store/x8i9mf6wvwj3n7il5kixfyrn0gdshnsb-opengrok-1.0
- found 1.0 in filename of file in /nix/store/x8i9mf6wvwj3n7il5kixfyrn0gdshnsb-opengrok-1.0
Semi-automatic update. These checks were done:
- built on NixOS
- ran `/nix/store/2flw25y597pyjl1hlnkpxm86crmps6cw-global-6.6.2/bin/gtags --help` got 0 exit code
- ran `/nix/store/2flw25y597pyjl1hlnkpxm86crmps6cw-global-6.6.2/bin/gtags --version` and found version 6.6.2
- ran `/nix/store/2flw25y597pyjl1hlnkpxm86crmps6cw-global-6.6.2/bin/global --help` got 0 exit code
- ran `/nix/store/2flw25y597pyjl1hlnkpxm86crmps6cw-global-6.6.2/bin/global help` got 0 exit code
- ran `/nix/store/2flw25y597pyjl1hlnkpxm86crmps6cw-global-6.6.2/bin/global --version` and found version 6.6.2
- ran `/nix/store/2flw25y597pyjl1hlnkpxm86crmps6cw-global-6.6.2/bin/gozilla --help` got 0 exit code
- ran `/nix/store/2flw25y597pyjl1hlnkpxm86crmps6cw-global-6.6.2/bin/gozilla --version` and found version 6.6.2
- ran `/nix/store/2flw25y597pyjl1hlnkpxm86crmps6cw-global-6.6.2/bin/htags -h` got 0 exit code
- ran `/nix/store/2flw25y597pyjl1hlnkpxm86crmps6cw-global-6.6.2/bin/htags --help` got 0 exit code
- ran `/nix/store/2flw25y597pyjl1hlnkpxm86crmps6cw-global-6.6.2/bin/htags help` got 0 exit code
- ran `/nix/store/2flw25y597pyjl1hlnkpxm86crmps6cw-global-6.6.2/bin/htags --version` and found version 6.6.2
- ran `/nix/store/2flw25y597pyjl1hlnkpxm86crmps6cw-global-6.6.2/bin/gtags-cscope -h` got 0 exit code
- ran `/nix/store/2flw25y597pyjl1hlnkpxm86crmps6cw-global-6.6.2/bin/gtags-cscope --help` got 0 exit code
- ran `/nix/store/2flw25y597pyjl1hlnkpxm86crmps6cw-global-6.6.2/bin/gtags-cscope -V` and found version 6.6.2
- ran `/nix/store/2flw25y597pyjl1hlnkpxm86crmps6cw-global-6.6.2/bin/gtags-cscope --version` and found version 6.6.2
- ran `/nix/store/2flw25y597pyjl1hlnkpxm86crmps6cw-global-6.6.2/bin/.gtags-wrapped --help` got 0 exit code
- ran `/nix/store/2flw25y597pyjl1hlnkpxm86crmps6cw-global-6.6.2/bin/.gtags-wrapped help` got 0 exit code
- ran `/nix/store/2flw25y597pyjl1hlnkpxm86crmps6cw-global-6.6.2/bin/.gtags-wrapped --version` and found version 6.6.2
- ran `/nix/store/2flw25y597pyjl1hlnkpxm86crmps6cw-global-6.6.2/bin/.global-wrapped --help` got 0 exit code
- ran `/nix/store/2flw25y597pyjl1hlnkpxm86crmps6cw-global-6.6.2/bin/.global-wrapped help` got 0 exit code
- ran `/nix/store/2flw25y597pyjl1hlnkpxm86crmps6cw-global-6.6.2/bin/.global-wrapped --version` and found version 6.6.2
- found 6.6.2 with grep in /nix/store/2flw25y597pyjl1hlnkpxm86crmps6cw-global-6.6.2
- found 6.6.2 in filename of file in /nix/store/2flw25y597pyjl1hlnkpxm86crmps6cw-global-6.6.2
Outside of the nix-build the target is `x86_64-apple-darwin17.4.0`,
while inside the target is `x86_64-apple-darwin`. This difference
causes the fallback target configuration for darwin, which disables
gdb. Add a patch to make the target matching more flexible.
Semi-automatic update. These checks were performed:
- built on NixOS
- ran `/nix/store/g7j0xbs2izhmr4jy7zj4q7b2nqgs5wn2-sysbench-1.0.13/bin/sysbench --help` got 0 exit code
- ran `/nix/store/g7j0xbs2izhmr4jy7zj4q7b2nqgs5wn2-sysbench-1.0.13/bin/sysbench --version` and found version 1.0.13
- found 1.0.13 with grep in /nix/store/g7j0xbs2izhmr4jy7zj4q7b2nqgs5wn2-sysbench-1.0.13
- found 1.0.13 in filename of file in /nix/store/g7j0xbs2izhmr4jy7zj4q7b2nqgs5wn2-sysbench-1.0.13
Semi-automatic update. These checks were performed:
- built on NixOS
- ran `/nix/store/g9jg6pc3vwnpfgbypnzv2v5gp4r7gnnn-usb-modeswitch-2.5.2/bin/usb_modeswitch -h` got 0 exit code
- ran `/nix/store/g9jg6pc3vwnpfgbypnzv2v5gp4r7gnnn-usb-modeswitch-2.5.2/bin/usb_modeswitch --help` got 0 exit code
- ran `/nix/store/g9jg6pc3vwnpfgbypnzv2v5gp4r7gnnn-usb-modeswitch-2.5.2/bin/usb_modeswitch --version` and found version 2.5.2
- ran `/nix/store/g9jg6pc3vwnpfgbypnzv2v5gp4r7gnnn-usb-modeswitch-2.5.2/bin/usb_modeswitch -h` and found version 2.5.2
- ran `/nix/store/g9jg6pc3vwnpfgbypnzv2v5gp4r7gnnn-usb-modeswitch-2.5.2/bin/usb_modeswitch --help` and found version 2.5.2
- found 2.5.2 with grep in /nix/store/g9jg6pc3vwnpfgbypnzv2v5gp4r7gnnn-usb-modeswitch-2.5.2
- found 2.5.2 in filename of file in /nix/store/g9jg6pc3vwnpfgbypnzv2v5gp4r7gnnn-usb-modeswitch-2.5.2
cc "@marcweber @peterhoeg"
Semi-automatic update. These checks were performed:
- built on NixOS
- ran `/nix/store/bg2nls3ahz6jd32nxdaax1akz2hjh8ma-uncrustify-0.66.1/bin/uncrustify -h` got 0 exit code
- ran `/nix/store/bg2nls3ahz6jd32nxdaax1akz2hjh8ma-uncrustify-0.66.1/bin/uncrustify --help` got 0 exit code
- ran `/nix/store/bg2nls3ahz6jd32nxdaax1akz2hjh8ma-uncrustify-0.66.1/bin/uncrustify -v` and found version 0.66.1
- ran `/nix/store/bg2nls3ahz6jd32nxdaax1akz2hjh8ma-uncrustify-0.66.1/bin/uncrustify --version` and found version 0.66.1
- found 0.66.1 with grep in /nix/store/bg2nls3ahz6jd32nxdaax1akz2hjh8ma-uncrustify-0.66.1
- found 0.66.1 in filename of file in /nix/store/bg2nls3ahz6jd32nxdaax1akz2hjh8ma-uncrustify-0.66.1
cc "@bjornfor"
Semi-automatic update. These checks were performed:
- built on NixOS
- ran `/nix/store/xmsjbixyip29vcxgh0wkhlvvb9zpbhz2-msitools-0.97/bin/msiinfo -h` got 0 exit code
- ran `/nix/store/xmsjbixyip29vcxgh0wkhlvvb9zpbhz2-msitools-0.97/bin/msiinfo --help` got 0 exit code
- ran `/nix/store/xmsjbixyip29vcxgh0wkhlvvb9zpbhz2-msitools-0.97/bin/msiinfo help` got 0 exit code
- ran `/nix/store/xmsjbixyip29vcxgh0wkhlvvb9zpbhz2-msitools-0.97/bin/msiinfo -v` and found version 0.97
- ran `/nix/store/xmsjbixyip29vcxgh0wkhlvvb9zpbhz2-msitools-0.97/bin/msiinfo --version` and found version 0.97
- ran `/nix/store/xmsjbixyip29vcxgh0wkhlvvb9zpbhz2-msitools-0.97/bin/msiextract -h` got 0 exit code
- ran `/nix/store/xmsjbixyip29vcxgh0wkhlvvb9zpbhz2-msitools-0.97/bin/msiextract --help` got 0 exit code
- ran `/nix/store/xmsjbixyip29vcxgh0wkhlvvb9zpbhz2-msitools-0.97/bin/msiextract help` got 0 exit code
- ran `/nix/store/xmsjbixyip29vcxgh0wkhlvvb9zpbhz2-msitools-0.97/bin/msiextract --version` and found version 0.97
- ran `/nix/store/xmsjbixyip29vcxgh0wkhlvvb9zpbhz2-msitools-0.97/bin/wixl -h` got 0 exit code
- ran `/nix/store/xmsjbixyip29vcxgh0wkhlvvb9zpbhz2-msitools-0.97/bin/wixl --help` got 0 exit code
- ran `/nix/store/xmsjbixyip29vcxgh0wkhlvvb9zpbhz2-msitools-0.97/bin/wixl --version` and found version 0.97
- ran `/nix/store/xmsjbixyip29vcxgh0wkhlvvb9zpbhz2-msitools-0.97/bin/wixl-heat -h` got 0 exit code
- ran `/nix/store/xmsjbixyip29vcxgh0wkhlvvb9zpbhz2-msitools-0.97/bin/wixl-heat --help` got 0 exit code
- ran `/nix/store/xmsjbixyip29vcxgh0wkhlvvb9zpbhz2-msitools-0.97/bin/msidump -h` got 0 exit code
- ran `/nix/store/xmsjbixyip29vcxgh0wkhlvvb9zpbhz2-msitools-0.97/bin/msidump --help` got 0 exit code
- ran `/nix/store/xmsjbixyip29vcxgh0wkhlvvb9zpbhz2-msitools-0.97/bin/msidump -v` and found version 0.97
- ran `/nix/store/xmsjbixyip29vcxgh0wkhlvvb9zpbhz2-msitools-0.97/bin/msidump --version` and found version 0.97
- ran `/nix/store/xmsjbixyip29vcxgh0wkhlvvb9zpbhz2-msitools-0.97/bin/msidiff -h` got 0 exit code
- ran `/nix/store/xmsjbixyip29vcxgh0wkhlvvb9zpbhz2-msitools-0.97/bin/msidiff --help` got 0 exit code
- ran `/nix/store/xmsjbixyip29vcxgh0wkhlvvb9zpbhz2-msitools-0.97/bin/msidiff -v` and found version 0.97
- ran `/nix/store/xmsjbixyip29vcxgh0wkhlvvb9zpbhz2-msitools-0.97/bin/msidiff --version` and found version 0.97
- found 0.97 with grep in /nix/store/xmsjbixyip29vcxgh0wkhlvvb9zpbhz2-msitools-0.97
- found 0.97 in filename of file in /nix/store/xmsjbixyip29vcxgh0wkhlvvb9zpbhz2-msitools-0.97
cc "@vcunat"
Semi-automatic update. These checks were performed:
- built on NixOS
- ran `/nix/store/lf189bg3wyp8bbiw6kqwlvhm3yc4wdgq-lttng-ust-2.10.1/bin/lttng-gen-tp -h` got 0 exit code
- ran `/nix/store/lf189bg3wyp8bbiw6kqwlvhm3yc4wdgq-lttng-ust-2.10.1/bin/lttng-gen-tp --help` got 0 exit code
- ran `/nix/store/lf189bg3wyp8bbiw6kqwlvhm3yc4wdgq-lttng-ust-2.10.1/bin/lttng-gen-tp help` got 0 exit code
- found 2.10.1 with grep in /nix/store/lf189bg3wyp8bbiw6kqwlvhm3yc4wdgq-lttng-ust-2.10.1
- found 2.10.1 in filename of file in /nix/store/lf189bg3wyp8bbiw6kqwlvhm3yc4wdgq-lttng-ust-2.10.1
cc "@bjornfor"
Semi-automatic update. These checks were performed:
- built on NixOS
- ran `/nix/store/mxkd9dxy95rw5xg54h55nm0rdk5makvm-lttng-tools-2.10.2/bin/lttng -V` and found version 2.10.2
- ran `/nix/store/mxkd9dxy95rw5xg54h55nm0rdk5makvm-lttng-tools-2.10.2/bin/lttng --version` and found version 2.10.2
- ran `/nix/store/mxkd9dxy95rw5xg54h55nm0rdk5makvm-lttng-tools-2.10.2/bin/lttng version` and found version 2.10.2
- ran `/nix/store/mxkd9dxy95rw5xg54h55nm0rdk5makvm-lttng-tools-2.10.2/bin/lttng-crash -V` and found version 2.10.2
- ran `/nix/store/mxkd9dxy95rw5xg54h55nm0rdk5makvm-lttng-tools-2.10.2/bin/lttng-crash --version` and found version 2.10.2
- ran `/nix/store/mxkd9dxy95rw5xg54h55nm0rdk5makvm-lttng-tools-2.10.2/bin/lttng-relayd -V` and found version 2.10.2
- ran `/nix/store/mxkd9dxy95rw5xg54h55nm0rdk5makvm-lttng-tools-2.10.2/bin/lttng-relayd --version` and found version 2.10.2
- ran `/nix/store/mxkd9dxy95rw5xg54h55nm0rdk5makvm-lttng-tools-2.10.2/bin/lttng-sessiond -V` and found version 2.10.2
- ran `/nix/store/mxkd9dxy95rw5xg54h55nm0rdk5makvm-lttng-tools-2.10.2/bin/lttng-sessiond --version` and found version 2.10.2
- found 2.10.2 with grep in /nix/store/mxkd9dxy95rw5xg54h55nm0rdk5makvm-lttng-tools-2.10.2
- found 2.10.2 in filename of file in /nix/store/mxkd9dxy95rw5xg54h55nm0rdk5makvm-lttng-tools-2.10.2
cc "@bjornfor"
The previous version was not the actual release, and was not supposed to
be published at all. This one is the signed release. Additionally,
upstream plans no more releases on sourceforge so the URL has been
changed to refer to strace.io instead.
Semi-automatic update. These checks were performed:
- built on NixOS
- ran `/nix/store/l2jl00f6gvvc17lsq27vvmw26md8nf4g-doclifter-2.17/bin/doclifter -V` and found version 2.17
- found 2.17 with grep in /nix/store/l2jl00f6gvvc17lsq27vvmw26md8nf4g-doclifter-2.17
- found 2.17 in filename of file in /nix/store/l2jl00f6gvvc17lsq27vvmw26md8nf4g-doclifter-2.17
Semi-automatic update. The following tests were automatically performed:
- built on NixOS
- ran `/nix/store/kcq8gh0l8v2m71pyz5qqh8hiwnrfkwl6-babeltrace-1.5.4/bin/babeltrace -h` got 0 exit code
- ran `/nix/store/kcq8gh0l8v2m71pyz5qqh8hiwnrfkwl6-babeltrace-1.5.4/bin/babeltrace --help` got 0 exit code
- ran `/nix/store/kcq8gh0l8v2m71pyz5qqh8hiwnrfkwl6-babeltrace-1.5.4/bin/babeltrace -h` and found version 1.5.4
- ran `/nix/store/kcq8gh0l8v2m71pyz5qqh8hiwnrfkwl6-babeltrace-1.5.4/bin/babeltrace --help` and found version 1.5.4
- ran `/nix/store/kcq8gh0l8v2m71pyz5qqh8hiwnrfkwl6-babeltrace-1.5.4/bin/babeltrace-log -h` got 0 exit code
- ran `/nix/store/kcq8gh0l8v2m71pyz5qqh8hiwnrfkwl6-babeltrace-1.5.4/bin/babeltrace-log -h` and found version 1.5.4
- found 1.5.4 with grep in /nix/store/kcq8gh0l8v2m71pyz5qqh8hiwnrfkwl6-babeltrace-1.5.4
Existing "mips64el" should be "mipsel".
This is just the barest minimum so that nixpkgs can recognize them as
systems - although required for building individual derivations onto
MIPS boards, it is not sufficient if you want to actually build nixos on
those targets
https://hydra.nixos.org/build/69542376
[dezgeg: changed to --enable-mpers=check instead of --enable-mpers=no,
which makes it probe at build-time whether a certain personality is
supported and enable it only if the probe succeeded, instead of
unconditionally disabling it. Should be more future-proof.]
This commit breaks native armv7l-linux builds. Revert it until it can
be root-caused. This reversion does not affect other platforms or
cross-compiling.
This reverts commit 0f5c804631.
Now that we do `--enable-targes=all`, there is no risk of missing the
needed emulation.
This reverts commit ebc9b161cd.
This reverts commit 88efc22b44.
They aren't meant to be critical (uncatchable) errors.
Tested with nix-env + checkMeta:
[ "x86_64-linux" "i686-linux" "x86_64-darwin" "aarch64-linux" ]
Certain tools, e.g. compilers, are customarily prefixed with the name of
their target platform so that multiple builds can be used at once
without clobbering each other on the PATH. I was using identifiers named
`prefix` for this purpose, but that conflicts with the standard use of
`prefix` to mean the directory where something is installed. To avoid
conflict and confusion, I renamed those to `targetPrefix`.
Feature rich browser-based frontend with data structure visualizations
(like DDD), and gdb terminal access. Compatible with C, C++, golang,
Rust, fortran. Written in Python and JavaScript
gdbgui is at the top of the GDB Front Ends
list on https://sourceware.org/gdb/wiki/GDB%20Front%20Ends
https://github.com/NixOS/nixpkgs/pull/30484#issuecomment-345472766
Since [1] libbfd is compiled with support for all available targets. However, it
can not choose whether an ARM ELF file is elf32-littlearm,
elf32-littlearm-symbian, or elf32-littlearm-vxworks, and fails with the "File
format is ambiguous" error. Here [2] Alan Modra intended to prioritize the
first of the three, but although his patch was merged and reportedly solved the
issue, currently glibc 2.28.1 and 2.29.1 again fail to disambiguate these
targets. This commit makes it prioritize elf32-littlearm over the other two.
[1] f8741c38cd
[2] https://sourceware.org/ml/binutils/2013-05/msg00271.html
There are separate derivations for these libraries and we don't want
conflict. Multitarget is generally more useful, and will eventually
speed up cross builds, so why not?!
On most distros, these are just built and distributed as part of
binutils. We don't use binutils across the board, however, but rather
switch between binutils and a cctools-binutils mashup, and change the
outputs on binutils too. This creates a combinatorial conditional soup
which is hard to maintain.
My hope is to lower the the state space. While my patch isn't the most
maintainable, they make downstream packages become more maintainable to
compensate. The additional derivations themselves are completely
platform-agnostic, always they always supports all possible target
platforms, and always yield "out" and "dev" outputs. That, in turn,
allows downstream packages to not worry about a dependency
shape-shifting under them.
In fact, the actual binutils package can avoid needing multiple outputs
now that these serve the requisite libraries, so that also can become
simpler on all platforms, too, removing the original wart this PR
circumnavigates for now. Actually changing the binutils package to
leverage is a mass rebuild, however, so I'll leave that for a separate
PR.
I do hope to upstream something like my patch too, but until then I'll
make myself maintainer of these derivations
The biggest benefit is that we no longer have to update the registry
package. This means that just about any cargo package can be built by
nix. No longer does `cargo update` need to be feared because it will
update to packages newer then what is available in nixpkgs.
Instead of fetching the cargo registry this bundles all the source code
into a "vendor/" folder.
This also uses the new --frozen and --locked flags which is nice.
Currently cargo-vendor only provides binaries for Linux and
macOS 64-bit. This can be solved by building it for the other
architectures and uploading it somewhere (like the NixOS cache).
This also has the downside that it requires a change to everyone's deps
hash. And if the old one is used because it was cached it will fail to
build as it will attempt to use the old version. For this reason the
attribute has been renamed to `cargoSha256`.
Authors:
* Kevin Cox <kevincox@kevincox.ca>
* Jörg Thalheim <Mic92@users.noreply.github.com>
* zimbatm <zimbatm@zimbatm.com>
* master: (81 commits)
Add NixOS 17.09 AMIs
gradle: 4.2 -> 4.2.1
maintainers.nix: use my GitHub handle as maintainer name
fcitx-engines.rime: init at 0.3.2
brise: init at 2017-09-16
librime: init at 1.2.9
marisa: init at 0.2.4
opencc: build shared library and programs
josm: 12712 -> 12914
exa: 0.7.0 -> 0.8.0
krb5: add deprecation date for old configuration
rustRegistry: 2017-09-10 -> 2017-10-03
go-ethereum: Fix libusb segmentation faults on Darwin
tor-browser-bundle-bin: 7.0.5 -> 7.0.6
libsodium: 1.0.13 -> 1.0.15
tor-browser-bundle: geoip support
tor-browser-bundle: support transports obfs2,obfs3
tor-browser-bundle: bump https-everywhere to 2017.9.12
tint2: limit platforms to Linux since macOS is not supported and fails the tests
eclipse-plugin-vrapper: init at 0.72.0
...
This reverts commit 0a944b345e, reversing
changes made to 61733ed6cc.
I dislike these massive stdenv changes with unclear motivation,
especially when they involve gratuitous mass renames like NIX_CC ->
NIX_BINUTILS. The previous such rename (NIX_GCC -> NIX_CC) caused
months of pain, so let's not do that again.
This reverts commit bd0d64730a.
Setting GTAGSCONF is not an adequate solution as it prevents the use of
it and the way it was done also breaks gtags when it is called by
global.
FixesNixOS/nixpkgs#26971
* pgadmin: use https homepage
* msn-pecan: move homepage to github
google code is now unavailable
* pidgin-latex: use https for homepage
* pidgin-opensteamworks: use github for homepage
google code is unavailable
* putty: use https for homepage
* ponylang: use https for homepage
* picolisp: use https for homepage
* phonon: use https for homepage
* pugixml: use https for homepage
* pioneer: use https for homepage
* packer: use https for homepage
* pokerth: usee https for homepage
* procps-ng: use https for homepage
* pycaml: use https for homepage
* proot: move homepage to .github.io
* pius: use https for homepage
* pdfread: use https for homepage
* postgresql: use https for homepage
* ponysay: move homepage to new site
* prometheus: use https for homepage
* powerdns: use https for homepage
* pm-utils: use https for homepage
* patchelf: move homepage to https
* tesseract: move homepage to github
* quodlibet: move homepage from google code
* jbrout: move homepage from google code
* eiskaltdcpp: move homepage to github
* nodejs: use https to homepage
* nix: use https for homepage
* pdf2djvu: move homepage from google code
* game-music-emu: move homepage from google code
* vacuum: move homepae from google code
This is needed for build != host == target builds. Moreoever, we want
to move towards always passing all 3, and the previous change to
unbreak Arm moved us away from that.
* pkgs: refactor needless quoting of homepage meta attribute
A lot of packages are needlessly quoting the homepage meta attribute
(about 1400, 22%), this commit refactors all of those instances.
* pkgs: Fixing some links that were wrongfully unquoted in the previous
commit
* Fixed some instances
This setup hook is propagated by gdb. Thus, a typical use is:
$ nix-shell -p gdb nix nix.debug sqlite.debug ...
and gdb will be able find the debug symbols of nix etc. automatically.
The main changes are in libSystem, which lost the coretls component in 10.13
and some hardening changes that quietly crash any program that uses %n in
a non-constant format string, so we've needed to patch a lot of programs that
use gnulib.
* Add kibana5 and logstash5
* Upgrade the elastic beats to 5.4
* Make sure all elastic products use the same version
(see elk5Version)
* Add a test for the ELK stack
- `isGNU` to `isHurd`, my sedding did not catch
- Simplify cross compilation in general
- Be more careful about python
- no more `gdbCross` in all-packages
We want platform triple prefixes and suffixes on derivation names to
be used consistently. The ideom this commit strives for is
- suffix means build != host, i.e. cross *built* packages. This is
already done.
- prefix means build != target, i.e. cross tools. This matches the
tradition of such binaries themselves being prefixed to disambiguate.]
Binutils and cctools, as build tools, now use the latter
- No more *Cross duplication for binutils on darwin either.
`cctools_cross` is merged into plain `cctools`, so `buildPackages`
chains alone are used to disambiguate.
- Always use a mashup of cctools and actual GNU Binutils as `binutils`.
Previously, this was only done in the native case as nobody had
bothered to implement the masher in the cross case. Implemented it
basically consisted of extending the wrapper to deal with prefixed
binaries.
Version 1.17 fails to build with the current libdrm
because of a changed struct (`drm_event_vblank`).
I had to patch `tools/Makefile.am` to use `GLIB_CFLAGS`;
otherwise, the build failed to find `glib.h`.
The old forms presumably predates, or were made in ignorance of,
`let inherit`. This way is better style as the scoping as more lexical,
something which Nix can (or might already!) take advantage of.
Will Dietz
Frederik Rietdijk
Matthew Bauer
Jörg Thalheim
eburimu
Léo Gaspard
Vladimír Čunát
c0bw3b
Linus Heckemann
Jan Tojnar
Orivej Desh
Francesco Zanini
R. RyanTM
Jean-Baptiste Giraudeau
Niklas Thörne
Pascal Wittmann
volth
volth
Markus Kowalewski
Will Dietz
Timo Kaufmann
Jörg Thalheim
Joachim F
xeji
Eelco Dolstra
Spencer Baugh
Peter Hoeg
Benjamin Hipple
Pavol Rusnak
Daiderd Jordan
John Ericson
Patrick Hilhorst
John Ericson
Charles Strahan
Jan Malakhovski
Yorick van Pelt
Elias Probst
R. RyanTM
symphorien
Tim Steinbach
Frederik Rietdijk
Vladyslav Mykhailichenko
Bas van Dijk
Jona Stubbe
Domen Kožar
lewo
Maximilian Bosch
tobim
John Ericson
viric
Matthew Stewart
Mario Rodas
Yegor Timoshenko
Ryan Mulligan
Gabriel Ebner
Silvan Mosberger
Luke Adams
Sander Hollaar
Alexandre Esteves
Tobias Mayer
georgewhewell
Robert Schütz
Tuomas Tynkkynen
Drew Hess
xeji
Ken Micklas
Shea Levy
Benno Fünfstück
Tom Bereknyei
Nikolay Amiantov
Andrew Childs
Peter Simons
Eldar Tsraev
Franz Pletz
adisbladis
Timofei Kushnir
Michael Raskin
Lancelot SIX
Daniel Barlow
Bjørn Forsman
Ben Gamari
Adrien Devresse
Victor Calvert
Markus Kowalewski
adisbladis
Herwig Hochleitner
Yurii Rashkovskii
Tobias Geerinckx-Rice
dywedir
Sarah Brofeldt
Robin Gloster
Samuel Dionne-Riel
Matthieu Coudron
Pascal Wittmann
Tuomas Tynkkynen
Eric Litak
José Romildo Malaquias
Piotr Bogdan
Kevin Cox
Patrick Mahoney
makefu
Roberto Di Remigio
Joachim Fasting
Michael Weiss
Samuel Leathers
Samuel Leathers
Bastian Köcher
Leandro Lisboa Penz
Rickard Nilsson
mimadrid
vinymeuh
Graham Christensen
Thomas Tuegel
Daniel Peebles
Dan Peebles
Peter Jones
Will Fancher
hsloan
TANIGUCHI Kohei
David McFarland
Ambroz Bizjak
Hamish Mackenzie
Mikael Brockman
Cole Scott
ndowens