JakeHillion/nixpkgs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
206,203 Commits 2 Branches 0 Tags 13 GiB
65061ab2ae
Commit Graph

3284 Commits

Author SHA1 Message Date
zowoq
c6d11ef7f3 brave: 1.0.0 -> 1.1.23 2019-12-21 13:35:19 +10:00
Tim Steinbach
6f845885c4
vivaldi: 2.9.1705.41-1 -> 2.10.1745.21-1 2019-12-20 11:28:50 -05:00
Ivan Kozik
5dd4f1d0b9 chromium: 79.0.3945.79 -> 79.0.3945.88 
https://chromereleases.googleblog.com/2019/12/stable-channel-update-for-desktop_17.html

CVE-2019-13767
 2019-12-18 04:56:50 +00:00
Graham Christensen
aa4a1b01d5
Merge pull request #75516 from ivan/chromium-79.0.3945.79 
chromium: 78.0.3904.108 -> 79.0.3945.79
 2019-12-15 14:48:34 -05:00
Andrew Childs
b29e3582ac chromium: add thefloweringash (myself) as maintainer 
I have an interest in making Chromium available on Aarch64. I'm adding
myself here on a recommendation from @ivan [1].

[1] https://github.com/NixOS/nixpkgs/pull/74015#issuecomment-565780595
 2019-12-15 21:34:22 +09:00
worldofpeace
be13df6c76
Merge pull request #75465 from worldofpeace/gnome-args 
doc/gnome: update wrapper args example, remove proliferated uses
 2019-12-15 00:13:17 -05:00
worldofpeace
abe3475df8 treewide: remove bash snippets in flags 
Co-Authored-By: Jan Tojnar <jtojnar@gmail.com>
 2019-12-15 00:10:41 -05:00
Ivan Kozik
af006f9ff3 chromium: fix enableWideVine for v79 which needs the manifest.json in WidevineCdm/ 2019-12-15 04:56:01 +00:00
Ivan Kozik
3d71db8abb chromium: explain enable_widevine = true 2019-12-15 04:55:59 +00:00
Ivan Kozik
950230bc84 chromium: remove enableNaCl option 
This hasn't worked since 2016 (https://github.com/NixOS/nixpkgs/issues/13983)
and is being removed very soon, per "Q4 2019" in
https://developer.chrome.com/native-client/migration

(It's staying around for "Chrome Apps", but those only run on ChromeOS now.)

earth.google.com users can use https://earth.google.com/web/?beta=1 to get
the wasm version instead of the PNaCl version.
 2019-12-15 04:55:30 +00:00
Ivan Kozik
ec75ea3329 chromium: use llvmPackages_9 to more closely match upstream 2019-12-15 04:35:36 +00:00
Ivan Kozik
46d252f1f1 chromium: fix GL support by not using the ANGLE GL implementation 2019-12-15 04:35:23 +00:00
cap
e99248632e tor-browser-bundle-bin: add cap to maintainers 2019-12-13 20:20:52 +01:00
cap
fca98ea5be tor-browser-bundle-bin: 9.0.1 -> 9.0.2 2019-12-13 20:12:23 +01:00
Ivan Kozik
14b40e291d chromium: 78.0.3904.108 -> 79.0.3945.79 
https://chromereleases.googleblog.com/2019/12/stable-channel-update-for-desktop.html

CVE-2019-13725 CVE-2019-13726 CVE-2019-13727 CVE-2019-13728
CVE-2019-13729 CVE-2019-13730 CVE-2019-13732 CVE-2019-13734
CVE-2019-13735 CVE-2019-13764 CVE-2019-13736 CVE-2019-13737
CVE-2019-13738 CVE-2019-13739 CVE-2019-13740 CVE-2019-13741
CVE-2019-13742 CVE-2019-13743 CVE-2019-13744 CVE-2019-13745
CVE-2019-13746 CVE-2019-13747 CVE-2019-13748 CVE-2019-13749
CVE-2019-13750 CVE-2019-13751 CVE-2019-13752 CVE-2019-13753
CVE-2019-13754 CVE-2019-13755 CVE-2019-13756 CVE-2019-13757
CVE-2019-13758 CVE-2019-13759 CVE-2019-13761 CVE-2019-13762
CVE-2019-13763

The new widevine patch was taken from
https://git.archlinux.org/svntogit/packages.git/plain/trunk/chromium-widevine.patch?h=packages/chromium
 2019-12-11 15:55:21 +00:00
adisbladis
7559235792
firefox-beta-bin: 72.0b1 -> 72.0b4 2019-12-09 11:33:42 +00:00
adisbladis
e8777e45e4
firefox-devedition-bin: 72.0b1 -> 72.0b4 2019-12-09 11:33:38 +00:00
Franz Pletz
a1e4ee6d4f
firefox: fix indexedDB for 71.0 
Adapted original patch[0] to also fix dom localstorage.

[0]: https://bugzilla.mozilla.org/show_bug.cgi?id=1601707#c6
 2019-12-07 19:28:47 +01:00
worldofpeace
0c8dadd9e5
Merge pull request #75040 from worldofpeace/remove-terror-webkitgtk 
🙈️ Remove webkitgtk24x
 2019-12-06 22:02:50 -05:00
Eduardo Quiros
476dc9e21a qutebrowser: 1.8.2 -> 1.8.3 2019-12-05 16:00:52 -06:00
worldofpeace
afb2182f33 uzbl: remove 
https://github.com/uzbl/uzbl/issues/408

Frightening version of webkitgtk used here.
 2019-12-05 07:01:27 -05:00
worldofpeace
37793c8099 vimprobable2: remove 2019-12-05 05:53:09 -05:00
Andreas Rammhold
8465cae85c
Merge pull request #74905 from andir/firefox-71 
firefox: 70.0.1 -> 71.0
 2019-12-05 10:45:34 +01:00
Andreas Rammhold
1993a8bb45
firefox-esr-68: 68.2.0esr -> 68.3.0esr 2019-12-03 14:52:06 +01:00
Andreas Rammhold
ff0cd023ef
firefox-devedition-bin: 71.0b6 -> 72.0b1 2019-12-03 12:10:45 +01:00
Andreas Rammhold
bbb74cdb3c
firefox-beta-bin: 71.0b6 -> 72.0b1 2019-12-03 12:10:26 +01:00
Andreas Rammhold
ba1acd2f0c
firefox-bin: 70.0.1 -> 71.0 2019-12-03 12:10:06 +01:00
Andreas Rammhold
8eb6c64404 firefox: 70.0.1 -> 71.0 2019-12-03 11:38:30 +01:00
Jan Tojnar
55a72926e1
Merge branch 'staging-next' into staging 2019-11-30 19:45:46 +01:00
Jan Tojnar
a69ad18da9
Merge branch 'master' into staging-next 2019-11-30 19:44:51 +01:00
R. RyanTM
3b15a7132a opera: 64.0.3417.83 -> 65.0.3467.48 (#74502) 2019-11-30 16:54:41 +01:00
Frederik Rietdijk
9f84415541 Merge staging-next into staging 2019-11-30 08:58:01 +01:00
Frederik Rietdijk
d14baf7747 Merge master into staging-next 2019-11-30 08:57:28 +01:00
worldofpeace
6687a4a727
Merge pull request #74265 from worldofpeace/next-fix 
next: Fix #74258
 2019-11-29 02:51:41 +00:00
Jonathan Ringer
0c1c18ca44
Merge branch 'master' into staging-next 2019-11-27 22:57:50 -08:00
worldofpeace
417d6354c8 next: Fix #74258 
Next had a few issues with its packaging:
* the platform port was exposed in all-packages
  And this is not useful for outside users.
  It's now a local attribute in the next package.

* the platform port wasn't wrapped correctly
  It appears that the lisp core was being wrapped,
  when instead the actual gtk application that's
  called within the lisp core had to be wrapped.

* codestyle/indentation
 2019-11-26 11:41:50 -05:00
Maximilian Bosch
448ff7d44f
Merge pull request #74263 from emmanuelrosa/qutebrowser-1.8.2 
qutebrowser: 1.8.1 -> 1.8.2
 2019-11-26 15:30:23 +01:00
Emmanuel Rosa
33d18156f9 qutebrowser: 1.8.1 -> 1.8.2 2019-11-26 20:04:38 +07:00
Andrew Childs
6ec5e745dc chromium: fix aarch64 build 
The skia patch no longer applies, and is no longer necessary.

The current version of chromium doesn't build with gcc. This has been
fixed upstream[1] and could be backported, but switching aarch64 to
clang/llvm and making the build the same on all platforms is simpler.

[1] 9662ec8440
 2019-11-26 01:25:39 +01:00
Frederik Rietdijk
06a054e6eb Merge master into staging-next 2019-11-25 21:51:57 +01:00
John Ericson
4f1261134e Merge remote-tracking branch 'upstream/master' into staging 2019-11-24 18:33:54 +00:00
John Ericson
1206faa6d5
Merge pull request #74057 from Ericson2314/wrapper-pname-support 
treewide: Purge most parseDrvName
 2019-11-24 13:31:35 -05:00
Herwig Hochleitner
a52d7674cc chromium: update vaapi patch 
https://github.com/NixOS/nixpkgs/issues/73878
 2019-11-24 19:07:59 +01:00
John Ericson
d34d84a61d firefox-wrapper: Get rid of name argument 
Only pname + version is supported now. (Both are still optional,
however.)
 2019-11-24 17:27:45 +00:00
John Ericson
d0d5136cce Merge remote-tracking branch 'upstream/master' into wrapper-pname-support 2019-11-24 17:25:07 +00:00
John Ericson
9b090ccbca treewide: Get rid of most parseDrvName without breaking compat 
That is because this commit should be merged to both master and
release-19.09.
 2019-11-24 17:22:28 +00:00
Frederik Rietdijk
1d18c5a0fe Merge staging-next into staging 2019-11-24 10:13:31 +01:00
worldofpeace
82f1e398d1 ephemeral: 6.0.0 -> 6.1.1 
https://github.com/cassidyjames/ephemeral/releases/tag/6.1.1
 2019-11-21 08:36:21 -05:00
Frederik Rietdijk
10d0c68a9b Merge staging-next into staging 2019-11-20 10:02:21 +01:00
Frederik Rietdijk
5f8b0d7d99 Merge staging-next into staging 2019-11-19 14:53:29 +01:00