Comparing changes
Open a pull request
base repository: NixOS/nixpkgs-channels
base: e758436f9868
head repository: NixOS/nixpkgs-channels
compare: 02dbdcddcd30
- 13 commits
- 14 files changed
- 3 contributors
Commits on Oct 2, 2019
-
gnupatch: rename patch files to match their CVE ids.
This should be a behavior no-op, but it helps vulnix figure out that we are up to date regarding security patches. (cherry picked from commit 2242bb86d1edbdd8083c840d1160349286372fac)
Configuration menu - View commit details
-
Copy full SHA for 41f6a49 - Browse repository at this point
Copy the full SHA 41f6a49View commit details -
libtiff: patch for CVE-2019-6128, CVE-2019-14973
CVE-2019-14973.patch is a manually backported of the upstream patch to work around some minor merge conflicts. (cherry picked from commit a2e1da7367bf2397cb0cd82a1ab6503a9c1fa5aa)
Configuration menu - View commit details
-
Copy full SHA for b7eac27 - Browse repository at this point
Copy the full SHA b7eac27View commit details -
gst-plugins-base,gst_all_1.gst-plugins-base: apply patch for CVE-2019…
…-9928 Refactor the patchPhase management for the package along the way to something more standard. (Cherry pick from 97e4a11b003a5a88397d9a1fc4ee8ce8f006a396 with an extra version of the package to patch in 19.03.)
Configuration menu - View commit details
-
Copy full SHA for 061663a - Browse repository at this point
Copy the full SHA 061663aView commit details -
glibc: patch CVE-2018-11236, CVE-2018-11237
Patches have been imported into nixpkgs and manually edited to avoid merge conflicts on ChangeLog / NEWS files. (cherry picked from commit 17be09a)
Configuration menu - View commit details
-
Copy full SHA for 2aae1c9 - Browse repository at this point
Copy the full SHA 2aae1c9View commit details
Commits on Oct 12, 2019
-
Configuration menu - View commit details
-
Copy full SHA for 1a62ef4 - Browse repository at this point
Copy the full SHA 1a62ef4View commit details -
curl: apply upstream security patch
Partially fixes #70084. Cherry-picked from 19.09's 22b5bbf.
Configuration menu - View commit details
-
Copy full SHA for 8350d25 - Browse repository at this point
Copy the full SHA 8350d25View commit details
Commits on Oct 13, 2019
-
poppler_0_61: add patch for CVE-2019-9959
custom adapted patch to accommodate the openjpeg1/openjpeg2 split that 0.61 still has (cherry picked from commit e6889d4)
Configuration menu - View commit details
-
Copy full SHA for 7240f2f - Browse repository at this point
Copy the full SHA 7240f2fView commit details -
Merge #70278: libtiff: patch for CVE-2019-6128, CVE-2019-14973
...into staging-19.03
Configuration menu - View commit details
-
Copy full SHA for 57bd5f1 - Browse repository at this point
Copy the full SHA 57bd5f1View commit details -
Merge #70273: gnupatch: rename patch files to match their CVE ids
...into staging-19.03
Configuration menu - View commit details
-
Copy full SHA for 7585be8 - Browse repository at this point
Copy the full SHA 7585be8View commit details -
Merge #70285: *gst-plugins-base: patch CVE-2019-9928
...into staging-19.03
Configuration menu - View commit details
-
Copy full SHA for 139e21b - Browse repository at this point
Copy the full SHA 139e21bView commit details -
poppler: add patch for CVE-2019-9959 (PR #71046)
(cherry picked from commit 3fa2864)
Configuration menu - View commit details
-
Copy full SHA for 3475116 - Browse repository at this point
Copy the full SHA 3475116View commit details -
Configuration menu - View commit details
-
Copy full SHA for 72d36be - Browse repository at this point
Copy the full SHA 72d36beView commit details
Commits on Oct 14, 2019
-
Merge branch 'staging-19.03' into release-19.03 (security)
Only x86_64-linux has managed to finish rebuilding so far https://hydra.nixos.org/eval/1548583 but I think that's a sufficient trade-off, given that regressions should be very unlikely.
Configuration menu - View commit details
-
Copy full SHA for 02dbdcd - Browse repository at this point
Copy the full SHA 02dbdcdView 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 e758436f9868...02dbdcddcd30