linux-3.0: upgrade to 3.0.52
linux-3.2: upgrade to 3.2.34
linux-3.4: upgrade to 3.4.19
linux-3.6: upgrade to 3.6.7
iwlwifi-6000g2a-ucode: update to version 18.168.6.1
add package: neoload-4.0.4
neoload: fix evaluation of tarball job
Fix xf86-video-sis
Merge pull request #189 from aforemny/xf86-video-sis

Fix xf86-video-sis
xf86 video openchrome: fixing the build, changing overrides.
chromium: Fix omahaproxy URL in updater.

Omahaproxy got an overhaul and thus doesn't give CSV output on the main URL
anymoare. We're switching to /all for now and may want to refine this to only
what we're exactly looking for, but for now it fixes the updater.

Signed-off-by: aszlig <aszlig@redmoonstudios.org>
chromium: Update channels to stable v23.0.1271.64.

This updates all release channels to the latest versions:

stable: 22.0.1229.94 -> 23.0.1271.64 (builds fine, tested)
beta: 23.0.1271.60 -> 24.0.1312.14 (builds fine, tested)
dev: 24.0.1312.2 -> 25.0.1323.1 (build failed, requires pciutils)

Signed-off-by: aszlig <aszlig@redmoonstudios.org>
chromium: Drop obsolete pre-v23 seccomp patch.

The patch is no longer needed, as we are now using the BPF seccomp sandbox.
Unfortunately this is not marked "adequately sandboxed" in chrome://sandbox, as
it awaits security review on http://crbug.com/26528.

Unfortunately this gets us into a position where we can't be sure if the sandbox
is working correctly, especially because the non-BPF seccomp sandbox has a bunch
of stability issues and is marked legacy. And we definitely don't want to add
support for the setuid sandbox, do we?

Signed-off-by: aszlig <aszlig@redmoonstudios.org>
chromium: Add dependency on pciutils for v25.

This fixes the build for latest development version 25.

Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Merge branch 'chromium-update'.

Was about to open a new pull request about how to proceed with the BPF seccomp
sandbox, but turns out that the Chromium security team not even has finished
reviewing the legacy sandbox (http://crbug.com/26528, next time look at the date
of the issue, shall we?), so it shouldn't make a big difference whether we
enable the old seccomp sandbox or the new BPF one.

Which of course won't make either of these options more secure and leaves us at
the same state we had before, just with chrome://sandbox stating "NOT adequately
sandboxed" which resembles the truth more closely.
smartmontools: update drivedb file to trunk revision 3605
androidenv: Remove examples directory

As discussed on nix-dev, it's better to use fetchurl to obtain the
source of the examples.
nix: Update to 1.2pre2980
fix sort in lists.nix
haskell-Boolean: update to version 0.1.1