swendel/nixpkgs
1
0
Fork 0
mirror of https://github.com/SebastianWendel/nixpkgs.git synced 2024-11-06 18:26:45 +01:00
Code Issues Packages Projects Releases Wiki Activity
286987 commits 5 branches 0 tags 31 GiB
Commit graph

4368 commits

Author SHA1 Message Date
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
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
Nikolay Korotkiy f82b01c0d9
lagrange: 1.3.0 → 1.3.2 2021-04-11 20:30:32 +03:00
Michael Weiss 5d775bb2b0
chromiumBeta: Fix the build (#119087) 2021-04-11 10:43:29 +02:00
Bernardo Meurer a451d399d3
Merge pull request #118900 from Luis-Hebendanz/fixing_firefox_issue_#118860 
firefox/wrapper.nix: Fixed issue #118860
 2021-04-10 22:18:22 +00: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
Luis Hebendanz 94d7d46e20 firefox/wrapper.nix: Fixed firefox is always 'managed by your organization' 2021-04-10 01:46:18 +02:00
Michael Weiss 95e9fb16ae
Merge pull request #118893 from primeos/chromium 
chromiumDev: 91.0.4464.5 -> 91.0.4469.4
 2021-04-09 18:51:25 +02:00
Robert Schütz ff0886337b
qutebrowser: don't crash on :version command (#118885) 2021-04-09 13:16:26 +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 c08d9a7e02 firefox: add missing libdrm and libXdamage dependencies 2021-04-09 09:26:12 +02:00
Gabriel Ebner aa0b68b26a chromium: add explicit mesa dependency 2021-04-09 09:26:12 +02:00
Anderson Torres 62670e9613
Merge pull request #118798 from OPNA2608/update/palemoon-29.1.1/21.05 
palemoon: 29.1.0 -> 29.1.1
 2021-04-08 13:03:09 -03:00
Michael Weiss 705e5ae6fb
chromiumBeta: 90.0.4430.51 -> 90.0.4430.61 2021-04-08 16:13:28 +02:00
OPNA2608 7e47d10887 palemoon: 29.1.0 -> 29.1.1 2021-04-08 10:48:12 +02:00
Sandro 7c932296e0
Merge pull request #116335 from SuperSandro2000/move-aliases.nix 2021-04-05 04:07:15 +02:00
Sandro Jäckel 3453b89f4b
lzma: deprecate alias 2021-04-04 19:49:52 +02:00
Robert Schütz 8b65ff2559
Merge pull request #115368 from dotlambda/angelfish-init 
angelfish: init at 1.8.0
 2021-04-04 12:35:03 +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
Sandro 6cd00e17c4
Merge pull request #118263 from dotlambda/qutebrowser-2.1.1 
qutebrowser: 2.1.0 -> 2.1.1
 2021-04-01 23:48:45 +02:00
Michael Weiss 985e98f4c4
chromiumDev: 91.0.4455.2 -> 91.0.4464.5 2021-04-01 20:17:45 +02:00
Robert Schütz d98452864f qutebrowser: 2.1.0 -> 2.1.1 2021-04-01 18:39:09 +02:00
Daniel Nagy fd56ee7964
amfora: add changelog 2021-04-01 17:59:47 +02:00
Sandro 4a3774f7df
Merge pull request #118056 from jb55/gmni 2021-04-01 13:55:03 +02:00
Michael Weiss e8c1d93f49
chromiumBeta: 90.0.4430.40 -> 90.0.4430.51 2021-04-01 13:48:45 +02:00
Ben Sima 4b8f14d9cb gmni: init at unstable-2021-03-26 
Reviewed-by: William Casarin <jb55@jb55.com>
Link: https://lists.sr.ht/~andir/nixpkgs-dev/%3C20210330145338.8149-1-ben@bsima.me%3E
 2021-03-31 13:39:57 -07:00
Michael Weiss d40c8f6279
ungoogled-chromium: 89.0.4389.90 -> 89.0.4389.114 2021-03-31 21:11:22 +02:00
Michael Weiss 82f3a0d20e
Merge pull request #118133 from primeos/chromium 
chromium: 89.0.4389.90 -> 89.0.4389.114
 2021-03-31 19:44:34 +02:00
Robert Schütz a0ec0bbd63 angelfish: init at 1.8.0 2021-03-31 17:06:13 +02:00
Nikolay Korotkiy 6dfaa2884a
lagrange: 1.2.2 → 1.3.0 2021-03-31 15:34:51 +03: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
Sandro 262a728ae5
Merge pull request #117867 from mrVanDalo/feature/tor-browser-override 
tor-browser-bundle-bin: make overrideAttrs work
 2021-03-29 00:09:38 +02:00
FliegendeWurst d0ee6127dc tor-browser-bundle-bin: 10.0.14 -> 10.0.15 2021-03-28 11:25:58 +02:00
Ingolf Wagner 8dadf3873f
tor-browser-bundle-bin: make overrideAttrs work 2021-03-28 09:22:07 +02:00
thyol 14d136c0a7 tor-browser-bundle-bin: 10.0.13 -> 10.0.14 2021-03-27 21:44:18 +01:00
rnhmjoj d3ebe83408 qutebrowser: add pynacl for qute-keepassxc 
Requested by @wedens.
 2021-03-27 12:35:06 +01:00
rnhmjoj b710cdf80a qutebrowser: 2.0.2 -> 2.1.0 2021-03-27 12:35:06 +01: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
R. RyanTM dfd5d237d9 links2: 2.21 -> 2.22 2021-03-23 14:16:38 -04:00
stigtsp 4787a38c70
Merge pull request #117343 from taku0/firefox-bin-87.0 
firefox-bin: 86.0.1 -> 87.0
 2021-03-23 14:29:33 +01:00
Martin Weinelt 4a8aaa58ad
firefox, firefox-esr: add myself to maintainers 2021-03-22 16:09:57 +01:00
Martin Weinelt 9a0519f080
firefox-esr: 78.8.0esr -> 78.9.0esr 2021-03-22 15:05:56 +01:00
Martin Weinelt e9dbf1a586
firefox: 86.0.1 -> 87.0 2021-03-22 15:05:37 +01:00
taku0 d7bba3e5da firefox-bin: 86.0.1 -> 87.0 2021-03-22 21:12:24 +09:00
Badi Abdul-Wahid 46318ab4df
vivaldi: 3.6.2165.36-1 -> 3.7.2218.45-1 2021-03-20 19:46:58 -05:00
github-actions[bot] c804f22a81
Merge master into staging-next 2021-03-19 12:26:52 +00:00
Michael Weiss 33bd43d2ea
chromiumDev: 91.0.4442.4 -> 91.0.4449.6 2021-03-19 11:26:49 +01:00
Jan Tojnar 2445e9a681
Merge branch 'master' into staging-next 2021-03-18 19:24:39 +01:00
Jan Tojnar 0136206b12
Merge branch 'master' into staging-next 2021-03-18 13:35:59 +01:00
Michael Weiss 622a4a2dd5
chromiumBeta: 90.0.4430.19 -> 90.0.4430.30 2021-03-18 13:11:08 +01:00
R. RyanTM d1d081daee
brave: 1.21.76 -> 1.21.77 (#116597) 2021-03-17 20:28:17 +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
Vladimír Čunát e3597057e7
Merge #116040: firefox-bin: 86.0 -> 86.0.1 2021-03-17 06:33:33 +01:00
github-actions[bot] d18aaddde4
Merge master into staging-next 2021-03-16 00:39:08 +00: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
github-actions[bot] 4915d2cb4c
Merge master into staging-next 2021-03-15 18:16:46 +00:00
Sandro ba5d0fcf89
Merge pull request #116130 from r-ryantm/auto-update/brave 
brave: 1.21.74 -> 1.21.76
 2021-03-15 15:34:36 +01:00
github-actions[bot] dec95bae4a
Merge master into staging-next 2021-03-15 12:25:41 +00: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
Martin Weinelt a390e92928 firefox: 86.0 -> 86.0.1 2021-03-14 16:24:12 +01:00
Martin Weinelt a613684873 firefox: 85.0.2 -> 86.0 2021-03-14 16:21:49 +01:00
Michael Weiss bb52ac0cb0
ungoogled-chromium: 89.0.4389.82 -> 89.0.4389.90 2021-03-14 13:35:12 +01:00
github-actions[bot] 8c04f70ddd
Merge master into staging-next 2021-03-14 12:21:07 +00:00
Bernardo Meurer dd58f3ad13
firefox-bin: add pciutils to libPath 2021-03-13 22:09:09 -08:00
github-actions[bot] c596c93079
Merge master into staging-next 2021-03-14 00:41:40 +00: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
Jan Tojnar 01a4d350c7
Merge branch 'master' into staging-next 
Reverted https://github.com/NixOS/nixpkgs/pull/115228 for kodi to avoid conflict.

It does not look like unzip would be used but not investigating now to speed up merge conflict resolution.
 2021-03-13 19:16:43 +01:00
Sandro 34405e2ca5
Merge pull request #116178 from logan12358/use-fetchFromSourcehut 
aerc, asuka, scdoc, wev, wlsunset, wshowkeys: use fetchFromSourceHut
 2021-03-13 16:54:35 +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
github-actions[bot] e1ede8b801
Merge master into staging-next 2021-03-13 12:21:02 +00: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
Julien Langlois 2fad2f2d68
google-chrome: add vulkan support 2021-03-13 12:35:20 +01:00
Julien Langlois ed0d586941
google-chrome: add libva support 
Chrome cannot do hardware video acceleration without libva in its search
path. This just adds libva. Tested against a VP9 video looking at
chrome://media-internals and intel_gpu_top.
 2021-03-13 12:35:18 +01:00