| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Major upstream changes are:
* Ancient Vaults: Players who have completed the main storyline can
visit a mysterious trader on the Outpost who will send them on a
quest to activate and enter the Ancient Gateways found floating in
some systems These gateways provide access to Ancient Vaults:
challenging procedural dungeons left by the ancients, filled with
dangerous guardians (including procedural bosses!) and fantastic lost
technologies.
* Terraforming: Using powerful devices acquired from the Ancient Vaults
along with a new Essence currency, you can now transform regions or
whole planets into entirely different biomes Terraformers can be used
to expand a region across a planet’s surface, replacing natural
blocks, objects and plant life, and eventually changing the type of
the planet itself Microformers are consumable single-use terraformers
which provide even more region types to add to your worlds.
* Weapon Upgrades: Use the ancient anvil available at the end of
Ancient Vaults and spend Essence to upgrade your outdated legendary
weapons, opening up many new options for endgame combat styles
* Elemental Damage: Monsters now have resistance and weakness to
elemental damage types, making your choice of weapons more important
than ever
* Holiday Spirit: Celebrate the holidays with the variety of festive
items bought from Space Santa at the Outpost!
The full changelog can be found at:
http://playstarbound.com/starbound-vault-update/
Tested using the games.starbound NixOS test.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
| |
With the latest patches, this is no longer needed.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
| |
Regression introduced by 4a27d62243942c4be181c7129fb532a709a15a8e.
I've removed the fwbase variable in this commit, so the kernel is unable
to completely load the WiFi firmware.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
| |
After fixing the issues left we had since version 4.8, we can now safely
switch to the latest mainline kernel. Turns out that the system is now a
lot more stable and triggers less warnings and errors in dmesg.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is essentially a backport of @plbossart's "experimental/codecs"
branch against Linux 4.9.
The original repository can be found at:
https://github.com/plbossart/sound/commits/experimental/codecs
Thanks to him for doing a lot of work on getting sound working for these
CherryTrail devices.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is essentially a cherry-pick of the three commits mentioned in:
https://bugs.freedesktop.org/show_bug.cgi?id=97529#c33
Plus a backport against Linux 4.9 of the following patch:
https://bugs.freedesktop.org/attachment.cgi?id=128410
(essentially https://patchwork.freedesktop.org/series/16242/)
And also the backlight.patch (a PMIC hack) we had before all combined
into one patch, which now should fix the following bug:
https://bugs.freedesktop.org/show_bug.cgi?id=97529
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
| |
I need this on all my machines, so nix-env'ing it on every machine on
demand was getting tedious over time.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
Since NixOS/nixpkgs@8b782f4bd43be46e944a6bbac8569667f70478de, the
packagePlatforms function now always returns a platform for
x86_64-linux, but in vuizvui we want to *only* build packages we
explicitly mark so.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
| |
We want to have sandboxed builds and a read-only store. Might make sense
to apply this to all machines in the long term.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
This one is annoying and it seems to be enabled by default in recent Vim
versions, so let's get rid of it.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
| |
Doesn't build since quite a while, so let's mark it as broken until
someone either fixes it or removes it entirely.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Cc: @Profpatsch, @sternenseemann
|
|
|
|
|
|
|
|
|
|
|
| |
This brings tishtushi in par with dnyarri and mmrnmhrm, because the
patch for the BFQ scheduler doesn't apply, while the one we already have
in pkgs.vuizvui.kernel.bfqsched *does* apply.
Besides it doesn't make sense to use different versions of the *same*
patch within the same repository.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
| |
This is needed mostly for the GPUs and for KMS to hopefully work.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I've been patching these machines up since ages and I'm tired now to do
both kernel configs *again* for the recent kernel versions.
Of course, in the long run I still want them to have their customized
kernel, but right now it's better to have a recent generic kernel rather
than have a fucked up custom kernel.
Also, this removes all that cruft for the Intel HDA pinning on dnyarri,
because the machine now has two X-Fi sound cards.
Both machines probably won't boot now, so we'll have to adjust a few
things very soon.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
| |
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
See the release announcement at:
https://lists.gnupg.org/pipermail/gnupg-announce/2016q4/000398.html
Unfortunately we still need the wrapper, because we need to pick up the
PID of the socket endpoint in order to gather various information we can
pass to pinentry (which then for example can recognize that the actual
SSH client is using X or is using a particular TTY).
On the upside however, this is a step into a direction I didn't imagine
to happen anytime soon, given the following statement from Werner Koch
back then:
https://lists.gnupg.org/pipermail/gnupg-devel/2014-November/029104.html
However I don't think the way I'm picking up the PID and doing
inspection of /proc/PID is going to happen in upstream GnuPG anytime
soon. But after cleaning up and doing it as a patch I might now consider
upstreaming it.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
| |
|
|
|
|
| |
oops
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We need to properly separate attrsOf from the nested attrsOf because
otherwise the either type isn't able to distinguish between both types
during merging of the subtypes.
Now we have sub sections which is '[section "subsection"]' in Git's
config syntax and attrsOf (attrsOf ...) on our side and simple sections
like '[section]' which is just a plain attrsOf. This way we have an
additional type constraint in that we can't mix up subsections with
sections by the same name.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
| |
This reverts commit 1fb2981f660b2155331cdac1b28640ba7c6b4786.
Since NixOS/nixpkgs@c67a7ee73156796187894c63386b1a78e5902ea5, the
Chromium beta channel builds fine again, so let's go back to beta.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The jackline package only existed in nixpkgs for a short period of time
until it got reverted in
NixOS/nixpkgs@7e0ca08bfa19304b446f860a8899122ef019c51a.
As soon as jackline enters nixpkgs again, this commit can either be
reverted or just left as-is, because it uses pkgs.jackline only if the
attribute exists.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Cc: @sternenseemann
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
As mentioned in the previous commit, kernel patches from
boot.kernelPatches are added to the kernel package via .override.
Unfortunately, .override overrides the function arguments of the
expression referenced from callPackage, so having the patches inside the
package expression itself will discard those patches once there is an
override.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The implementation of boot.kernelPatches uses .override and passes back
the original kernelPatches attribute to the patches that are going to be
added from boot.kernelPatches.
However, the T100HA module already uses .override to pass these patches
but without re-using the existing patches. So instead of just adding
preexisting patches to the kernelPatches attribute, let's just switch to
boot.kernelPatches, which should also allow overrides and introspection
from different NixOS modules.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit e27c4cdfbe994a259b77cb4f71c1746552f639f3.
I was wrong about this patch being applied upstream, but it turns out
that somehow both of these patches are opplied twice, so we'll need to
deduplicate the patch list or even better not introduce these duplicates
in the first place.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
| |
The patch doesn't apply because it is already included upstream.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|