-
-
Notifications
You must be signed in to change notification settings - Fork 104
Comparing changes
Open a pull request
base repository: NixOS/nixpkgs-channels
base: 6450d8c5ca6f
head repository: NixOS/nixpkgs-channels
compare: f3294b93ecb8
Commits on Feb 13, 2019
-
Configuration menu - View commit details
-
Copy full SHA for 0ce675a - Browse repository at this point
Copy the full SHA 0ce675aView commit details
Commits on Feb 18, 2019
-
Configuration menu - View commit details
-
Copy full SHA for 01c8bc8 - Browse repository at this point
Copy the full SHA 01c8bc8View commit details -
Configuration menu - View commit details
-
Copy full SHA for ce4a012 - Browse repository at this point
Copy the full SHA ce4a012View commit details
Commits on Feb 21, 2019
-
Configuration menu - View commit details
-
Copy full SHA for 22c7c4b - Browse repository at this point
Copy the full SHA 22c7c4bView commit details -
linux: Enable support for Self-Encrypting Drives
To quote block/Kconfig: > Builds Logic for interfacing with Opal enabled controllers. > Enabling this option enables users to setup/unlock/lock > Locking ranges for SED devices using the Opal protocol. Without `BLK_SED_OPAL`, it is impossible to resume from sleep when using a locked self-encrypting drive. This configuration option appeared in earlier kernels, but only reached maturity in 4.14 according to discussion at: - Drive-Trust-Alliance/sedutil#90 and - Drive-Trust-Alliance/sedutil#190 This kernel option is enabled in the default kernels shipped with Fedora, Debian, and other mainstream Linux distributions.
Configuration menu - View commit details
-
Copy full SHA for 0ea8c6e - Browse repository at this point
Copy the full SHA 0ea8c6eView commit details -
Configuration menu - View commit details
-
Copy full SHA for 3ad5550 - Browse repository at this point
Copy the full SHA 3ad5550View commit details -
home-assistant-cli: 0.5.0 -> 0.6.0
Robert Schütz committedFeb 21, 2019 Configuration menu - View commit details
-
Copy full SHA for 3382d93 - Browse repository at this point
Copy the full SHA 3382d93View commit details -
abcmidi: 2019.01.01 -> 2019.02.08
Robert Schütz committedFeb 21, 2019 Configuration menu - View commit details
-
Copy full SHA for 255f67e - Browse repository at this point
Copy the full SHA 255f67eView commit details -
Merge pull request #56148 from adamtulinius/morph-v1.2.0
morph: 1.1.0 -> 1.2.0
Configuration menu - View commit details
-
Copy full SHA for 49d9638 - Browse repository at this point
Copy the full SHA 49d9638View commit details -
Configuration menu - View commit details
-
Copy full SHA for 291c809 - Browse repository at this point
Copy the full SHA 291c809View commit details -
Merge pull request #56147 from callahad/linux-kernel-sed
linux: Enable support for Self-Encrypting Drives
Configuration menu - View commit details
-
Copy full SHA for bd3fdc9 - Browse repository at this point
Copy the full SHA bd3fdc9View commit details -
dockerTools: mark store-path-to-layer.sh as executable
bcf54ce introduced a treewide change to use ${stdenv.shell} where-ever possible. However, this broke a script used by dockerTools, store-path-to-layer.sh, as it did not preserve the +x mode bit. This meant the file got put into the store as mode 0444, resulting in a build-time error later on that looked like: xargs: /nix/store/jixivxhh3c8sncp9xlkc4ls3y5f2mmxh-store-path-to-layer.sh: Permission denied However, in a twist of fate, bcf54ce not only introduced this regression but, in this particular instance, didn't even fix the original bug: the store-path-to-layer.sh script *still* uses /bin/sh as its shebang line, rather than an absolute path to stdenv. (Fixing this can be done in a separate commit.) Signed-off-by: Austin Seipp <aseipp@pobox.com>
Configuration menu - View commit details
-
Copy full SHA for c36c048 - Browse repository at this point
Copy the full SHA c36c048View commit details -
Merge pull request #56152 from adamtulinius/k8s-scheduler-missing-res…
…tart nixos/kubernetes: add missing systemd restart options
Configuration menu - View commit details
-
Copy full SHA for 8ef1e41 - Browse repository at this point
Copy the full SHA 8ef1e41View commit details -
Configuration menu - View commit details
-
Copy full SHA for dd269b4 - Browse repository at this point
Copy the full SHA dd269b4View commit details -
postgresql: fix regression in NixOS after update to 11.2 (#56146)
ryantm bot updates `psqlSchema` alongside with version: NixOS/nixpkgs#50646, NixOS/nixpkgs#55860 but `psqlSchema` is used to generate `stateDir`. It shouldn't be updated. Ideally it should be equal to postgresql major version for pg versions, but we already have deployments in /var/lib/postgresql/11.1. Strange why nobody complained when it was changed from 11.0 -> 11.1. I propose do correct naming for PG12+, but status quo for current versions. Fixes NixOS/nixpkgs#56134
Configuration menu - View commit details
-
Copy full SHA for d0d0992 - Browse repository at this point
Copy the full SHA d0d0992View commit details -
Merge pull request #56114 from das-g/owncloud-client-2.5.3
owncloud-client: 2.4.3 -> 2.5.3.11470
Configuration menu - View commit details
-
Copy full SHA for d1a66f6 - Browse repository at this point
Copy the full SHA d1a66f6View commit details -
Configuration menu - View commit details
-
Copy full SHA for ba42e05 - Browse repository at this point
Copy the full SHA ba42e05View commit details -
Merge pull request #55978 from dtzWill/update/udiskie-1.7.7
udiskie: 1.7.5 -> 1.7.7
Configuration menu - View commit details
-
Copy full SHA for 6c5097b - Browse repository at this point
Copy the full SHA 6c5097bView commit details -
Configuration menu - View commit details
-
Copy full SHA for 191eeb4 - Browse repository at this point
Copy the full SHA 191eeb4View commit details -
Configuration menu - View commit details
-
Copy full SHA for b720709 - Browse repository at this point
Copy the full SHA b720709View commit details -
Merge pull request #53873 from tilpner/tahoelafs-update
tahoe-lafs: 1.12.1 -> 1.13.0
Configuration menu - View commit details
-
Copy full SHA for 9c26b10 - Browse repository at this point
Copy the full SHA 9c26b10View commit details -
Configuration menu - View commit details
-
Copy full SHA for f3294b9 - Browse repository at this point
Copy the full SHA f3294b9View commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff 6450d8c5ca6f...f3294b93ecb8