| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
Mdbook has become really useful for writing lab material, so I'll
introduce it permanently to my package collection.
|
|
|
|
|
|
|
|
|
|
|
| |
I've been using taskwarrior a lot again lately, and this time I'd be
interested in seeing how much time I actually spend on certain tasks, so
I'm adding timewarrior to the mix. Unfortunately the hook requires that
python3 is installed.
WTF is a neat terminal dashboard that show information that I deem
useful and would like to keep an eye on without having to manually check
for stuff.
|
|
|
|
|
|
|
|
| |
When you have a lot of branches it's sometimes tedious to find out the
ones you've been working on recently. Sorting the branches by committer
date by default should make it more obvious.
Signed-off-by: aszlig <aszlig@nix.build>
|
| |
|
|
|
|
| |
Fixes build (!) of my emacs on i686-linux.
|
|
|
|
| |
Fixes eval of my emacs on i686-linux
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Quoting from https://github.com/i3/i3/pull/5173:
A bug was introduced in https://github.com/i3/i3/pull/5118 in which
configs with bar blocks will segfault during validation. They were
copying the i3 font which is not set during validation. This PR simply
checks that the load_type is not validated before copying the font.
This fixes the Hydra build for the i3 configuration on my machines.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
| |
depot reimports nixpkgs, so we need to make sure it passes the correct
value for `system`. As a result of how depot works, cross is unsupported
at the moment.
This breaks machines/sternenseemann/ludwig for the moment, which we'll
be able to address separately.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Introduced by a recent change[1], all NixOS VM tests are evaluated using
the NixOS module system and with [2], makeTest doesn't return a
derivation anymore but the .config attribute of the module system
evaluation.
This however doesn't work very well when thrown into Hydra, which
traverses through all attributes recursively looking for derivations.
We had our fair share of OOMs on our Hydra evaluator and right now, some
jobsets are still getting evaluation timouts, one of them is due to the
fact that we use makeTest without returning the actual test derivation.
[1]: https://github.com/NixOS/nixpkgs/pull/191540
[2]: https://github.com/NixOS/nixpkgs/commit/aed1deab0574f663be2d401861b
Signed-off-by: aszlig <aszlig@nix.build>
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
| |
Disalbes checkMeta for depot which should prevent the odd eval failure
due to extra meta attrs it uses
|
| |
|
|
|
|
|
| |
Seems like upstream fixed this header related issue in the meantime (or
someone worked around it in nixpkgs).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
| |
|
|
|
|
| |
Contains adjustments for recent alias removals 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 Qr-code was done with a strange format that only allowed ASCII.
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
| |
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>
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
| |
Seems like something got more strict about setup hook execution and the
relevant env vars for gi weren't set in checkPhase.
|
|
|
|
| |
This stopped working for me for some reason, so no point in keeping it
|