| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Upstream has 30x redirects for some URLs.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The “shallow” parser uses the fact that every netencode value is
length-encoded (or a scalar with a fixed length).
It does not need to parse the inner values in order to get the
structure of the thing.
That means that we can implement very fast structure-based operations,
like “take the first 5 elements of a list” or “get the record value
with the key name `foo`”.
We can even do things like intersperse elements into a list of values
and write the resulting netencode structure to a socket, without ever
needing to copy the data (it’s all length-indexed pointers to bytes).
|
|
|
|
|
| |
Less generic, has the spirit of “netstrings, but extended to a
structured encoding format”.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
https://dotti.me/
DOT-TIME(7) TIME FORMATS DOT-TIME(7)
NAME
dot-time - a universal convention for conveying time
DESCRIPTION
For those of us who travel often or coordinate across many timezones,
working with local time is frequently impractical. ISO8601, in all its
wisdom, allows for time zone designators, but still represents the
hours and minutes as local time, thus making it inconvenient for
quickly comparing timestamps from different locations.
Dot time instead uses UTC for all date, hour, and minute indications,
and while it allows for time zone designators, they are optional infor‐
mation that can be dropped without changing the indicated time. It uses
an alternate hour separator to make it easy to distinguish from regular
ISO8601. When a time zone designator is provided, one can easily obtain
the matching local time by adding the UTC offset to the UTC time.
EXAMPLES
These timestamps all represent the same point in time.
┌─────────────────────┬─────────────────────┐
│ dot time │ ISO8601 │
├─────────────────────┼─────────────────────┤
│ 2019-06-19T22·13-04 │ 2019-06-19T18:13-04 │
├─────────────────────┼─────────────────────┤
│ 2019-06-19T22·13+00 │ 2019-06-19T22:13+00 │
├─────────────────────┼─────────────────────┤
│ 2019-06-19T22·13+02 │ 2019-06-20T00:13+02 │
└─────────────────────┴─────────────────────┘
2019-06-19 DOT-TIME(7)
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Uses the nom parsing combinator library.
|
| |
|
|
|
|
|
|
|
|
|
| |
Change the number format to be more concise, working in steps of 2^n,
going from 2^1 (1 bit) to 2^9 (512 bits), though implementations are
free to define the biggest numbers they want to support.
Records get the marker `{` and are closed by `}`, so parens match up
nicely, similar to lists.
|
| |
|
| |
|
|
|
|
| |
I shouldn't be working today I think.
|
|
|
|
| |
Duh.
|
|
|
|
|
| |
Replacing the simple inclusion of some programs in packages with
their respective programs.* equivalent.
|
|
|
|
| |
Using the wrapper rather than normal.
|
|
|
|
| |
Kinda forgot that just adding the packages is probably not enough.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Recently, the way to add scripts to the mpv wrapper has changed[1] and
instead of using .override, there is now a dedicated wrapMpv function
that can be used to compose the wrapped mpv derivation, similar on how
it's done for wrapFirefox and wrapNeovim.
The change also introduced the following evaluation error when using the
old mpv-with-scripts package:
Use wrapMpv for editing the environment of mpv
Since this evaluation error essentially blocks Vuizvui channel
generation, I decided to fix this, even though I usually try to avoid
touching other people's machine configurations.
[1]: https://github.com/NixOS/nixpkgs/commit/f93918bdc387d353285f458c06c6a111ae90b7b2
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @Profpatsch
|
|
|
|
| |
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.
|
|
|
|
| |
We'll need these to replace docker.
|
|
|
|
| |
Still a continuation of some housekeeping.
|
|
|
|
|
| |
I think I'll switch to `podman` now. I was never a fan of docker needing
a daemon to begin with.
|
| |
|
| |
|
|
|
|
| |
Fixed for newer cow versions
|
|
|
|
|
|
|
|
| |
This is now on par with the original script in
https://github.com/Profpatsch/dotfiles/blob/a25c6c419525bef7ef5985f664b058dc9eb919e9/scripts/scripts/xdg-open
Eventually it should probably migrate away from a generated bash
script, but for now it’s fine.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Like a normal `import`, but for dhall files. `importDhall2` can
additionally handle dependencies and additional source files, though
the interface is not stable yet.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
| |
The import list of list.go has changed upstream, so the rebase of this
patch doesn't change anything in its functionality but just makes sure
that it applies against gopass version 1.9.0.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is quite useful in CSS files and others to directly highlight the
colours in the actual colour value rather than with the generic colour
of the syntax file.
To make sure we don't break the after/syntax files for Haskell and HTML,
I also changed the way we install those files in the output directory so
that if a file already exists, it is appended to rather than
overwritten.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
| |
We essentially only want to have the ftdetect and syntax files,
everything else is just cruft that is not in any way related to Vim.
Ideally we want to do a whitelist approach instead of the "remove
everything unneeded" we're doing right now, but since I don't want to
refactor the whole Vim expression I'll leave it the dirty[TM] way.
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>
|