| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This was one of the places where types.loaOf was still in place and it
got removed a while[1] ago and this in turn causes evaluation to fail
for quite a few machines:
The option value `boot.initrd.luks.devices' in `...' is not of type
`attribute set of submodules'.
I've not only changed all the machines to use attribute sets but also
fixed the check in core/tests.nix, because comparing against a list when
the actual type is an attribute set will result in all the LUKS tests to
be part of *all* channels, no matter whether you're actually using LUKS.
[1]: https://github.com/NixOS/nixpkgs/commit/20d491a317d9956ddca80913f07
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @Profpatsch
Cc: @sternenseemann
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The package attributes for GSstreamer 0.x were dropped[1] a while ago,
so evaluating the packages no longer succeeds and instead we get an
error like this on Hydra:
error: undefined variable 'gstreamer' at .../profiles/packages.nix:129:7
Initially I was tempted to change this to use pkgs.gst_all_1.gstreamer,
but looking at the differences between the old pkgs.gstreamer, the new
package only contains the relevant libraries while the old one contains
a few binaries, namely gst-feedback, gst-inspect, gst-launch,
gst-typefind, gst-xmlinspect, gst-xmllaunch and all of them again with a
"-0.10" suffix.
All of these tools are development tools and should not be used in real
applications, for example from the manual[2] on gst-launch-1.0:
> Please note that gst-launch-1.0 is primarily a debugging tool. You
> should not build applications on top of it. For applications, use the
> gst_parse_launch() function of the GStreamer API as an easy way to
> construct pipelines from pipeline descriptions.
While environment.systemPackages does link other directories than just
$out/bin, the primary reason why you'd want to put something in there is
to make it available in the system's PATH.
When asking @devhell about this he didn't remember the exact reason why
he put gstreamer in systemPackages, so I can only *assume* it was
because of tools like gst-launch, which unfortunately even I can
remember seeing recommended (instead of eg. ffmpeg) in some dark corners
of the web.
So if this would be really about gst-launch, we would need to put in
pkgs.gst_all_1.gstreamer.dev into systemPackages, since the development
tools are now where they belong.
Given that @devhell doesn't know the reason anymore and *also* told me
to remove it *and* it's also just a development tool which is not
supposed to be used in production, I'm hereby removing the package.
Should there really be applications which rely on this, they should
hopefully break after this change so they can be fixed to not rely on
these development tools.
[1]: https://github.com/NixOS/nixpkgs/commit/4a4e642abaaa026b55f42248a7b
[2]: https://gstreamer.freedesktop.org/documentation/tools/gst-launch.html
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @devhell
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
A recent change[1] has removed the lib output from the systemd package,
so our GnuPG agent wrapper no longer compiles.
Using getLib falls back to the "out" output if the "lib" output is
unavailable and should be backwards- and forwards-compatible (in case
the "lib" output is added back someday).
[1]: https://github.com/NixOS/nixpkgs/commit/b68bddfbda2092c5fde2c4cece2
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
| |
Using "with lib;" over such a broad scope makes it more difficult to
detect early evaluation errors since we need to evaluate the whole
system to check whether a non-existing attribute set is actually using
the "lib" fallback or whether it really exists in the current scope.
This makes "nix-instantiate --parse" feasible for detecting typos early
on.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
| |
This is really useful.
|
|
|
|
|
| |
At some point compton was renamed to picom, we have an alias for it, but
I feel better if it's using the new name.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
So far we directly start a mosh-daemon when the user connects.
This breaks down in situations where UDP is blocked (e.g. some
hotspots). In that case, ssh can be used directly:
Example:
ssh -t weechat@legosi ssh
The ssh argument tells it to connect directly.
Note the `-t`, which forces a pseudo-tty, otherwise tmux will
complain that it can’t find a terminal.
|
|
|
|
|
|
|
| |
This has also been removed [1] upstream and therefore needs to be
removed here.
[1]: https://github.com/NixOS/nixpkgs/commit/b2f3bbd3fb958601a7357e39d66f226e065d76c1
|
|
|
|
|
|
|
| |
This package, the module and its test have been removed [1], so to
unbreak Hydra we need to remove it as well.
[1]: https://github.com/NixOS/nixpkgs/commit/aebf9a4709215c230e5841d60e2
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The option has been removed upstream[1] and it only has been true by
default for a very small time frame in 2014[2] and I believe even
earlier (before the nixos -> nixpkgs merge) there was another occasion
where it defaulted to true.
However, with the option gone, this is now no longer necessary.
[1]: https://github.com/NixOS/nixpkgs/commit/aebf9a4709215c230e5841d60e2
[2]: https://github.com/NixOS/nixpkgs/commit/b792394119b8ffc4a2fd34a6704
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
| |
Similar to aszlig, I have fond memories of these fonts. I've not been
able to use them though because of my work. Maybe these will work
better, and v2 of these fonts will hopefully land in nixpkgs soon too.
|
|
|
|
|
| |
Same look, but written in rust and the binary is smaller too, what's not
to like?
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I've been using this configuration since years already but so far it has
been residing in ~/.muttrc and I copied to new machines accordingly.
The reason why I didn't add it here was because the config was too ugly
and I never got so far as to properly re-do it.
Unfortunately, the config is still ugly as hell, but at least we now
generate it from a structured Nix format and also the IMAP/SMTP user and
server infos are now retrieved via gopass instead.
This also includes my small prank multipart/alternative filter, which
should hopefully "encourange" recipients to disable HTML
parsing/rendering.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The DOSEMU fonts we were using so far for CP437 were bitmap fonts only
and with no unicode support.
Luckily there is https://int10h.org/oldschool-pc-fonts/ - which is a
really cool font pack containing all the cool oldschool fonts that I
remember from my childhood and still use today for creating ASCII art.
Since we recently* hit the 21st century, I think it's about time that
even I should start having terminals with proper Unicode support. The
latter is already the case, but the glyphs just didn't display
correctly.
The font that I switched to (MxPlus IBM VGA 8x16) is using embededd
bitmaps, so I also enabled useEmbeddedBitmaps option, so that the font
still looks as crisp as the old DOSEMU font.
To make sure it really is the same font, I compared screenshots of all
the CP437 characters with the new font and they match the old font 1:1.
I also removed the liberation_ttf font, since it's already included by
the default NixOS font configuration.
* -> Your mileage may vary, but hey, the 90ies were yesterday, right?
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
| |
I'm really not digging the fact that weechat _constantly_ changes stuff
in it's config directory. Makes keeping it under version control a pain
in the ass.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I regularily keep things in nix-env to see whether I keep using them and
"entry" is one of the little tools I ended up using quite regularily.
The program monitors a set of files via inotify and runs a command
whenever one or more of them change, which makes it quite useful for a
"change code, compile, run" cycle.
Upstream URL: https://eradman.com/entrproject/
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
| |
Whatever the case, I don't want this anymore.
This reverts commit 04bbb9966ba29fca3026a606adaa42a8a415523b.
|
|
|
|
| |
This seems to be useful.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
From the release notes of Git version 2.27.0:
* "git pull" issues a warning message until the pull.rebase
configuration variable is explicitly given, which some existing
users may find annoying---those who prefer not to rebase need to
set the variable to false to squelch the warning.
This is exactly the warning which is annoying me all the time now, so in
order to get rid of it, let's explicitly set the default behaviour
(which is doing a recursive merge).
Just to be sure that I really want the default behaviour, I analysed my
shell history for invocations of "git pull" and only around 20% of the
invocations were with --rebase, 14% were with an explicit URL (but no
rebase) and the rest were recursive merges.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
| |
This seems useful.
|
|
|
|
| |
Stuff like `virt-manager` has broken buttons.
|
|
|
|
|
|
|
|
| |
I've had this in my configuration.nix for a while and since I got used
to it, I think it's a good idea to enable both Nix Flakes and the "nix"
command by default for all my machines.
Signed-off-by: aszlig <aszlig@nix.build>
|
| |
|
| |
|
|
|
|
| |
Also add the service to legosi so I can use it from the weechat user.
|
|
|
|
| |
I'm fairly certain this isn't needed anymore.
|
|
|
|
|
|
|
| |
According to [1], `udev` has gained native support for FIDO security
tokens, and subsequently has been removed upstream.
[1]: 89c3e73dad0970b26183e415555fb0379ba33e7a
|
|
|
|
|
|
|
| |
As already stated otherwise in this log, it's back, so reverting the
removal.
This reverts commit 54b3f8ac7da02738be6919d05ae12d5c14796e3f.
|
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit 64fdbcc7e0949a3d3bf1cee3361d5ebe5c56cc4c.
It seems that there is now[1] a maintained version of p7zip and since I
didn't get used to unar so far, I take this opportunity to switch back
to p7zip.
[1]: https://github.com/NixOS/nixpkgs/pull/90140
Signed-off-by: aszlig <aszlig@nix.build>
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I even mentioned the full names of the test attributes in
bc4203d221c87a0622d089aaa61884f86d40fd44:
tests.wireguard.wireguard-basic-linux-5_4
tests.wireguard.wireguard-basic-linux-latest
tests.wireguard.wireguard-generated-linux-5_4
tests.wireguard.wireguard-generated-linux-latest
tests.wireguard.wireguard-namespaces-linux-5_4
tests.wireguard.wireguard-namespaces-linux-latest
tests.wireguard.wireguard-wg-quick-linux-5_4
tests.wireguard.wireguard-wg-quick-linux-latest
So I forgot about the additional "wireguard-" prefix, so Hydra fails to
evaluate again:
in job 'tests.nixos.wireguard.basic-linux-5_4':
evaluation aborted with the following error message: 'cannot find attribute `nixos.wireguard.basic-linux-5_4''
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Commit 89c3cda819da5dc32e4a29ff8f2aad118bde64c7 changed the wireguard
attributes to use nested attributes because it was changed upstream.
However what the commit has missed is that the attributes are not just
plain attributes but come with a kernel version suffix, for example like
this:
tests.wireguard.wireguard-basic-linux-5_4
tests.wireguard.wireguard-basic-linux-latest
tests.wireguard.wireguard-generated-linux-5_4
tests.wireguard.wireguard-generated-linux-latest
tests.wireguard.wireguard-namespaces-linux-5_4
tests.wireguard.wireguard-namespaces-linux-latest
tests.wireguard.wireguard-wg-quick-linux-5_4
tests.wireguard.wireguard-wg-quick-linux-latest
Adding the "-linux-${version}" suffix should fix evaluation.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
A few days ago, the wireguard tests were consolidated[1] into a single
attribute with various subattributes, similar to how the virtualbox
tests and many other tests are structured.
I fixed the attributes and also added the wg-quick attribute that was
also introduced in the meantime[2].
This should fix the evaluation errors occuring whenever a channel
contains a machine configuration with wireguard enabled.
[1]: https://github.com/NixOS/nixpkgs/commit/41bd6d2614749d12ce5ded3e991555b56ea6b2dc
[2]: https://github.com/NixOS/nixpkgs/commit/abf60791e2bd274d39e0f18def46795798f9aefd
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @Profpatsch
|
|
|
|
| |
I shouldn't be working today I think.
|
|
|
|
| |
Duh.
|
|
|
|
|
| |
Replacing the simple inclusion of some programs in packages with
their respective programs.* equivalent.
|
|
|
|
| |
Aquired by Zoom, no thanks.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The patch I added to xournal was for keeping the aspect ratio when
annotating PDFs with images. However, looking at xournal++ the aspect
ratio is kept by default when resizing via corners so the patch is not
needed.
Since I don't really care a lot whether it's xournal or xournal++ and as
long as it does the very little things I intend to use it for, I don't
mind if it has too many features for my taste.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
| |
Knew I forgot something in the last clean-up.
|
|
|
|
| |
Still a continuation of some housekeeping.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In 7faaaab0af1e30bdfb72eca02abdfe92efefe4e0, I've changed the TERM
variable to contain "xterm-256color".
However, in our shell initialisation, we check whether $TERM is "xterm"
rather than whether $TERM *starts* with xterm.
Doing the latter fixes title setting and home/end keys in Vi normal
mode.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
| |
So far I've been fine with just everything using 16 colours, but since
I'm even using 256 colours in my own ASCII art spriting engine I think I
can safely enter the 90ies and get some more colours.
Of course, the XTerm version I'm using is already supporting 256 colors,
it's just that the terminfo entry doesn't say so.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
A while ago, p7zip has been marked as insecure[1], and while I didn't
use p7zip for any real archives, I used it for unrelated things like
executables and ISO9660 images and of course occasionally also 7z files.
While I haven't done extensive testing with unar, it does seem to have a
similar feature set when it comes to non-archive formats and also has
support for 7z archives as well.
[1]: https://github.com/NixOS/nixpkgs/commit/aa80b4780d849a00d86c28d6b3c
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
| |
The option has been renamed[1] from just "docker-containers" to
"virtualisation.oci-containers.containers", so our checks no longer
evaluate.
[1]: https://github.com/NixOS/nixpkgs/commit/2f7747526cc80844a506c4aa147
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
| |
Unfortunately, development has seemingly ceased and has been marked as
insecure in aa80b4780d849a00d86c28d6b3c78a777dd02e9a.
|
| |
|
|
|
|
| |
Headless server for the drawpile shared drawing application.
|
|
|
|
|
|
|
| |
With the merge of [1], the `.enable` check for
`config.services.dokuwiki` has been removed.
[1]: https://github.com/NixOS/nixpkgs/pull/83769
|
|
|
|
|
|
|
| |
This option has been dropped upstream in
4732f59226a21b01d630c7ef4fb884bbfbe7dc83
Cc: @aszlig
|