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
The first problem that was introduced in a276d5160c
was a linking error:
ld: cannot find -licui18n
ld: cannot find -licuuc
ld: cannot find -licudata
So I added icu to the buildInputs.
The second problem was that the interpreter wasn't patched in
share/filters, apparently this is only needed when building with
autotools:
make[3]: Entering directory '/build/inkscape-0.92.3/share/filters'
./i18n.py ./filters.svg > ./filters.svg.h
./i18n.py: /usr/bin/env: bad interpreter: No such file or directory
A similar error also occurs for share/palettes, share/patterns,
share/symbols and share/templates, so I added patching the interpreter
there as well.
Switching to autotools in Inkscape is a very bad idea, because upstream
currently still has their own autotools files in the 0.92.x tree but
master already has them removed, see this commit:
e471a664f9
However for the sake of trying to not break Inkscape on Darwin again,
I tried to keep the fixes minimal and not went back to CMake.
I did however mark the stuff that's unneeded for CMake, so that we can
avoid forgetting to remove that crap once we get back to CMake.
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @matthewbauer
On GNU/Linux the build references these files, so let's fetch them from
the Chromium repository. I haven't checked whether they are heavily
patched or whether we can use the version from LLVM, but when looking at
the changes, they do seem to divert a bit from upstream LLVM.
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @matthewbauer, @stesie
The tarball from upstream seems to be generated on the fly, so the
output is not deterministic and using fetchzip makes this more reliable
as we have a recursively hashed output path without any of the
non-determinisms in tarballs.
Unfortunately, the build still fails on NixOS systems, because we need a
few more stuff in the build tree.
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @matthewbauer, @stesie
Fixes#39334
and Fixes#36729
Also, Fixes#36932 (hopefully it's still building)
(This might be able to be able to be cherry-picked to 18.03 but be
careful - chromium is extremely touchy. Probably best to wait for it
to be built successfully on Hydra a few times.)
Otherwise the build fails with the perplexing error
make: *** No rule to make target 'cmd-list.made', needed by 'doc.dep'. Stop.
make: Leaving directory '/tmp/nix-build-git-2.16.3.drv-0/git-2.16.3/Documentation'
on NixOS (but not on Debian, where it succeeds, presumably since it picks up the
system perl).
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/eccodes/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/i6m5cl0plmsnll3n90h88vcnjc269vh9-eccodes-2.7.3/bin/codes_info -v’ and found version 2.7.3
- ran ‘/nix/store/i6m5cl0plmsnll3n90h88vcnjc269vh9-eccodes-2.7.3/bin/grib_histogram -h’ got 0 exit code
- ran ‘/nix/store/i6m5cl0plmsnll3n90h88vcnjc269vh9-eccodes-2.7.3/bin/grib_histogram --help’ got 0 exit code
- ran ‘/nix/store/i6m5cl0plmsnll3n90h88vcnjc269vh9-eccodes-2.7.3/bin/grib_filter -V’ and found version 2.7.3
- ran ‘/nix/store/i6m5cl0plmsnll3n90h88vcnjc269vh9-eccodes-2.7.3/bin/grib_ls -V’ and found version 2.7.3
- ran ‘/nix/store/i6m5cl0plmsnll3n90h88vcnjc269vh9-eccodes-2.7.3/bin/grib_dump -V’ and found version 2.7.3
- ran ‘/nix/store/i6m5cl0plmsnll3n90h88vcnjc269vh9-eccodes-2.7.3/bin/grib_merge -V’ and found version 2.7.3
- ran ‘/nix/store/i6m5cl0plmsnll3n90h88vcnjc269vh9-eccodes-2.7.3/bin/grib2ppm -h’ got 0 exit code
- ran ‘/nix/store/i6m5cl0plmsnll3n90h88vcnjc269vh9-eccodes-2.7.3/bin/grib2ppm --help’ got 0 exit code
- ran ‘/nix/store/i6m5cl0plmsnll3n90h88vcnjc269vh9-eccodes-2.7.3/bin/grib_set -V’ and found version 2.7.3
- ran ‘/nix/store/i6m5cl0plmsnll3n90h88vcnjc269vh9-eccodes-2.7.3/bin/grib_get -V’ and found version 2.7.3
- ran ‘/nix/store/i6m5cl0plmsnll3n90h88vcnjc269vh9-eccodes-2.7.3/bin/grib_get_data -V’ and found version 2.7.3
- ran ‘/nix/store/i6m5cl0plmsnll3n90h88vcnjc269vh9-eccodes-2.7.3/bin/grib_copy -V’ and found version 2.7.3
- ran ‘/nix/store/i6m5cl0plmsnll3n90h88vcnjc269vh9-eccodes-2.7.3/bin/grib_compare -V’ and found version 2.7.3
- ran ‘/nix/store/i6m5cl0plmsnll3n90h88vcnjc269vh9-eccodes-2.7.3/bin/grib_index_build help’ got 0 exit code
- ran ‘/nix/store/i6m5cl0plmsnll3n90h88vcnjc269vh9-eccodes-2.7.3/bin/grib_index_build -V’ and found version 2.7.3
- ran ‘/nix/store/i6m5cl0plmsnll3n90h88vcnjc269vh9-eccodes-2.7.3/bin/bufr_ls -V’ and found version 2.7.3
- ran ‘/nix/store/i6m5cl0plmsnll3n90h88vcnjc269vh9-eccodes-2.7.3/bin/bufr_dump -V’ and found version 2.7.3
- ran ‘/nix/store/i6m5cl0plmsnll3n90h88vcnjc269vh9-eccodes-2.7.3/bin/bufr_set -V’ and found version 2.7.3
- ran ‘/nix/store/i6m5cl0plmsnll3n90h88vcnjc269vh9-eccodes-2.7.3/bin/bufr_get -V’ and found version 2.7.3
- ran ‘/nix/store/i6m5cl0plmsnll3n90h88vcnjc269vh9-eccodes-2.7.3/bin/bufr_copy -V’ and found version 2.7.3
- ran ‘/nix/store/i6m5cl0plmsnll3n90h88vcnjc269vh9-eccodes-2.7.3/bin/bufr_compare -V’ and found version 2.7.3
- ran ‘/nix/store/i6m5cl0plmsnll3n90h88vcnjc269vh9-eccodes-2.7.3/bin/bufr_index_build help’ got 0 exit code
- ran ‘/nix/store/i6m5cl0plmsnll3n90h88vcnjc269vh9-eccodes-2.7.3/bin/bufr_index_build -V’ and found version 2.7.3
- ran ‘/nix/store/i6m5cl0plmsnll3n90h88vcnjc269vh9-eccodes-2.7.3/bin/gts_get -V’ and found version 2.7.3
- ran ‘/nix/store/i6m5cl0plmsnll3n90h88vcnjc269vh9-eccodes-2.7.3/bin/gts_compare -V’ and found version 2.7.3
- ran ‘/nix/store/i6m5cl0plmsnll3n90h88vcnjc269vh9-eccodes-2.7.3/bin/gts_copy -V’ and found version 2.7.3
- ran ‘/nix/store/i6m5cl0plmsnll3n90h88vcnjc269vh9-eccodes-2.7.3/bin/gts_dump -V’ and found version 2.7.3
- ran ‘/nix/store/i6m5cl0plmsnll3n90h88vcnjc269vh9-eccodes-2.7.3/bin/gts_filter -V’ and found version 2.7.3
- ran ‘/nix/store/i6m5cl0plmsnll3n90h88vcnjc269vh9-eccodes-2.7.3/bin/gts_ls -V’ and found version 2.7.3
- ran ‘/nix/store/i6m5cl0plmsnll3n90h88vcnjc269vh9-eccodes-2.7.3/bin/metar_dump -V’ and found version 2.7.3
- ran ‘/nix/store/i6m5cl0plmsnll3n90h88vcnjc269vh9-eccodes-2.7.3/bin/metar_ls -V’ and found version 2.7.3
- ran ‘/nix/store/i6m5cl0plmsnll3n90h88vcnjc269vh9-eccodes-2.7.3/bin/metar_compare -V’ and found version 2.7.3
- ran ‘/nix/store/i6m5cl0plmsnll3n90h88vcnjc269vh9-eccodes-2.7.3/bin/metar_get -V’ and found version 2.7.3
- ran ‘/nix/store/i6m5cl0plmsnll3n90h88vcnjc269vh9-eccodes-2.7.3/bin/metar_filter -V’ and found version 2.7.3
- ran ‘/nix/store/i6m5cl0plmsnll3n90h88vcnjc269vh9-eccodes-2.7.3/bin/metar_copy -V’ and found version 2.7.3
- ran ‘/nix/store/i6m5cl0plmsnll3n90h88vcnjc269vh9-eccodes-2.7.3/bin/grib_to_netcdf -V’ and found version 2.7.3
- ran ‘/nix/store/i6m5cl0plmsnll3n90h88vcnjc269vh9-eccodes-2.7.3/bin/codes_bufr_filter -V’ and found version 2.7.3
- ran ‘/nix/store/i6m5cl0plmsnll3n90h88vcnjc269vh9-eccodes-2.7.3/bin/bufr_filter -V’ and found version 2.7.3
- found 2.7.3 with grep in /nix/store/i6m5cl0plmsnll3n90h88vcnjc269vh9-eccodes-2.7.3
- directory tree listing: https://gist.github.com/f485bc3b3d6105246360c970ac7462e1
Adds a couple of useful NetBSD and OpenBSD derivations. Some of these
will be integrated into Nixpkgs later.
Noncomprehensive list:
- netbsd.getent
- netbsd.getconf
- netbsd.fts
- openbsd.mg
- netbsd.compat (can replace libbsd)
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/latte-dock/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/6nvkkskm7j4ngqfy722ajp289gqhg1a9-latte-dock-0.7.5/bin/latte-dock -h’ got 0 exit code
- ran ‘/nix/store/6nvkkskm7j4ngqfy722ajp289gqhg1a9-latte-dock-0.7.5/bin/latte-dock --help’ got 0 exit code
- found 0.7.5 with grep in /nix/store/6nvkkskm7j4ngqfy722ajp289gqhg1a9-latte-dock-0.7.5
- directory tree listing: https://gist.github.com/8f58b4f85d4c80752b6d66e912ce92c0
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/pcmanfm/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/z37gyw9vskaby2caizkzghjd7ikafv64-pcmanfm-1.3.0/bin/pcmanfm -h’ got 0 exit code
- ran ‘/nix/store/z37gyw9vskaby2caizkzghjd7ikafv64-pcmanfm-1.3.0/bin/pcmanfm --help’ got 0 exit code
- ran ‘/nix/store/z37gyw9vskaby2caizkzghjd7ikafv64-pcmanfm-1.3.0/bin/.pcmanfm-wrapped -h’ got 0 exit code
- ran ‘/nix/store/z37gyw9vskaby2caizkzghjd7ikafv64-pcmanfm-1.3.0/bin/.pcmanfm-wrapped --help’ got 0 exit code
- found 1.3.0 with grep in /nix/store/z37gyw9vskaby2caizkzghjd7ikafv64-pcmanfm-1.3.0
- directory tree listing: https://gist.github.com/f15deaa66af5124a632abbca797f7240
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/osrm-backend/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/y0779ksgxhvysi6ha717axl7v06grmar-osrm-backend-5.17.2/bin/osrm-extract -h’ got 0 exit code
- ran ‘/nix/store/y0779ksgxhvysi6ha717axl7v06grmar-osrm-backend-5.17.2/bin/osrm-extract --help’ got 0 exit code
- ran ‘/nix/store/y0779ksgxhvysi6ha717axl7v06grmar-osrm-backend-5.17.2/bin/osrm-extract -v’ and found version 5.17.2
- ran ‘/nix/store/y0779ksgxhvysi6ha717axl7v06grmar-osrm-backend-5.17.2/bin/osrm-extract --version’ and found version 5.17.2
- ran ‘/nix/store/y0779ksgxhvysi6ha717axl7v06grmar-osrm-backend-5.17.2/bin/osrm-partition -h’ got 0 exit code
- ran ‘/nix/store/y0779ksgxhvysi6ha717axl7v06grmar-osrm-backend-5.17.2/bin/osrm-partition --help’ got 0 exit code
- ran ‘/nix/store/y0779ksgxhvysi6ha717axl7v06grmar-osrm-backend-5.17.2/bin/osrm-partition -v’ and found version 5.17.2
- ran ‘/nix/store/y0779ksgxhvysi6ha717axl7v06grmar-osrm-backend-5.17.2/bin/osrm-partition --version’ and found version 5.17.2
- ran ‘/nix/store/y0779ksgxhvysi6ha717axl7v06grmar-osrm-backend-5.17.2/bin/osrm-customize -h’ got 0 exit code
- ran ‘/nix/store/y0779ksgxhvysi6ha717axl7v06grmar-osrm-backend-5.17.2/bin/osrm-customize --help’ got 0 exit code
- ran ‘/nix/store/y0779ksgxhvysi6ha717axl7v06grmar-osrm-backend-5.17.2/bin/osrm-customize -v’ and found version 5.17.2
- ran ‘/nix/store/y0779ksgxhvysi6ha717axl7v06grmar-osrm-backend-5.17.2/bin/osrm-customize --version’ and found version 5.17.2
- ran ‘/nix/store/y0779ksgxhvysi6ha717axl7v06grmar-osrm-backend-5.17.2/bin/osrm-contract -h’ got 0 exit code
- ran ‘/nix/store/y0779ksgxhvysi6ha717axl7v06grmar-osrm-backend-5.17.2/bin/osrm-contract --help’ got 0 exit code
- ran ‘/nix/store/y0779ksgxhvysi6ha717axl7v06grmar-osrm-backend-5.17.2/bin/osrm-contract -v’ and found version 5.17.2
- ran ‘/nix/store/y0779ksgxhvysi6ha717axl7v06grmar-osrm-backend-5.17.2/bin/osrm-contract --version’ and found version 5.17.2
- ran ‘/nix/store/y0779ksgxhvysi6ha717axl7v06grmar-osrm-backend-5.17.2/bin/osrm-datastore -h’ got 0 exit code
- ran ‘/nix/store/y0779ksgxhvysi6ha717axl7v06grmar-osrm-backend-5.17.2/bin/osrm-datastore --help’ got 0 exit code
- ran ‘/nix/store/y0779ksgxhvysi6ha717axl7v06grmar-osrm-backend-5.17.2/bin/osrm-datastore -v’ and found version 5.17.2
- ran ‘/nix/store/y0779ksgxhvysi6ha717axl7v06grmar-osrm-backend-5.17.2/bin/osrm-datastore --version’ and found version 5.17.2
- ran ‘/nix/store/y0779ksgxhvysi6ha717axl7v06grmar-osrm-backend-5.17.2/bin/osrm-routed -h’ got 0 exit code
- ran ‘/nix/store/y0779ksgxhvysi6ha717axl7v06grmar-osrm-backend-5.17.2/bin/osrm-routed --help’ got 0 exit code
- ran ‘/nix/store/y0779ksgxhvysi6ha717axl7v06grmar-osrm-backend-5.17.2/bin/osrm-routed -v’ and found version 5.17.2
- ran ‘/nix/store/y0779ksgxhvysi6ha717axl7v06grmar-osrm-backend-5.17.2/bin/osrm-routed --version’ and found version 5.17.2
- found 5.17.2 with grep in /nix/store/y0779ksgxhvysi6ha717axl7v06grmar-osrm-backend-5.17.2
- directory tree listing: https://gist.github.com/82e852d822486a83285e755488f6d056
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/openfortivpn/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/p02dl9fy2g9f6dddm4i0z1nbi4b4vk7j-openfortivpn-1.7.0/bin/openfortivpn -h’ got 0 exit code
- ran ‘/nix/store/p02dl9fy2g9f6dddm4i0z1nbi4b4vk7j-openfortivpn-1.7.0/bin/openfortivpn --help’ got 0 exit code
- ran ‘/nix/store/p02dl9fy2g9f6dddm4i0z1nbi4b4vk7j-openfortivpn-1.7.0/bin/openfortivpn help’ got 0 exit code
- ran ‘/nix/store/p02dl9fy2g9f6dddm4i0z1nbi4b4vk7j-openfortivpn-1.7.0/bin/openfortivpn --version’ and found version 1.7.0
- found 1.7.0 with grep in /nix/store/p02dl9fy2g9f6dddm4i0z1nbi4b4vk7j-openfortivpn-1.7.0
- directory tree listing: https://gist.github.com/34708b90f0d4fc975a7b9dbd4670bfee
Unfortunately, the new version fails its test suite AGAIN when the recommended
packages are not build. Makes one wonder whether maybe we should offer the R
developers CI builds that check this. I've reported the issue upstream, let's
see what happens.
The package was originally broken as reported in #38940 and
facebook/osquery#4257. The latest version (3.x) contains several
important fixes for GCC 7, so now we can compile without a much less
complicated patches.
The following changes were needed to fix the derivation:
* Upgrade `osquery/third-party` to the latest rev to be compliant with
osquery 3.
* Keep using an override for the AWS SDK (for a lower closure size and
less compile time), but make the `ec2` API available.
* Added the dependencies `fpm`, `zstd`, `rdkafka`, `rapidjson` to the
build. `linenoise-ng` is obsolete as it's directly bundled with
`osquery/third-party`.
* Fixed the linking issue with `gflags` as recommended in the mailing
list: https://groups.google.com/d/msg/nix-devel/l1blj-mWxtI/J3CwPATBCAAJ
* Dropped the obsolete dependencies `cpp-netlib`, `lz4`, `apt` and
`devicemapper` (thanks @Infinisil).
* Override `OSQUERY_PLATFORM` to provide `nixos:version`
for sandbox and non-NixOS based builds. The `platform-nixos.patch`
file is now obsolete (thanks @flokli).
The patch was rebased against the 3.x branch of `osquery` and contains
mostly old changes. Additionally several testing targets were skipped as
they broke the build.
The functionality has been testing using the following command:
```
mkdir /tmp/osq.log/
./result/bin/osqueryd --pidfile /tmp/osq.pid \
--database_path /tmp/test.db --logger_path /tmp/osq.log
```
With the daemon running the database can be queried easily using
`./result/bin/osqueryi`.
Fixes ticket #38940
See ticket #36453
Further reference can be gathered from the affected Hydra logs for
the master branch: https://hydra.nixos.org/job/nixos/trunk-combined/nixpkgs.osquery.x86_64-linux
Semi-automatic update. These checks were done:
- built on NixOS
- ran `/nix/store/xxf54yjdmhkmsy5h0rrh985lygpi3sjv-google-compute-engine-20180129/bin/optimize_local_ssd -h` got 0 exit code
- ran `/nix/store/xxf54yjdmhkmsy5h0rrh985lygpi3sjv-google-compute-engine-20180129/bin/optimize_local_ssd --help` got 0 exit code
- ran `/nix/store/xxf54yjdmhkmsy5h0rrh985lygpi3sjv-google-compute-engine-20180129/bin/optimize_local_ssd help` got 0 exit code
- ran `/nix/store/xxf54yjdmhkmsy5h0rrh985lygpi3sjv-google-compute-engine-20180129/bin/set_multiqueue -h` got 0 exit code
- ran `/nix/store/xxf54yjdmhkmsy5h0rrh985lygpi3sjv-google-compute-engine-20180129/bin/set_multiqueue --help` got 0 exit code
- ran `/nix/store/xxf54yjdmhkmsy5h0rrh985lygpi3sjv-google-compute-engine-20180129/bin/set_multiqueue help` got 0 exit code
- ran `/nix/store/xxf54yjdmhkmsy5h0rrh985lygpi3sjv-google-compute-engine-20180129/bin/set_multiqueue -V` and found version 20180129
- ran `/nix/store/xxf54yjdmhkmsy5h0rrh985lygpi3sjv-google-compute-engine-20180129/bin/set_multiqueue -v` and found version 20180129
- ran `/nix/store/xxf54yjdmhkmsy5h0rrh985lygpi3sjv-google-compute-engine-20180129/bin/set_multiqueue --version` and found version 20180129
- ran `/nix/store/xxf54yjdmhkmsy5h0rrh985lygpi3sjv-google-compute-engine-20180129/bin/set_multiqueue version` and found version 20180129
- ran `/nix/store/xxf54yjdmhkmsy5h0rrh985lygpi3sjv-google-compute-engine-20180129/bin/set_multiqueue -h` and found version 20180129
- ran `/nix/store/xxf54yjdmhkmsy5h0rrh985lygpi3sjv-google-compute-engine-20180129/bin/set_multiqueue --help` and found version 20180129
- ran `/nix/store/xxf54yjdmhkmsy5h0rrh985lygpi3sjv-google-compute-engine-20180129/bin/set_multiqueue help` and found version 20180129
- ran `/nix/store/xxf54yjdmhkmsy5h0rrh985lygpi3sjv-google-compute-engine-20180129/bin/.google_accounts_daemon-wrapped -h` got 0 exit code
- ran `/nix/store/xxf54yjdmhkmsy5h0rrh985lygpi3sjv-google-compute-engine-20180129/bin/.google_accounts_daemon-wrapped --help` got 0 exit code
- ran `/nix/store/xxf54yjdmhkmsy5h0rrh985lygpi3sjv-google-compute-engine-20180129/bin/google_accounts_daemon -h` got 0 exit code
- ran `/nix/store/xxf54yjdmhkmsy5h0rrh985lygpi3sjv-google-compute-engine-20180129/bin/google_accounts_daemon --help` got 0 exit code
- ran `/nix/store/xxf54yjdmhkmsy5h0rrh985lygpi3sjv-google-compute-engine-20180129/bin/.google_instance_setup-wrapped -h` got 0 exit code
- ran `/nix/store/xxf54yjdmhkmsy5h0rrh985lygpi3sjv-google-compute-engine-20180129/bin/.google_instance_setup-wrapped --help` got 0 exit code
- ran `/nix/store/xxf54yjdmhkmsy5h0rrh985lygpi3sjv-google-compute-engine-20180129/bin/google_instance_setup -h` got 0 exit code
- ran `/nix/store/xxf54yjdmhkmsy5h0rrh985lygpi3sjv-google-compute-engine-20180129/bin/google_instance_setup --help` got 0 exit code
- ran `/nix/store/xxf54yjdmhkmsy5h0rrh985lygpi3sjv-google-compute-engine-20180129/bin/.google_network_setup-wrapped -h` got 0 exit code
- ran `/nix/store/xxf54yjdmhkmsy5h0rrh985lygpi3sjv-google-compute-engine-20180129/bin/.google_network_setup-wrapped --help` got 0 exit code
- ran `/nix/store/xxf54yjdmhkmsy5h0rrh985lygpi3sjv-google-compute-engine-20180129/bin/google_network_setup -h` got 0 exit code
- ran `/nix/store/xxf54yjdmhkmsy5h0rrh985lygpi3sjv-google-compute-engine-20180129/bin/google_network_setup --help` got 0 exit code
- ran `/nix/store/xxf54yjdmhkmsy5h0rrh985lygpi3sjv-google-compute-engine-20180129/bin/.google_ip_forwarding_daemon-wrapped -h` got 0 exit code
- ran `/nix/store/xxf54yjdmhkmsy5h0rrh985lygpi3sjv-google-compute-engine-20180129/bin/.google_ip_forwarding_daemon-wrapped --help` got 0 exit code
- ran `/nix/store/xxf54yjdmhkmsy5h0rrh985lygpi3sjv-google-compute-engine-20180129/bin/.google_ip_forwarding_daemon-wrapped help` got 0 exit code
- ran `/nix/store/xxf54yjdmhkmsy5h0rrh985lygpi3sjv-google-compute-engine-20180129/bin/google_ip_forwarding_daemon -h` got 0 exit code
- ran `/nix/store/xxf54yjdmhkmsy5h0rrh985lygpi3sjv-google-compute-engine-20180129/bin/google_ip_forwarding_daemon --help` got 0 exit code
- ran `/nix/store/xxf54yjdmhkmsy5h0rrh985lygpi3sjv-google-compute-engine-20180129/bin/google_ip_forwarding_daemon help` got 0 exit code
- ran `/nix/store/xxf54yjdmhkmsy5h0rrh985lygpi3sjv-google-compute-engine-20180129/bin/.google_clock_skew_daemon-wrapped -h` got 0 exit code
- ran `/nix/store/xxf54yjdmhkmsy5h0rrh985lygpi3sjv-google-compute-engine-20180129/bin/.google_clock_skew_daemon-wrapped --help` got 0 exit code
- ran `/nix/store/xxf54yjdmhkmsy5h0rrh985lygpi3sjv-google-compute-engine-20180129/bin/.google_clock_skew_daemon-wrapped help` got 0 exit code
- ran `/nix/store/xxf54yjdmhkmsy5h0rrh985lygpi3sjv-google-compute-engine-20180129/bin/google_clock_skew_daemon -h` got 0 exit code
- ran `/nix/store/xxf54yjdmhkmsy5h0rrh985lygpi3sjv-google-compute-engine-20180129/bin/google_clock_skew_daemon --help` got 0 exit code
- ran `/nix/store/xxf54yjdmhkmsy5h0rrh985lygpi3sjv-google-compute-engine-20180129/bin/google_clock_skew_daemon help` got 0 exit code
- ran `/nix/store/xxf54yjdmhkmsy5h0rrh985lygpi3sjv-google-compute-engine-20180129/bin/.google_metadata_script_runner-wrapped -h` got 0 exit code
- ran `/nix/store/xxf54yjdmhkmsy5h0rrh985lygpi3sjv-google-compute-engine-20180129/bin/.google_metadata_script_runner-wrapped --help` got 0 exit code
- ran `/nix/store/xxf54yjdmhkmsy5h0rrh985lygpi3sjv-google-compute-engine-20180129/bin/google_metadata_script_runner -h` got 0 exit code
- ran `/nix/store/xxf54yjdmhkmsy5h0rrh985lygpi3sjv-google-compute-engine-20180129/bin/google_metadata_script_runner --help` got 0 exit code
- found 20180129 with grep in /nix/store/xxf54yjdmhkmsy5h0rrh985lygpi3sjv-google-compute-engine-20180129
- found 20180129 in filename of file in /nix/store/xxf54yjdmhkmsy5h0rrh985lygpi3sjv-google-compute-engine-20180129
only build on Linux
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/sabnzbd/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/rl41iqq34y5lbia598awnnr5zlqvn7p0-sabnzbd-2.3.3/bin/.sabnzbd-wrapped -h’ got 0 exit code
- ran ‘/nix/store/rl41iqq34y5lbia598awnnr5zlqvn7p0-sabnzbd-2.3.3/bin/.sabnzbd-wrapped --help’ got 0 exit code
- ran ‘/nix/store/rl41iqq34y5lbia598awnnr5zlqvn7p0-sabnzbd-2.3.3/bin/sabnzbd -h’ got 0 exit code
- ran ‘/nix/store/rl41iqq34y5lbia598awnnr5zlqvn7p0-sabnzbd-2.3.3/bin/sabnzbd --help’ got 0 exit code
- found 2.3.3 with grep in /nix/store/rl41iqq34y5lbia598awnnr5zlqvn7p0-sabnzbd-2.3.3
- directory tree listing: https://gist.github.com/06ad54e65a99a41896933852c69b59c1
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/sc-controller/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/d6a2kmmbi7lw8xq2yk7si8qd4af897lx-sc-controller-0.4.2/bin/scc -h’ got 0 exit code
- ran ‘/nix/store/d6a2kmmbi7lw8xq2yk7si8qd4af897lx-sc-controller-0.4.2/bin/scc --help’ got 0 exit code
- ran ‘/nix/store/d6a2kmmbi7lw8xq2yk7si8qd4af897lx-sc-controller-0.4.2/bin/scc help’ got 0 exit code
- ran ‘/nix/store/d6a2kmmbi7lw8xq2yk7si8qd4af897lx-sc-controller-0.4.2/bin/..scc-wrapped-wrapped -h’ got 0 exit code
- ran ‘/nix/store/d6a2kmmbi7lw8xq2yk7si8qd4af897lx-sc-controller-0.4.2/bin/..scc-wrapped-wrapped --help’ got 0 exit code
- ran ‘/nix/store/d6a2kmmbi7lw8xq2yk7si8qd4af897lx-sc-controller-0.4.2/bin/..scc-wrapped-wrapped help’ got 0 exit code
- ran ‘/nix/store/d6a2kmmbi7lw8xq2yk7si8qd4af897lx-sc-controller-0.4.2/bin/.scc-wrapped -h’ got 0 exit code
- ran ‘/nix/store/d6a2kmmbi7lw8xq2yk7si8qd4af897lx-sc-controller-0.4.2/bin/.scc-wrapped --help’ got 0 exit code
- ran ‘/nix/store/d6a2kmmbi7lw8xq2yk7si8qd4af897lx-sc-controller-0.4.2/bin/.scc-wrapped help’ got 0 exit code
- found 0.4.2 with grep in /nix/store/d6a2kmmbi7lw8xq2yk7si8qd4af897lx-sc-controller-0.4.2
- directory tree listing: https://gist.github.com/3f673ef175fbb295f67a2384aef61ede
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/urh/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/cs9vqxk0xqcpqcs10bbqhq6h7vdbmyny-urh-2.0.2/bin/.urh-wrapped --version’ and found version 2.0.2
- ran ‘/nix/store/cs9vqxk0xqcpqcs10bbqhq6h7vdbmyny-urh-2.0.2/bin/urh --version’ and found version 2.0.2
- found 2.0.2 with grep in /nix/store/cs9vqxk0xqcpqcs10bbqhq6h7vdbmyny-urh-2.0.2
- directory tree listing: https://gist.github.com/fd267c85c4f90f14b9af167c50b169a0
When using diskrsync over SSH, on the remote machine it calls an executable
equal to argv0. Typically, this is just diskrsync but now that diskrsync is
wrapped, the wrapper uses absolute path to diskrsync and that path doesn't most
likely work on the remote machine. Thus, we need to force argv0 to "diskrsync"
so that it works on the remote machine.
aka 5.01+coreboot-001+
The version maintained by coreboot project is superior to Debian, it
integrates all the Debian patches and fixes a bunch more bugs.
In particular, it fixes SMP freezes and apparent memory errors when
running under coreboot ROM.
With hardening enabled it reports errors on known-good memory modules
on my Thinkpad X230 (Ivy Bridge). It's the same bug as reported in
https://bugs.launchpad.net/ubuntu/+source/memtest86+/+bug/1071209 but
memtest86+ fails on test #9 instead of test #7 (because #7 in 4.20
became #9 in 5.01) and with all the addresses multiplied by 2 (I guess
the bug was reported for i686, and I test on x86_64, it was 2012 after
all).
Setting haskell.packageOverrides like so:
haskell = super.haskell // {
packageOverrides = self: super: {
my-package = ...;
my-other-package = ...;
};
};
causes all compiler-specific package sets to be overridden with those
overrides.
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/gegl/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/2w7m19f387zkwhxbv6k2p8nrrlwqimpn-gegl-0.3.34/bin/gegl -h’ got 0 exit code
- ran ‘/nix/store/2w7m19f387zkwhxbv6k2p8nrrlwqimpn-gegl-0.3.34/bin/gegl --help’ got 0 exit code
- found 0.3.34 with grep in /nix/store/2w7m19f387zkwhxbv6k2p8nrrlwqimpn-gegl-0.3.34
- directory tree listing: https://gist.github.com/96c792a5cd60943effce7884fc50cc3a
I've rebuild all packages that depend on gpgme and everything seems fine
so far (there are a few failures but the ones I've checked are unrelated
to gpgme).
Upstream release notes (Noteworthy changes in version 1.11.1):
* Fixed build problems in the 1.11.0 release.
* Added C++ interfaces which were planned for 1.11.0.
The 1.11.0 release came with these changes:
* New encryption API to support direct key specification including
hidden recipients option and taking keys from a file. This also
allows to enforce the use of a subkey.
* New encryption flag for the new API to enforce the use of plain
mail addresses (addr-spec).
* The import API can now tell whether v3 keys are skipped. These old
and basically broken keys are not anymore supported by GnuPG 2.1.
* The decrypt and verify API will now return the MIME flag as
specified by RFC-4880bis.
* The offline mode now has an effect on gpg by disabling all network
access. [#3831]
* A failed OpenPGP verification how returns the fingerprint of the
intended key if a recent gpg version was used for signature
creation.
* New tool gpgme-json as native messaging server for web browsers.
As of now public key encryption and decryption is supported.
Requires Libgpg-error 1.29.
* New context flag "request-origin" which has an effect when used
with GnuPG 2.2.6 or later.
* New context flag "no-symkey-cache" which has an effect when used
with GnuPG 2.2.7 or later.
* New convenience constant GPGME_KEYLIST_MODE_LOCATE.
* Improved the Python documentation.
* Fixed a potential regression with GnuPG 2.2.6 or later.
* Fixed a crash in the Python bindings on 32 bit platforms. [#3892]
* Various minor fixes.