Skip to content
This repository has been archived by the owner on Apr 12, 2021. It is now read-only.
Permalink

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: e3d393e7177e
Choose a base ref
...
head repository: NixOS/nixpkgs-channels
compare: d2f46002829c
Choose a head ref
  • 5 commits
  • 5 files changed
  • 4 contributors

Commits on Nov 3, 2020

  1. linux: 5.4.73 -> 5.4.74

    @NeQuissimus
    NeQuissimus committed Nov 3, 2020
    Copy the full SHA
    fbd345d View commit details
    Browse the repository at this point in the history

  2. salt: 2019.2.4 -> 2019.2.7 

    Fixes: CVE-2020-16846, CVE-2020-17490, CVE-2020-25592
    @mweinelt
    mweinelt committed Nov 3, 2020
    Copy the full SHA
    3488347 View commit details
    Browse the repository at this point in the history

  3. Merge pull request #102646 from mweinelt/20.03/salt 

    [20.03] salt: 2019.2.4 -> 2019.2.7
    @andir
    andir committed Nov 3, 2020
    Copy the full SHA
    fc997fd View commit details
    Browse the repository at this point in the history

  4. chromiumDev: 88.0.4292.2 -> 88.0.4298.4 

    This should also fix VA-API for chromiumBeta (though that part needs
some cleanup). However, chromiumDev likely still fails due to the
absence of dirmd (not included in the tarball so far, we might have to
package and add it as a dependency).

(cherry picked from commit 50a2f50)
    @primeos
    primeos committed Nov 3, 2020
    Copy the full SHA
    90c1c40 View commit details
    Browse the repository at this point in the history

  5. chromium: 86.0.4240.111 -> 86.0.4240.183 

    https://chromereleases.googleblog.com/2020/11/stable-channel-update-for-desktop.html

This update includes 10 security fixes. Google is aware of reports that
an exploit for CVE-2020-16009 exists in the wild.

CVEs:
CVE-2020-16004 CVE-2020-16005 CVE-2020-16006 CVE-2020-16007
CVE-2020-16008 CVE-2020-16009 CVE-2020-16011

(cherry picked from commit 531decc)
Backport of #102608. I'll push this directly as it should build fine and
we need the security fixes timely (see above).
    @primeos
    primeos committed Nov 3, 2020
    Copy the full SHA
    d2f4600 View commit details
    Browse the repository at this point in the history