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

4361 commits

Author SHA1 Message Date
John Ericson 17305d2df0
Merge pull request #111487 from Ericson2314/llvm-outputs-and-cross-compile-tools 
llvmPackages: Clean up outputs
 2021-04-30 11:28:08 -04:00
Michael Weiss 7fff32f51b
Merge pull request #121150 from primeos/ungoogled-chromium 
ungoogled-chromium: 90.0.4430.85 -> 90.0.4430.93
 2021-04-30 13:37:24 +02:00
Sandro 9726379687
Merge pull request #120923 from sikmir/lagrange 
lagrange: 1.3.2 → 1.3.4
 2021-04-30 08:53:47 +02:00
Robert Schütz cba5ac76a2 qutebrowser: 2.2.0 -> 2.2.1 
https://github.com/qutebrowser/qutebrowser/releases/tag/v2.2.1
 2021-04-30 01:46:14 -04:00
Andrew Childs 7869d16545 llvmPackages: Multuple outputs for everythting 
Also begin to start work on cross compilation, though that will have to
be finished later.

The patches are based on the first version of
https://reviews.llvm.org/D99484. It's very annoying to do the
back-porting but the review has uncovered nothing super major so I'm
fine sticking with what I've got.

Beyond making the outputs work, I also strove to re-sync the packages,
as they have been drifting pointlessly apart for some time.

----

Other misc notes, highly incomplete

- lvm-config-native and llvm-config are put in `dev` because they are
  tools just for build time.

- Clang no longer has an lld dep. That was introduced in
  db29857eb3, but if clang needs help
  finding lld when it is used we should just pass it flags / put in the
  resource dir. Providing it at build time increases critical path
  length for no good reason.

----

A note on `nativeCC`:

`stdenv` takes tools from the previous stage, so:

1. `pkgsBuildBuild`: `(?1, x, x)`
2. `pkgsBuildBuild.stdenv.cc`: `(?0, ?1, x)`

while:

1. `pkgsBuildBuild`: `(?1, x, x)`
2. `pkgsBuildBuild.targetPackages`: `(x, x, ?2)`
3. `pkgsBuildBuild.targetPackages.stdenv.cc`: `(?1, x, x)`
 2021-04-30 05:41:00 +00:00
Sandro 2201c19776
Merge pull request #120891 from lunik1/opera-fix-build 
opera: add libdrm and mesa dependencies
 2021-04-30 06:34:27 +02:00
Sandro 75a24a5bc9
Merge pull request #121170 from samuelgrf/add-mainProgram-to-packages 2021-04-30 01:20:37 +02:00
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
Samuel Gräfenstein c7aa3db361
tor-browser-bundle-bin: add meta.mainProgram 2021-04-29 16:13:04 +02:00
Samuel Gräfenstein a4895f7183
google-chrome*: add meta.mainProgram 2021-04-29 14:51:41 +02:00
Michael Weiss dbfd9c4942
ungoogled-chromium: 90.0.4430.85 -> 90.0.4430.93 2021-04-29 14:07:39 +02: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
Nikolay Korotkiy 261069c250
lagrange: 1.3.2 → 1.3.4 2021-04-27 22:25:01 +03:00
lunik1 f3709c804d
opera: add libdrm and mesa dependencies 
Fixes #120873
 2021-04-27 17:50:43 +01: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