remove the kernel patch, since the package no longer builds the module, its already in the kernel
move it from the kernel function to the main all-packages list
From the Changelog:
* Fixed drag & drop issues on sidebar.
* Fixed starting Tomahawk with a filename as parameter.
* Update column view when collection changes.
* (Linux) Don't crash on environments with invalid locales.
Signed-off-by: devhell <"^"@regexmail.net>
Closes: #9858
Tested-by: aszlig <aszlig@redmoonstudios.org>
Tested-by: David Kleuker <post@davidak.de>
The default options for all file systems currently are
"defaults.relatime", which works well on file systems which support the
relatime option.
Unfortunately, this is not the case for the VirtualBox shared folder
filesystem, so until now, you need to set something like:
fileSystems."/foo" = {
device = "foo";
fsType = "vboxsf";
options = "defaults";
};
Otherwise mounting the file system would fail.
Now, we provide only the "defaults" option to the "vboxsf" file system,
so something like this is enough:
fileSystems."/foo" = {
device = "foo";
fsType = "vboxsf";
};
An alternative to that could be to document that you need to set default
options, but we really should do what users expect instead of forcing
them to look up the documentation as to why this has failed.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
I've been trying to package this a while ago but found out that apart
from the hand-rolled build system a few sources were missing I didn't
continue to work on it.
This was the WIP expression:
https://gist.github.com/aszlig/c271f294410cc5af0f0a
Now, since the latest upstream version, the project uses autoconf and
automake, which makes it very much painless for us.
So now I can watch demoscene videos without getting hearing loss because
of volume differences :-)
Also, this might be useful for beets as well, in case they're going to
move away from using python-audiotools:
https://github.com/sampsyo/beets/issues/1342#issuecomment-86807500
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Unfortunately, we can't test whether USB is really working, but we can
make sure that VirtualBox has access to the USB devices.
This is essentially testing #9736, which I haven't yet been able to
reproduce though, but it makes sense to test it so it won't happen in
future releases.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
