summary refs log tree commit diff
path: root/pkgs/os-specific
Commit message (Collapse)AuthorAge
* util-linux: Clean up to use less bashJohn Ericson2018-08-02
|
* treewide: Remove stdenv.isCrossJohn Ericson2018-08-02
| | | | | | | I *want* cross-specific overrides to be verbose, so I rather not have this shorthand. This makes the syntactic overhead more proportional to the maintainence cost. Hopefully this pushes people towards fewer conditionals and more abstractions.
* Merge pull request #43637 from qolii/hardkernel_update_and_defconfigxeji2018-08-01
|\ | | | | linux-hardkernel: 4.14.47-139 -> 4.14.55-146. Additionally, use vendo…
| * linux-hardkernel: 4.14.47-139 -> 4.14.55-146. Additionally, use vendor ↵qoli2018-07-16
| | | | | | | | defconfig.
* | beegfs: 6.18 -> 7.0 (#44210)markuskowa2018-07-30
| |
* | linux: 4.18-rc6 -> 4.18-rc7Tim Steinbach2018-07-29
| |
* | libsemanage, libselinux: fix meta.outputsToInstallAmineChikhaoui2018-07-30
| | | | | | | | | | | | Same as 57b9719e4cf601c617f02f59365e7218eefb9b0f. +libselinux from vcunat - was probably not breaking but confusing anyway. Close #44212.
* | checkpolicy: fix bad meta.outputsToInstallVladimír Čunát2018-07-29
| | | | | | | | | | | | | | This was silently blocking the channels. Thanks amine* from IRC. Maybe inheriting whole meta should be avoided and particular attributes should be picked instead, as e.g. adding longDescription would have unexpected consequences as well.
* | Merge pull request #43982 from viric/viric_cleanviric2018-07-29
|\ \ | | | | | | Take me (viric) out of most maintenance
| * \ Merge remote-tracking branch 'central/master' into viric_cleanLluís Batlle i Rossell2018-07-28
| |\ \
| * | | Take me (viric) out of most maintenanceLluís Batlle i Rossell2018-07-22
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Since years I'm not maintaining anything of the list below other than some updates when I needed them for some reason. Other people is doing that maintenance on my behalf so I better take me out but for very few packages. Finally!
* | | | linux: 4.17.10 -> 4.17.11Tim Steinbach2018-07-28
| | | |
* | | | linux: 4.14.58 -> 4.14.59Tim Steinbach2018-07-28
| | | |
* | | | linux: 4.9.115 -> 4.9.116Tim Steinbach2018-07-28
| | | |
* | | | linux: 4.4.144 -> 4.4.145Tim Steinbach2018-07-28
| | | |
* | | | iwd: 0.3 -> 0.4Vladyslav Mykhailichenko2018-07-26
| |/ / |/| |
* | | fuse: 2.9.7 -> 2.9.8 (security, CVE-2018-10906)Michael Weiss2018-07-25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Upstream changelog: - SECURITY UPDATE: In previous versions of libfuse it was possible to for unprivileged users to specify the allow_other option even when this was forbidden in /etc/fuse.conf. The vulnerability is present only on systems where SELinux is active (including in permissive mode). - libfuse no longer segfaults when fuse_interrupted() is called outside the event loop. - The fusermount binary has been hardened in several ways to reduce potential attack surface. Most importantly, mountpoints and mount options must now match a hard-coded whitelist. It is expected that this whitelist covers all regular use-cases. - Fixed rename deadlock on FreeBSD.
* | | fuse3: 3.2.4 -> 3.2.5 (security, CVE-2018-10906)Michael Weiss2018-07-25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Upstream changelog: - SECURITY UPDATE: In previous versions of libfuse it was possible to for unprivileged users to specify the allow_other option even when this was forbidden in /etc/fuse.conf. The vulnerability is present only on systems where SELinux is active (including in permissive mode). - The fusermount binary has been hardened in several ways to reduce potential attack surface. Most importantly, mountpoints and mount options must now match a hard-coded whitelist. It is expected that this whitelist covers all regular use-cases. - Added a test of seekdir to test_syscalls. - Fixed readdir bug when non-zero offsets are given to filler and the filesystem client, after reading a whole directory, re-reads it from a non-zero offset e. g. by calling seekdir followed by readdir.
* | | Merge pull request #43892 from periklis/skhd-updateDaiderd Jordan2018-07-25
|\ \ \ | | | | | | | | skhd: bump 0.1.1 to 0.2.2
| * | | skhd: bump 0.1.1 to 0.2.2Periklis Tsirakidis2018-07-25
| | | |
* | | | linux: 4.17.9 -> 4.17.10Tim Steinbach2018-07-25
| | | |
* | | | linux: 4.14.57 -> 4.14.58Tim Steinbach2018-07-25
| | | |
* | | | linux: 4.9.114 -> 4.9.115Tim Steinbach2018-07-25
| | | |
* | | | linux: 4.4.143 -> 4.4.144Tim Steinbach2018-07-25
|/ / /
* | | util-linux: No more crossAttrsJohn Ericson2018-07-24
| | | | | | | | | | | | More cleanup will come later
* | | kmod: Remove crossAttrsJohn Ericson2018-07-24
| | | | | | | | | | | | Issue #21191 is indeed fixed now.
* | | Merge pull request #44065 from Ericson2314/no-crossAttrs-masterJohn Ericson2018-07-24
|\ \ \ | | | | | | | | treewide: Remove some crossAttrs
| * | | jom: Remove crossAttrsJohn Ericson2018-07-24
| | | | | | | | | | | | | | | | Untested, but I don't think this has ever built.
| * | | hurd: Remove cross attrsJohn Ericson2018-07-24
| | | |
| * | | gnu mig: Remove crossAttrsJohn Ericson2018-07-24
| | | |
* | | | skarnet software: add Profpatsch as maintainerProfpatsch2018-07-25
| | | |
* | | | skarnet software: rename attributes and split outputsProfpatsch2018-07-25
|/ / / | | | | | | | | | | | | | | | Change the attribute names of camelCased utils to kebab-case to improve consistency. Split every package into multiple outputs where possible.
* | | kernel: Reduce peak disk usage during buildTuomas Tynkkynen2018-07-24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Since commit f620b1b693ec25af, the build directory is located inside the source directory. Thus, the `cp -dpR` copies gigabytes worth of .o files only to be deleted later on when we trim all non-essential files from `$dev/lib/modules/${modDirVersion}/source/` thus causing a significant amount of wasted I/O and peak disk usage. As `cp` doesn't come with a `--exclude` flag, use rsync. And throw out the Documentation folder while at it.
* | | kernel: Respect makeFlagsArray in more placesTuomas Tynkkynen2018-07-24
| | | | | | | | | | | | It's used two lines above, so be consistent.
* | | kernel: Remove dead codeTuomas Tynkkynen2018-07-24
| | | | | | | | | | | | It's set in the same phase
* | | kernel: Remove empty preUnpackTuomas Tynkkynen2018-07-24
| | |
* | | Merge staging-next into master (#44009)Frederik Rietdijk2018-07-24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * substitute(): --subst-var was silently coercing to "" if the variable does not exist. * libffi: simplify using `checkInputs` * pythonPackges.hypothesis, pythonPackages.pytest: simpify dependency cycle fix * utillinux: 2.32 -> 2.32.1 https://lkml.org/lkml/2018/7/16/532 * busybox: 1.29.0 -> 1.29.1 * bind: 9.12.1-P2 -> 9.12.2 https://ftp.isc.org/isc/bind9/9.12.2/RELEASE-NOTES-bind-9.12.2.html * curl: 7.60.0 -> 7.61.0 * gvfs: make tests run, but disable * ilmbase: disable tests on i686. Spooky! * mdds: fix tests * git: disable checks as tests are run in installcheck * ruby: disable tests * libcommuni: disable checks as tests are run in installcheck * librdf: make tests run, but disable * neon, neon_0_29: make tests run, but disable * pciutils: 3.6.0 -> 3.6.1 Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/pciutils/versions. * mesa: more include fixes mostly from void-linux (thanks!) * npth: 1.5 -> 1.6 minor bump * boost167: Add lockfree next_prior patch * stdenv: cleanup darwin bootstrapping Also gets rid of the full python and some of it's dependencies in the stdenv build closure. * Revert "pciutils: use standardized equivalent for canonicalize_file_name" This reverts commit f8db20fb3ae382eba1ba2b160fe24739f43c0bd7. Patching should no longer be needed with 3.6.1. * binutils-wrapper: Try to avoid adding unnecessary -L flags (cherry picked from commit f3758258b8895508475caf83e92bfb236a27ceb9) Signed-off-by: Domen Kožar <domen@dev.si> * libffi: don't check on darwin libffi usages in stdenv broken darwin. We need to disable doCheck for that case. * "rm $out/share/icons/hicolor/icon-theme.cache" -> hicolor-icon-theme setup-hook * python.pkgs.pytest: setupHook to prevent creation of .pytest-cache folder, fixes #40273 When `py.test` was run with a folder as argument, it would not only search for tests in that folder, but also create a .pytest-cache folder. Not only is this state we don't want, but it was also causing collisions. * parity-ui: fix after merge * python.pkgs.pytest-flake8: disable test, fix build * Revert "meson: 0.46.1 -> 0.47.0" With meson 0.47.0 (or 0.47.1, or git) things are very wrong re:rpath handling resulting in at best missing libs but even corrupt binaries :(. When we run patchelf it masks the problem by removing obviously busted paths. Which is probably why this wasn't noticed immediately. Unfortunately the binary already has a long series of paths scribbled in a space intended for a much smaller string; in my testing it was something like lengths were 67 with 300+ written to it. I think we've reported the relevant issues upstream, but unfortunately it appears our patches are what introduces the overwrite/corruption (by no longer being correct in what they assume) This doesn't look so bad to fix but it's not something I can spend more time on at the moment. -- Interestingly the overwritten string data (because it is scribbled past the bounds) remains in the binary and is why we're suddenly seeing unexpected references in various builds -- notably this is is the reason we're seeing the "extra-utils" breakage that entirely crippled NixOS on master (and probably on staging before?). Fixes #43650. This reverts commit 305ac4dade5758c58e8ab1666ad0197fd305828d. (cherry picked from commit 273d68eff8f7b6cd4ebed3718e5078a0f43cb55d) Signed-off-by: Domen Kožar <domen@dev.si>
* | | linux: 4.18-rc5 -> 4.18-rc6Tim Steinbach2018-07-22
| | |
* | | linux: 4.17.8 -> 4.17.9Tim Steinbach2018-07-22
| | |
* | | linux: 4.14.56 -> 4.14.57Tim Steinbach2018-07-22
| | |
* | | linux: 4.9.113 -> 4.9.114Tim Steinbach2018-07-22
| | |
* | | linux: 4.4.142 -> 4.4.143Tim Steinbach2018-07-22
|/ /
* | batman-adv: 2018.1 -> 2018.2Franz Pletz2018-07-22
| |
* | alfred: 2018.1 -> 2018.2Franz Pletz2018-07-22
| |
* | Merge staging-next into masterFrederik Rietdijk2018-07-22
|\ \
| * \ Merge master into staging-nextFrederik Rietdijk2018-07-21
| |\ \
| * \ \ Merge master into staging-nextFrederik Rietdijk2018-07-19
| |\ \ \
| * \ \ \ Merge staging-next into stagingFrederik Rietdijk2018-07-16
| |\ \ \ \
| * \ \ \ \ Merge branch 'master' into stagingRobert Schütz2018-07-15
| |\ \ \ \ \
| * \ \ \ \ \ Merge master into stagingFrederik Rietdijk2018-07-13
| |\ \ \ \ \ \