BoomMicrophone/nixpkgs-suyu
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
284206 commits 1 branch 0 tags 3.8 GiB
Commit graph

930 commits

Author SHA1 Message Date
github-actions[bot]
d4f421cad9
Merge master into staging-next 2021-04-16 12:06:14 +00:00
Michael Weiss
37f8212780
chromiumDev: 91.0.4469.4 -> 91.0.4472.10 2021-04-16 11:45:58 +02:00
github-actions[bot]
9c190d28df
Merge master into staging-next 2021-04-15 12:06:13 +00:00
Martin Weinelt
7cf67850c0
Merge branch 'master' into staging-next 2021-04-15 01:01:26 +02:00
Michael Weiss
6720b034aa
chromium: 89.0.4389.128 -> 90.0.4430.72 
https://chromereleases.googleblog.com/2021/04/stable-channel-update-for-desktop_14.html

This update includes 37 security fixes.

CVEs:
CVE-2021-21201 CVE-2021-21202 CVE-2021-21203 CVE-2021-21204
CVE-2021-21205 CVE-2021-21221 CVE-2021-21207 CVE-2021-21208
CVE-2021-21209 CVE-2021-21210 CVE-2021-21211 CVE-2021-21212
CVE-2021-21213 CVE-2021-21214 CVE-2021-21215 CVE-2021-21216
CVE-2021-21217 CVE-2021-21218 CVE-2021-21219
 2021-04-15 00:53:31 +02:00
Michael Weiss
14ec94a2fe
chromiumBeta: 90.0.4430.70 -> 90.0.4430.72 2021-04-15 00:53:04 +02:00
Michael Weiss
96e4c599de
Merge pull request #119401 from primeos/chromium 
chromium: 89.0.4389.114 -> 89.0.4389.128
 2021-04-15 00:40:44 +02:00
github-actions[bot]
eb8e023674
Merge master into staging-next 2021-04-14 18:11:01 +00:00
Michael Weiss
de2edb81da
chromium: get-commit-message.py: Deduplicate the CVE list 2021-04-14 14:33:34 +02:00
Michael Weiss
a8937cc97b
chromium: 89.0.4389.114 -> 89.0.4389.128 
https://chromereleases.googleblog.com/2021/04/stable-channel-update-for-desktop.html

This update includes 2 security fixes. Google is aware of reports that
exploits for CVE-2021-21206 and CVE-2021-21220 exist in the wild.

CVEs:
CVE-2021-21206 CVE-2021-21220
 2021-04-14 10:49:34 +02:00
Vladimír Čunát
d2eb7a7887
Merge branch 'staging' into staging-next 
A few conflicts but relatively clear ones (I think).
 2021-04-14 10:08:25 +02:00
Michael Weiss
acf402b0c0
chromiumDev: Fix the build 
Mixing Python 2 and Python 3 causes issues with the Python dependencies.
 2021-04-13 13:30:54 +02:00
Michael Weiss
fc586861ee
chromiumBeta: 90.0.4430.61 -> 90.0.4430.70 2021-04-13 10:19:51 +02:00
Michael Weiss
8c60448e26
chromiumDev: Fix two build errors 
Python 3 is now required (hard-coded in some scripts, but other scripts
still require Python 2) and a patch is required for [0].

[0]: https://bugs.chromium.org/p/chromium/issues/detail?id=1192875
 2021-04-13 10:19:51 +02:00
Luke Granger-Brown
08b22e605b Merge remote-tracking branch 'upstream/staging-next' into down-integrate-staging 2021-04-12 18:49:01 +00:00
Michael Weiss
5d775bb2b0
chromiumBeta: Fix the build (#119087) 2021-04-11 10:43:29 +02:00
Michael Weiss
227efbd318
chromium: Fix the build (libva redefinition) 
The recent libva 2.11.0 update (780fa55) broke the chromium and
ungoogled-chromium builds. Fix #118931.
 2021-04-10 12:06:42 +02:00
Michael Weiss
5768ccf6fe
chromium{Beta,Dev}: Fix the linking 
Linking with ThinLTO (required for CFI) was failing as I forgot use
stdenv from llvmPackages_12 in 166520812e (need to refactor that part).
 2021-04-09 12:09:59 +02:00
Michael Weiss
d5fcfcb3de
chromiumDev: 91.0.4464.5 -> 91.0.4469.4 2021-04-09 12:09:58 +02:00
Gabriel Ebner
aa0b68b26a chromium: add explicit mesa dependency 2021-04-09 09:26:12 +02:00
Michael Weiss
705e5ae6fb
chromiumBeta: 90.0.4430.51 -> 90.0.4430.61 2021-04-08 16:13:28 +02:00
Sandro Jäckel
dcb501f993
kerberos: deprecate alias 2021-04-04 03:18:56 +02:00
Michael Weiss
d832cb56dd
Merge pull request #118166 from primeos/ungoogled-chromium 
ungoogled-chromium: 89.0.4389.90 -> 89.0.4389.114
 2021-04-02 23:05:08 +02:00
Michael Weiss
166520812e
chromium{Beta,Dev}: Use LLVM 12 
LLVM 12 is required but the build still fails due to other changes that
where introduced in the meantime (and Chromium 90.0.4430.51 introduced
another LLVM failure).
 2021-04-02 13:32:17 +02:00
Michael Weiss
985e98f4c4
chromiumDev: 91.0.4455.2 -> 91.0.4464.5 2021-04-01 20:17:45 +02:00
Michael Weiss
e8c1d93f49
chromiumBeta: 90.0.4430.40 -> 90.0.4430.51 2021-04-01 13:48:45 +02:00
Michael Weiss
d40c8f6279
ungoogled-chromium: 89.0.4389.90 -> 89.0.4389.114 2021-03-31 21:11:22 +02:00
Michael Weiss
9495de73dd
chromium: 89.0.4389.90 -> 89.0.4389.114 
https://chromereleases.googleblog.com/2021/03/stable-channel-update-for-desktop_30.html

This update includes 8 security fixes.

CVEs:
CVE-2021-21194 CVE-2021-21195 CVE-2021-21196 CVE-2021-21197
CVE-2021-21198 CVE-2021-21199
 2021-03-31 12:54:36 +02:00
Michael Weiss
dbdab5b83b
chromiumBeta: 90.0.4430.30 -> 90.0.4430.40 2021-03-25 14:55:51 +01:00
Michael Weiss
14efa32fa5
chromiumDev: 91.0.4449.6 -> 91.0.4455.2 2021-03-24 13:40:40 +01:00
Michael Weiss
33bd43d2ea
chromiumDev: 91.0.4442.4 -> 91.0.4449.6 2021-03-19 11:26:49 +01:00
Michael Weiss
622a4a2dd5
chromiumBeta: 90.0.4430.19 -> 90.0.4430.30 2021-03-18 13:11:08 +01:00
Michael Weiss
5e42fea124
chromiumBeta,chromiumDev: Mark as broken 
The builds currently fail with (should work with LLVM 12 [0]):
../../base/check.h:88:3: error: 'nomerge' attribute cannot be applied to a declaration
  NOMERGE ~CheckError();
  ^       ~
../../base/compiler_specific.h:344:19: note: expanded from macro 'NOMERGE'
#define NOMERGE [[clang::nomerge]]
                  ^
1 error generated.

[0]: fb0f728805
 2021-03-17 15:04:53 +01:00
Michael Weiss
2926759b15
Merge pull request #116309 from primeos/ungoogled-chromium 
ungoogled-chromium: 89.0.4389.82 -> 89.0.4389.90
 2021-03-15 22:06:10 +01:00
Michael Weiss
fe3c3a2641
Merge pull request #116218 from primeos/chromium-drop-enableVaapi 
chromium: Remove the enableVaapi flag/option
 2021-03-15 12:14:23 +01:00
Michael Weiss
bb52ac0cb0
ungoogled-chromium: 89.0.4389.82 -> 89.0.4389.90 2021-03-14 13:35:12 +01:00
Michael Weiss
14e11862ea
chromium: Remove the enableVaapi flag/option 
Chromium is still compiled with use_vaapi=true but since M89 the
--enable-accelerated-video-decode was replaced with
--enable-features=VaapiVideoDecoder.

Instead of updating our wrapper it seems like a better idea to drop
enableVaapi entirely and let users use commandLineArgs or
chrome://flags/ to enable hardware accelerated video decoding.
 2021-03-13 16:38:42 +01:00
Michael Weiss
5f8b951139
chromium: 89.0.4389.82 -> 89.0.4389.90 
https://chromereleases.googleblog.com/2021/03/stable-channel-update-for-desktop_12.html

This update includes 5 security fixes. Google is aware of reports that
an exploit for CVE-2021-21193 exists in the wild.

CVEs:
CVE-2021-21191 CVE-2021-21192 CVE-2021-21193 CVE-2021-21193
 2021-03-13 12:14:37 +01:00
Michael Weiss
9fe8be6685
chromiumDev: 90.0.4430.19 -> 91.0.4442.4 2021-03-13 12:14:16 +01:00
Michael Weiss
381af7aa3f
chromiumBeta: 89.0.4389.72 -> 90.0.4430.19 2021-03-11 22:48:17 +01:00
Michael Weiss
dc8eacfba0
Merge pull request #114979 from primeos/chromium-pipewire-0.3 
chromium: Switch from PipeWire 0.2 to the current 0.3.x releases
 2021-03-11 11:30:13 +01:00
Michael Weiss
746de7f70e
ungoogled-chromium: 88.0.4324.182 -> 89.0.4389.82 2021-03-10 16:01:40 +01:00
Michael Weiss
1868ac1d21
chromiumDev: 90.0.4430.11 -> 90.0.4430.19 2021-03-09 21:36:12 +01:00
Michael Weiss
17c4f6fa36
chromium: Make get-commit-message.py more robust 
Not all updates contain security fixes.
 2021-03-07 12:05:21 +01:00
Michael Weiss
b1c5aa5ef1
chromium: 89.0.4389.72 -> 89.0.4389.82 2021-03-06 11:59:38 +01:00
Michael Weiss
6abbdecf62
Merge pull request #114977 from primeos/chromium-remove-client-credentials 
chromium: Remove google_default_client_{id,secret}
 2021-03-05 13:08:09 +01:00
Michael Weiss
36e5fe006a
chromium: Switch from PipeWire 0.2 to the current 0.3.x releases 
This should make it work more reliable and support additional features
like window sharing. See [0] for more details.

[0]: https://jgrulich.cz/2020/12/18/webrtc-chromium-updates-in-2020/
 2021-03-04 17:53:06 +01:00
Michael Weiss
8671fe7c90
chromiumDev: 90.0.4427.5 -> 90.0.4430.11 2021-03-04 11:50:46 +01:00
Michael Weiss
9004162c26
chromium: Add my script to generate the commit messages 
Might not be that readable and reliable but it should get the job done.
 2021-03-03 16:55:03 +01:00
Michael Weiss
dc9f2c5e70
chromium: Remove google_default_client_{id,secret} 
Reason: Google is limiting access to their private Chrome APIs starting
on March 15, 2021 [0]. Closes #110245.

From the mailing list thread [1]:
"The changes we announced affect the OAuth 2.0 client id and secret
which are used for signing into Chrome, not the API key."
"To avoid using that API, it's sufficient to either not set the OAuth
2.0 credentials, or disabling the Google signin integration" (e.g. by
passing the flag --allow-browser-signin=false)

[0]: https://blog.chromium.org/2021/01/limiting-private-api-availability-in.html
[1]: https://groups.google.com/a/chromium.org/g/chromium-packagers/c/SG6jnsP4pWM/
 2021-03-03 13:13:17 +01:00