This branch makes the manual config kernel a lot more space efficient by separating out the build and source trees (needed for out-of-tree modules) from the actual bzImage and in-tree modules.
Also some other small improvements along the way.
This makes it possible to still build out-of-tree modules without making a system using this kernel depend on the full source and build tree at runtime.
Note that references to the source tree are removed from kernel modules after build.
Ideally, this would be accomplished by modifying the Makefile that puts the reference there in the first place, but I haven't tracked that down yet.
Before, only the first output (and not even that when accessed through 'all' or its corresponding attribtue) had meta information and the relevant passthru attributes.
This doesn't change stdenv's hash and the tarball still builds, I'm pretty sure this is safe for master.
Outrageous! They fixed the tarball by including the missing file.
Well, at least we now don't have that much cruft laying around and can remove
that rather long patch.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
This update involves a bunch of fixes on our side:
Update the Gentoo patch to 3.14.1 from http://bit.ly/ZG8OK5 and drop the older
one from http://bit.ly/15mN0X1 (for 3.12.5).
While checking the old patch from Gentoo, I discovered, that the patch added in
revision 06c543b11d wasn't the original one in the
Gentoo repository.
Instead of doing the same again, we now patch up our specific modifications
using sed within the postPatch hook.
In addition to that, we now have another patch from RedHat/Fedora which syncs
the NSS PEM support repository with the latest upstream changes. Patch is coming
from the SRPM at http://koji.fedoraproject.org/koji/rpminfo?rpmID=3772072 and I
just stripped the "0001-" prefix from the filename.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
This patch is cherry-picked from VirtualBox Subversion, revision 44867.
It's rather small and only is in effect if kernel version is >= 3.9.0, so it
won't break existing kernels, so I'm adding it here despite we usually only care
about the latest stable upstream (kernel) versions.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
This adds a patch to support CONFIG_UIDGID_STRICT_TYPE_CHECKS being activated in
the kernel config (selected by CONFIG_USER_NS for example).
When this kernel option is enabled, current->cred->uid is a structure rather
than a simple integer type (uid_t and gid_t), so we need to check for that and
also pass the current user namespace where needed.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
The tarball for this version is missing the file VRDEVideoIn.h, which is added
through the missing_files_4.2.8.patch and extracted from Subversion, revision
44528.
Upstream changelog(s) can be found at the usual place:
https://www.virtualbox.org/wiki/Changelog
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
As timeconst.pl was replaced by a bc script in the merge window for kernel 3.9,
we also need bc during build time, for more information about the reasons,
please have a look at the following commit:
torvalds/linux@70730bca13
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
This was missing in the previous update as well, and no one seemed to notice it,
including myself? Anyway, it's now fixed.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
This gets rid of the patch for newer pulseaudio library versions.
In addition, we now have protobuf and pciutils in default dependencies, as those
are required (or better: optional, but recommended and thus activated by the
default gyp options) by versions >= 25.
Also, we now no longer depend on libpng, but I'm not dropping this, as we want
to get back to libpng from nixpkgs again 'real soon'.
The stack-protector flag is now disabled by default accross all versions, and
probably didn't hurt back in version 24, but at least we're now no longer add it
dependant on a particular version.
And those pesky post/onlyXX version booleans are now pre/postXX, to ensure
better clarity.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
So, after searching for days in the wrong spot, eventually discovering that
postPatch isn't run on Hydra, we're now set to move forward to version 25, YAY!
Build has been tested locally (not that this would mean anything for Hydra, as
we've seen) and the output has been actively used for browsing by me :-)
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
This is needed in order to ensure that the postPatch hook is executed, which is
not when the patches list is empty.
It is fixed by 82f94df719 in stdenv-updates.
So as soon as the branch gets merged, we can get rid of this hack as well.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
This reverts commit b7cbb4da11.
The main reason behind this - apart from looking ugly - is that it didn't really
solve anything, see:
http://hydra.nixos.org/build/4198299
So, we need a different and less hacky approach...
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
So, chromium 25 is now stable, so we really need to get the build fixed on Hydra
as soon as possible. And let's hope without nasty workarounds.
This commits updates dev and beta channels to version 26.0.1410.12, because
version 27.0.1423.0 seems to be unavailable right now. Build is running
successfully on my machine, and the browser works as well on the sites I usually
visit.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
I'm not sure whether this was by intention, but so far postPatch hooks were
silently skipped whenever the patches list was empty. This change could possibly
change the build results of the following packages:
* gcc
* cmake (264)
* systemtap
* quemu-kvm
These packages all have in common that they have a postPatch hook and the
patches list can be empty when certain conditions are met.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2.60 is the newest of the gtk2-compatible versions. (Transmission >=
2.61 requires gtk3.)
* Add inotify as input to not have transmission-daemon poll the torrent
auto-load directory.
* Add file as input to fix a small build time issue (non-fatal).
* Remove unneeded gtk configure flags (support is auto-detected).
* icon-theme.cache is only generated when building with gtk, so use
rm -f to not error out when building without gtk.
* Use gtk ? null instead of gtkClient flag because it is simpler.
Build and runtime tested with and without gtk support.
Test suite graphviz-testsuite: RUNNING...
This is the test suite for the graphviz library.
If any of these tests fail, please inform the maintainer,
including full output of this test suite.
======================================================================
Running test: "Printing and parsing of Attributes".
The most common source of errors in printing and parsing are for
Attributes.
+++ OK, passed 200 tests.
All tests for "Printing and parsing of Attributes" were successful!
======================================================================
Running test: "Printing generalised Dot code".
When generalising "DotGraph" values to other "DotRepr" values,
the generated Dot code should be identical.
+++ OK, passed 200 tests.
All tests for "Printing generalised Dot code" were successful!
======================================================================
Running test: "Printing and Parsing DotReprs".
The graphviz library should be able to parse back in its own
generated Dot code for any "DotRepr" instance
+++ OK, passed 200 tests.
+++ OK, passed 200 tests.
+++ OK, passed 200 tests.
All tests for "Printing and Parsing DotReprs" were successful!
======================================================================
Running test: "Pre-processing Dot code".
When parsing Dot code, some pre-processing is done to remove items
such as comments and to join together multi-line strings. This
test verifies that this pre-processing doesn't affect actual
Dot code by running the pre-processor on generated Dot code.
This test is not run on generalised Dot graphs as if it works for
normal dot graphs then it should also work for generalised ones.
+++ OK, passed 200 tests.
All tests for "Pre-processing Dot code" were successful!
======================================================================
Running test: "Augmenting FGL Graphs".
The various Graph to Graph functions in Data.GraphViz should
only _augment_ the graph labels and not change the graphs
themselves. This test compares the original graphs to these
augmented graphs and verifies that they are the same.
*** Failed! (after 1 test):
Exception:
Error running utility program: Error messages from neato:
-1:']'->[]
The tests for "Augmenting FGL Graphs" failed!
Not attempting any further tests.
Test suite graphviz-testsuite: FAIL
Test suite logged to: dist/test/graphviz-2999.16.0.0-graphviz-testsuite.log
0 of 1 test suites (0 of 1 test cases) passed.
Running 4 test suites...
Test suite doctests: RUNNING...
### Error in src/Data/Complex/Lens.hs:33: expression `let { a doctests: <stderr>: hPutChar: invalid argument (invalid character)
Test suite doctests: FAIL
Test suite logged to: dist/test/lens-3.8.7.3-doctests.log
Test suite hunit: RUNNING...
Test suite hunit: PASS
Test suite logged to: dist/test/lens-3.8.7.3-hunit.log
Test suite properties: RUNNING...
Test suite properties: PASS
Test suite logged to: dist/test/lens-3.8.7.3-properties.log
Test suite templates: RUNNING...
Test suite templates: PASS
Test suite logged to: dist/test/lens-3.8.7.3-templates.log
3 of 4 test suites (3 of 4 test cases) passed.
Test suite graphviz-testsuite: RUNNING...
This is the test suite for the graphviz library.
If any of these tests fail, please inform the maintainer,
including full output of this test suite.
======================================================================
Running test: "Printing and parsing of Attributes".
The most common source of errors in printing and parsing are for
Attributes.
+++ OK, passed 200 tests.
All tests for "Printing and parsing of Attributes" were successful!
======================================================================
Running test: "Printing generalised Dot code".
When generalising "DotGraph" values to other "DotRepr" values,
the generated Dot code should be identical.
+++ OK, passed 200 tests.
All tests for "Printing generalised Dot code" were successful!
======================================================================
Running test: "Printing and Parsing DotReprs".
The graphviz library should be able to parse back in its own
generated Dot code for any "DotRepr" instance
+++ OK, passed 200 tests.
+++ OK, passed 200 tests.
+++ OK, passed 200 tests.
All tests for "Printing and Parsing DotReprs" were successful!
======================================================================
Running test: "Pre-processing Dot code".
When parsing Dot code, some pre-processing is done to remove items
such as comments and to join together multi-line strings. This
test verifies that this pre-processing doesn't affect actual
Dot code by running the pre-processor on generated Dot code.
This test is not run on generalised Dot graphs as if it works for
normal dot graphs then it should also work for generalised ones.
+++ OK, passed 200 tests.
All tests for "Pre-processing Dot code" were successful!
======================================================================
Running test: "Augmenting FGL Graphs".
The various Graph to Graph functions in Data.GraphViz should
only _augment_ the graph labels and not change the graphs
themselves. This test compares the original graphs to these
augmented graphs and verifies that they are the same.
*** Failed! (after 1 test):
Exception:
Error running utility program: Error messages from neato:
-1:']'->[]
The tests for "Augmenting FGL Graphs" failed!
Not attempting any further tests.
Test suite graphviz-testsuite: FAIL
Test suite logged to: dist/test/graphviz-2999.16.0.0-graphviz-testsuite.log
0 of 1 test suites (0 of 1 test cases) passed.
Running 4 test suites...
Test suite doctests: RUNNING...
### Error in src/Data/Complex/Lens.hs:33: expression `let { a doctests: <stderr>: hPutChar: invalid argument (invalid character)
Test suite doctests: FAIL
Test suite logged to: dist/test/lens-3.8.7.3-doctests.log
Test suite hunit: RUNNING...
Test suite hunit: PASS
Test suite logged to: dist/test/lens-3.8.7.3-hunit.log
Test suite properties: RUNNING...
Test suite properties: PASS
Test suite logged to: dist/test/lens-3.8.7.3-properties.log
Test suite templates: RUNNING...
Test suite templates: PASS
Test suite logged to: dist/test/lens-3.8.7.3-templates.log
3 of 4 test suites (3 of 4 test cases) passed.
Test suite test: RUNNING...
test: SqlError {sqlState = "", sqlNativeError = -1, sqlErrorMsg = "could not connect to server: No such file or directory\n\tIs the server running locally and accepting\n\tconnections on Unix domain socket \"/tmp/.s.PGSQL.5432\"?\n"}
Test suite test: FAIL
Test suite logged to: dist/test/postgresql-simple-0.2.4.1-test.log
0 of 1 test suites (0 of 1 test cases) passed.
tests/Test.hs:3:8:
Could not find module `Happstack.Server.Tests'
Perhaps you meant
Happstack.Server.Types (from happstack-server-7.1.6)
Happstack.Server.Auth (from happstack-server-7.1.6)
Happstack.Server.Client (from happstack-server-7.1.6)
Use -v to see a list of the files searched for.
Running 1 test suites...
Test suite tests: RUNNING...
Tests for all distributions:
Tests for: BetaDistribution:
C.D.F. sanity: [OK, passed 100 tests]
CDF limit at +tests: <stdout>: commitBuffer: invalid argument (invalid character)
Test suite tests: FAIL
Test suite logged to: dist/test/statistics-0.10.2.0-tests.log
Test suite test: RUNNING...
test: SqlError {sqlState = "", sqlNativeError = -1, sqlErrorMsg = "could not connect to server: No such file or directory\n\tIs the server running locally and accepting\n\tconnections on Unix domain socket \"/tmp/.s.PGSQL.5432\"?\n"}
Test suite test: FAIL
Test suite logged to: dist/test/postgresql-simple-0.2.4.1-test.log
0 of 1 test suites (0 of 1 test cases) passed.
Test/Runner.hs:5:8:
Could not find module `Language.Haskell.Exts.Annotated'
Use -v to see a list of the files searched for.
Setup: Pattern match failure in do expression at Setup.hs:6:5-15
Running 1 test suites...
Test suite spec: RUNNING...
Sendfile
sendfile
spec: test/inputFile: openFd: does not exist (No such file or directory)
- sends an entire file FAILED [1]
spec: test/inputFile: openFd: does not exist (No such file or directory)
- sends a part of file FAILED [2]
spec: test/inputFile: openFd: does not exist (No such file or directory)
- terminates even if length is over
spec: test/inputFile: openFd: does not exist (No such file or directory)
- terminates even if offset is over
- terminates even if the file is truncated FAILED [3]
sendfileWithHeader
spec: test/inputFile: openFd: does not exist (No such file or directory)
- sends an header and an entire file FAILED [4]
spec: test/inputFile: openFd: does not exist (No such file or directory)
- sends an header and a part of file FAILED [5]
spec: test/inputFile: openFd: does not exist (No such file or directory)
- sends a large header and an entire file FAILED [6]
spec: test/inputFile: openFd: does not exist (No such file or directory)
- sends a large header and a part of file FAILED [7]
spec: test/inputFile: openFd: does not exist (No such file or directory)
- terminates even if length is over
spec: test/inputFile: openFd: does not exist (No such file or directory)
- terminates even if offset is over
- terminates even if the file is truncated FAILED [8]
1) Sendfile.sendfile sends an entire file FAILED (uncaught exception)
IOException (test/inputFile: openBinaryFile: does not exist (No such file or directory))
2) Sendfile.sendfile sends a part of file FAILED (uncaught exception)
IOException (test/inputFile: openBinaryFile: does not exist (No such file or directory))
3) Sendfile.sendfile terminates even if the file is truncated FAILED (uncaught exception)
IOException (test/inputFile: openBinaryFile: does not exist (No such file or directory))
4) Sendfile.sendfileWithHeader sends an header and an entire file FAILED (uncaught exception)
IOException (test/inputFile: openBinaryFile: does not exist (No such file or directory))
5) Sendfile.sendfileWithHeader sends an header and a part of file FAILED (uncaught exception)
IOException (test/inputFile: openBinaryFile: does not exist (No such file or directory))
6) Sendfile.sendfileWithHeader sends a large header and an entire file FAILED (uncaught exception)
IOException (test/inputFile: openBinaryFile: does not exist (No such file or directory))
7) Sendfile.sendfileWithHeader sends a large header and a part of file FAILED (uncaught exception)
IOException (test/inputFile: openBinaryFile: does not exist (No such file or directory))
8) Sendfile.sendfileWithHeader terminates even if the file is truncated FAILED (uncaught exception)
IOException (test/inputFile: openBinaryFile: does not exist (No such file or directory))
Running 1 test suites...
Test suite test-versions: RUNNING...
test-versions: test/queens-ghc-6.12.1.eventlog: openBinaryFile: does not exist (No such file or directory)
Test suite test-versions: FAIL
Test suite logged to: dist/test/ghc-events-0.4.2.0-test-versions.log
0 of 1 test suites (0 of 1 test cases) passed.
tests/Test.hs:3:8:
Could not find module `Happstack.Server.Tests'
Perhaps you meant
Happstack.Server.Types (from happstack-server-7.1.6)
Happstack.Server.Auth (from happstack-server-7.1.6)
Happstack.Server.Client (from happstack-server-7.1.6)
Use -v to see a list of the files searched for.
Running 1 test suites...
Test suite tests: RUNNING...
Tests for all distributions:
Tests for: BetaDistribution:
C.D.F. sanity: [OK, passed 100 tests]
CDF limit at +tests: <stdout>: commitBuffer: invalid argument (invalid character)
Test suite tests: FAIL
Test suite logged to: dist/test/statistics-0.10.2.0-tests.log
In the master branch, doCheck defaults to 'false', which means that no package
will change its hash unless its doCheck field is set to 'true' explicitly. In
the stdenv-updates branch, however, all Haskell packages have a default setting
of 'doCheck=true'. Once that branch has been merged, filtering doCheck is no
longer necessary.
Test/Runner.hs:5:8:
Could not find module `Language.Haskell.Exts.Annotated'
Use -v to see a list of the files searched for.
Setup: Pattern match failure in do expression at Setup.hs:6:5-15
Running 1 test suites...
Test suite spec: RUNNING...
Sendfile
sendfile
spec: test/inputFile: openFd: does not exist (No such file or directory)
- sends an entire file FAILED [1]
spec: test/inputFile: openFd: does not exist (No such file or directory)
- sends a part of file FAILED [2]
spec: test/inputFile: openFd: does not exist (No such file or directory)
- terminates even if length is over
spec: test/inputFile: openFd: does not exist (No such file or directory)
- terminates even if offset is over
- terminates even if the file is truncated FAILED [3]
sendfileWithHeader
spec: test/inputFile: openFd: does not exist (No such file or directory)
- sends an header and an entire file FAILED [4]
spec: test/inputFile: openFd: does not exist (No such file or directory)
- sends an header and a part of file FAILED [5]
spec: test/inputFile: openFd: does not exist (No such file or directory)
- sends a large header and an entire file FAILED [6]
spec: test/inputFile: openFd: does not exist (No such file or directory)
- sends a large header and a part of file FAILED [7]
spec: test/inputFile: openFd: does not exist (No such file or directory)
- terminates even if length is over
spec: test/inputFile: openFd: does not exist (No such file or directory)
- terminates even if offset is over
- terminates even if the file is truncated FAILED [8]
1) Sendfile.sendfile sends an entire file FAILED (uncaught exception)
IOException (test/inputFile: openBinaryFile: does not exist (No such file or directory))
2) Sendfile.sendfile sends a part of file FAILED (uncaught exception)
IOException (test/inputFile: openBinaryFile: does not exist (No such file or directory))
3) Sendfile.sendfile terminates even if the file is truncated FAILED (uncaught exception)
IOException (test/inputFile: openBinaryFile: does not exist (No such file or directory))
4) Sendfile.sendfileWithHeader sends an header and an entire file FAILED (uncaught exception)
IOException (test/inputFile: openBinaryFile: does not exist (No such file or directory))
5) Sendfile.sendfileWithHeader sends an header and a part of file FAILED (uncaught exception)
IOException (test/inputFile: openBinaryFile: does not exist (No such file or directory))
6) Sendfile.sendfileWithHeader sends a large header and an entire file FAILED (uncaught exception)
IOException (test/inputFile: openBinaryFile: does not exist (No such file or directory))
7) Sendfile.sendfileWithHeader sends a large header and a part of file FAILED (uncaught exception)
IOException (test/inputFile: openBinaryFile: does not exist (No such file or directory))
8) Sendfile.sendfileWithHeader terminates even if the file is truncated FAILED (uncaught exception)
IOException (test/inputFile: openBinaryFile: does not exist (No such file or directory))
Running 1 test suites...
Test suite test-versions: RUNNING...
test-versions: test/queens-ghc-6.12.1.eventlog: openBinaryFile: does not exist (No such file or directory)
Test suite test-versions: FAIL
Test suite logged to: dist/test/ghc-events-0.4.2.0-test-versions.log
0 of 1 test suites (0 of 1 test cases) passed.
my-env/default.nix lists an example on how to create an SDL environment
that can be installed with "nix-env -i sdl-env". That is actually wrong
and will not work. The correct command is "nix-env -i env-sdl".
Conflicts:
pkgs/applications/networking/browsers/chromium/default.nix
pkgs/top-level/all-packages.nix
Merge conflicts seemed trivial, but a look from viric and aszlig would be nice.
