Commit graph

9534 commits

Author SHA1 Message Date
Ambroz Bizjak 5bec9dc65b virtualbox: 5.2.28 -> 6.0.6
Quite some fixing was needed to get this to work.

Changes in VirtualBox and additions:

- VirtualBox is no longer officially supported on 32-bit hosts so i686-linux is removed from platforms
  for VirtualBox and the extension pack. 32-bit additions still work.

- There was a refactoring of kernel module makefiles and two resulting bugs affected us which had to be patched.
  These bugs were reported to the bug tracker (see comments near patches).

- The Qt5X11Extras makefile patch broke. Fixed it to apply again, making the libraries logic simpler
  and more correct (it just uses a different base path instead of always linking to Qt5X11Extras).

- Added a patch to remove "test1" and "test2" kernel messages due to forgotten debugging code.

- virtualbox-host NixOS module: the VirtualBoxVM executable should be setuid not VirtualBox.
  This matches how the official installer sets it up.

- Additions: replaced a for loop for installing kernel modules with just a "make install",
  which seems to work without any of the things done in the previous code.

- Additions: The package defined buildCommand which resulted in phases not running, including RUNPATH
  stripping in fixupPhase, and installPhase was defined which was not even run. Fixed this by
  refactoring using phases. Had to set dontStrip otherwise binaries were broken by stripping.
  The libdbus path had to be added later in fixupPhase because it is used via dlopen not directly linked.

- Additions: Added zlib and libc to patchelf, otherwise runtime library errors result from some binaries.
  For some reason the missing libc only manifested itself for mount.vboxsf when included in the initrd.

Changes in nixos/tests/virtualbox:

- Update the simple-gui test to send the right keys to start the VM. With VirtualBox 5
  it was enough to just send "return", but with 6 the Tools thing may be selected by
  default. Send "home" to reliably select Tools, "down" to move to the VM and "return"
  to start it.

- Disable the VirtualBox UART by default because it causes a crash due to a regression
  in VirtualBox (specific to software virtualization and serial port usage). It can
  still be enabled using an option but there is an assert that KVM nested virtualization
  is enabled, which works around the problem (see below).

- Add an option to enable nested KVM virtualization, allowing VirtualBox to use hardware
  virtualization. This works around the UART problem and also allows using 64-bit
  guests, but requires a kernel module parameter.

- Add an option to run 64-bit guests. Tested that the tests pass with that. As mentioned
  this requires KVM nested virtualization.
2019-05-09 23:36:57 +02:00
worldofpeace 974cbe2acc
Merge pull request #61174 from worldofpeace/bump-upower
upower: 0.99.9 -> 0.99.10
2019-05-09 16:10:28 -04:00
Renaud 1cd3efc07c
Merge pull request #60898 from lopsided98/rpi-firmware-update
raspberrypifw: 1.20181112 -> 1.20190401
2019-05-09 17:35:59 +02:00
worldofpeace b39324bf52 upower: 0.99.9 -> 0.99.10
Using placeholder and drop the NIX_CFLAGS_LINK.

https://gitlab.freedesktop.org/upower/upower/blob/UPOWER_0_99_10/NEWS
2019-05-08 23:06:00 -04:00
Graham Christensen 52ce589968
Merge pull request #61138 from rnhmjoj/collide
Avoid collisions between essential packages
2019-05-08 11:42:19 -04:00
Tim Steinbach ec75f9c2c8
linux: 5.0.13 -> 5.0.14 2019-05-08 10:13:43 -04:00
Tim Steinbach de8a2720e2
linux: 4.9.173 -> 4.9.174 2019-05-08 10:13:43 -04:00
Tim Steinbach f531f08f0c
linux: 4.19.40 -> 4.19.41 2019-05-08 10:13:42 -04:00
Tim Steinbach 103a7daa53
linux: 4.14.116 -> 4.14.117 2019-05-08 10:13:42 -04:00
rnhmjoj 87bfe6e115
procps: lower priority to solve collisions with coreutils 2019-05-08 16:00:18 +02:00
rnhmjoj d16a24379a
systemd: lower priority to solve collisions with openresolv 2019-05-08 13:21:04 +02:00
worldofpeace e74d8878fe
Merge pull request #60979 from CrazedProgrammer/update-compsize
compsize: 2018-04-07 -> 1.3
2019-05-07 17:50:45 -04:00
Renaud 2fb1b3156f
Merge pull request #60932 from c0bw3b/patches-cleanup
[treewide] delete (some) unused patches
2019-05-07 23:34:04 +02:00
Joachim Fasting 87bc514620
hardened-config: enable the SafeSetID LSM
The purpose of this LSM is to allow processes to drop to a less privileged
user id without having to grant them full CAP_SETUID (or use file caps).

The LSM allows configuring a whitelist policy of permitted from:to uid
transitions.  The policy is enforced upon calls to setuid(2) and related
syscalls.

Policies are configured through securityfs by writing to
- safesetid/add_whitelist_policy ; and
- safesetid/flush_whitelist_policies

A process attempting a transition not permitted by current policy is killed
(to avoid accidentally running with higher privileges than intended).

A uid that has a configured policy is prevented from obtaining auxiliary
setuid privileges (e.g., setting up user namespaces).

See also: https://www.kernel.org/doc/html/latest/admin-guide/LSM/SafeSetID.html
2019-05-07 13:39:24 +02:00
Renaud 7085da0cef
Merge pull request #60870 from dkudriavtsev/patch-1
miraclecast: 20170427 -> 20190403
2019-05-07 13:37:39 +02:00
Jörg Thalheim 2146e1023a
Merge pull request #61076 from Mic92/linux-fpu
linux_5_0: restore __kernel_fpu_{begin,restore}
2019-05-07 10:35:04 +01:00
Matthew Bauer 69cf07ec0f
Merge pull request #60828 from matthewbauer/mark-bad-platforms
Mark some bad platforms
2019-05-06 15:54:08 -04:00
Jörg Thalheim 7b77c27caa
linux_5_0: restore __kernel_fpu_{begin,restore}
In 5.0er these function were removed from the public interface also zfs needs
them for AVX/AES-NI support. Without this patch for example throughput on a
encrypted zfs dataset drops to 200 MB/s from 1.2 GB/s. These functions were
removed as their was no user within the linux kernel tree itself.
2019-05-06 14:14:40 +01:00
Austin Seipp 0a4cd28f84
linuxPackages.bcc: 0.8.0 -> 0.9.0
Requires a minor tweak to the deadlock detector patch (the file was
renamed in the upstream repo).

bcc now also wants a copy of libbpf, which it doesn't have in the source
release tarball. Clone a copy from GiHub that's synchronized with the
release, and put it in place.

Tested on Linux 5.1 (with bpftrace as well).

Signed-off-by: Austin Seipp <aseipp@pobox.com>
2019-05-06 01:42:02 -05:00
Austin Seipp 181e971755
linux: add 5.1 release
Signed-off-by: Austin Seipp <aseipp@pobox.com>
2019-05-06 00:39:22 -05:00
José Romildo Malaquias 1c137e36ea
Merge pull request #59378 from romildo/upd.deepin.deepin-anything
deepin.deepin-anything: init at 0.0.7
2019-05-05 15:05:15 -03:00
José Romildo Malaquias 868ed9f2c4 linuxPackages.deepin-anything: init at 0.0.7 2019-05-05 13:26:42 -03:00
Renaud 67b263f6ac
Merge pull request #60975 from c0bw3b/pkg/mstpd
mstpd: 0.0.5.20171113 -> 0.0.7
2019-05-05 18:18:35 +02:00
Tim Steinbach 9d6aef817b
linux: 5.0.12 -> 5.0.13 2019-05-05 11:16:44 -04:00
Tim Steinbach e867007dc8
linux: 4.19.39 -> 4.19.40 2019-05-05 11:16:17 -04:00
CrazedProgrammer baf2d552e8 compsize: 2018-04-07 -> 1.3 2019-05-05 12:03:33 +02:00
Renaud 25e0560958
mstpd: 0.0.5.20171113 -> 0.0.7 2019-05-05 11:24:34 +02:00
c0bw3b 9cb260d091 [treewide] delete unused patches 2019-05-04 19:52:24 +02:00
Tim Steinbach 59e9fb1d52
linux: 5.0.11 -> 5.0.12 2019-05-04 10:26:55 -04:00
Tim Steinbach 5ee553b280
linux: 4.9.172 -> 4.9.173 2019-05-04 10:26:40 -04:00
Tim Steinbach 7d0a77cd36
linux: 4.19.38 -> 4.19.39 2019-05-04 10:25:28 -04:00
Tim Steinbach a03324e9ba
linux: 4.14.115 -> 4.14.116 2019-05-04 10:25:01 -04:00
Ben Wolsieffer a68213ae8a raspberrypifw: 1.20181112 -> 1.20190401 2019-05-03 18:12:13 -04:00
Austin Seipp f60936d14d
Merge pull request #60121 from eadwu/nvidia_x11_beta/430.09
nvidia_x11_beta: stable -> 430.09
2019-05-03 15:33:04 -05:00
Austin Seipp c8cb015ff6
linuxPackages.perf: add libopcodes as a buildInput
Newer versions of perf in Linux 5.1+ support disassembling and
annotating eBPF programs inside the kernel. In order to do this, it uses
libbfd's support for bpf disassembly. There are two parts: libopcodes
and libbfd.

The 'perf' build system seems to expect libopcodes/libbfd to go "hand in
hand" -- always together, if one or the other is installed. If the build
system detects libbfd is available, then an import of <dis-asm.h> is
performed, but this fails since it wasn't in the buildInput. Fixing this
should be an easy, backwards-compatible change.

Fixes #60891, allowing linuxPackages_testing.perf to build again
(currently kernel version 5.1.0-rc7).

Signed-off-by: Austin Seipp <aseipp@pobox.com>
2019-05-03 15:10:46 -05:00
Austin Seipp f40a559cbb
bpftrace: nuke some unneeded files from $out
Signed-off-by: Austin Seipp <aseipp@pobox.com>
2019-05-03 12:25:59 -05:00
Austin Seipp 89d5bfc2db
Merge pull request #60844 from thoughtpolice/nixpkgs/bpftrace-update
bpftrace: unstable-2018-10-27 -> 0.9
2019-05-03 12:09:57 -05:00
Austin Seipp 241063ca84
bpftrace: unstable-2018-10-27 -> 0.9
Update bpftrace to the latest pre-release, with a real version number.

The most notable change now is that bpftrace can use a stable version of
the 'bcc' toolchain in order to build, meaning no more hacks are needed
to clone the source code and fix up the build system, etc. This
simplifies things greatly and removes the old bcc-source patch.

Similarly, we can remove our custom gtests patch (which disabled the
build) by just passing -DBUILD_TESTING=FALSE when running cmake. This
was also added upstream recently.

However, something does still need to be fixed, at a cost: bpftrace
requires the kernel -dev package because it wants both objects and
include directories (some files are only shipped in one or the other).
Therefore, we remove the dependency on linuxHeaders and instead use
kernel.dev as the sole input to the build.

This is both a positive and a negative: the positive is that tools work
without annoying fatal errors, and that the bpf toolchain is
synchronized to the linuxPackages.kernel derivation it was built
against. The downside is that the .dev expression is much heavier as a
dependency, so bpftrace is now closer to 700mb in closure size. (This
especially hurts across kernel upgrades requiring a whole new rebuild,
especially if you have existing nixos generations that won't GC, etc.)

We probably want to slim this down substantially in the future (and
there may be a few ways to do that), but as this will probably also
touch bcc, and as a first cut of the pre-releases, this is probably fine
while we work out other kinks.

Signed-off-by: Austin Seipp <aseipp@pobox.com>
2019-05-03 11:32:58 -05:00
Dmitry Kudriavtsev 6b5848e26b
miraclecast: 20170427 -> 20190403 2019-05-03 09:21:52 -07:00
Renaud 45b7685314
Merge pull request #60800 from r-ryantm/auto-update/sysstat
sysstat: 12.1.3 -> 12.1.4
2019-05-03 11:36:28 +02:00
Leah Neukirchen 23336fb44a extrace: init at 0.7 2019-05-03 18:19:57 +09:00
Matthew Bauer b7950c560a kexectools: mark bad platforms 2019-05-02 21:30:32 -04:00
R. RyanTM a0e953768a sysstat: 12.1.3 -> 12.1.4
Semi-automatic update generated by
https://github.com/ryantm/nixpkgs-update tools. This update was made
based on information from
https://repology.org/metapackage/sysstat/versions
2019-05-02 13:22:12 -07:00
Tim Steinbach 6494ad9996
linux: 5.0.10 -> 5.0.11 2019-05-02 13:57:46 -04:00
Tim Steinbach 9d7638371f
linux: 4.9.171 -> 4.9.172 2019-05-02 13:57:46 -04:00
Tim Steinbach e0bf73dbde
linux: 4.19.37 -> 4.19.38 2019-05-02 13:57:45 -04:00
Tim Steinbach 5d03bfd653
linux: 4.14.114 -> 4.14.115 2019-05-02 13:57:45 -04:00
R. RyanTM 36f45dc7d3 mbpfan: 2.1.0 -> 2.1.1
Semi-automatic update generated by
https://github.com/ryantm/nixpkgs-update tools. This update was made
based on information from
https://repology.org/metapackage/mbpfan/versions
2019-05-01 03:55:14 -07:00
R. RyanTM da627dec9f btfs: 2.18 -> 2.19 (#60478)
* btfs: 2.18 -> 2.19

Semi-automatic update generated by
https://github.com/ryantm/nixpkgs-update tools. This update was made
based on information from
https://repology.org/metapackage/btfs/versions

* btfs: refactor
2019-05-01 00:22:15 +02:00
Frederik Rietdijk fd2bd6e433
Merge staging-next into master 2019-04-30 15:50:24 +02:00