| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Forgot that my volume controls are bound to pamixer, so reenabling it.
|
|
|
|
|
|
|
| |
In an effort to make my footprint a bit smaller I've taken a bit of time
to disable pkgs I'm sure I won't be needing anytime soon. However, I'm
keeping them commented for historic reasons and in case I do need
something back I don't have to look far.
|
|
|
|
|
| |
Running kernel 4.14 allows btrfs with zstd compression, so let's enable
that and also remove "ssd" enforcement on eris.
|
|
|
|
|
|
|
|
|
|
| |
This build error is quite annoying, so I applied the patch on v0.11.0
and rebased it against v0.12.0. The only hunk that's failing is the
import of get_secret_app_key in searx/webapp.py, so no big conflicts
with the actual logic of the patch.
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @Profpatsch
|
|
|
|
|
|
|
|
|
|
|
| |
The config attribute set is recursive, so "vuizvui" within that scope
refers to the "vuizvui" attribute within config directly instead of
using the one from pkgs.
Prepending "pkgs." explicitly to the attribute path now avoids this.
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @Profpatsch
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We no longer use the legacy SSH store protocol for taalo but the new
ssh-ng protocol, which makes the implementation of taalo-build a LOT
less clunky.
It also didn't make sense to have this as a NixOS module when we after
all just emit a static store path without any stuff depending on
configuration options.
The new implementation basically just wraps nix-build and nix-store -r
along with the right NIX_REMOTE variable.
With Nix 1.2 this can also be done with the new "nix build" command
using the --store option, but unfortunately "nix build" doesn't yet have
the same functionality as nix-build.
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @Profpatsch, @bendlas
|
|
|
|
|
|
| |
And here I've been sitting, wondering what the hell was wrong and why it
would wait ages to access a partition that doesn't (as it turns out)
exist. Duh.
|
|
|
|
| |
This is due to a bug and should be reenabled once solved.
|
| |
|
| |
|
|
|
|
| |
Patch doesn’t apply, I don’t use it anymore.
|
|
|
|
| |
My wifi module broke, because the microcode was too old and that option not set.
|
| |
|
| |
|
|
|
|
|
|
|
| |
I'm no longer using Synergy for anything, so let's prevent synergc from
attempting to connect to a non-existant server.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
| |
Using polybar now I feel there is no need for pasystray and I would also
like to have compton draw me shadows under windows.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
In the end I guess we're going to remove one or more of these, but right
now let's add all of them to have a way to evaluate.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Cc: @BrokkoliBerta
|
|
|
|
| |
Uni has some bonkers nameservers. This should hopefully fix it.
|
|
|
|
|
|
|
| |
Since rofi 1.4.0 the old way of theming has been dropped in favor of a
more complex and fine-grained theme engine. These theme files are rather
large and so it makes sense to move to the theme configuration to rofi's
XDG_USER_CONFIG_DIR.
|
|
|
|
|
|
|
|
|
| |
The option enableIntel2200BGFirmware was more or less an alias of
enableRedistributableFirmware and now has been removed upstream in
commit NixOS/nixpkgs@3df126dbf742f984b226f974ecfa649c70eb634e.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Cc: @sternenseemann
|
|
|
|
| |
Sorry.
|
|
|
|
| |
Let's switch to networkd.
|
|
|
|
|
| |
More often than not connman is not working reliably; on this machine at
least.
|
|
|
|
|
|
|
|
|
| |
Since this is a reinstall (thanks Toshiba BIOS people /s) I've opted to
remove f2fs and replace it with btrfs. After each new kernel fsck.f2fs
would take forever to check the filesystem before the system was usable,
and this doesn't happen with btrfs (or any other FS AFAIK). Also, I
really miss --reflink. We're also removing 'elevator=noop' here since
we're going to use BFQ.
|
| |
|
|
|
|
| |
thx @aszlig
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
Actually this is the only one workstation where I use gpodder, so let's
move it there and also don't make it a lazy package.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Both machines are using Plasma along with a few common KDE applications,
so let's actually be more aggressive about deduplicating the options,
because after all whenever these machines start to deviate more from
each other, we can still either override those options or move them out.
I've also cleaned up a few packages, so instead of having mpv *and* vlc
we now have mpv and bomi for both machines. The latter is mostly about
figuring out whether it's actually a good GUI video player, as it is
basically a front-end for mpv.
With this unification this means that some packages which are generally
useful, such as okular and gwenview are now not only available to tyree
but brawndo as well.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Cc: @dwenola, @BrokkoliBerta
|
|
|
|
|
|
|
|
|
|
|
| |
Most of them are KDE PIM applications and kmail so far was already
within the systemPackages in the configuration.nix directly so far.
The one exception to these is kmix (an audio volume mixer), which is
generally useful to have I think.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Cc: @BrokkoliBerta
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit 0cfbc3bcd4be9ba3798f1752f82f6ea2d3aba650.
Since NixOS/nixpkgs@ae9d311565d8c790900ebbc0976e447034930112 the addSSL
option is now mutually exclusive to forceSSL.
Turns out that this actually was a bug that got introduced in
NixOS/nixpkgs@a912a6a291eaa5f6a2ad9143c9e276779c357a41.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Cc: @Profpatsch
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
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
|
| |
|
| |
|