JakeHillion/nixpkgs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
277,096 Commits 2 Branches 0 Tags 13 GiB
33bd43d2ea
Commit Graph

900 Commits

Author SHA1 Message Date
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
Michael Weiss
9f38162b30
chromium: 88.0.4324.182 -> 89.0.4389.72 
https://chromereleases.googleblog.com/2021/03/stable-channel-update-for-desktop.html

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

CVEs:
CVE-2021-21159 CVE-2021-21160 CVE-2021-21161 CVE-2021-21162
CVE-2021-21163 CVE-2021-21164 CVE-2021-21165 CVE-2021-21166
CVE-2021-21167 CVE-2021-21168 CVE-2021-21169 CVE-2021-21170
CVE-2021-21171 CVE-2021-21172 CVE-2021-21173 CVE-2021-21174
CVE-2021-21175 CVE-2021-21176 CVE-2021-21177 CVE-2021-21178
CVE-2021-21179 CVE-2021-21180 CVE-2020-27844 CVE-2021-21181
CVE-2021-21182 CVE-2021-21183 CVE-2021-21184 CVE-2021-21185
CVE-2021-21186 CVE-2021-21187 CVE-2021-21188 CVE-2021-21189
CVE-2021-21190
 2021-03-03 12:23:11 +01:00
Michael Weiss
f4c885a79a
chromiumBeta: 89.0.4389.69 -> 89.0.4389.72 2021-03-02 20:28:11 +01:00
Michael Weiss
5240639ab6
chromiumDev: 90.0.4421.5 -> 90.0.4427.5 2021-02-27 16:35:48 +01:00
Michael Weiss
adccc8b65b
chromiumBeta: 89.0.4389.58 -> 89.0.4389.69 2021-02-27 16:35:48 +01:00
Michael Weiss
62df868822
ungoogled-chromium: 88.0.4324.150 -> 88.0.4324.182 2021-02-19 19:47:38 +01:00
Michael Weiss
8df4ea8d28
chromiumDev: 90.0.4412.3 -> 90.0.4421.5 2021-02-19 19:45:39 +01:00
Michael Weiss
849bd20271
chromiumBeta: 89.0.4389.47 -> 89.0.4389.58 2021-02-18 12:13:16 +01:00
TredwellGit
c3181699cd chromium: 88.0.4324.150 -> 88.0.4324.182 
https://chromereleases.googleblog.com/2021/02/stable-channel-update-for-desktop_16.html

This update includes 10 security fixes.

CVEs:
CVE-2021-21149 CVE-2021-21150 CVE-2021-21151 CVE-2021-21152
CVE-2021-21153 CVE-2021-21154 CVE-2021-21155 CVE-2021-21156
CVE-2021-21157
 2021-02-17 05:43:11 +00:00
Michael Weiss
d35eb344f8
chromiumBeta: 89.0.4389.40 -> 89.0.4389.47 2021-02-11 12:37:06 +01:00
Michael Weiss
ed6ccd4b27
chromiumDev: 90.0.4408.0 -> 90.0.4412.3 2021-02-09 22:35:08 +01:00
Michael Weiss
43161bc2b7
ungoogled-chromium: 88.0.4324.146 -> 88.0.4324.150 2021-02-09 15:24:38 +01:00
Michael Weiss
89db67e734
chromium: Update the documentation 
And close #78450 because I'm maintaining Chromium for approximately one
year now and it looks like I can keep maintaining it (at least as long
as I have enough time for it). I'm also working on the documentation,
automation, and cleanups so finding a new maintainer in the future
should hopefully be easier.
 2021-02-07 19:26:14 +01:00
Michael Weiss
d55603f11d
chromium: Remove the Adobe Flash Player plugin support 
The Flash support was completely removed in Chromium M88:
- https://www.chromium.org/flash-roadmap#TOC-Flash-Support-Removed-from-Chromium-Target:-Chrome-88---Jan-2021-
- https://chromestatus.com/feature/5643527180517376

See #110314.
 2021-02-07 12:27:36 +01:00
Michael Weiss
576464c74d
chromium: Remove our old overrides for VA-API and Ozone 
These gn arguments aren't required anymore as they're now equal to the
current defaults.
 2021-02-06 12:28:50 +01:00
Michael Weiss
06d0d8ecfa
chromiumDev: 90.0.4400.8 -> 90.0.4408.0 2021-02-06 00:55:35 +01:00
Michael Weiss
ad588f04d4
chromium: 88.0.4324.146 -> 88.0.4324.150 
https://chromereleases.googleblog.com/2021/02/stable-channel-update-for-desktop_4.html

This update includes 1 security fix. Google is aware of reports that an
exploit for CVE-2021-21148 exists in the wild.

CVEs: CVE-2021-21148
 2021-02-05 21:03:36 +01:00
Michael Weiss
6f0de2b041
chromiumBeta: 89.0.4389.23 -> 89.0.4389.40 2021-02-04 11:42:14 +01:00
Michael Weiss
bdf7d732d3
ungoogled-chromium: 88.0.4324.104 -> 88.0.4324.146 (security) 2021-02-03 12:38:21 +01:00
Michael Weiss
4fe69d33ae
chromium: 88.0.4324.96 -> 88.0.4324.146 
https://chromereleases.googleblog.com/2021/02/stable-channel-update-for-desktop.html

This update includes 6 security fixes.

CVEs:
CVE-2021-21142 CVE-2021-21143 CVE-2021-21144 CVE-2021-21145
CVE-2021-21146 CVE-2021-21147
 2021-02-03 12:38:09 +01:00
Jan Tojnar
54f4529aec
Merge pull request #111519 from siraben/xdg-utils-naming 2021-02-01 17:18:57 +01:00
Michael Weiss
3151fd59e7
Merge pull request #111340 from primeos/ungoogled-chromium 
ungoogled-chromium: 87.0.4280.141 -> 88.0.4324.104
 2021-02-01 14:14:03 +01:00
Ben Siraphob
a6ac3eedbd treewide: xdg_utils -> xdg-utils 2021-02-01 15:05:09 +07:00
Michael Weiss
d1c040f8c6
chromiumDev: Build without TFLite and apply a fix 
During d6d4228b39 I failed to notice that the current chromiumDev
version is older than the first one that contained the commit to fix the
dependency on opus in webcodecs.
This should hopefully fix build of chromiumDev (if there are no
additional issues).
 2021-02-01 01:43:30 +01:00
Michael Weiss
268600e6b7
ungoogled-chromium: 87.0.4280.141 -> 88.0.4324.104 
Unfortunately this requires a crazy hack to support building with
Google's proprietary Widevine DRM technology as that requires fetching
the Google Chrome sources (see also 86ff1e45ce).
The hack is required because ungoogled-chromium doesn't always use tags
that correspond to a Google Chrome release.
 2021-01-30 19:22:22 +01:00
Michael Weiss
d6d4228b39
chromiumBeta: Backport a patch to fix the build 
The build was failing with:
In file included from ../../third_party/blink/renderer/modules/webcodecs/audio_encoder.cc:7:
In file included from ../../media/audio/audio_opus_encoder.h:16:
gen/shim_headers/opus_shim/third_party/opus/src/include/opus.h:5:10: error: 'opus.h' file not found with <angled> include; use "quotes" instead
#include <opus.h>
         ^~~~~~~~
         "opus.h"
[...]
fatal error: too many errors emitted, stopping now [-ferror-limit=]
20 errors generated.
[42272/44233] CXX obj/third_party/blink/renderer/modules/webcodecs/webcodecs/decoder_template.oo[K

Note: This also fixes the ungoogled-chromium channel name in versionRange.
 2021-01-30 12:08:17 +01:00
Michael Weiss
241db3bb01
chromium{Beta,Dev}: Disable PGO to "fix" a build error 
This also fixes/improves versionRange because the ungoogled-chromium
version will lag behind the Chromium version.
 2021-01-28 22:32:32 +01:00
Michael Weiss
11ec29dd70
chromiumDev: 89.0.4389.23 -> 90.0.4400.8 2021-01-28 21:30:26 +01:00
Michael Weiss
a7339c3a24
chromiumBeta: 88.0.4324.96 -> 89.0.4389.23 2021-01-28 21:30:25 +01:00
Michael Weiss
bfc1cee4bf
chromiumDev: 89.0.4389.9 -> 89.0.4389.23 2021-01-28 15:45:00 +01:00
Michael Weiss
863982d272
chromium: Fix the version comparison in print_updates() 
I forgot that string comparison isn't enough because e.g.:
>>> "89.0.4389.9" < "89.0.4389.23"
False

distutils.version.LooseVersion is undocumented but it works and is
already available so why not use it:
>>> LooseVersion("89.0.4389.9") < LooseVersion("89.0.4389.23")
True
 2021-01-28 15:45:00 +01:00