Age | Commit message (Collapse) | Author | Files | Lines | |
---|---|---|---|---|---|
2022-06-25 | Merge pull request #178390 from aszlig/firefox-fix-signing-required-detection | Martin Weinelt | 1 | -2/+5 | |
2022-06-23 | Merge pull request #178645 from primeos/ungoogled-chromium | Michael Weiss | 3 | -55/+8 | |
ungoogled-chromium: 102.0.5005.115 -> 103.0.5060.53 | |||||
2022-06-23 | treewide/applications: add `sourceType` `binaryNativeCode` for many packages | Robert Scott | 3 | -0/+3 | |
2022-06-23 | ungoogled-chromium: 102.0.5005.115 -> 103.0.5060.53 | Michael Weiss | 3 | -55/+8 | |
2022-06-21 | chromium: 102.0.5005.115 -> 103.0.5060.53 | Michael Weiss | 1 | -10/+10 | |
https://chromereleases.googleblog.com/2022/06/stable-channel-update-for-desktop_21.html This update includes 14 security fixes. CVEs: CVE-2022-2156 CVE-2022-2157 CVE-2022-2158 CVE-2022-2160 CVE-2022-2161 CVE-2022-2162 CVE-2022-2163 CVE-2022-2164 CVE-2022-2165 | |||||
2022-06-21 | firefox: Improve detecting signing requirements | aszlig | 1 | -2/+5 | |
Firefox 61 started to enforce signatures for add-ons and since commit d031843a1eee244172570c64c9e238641563e68e, we get an evaluation error that recommends the user to switch to Firefox ESR. This isn't an option for everyone and as I also pointed out in the pull request[1] introducing the above commit, I've been building Firefox like this: let firefoxNoSigning = firefox-unwrapped.overrideAttrs (lib.const { MOZ_REQUIRE_SIGNING = false; }); in wrapFirefox firefoxNoSigning { nixExtensions = ...; } However, this only works after manually modifying nixpkgs (or copy & paste wrapper.nix elsewhere) every time I want to have a new Firefox version. Of course, this gets annoying and tedious after a while, so this motivated me to properly fix this to not only check for an ESR version but also check the value of MOZ_REQUIRE_SIGNING. Note that I'm using toString here to check for the value because there are several ways (false, null, "", ...) to set the environment variable to an empty string and toString makes sure that it really is the desired behaviour. I specifically checked the Firefox source and also tested this with multiple values and only building with MOZ_REQUIRE_SIGNING set to an empty string seems to work (no "0", "false" or other variants). Additionally, there is another method to allow unsigned add-ons, which is by using the --with-unsigned-addon-scopes configure option[2]. Unfortunately, this does not work with nixExtensions because we don't have (or want) a central directory where those add-ons reside. Given that nixExtensions disallows manually installing add-ons, setting MOZ_REQUIRE_SIGNING to false should be safe in this case. [1]: https://github.com/NixOS/nixpkgs/pull/133504 [2]: https://bugs.archlinux.org/task/63075 Signed-off-by: aszlig <aszlig@nix.build> | |||||
2022-06-20 | Merge pull request #178303 from Icy-Thought/master | Anderson Torres | 1 | -2/+2 | |
brave: 1.38.115 -> 1.39.122 | |||||
2022-06-20 | Merge pull request #178279 from primeos/chromiumDev | Michael Weiss | 1 | -5/+5 | |
chromiumDev: 104.0.5110.0 -> 104.0.5112.12 | |||||
2022-06-20 | brave: 1.38.115 -> 1.39.122 | Icy-Thought | 1 | -2/+2 | |
2022-06-19 | chromiumDev: 104.0.5110.0 -> 104.0.5112.12 | Michael Weiss | 1 | -5/+5 | |
2022-06-19 | vivaldi: 5.3.2679.55-1 -> 5.3.2679.58-1 | José Romildo | 1 | -2/+2 | |
2022-06-19 | Merge master into staging-next | github-actions[bot] | 2 | -7/+8 | |
2022-06-19 | Merge pull request #175158 from kuwii/dev/microsoft-edge | Sandro | 2 | -7/+8 | |
microsoft-edge: 100.0.1185.44 -> 102.0.1245.44 | |||||
2022-06-18 | Merge master into staging-next | github-actions[bot] | 1 | -3/+3 | |
2022-06-19 | microsoft-edge: 100.0.1185.44 -> 102.0.1245.44 | kuwii | 2 | -7/+8 | |
2022-06-18 | chromiumBeta: 103.0.5060.42 -> 103.0.5060.53 | Michael Weiss | 1 | -3/+3 | |
2022-06-15 | Merge master into staging-next | github-actions[bot] | 1 | -5/+5 | |
2022-06-15 | Merge pull request #176206 from squalus/librewolf | Sandro | 1 | -5/+5 | |
librewolf: 100.0.2-1 -> 101.0.1-1 | |||||
2022-06-15 | Merge master into staging-next | github-actions[bot] | 1 | -2/+2 | |
2022-06-14 | Merge pull request #177402 from romildo/upd.vivaldi | Sandro | 1 | -2/+2 | |
2022-06-14 | Merge master into staging-next | github-actions[bot] | 1 | -3/+3 | |
2022-06-14 | Merge pull request #177583 from panicgh/tbb | Martin Weinelt | 1 | -3/+3 | |
2022-06-14 | Merge master into staging-next | github-actions[bot] | 1 | -1/+8 | |
2022-06-14 | tor-browser-bundle-bin: 11.0.13 -> 11.0.14 | Nicolas Benes | 1 | -3/+3 | |
2022-06-13 | palemoon: Limit build cores count | OPNA2608 | 1 | -1/+8 | |
Building with too many cores may be the cause of the build flakiness with OfBorg. Upstream says <=32 cores should work fine, let's see if this helps. https://forum.palemoon.org/viewtopic.php?f=5&t=28480 | |||||
2022-06-13 | Merge master into staging-next | github-actions[bot] | 7 | -0/+7 | |
2022-06-13 | yandex-browser: mark meta.sourceProvenance | FliegendeWurst | 1 | -0/+1 | |
2022-06-13 | vivaldi: mark meta.sourceProvenance | FliegendeWurst | 1 | -0/+1 | |
2022-06-13 | microsoft-edge: mark meta.sourceProvenance | FliegendeWurst | 1 | -0/+1 | |
2022-06-13 | firefox-bin: mark meta.sourceProvenance | FliegendeWurst | 1 | -0/+1 | |
2022-06-13 | google-chrome: mark meta.sourceProvenance | FliegendeWurst | 1 | -0/+1 | |
2022-06-13 | opera: mark meta.sourceProvenance | FliegendeWurst | 1 | -0/+1 | |
2022-06-13 | tor-browser-bundle-bin: mark meta.sourceProvenance | FliegendeWurst | 1 | -0/+1 | |
2022-06-13 | Merge master into staging-next | github-actions[bot] | 1 | -2/+2 | |
2022-06-12 | librewolf: 100.0.2-1 -> 101.0.1-1 | squalus | 1 | -5/+5 | |
2022-06-12 | Merge pull request #177295 from OPNA2608/fix/palemoon-31.1.0 | Anderson Torres | 1 | -2/+2 | |
palemoon: Fix 31.1.0 bump | |||||
2022-06-13 | Merge master into staging-next | github-actions[bot] | 1 | -1/+1 | |
2022-06-12 | vivaldi: 5.3.2679.38-1 -> 5.3.2679.55-1 | José Romildo | 1 | -2/+2 | |
2022-06-12 | Merge master into staging-next | github-actions[bot] | 1 | -5/+5 | |
2022-06-12 | buildMozillaMach: allow PGO on all Linux platforms | Martin Weinelt | 1 | -1/+1 | |
Tested on the aarch64 community builder and it didn't get stuck like back when we first tried to enable PGO. | |||||
2022-06-12 | Merge pull request #177330 from primeos/ungoogled-chromium | Michael Weiss | 1 | -5/+5 | |
ungoogled-chromium: 102.0.5005.61 -> 102.0.5005.115 | |||||
2022-06-12 | Merge master into staging-next | github-actions[bot] | 1 | -393/+393 | |
2022-06-11 | ungoogled-chromium: 102.0.5005.61 -> 102.0.5005.115 | Michael Weiss | 1 | -5/+5 | |
2022-06-11 | palemoon: Fix 31.1.0 bump | OPNA2608 | 1 | -2/+2 | |
2022-06-11 | firefox-devedition-bin-unwrapped: 102.0b5 -> 102.0b6 | R. Ryantm | 1 | -393/+393 | |
2022-06-11 | Merge master into staging-next | github-actions[bot] | 5 | -1197/+1197 | |
2022-06-10 | firefox-devedition-bin-unwrapped: 102.0b1 -> 102.0b5 | Martin Weinelt | 1 | -393/+393 | |
2022-06-10 | firefox-beta-bin-unwrapped: 102.0b1 -> 102.0b5 | Martin Weinelt | 1 | -393/+393 | |
2022-06-10 | firefox-bin-unwrapped: 101.0 -> 101.0.1 | Martin Weinelt | 1 | -393/+393 | |
https://www.mozilla.org/en-US/firefox/101.0.1/releasenotes/ | |||||
2022-06-10 | firefox-unwrapped: 101.0 -> 101.0.1 | R. Ryantm | 1 | -2/+2 | |
https://www.mozilla.org/en-US/firefox/101.0.1/releasenotes/ |