| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| | |
|
| |
|
|
| |
This should do the trick.
|
| |
|
|
| |
Argh
|
| | |
|
| |
|
|
|
|
|
|
| |
The hydra still doesn’t like the import:
error: "\u001b[31;1merror:\u001b[0m\u001b[34;1m --- RestrictedPathError --- hydra-eval-jobs\u001b[0m\naccess to path '\u001b[33;1m/nix/store/b6ba70kcrvnxq165h791l71wvmdj2qy1-prepare-tvl\u001b[0m' is forbidden in restricted mode"
So let’s try this.
|
| | |
|
| | |
|
| |
|
|
|
| |
We don’t want any builtins.fetchgit stuff from random domains,
hopefully this will fix the current eval error.
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
This pulls in tvl, since the blog ist mostly over there.
It uses `fetchGit`, so caveats may apply. It shouldn’t increase
evaluation times very much, since the blog only uses a small subset of
tvl.
https://github.com/openlab-aux/vuizvui/issues/50 might apply.
|
| | |
|
| |
|
|
|
|
| |
Also make sure libreoffice is only installed/pulled when clicking on
the link (although there could be a popup of sorts if it has to do
stuff …).
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
This uses the system monospace font to generate a PDF. Before the
printer would be sent a .txt, and it varies from printer to printer
how plain text files are typeset (if at all). Now it only depends on
the system monospace font, which is SourceCode Pro in my case (obvious
TODO is to fix that sometime, or make it configurable).
|
| | |
|
| |
|
|
|
| |
Sync the calendar every 15 minutes with a user service, and add ics
file support to xdg-open.
|
| |
|
|
|
|
|
|
|
|
|
| |
calling `execlineb -c` has unfortunate quoting issues, cause for
cornercases like arguments that contain spaces or `"` the result would
be a completely broken command line.
Instead, let’s do our own block construction in a small rust
program (for speed). I tried implementing it in bash first but even
prepending spaces to a string is a complete waste of time in that
language.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Similar to 4701a995cb865c5d7178f574a3eae5872595e768, where I replaced
the libtidy alias for html-tidy because it broke evaluation of the PSI
test, I found another test for nman which uses an alias.
The background is that aliases are now[1] no longer allowed in NixOS VM
tests and since "s6PortableUtils" is indirectly referenced, we get an
evaluation error on Hydra.
Using the unaliased name fixes evaluation and should not change anything
in functionality.
[1]: https://github.com/NixOS/nixpkgs/commit/3edde6562e19698da69a499881e0a2e4f5a497a2
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @Profpatsch
|
| |
|
|
|
|
|
|
|
| |
Since this package is introduced via an overlay expression pulled in via
IFD, I can't really fix it. Since dhall-flycheck has already been
removed from all machines it was a part of, just remove it completely to
migitate this issue.
cc @Profpatsch
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
A simple text letter formatter (A4) for printing.
|
| |
|
|
|
|
| |
The concept of a transparent handler wasn’t actually used anywhere and
now that we want to generate the firefox json as well, it just hinders
us from doing that in an easy way.
|
| |
|
|
|
|
| |
The type string would blow up too much if you can’t reference any
dhall file in the sources list. This all feels a bit hacky, but at
least semantically it seems to work out?
|
| |
|
|
|
|
|
| |
No use in passing through the mime type now that we can just directly
render the commands in the protocol handlers.
This gives us the base for generating the Firefox handlers.json.
|
| |
|
|
| |
Removes the duplication of command handlers.
|
| |
|
|
|
|
|
|
|
| |
This diff is a bit bad cause of whitespace changes, but effectively
this copies all handlers into the mime handler definitions and
duplicates them for now.
We want to use the same config to generate a firefox mime handler
file.
|
| | |
|
| |
|
|
|
|
| |
testRustSimple wouldn’t work with all the rust functions, so let’s
just use it internally and expose the tests via the conventional
`doCheck` attribute instead.
|
| |
|
|
| |
Just to prove I can.
|
| |
|
|
|
|
|
|
| |
The -T flag is GNU coreutils specific, for s6-ln and POSIX ln, the equivalent
seems to be -L which mandates behavior like linkat(3) with the AT_SYMLINK_FOLLOW
flag.
cc @Profpatsch
|
| | |
|
| |
|
|
| |
It was unused and required a broken hnix pin.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
I think nman is of general interest, so general pointers on setting
it up may be useful for others.
|
