| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
There are two other occasions where packageOverrides are still in use,
one of them is @sternenseemann's fliewatuet machine and another one is
@devhell's package profile.
I've replaced every other occurence of packageOverrides and replaced it
with overlays and checked the store path hash after evaluation.
The reason why I left @sternenseemann's fliewatuet alone was that for
I wasn't quite sure whether "bluez = pkgs.bluez5" is still needed or
intentional to pin it to version 5. Because if it's not the case the
packageOverrides can just be dropped because bluez is already bluez5 in
upstream <nixpkgs>.
For @devhell's package profile, I did the conversion, but the store path
turned out to be a different one than what it was prior to the change.
I did take a quick look at the requisites of the drv and found that sox
was one of the different paths that led to the change in the final store
path.
This obviously needs to be tested and/or investigated first.
Other than that, the main reason why I'm moving everything to overlays
is that it's the replacement for packageOverrides and also has a better
way to pass through chains of overrides than packageOverrides had.
My guess is that after NixOS 17.09, the old packageOverrides function
will be removed, so let's make sure we're ready for that.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Cc: @devhell, @sternenseemann
|
|
|
|
|
|
|
| |
The option value was missing a .host, which caused the evaluation to
fail because of a missing attribute.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This makes sense to put into the core module here, because we already
have the public key in there as well and if we want to use the binary
cache outside of a channel it's a good idea to provide it here by
default.
Being a default of course also means that users can easily override this
using:
nix.binaryCaches = mkForce [ "something else" ];
I've also removed the redundant setting of that option in all of the
machine configurations.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Cc: @sternenseemann
|
|
|
|
|
|
| |
Added in NixOS/nixpkgs@dc87b5587e3fb39e96e6b965a26f324daf7508f8.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
New tests as of NixOS/nixpkgs@b0179351036a870da8c1a89c991a359a73aab0e2:
* containers-restart_networking
* nginx
* pgjwt
* postgresql (now with subtests per package)
* sddm (now with subtest "autoLogin" and "default")
* wordpress
The following tests were renamed:
* kde5 -> plasma5
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
| |
Fixes evaluation.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This fixes the attributes accordingly to the following two upstream
commits:
* NixOS/nixpkgs@f21d4d00152726c02f870cb20faba4aca18ef49a
* NixOS/nixpkgs@8eb4d2afbc1d61d316073f25f5885a46ccb37ea2
The first renames desktopManager.kde5 to desktopManager.plasma5 and the
second one removes the kde5 attribute from the top-level packages set
and puts applications in kdeApplications instead.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
|
|
|
| |
Haha, so that's what I got from introducing callSubTests in
NixOS/nixpkgs@b3337edd0b77f04d0abe4a29642a5e4fdb4ad692.
While in general this is an improvement, it makes it harder for vuizvui
to gather tests that were added or removed.
Maybe we should write an updater for this soon.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
New tests as of NixOS/nixpkgs@b207bf523b8c49b037a4a87456d61f63043cd2c6:
* containers-extra_veth
* containers-hosts
* containers-macvlans
* containers-physical_interfaces
* containers-tmpfs
* glance
* hound
* keystone
* leaps
* mongodb
* nat.firewall-conntrack
* pam-oath-login
* samba
* sddm
The following tests were removed:
* kde4
* panamax
I've also added a few checks on whether containers are actually enabled,
because some tests like containers-bridge would run if containers with a
bridge were defined but enableContainers was false.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This allows to add packages to vuizvui.lazyPackages which then aren't
directly installed onto the system but instead built by the Hydra and
only fetched from it as soon as a binary of one of these packages is
executed.
Doing this only within a NixOS module however isn't enough, because by
default gc-keep-outputs is false, so a garbage collect on the Hydra
instance would remove the packages we wrap in vuizvui.lazyPackages.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit a93b7583084ff9084d73873d80d8dc428406593c.
The issue isn't completely resolved but most of the packages should have
been fixed that tripped the nondeterministic behaviour, see:
https://ghc.haskell.org/trac/ghc/ticket/4012#comment:232
After having done some tests in the past I didn't stumble on this
problem anymore so far, so let's give it a try.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
New tests as of NixOS/nixpkgs@4ac7b7d5deb4a2ccf291c1251ff7515f1ab17c82:
* nixos.kde5
* nixos.ferm
* nixos.quagga
The following tests were removed:
* nixos.dockerRegistry
* nixos.sddm
The test for SDDM is now included within the KDE5 test.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
| |
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit 3f0a9e8002802e5a772b7582f8254c92d7a2a4d5.
It's now possible to disable support and tests for containers simply by
using config.boot.enableContainers in the machine config, because that's
the super option that enables all the container-related services and
tools in upstream NixOS and it's also enabled by default.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
| |
New tests are since NixOS/nixpkgs@4f796c28d57887cc9812190bc99fb45b2a.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
| |
This is to get a first working channel for bootstrapping. Fixing the
test is the long-term goal of course, so this is only temporarily.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
The name "profiles" really doesn't match what these modules are for.
Instead they define the very core of Vuizvui and its internal plumbing
and those options are available/enabled to all machines and modules.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|