| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
My battery is bigger nowadays, so these are a little early.
|
| |
|
|
|
|
|
| |
They are current decomissioned, so no need to waste precious hydra
resources.
|
|
|
|
|
|
| |
systemd-networkd-wait-online is still annoying as hell, but just
disabling it normally clashes now with the default, so let's force it
into a disabled state.
|
|
|
|
| |
This reverts commit b1440a0ee2a096fd99f2d9217830e47e00d058de.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The "vim_configurable" derivation has had a long history in nixpkgs back
then when there was no RFC process and where people still were figuring
out better ways on how to configure compile-time flags.
One of those was a composableDerivation function, which was used for
"vim_configurable" and mapped attribute sets to autoconf-flags, so that
for example if there was a "--enable-foo" flag you could just use
something like:
vim_configurable.merge { cfg.fooSupport = true; }
You'd then get a Vim with "--enable-foo" passed to configureFlags.
However, the composableDerivation feature was too complicated and was
ultimately removed at some point. While it does allow for things such as
introducing new "edf" (stands for Enable Disable Feature and maps the
autoconf flags mentioned above to attribute sets) flags, the complexity
that comes with that system is way too large than using something like
eg.:
vim-full.overrideAttrs (drv: {
configureFlags = (drv.configureFlags or []) ++ [ "--enable-foo" ];
})
While this looks more verbose than the above, one can easily follow
what's happening, whereas if you'd need to add and enable a new "edf"
flag, you'd do something like this:
vim_configurable.merge {
flags = composableDerivation.edf { name = "foo"; };
cfg.fooSupport = true;
}
I admit that this does look a little nicer, but even I'm not sure
whether it's worth adding so much complexity since in practice I rarely
came across a sitation where something like the above would be really
beneficial.
So back then when "vim_configurable" was introduced[1], it was used as
an alternative to the main vim derivation but using composableDerivation
instead.
Nowadays however, vim_configurable no longer uses composableDerivation
and the rename also doesn't change any features, so I think it's safe to
rename vim_configurable to vim-full in Vuizvui.
[1]: https://github.com/NixOS/nixpkgs/commit/9a4e9e7a3b4014bb3c9f678ec22d254b85c4c98a
[2]: https://github.com/NixOS/nixpkgs/commit/4e5ebcc3ed1de9c5c2001c7d5829f4566e0bde3f
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @Profpatsch
Cc: @devhell
|
| |
|
|
|
|
|
|
| |
Hydra seems to have an issue now with these, even though they compiled
fine locally, but I don't really need them now anyway, so might as well
remove them.
|
| |
|
|
|
|
|
|
| |
This prevents the catch-all package overwriting e.g. noto-fonts-emoji
(where the version from google-fonts doesn't work atm due to some
unsupported features on my machine).
|
| |
|
|
|
|
| |
nautilus started behaving weirdly in sway recently.
|
|
|
|
|
|
| |
Microsoft apparently decided to discontinue the Teams electron app for
Linux. True or not, the app sucks either way, and this just saves disk
space if we're to use the progressive web app.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
CVE patch is out already, but let’s wait until upstream has all the
patches.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Comment out a lot of the old stuff that I might not want to re-enable
later. And get rid of the pre-tailscale wireguard desaster.
|
| |
|
|
|
|
| |
Mod4 doesn't exist on ludwig's keyboard.
|
|
|
|
|
| |
Some stuff we don't desperately need is disabled to already get started
on closure size limitation.
|
|
|
|
|
|
|
|
|
|
| |
Making it a proper module with options allows us to selectively switch
off stuff we don't need, e.g. saneterm. This should help keeping the
closure of ludwig smallish.
Additionally refactor font handling in the module: Instead of including
fonts.nix and assuming Bitstream Vera is available, we check
fonts.fontconfig.defaultFonts for the font to prefer.
|
| |
|
| |
|
|
|
|
|
| |
Seems like upstream fixed this header related issue in the meantime (or
someone worked around it in nixpkgs).
|
| |
|
|
|
|
|
|
|
|
| |
This is the old racker machine, but needs to be re-installed (hence the
updated stateVersion) and is renamed more consistently. This has not
much set up yet, trying to get binary cache up for the first install.
cc @aszlig, LMK if this is an unreasonable burden on the builders.
|
|
|
|
| |
I re-created the swap for some reason, so this needs to be reflected.
|
|
|
|
|
|
|
|
|
| |
I've been testing PipeWire on this machine for quite a while and it
works pretty well so far. My goal is to switch all my machines to it,
but since Dnyarri currently has a pretty complicated audio setup I
decided to not make it the default for the workstation profile yet.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
| |
I do have location.latitude and location.longitude set in my workstation
profile, but since Slylandro is a laptop that frequently changes
location it makes sense to automate this in a way that I don't need to
manually set the location every time I switch places.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
| |
While I do use redshift to decrease the brightness at night, I also tend
to sometimes use the laptop when barely awake. Having a convenient CLI
makes it easier to script, eg. "mpv somefile; light -S 0".
The reason why I did not add this to my generic workstation profile is
because my workstations are usually placed in a way that I need to be
awake enough to approach them.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I never got really used to the "buttonareas" click method and while
"clickfinger" does have some disadvantages (eg. dragging is much more
difficult without drag lock), in most other cases I find the clickfinger
method a lot more convenient, since it usually only requires one hand to
operate.
Since we have clickfinger enabled, I also don't see a point in enabling
middle click emulation since three fingers already count for a real
middle click.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
| |
Another one of the attributes that got renamed from xdg_utils to
xdg-utils a while ago[1] and which now[2] throws an evaluation error.
[1]: https://github.com/NixOS/nixpkgs/commit/a6ac3eedbd197746dae3be74d3a
[2]: https://github.com/NixOS/nixpkgs/commit/d06207386df9a53fe01f8a30130
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @sternenseemann
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
The gnome3 attribute got renamed a while ago[1] and a recent change[2]
now causes an evaluation error when it's used, so let's rename it to
just "gnome".
[1]: https://github.com/NixOS/nixpkgs/commit/468cb5980b56d348979488a74a9
[2]: https://github.com/NixOS/nixpkgs/commit/d06207386df9a53fe01f8a30130
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
| |
This actually consists of several modules which are of poor code
quality, none of them however are essential for the TUXEDO Pulse 15
because its keyboard backlight is single color so let's drop them since
they just taint the kernel for no reason.
Signed-off-by: aszlig <aszlig@nix.build>
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
After resume from suspend the NVMe does not wake up again when the
device was put into D3cold. This is something that is worked around by
TUXEDO Tomte[1] via udev rules. However, I personally don't like this
approach and it can lead to race conditions when we're going into
suspend before udev is initialised.
Interestingly, the device does even go into NPSS via APST, but if
changing to D3cold while APST is enabled, the device does not wake up
again.
Right now I just added a new quirk to disable D3cold during device
probe for now, but we could maybe find a better workaround eg. by
disabling APST before D3cold and re-enabling it again. Not sure whether
this is feasible, but since I have limited time right now I can't dig
more into this.
[1]: https://github.com/tuxedocomputers/tuxedo-tomte/commit/2c8d71170868a2663705fbea6ac150eecb96e6ce
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Most of the options in nix.conf are now exposed as a submodule with a
freeform type and since that change[1] got introduced, we get a bunch of
warnings during machine evaluation:
trace: warning: The option `nix.useSandbox' defined in `...' has been renamed to `nix.settings.sandbox'.
trace: warning: The option `nix.maxJobs' defined in `...' has been renamed to `nix.settings.max-jobs'.
trace: warning: The option `nix.buildCores' defined in `...' has been renamed to `nix.settings.cores'.
To shut them up, I went through all machines and modules and renamed the
remaining options that were not renamed back then when @devhell did some
renames in a0297bf921399c3243dcca99626d8697f0735abe.
This was done by looking through the output of:
$ git grep -A 10 '\<nix\(\.\| *=\)' machines modules
After that I tested the contents of the nix.conf of all the machines
against the changes this commit introduced via the following command:
$ nix-build --no-out-link -E '
with import <nixpkgs/lib>;
map (m: m.eval.config.environment.etc."nix/nix.conf".source)
(collect (m: m ? eval) (import ./machines))
'
I've sorted the resulting nix.conf files and diffed on that result and
the only difference that showed up was the following:
allowed-users = *
-auto-optimise-store = false
auto-optimise-store = true
builders-use-substitutes = true
cores = 0
This is because the previous way to generate the config was by
concatenating strings whereas the new way works on an attribute set, so
we get deduplication by design.
[1]: https://github.com/NixOS/nixpkgs/pull/139075
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @devhell
Cc: @Profpatsch
Cc: @sternenseemann
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I already killed that machine on 2022-08-04:
tishtushi[~]0> cryptsetup erase /dev/sda2
WARNING!
========
This operation will erase all keyslots on device /dev/sda2.
Device will become unusable after this operation.
Are you sure? (Type 'yes' in capital letters): YES
tishtushi[~]0> cryptsetup erase /dev/sda3
WARNING!
========
This operation will erase all keyslots on device /dev/sda3.
Device will become unusable after this operation.
Are you sure? (Type 'yes' in capital letters): YES
Since some of the hardware was already broken (touchpad, keyboard, HDD,
SSD and webcam), I hardly doubt that I'll use it again so it makes sense
to remove the config here.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
| |
The machine no longer exists, so it doesn't make sense to continuously
build it on Hydra.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
| |
The amdgpu module is initialised at roughly the same time as the X
server, which sometimes leads into race conditions where X won't start
because the kernel driver is not yet loaded.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
| |
This is a custom kernel module for TUXEDO laptops, which allows to
control the backlight. I haven't played around with its settings yet,
but having the module available helps with that.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
| |
This is needed for the GPU and the WiFi adapter.
Signed-off-by: aszlig <aszlig@nix.build>
|