https://hydra.nixos.org/build/295225429
This unbreaks nixosTests.budgie when a fix for qt6gtk2 is still in
review. This does not seem to work in Wayland so I guess we will
eventually drop that in next Budgie bump anyway.
See also 7e685d3693 for Cinnamon and 36bc3f46ba for Pantheon.
Roboto was already set as the font for the manuals,
but without a way to get it, so people who didn't
happen to have it installed saw their default font
On `fish`, Starship supports transient prompts with no external dependencies.
This commit adds three options that allows users to edit the function bodies of
`starship_transient_prompt_func` and `starship_transient_rprompt_func` and call
`enable_transience` after the Starship initialisation code is sourced into the
shell.
This avoids the need for downstream NixOS configurations to use the
`programs.fish.promptInit` option with the `lib.mkAfter` function to correctly
enable transience.
Signed-off-by: Fernando Rodrigues <alpha@sigmasquadron.net>
Use vwifi to write a proper test for Kismet. This test demonstrates how
to simulate wireless networks in NixOS tests, and extract meaningful
data by putting an interface in monitor mode using Kismet.
Fix compatibility with previous versions by making sure all the uploads
and plugins end up in the correct directory. Add a test for the exact
path we care about to ensure that it doesn't work "on accident."
Discovered while updating instances to unstable.
flashprog uses the libraries libjaylink and libftdi. So in order for
flashprog to work properly for non-privileged users, enable their
related NixOS modules which enable several udev rules for devices used
by flashprog.
Signed-off-by: Felix Singer <felixsinger@posteo.net>
This prevents the network from being torn down before alloy itself it
stopped.
Alloy tries to flush its WAL on SIGTERM, and if the network stack is
already down, it tries to flush logs up to 90s during shutdown/reboot.
From https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/:
> network.target has very little meaning during start-up. It only
> indicates that the network management stack is up after it has been
> reached. Whether any network interfaces are already configured when
> it is reached is undefined. Its primary purpose is for ordering
> things properly at shutdown: since the shutdown ordering of units in
> systemd is the reverse of the startup ordering, any unit that is order
> After=network.target can be sure that it is stopped before the network
> is shut down if the system is powered off. This allows services to
> cleanly terminate connections before going down, instead of abruptly
> losing connectivity for ongoing connections, leaving them in an
> undefined state. […]
