1
0
Fork 1
mirror of https://github.com/NixOS/nixpkgs.git synced 2024-12-04 19:45:54 +00:00
Commit graph

15701 commits

Author SHA1 Message Date
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
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
Jan Malakhovski c3148948ff memtest86plus: 5.01 -> 5.01+coreboot-20180113
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.
2018-04-22 21:51:05 +03:00
Jan Malakhovski 7de43f38e0 memtest86plus: disable all hardening
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).
2018-04-22 21:51:05 +03:00
Jörg Thalheim 94d92fd046 Revert "nix-pin: 0.1.2 -> 0.2.2"
This reverts commit 92f083af23.

breaks evaluation
2018-04-22 16:43:27 +01:00
Jörg Thalheim b96cc8fb86 Revert "nix-pin: add passthru.updateScript"
This reverts commit 146dabd4ac.

breaks evaluation
2018-04-22 16:43:18 +01:00
Jörg Thalheim c3e78d3988
Merge pull request #39123 from Infinisil/add/dust
dust: init at 0.2.3
2018-04-22 16:21:49 +01:00
Jörg Thalheim 37fc73754e
Merge pull request #39231 from r-ryantm/auto-update/ibus-libpinyin
ibus-engines.libpinyin: 1.9.3 -> 1.10.0
2018-04-22 16:04:36 +01:00
Jörg Thalheim cd2cb152be
Merge pull request #39184 from r-ryantm/auto-update/youtube-dl
python27Packages.youtube-dl: 2018.03.26.1 -> 2018.04.16
2018-04-22 15:38:34 +01:00
Jörg Thalheim caa45305fe nix-review: 0.1.2 -> 0.2.0 2018-04-22 12:50:25 +01:00
Jörg Thalheim f56d484225
Merge pull request #39323 from timbertson/nix-pin
nix-pin: 0.1.2 -> 0.2.2
2018-04-22 12:20:01 +01:00
Jörg Thalheim 7c370ae6c7
Merge pull request #39325 from timbertson/nix-update-source
nix-update-source: 0.4.0 -> 0.5.0
2018-04-22 12:18:31 +01:00
Frederik Rietdijk b25c04d158
Merge pull request #39293 from FRidh/asciidoctor
asciidoctor: remove mathematical from wrapper, fixes #39098
2018-04-22 08:32:34 +02:00
Tim Cuthbertson 146dabd4ac nix-pin: add passthru.updateScript 2018-04-22 15:17:39 +10:00
Tim Cuthbertson 0eab0596d0 nix-update-source: 0.4.0 -> 0.5.0 2018-04-22 15:15:34 +10:00
Tim Cuthbertson 92f083af23 nix-pin: 0.1.2 -> 0.2.2 2018-04-22 14:12:32 +10:00
Michael Weiss 355d39c02c lf: 2 -> 3 2018-04-21 23:59:17 +02:00
Jörg Thalheim 3df0ac9762
Merge pull request #39198 from r-ryantm/auto-update/playerctl
playerctl: 0.5.0 -> 0.6.0
2018-04-21 19:02:20 +01:00
Pascal Wittmann 3d1976b083
pdf2djvu: 0.9.8 -> 0.9.9 2018-04-21 15:48:27 +02:00
Herwig Hochleitner dcf7e63f37 i2p: 0.9.33 -> 0.9.34 2018-04-21 14:57:44 +02:00
Jörg Thalheim c0eaaaef33
Merge pull request #39236 from ckauhaus/vulnix-update-1.6
vulnix: 1.4.0 -> 1.6.1
2018-04-21 12:08:25 +01:00
Jörg Thalheim e5e8a85555 xfstests: 2017-07-16 -> 2018-04-11 2018-04-21 11:53:08 +01:00
Jörg Thalheim 04ec325166
Merge pull request #39242 from r-ryantm/auto-update/fio
fio: 3.5 -> 3.6
2018-04-21 11:50:43 +01:00
Jörg Thalheim 7c7bd9bb2c
Merge pull request #39247 from r-ryantm/auto-update/facter
facter: 3.11.0 -> 3.11.1
2018-04-21 11:29:29 +01:00
Jörg Thalheim cba6e774fd
Merge pull request #39258 from r-ryantm/auto-update/debootstrap
debootstrap: 1.0.95 -> 1.0.97
2018-04-21 10:56:01 +01:00
Jörg Thalheim a769ffc85c
Merge pull request #39056 from mt-caret/jumanpp
jumanpp: init at 1.02
2018-04-21 10:27:57 +01:00
Jörg Thalheim 9d7959de31
Merge pull request #35248 from telent/cross-monit
monit: cross-compile, and make openssl optional
2018-04-21 08:56:12 +01:00
Frederik Rietdijk ddcdc0f10a asciidoctor: remove mathematical from wrapper, fixes #39098
because it does not exist in the original derivation, breaking
installation with `nix-env`. Should asciidoctor-mathematical exist?
2018-04-21 09:37:35 +02:00
Francesco Gazzetta 780558a7ea bash-supergenpass: 2012-11-02 -> 2018-04-18 2018-04-20 17:59:56 -05:00
Eelco Dolstra 03b36522e7
nix: 2.0 -> 2.0.1 2018-04-20 23:37:18 +02:00
Peter Simons 955a615fc1
Merge pull request #39280 from r-ryantm/auto-update/asymptote
asymptote: 2.42 -> 2.44
2018-04-20 22:01:43 +02:00
R. RyanTM 475e2dd2c4 asymptote: 2.42 -> 2.44
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.

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

These checks were done:

- built on NixOS
- ran ‘/nix/store/cxi50l6jrwac932swm8pfd2zb1pm9g4b-asymptote-2.44/bin/asy -h’ got 0 exit code
- ran ‘/nix/store/cxi50l6jrwac932swm8pfd2zb1pm9g4b-asymptote-2.44/bin/asy --help’ got 0 exit code
- found 2.44 with grep in /nix/store/cxi50l6jrwac932swm8pfd2zb1pm9g4b-asymptote-2.44
- directory tree listing: https://gist.github.com/f39c5dba52ed8849c1eb79ba04db4f1d
2018-04-20 12:43:47 -07:00
Robert Schütz e59eb49a0a
simp_le: drop upper bound of acme requirement (#39263) 2018-04-20 19:40:38 +02:00