Tuomas Tynkkynen
Tuomas Tynkkynen
Yup. https://github.com/madjar/nox/pull/86
Travis additionally does the nixpkgs evaluation checks with `nix-build pkgs/top-level/release.nix -A tarball` and also builds of the manuals.
Note that `canberra` seems to be some sort of sound event library, so most likely that message isn't related to the application looking ugly...
IIRC I read somewhere that Ted Ts'o (the ext4 maintainer) suggested in the dpkg mailing lists to use `sync_file_range()` on every modified/new file, then followed by `fsync()` on every modified/new...
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=605009 it seems. I don't know if that's actually implemented in dpkg, would have to check the source. Yes, `sync_file_range()` is an optimization only (even in Linux!), so simply `#ifdef`'ing...
Yeah, probably the installer should bail out if SELinux is enforcing (at least for now).
The `getenforce` command should be better for scripting. Perhaps: ```` getenforce=$(PATH=$PATH:/sbin:/usr/sbin command -v getenforce) if [ -n "$getenforce" ] && [ "$($getenforce)" = Enforcing ]; then echo "No multi-user for...
Because I personally don't know anything about writing SELinux rules for Fedora (nor CentOS for that matter. Don't you also need something to allow systemd to use socket activation for...
Yes, that sounds good. I think we still need some quick solution for Nix 2.1.
A probable cause is that `--remove-needed` doesn't update the symbol versioning table. I have some WIP patches that I might get finished at some point...