| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
| |
This fixes the build for Tomahawk because some of these dependencies
were already refactored in upstream <nixpkgs> and hence we can simply
specify the dependencies directly.
Alongside of this, I've broken out some of the buildInputs into
nativeBuildInputs, so this will stay safe for cross compilation.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
| |
This reverts commit 267b8363695190f2d0834892b4b1159d7918d447.
Issue NixOS/nixpkgs#15498 is already fixed upstream, so this ugly
workaround isn't needed anymore.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
|
| |
Let's enable the options that *should* work with this kind of hardware
regardless whether it's currently working in mainline. It doesn't make a
huge difference to the kernel configuration prior to this change, but
let's better compile in these options rather than wondering why some
hardware isn't working.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
| |
|
|
|
|
| |
Okay, that didn’t do what I thought it would.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Testing if that improves streaming.
|
| |
|
|
|
|
| |
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
| |
I've copied the notsure config, which wasn't an EFI system, so let's
actually use systemd-boot here, shall we? ;-)
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
| |
This is to get a first working channel for bootstrapping. Fixing the
test is the long-term goal of course, so this is only temporarily.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
| |
Unfortunately, this is currently necessary for the Broadcom wireless
drivers.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
| |
Hardware-specific info largely from nixos-generate-config.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
| |
Just because it doesn't build at the moment and just temporarily.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
| |
This one more or less shares the same profile as "notsure", but I'm too
lazy right now to consolidate and/or modularize everything properly.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
| |
It hasn’t been merged into nixpkgs yet.
|
| |
|
|
|
|
|
|
|
| |
Due to bandwidth constraints I'm not using Tomahawk at the moment and I
don't have time to investigate the current build failure.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
| |
Gah, yes, I'm still waking up and my eyes are not working already...
Accidentally copy & pasted tho wrong hash in there.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
|
| |
Nothing very scary here, just getting things up to date.
This also reflects on my choices of kernel options, most of them
probably are unnecessary but I'm going to rip apart the whole kernel
config very soon[TM] anyway.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
| |
I no longer use VirtualBox on any of my machines anymore, so let's
remove it for good :-)
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
| |
I hate you, gpg-agent. Go die in a fire.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
i3bar seems to close the FD for stderr, so conky will get a broken pipe
error when writing error messages to stderr.
Of course in the long run it's better to log these errors somewhere
where they can be inspected later.
But for now, it's better than terminating i3bar altogether, because
that's really annoying ;-)
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This seems to be related to this bug:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1434986
The problem here is a race condition, because NetworkManager is trying
to pick up the device _before_ the renaming and then fails to correctly
identify it.
Another solution would be to reorder the service unit after the networkd
service, but that would only work well if the interface is plugged in at
boot time and if it's pluggen in/out afterwards we likely have the same
problem again.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I didn't use -rc6 directly but a few commits after the tag.
Within the mainline merges there was torvalds/linux@45209046c47b93fad.
I didn't investigate further why this exactly is a problem other than
freezing the machine shortly after the bootloader hands over control to
the kernel.
Reverting this commit fixes this issue for now until I have time to look
into it.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
|
|
| |
The main user currently doesn't have permissions to use NetworkManager,
because until now I've used a fixed list of APs directly using
wpa_supplicant.conf and disabled NM via configuration.nix.
However for end users it's a bit tedious to manage wireless networks
that way, so let's add user "bla" to the networkmanager group.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
| |
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
| |
Not that this improves anything significant in terms of hardware
support, but I'm debugging on the basis of the -next kernels, so it's
better to stay on latest mainline for the vuizvui builds (current -next
kernels for the last few weeks make the situation even worse).
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
|
|
| |
This one is tracked upstream at systemd/systemd#3632.
I've implemented the workaround proposed by @medhefgo as a patch.
As this module is only for a particular hardware, we won't cause
troubles for other hardware.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
|
| |
This adds a few #ifdefs for Atom platforms, however I don't remember
what exactly it fixed/changed for the T100HA.
Nevertheless it's probably a good idea to optimize for that architecture
because we're going to compile our custom kernel anyway.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
| |
While hacking on Hydra, this gets quite annoying, because all of these
template toolkit files don't get properly highlighted whenever I edit
them, so I always had to set the file type manually.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
|
| |
HTML already is such a verbose markup language, so having 4 spaces just
makes it look even more shifted to the right than it's mostly is.
And in the past I've already set ts=2 sw=2 in HTML files every time I
edited them anyway.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
| |
Only some machines should get the full config (with all packages).
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This is needed to run the OMEMO plugin:
https://github.com/omemo/gajim-omemo
I'm using drvAttrs directly here, so that we can pass
propagatedBuildInputs properly to the wrapper (without duplicating the
dependencies all over the place).
Ideally, this will be fixed in <nixpkgs> but in a much more fine-grained
way in that we are going to have Nix expressions for every single plugin
and its dependencies.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The previous attempts only fixed the KEY_CONSIDERED status line for a
few specific GnuPG functions, but after looking up the GnuPG source code
the status line can happen on virtually *any* function that looks up one
or more keys.
So this time, we're going to add handling of KEY_CONSIDERED to every
single status line handler.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The previous patch didn't handle the KEY_CONSIDERED status at the
correct position, because the status will be returned during signing and
not during verification.
So this time, let's handle it during signing and actually test it (I did
and it worked).
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
| |
| |
| |
| |
| |
| |
| |
| | |
If the nix-instantiate step in taalo-build should fail, we want it to
fail altogether rather than just going on and bailing out very late
(with an exit status of 0) when the readlink call fails.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
GnuPG 2.1.13 has introduced a KEY_CONSIDERED status, which isn't really
picked up well by Gajim:
https://lists.gnupg.org/pipermail/gnupg-announce/2016q2/000390.html
There is also a new NOTATION_FLAGS status, but that shouldn't have an
effect on Gajim.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|/ |
|
|\ |
|
| |
| |
| |
| |
| |
| |
| | |
Docbook XSL got updated in NixOS/nixpkgs@fb893a8, so we need to adjust
the path to the namespace URL to reflect the current version.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
| |
| |
| |
| |
| |
| |
| | |
This also fixes our hack for libxslt.bin, because it has been fixed
upstream at NixOS/nixops@3e823357f3f4825cd24c3361e511a234f6726105.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|