Quite a mess but at least the mdraid tests succeed now. However, the
lvm2 tests are still failing, so we need to bring back a few more old
crap :-(
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
I'm really not sure whether these tests are actually run upstream,
because there are quite a few oddities which either are my fault by just
missing something important or upstream really doesn't bother to run
those tests.
One example of this are testDiskChunk1 and testDiskChunk2, which create
two non-existing partitions and tries to allocate them. Now, in
allocatePartitions(), the partedPartition attributes are reset to None
and shortly afterwards a for loop is expecting it to be NOT None.
So, for now I'm disabling these tests and will see if we stumble on them
during work on nixpart 1.0, so we're really sure whether it's my fault
or a real bug in blivet.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
We don't want Hydra to even try and build this, because we're going to
fill in the right sha256 as soon as the the new nixpart version is
released.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Put a copy of old version 0.17 expression into 0.17.nix and update the
pointers from nixpart0 accordingly.
This also means, that plain nixpart is now way more broken than
nixpart0 (we might want to temporarily fix 0.4 anyway).
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Update the nixpart0 pointer to point to this version, because we're
going to update blivet as well and NixOps still points to nixpart0.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
In order to properly run tests, we need to fix the unicode tests and
after some search, I have found that Ludo (who is also the <nixpkgs>
maintainer of parted) already reported this upstream and also provided a
solution:
http://lists.gnu.org/archive/html/bug-parted/2014-08/msg00003.html
I'm updating parted to 3.2, because the latest blivet implementation
relies on it for device geometry calculations.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Git commit ids shouldn't be used as version numbers in nixpkgs:
* they don't increase monotonically
* they don't always start with a digit, causing nix to not parse them as
version numbers, and instead sees them as part of the package name,
causing the package to (seemingly) conflict with itself upon upgrade.
And use fetchzip instead of fetchurl towards github.com to not let this
happen again. (fetchzip checks the hash on the *extracted* archive, so
changes in compression algo etc. doesn't change the hash.)
Currently some plugins use "vim-" prefix, some use "-vim" suffix and
some have no prefix or suffix at all.
I chose "vimplugin-" prefix to match the attribute path: vimPlugins.*
We don't really need this anymore, except that our docs say that you
can put firmware in /root/test-firmware, which doesn't work via
/sys/module/firmware_class/parameters/path.
Test suite hspec: RUNNING...
hspec: test/gibiansky/tests/: getDirectoryContents: does not exist (No such file or directory)
Test suite hspec: FAIL
Test suite logged to: dist/test/hindent-3.9-hspec.log
0 of 1 test suites (0 of 1 test cases) passed.
