Commit Graph
100 Commits
Author SHA1 Message Date
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 116d152c9e Merge pull request #116176 from primeos/chromium
chromium: 89.0.4389.82 -> 89.0.4389.90
2021-03-13 21:11:00 +01:00
Michael Weiss 2721f407e5 Merge pull request #116146 from Emantor/pkgconfig/iniparser
iniparser: add pkgconfig file
2021-03-13 17:48:29 +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 c881760d41 Merge pull request #116007 from jflanglois/chrome-libva
google-chrome: add optional libva and vulkan support
2021-03-13 12:47:56 +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 90e466041a intel-media-driver: 21.1.1 -> 21.1.2 2021-03-11 18:30:45 +01:00
Michael Weiss a3228bb6e8 bundler-audit: 0.7.0.1 -> 0.8.0 2021-03-11 16:55:03 +01:00
Michael Weiss 938453eacd Merge pull request #102225 from luc65r/fetchsrht
Add fetcher: fetchFromSourcehut
2021-03-11 12:51:13 +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 4ee208ecdc Merge pull request #115781 from primeos/ungoogled-chromium
ungoogled-chromium: 88.0.4324.182 -> 89.0.4389.82
2021-03-11 11:28:36 +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 095ad1b5b9 Merge pull request #115243 from primeos/chromium
chromium: 89.0.4389.72 -> 89.0.4389.82
2021-03-07 11:38:22 +01:00
Michael Weiss b1c5aa5ef1 chromium: 89.0.4389.72 -> 89.0.4389.82 2021-03-06 11:59:38 +01:00
Michael Weiss f6e94a2e21 gns3-{gui,server}: Remove myself as maintainer 2021-03-05 18:46:02 +01:00
Michael Weiss 1da40cb31c Merge pull request #115194 from primeos/python-google-api-client
[needs new maintainer] python3Packages.google_api_python_client: 1.12.8 -> 2.0.2
2021-03-05 17:08:05 +01:00
Michael Weiss cc4be81635 python3Packages.google_api_python_client: Remove myself as maintainer 2021-03-05 15:05:04 +01:00
Michael Weiss 39aff3a902 python3Packages.google_api_python_client: 1.12.8 -> 2.0.2 2021-03-05 15:05:01 +01:00
Michael Weiss dac4672072 html-proofer: Add bundlerUpdateScript and remove myself as maintainer 2021-03-05 14:59:24 +01:00
Michael Weiss e2285e1fd1 html-proofer: 3.18.6 -> 3.18.8 2021-03-05 14:59:19 +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 WeissandSandro d774b4234a [needs new maintainer] gitRepo: Remove myself as maintainer (#114835)
Co-authored-by: Sandro <sandro.jaeckel@gmail.com>
2021-03-03 13:44:26 +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 8fc24d14bb Merge pull request #114973 from primeos/chromium
chromium: 88.0.4324.182 -> 89.0.4389.72
2021-03-03 12:35:35 +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 a676907ae3 gitRepo: 2.12.2 -> 2.13.1 2021-03-02 13:04:06 +01:00
Michael Weiss c4e4ba0967 Merge pull request #114223 from meutraa/update/android-studio
androidStudioPackages: change --set JAVA_HOME to --set-default in wra…
2021-03-01 15:49:56 +01:00
Michael Weiss 9877ed5b95 Merge pull request #114226 from meutraa/update/android-studio-canary
androidStudioPackages.{beta,canary,dev}: update
2021-03-01 15:42:19 +01:00
Michael Weiss 00529f5bba lf: 20 -> 21 2021-02-28 14:01:59 +01:00
Michael Weiss 5df05c902c gollum: 5.1.2 -> 5.2.1 2021-02-27 21:39:16 +01:00
Michael Weiss 18df480d9b gollum: Transfer maintainership to erictapen
I'm not using Gollum anymore while Justin still uses it and has also
written the NixOS module. So it makes perfect sense to pass it on :)
2021-02-27 21:39:16 +01:00
Michael Weiss 322e538df8 libglvnd: Improve the license information (#114466)
Unfortunately the upstream licensing is quite complicated:
https://gitlab.freedesktop.org/glvnd/libglvnd#libglvnd

The main libglvnd license is MIT-like but files under different licenses
are also included. This is an approximation that ignores some license
"customizations".

Other distributions use the following license specifications:
- "MIT":
  - https://src.fedoraproject.org/rpms/libglvnd/blob/rawhide/f/libglvnd.spec
  - https://build.opensuse.org/package/view_file/openSUSE:Factory/libglvnd/libglvnd.spec
  - https://gitweb.gentoo.org/repo/gentoo.git/tree/media-libs/libglvnd/libglvnd-1.3.2-r2.ebuild
- "custom:MIT-alike": https://github.com/void-linux/void-packages/blob/master/srcpkgs/libglvnd/template
- "APACHE20 MIT": https://www.freshports.org/graphics/libglvnd
- "custom:BSD-like": https://archlinux.org/packages/extra/x86_64/libglvnd/
2021-02-27 20:24:08 +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 24e89ccb75 Merge pull request #113751 from bobrik/ivan/libglvnd-aarch64-darwin
libglvnd: disable asm on aarch64-darwin
2021-02-26 19:50:34 +01:00
Michael Weiss ed113c9bd5 tdesktop: 2.6.0 -> 2.6.1 2021-02-26 13:43:29 +01:00
Michael Weiss c6f1dc2320 libglvnd: Switch to the new official repository
"The official repository for libglvnd is hosted on FreeDesktop.org's
GitLab: https://gitlab.freedesktop.org/glvnd/libglvnd" [0]

[0]: https://github.com/NVIDIA/libglvnd/tree/master#introduction
2021-02-26 12:40:17 +01:00
Michael Weiss 8066dd61a3 libglvnd: Add myself as maintainer
The package lacked a maintainer and since I already maintain Mesa it
makes sense to look after libglvnd as well.
2021-02-26 12:30:42 +01:00
Michael Weiss 682696deba tcpflow: 1.5.2 -> 1.6.1
The substituteInPlace "patch" is required to fix the following build error:
datalink.cpp:177:27: error: format not a string literal and no format
arguments
[8;;https://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html#index-Wformat-security-Werror=format-security8;;]
  177 |         DEBUG(6)(s.c_str());
      |                           ^

This also removes me as maintainer since I don't use tcpflow anymore.
2021-02-24 18:45:20 +01:00
Michael Weiss 2c042fe9c8 tdesktop: 2.5.9 -> 2.6.0
This also adds libthai and libdatrie as optional dependencies for gtk3.
2021-02-24 17:49:59 +01:00
Michael Weiss 74b34f4a17 signal-desktop: 1.40.0 -> 1.40.1 2021-02-23 17:23:15 +01:00
Michael Weiss 71fcdff01a html-proofer: 3.18.5 -> 3.18.6 2021-02-23 17:15:51 +01:00
Michael Weiss f352fdd819 Merge pull request #113754 from bobrik/ivan/mesa-aarch64-darwin
mesa: fix missing timespec_get on darwin
2021-02-20 19:39:13 +01:00
Michael Weiss 2dd1c214ba Merge pull request #113712 from primeos/ungoogled-chromium
ungoogled-chromium: 88.0.4324.150 -> 88.0.4324.182
2021-02-19 21:26:10 +01:00
Michael Weiss 7722cb1b13 Merge pull request #113660 from Hoverbear/nvme-cli-add-libuuid
nvme-cli: add libuuid input
2021-02-19 19:58:53 +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 a1aec6be0b cargo-c: 0.7.2 -> 0.7.3 2021-02-18 19:06:36 +01:00
Michael Weiss 7b41fd7bff signal-desktop: 1.39.6 -> 1.40.0 2021-02-18 15:41:03 +01:00
Michael Weiss b78942f040 tdesktop: 2.5.8 -> 2.5.9 2021-02-18 15:32:07 +01:00
Michael Weiss 968d7e80c7 Merge pull request #113236 from blitz/kcmp
linux: enable kcmp() system call
2021-02-18 14:43:29 +01:00
Michael Weiss 849bd20271 chromiumBeta: 89.0.4389.47 -> 89.0.4389.58 2021-02-18 12:13:16 +01:00
Michael Weiss eecade6b3e Merge pull request #113313 from primeos/nix-prefetch-git-avoid-initial-branch-warnings
nix-prefetch-git: Run git-init with --initial-branch=master
2021-02-18 11:53:11 +01:00
Michael Weiss 2aadb9a53d nix-prefetch-git: Run git-init with --initial-branch=master
The reason for this change is simply to avoid the following messages
that are unnecessary and can be confusing (and these messages will be
repeated for each submodule):
hint: Using 'master' as the name for the initial branch. This default branch name
hint: is subject to change. To configure the initial branch name to use in all
hint: of your new repositories, which will suppress this warning, call:
hint:
hint:   git config --global init.defaultBranch <name>
hint:
hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and
hint: 'development'. The just-created branch can be renamed via this command:
hint:
hint:   git branch -m <name>

With this change the behaviour remains unchanged (apart from the
suppressed "warning" in the console output of course) and therefore this
doesn't cause any hashes to change and by default nix-prefetch-git uses
the "fetchgit" branch anyway (branchName can be set to override the
default):
Switched to a new branch 'fetchgit'

For that reason the initial branch name doesn't matter anyway and since
we're not relying on / hardcoding "master" we could simply switch to
"main" (which seems most common nowadays). See [0] for more details on
why this wouldn't break anything.
However, since the initial branch name doesn't matter and to avoid any
additional risks it was "decided" to keep using "master" (s. #113313).

[0]: https://github.com/NixOS/nixpkgs/pull/113313#issuecomment-780589516
2021-02-18 11:34:34 +01:00
Michael Weiss e5bb19173e python3Packages.cryptography: 3.4.5 -> 3.4.6 2021-02-17 21:10:58 +01:00
Michael Weiss 5c7d7c32af Merge pull request #113368 from TredwellGit/chromium
chromium: 88.0.4324.150 -> 88.0.4324.182
2021-02-17 15:41:50 +01:00
Michael Weiss 2f467621b7 tev: Set TEV_DEPLOY=1 2021-02-16 14:46:25 +01:00
Michael Weiss 3d9deb5473 gns3-{gui,server}: 2.2.17 -> 2.2.18 2021-02-16 14:46:00 +01:00
Michael Weiss 1159a79877 tev: 1.16 -> 1.17 2021-02-16 14:14:39 +01:00
Michael Weiss 9b17dda68c python3Packages.cryptography: 3.4.4 -> 3.4.5 2021-02-14 12:37:01 +01:00
Michael Weiss b4f2376434 gitRepo: 2.12.1 -> 2.12.2 2021-02-12 12:38:33 +01:00
Michael Weiss 2c2ce6bf9e Merge pull request #112866 from bobrik/ivan/libaom-aarch64-fix
libaom: only disable cpu detectio on arm64 and do it as recommended
2021-02-12 12:02:41 +01:00
Michael Weiss c9858b6d88 gitRepo: 2.12 -> 2.12.1 2021-02-11 19:27:32 +01:00
Michael Weiss 939c9aa22c python3Packages.cryptography: 3.4.2 -> 3.4.4
Contains a few minor fixes and improvements.
2021-02-11 15:14:37 +01:00
Michael Weiss d58e9cd05b libaom: 2.0.1 -> 2.0.2 2021-02-11 13:10:40 +01:00
Michael Weiss d35eb344f8 chromiumBeta: 89.0.4389.40 -> 89.0.4389.47 2021-02-11 12:37:06 +01:00
Michael Weiss 7fdadc140c fscryptctl: init at 1.0.0 (#112651)
Release notes: https://github.com/google/fscryptctl/releases/tag/v1.0.0

fscryptctl-experimental will remain at version 0.1.0 to ensure a smooth
transition.
2021-02-11 12:36:34 +01:00
Michael Weiss 8132d63bc5 git: 2.30.0 -> 2.30.1 (#112581) 2021-02-10 11:39:09 +01:00
Michael Weiss da73f94622 python3Packages.cryptography: 3.3.2 -> 3.4.2
Backwards incompatible changes: Support for Python 2 has been removed.
Note: This isn't a problem for Nixpkgs because
pythonPackages.cryptography is frozen at version 3.3.2.

Other important packaging changes: "Cryptography now incorporates Rust
code. Users building cryptography themselves will need to have the Rust
toolchain installed. Users who use an officially produced wheel will not
need to make any changes. The minimum supported Rust version is 1.45.0."
2021-02-10 07:03:40 +01:00
Michael Weiss ed6ccd4b27 chromiumDev: 90.0.4408.0 -> 90.0.4412.3 2021-02-09 22:35:08 +01:00
Michael Weiss a6fa79639a inxi: 3.3.00-1 -> 3.3.01-1 2021-02-09 21:55:59 +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 af9568fae8 python3Packages.cryptography: 3.3.1 -> 3.3.2 (security, CVE-2020-36242)
SECURITY ISSUE: Fixed a bug where certain sequences of update() calls
when symmetrically encrypting very large payloads (>2GB) could result in
an integer overflow, leading to buffer overflows. CVE-2020-36242

Note: This also updates {,vectors-}3.3.nix (for Python 2 / nixops)
because of the security issue.
2021-02-07 20:09:55 +01:00
Michael Weiss cd4c376baf glances: 3.1.6.1 -> 3.1.6.2 2021-02-07 19:28:01 +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 de88795283 Merge pull request #112288 from primeos/chromium
chromium: Remove the Adobe Flash Player plugin support
2021-02-07 19:13:26 +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 f11c4708da wob: 0.10 -> 0.11 2021-02-06 19:31:24 +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 df9dac5e77 fuse3: 3.10.1 -> 3.10.2 (#112016) 2021-02-06 11:52:09 +01:00
Michael Weiss 06d0d8ecfa chromiumDev: 90.0.4400.8 -> 90.0.4408.0 2021-02-06 00:55:35 +01:00
Michael Weiss e1ad722370 Merge pull request #112071 from primeos/chromium
chromium: 88.0.4324.146 -> 88.0.4324.150
2021-02-06 00:37:13 +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 WeissandSandro d0b891c828 isync: 1.3.4 -> 1.4.0
Important changes:
- The 'isync' compatibility wrapper was removed.
- The Master/Slave configuration keywords where deprecated and should be
  replaced with Far/Near. All users should update their configuration
  file accordingly. It's a trivial change and the old Master/Slave
  keywords will still work for now but result in the following message:
  Notice: Master/Slave are deprecated; use Far/Near instead.

Co-authored-by: Sandro <sandro.jaeckel@gmail.com>
2021-02-04 19:54:54 +01:00
Michael Weiss 6f6ce15938 fscryptctl-experimental: 2017-10-23 -> 0.1.0
Version 0.1.0 is based on the last commit that included support for V1
encryption policies. Version 1.0 is about to be released and will
include a PR which removes V1 policy support and adds V2 policy support.
Source: https://github.com/google/fscryptctl/issues/12#issuecomment-772888154

When version 1.0 is released we'll likely package it as fscryptctl and
mark fscryptctl-experimental as broken (referring to fscryptctl).
2021-02-04 13:39:00 +01:00
Michael Weiss e74cfaf671 isync: 1.3.3 -> 1.3.4 (#111789) 2021-02-04 12:19:16 +01:00
Michael Weiss 6f0de2b041 chromiumBeta: 89.0.4389.23 -> 89.0.4389.40 2021-02-04 11:42:14 +01:00
Michael Weiss 25e3e66b65 iputils: 20200821 -> 20210202 (#111645) 2021-02-03 21:02:06 +01:00
Michael Weiss 570d7def06 Merge pull request #111740 from primeos/chromium
chromium: 88.0.4324.96 -> 88.0.4324.146
2021-02-03 20:33:58 +01:00
Michael Weiss d345d333ab intel-media-driver: 21.1.0 -> 21.1.1 2021-02-03 18:52:55 +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