Commit graph

118349 commits

Author SHA1 Message Date
Nikolay Amiantov 38b94d1f1f wt: 3.3.6 -> 4.0.0
Fix build with new Boost.
2017-10-19 17:14:20 +03:00
Frederik Rietdijk 52350b5261 Merge remote-tracking branch 'upstream/master' into HEAD 2017-10-19 15:50:14 +02:00
Frederik Rietdijk d854b3df2c Merge pull request #30503 from guibou/guibou_vfx_pkgs
Many packages used in computer animation industry
2017-10-19 15:38:56 +02:00
Nikolay Amiantov 0d5ff53a15 bazel_0_4: build on Darwin 2017-10-19 16:38:06 +03:00
Tim Steinbach f11948d31e Merge pull request #30579 from NeQuissimus/openjdk8u152
openjdk: 8u144 -> 8u152
2017-10-19 09:22:26 -04:00
Frederik Rietdijk 5c11622348 python.pkgs.powerline: remove vcs clients from propagatedBuildInputs 2017-10-19 14:59:26 +02:00
Tim Steinbach c8a7124c24 Merge pull request #30560 from casey/alacritty-update
alacritty: unstable 2017-09-02 -> 2017-10-17
2017-10-19 08:55:06 -04:00
Tim Steinbach 1c71b0ef31
openjdk: 8u144 -> 8u152 2017-10-19 08:39:01 -04:00
Thomas Tuegel f7de0da188
Merge branch 'pull/30305'
plasma5: 5.10.5 -> 5.11.1
sddm: 0.15.0 -> 0.16.0
2017-10-19 07:18:36 -05:00
Thomas Tuegel dae260034c
nixos/sddm: delete QML cache
Prior to Qt 5.9.2, there is a QML cache invalidation bug which causes SDDM to
segfault when upgrading Plasma.

See also: https://bugreports.qt.io/browse/QTBUG-62302
2017-10-19 07:09:01 -05:00
Thomas Tuegel ef4a6bd181
sddm: remove HiDPI patch
Disabling HiDPI support seemed to resolve a segfault at SDDM startup, but that
was a red herring. The problem actually resulted from a QML cache invalidation
bug. It should be safe to enable HiDPI support again.
2017-10-19 07:07:24 -05:00
Tim Steinbach 0b409b37d4
linux-copperhead: 4.13.7.a -> 4.13.8.a 2017-10-19 08:02:26 -04:00
Thomas Tuegel 0cc2171910
grantlee5: Fix debug build 2017-10-19 06:52:56 -05:00
Tim Steinbach 606487e19c Merge pull request #30522 from NeQuissimus/docker_17_10
docker: add 17.10.0-ce
2017-10-19 07:39:50 -04:00
Jörg Thalheim 6f9c76662b Merge pull request #30572 from flokli/twilio
twilio: init at 6.8.0
2017-10-19 11:29:20 +01:00
Nikolay Amiantov 94dc37d622 cntk: init at 2.2 2017-10-19 13:24:24 +03:00
Nikolay Amiantov cf2cc8b1d3 Merge pull request #30434 from abbradar/tensorflow
Build Tensorflow from source
2017-10-19 13:24:09 +03:00
Nikolay Amiantov fe153d73ce tensorflow: 1.3.0 ->1.3.1
Build from source.

It's implemented as a two-staged Bazel build (see also
546b4aec776b3ea676bb4d58d89751919ce4f1ef).
2017-10-19 13:19:11 +03:00
Nikolay Amiantov e3afbd6d26 bazel_0_4: set absolute path to /usr/bin/env
Also cleanup TMPDIR.
2017-10-19 13:19:11 +03:00
Nikolay Amiantov ba9cde1dd5 bazel_0_4: add optional Nix-specific hacks
* Skip verifying checksums for already fetched packages.
  Needed for two-staged building in Nix:
    1. Build a fixed derivation with `bazel fetch` (filtered out of non-reproducable bits).
    2. Build an actual derivation which uses fetched dependencies (skipping
       checksums needed here because they depend on the build directory).
* Don't clean environment variables for children processes.
  Needed for Nix compiler wrappers.
2017-10-19 13:19:11 +03:00
Nikolay Amiantov 15bfc8c12a Merge pull request #30433 from abbradar/cudatoolkit
CUDA-related updates and cleanups
2017-10-19 13:18:43 +03:00
Nikolay Amiantov 1360c356e3 driversi686Linux: init
This is added so that Hydra would build several drivers-related packages for i686.

Closes #30455.
2017-10-19 13:12:28 +03:00
Nikolay Amiantov 59f51eba29 opencv3: use older cudatoolkit 2017-10-19 12:47:56 +03:00
Nikolay Amiantov 22b582821d blender: fix build with new cudatoolkit 2017-10-19 12:47:56 +03:00
Nikolay Amiantov b317d7cfd4 opensubdiv: 3.2.0 -> 3.3.0
Fix build with new CUDA toolkit.
2017-10-19 12:47:56 +03:00
Nikolay Amiantov 771e403786 python.pkgs.Theano: merge CUDA and non-CUDA versions 2017-10-19 12:47:30 +03:00
Nikolay Amiantov efd2444de5 python.pkgs.libgpuarray: -9998.0 -> 0.6.9 2017-10-19 12:47:30 +03:00
Nikolay Amiantov 50a223b144 clblas: 20160505 -> 2.12 2017-10-19 12:47:30 +03:00
Nikolay Amiantov 57f82de364 caffe: 1.0-rc5 -> 1.0
Fix build with cudatoolkit9.
2017-10-19 12:47:30 +03:00
Nikolay Amiantov 378bfba023 treewide: use default compiler for cuda 2017-10-19 12:47:30 +03:00
Nikolay Amiantov 85d3c00dce treewise: respect config.cudaSupport in packages 2017-10-19 12:47:30 +03:00
Nikolay Amiantov 6309e5fa01 cudnn: refactor to use shared derivation
Also return 8.0-6.0 version for TensorFlow.
2017-10-19 12:47:30 +03:00
Nikolay Amiantov ce9059a120 cudnn_cudatoolkit9: init at 7.0
Make it the default.
2017-10-19 12:47:30 +03:00
Nikolay Amiantov 7cf6010fd3 cudatoolkit: use recommended gcc by default
This way one may build packages requiring old CUDA Toolkit with usual stdenv;
only bits which are compiled with NVCC would use older GCC.
2017-10-19 12:47:30 +03:00
Nikolay Amiantov fe7c7a852d cudatoolkit9: init at 9.0.176
Make CUDA Toolkit 9 the default choice.
2017-10-19 12:47:30 +03:00
Nikolay Amiantov 0bc4216bf0 Merge branch 'staging' 2017-10-19 12:46:38 +03:00
Vladimír Čunát c0e00efdae
knot-dns: fix kdig +tls broken in 2.6.0 2017-10-19 11:18:20 +02:00
Joerg Thalheim 65256b7f26 wireguard: 0.0.20171011 -> 0.0.20171017 2017-10-19 09:40:51 +01:00
Florian Klink 2856891562 twilio: init at 6.8.0 2017-10-19 09:56:47 +02:00
Kevin Quick a1afec9c14 maintainers: add Kevin Quick 2017-10-19 08:18:55 +02:00
Dmitry Kalinkin 19efa65f59
texlive: fix after dependency update 2017-10-19 00:25:24 -04:00
Michael Peyton Jones 281bf1dded tzupdate service: init 2017-10-19 05:15:32 +01:00
Bastian Köcher 7132cbd598
qt5: Disable gold linker on Linux as it generates duplicate symbols
Signed-off-by: adisbladis <adis@blad.is>
2017-10-19 11:09:25 +08:00
adisbladis 0d45be3d91
sddm: 0.15.0 -> 0.16.0 2017-10-19 11:09:24 +08:00
adisbladis f8368f68ea
plasma5.plasma-vault: init at 5.11.1 2017-10-19 11:09:23 +08:00
adisbladis 84847258bb
plasma: 5.10.5 -> 5.11.1 2017-10-19 11:09:22 +08:00
Casey Rodarmor a441af368a alacritty: unstable 2017-09-02 -> 2017-10-17 2017-10-18 20:05:04 -07:00
aszlig 27b7192726
digikam: 5.4.0 -> 5.7.0
The build for the version 5.4.0 of digiKam has been broken at the time
prior to this commit, which is the main reason for this update as I
don't think it makes sense to fix the build for 5.4.0 when we're going
to update it anyway.

A lot has changed upstream between version 5.4.0 and 5.7.0 and it's too
much to be summarized here, so here are the URLs to the upstream
announcements:

 * https://www.digikam.org/news/2017-03-14_digiKam_5.5.0_is_released/
 * https://www.digikam.org/news/2017-06-21-5.6.0-release-announcement/
 * https://www.digikam.org/news/2017-09-11-5.7.0_release_announcement/

On the packaging side, we now no longer have the patch that disables
-fno-operator-names because the build runs fine without that patch
(which didn't even apply but I didn't check why) and IMO it doesn't make
sense to rebase that patch for no reason.

Additionally, there were build time dependencies lurking around in
propagatedBuildInputs, which is kinda pointless and the application just
runs fine if those dependencies are listed in buildInputs.

While looking for clues about why that might be necessary I haven't
found any comment about it in the source nor a clarification within the
message of the commit where this has been introduced.

The commit in question is be7b7d908f.

Apart from these changes, the rest is just adding a few dependencies
(kcalcore, libksane, mesa and pcre) to get less errors during
cmakeConfigurePhase.

I've tested digiKam by playing around within a VM using photos I
netcat'ed into it and it works so far. The VM was built using:

nix-build nixos --arg configuration '{ pkgs, ... }: {
  imports = [ ./nixos/tests/common/user-account.nix ];
  environment.systemPackages = [ pkgs.digikam ];
  services.xserver.enable = true;
  services.xserver.displayManager.sddm.enable = true;
  services.xserver.desktopManager.plasma5.enable = true;
  services.xserver.desktopManager.default = "plasma5";
  virtualisation.memorySize = 1024;
}' -A vm

What I didn't test however was whether importing from a camera would
work (as I don't have one), but aside from that, the application seems
to run fine compared to the fact that it didn't even build until now :-)

Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Cc: @the-kenny, @urkud, @viric, @cillianderoiste, @ttuegel
Cc: @jraygauthier, @fkz, @sh01, @lsix
2017-10-19 04:42:53 +02:00
Michael Peyton Jones 922bd8182e tzupdate: init at 1.2.0 2017-10-19 03:19:14 +01:00
aszlig a8989e6bb0
libqtav: unstable-2017-03-30 -> 1.12.0
This was actually already mentioned in the comment above version:

  Awaiting upcoming `v1.12.0` release. `v1.11.0` is not supporting
  cmake which is the the reason behind taking an unstable git rev.

So version 1.12.0 has been released in the meantime and it's also needed
by the latest version of digiKam, which is the only package in nixpkgs
that depends on libqtav.

As we're going to bump digiKam, I think bumping this is safe as in the
worst case we can only make things broken which are already broken
(digiKam currently doesn't build).

The fixes for the CMakeLists.txt are now also no longer needed, so we
can safely drop them as well.

Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Cc: @jraygauthier
2017-10-19 04:07:30 +02:00