| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
It was unused and required a broken hnix pin.
|
|
|
|
|
| |
Luckily most people seem to be using Signal nowadays, so I can get rid
of this crap.
|
| |
|
|
|
|
| |
In case pipewire wants it or I want to use the jack shim.
|
|
|
|
|
| |
blueman is annoying me a bit atm and bluetoothctl plus pactl seem to be
enough mostly.
|
| |
|
| |
|
|
|
|
|
| |
Once again PVP causes a configure failure which doesn't translate into a
build failure. Fixed by bumping upstream repository.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We had a bunch of instances of
https://github.com/NixOS/nix/issues/2176,
where nix would exit with a “killed by signal 9” error.
According to Eelco in that issue, this is perfectly normal behaviour
of course, and appears if the last command in a loop closes `stdout`
or `stdin`, then the builder will SIGKILL it immediately. This is of
course also a perfectly fine error message for that case.
It turns out that mainly GNU coreutils exhibit this behaviour …
Let’s see if using a more sane tool suite fixes that.
|
|
|
|
|
|
|
|
|
|
| |
Port of <https://cl.tvl.fyi/c/depot/+/2657>. Original message:
`forstdin` iterates over the tests in the test directory, and by
default it does *not* fail if an inner loop returns an error, unless
`-o okcodes` is given, a list of exit codes that indicate success.
Now it fails if a loop returns ≠ 0.
|
|
|
|
|
| |
Since we pass the config, the home directory config isn’t picked up
anymore, so I need to pass it via `extraConfig`.
|
|
|
|
| |
Let's keep it simple, everything else seems to just end in tears.
|
|
|
|
|
|
| |
Copied whatever Profpatsch is using. 5% seems a little extreme, but with
treshhold 2% tail /dev/zero still froze my laptop for a solid minute and
a half.
|
|
|
|
| |
I actually use this now.
|
| |
|
|
|
|
| |
Hearing a lot of good things lately, time to see what it is about.
|
|
|
|
| |
Sigh.
|
|
|
|
|
| |
So the previous idea didn't work as expected, instead I'm going to use
the directory name Syncthing would use anyway.
|
|
|
|
| |
This reverts commit d46aa4ec882dcb9ac0e09da6e1aecb361d90d287.
|
|
|
|
|
| |
This doesn't seem to work properly, Syncthing will still add its default
`Sync` directory.
|
|
|
|
| |
https://youtu.be/LB8bhHyPLgk?t=418
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
nix-env-diff is a tiny utility which parses and compares the output of
`nix-env -qaP --out-path`, printing all changed and added out paths (or
attributes if desired). This facilitates a simple way to determine
rebuilds or changed reverse dependencies when working on nixpkgs in a
similar way as nixpkgs-review and ofborg do it.
Both the new evaluation and the base evaluation to compare against have
to be created manually using nix-env, which in turn also allows
considering attribute sets that are normally not evaluated do to missing
`lib.recurseIntoAttrs`. As an example, here is an example building all
changed attributes in `ocaml-ng.ocamlPackages_4_12`:
```
nix-env -qaP -A ocaml-ng.ocamlPackages_4_12 --out-path -f . \
| nix-env-diff --attrs ./base-ocamlPackages_4_12 \
| xargs -n 1 -P 4 nix-instantiate --quiet -A \
| xargs nix-store --realise --builders 'ssh://edwin'
```
`./base-ocamlPackages_4_12` contains the result of the `nix-env`
invocation executed on the master branch.
|
|
|
|
|
|
|
|
|
| |
Shared by adisbladis in #nixos-chat this is a very stupid fish function
which bonks a nixpkgs package into the PATH in the current shell. This
is often useful if you need a package ad-hoc and opening a nix-shell is
too much hassle or you find yourself perpetually opening and closing a
nix-shell. Extremely racy with the garbage collector, but this is yolo
ops territory anyways.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Since Tishtushi had a SSD failure and thus became a majoor nuisance to
work with, I got a temporary laptop from someone (since I don't know
whether they want to be mentioned, I leave out their name for now) in
order to be able to be more productive than waiting for several seconds
for a 1 KiB text file to be saved.
Right now, I'm not sure whether any firmware is needed for the temporary
laptop, so this is a hardware configuration just to get started with a
proper Hydra channel.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
| |
For some reason I currently don't have time to investigate, the test has
stopped to recognise the "Register new account" text, because the text
extracted via OCR was "Reg ster new account" (note: without the "i").
Since we're not testing OCR in general and all we really care here in
the test is whether the application starts up, I just changed the "i" to
a "." (any character in regex) to make sure the detection passes.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
| |
The conflicting changes here are largely because of changed context,
except one hunk which is dropped because the "saveAfterCopyPath" no
longer existists in version 0.9.0.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
| |
This is quite useful to the eye.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
These are the scripts I used to print my gpg private key onte a bunch
of A4 papers, as QR codes of the paperkey output.
It also contains an example of how to automatically read it back in
with a ScanSnap „Einzugsscanner“. I think there also was a test that
checks that the full roundtrip works :)
The QR codes generation was designed in a way that they contain the
highest amount of data when printed on A4 paper, while still being
high-redundancy enough that you can destroy about 1/4th of them before
they become unreadable.
The key was also printed as plain paperkey format, so in the worst
case when I don’t have a scanner I can type it in by hand.
|
|
|
|
| |
Do a barrel roll!
|
| |
|
|
|
|
| |
Plus add some other virtualization thingies I can uncomment if I need them.
|
| |
|
|
|
|
| |
why not lol
|
| |
|
|
|
|
| |
Used for IHP development https://ihp.digitallyinduced.com/Guide/index.html
|
| |
|
| |
|
|
|
|
|
|
|
| |
gonic is a modern alternative to mpd, it indexes music directories and
provides a server with a protocol to request files and metadata.
It has an Android app.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
The goal is to be able to have multiple weechat services on one
machine, so a bunch of people can run their weechat clients under
different service users.
|
| |
|
| |
|
| |
|
| |
|