summaryrefslogtreecommitdiffstats
path: root/pkgs/os-specific
AgeCommit message (Collapse)Author
7 daysmicrocode-intel: Add Felix Singer as maintainerFelix Singer
Signed-off-by: Felix Singer <felixsinger@posteo.net>
7 dayszfs: Fix bash completions with 2.1Will Fancher
7 daysraspberrypifw: 1.20240529 -> 1.20240902 (#339030)Nick Cao
7 daysClean up cross bootstrapping, take 2 (#321525)John Ericson
7 daysMerge master into staging-nextgithub-actions[bot]
7 daysnixos-rebuild: Fix repl with channels (#332705)Aleksana
7 daysClean up cross bootstrappingJohn Ericson
For a long time, we've had `crossLibcStdenv`, `*Cross` libc attributes, and `*bsdCross` pre-libc package sets. This was always bad because having "cross" things is "not declarative": the naming doesn't reflect what packages *need* but rather how we *provide* something. This is ugly, and creates needless friction between cross and native building. Now, almost all of these `*Cross` attributes are gone: just these are kept: - Glibc's and Musl's are kept, because those packages are widely used and I didn't want to risk changing the native builds of those at this time. - generic `libcCross`, `theadsCross`, and friends, because these relate to the convolulted GCC bootstrap which still needs to be redone. The BSD and obscure Linux or freestnanding libcs have conversely all been made to use a new `stdenvNoLibc`, which is like the old `crossLibcStdenv` except: 1. It usable for native and cross alike 2. It named according to what it *is* ("a standard environment without libc but with a C compiler"), rather than some non-compositional jargon ("the stdenv used for building libc when cross compiling", yuck). I should have done this change long ago, but I was stymied because of "infinite recursions". The problem was that in too many cases we are overriding `stdenv` to *remove* things we don't need, and this risks cyles since those more minimal stdenvs are used to build things in the more maximal stdenvs. The solution is to pass `stage.nix` `stdenvNoCC`, so we can override to *build up* rather than *tear down*. For now, the full `stdenv` is also passed, so I don't need to change the native bootstraps, but I can see this changing as we make things more uniform and clean those up. (adapted from commit 51f1ecaa59a3b7c182b24e71a3176c83d6cd601e) (adapted from commit 1743662e55669081056743f22f6e616588061cba)
7 daysMerge master into staging-nextgithub-actions[bot]
7 daysmaintainers: remove kierdavisKier Davis
8 dayslinuxPackages.nullfs: init at 0.17Callum Leslie
8 daysMerge master into staging-nextgithub-actions[bot]
8 dayszfs_2_2: 2.2.5 -> 2.2.6 (#339696)Adam C. Stephens
8 daysprl-tools: init Rosetta support (#334661)codgician
prl-tools: install prlbinfmtconfig
9 dayszfs_2_2: 2.2.5 -> 2.2.6Andrew Marshall
- This release brings official support for Kernel 6.10 - Also update zfs_unstable as it would otherwise lag behind - Upstream now links `zpool` completion, so only do so on older zfs (since we still need to support 2.1.x) Changelog: https://github.com/openzfs/zfs/releases/tag/zfs-2.2.6
9 daysMerge master into staging-nextgithub-actions[bot]
9 daysKernel updates for 2024-09-04 (#339536)K900
9 daysMerge master into staging-nextgithub-actions[bot]
9 daysraycast: 1.81.2 -> 1.82.0DontEatOreo
Changelog: https://www.raycast.com/changelog/1-82-0
9 dayslinux_4_19: 4.19.320 -> 4.19.321K900
9 dayslinux_5_4: 5.4.282 -> 5.4.283K900
9 dayslinux_5_10: 5.10.224 -> 5.10.225K900
9 dayslinux_5_15: 5.15.165 -> 5.15.166K900
9 dayslinux_6_1: 6.1.107 -> 6.1.108K900
9 dayslinux_6_6: 6.6.48 -> 6.6.49K900
9 dayslinux_6_10: 6.10.7 -> 6.10.8K900
9 daysMerge remote-tracking branch 'origin/master' into staging-nextK900
10 dayslibtraceevent: 1.8.2 -> 1.8.3 (#329910)Sandro
10 dayslibtracefs: 1.7.0 -> 1.8.1 + other updates (#332184)Sandro
10 dayscpupower-gui: fix crash when freq is set (#337180)Aleksana
10 dayszfs: fix maybe getting wrong kernel in latestCompatibleLinuxPackages (#339238)Adam C. Stephens
10 dayspower-profiles-daemon: move to pkgs/by-namer-vdp
10 dayspower-profiles-daemon: reformat with nixfmtr-vdp
10 dayszfs: fix maybe getting wrong kernel in latestCompatibleLinuxPackagesAndrew Marshall
E.g. might have gotten -rt, -xanmod, etc.
10 daysMerge master into staging-nextgithub-actions[bot]
10 dayspower-profiles-daemon: 0.21 -> 0.22K900
Diff: https://gitlab.freedesktop.org/upower/power-profiles-daemon/-/compare/0.21...0.22
11 daysMerge master into staging-nextgithub-actions[bot]
11 dayslinux_xanmod, linux_xanmod_latest: 2024-08-29 (#338803)Fabián Heredia Montiel
11 dayspam_rssh: 1.1.0 -> 1.2.0-rc2Majiir Paktu
11 daysMerge master into staging-nextgithub-actions[bot]
11 daysraspberrypifw: 1.20240529 -> 1.20240902R. Ryantm
11 daysintel-compute-runtime: 24.26.30049.6 -> 24.31.30508.7R. Ryantm
12 daysMerge master into staging-nextgithub-actions[bot]
12 dayszenmonitor: 2.0.0 -> unstable-2024-05-21 and new srcArtturin
Old src disappeared, diffed old src and new src and it's okay
12 daysMerge branch 'master' into staging-nextJan Tojnar
12 daysLinux kernels 2024-09-01 (#338784)Maximilian Bosch
12 dayslinux_xanmod_latest: 6.10.6 -> 6.10.7Mathias Zhang
12 dayslinux_xanmod: 6.6.47 -> 6.6.48Mathias Zhang
12 daysMerge staging-next into staginggithub-actions[bot]
12 daysutm: 4.5.3 -> 4.5.4 (#338560)Weijia Wang
12 dayslinux_rpi{02w,1,2,3,4}: Add dtb for rpi-zero-2-wJulius Michaelis
Given that linux_rpi02w exists (as an alias for linux_rpi3), not having the dtb makes little sense