alioth/nixpkgs
3
0
Fork 0
forked from mirrors/nixpkgs
Code Releases Activity
286061 commits 217 branches 121 tags 4.5 GiB
Commit graph

4349 commits

Author SHA1 Message Date
Michael Weiss 0d7f9f8ac3
chromiumDev: 92.0.4484.7 -> 92.0.4491.6 2021-04-29 21:53:31 +02:00
Anderson Torres ff7d6c9a47
Merge pull request #120930 from OPNA2608/update/palemoon-29.2.0/21.05 
palemoon: 29.1.1 -> 29.2.0
 2021-04-29 14:35:15 -03:00
OPNA2608 668264d220 palemoon: 29.1.1 -> 29.2.0 2021-04-29 12:51:11 +02:00
Michael Weiss 3b6d416960
Merge pull request #121084 from primeos/chromiumBeta 
chromiumBeta: 91.0.4472.19 -> 91.0.4472.27
 2021-04-29 12:15:12 +02:00
Alyssa Ross a8afbb45c1 treewide: use lib.warnIf where appropriate 2021-04-28 21:44:21 +00:00
Michael Weiss 716d176974
chromiumBeta: 91.0.4472.19 -> 91.0.4472.27 2021-04-28 23:19:29 +02:00
Michael Weiss d6bd816370
chromium: 90.0.4430.85 -> 90.0.4430.93 
https://chromereleases.googleblog.com/2021/04/stable-channel-update-for-desktop_26.html

This update includes 9 security fixes.

CVEs:
CVE-2021-21227 CVE-2021-21232 CVE-2021-21233 CVE-2021-21228
CVE-2021-21229 CVE-2021-21230 CVE-2021-21231
 2021-04-27 15:45:25 +02:00
Robert Schütz f5f0c3be1a
tor-browser-bundle-bin: use ffmpeg instead of ffmpeg_3 (#120653) 2021-04-27 12:40:25 +02:00
Jan Tojnar 0f1c4558d3
Merge branch 'master' into staging-next 
Choose binwalk 2.3.1, 27 is legacy version for Python 2.
 2021-04-25 02:50:48 +02:00
Michael Weiss eb335f697e
chromium: Warn about and cleanup old chromiumVersionAtLeast conditionals 2021-04-24 12:47:12 +02:00
Michael Weiss a82f2a0146
ungoogled-chromium: 89.0.4389.114 -> 90.0.4430.85 2021-04-24 12:21:28 +02:00
github-actions[bot] 6e7c70d02d
Merge master into staging-next 2021-04-24 00:16:17 +00:00
Michael Weiss 0dee033ce7
chromiumDev: Fix the configuration phase (#120464) 
The Python 3 support still isn't ready...
 2021-04-23 23:24:13 +02:00
Alyssa Ross 4f4d95bbc2
Merge remote-tracking branch 'nixpkgs/master' into staging-next 
Conflicts:
	pkgs/development/python-modules/pyvex/default.nix
	pkgs/top-level/python-packages.nix
 2021-04-23 13:49:12 +00:00
Michael Weiss a75b5add13
chromiumDev: 91.0.4472.19 -> 92.0.4484.7 2021-04-23 12:03:56 +02:00
github-actions[bot] 481a9bc47c
Merge master into staging-next 2021-04-23 00:15:39 +00:00
Michael Weiss 6664b74af1
chromiumBeta: 90.0.4430.85 -> 91.0.4472.19 2021-04-22 21:18:26 +02:00
Martin Weinelt e75f053238
Merge pull request #119434 from ooesili/firefox-ld-path-prefix 
Add Firefox libs to beginning of LD_LIBRARY_PATH
 2021-04-22 20:25:45 +02:00
github-actions[bot] 120744d620
Merge master into staging-next 2021-04-22 12:06:24 +00:00
Michael Weiss 7495ee4f5f
chromiumDev: 91.0.4472.10 -> 91.0.4472.19 2021-04-22 12:04:15 +02:00
Martin Weinelt 6292be499b
Merge branch 'master' into staging-next 2021-04-22 00:54:14 +02:00
Michael Weiss 3b1b544b8f
Merge pull request #120056 from primeos/chromium 
chromium: 90.0.4430.72 -> 90.0.4430.85
 2021-04-21 22:31:44 +02:00
github-actions[bot] 799ebbc91d
Merge master into staging-next 2021-04-21 18:13:29 +00:00
FliegendeWurst 9c39fef460 tor-browser-bundle-bin: 10.0.15 -> 10.0.16 2021-04-21 18:13:24 +02:00
Michael Weiss a2dd59e0ff
chromium: 90.0.4430.72 -> 90.0.4430.85 
https://chromereleases.googleblog.com/2021/04/stable-channel-update-for-desktop_20.html

This update includes 7 security fixes. Google is aware of reports that
exploits for CVE-2021-21224 exist in the wild.

CVEs:
CVE-2021-21222 CVE-2021-21223 CVE-2021-21224 CVE-2021-21225
CVE-2021-21226
 2021-04-21 15:03:11 +02:00
Michael Weiss 951e888cbd
chromiumBeta: 90.0.4430.72 -> 90.0.4430.85 2021-04-21 15:01:05 +02:00
Michael Weiss 80f4cce6fa
chromiumDev: Fix the patch phase 2021-04-21 15:00:14 +02:00
github-actions[bot] b08c9b444b
Merge master into staging-next 2021-04-20 18:13:16 +00:00
github-actions[bot] e605a07cc0
Merge master into staging-next 2021-04-20 06:06:25 +00:00
Edward Amsden 20483e0c4c
brave: 1.21.77 -> 1.23.71 2021-04-19 21:23:24 -04:00
R. RyanTM ec625a831c ephemeral: 7.0.5 -> 7.1.0 2021-04-19 20:50:06 -04:00
Martin Weinelt 6b34489f81
Merge branch 'master' into staging-next 2021-04-20 02:06:07 +02:00
Martin Weinelt fa03ffe475
Merge pull request #119867 from taku0/firefox-bin-88.0 
firefox-bin: 87.0 -> 88.0
 2021-04-20 01:50:16 +02:00
Bernardo Meurer 44fa00a5b8
Merge pull request #119862 from mweinelt/firefox 
firefox: 87.0 -> 88.0; firefox-esr: 78.9.0esr -> 78.10.0esr
 2021-04-19 19:33:42 +00:00
github-actions[bot] 6ef7c23763
Merge master into staging-next 2021-04-19 18:11:51 +00:00
Sebastian Graf fa7004fd29 firefox: Remove SNAP_NAME=firefox in wrapper 
082ed38 introduced it to fix the profile-per-install policy of FF 67. But since
FF 69 (or 68?), there is `MOZ_LEGACY_PROFILES`, which we use since 87e2618.
There is no reason for the `SNAP_NAME=firefox` workaround anymore.

Additionally, the combination of `SNAP_NAME=firefox` with
a large ~/.nix-profile/share in `XDG_DATA_DIRS` triggered
https://bugzilla.mozilla.org/show_bug.cgi?id=1569625 for me, so this really
fixes a bug in my configuration.

The only downside of this approach is that we lose support for running FF 67
(and possibly 68).
 2021-04-19 14:33:19 +02:00
taku0 b6decc0490 firefox-bin: 87.0 -> 88.0 2021-04-19 21:12:25 +09:00
Martin Weinelt af13285fff
firefox-esr: 78.9.0esr -> 78.10.0esr 
https://www.mozilla.org/en-US/firefox/78.10.0/releasenotes/
 2021-04-19 13:58:29 +02:00
Martin Weinelt 8fe28fb308
firefox: 87.0 -> 88.0 
https://www.mozilla.org/en-US/firefox/88.0/releasenotes/
 2021-04-19 13:58:00 +02:00
github-actions[bot] d4f421cad9
Merge master into staging-next 2021-04-16 12:06:14 +00:00
Shaw Vrana 31f5263929
qutebrowser: 2.1.1 -> 2.2.0 (#119376) 
* pdfjs: 2.6.347 -> 2.8.335

* set QUTE_QTWEBENGINE_VERSION_OVERRIDE

Co-authored-by: Robert Schütz <dev@schuetz-co.de>
 2021-04-16 12:35:14 +02: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
Wesley Merkel 2fc271ffdd Add Firefox libs to beginning of LD_LIBRARY_PATH 
When firefox is executed by programs that also make changes to
`LD_LIBRARY_PATH`, the paths can conflict causing firefox to look for
shared libraries in the wrong location. This is because the wrapper
script around firefox *appends* library paths to `LD_LIBRARY_PATH`
instead of prepending them, causing library paths that are already in
the environment to take precedence over the library paths that firefox
depends on.

As an example, Discord and firefox both depend on different versions of
libnss. When Discord launches firefox, which happens when clicking on
hyperlinks, the path in `LD_LIBRARY_PATH` to libnss set by Discord takes
precedence over then one set by the firefox wrapper script causing
firefox to load a different version of libnss than the one it was built
against. This causes a fatal error in firefox which prevents it from
starting.

This commit fixes this issue by switching the firefox wrapper script to
*prepend* its library paths to `LD_LIBRARY_PATH`.

Fixes #118432
 2021-04-14 10:52:28 -05:00
Michael Weiss de2edb81da
chromium: get-commit-message.py: Deduplicate the CVE list 2021-04-14 14:33:34 +02:00