| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
| |
Apparently nginx resolves localhost to [::1] in a newer version by defaul, yet
my static file server only binds to 127.0.0.1.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Get rid of the annoying build error again (see 8be3704c3fbe08308132d92a6
for the last time), but this time for searx 0.13.1.
The main thing that has changed is that instead of hmac.new() there is
now a helper function called new_hmac(), which the patch now uses.
I've also cleaned up some tiny bits reported by flake8 and fixed the
description of SecretAppKeyError to refer to XDG_CACHE_HOME instead of
XDG_CACHE_DIR.
In addition to the updated patch, we now need to add XDG_CACHE_HOME to a
writable directory (in this case $TMPDIR), because otherwise the
test_webapp fails with an SecretAppKeyError, as it will try to create
leading directories to XDG_CACHE_HOME.
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @Profpatsch
|
| | |
|
| |
|
|
|
| |
The wlp-supplicant module is just too buggy (especially after waking from
standby it mostly doesn’t reinitialize the connection).
|
| |
|
|
| |
That’s from back when I wasn’t accustomed to the module system yet.
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
This build error is quite annoying, so I applied the patch on v0.11.0
and rebased it against v0.12.0. The only hunk that's failing is the
import of get_secret_app_key in searx/webapp.py, so no big conflicts
with the actual logic of the patch.
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @Profpatsch
|
| |
|
|
|
|
|
|
|
|
|
| |
The config attribute set is recursive, so "vuizvui" within that scope
refers to the "vuizvui" attribute within config directly instead of
using the one from pkgs.
Prepending "pkgs." explicitly to the attribute path now avoids this.
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @Profpatsch
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We no longer use the legacy SSH store protocol for taalo but the new
ssh-ng protocol, which makes the implementation of taalo-build a LOT
less clunky.
It also didn't make sense to have this as a NixOS module when we after
all just emit a static store path without any stuff depending on
configuration options.
The new implementation basically just wraps nix-build and nix-store -r
along with the right NIX_REMOTE variable.
With Nix 1.2 this can also be done with the new "nix build" command
using the --store option, but unfortunately "nix build" doesn't yet have
the same functionality as nix-build.
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @Profpatsch, @bendlas
|
| |
|
|
| |
Patch doesn’t apply, I don’t use it anymore.
|
| |
|
|
| |
My wifi module broke, because the microcode was too old and that option not set.
|
| |
|
|
| |
thx @aszlig
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit 0cfbc3bcd4be9ba3798f1752f82f6ea2d3aba650.
Since NixOS/nixpkgs@ae9d311565d8c790900ebbc0976e447034930112 the addSSL
option is now mutually exclusive to forceSSL.
Turns out that this actually was a bug that got introduced in
NixOS/nixpkgs@a912a6a291eaa5f6a2ad9143c9e276779c357a41.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Cc: @Profpatsch
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
In order to use forceSSL you now also need to use addSSL and there is an
assertion now to check that since NixOS/nixpkgs@a912a6a291eaa5f6a2ad914.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Cc: @Profpatsch
|
| |
|
|
|
|
|
|
|
|
| |
Since NixOS/nixpkgs@c217f48c358db05bd0ad7893e8e3ebabe4784cbe, the searx
package is no longer in pythonPackages but a top-level attribute.
Tested eval by "nix-instantiate machines -A profpatsch.haku.build".
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Cc: @Profpatsch
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
sane has a file called `net.conf` which is a list of hosts that are searched for
remote scanners.
|
| |
|
|
|
| |
Apparently `enableACME` doesn’t generate certificates for the right subdomains
if they are on the same machine in different virtual hosts.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Until now, the config on the actual server was deviating because I changed it
locally.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The package fails because the mtp-jolla.patch was already applied
upstream, see the following build log:
https://headcounter.org/hydra/log/d21f1590i2hs6xhgkdr00906ksnvgxfz-libmtp-1.1.13.drv
This is the upstream commit by @Profpatsch that's now part of libmtp
version 1.1.13:
https://sourceforge.net/p/libmtp/code/ci/8919ebeef58251639454c2394c0274597be3df9c/
Tested by evaluating machines.profpatsch.katara.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Cc: @Profpatsch
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Evaluation error introduced by 736e0da1e251df836b1669ffee80cecfd6bbf0e9.
The attribute "hledger" isn't a top-level pkgs attribute but resides
within haskellPackages.
This fixes evaluation, as tested by:
nix-instantiate machines -A profpatsch.katara.build
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Cc: @Profpatsch
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Hopefully temporarily.
|
| | |
|
