Commit Graph

15733 Commits

Author SHA1 Message Date
Will Dietz
6e8118b239 nix: fix stdenv.system check -- should be hostPlatform
(stdenv.system is the system running the build, apparently)
2018-04-28 22:11:30 -05:00
obadz
65adfc73ad zerotierone: 1.2.4 -> 1.2.8 2018-04-28 14:47:13 +01:00
Matthew Justin Bauer
4359507e72
Merge pull request #39531 from r-ryantm/auto-update/openvpn
openvpn: 2.4.5 -> 2.4.6
2018-04-28 00:58:56 -05:00
Jean-Baptiste Giraudeau
92808e667f blobfuse: init at 1.0.1-RC-Preview (#39073) 2018-04-27 23:58:40 +01:00
Sander Hollaar
14568ddaab netcat-openbsd: 1.187 -> 1.190: (#39605)
http://metadata.ftp-master.debian.org/changelogs/main/n/netcat-openbsd/netcat-openbsd_1.190-1_changelog
2018-04-27 23:19:05 +01:00
xeji
61b96ab9a2
Merge pull request #39168 from vodkabot/master
twilight: init at 2018-04-19
2018-04-27 23:36:03 +02:00
Robert Schütz
ac0ee0c837
Merge pull request #39599 from erikarvstedt/opentimestamps
opentimestamps: 0.2.1 -> 0.3.0, opentimestamps-client: 0.5.1 -> 0.6.0
2018-04-27 23:31:05 +02:00
Erik Arvstedt
4e79f2fb42 opentimestamps-client: 0.5.1 -> 0.6.0 2018-04-27 23:10:04 +02:00
xeji
805d9878c3
Merge pull request #39410 from r-ryantm/auto-update/openfortivpn
openfortivpn: 1.6.0 -> 1.7.0
2018-04-27 20:30:05 +02:00
Matthew Justin Bauer
d0cf82cf85
Merge pull request #39532 from r-ryantm/auto-update/packagekit
packagekit: 1.1.9 -> 1.1.10
2018-04-27 13:19:43 -05:00
Jörg Thalheim
42581b23f2
Merge pull request #39598 from marsam/feature/update-vale
vale: 0.10.1 -> 0.11.2
2018-04-27 13:19:30 +01:00
Jörg Thalheim
37e79019d6
Merge pull request #39472 from ChengCat/fcitx-libpinyin
fcitx-libpinyin: fix data path
2018-04-27 10:59:33 +01:00
Jörg Thalheim
49f096b3e6
Merge pull request #39546 from r-ryantm/auto-update/hwinfo
hwinfo: 21.52 -> 21.53
2018-04-27 09:21:32 +01:00
Jörg Thalheim
3ce30f679e
Merge pull request #39568 from jlesquembre/psql
pspg: 1.0.0 -> 1.1.0
2018-04-27 09:04:04 +01:00
Mario Rodas
2cfda31cff vale: 0.10.1 -> 0.11.2 2018-04-26 22:20:30 -05:00
Yucheng Zhang
19f6fe6e9c fcitx-libpinyin: fix data path 2018-04-27 10:57:37 +08:00
Ruben Maher
e8dcf87007 awsebcli: 3.12.3 -> 3.12.4 2018-04-27 10:29:19 +09:30
Ruben Maher
ffe9f0a2bb awsebcli: pin pathspec dependency to 0.5.5
pathspec has been bumped to 0.5.6 in c705acef and awsebcli's setup.py refuses to
use that version.
2018-04-27 10:29:19 +09:30
Franz Pletz
c208823e2d
youtubeDL: 2018.04.16 -> 2018.04.25 2018-04-27 01:13:36 +02:00
Franz Pletz
1ae220b689
pssh: add explicit references to openssh and rsync 2018-04-27 01:12:08 +02:00
Jörg Thalheim
29d726bae1
Merge pull request #39557 from r-ryantm/auto-update/bdf2psf
bdf2psf: 1.178 -> 1.184
2018-04-26 23:10:29 +01:00
José Luis Lafuente
a95a0a932b
pspg: 1.0.0 -> 1.1.0 2018-04-26 20:28:06 +02:00
R. RyanTM
1cbbf3088e bdf2psf: 1.178 -> 1.184
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.

This update was made based on information from https://repology.org/metapackage/bdf2psf/versions.

These checks were done:

- built on NixOS
- ran ‘/nix/store/xd8wdqmq5583b39cl6bwv1n2mnfxlz2y-bdf2psf-1.184/bin/bdf2psf -h’ got 0 exit code
- ran ‘/nix/store/xd8wdqmq5583b39cl6bwv1n2mnfxlz2y-bdf2psf-1.184/bin/bdf2psf --help’ got 0 exit code
- found 1.184 with grep in /nix/store/xd8wdqmq5583b39cl6bwv1n2mnfxlz2y-bdf2psf-1.184
- directory tree listing: https://gist.github.com/8810c5939feee7c4840d8eae52e98832
2018-04-26 07:24:38 -07:00
R. RyanTM
50a4977252 hwinfo: 21.52 -> 21.53
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.

This update was made based on information from https://repology.org/metapackage/hwinfo/versions.

These checks were done:

- built on NixOS
- ran ‘/nix/store/a5f46qz0541j2jbqycbaq1y33nb356pj-hwinfo-21.53/bin/hwinfo -h’ got 0 exit code
- ran ‘/nix/store/a5f46qz0541j2jbqycbaq1y33nb356pj-hwinfo-21.53/bin/hwinfo --help’ got 0 exit code
- ran ‘/nix/store/a5f46qz0541j2jbqycbaq1y33nb356pj-hwinfo-21.53/bin/hwinfo --version’ and found version 21.53
- ran ‘/nix/store/a5f46qz0541j2jbqycbaq1y33nb356pj-hwinfo-21.53/bin/check_hd help’ got 0 exit code
- ran ‘/nix/store/a5f46qz0541j2jbqycbaq1y33nb356pj-hwinfo-21.53/bin/getsysinfo -h’ got 0 exit code
- ran ‘/nix/store/a5f46qz0541j2jbqycbaq1y33nb356pj-hwinfo-21.53/bin/getsysinfo --help’ got 0 exit code
- ran ‘/nix/store/a5f46qz0541j2jbqycbaq1y33nb356pj-hwinfo-21.53/bin/getsysinfo help’ got 0 exit code
- found 21.53 with grep in /nix/store/a5f46qz0541j2jbqycbaq1y33nb356pj-hwinfo-21.53
- directory tree listing: https://gist.github.com/c3f6d76aa5a198a4ded2f2598380a0ef
2018-04-26 04:43:51 -07:00
R. RyanTM
4176d58331 packagekit: 1.1.9 -> 1.1.10
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
2018-04-26 01:22:20 -07:00
R. RyanTM
8898063828 openvpn: 2.4.5 -> 2.4.6
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.

This update was made based on information from https://repology.org/metapackage/openvpn/versions.

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 2.4.6 with grep in /nix/store/5hj70y409c0b01zmx4rddiicgq7jajb2-openvpn-2.4.6
- directory tree listing: https://gist.github.com/ce0bc5e31d7d26ead341febdc7bdc6ee
2018-04-26 01:20:56 -07:00
Jörg Thalheim
5c6f84550f
Merge pull request #39520 from r-ryantm/auto-update/thefuck
thefuck: 3.25 -> 3.26
2018-04-26 09:00:44 +01:00
adisbladis
3e6558a409
Merge pull request #39519 from r-ryantm/auto-update/yubikey-personalization
yubikey-personalization: 1.18.1 -> 1.19.0
2018-04-26 15:26:19 +08:00
R. RyanTM
7cbf00847c thefuck: 3.25 -> 3.26
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.

This update was made based on information from https://repology.org/metapackage/thefuck/versions.

These checks were done:

- built on NixOS
- ran ‘/nix/store/p0waa9llvgzfvjv05vgwvsic2xlkm4jr-thefuck-3.26/bin/.thefuck-wrapped -h’ got 0 exit code
- ran ‘/nix/store/p0waa9llvgzfvjv05vgwvsic2xlkm4jr-thefuck-3.26/bin/.thefuck-wrapped --help’ got 0 exit code
- ran ‘/nix/store/p0waa9llvgzfvjv05vgwvsic2xlkm4jr-thefuck-3.26/bin/thefuck -h’ got 0 exit code
- ran ‘/nix/store/p0waa9llvgzfvjv05vgwvsic2xlkm4jr-thefuck-3.26/bin/thefuck --help’ got 0 exit code
- found 3.26 with grep in /nix/store/p0waa9llvgzfvjv05vgwvsic2xlkm4jr-thefuck-3.26
- directory tree listing: https://gist.github.com/7fd81df3f197603f76bdf8c0ae663dcb
2018-04-25 21:44:13 -07:00
R. RyanTM
3a8fb11949 yubikey-personalization: 1.18.1 -> 1.19.0
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.

This update was made based on information from https://repology.org/metapackage/yubikey-personalization/versions.

These checks were done:

- built on NixOS
- ran ‘/nix/store/gbg5yr1p726q33f057gwcjgq35jc8qg3-yubikey-personalization-1.19.0/bin/ykpersonalize -h’ got 0 exit code
- ran ‘/nix/store/gbg5yr1p726q33f057gwcjgq35jc8qg3-yubikey-personalization-1.19.0/bin/ykpersonalize --help’ got 0 exit code
- ran ‘/nix/store/gbg5yr1p726q33f057gwcjgq35jc8qg3-yubikey-personalization-1.19.0/bin/ykpersonalize -V’ and found version 1.19.0
- ran ‘/nix/store/gbg5yr1p726q33f057gwcjgq35jc8qg3-yubikey-personalization-1.19.0/bin/ykchalresp -h’ got 0 exit code
- ran ‘/nix/store/gbg5yr1p726q33f057gwcjgq35jc8qg3-yubikey-personalization-1.19.0/bin/ykchalresp --help’ got 0 exit code
- ran ‘/nix/store/gbg5yr1p726q33f057gwcjgq35jc8qg3-yubikey-personalization-1.19.0/bin/ykchalresp -V’ and found version 1.19.0
- ran ‘/nix/store/gbg5yr1p726q33f057gwcjgq35jc8qg3-yubikey-personalization-1.19.0/bin/ykinfo -h’ got 0 exit code
- ran ‘/nix/store/gbg5yr1p726q33f057gwcjgq35jc8qg3-yubikey-personalization-1.19.0/bin/ykinfo --help’ got 0 exit code
- ran ‘/nix/store/gbg5yr1p726q33f057gwcjgq35jc8qg3-yubikey-personalization-1.19.0/bin/ykinfo help’ got 0 exit code
- ran ‘/nix/store/gbg5yr1p726q33f057gwcjgq35jc8qg3-yubikey-personalization-1.19.0/bin/ykinfo -V’ and found version 1.19.0
- found 1.19.0 with grep in /nix/store/gbg5yr1p726q33f057gwcjgq35jc8qg3-yubikey-personalization-1.19.0
- directory tree listing: https://gist.github.com/6592e44c4a66c1b7cf2c9f4c2a75c3ab
2018-04-25 20:40:14 -07:00
Matthew Justin Bauer
160d9ed652
Merge pull request #36055 from ryantm/auto-update/thin-provisioning-tools-0.6.3-to-0.7.5
thin-provisioning-tools: 0.6.3 -> 0.7.5
2018-04-25 14:48:56 -05:00
Matthew Justin Bauer
a4a2626cd9
Merge pull request #35280 from markus1189/logkeys
Logkeys: Update and add `device` option to service
2018-04-25 14:48:29 -05:00
John Ericson
ba52ae5048 treewide: isArm -> isAarch32
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
2018-04-25 15:28:55 -04:00
Matthew Justin Bauer
e40213ed24
Merge pull request #39183 from r-ryantm/auto-update/xpra
xpra: 2.2.5 -> 2.2.6
2018-04-25 14:28:51 -05:00
Dmitry Kalinkin
31e9e752ae fio: 3.5 -> 3.6, enable on darwin (#39452) 2018-04-25 08:16:13 +01:00
Jan Malakhovski
bd1d0e0292 flashrom: fix build with gcc7 2018-04-25 04:21:27 +00:00
Jan Tojnar
7e33e374db
gupnp-tools: 0.8.13 → 0.8.14 2018-04-25 02:04:33 +02:00
R. RyanTM
6d9eb6c8a9 openfortivpn: 1.6.0 -> 1.7.0
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
2018-04-24 09:59:29 -07:00
Jörg Thalheim
62529a693b
Merge pull request #39336 from Ma27/fix-osquery
osquery: 2.5.2 -> 3.2.2
2018-04-24 09:29:46 +01:00
Francesco Gazzetta
56df1aca24 powerline-go: 1.8.2 -> 1.10.0 2018-04-24 06:47:44 +00:00
Maximilian Bosch
3cd2707e37
osquery: 2.5.2 -> 3.2.2
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
2018-04-24 07:13:49 +02:00
Robert Schütz
1aaab715e4
Merge pull request #39195 from teto/vdirsyncer
[RDY] Vdirsyncer update
2018-04-24 00:52:41 +02:00
Ryan Mulligan
d32983a1ca google-compute-engine: 20170914 -> 20180129 (#36565)
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
2018-04-23 22:03:19 +01:00
Matthew Justin Bauer
1439d0b9a2
Merge pull request #35685 from edef1c/ipxe-iso
ipxe: fix ISO build, update the package
2018-04-23 11:49:25 -05:00
Michael Weiss
cd1eefcd29 maim: 5.4.68 -> 5.5 2018-04-23 10:32:11 +02:00
Michael Weiss
85dfd4b41c slop: 7.3.49 -> 7.4 2018-04-23 10:32:11 +02:00
Matthias Beyer
49f55fa337 vdirsyncer: 0.16.4 -> 0.17.0a2 2018-04-23 17:19:26 +09:00
Tim Cuthbertson
1faea2934b nix-pin: 0.1.2 -> 0.2.2 and add updateScript 2018-04-23 15:38:16 +10:00
Jörg Thalheim
f2129ae7c7
Merge pull request #39339 from jluttine/fix-diskrsync-argv0
diskrsync: fix argv0
2018-04-22 23:25:29 +01:00
Jaakko Luttinen
0f92afdd6d
diskrsync: fix argv0
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.
2018-04-22 22:43:39 +03:00