about summary refs log tree commit diff
Commit message (Collapse)AuthorAgeFilesLines
...
* modules/core/tests: adapt to paperless module renamesternenseemann2022-10-011-2/+2
| | | | | | | | Ref. https://github.com/NixOS/nixpkgs/commit/0977227b8622daccb5a8435d3d4216eedf845973 Evaluating the vuizvui Hydra seemingly hit an infinite loop involving the rename warning for this change, so hopefully adapting to it makes it possible to evaluate it again.
* release.nix: update programs.sqlite to 22.11pre411613.7e52b35fe98sternenseemann2022-09-291-2/+2
|
* pkgs/tvl: 2022-09-28 -> 2022-09-29sternenseemann2022-09-291-1/+1
| | | | | Disalbes checkMeta for depot which should prevent the odd eval failure due to extra meta attrs it uses
* machines/wolfgang: allow optionally injecting local configurationsternenseemann2022-09-282-0/+5
|
* machines/sternenseemann/ludwig: drop now obsolete spidermonkey fixsternenseemann2022-09-281-11/+0
| | | | | Seems like upstream fixed this header related issue in the meantime (or someone worked around it in nixpkgs).
* channel: Fix exposing meta.isHydraChannelaszlig2022-09-281-23/+27
| | | | | | | | | | | | | | | | | | | | | The isHydraChannel meta attribute is needed in order to tell Hydra that the derivation in question should be a channel tarball. However in Nixpkgs the meta attribute is not used, so checkMeta doesn't recognise it as a valid attribute which leads to an evaluation error. Recently[1] a commit got merged, which enables shallow type checking for meta attributes by default. This led to an evaluation error for our Hydra machine channels for the reason mentioned above. I opted to work around that issue by adding meta.isHydraChannel after mkDerivation, because adding isHydraChannel as a valid meta attribute to Nixpkgs doesn't feel right to me since it's only relevant for Hydra and its apparently deprecated[2] channel feature. [1]: https://github.com/NixOS/nixpkgs/commit/6762de9a28e248f46bd0810e03c [2]: https://github.com/NixOS/hydra/blob/53335323ae79ca1a42643f58e520b376898ce641/doc/manual/src/jobs.md#meta-fields Signed-off-by: aszlig <aszlig@nix.build>
* pkgs/tvl: fix evalsternenseemann2022-09-281-1/+1
|
* pkgs/tvl: 2022-06-03 -> 2022-09-28sternenseemann2022-09-281-1/+1
| | | | Contains adjustments for recent alias removals in nixpkgs.
* machines/sternenseemann/ludwig: workarounds initial i686 failuressternenseemann2022-09-271-3/+31
|
* machines/sternenseemann/ludwig: resurrectsternenseemann2022-09-272-5/+8
| | | | | | | | 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.
* machines/sternenseemann/wolfgang: update swap IDsternenseemann2022-09-271-1/+1
| | | | I re-created the swap for some reason, so this needs to be reflected.
* slylandro: Switch to PipeWireaszlig2022-09-261-0/+11
| | | | | | | | | 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>
* slylandro: Switch location provider to geoclue2aszlig2022-09-261-0/+2
| | | | | | | | | 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>
* slylandro: Add light commandaszlig2022-09-261-0/+2
| | | | | | | | | | | | 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>
* slylandro: Add libinput config for touchpadaszlig2022-09-261-0/+6
| | | | | | | | | | | | | | 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>
* pkgs/profpatsch: fix tvl referenceProfpatsch2022-09-261-0/+2
|
* wolfgang: Fix attribute name for xdg-utilsaszlig2022-09-261-1/+1
| | | | | | | | | | | 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
* machines/shiki: fix source-han-sansProfpatsch2022-09-261-3/+1
|
* pkgs/profpatsch/show-qr-code: fix encoding with newlinesProfpatsch2022-09-261-1/+8
| | | | The Qr-code was done with a strange format that only allowed ASCII.
* devhell/pkgs: Fix attribute name for virt-manageraszlig2022-09-261-1/+1
| | | | | | | | | | | The virtmanager attribute has been renamed a while ago[1] to its upstream name (virt-manager) and referencing the alias will now[2] throw an evaluation error. [1]: https://github.com/NixOS/nixpkgs/commit/5b640bfd089904bfe806606b8b2 [2]: https://github.com/NixOS/nixpkgs/commit/d06207386df9a53fe01f8a30130 Signed-off-by: aszlig <aszlig@nix.build>
* machines: Fix attribute name for gnomeaszlig2022-09-261-2/+2
| | | | | | | | | | | 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>
* Fix attribute name for iproute2aszlig2022-09-261-1/+1
| | | | | | | | | | | The attribute has been renamed[1] to iproute2 a while ago and recently the alias was converted to a throw[2], so let's do the rename on our side as well. [1]: https://github.com/NixOS/nixpkgs/commit/20a9caf0a474e182909ac850fa6 [2]: https://github.com/NixOS/nixpkgs/commit/d06207386df9a53fe01f8a30130 Signed-off-by: aszlig <aszlig@nix.build>
* pkgs/profpatsch: Fix attribute name for util-linuxaszlig2022-09-261-2/+2
| | | | | | | | | | | This attribute has been renamed a while ago[1] but recently even the alias was removed[2], which now triggers an evaluation error in Vuizvui. [1]: https://github.com/NixOS/nixpkgs/commit/bc49a0815ae860010b4d593b02f [2]: https://github.com/NixOS/nixpkgs/commit/ba3319568df2c6675dbe36478fb Signed-off-by: aszlig <aszlig@nix.build> Cc: @Profpatsch
* Fix attribute name for man-pages-posixaszlig2022-09-262-2/+2
| | | | | | | | | | | | The posix_man_pages attribute has been renamed in nixpkgs[1] to man-pages-posix to more closely match the upstream name. This now[2] results in an evaluation error. [1]: https://github.com/NixOS/nixpkgs/commit/4461230cc5e11952407f8ddd205 [2]: https://github.com/NixOS/nixpkgs/commit/d06207386df9a53fe01f8a30130 Signed-off-by: aszlig <aszlig@nix.build> Cc: @devhell
* pkgs/vim: Add quick-scope pluginaszlig2022-09-181-0/+7
| | | | | | | | | | | | Found this thanks to @fpletz starring the repository and since I constantly use f/F and t/T when navigating, I decided to give it a try. Usually when trying things, I'd just add the Vim version with the plugin to my local Nix profile, but since I'm already irritated when other things than the cursor are highlighted in the current line, I decided to do something completely irrational and just add it to all my machines. Signed-off-by: aszlig <aszlig@nix.build>
* radare2: Add patch to default to AT&T ASM syntaxaszlig2022-09-184-2/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Some personal history on this: I started to get used to AT&T syntax because it's the default in GDB and used that ever since until I one day starting to do some more reverse engineering using radare, which defaults to Intel syntax. Ever since then probably my most used command in GDB was "set disassembly-flavor intel" (because I was to lazy to add it to the config) because I constantly got confused by the source/destination operand swaps. This even happened during live reverse engineering at rC3 where I was confused about some function logic only to find out that I was viewing in AT&T syntax. Fast-forward to today: I'm debugging some application using WINE and winedbg uses AT&T syntax, which I didn't like at first. After reflecting on this for a while, I thought it would probably be better to get used to AT&T syntax again and switch everything to use AT&T for the following reasons: * Operands are more natural to read, since most libraries/APIs in higher level languages do it like this (well, except memcpy, strcpy, etc... maybe I now get confused by libc functions...) * AT&T syntax feels less verbose, for example "mov ecx, dword [eax]" is just "movl (%eax), %ecx" This very commit makes sure that radare2 now defaults to AT&T syntax instead of eg. ensuring that GDB uses Intel syntax by default. Signed-off-by: aszlig <aszlig@nix.build>
* workstation/packages: Add zbar to system packagesaszlig2022-09-111-0/+1
| | | | | | | | | | | Just had to scan the credentials for a Wi-Fi access point and they were only available via QR code, but was unable to make it available via Nix shell because I had (for obvious reasons) no access to the Internet. Adding zbar to all my machines will ensure that something like this won't happen again. Signed-off-by: aszlig <aszlig@nix.build>
* pkgs/sandbox: Create injected target directoryaszlig2022-09-101-4/+11
| | | | | | | | | | | | | When using NIX_SANDBOX_DEBUG_INJECT_FILES (which we now call NIX_SANDBOX_DEBUG_INJECT_DIRS, because it's more accurate), I usually used it to provide fake /dev or /sys directories. I turned out, that today I was trying to use this functionality again (who'd have known) and it also turned out that I forgot to create the target directory, which wasn't needed back then for /dev or /sys because they were already existing. Signed-off-by: aszlig <aszlig@nix.build>
* machines/slylandro: Remove tuxedo-keyboard moduleaszlig2022-09-081-1/+0
| | | | | | | | | 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>
* workstation: Use oldschool font pack from nixpkgsaszlig2022-09-051-11/+1
| | | | | | | | | Back then when I added the font pack in 0171f8d895efd46300ba01c6adeb7aa, version 2.0 was not yet merged to nixpkgs. This has happened in the meantime and the current version is version 2.2 and I also do not see any reason to keep the 2.0 version in Vuizvui. Signed-off-by: aszlig <aszlig@nix.build>
* profiles/workstation: Use autoLogin on LUKSaszlig2022-09-051-19/+28
| | | | | | | | | | | | | | | | | After countless boots with unlocking my LUKS containers and thereafter logging in via lightdm I started to wonder whether it really makes sense to do the latter. All of my workstations are single-user, I usually don't switch my session type (and even if, then via system configuration) and if someone manages to unlock my LUKS containers, it's really trivial to circumvent the user authentication. So if I'm not forgetting about something big[TM], the only purpose this additional auth serves is me being annoyed for no reason, so let's disable it if the configuration indicates that LUKS is used. Signed-off-by: aszlig <aszlig@nix.build>
* Use a font point size of 10 on hidpiaszlig2022-09-055-7/+13
| | | | | | | | | With my new laptop, a font size of 12pt is rather large and given that hidpi displays usually have a quite large resolution (the name might hint at that), we don't necessarily need to use embedded bitmaps anymore which was one of the reasons why I used a point size of 12. Signed-off-by: aszlig <aszlig@nix.build>
* machines/sternenseemann/wolfgang: update wireguard configsternenseemann2022-09-011-5/+5
|
* machines/sternenseemann/wolfgang: switch to yt-dlpsternenseemann2022-09-011-1/+1
|
* slylandro: Add quirk for disabling D3cold on NVMeaszlig2022-08-264-0/+62
| | | | | | | | | | | | | | | | | | | | | | 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>
* pkgs/vim: Remove hex and color names highlightingaszlig2022-08-231-0/+5
| | | | | | | | | | | | We only want to highlight #aabbcc-style hex colors and not every damn hex value that happens to be 3 or 4 bytes, which is very annoying when you're doing a lot of bit manipulation. Additionally, I currently have a code base where "gold" is something a player can have, so one doesn't need much imagination on how irritating that is. Signed-off-by: aszlig <aszlig@nix.build>
* pkgs/rustfmt: Use Nightly versionaszlig2022-08-231-1/+1
| | | | | | | The config we're baking in by default relies on Nightly features, so it only makes sense to actually use a rustfmt version that supports it. Signed-off-by: aszlig <aszlig@nix.build>
* pkgs/sternenseemann/saneterm: fix buildsternenseemann2022-08-161-0/+4
| | | | | Seems like something got more strict about setup hook execution and the relevant env vars for gi weren't set in checkPhase.
* modules/profiles/tvl: disable search domainsternenseemann2022-08-161-3/+0
| | | | This stopped working for me for some reason, so no point in keeping it
* machines + modules: Fix Nix option definitionsaszlig2022-08-1513-42/+25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* pkgs/vim: Use postFetch instead of extraPostFetchaszlig2022-08-151-3/+3
| | | | | | | | | | | | | | | | We no longer need to use extraPostFetch in order to append stuff to the postFetch phase of fetchzip. Since this got fixed[1], we now get appropriate warnings during evaluation: warning: use 'postFetch' instead of 'extraPostFetch' with 'fetchzip' and 'fetchFromGitHub'. Neither do we like warnings nor do we like to use workarounds from the past that got fixed, so let's fix it on our side as well :-) [1]: https://github.com/NixOS/nixpkgs/pull/173430 Signed-off-by: aszlig <aszlig@nix.build>
* profiles/workstation: Add perf to systemPackagesaszlig2022-08-151-5/+8
| | | | | | | | I use perf on a regular basis and since it's dependant on the currently running kernel version, it' just makes sense to have it available at all times rather than "nix run" it with the right kernel version. Signed-off-by: aszlig <aszlig@nix.build>
* machines/tishtushi: Remove machine configaszlig2022-08-152-57/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | 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>
* core/tests: Remove nixos.docker-edgeaszlig2022-08-151-4/+0
| | | | | | | | The package has been removed and we're getting the following eval error: error: 'docker-edge' has been removed, it was an alias for 'docker' Signed-off-by: aszlig <aszlig@nix.build>
* profiles/managed: Remove TLPaszlig2022-08-151-2/+0
| | | | | | | | | | | | | | Right now we're getting an eval error like this: Failed assertions: - You have set services.power-profiles-daemon.enable = true; which conflicts with services.tlp.enable = true; Since the machines in question are for desktop environment users, TLP doesn't make a lot of sense. Besides, the option should not be defined in managed.nix anyway, because it's a hardware-specific option. Signed-off-by: aszlig <aszlig@nix.build>
* machines/shakti: Remove machine configaszlig2022-08-152-74/+0
| | | | | | | The machine no longer exists, so it doesn't make sense to continuously build it on Hydra. Signed-off-by: aszlig <aszlig@nix.build>
* packages: Replace jwhois by whoisaszlig2022-08-151-1/+1
| | | | | | | | | | | | | | | | The upstream project seems to be no longer maintained[1] and the last release from 2005 contains a whole bunch of outdated NIC information so that it became pretty annoying to use. Back then jwhois was the only whois client packaged in nixpkgs, so this might be the reason why it ended up in my setup in the first place. The "whois" package on the other hand seems to be actively maintained and works well for the domains I care about. [1]: https://github.com/jonasob/jwhois/issues/32 Signed-off-by: aszlig <aszlig@nix.build>
* slylandro: Initialise amdgpu module early in bootaszlig2022-08-031-0/+1
| | | | | | | | 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>
* slylandro: Enable keyboard backlightaszlig2022-08-031-0/+1
| | | | | | | | 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>
* slylandro: Add linux-firmwareaszlig2022-08-031-0/+1
| | | | | | This is needed for the GPU and the WiFi adapter. Signed-off-by: aszlig <aszlig@nix.build>
generated by cgit-pink 1.4.1 (git 2.36.1) at 2024-07-06 10:11:24 +0000