| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
So far I mostly used this implementation for the games we have packaged,
where we pretty much patch out all commands that execute external
programs.
However in order to be useful in a more generic way, it makes sense to
provide a /bin/sh implementation, especially when you have to deal with
scripting languages.
I'm using dash here, because it's a more minimal implementation rather
than the default shell (bash) we use in nixpkgs and it practically only
needs to be able to run constructs like "/bin/sh -c foo".
Signed-off-by: aszlig <aszlig@nix.build>
|
| |
|
|
|
|
|
|
| |
This machine was used for controlling the LED lighting bars at
Rockfabrik. I no longer work there and the machine has subsequently been
replaced by something else, so I don't need kzerza anymore.
Signed-off-by: aszlig <aszlig@nix.build>
|
| |
|
|
|
|
|
| |
I no longer use last.fm nor do I use this project (even though it's my
own one), so let's remove it.
Signed-off-by: aszlig <aszlig@nix.build>
|
| |
|
|
|
|
|
| |
This option was removed in Linux 5.0, so let's make its absence
non-fatal for the build of the config.
Signed-off-by: aszlig <aszlig@nix.build>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
When writing that module back then in 88a10f1a6e2ea172ff985f64bfcf82e2,
I had to work around a systemd limitation (which I need to check whether
this is still the case today) and hardcoded the user name for the time
being.
While it's still quite ugly, there was interest from @Profpatsch, so I
decided to add an internal option to change that username.
Signed-off-by: aszlig <aszlig@nix.build>
|
| |
|
|
|
| |
This will prevent version pinning and always install the latest and
greatest.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Upstream changes:
* Improved performance in locations with lots of light sources (e.g.
torches).
* Improved performance on farms with lots of animals.
* Tweaked new "H" health icon.
Upstream bug fixes:
* Fixed multiplayer visual glitch when another player uses a tool and
then starts moving in a new direction.
* Fixed "fishing stance" visual glitches in multiplayer.
Signed-off-by: aszlig <aszlig@nix.build>
|
| |
|
|
|
|
|
|
|
|
|
| |
I checked the archives against the previous versions and the contents
match, however the archives themselves had differences with the file
order so the hashes are different now.
In the long term, we probably should use fetchzip instead so we don't
get a hash mismatch if none of the actual contents change.
Signed-off-by: aszlig <aszlig@nix.build>
|
| |
|
|
|
|
|
|
|
|
|
| |
The use of mono50 was just an old relic where I was debugging some issue
with a game, but I used it as a template for packaging other games, so
it spread throughout the code base.
I've tested all these games just to make sure they still work with the
latest version.
Signed-off-by: aszlig <aszlig@nix.build>
|
| |
|
|
|
|
|
|
|
|
| |
The "Product" model expects to have a "supports_canonical" attribute in
the JSON Product object, which since a while is no longer there.
We really don't need that attribute for our purposes, so we can simply
drop the line where we do the lookup.
Signed-off-by: aszlig <aszlig@nix.build>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The object in question to get the response from the Recaptcha widget is
now called "grecaptcha" instead of just "captcha" and the method to call
now is also called "getResponse" instead of "get_response".
Another change is that the grecaptcha object isn't available immediately
once the page is loaded, so I added a try...catch loop for that. I know
it's evil to do that, but I tried to check just for whether grecaptcha
is available and then call the getResponse method but found out that
during object construction there is a small time window where
getResponse is available but isn't a callable method.
There is still another issue with the HB fetcher, but the first step is
hereby fixed.
Signed-off-by: aszlig <aszlig@nix.build>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If taalo-build is used on a Nix expression returning multiple
derivations either by a list or an attribute set, nix-instantiate will
return multiple paths.
Quoting the argument to "nix-store -r" however will pass the newline-
separated files returned by nix-instantiate as one big file name, which
in turn causes the realize to fail.
Removing those quotes doesn't have this problems and we also don't get
into trouble because those paths are under our control and don't contain
spaces or tabs (which would then be splitted by the shell).
Signed-off-by: aszlig <aszlig@nix.build>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I did have a major outage this week, because I was using bcache with
writeback mode on a RAID10 backing storage. Fortunately, I was able to
recover 99.9% of the data (only the most recent stuff wasn't
recoverable), but I certainly don't want this to happen again in the
future.
While I did use bcache with hibernate and writeback, the interesting
part is that the caching device went bonkers after a "normal" shutdown
rather than a suspend/hibernate, with "normal" being "with a bunch of
kernel warnings about zswap". Also, this happened around a btrfs scrub,
so the inconsistency was all over the place.
So first of all, I'm now going with writaround mode rather than
writeback mode for the time being. Although it's slower than writeback,
the chances that I need to do such a recovery again is close to 0% with
writethrough and writearound because all writes are synchronous.
Second, this very change makes sure that whenever the machine goes to
sleep or a scrub is started, the caching is disabled and afterwards it's
re-enabled. That way we shouldn't have lots of trash on the caching
device.
Signed-off-by: aszlig <aszlig@nix.build>
|
| |
|
|
|
|
|
|
| |
I had this in my local configuration.nix since a while and while it
might be annoying when this runs every month, I think it's better to do
it regularily rather than having a dying disk go unnoticed.
Signed-off-by: aszlig <aszlig@nix.build>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Since add_DT_NEEDED_for_dynamic is no longer the default for ld[1],
we'll get a linking error like this:
nix-query.o: undefined reference to symbol '_ZNK3nix5Store22followLinksToStorePathERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE'
Unfortunately, the only way to work around this without re-enabling the
same flag is directly specify dependencies we really *should* not need
to specify because they're a transient dependency of libnixmain.
So for now I'm reverting back to the previous behaviour with
--copy-dt-needed-entries until I got time to look into it in detail.
From the ld(1) manual page:
--copy-dt-needed-entries
--no-copy-dt-needed-entries
This option affects the treatment of dynamic libraries referred to
by DT_NEEDED tags inside ELF dynamic libraries mentioned on the
command line. Normally the linker will add a DT_NEEDED tag to the
output binary for each library mentioned in a DT_NEEDED tag in an
input dynamic library. With --no-copy-dt-needed-entries specified on
the command line however any dynamic libraries that follow it will
have their DT_NEEDED entries ignored. The default behaviour can be
restored with --copy-dt-needed-entries.
This option also has an effect on the resolution of symbols in
dynamic libraries. With the default setting dynamic libraries
mentioned on the command line will be recursively searched,
following their DT_NEEDED tags to other libraries, in order to
resolve symbols required by the output binary. With
--no-copy-dt-needed-entries specified however the searching of
dynamic libraries that follow it will stop with the dynamic library
itself. No DT_NEEDED links will be traversed to resolve symbols.
[1]: https://github.com/NixOS/nixpkgs/commit/bcfe7af84b3628a31bfcc43dde30fc553a73adac
Signed-off-by: aszlig <aszlig@nix.build>
|
| |
|
|
|
|
| |
The currently available VBox version (5.2.22) in nixpkgs does not build
with kernel 4.20, and Vbox 6 is still WIP, so switching to kernel 4.19
for now should hopefully result in VBox being available on my systems.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I refactored the two tools a while ago but eventually rendered
taalo-realize useless, because it doesn't copy the derivation to realize
to the remote host.
This is done now, plus the taalo-build command now makes sure that we
instantiate on the local machine, thus speeding up builds a lot (except
maybe if the local host is under very high load).
In addition I added an indirect gcroot inside a temporary directory, so
that we don't get into a race condition when garbage collecting between
instantiate and realize.
Instead of nix-copy-closure, I now use "nix copy", which properly
supports the ssh-ng store backend. However I didn't use "nix build" and
friends, because these commands still lack a few features.
Signed-off-by: aszlig <aszlig@nix.build>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
I have not yet tested this in production but will do shortly.
Nevertheless, kernel 4.19 should bring a few improvements regarding
hardware support to the table and kernel 4.14 doesn't build anymore with
our BFQ patch, so let's move on :-)
In case the kernel doesn't work, we can still patch it up accordingly.
Signed-off-by: aszlig <aszlig@nix.build>
|
| |
|
|
|
|
|
| |
This reverts commit 292099429d0bab51f0cb634c6bc5c9745c4c1383.
Well, looks like iwd ist still not ready for primetime with my
university's eduroam implementation.
|
| |
|
|
| |
It's time...
|
| |
|
|
|
|
| |
This reverts commit 7415729ff62b9ad5ce5a166c227d5c882094fe6b.
Nope, can't do without VBox right now. Damn work.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Let's try again with geoip2. This time I built and tested it locally
before applying it to vuizvui. All seems well, for now...
|
| |
|
|
|
|
| |
Now, it's not yet clear if iwd will work with my uni's eduroam service
at all. Either way though, this is in preparation for the switch and
test once I'm near an eduroam access point.
|
| |
|
|
| |
For now...
|
| |
|
|
|
| |
Hopefully this is the last package that needs to be disabled for a
successful machine build.
|
| |
|
|
| |
The urge to have a new build is stronger than all the beautiful colors.
|
| |
|
|
|
|
|
|
|
|
| |
Since kernel 4.20, the option no longer exists and it's enabled
unconditionally.
So in order to stay backwards-compatible with older kernels, let's only
enable that option if it actually exists (thus the "?").
Signed-off-by: aszlig <aszlig@nix.build>
|
| |
|
|
|
|
|
|
| |
Since quite a while, NixOS re-uses the passphrases from earlier devices,
so there is no need anymore for such a device in order to unlock
multiple containers with the same passphrase.
Signed-off-by: aszlig <aszlig@nix.build>
|
| |
|
|
|
|
|
| |
The "luksClose" subcommand for cryptsetup has been deprecated for a
while, so let's move over to "close".
Signed-off-by: aszlig <aszlig@nix.build>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Since I got a new SSD for the machine (thanks @cvdnext), I also had the
opportunity to re-create my LUKS containers to LUKS2 with Argon2 key
derivation alongside creating bcache backing devices.
The change in order to support bcache is just a matter of adding
"bcache" to availableKernelModules and we're done.
However, as the storage configuration is not a very common one, I
decided to add a test specific to that to make sure future NixOS updates
won't prevent the machine from booting.
Signed-off-by: aszlig <aszlig@nix.build>
|
| |
|
|
| |
Remove unused packages and commented out stuff.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
