| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
In order to use forceSSL you now also need to use addSSL and there is an
assertion now to check that since NixOS/nixpkgs@a912a6a291eaa5f6a2ad914.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Cc: @Profpatsch
|
|
|
|
|
|
|
|
|
|
| |
Since NixOS/nixpkgs@c217f48c358db05bd0ad7893e8e3ebabe4784cbe, the searx
package is no longer in pythonPackages but a top-level attribute.
Tested eval by "nix-instantiate machines -A profpatsch.haku.build".
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Cc: @Profpatsch
|
|
|
|
|
|
|
|
|
|
|
|
| |
I don't use anything that's machine specific within my Vim
configuration (and even if, we can pass it via the callPackage
arguments) so it's kinda pointless that it's a module instead of a plain
package (override).
This makes it also easier to nix-build the package without the need to
go through the module system.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
|
|
|
| |
This dissolves the user.aszlig.system.kernel module, which was not only
to stay on the latest bleeding edge kernel but also to enable BFQ. The
latter has been factored out already a while ago already.
Originally, I had a fully custom kernel config for mmrnmhrm and dnyarri,
but it's no longer the case and thus the user.aszlig.system.kernel
module is now no longer needed.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
| |
|
| |
|
|
|
|
| |
cc @aszlig
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
sane has a file called `net.conf` which is a list of hosts that are searched for
remote scanners.
|
| |
|
|
|
|
|
| |
Apparently `enableACME` doesn’t generate certificates for the right subdomains
if they are on the same machine in different virtual hosts.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Until now, the config on the actual server was deviating because I changed it
locally.
|
| |
|
| |
|
|
|
|
| |
A simple script to gather DNS & download speed data.
|
|
|
|
| |
Signed-off-by: devhell <devhell@mailfresser.de>
|
|
|
|
|
|
|
| |
For whatever reason the /boot configuration was missing and subsequently
nixos-rebuild would fail. Thanks for pointing out the error @aszlig!
Signed-off-by: devhell <devhell@mailfresser.de>
|
|
|
|
|
|
|
| |
Let's see how the touchpad on this new laptop behaves with libinput
instead of synaptics.
Signed-off-by: devhell <devhell@mailfresser.de>
|
|
|
|
|
|
|
| |
I no longer need to actively debug the kernel or do much development on
the machine, so this is no longer needed.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
| |
This reverts commit 2e90b9562939208e5392790834c6ffd89aede692.
Sorry about this. I was wrong as it seems networking.wireless is
required for connman.
|
|
|
|
| |
Not even sure if it is needed anymore to keep connman working.
|
| |
|
|
|
|
| |
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
| |
|
|\
| |
| |
| |
| |
| |
| | |
This merges pull request #15 and thus also introduces @devhell as a new
member of vuizvui.
Changes were approved by @devhell via XMPP.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This reverts commit 646e0cb3dede3880ed578d09b7337445990f5416.
The layout checker has been fixed in NixOS/nixpkgs@44c64fef16ed566786c8.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Cc: @devhell
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This introduces another profile module called "packages", which contains
all the package configuration (including overrides) of all the machines
in the devhell namespace.
The machine-specific configuration is now merged into the machine
configurations the same way as we've done previously with the services.
One major difference here is that the haskellPackages workaround is no
longer needed in the package configuration, as it is handled by vuizvui.
Tested this by evaluating all machines and all evaluations succeeded.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Cc: @devhell
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
I've added another profile called "services", which now resembles the
services_common.nix from the previous configuration.
The machine-specific definitions now reside directly inside the
machine's Nix expressions for now, until they're properly refactored.
Most of these machine-specific values can be easily modularized,
especially the xrdb config, for example having one base xrdb module
and only small machine-specific definitions if stuff needs to be
overridden.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Cc: @devhell
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Those definitions are machine-specific, so IMHO it doesn't make sense to
abstract those options because in the end they're bound to a specific
machine nonetheless and won't be re-used.
If one day it's necessary to re-use these definitions it still can be
done very easily.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Cc: @devhell
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In his configuration he had machine_common.nix which was imported from
the other machine_*.nix files. However in order to start modularizing
I've converted machine_common.nix into a proper NixOS module which now
resides in modules/user/devhell/profiles/base.nix and can be simply
activated via:
vuizvui.user.devhell.profiles.base.enable = true;
Apart from that I've removed the following configuration definitiens
from machine_common.nix:
nix.binaryCaches = [
"https://headcounter.org/hydra/"
"https://cache.nixos.org/"
];
nix.requireSignedBinaryCaches = true;
nix.binaryCachePublicKeys = [
"headcounter.org:/7YANMvnQnyvcVB6rgFTdb8p5LG1OTXaO+21CaOSBzg="
"cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY="
];
nix.nixPath = lib.mkOptionDefault [
"nixpkgs=/home/dev/git/remote/other_github/nixpkgs"
];
The reason for removing them is because we already handle that via the
vuizvui core modules (modules/core/common.nix).
I've tested this by evaluating the machines by temporarily setting
"allowUnfree = true" (which is part of another module I didn't migrate
yet) and it succeeds.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Cc: @devhell
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The package fails because the mtp-jolla.patch was already applied
upstream, see the following build log:
https://headcounter.org/hydra/log/d21f1590i2hs6xhgkdr00906ksnvgxfz-libmtp-1.1.13.drv
This is the upstream commit by @Profpatsch that's now part of libmtp
version 1.1.13:
https://sourceforge.net/p/libmtp/code/ci/8919ebeef58251639454c2394c0274597be3df9c/
Tested by evaluating machines.profpatsch.katara.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Cc: @Profpatsch
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
We only use the firmware blobs for the CPU microcode and the GPU, both
of them are redistributable so there is no need to enable those that
have even more licensing restrictions.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Tomahawk is no longer actively developed and the current state within
vuizvui is also broken. So after asking the users of brawndo and tyree
whether they still use it they answered with a "no", so it doesn't make
sense to fix up that package if noone is using it anyway.
This has also been announced via the README in the official GitHub
repository, where the change + comments can be seen here:
https://github.com/tomahawk-player/tomahawk/commit/c8389592488c07079
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Evaluation error introduced by 736e0da1e251df836b1669ffee80cecfd6bbf0e9.
The attribute "hledger" isn't a top-level pkgs attribute but resides
within haskellPackages.
This fixes evaluation, as tested by:
nix-instantiate machines -A profpatsch.katara.build
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Cc: @Profpatsch
|