This repository has been archived by the owner on Apr 12, 2021. It is now read-only.
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: NixOS/nixpkgs-channels
base: 95b35a2514ff
Could not load branches
Nothing to show
Could not load tags
Nothing to show
{{ refName }}
default
...
head repository: NixOS/nixpkgs-channels
compare: bfa2452dc83c
Could not load branches
Nothing to show
Could not load tags
Nothing to show
{{ refName }}
default
- 11 commits
- 67 files changed
- 7 contributors
Commits on Apr 27, 2020
-
dotnet: add initial support for arm64
`jellyfin` appeared unsupported on `aarch64` due to `dotnet` platform support in nixpkgs, but there are ARM64 downloads of the `dotnet` SDKs available. This change follows the kind of pattern used in the `firecracker` packaging to support selective x86_64/arm64 downloads. With this change I can build `jellyfin` on a Raspberry Pi 4. The other content hashes have been filled in, and all build successfully, but they have not been further tested.
Configuration menu - View commit details
-
Copy full SHA for 3e98f66 - Browse repository at this point
Copy the full SHA 3e98f66View commit details
Commits on Apr 28, 2020
-
Configuration menu - View commit details
-
Copy full SHA for e89e2ed - Browse repository at this point
Copy the full SHA e89e2edView commit details -
libusb: point alias to libusb1
Until recently, libusb-compat propagated libusb1 and many packages unknowingly used it to obtain libusb1. When NixOS/nixpkgs#82944 removed this evil propagation, it broke many packages with such incorrect assumption. This patch trades the breakage of packages wanting libusb1 caused by the PR for a hopefully less common breakage of the packages relying on the compat library.
Configuration menu - View commit details
-
Copy full SHA for 45edbeb - Browse repository at this point
Copy the full SHA 45edbebView commit details -
chromium: 81.0.4044.122 -> 81.0.4044.129
https://chromereleases.googleblog.com/2020/04/stable-channel-update-for-desktop_27.html This update includes 2 security fixes. CVEs: CVE-2020-6462 CVE-2020-6461
Configuration menu - View commit details
-
Copy full SHA for db4aece - Browse repository at this point
Copy the full SHA db4aeceView commit details
Commits on Apr 29, 2020
-
fish-shell/fish-shell@3.1.1...3.1.2 "This release of fish fixes a major issue discovered in fish 3.1.1: Commands such as `fzf` and `enhancd`, when used with `eval`, would hang. `eval` buffered output too aggressively, which has been fixed."
Configuration menu - View commit details
-
Copy full SHA for 7a15b60 - Browse repository at this point
Copy the full SHA 7a15b60View commit details -
Configuration menu - View commit details
-
Copy full SHA for d21cc14 - Browse repository at this point
Copy the full SHA d21cc14View commit details -
Configuration menu - View commit details
-
Copy full SHA for a6dc21f - Browse repository at this point
Copy the full SHA a6dc21fView commit details -
Configuration menu - View commit details
-
Copy full SHA for d67d074 - Browse repository at this point
Copy the full SHA d67d074View commit details -
Configuration menu - View commit details
-
Copy full SHA for 6015d03 - Browse repository at this point
Copy the full SHA 6015d03View commit details -
Configuration menu - View commit details
-
Copy full SHA for 2b5e2ff - Browse repository at this point
Copy the full SHA 2b5e2ffView commit details -
Merge pull request #86206 from primeos/chromium
chromium: 81.0.4044.122 -> 81.0.4044.129
Configuration menu - View commit details
-
Copy full SHA for bfa2452 - Browse repository at this point
Copy the full SHA bfa2452View 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 95b35a2514ff...bfa2452dc83c