summary refs log tree commit diff
path: root/pkgs/applications/networking/browsers/chromium/source
Commit message (Collapse)AuthorAge
* chromium: UpdatesWilliam A. Kennington III2015-09-30
| | | | | | | Built and run locally - Beta: 46.0.2490.33 -> 46.0.2490.42 - Stable: 45.0.2454.99 -> 45.0.2454.101
* chromium-dev: Revert to 47.0.2508.0Eelco Dolstra2015-09-28
| | | | | | | 47.0.2516.0 doesn't build. http://hydra.nixos.org/build/26422610 http://hydra.nixos.org/build/26422600
* chromium: UpdatesWilliam A. Kennington III2015-09-23
| | | | | - stable: 45.0.2454.93 -> 45.0.2454.99 - dev: 47.0.2508.0 -> 47.0.2516.0
* chromium: remove preferLocalBuildDomen Kožar2015-09-20
| | | | | | | | | | | | | | | | | It's another attempt to fix chromium builds. See http://hydra.nixos.org/build/26086977/nixlog/4/raw Unpacking sources is actually taking more than 2h so build fails. Instead, rather build it remotely and then copy over the output as we don't have limits for download time. See 089bdce621c1e5e5ff85b5a6e8077c21bcee2685 for reference cc @aszlig (cherry picked from commit cef54e7d67870ff68c9787ff60cd50ca4bf1d8af) Signed-off-by: Domen Kožar <domen@dev.si>
* chromium: UpdatesWilliam A. Kennington III2015-09-17
| | | | | | - dev: 47.0.2503.0 -> 47.0.2508.0 - beta: 46.0.2490.22 -> 46.0.2490.33 - stable: 45.0.2454.85 -> 45.0.2454.93
* chromiumBeta: UpdateWilliam A. Kennington III2015-09-13
|
* chromium: Dev / Beta UpdatesWilliam A. Kennington III2015-09-08
|
* chromium: UpdatesWilliam A. Kennington III2015-09-01
| | | | This bumps the stable and dev track forward a version
* chromium: UpdatesWilliam A. Kennington III2015-08-21
|
* chromiumBeta: 45.0.2454.26 -> 45.0.2454.37William A. Kennington III2015-08-14
|
* chromium: UpdatesWilliam A. Kennington III2015-08-11
|
* chromium: Update beta and dev channels.aszlig2015-08-11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Overview of the updated versions: beta: 45.0.2454.15 -> 45.0.2454.26 dev: 45.0.2454.15 -> 46.0.2471.2 Changes for getting beta and dev channel to build: * The reference for chrome::FILE_FLASH_PLUGIN doesn't exist anymore in version 46, because it has been dropped upstream, see the following review URL: https://codereview.chromium.org/1255943002 We set the PPAPI Flash path using a command line flag anyway, so it doesn't hurt us if we don't patch that path (which was an old artifact from the NSAPI->PPAPI conversion anyway). Changes for the dev channel only: * It seems that in the SCM, chrome/test/data/webui/ contains a lot of files, however they are missing in the tarball. This has been reported upstream at: https://crbug.com/515917 Our fix is to just not include webui/i18n_process_css_test.html at all, to avoid the configure (gyp) phase to fail, because we're not building tests anyway. All channels built and tested by my Hydra instance at: https://headcounter.org/hydra/eval/218978 Test reports: x86: https://headcounter.org/hydra/build/723341/download/1/log.html x86_64: https://headcounter.org/hydra/build/723342/download/1/log.html Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* chromium: Cleanup old patch and update stableWilliam A. Kennington III2015-08-05
|
* chromium: UpdatesWilliam A. Kennington III2015-07-30
|
* chromium: Add another mirror for Chrome deb.aszlig2015-07-30
| | | | | | | | | | | | | | | The only mirror left which still has the .deb for 44.0.2403.89 is http://mirror.pcbeta.com/, but that one doesn't seem to be reachable from certain contries. And according to @CestDiego, it doesn't seem to be reachable from within the US. Closes #9021, thanks to @CestDiego for reporting. Signed-off-by: aszlig <aszlig@redmoonstudios.org> Reported-by: Diego Berrocal <cestdiego@gmail.com> Tested-by: Diego Berrocal <cestdiego@gmail.com>
* chromium: BumpWilliam A. Kennington III2015-07-26
|
* chromium: Update stable 43 -> 44William A. Kennington III2015-07-21
|
* chromium-dev: UpdateWilliam A. Kennington III2015-07-20
|
* chromium: Minor updatesWilliam A. Kennington III2015-07-15
| | | | | Notably a version bump for Flash Player to 18.0.0.209-r1
* chromium: Update stable and beta channels.aszlig2015-07-04
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | Overview of the updated versions: stable: 43.0.2357.125 -> 43.0.2357.130 beta: 44.0.2403.52 -> 44.0.2403.61 For the beta channel the following changes were necessary: * Drop all patches which were added in c290595 because they apply to 44.0.2403.52 only. The shipped version of Blink was older than the one used for Chromium itself and thus contained just the cherry-picked patches from upstream Blink. * The ffmpegsumo library is now statically linked the same way as in the dev version, so let's not try to put it into the output store path. All channels were built successfully on my Hydra at: https://headcounter.org/hydra/eval/187176 VM tests did also pass and can be found at: x86: https://headcounter.org/hydra/build/707636 x86_64: https://headcounter.org/hydra/build/707637 Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* chromium: Disable setuid sandbox without errors.aszlig2015-07-04
| | | | | | | | | | | | | | | | | Just silencing the error will not prevent Chromium from trying to start up the SUID sandbox anyway, thus flooding stderr with: LaunchProcess: failed to execvp: After digging a bit in the source code I found out that the SUID sandbox binary is indeed used, but only for setting oom_score_adj within the user namespace (as "root"). So let's build the sandbox binary and of course don't set setuid bit. These annoying error messages were originally introduced by 0aad4b7 and I'm deeply sorry for annoying you guys out there with them. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* chromium: Remove out-of-tree sandbox derivation.aszlig2015-07-04
| | | | | | | | | | | | | | Since 0aad4b7, we no longer need to have an external sandbox binary, because the upstream implementation of the user namespace sandbox no longer needs an external sandbox binary. In our implementation of the user namespace sandbox, we (ab)used the setuid sandbox to run non-setuid and set up user namespaces instead. Because our implementation is no longer needed, we can safely drop the external binary entirely. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* chromium: Remove obsolete sandbox_userns_36.patch.aszlig2015-07-04
| | | | | | | The file is no longer referenced since 6a8afa4 and thus can be safely dropped. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* chromium: Update all channels to latest versions.aszlig2015-06-23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Overview of the updated versions: stable: 43.0.2357.124 -> 43.0.2357.125 beta: 44.0.2403.39 -> 44.0.2403.52 [1] dev: 45.0.2421.0 -> 45.0.2431.0 [2] [1] Beta channel fixes: I had to fetch a patch from a newer revision of Blink (r195908), see https://codereview.chromium.org/1157943002/ for more information about the patch. Here is the failing build log: https://headcounter.org/hydra/build/704037/nixlog/2 Another fix for Blink, was needed in order to get it to build, see: https://codereview.chromium.org/1156113007/ Also I needed to revert https://codereview.chromium.org/1150543002/ using another patch, because the build won't succeed and bail out with WEBRTC_VIDEO_CODEC_FALLBACK_SOFTWARE not being found (it's only used once in the source, but isn't defined anywhere). Here are the trybot results: https://chromium-cq-status.appspot.com/patch-status/1150543002/20001 [2] Dev channel fixes: The "ffmpegsumo" shared library is now no longer built, because it is now statically linked against Chromium, for details see: https://codereview.chromium.org/1141703002 All channels built and tested on my Hydra at: https://headcounter.org/hydra/eval/178458 Test reports: x86: https://headcounter.org/hydra/build/704908/download/1/log.html x86_64: https://headcounter.org/hydra/build/704914/download/1/log.html Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* chromium: Drop plugin_paths patch for old versions.aszlig2015-06-11
| | | | | | The patch was for versions prior to version 22, so we no longer need it. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* chromium: Fix plugin_paths patch for version 44.aszlig2015-06-11
| | | | | | | | | The pepper effects plugin has been removed and migrated to NaCl, so I'm just dropping the hunk of that patch. Upstream reviow URL: https://codereview.chromium.org/1085393003 Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* Chromium: Update and build fixes.Ambroz Bizjak2015-06-11
| | | | | | | | | | Changes included: - Update versions. - Use gyp package not gyp_svn1977. - Remove icu from buildInputs, since this causes a build error due to inferference with use_system_icu=false. - Remove the hack that inserts the absolute path into gyp files, and pass `--depth .` to gyp. This resolves the `third_party/angle` gyp error. - Do a normal copy of the source code not a symlink copy. This resolves some link error where the symlinks interfere with relative paths (seems like because gyp resolves symlinks first). Note, this used to be worked around with the absolute path insertion hack. - Change the bucketURL in update.nix to https (for more secure updates).
* chromium/update: Remove reference to <nixpkgs>.aszlig2015-04-29
| | | | | | | We shouldn't make assumptions on what is set by NIX_PATH in order to make it easier to rename that Nix path reference. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* chromium: UpdateWilliam A. Kennington III2015-03-12
| | | | Tested that chromium, chromiumBeta, chromiumDev all build
* Re-re-revert "chromium: remove preferLocalBuild".aszlig2015-02-22
| | | | | | | | | | | | | | | | This reverts commit 0696b0ef7843bbd50592bad64efeb61634052a8e. Okay, now finally, let's get this straight. We actually *want* preferLocalBuild, *because* we have improved the source splitup in c92dbffeac75afe93c05c1ef216e927f075755c5. The idea is to use local builds in order to prevent the source being pushed to a remote machine, splitted up there (and thus copied again) and then being copied *again* FROM the remote machine. "DOH!" - as @edolstra or @rbvermaa would call it... and good d^Hnight. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* Re-revert "chromium: remove preferLocalBuild".aszlig2015-02-22
| | | | | | | | | This reverts commit 26f024626c45dcc2fd82f91f6c0dea63521d8bc4. I actually wasn't reading the "remove" in the commit message, so sorry for the brainfart/noise. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* Revert "chromium: remove preferLocalBuild"aszlig2015-02-22
| | | | | | | | | This reverts commit fdb5cf8107d6ecb5c775c2ad026551dbd11248f1. The reason I'm reverting this is that the implications this had on the IO load of Hydra are fixed by c92dbffeac75afe93c05c1ef216e927f075755c5. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* chromium: Split up the source tarball on the fly.aszlig2015-02-22
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | So far we've done the source code split up by using the generic unpackPhase and copying it all over into the different outputs. However, this had the problem of generating the I/O load of about three times the size of the source tree: First at fetchurl of the tarball (although it's not as much because it's compressed), second at unpackPhase and third at installPhase. Now we don't use installPhase anymore and directly unpack into the output paths, which unfortunately becomes quite a bit more complex because we need to transform the paths of the tar file on the fly. I've also tried using GNU Tar's --to-command option to even untar *and* patch it at the same time, but forking for every single file in the tarball gets REALLY slow and also gets even more complex than this two stage approach because you need to make sure that the patch file is applied correctly, for example for files that don't yet exist but are to be created by the patch file. We're using --anchored and --no-wildcards-match-slash here to prevent accidentally excluding files we don't want to exclude. One example is something like v8/tools/gyp/v8.gyp. So the current approach is some compromise between complexity and speed and should hopefully get rid of the Hydra build timeouts by lowering I/O load. See here for examples of builds having this issue: http://hydra.nixos.org/build/19045023 http://hydra.nixos.org/build/19044973 http://hydra.nixos.org/build/19044968 http://hydra.nixos.org/build/19045019 Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* chromium: Update all channels to latest versions.aszlig2015-02-22
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | Overview of the updated versions: stable: 40.0.2214.91 -> 40.0.2214.115 beta: 41.0.2272.16 -> 41.0.2272.64 dev: 41.0.2272.16 -> 42.0.2305.3 Introduces 42.0.2305.3 as the new dev version, which no longer requires our user namespaces sandbox patch. Thanks to everyone participating in https://crbug.com/312380 for finally having this upstream. In the course of supporting the official namespace sandbox (that's what the user namespace sandbox is called), a few things needed to be fixed for version 42: * Add an updated nix_plugin_paths.patch, because the old one tries to patch the path for libpdf, which is now natively included in Chromium. * Don't copy libpdf.so to libexec path for version 42, it's no longer needed as it's completely built-in now. * Disable SUID sandbox directly in the source instead of going the easy route of passing --disable-setuid-sandbox. The reason is that with the command line flag a nasty nagbar will appear. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* chromium: remove preferLocalBuild due to intense IO in VM testsDomen Kožar2015-02-06
| | | | | (cherry picked from commit 84bd62da0a63e18fa285bacf0e648b82d601816e) Signed-off-by: Domen Kožar <domen@dev.si>
* chromium: Update all channels to latest versions.aszlig2015-01-26
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This brings a new stable version 40.0.2214.91 along with a beta update to version 41.0.2272.16, the dev channel is still stuck at version 41.0.2272.12 and within the next days will jump to version 42. For this reason, I've done some cheating here and brought the beta channel in par with the dev channel, because dev is older than beta on OmahaProxy. Here's an overview of the channel upgrades: stable: 39.0.2171.65 -> 40.0.2214.91 [1] beta: 40.0.2214.10 -> 41.0.2272.16 [1] [2] [3] dev: 41.0.2224.3 -> 41.0.2272.16 [1] [2] [3] [1]: We needed to patch in locations of lib{pci,udev}.so, because Chromium tries to load them at runtime. For version 41 startup will fail if it is unable to load libudev, but it also has the advantage that this fixes GPU detection using libpci in the stable version, which in turn could fix a few bugs on NixOS. [2]: The upstream Debian package for the binary plugins now uses XZ compression for the enclosed data tarball. [3]: Chromium 41 needs {shapshot,natives}_blob.bin in order to start up, so let's cp it among with the .pak files to avoid adding a conditional for version 40. The release annoucement of the stable channel update can be found here: http://googlechromereleases.blogspot.de/2015/01/stable-update.html Note that this release contains 62 security fixes(!) and I'm hereby apologizing for the delay of this update. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* chromium: Fix userns patch for kernel 3.18.2.aszlig2015-01-13
| | | | | | | | | | | | | | | | | | Writing the gid_map is already non-fatal, but the actual sandbox process still tries to setresgid() to nogroup (usually 65534). This however fails, because if user namespace sandboxing is present, the namespace doesn't have CAP_SETGID at this point. Fortunately, the effective GID is already 65534, so we just need to check whether the target gid matches and only(!) setresgid() if it doesn't. So if someone would run a SUID version of the sandbox, it would still work nonetheless without a negative impact on security. Fixes #5730, thanks to @wizeman for reporting and initial debugging. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* chromium: Allow env vars for passing plugin paths.aszlig2014-11-22
| | | | | | | | | | | | | | | | | | | | | | | | | Introduces environment variables to set plugin base paths. The schema for these is like NIX_CHROMIUM_PLUGIN_PATH_<N>. Where <N> is the path type we want to change, the supported (full) variable names are: * NIX_CHROMIUM_PLUGIN_PATH_ALL * NIX_CHROMIUM_PLUGIN_PATH_PEPPERFLASH * NIX_CHROMIUM_PLUGIN_PATH_FILEFLASH * NIX_CHROMIUM_PLUGIN_PATH_PDF * NIX_CHROMIUM_PLUGIN_PATH_FILE_EFFECTS * NIX_CHROMIUM_PLUGIN_PATH_NACL * NIX_CHROMIUM_PLUGIN_PATH_PNACL * NIX_CHROMIUM_PLUGIN_PATH_WIDEVINE Whereas NIX_CHROMIUM_PLUGIN_PATH_ALL is the plugin base path for every path which is not set explicitly, so by setting ..._ALL and not setting ..._WIDEVINE, the widevine plugin will be searched in the directory specified using ..._ALL. Right now, the only plugin where this is used is widevine, and it still doesn't properly work yet. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* chromium: Update all channels to latest versions.aszlig2014-11-22
| | | | | | | | | | | | | | | | | | | | | | With this commit, the following new upstream versions are introduced: stable: 38.0.2125.101 -> 39.0.2171.65 beta: 39.0.2171.19 -> 40.0.2214.10 dev: 40.0.2182.3 -> 41.0.2224.3 We can now remove missing_alg_import.patch, because version 39 is nom stable and thus fixes the missing include directive upstream. However, starting with version 40, we hit a few bugs with system protobuf, so we're disabling it for every version >=40 to avoid runtime/startup errors. Here is the stable channel announcement for version 39 on the official blog: http://googlechromereleases.blogspot.de/2014/11/stable-channel-update_18.html Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* Revert "chromium: update dev, beta, stable channels"Domen Kožar2014-10-22
| | | | | | | This reverts commit 32df2a083842bf22cf5f47c0561c19a646c40df2. See https://github.com/NixOS/nixpkgs/commit/32df2a083842bf22cf5f47c0561c19a646c40df2#commitcomment-8260774
* chromium: update dev, beta, stable channelsDomen Kožar2014-10-22
|
* chromium: Drop conditionals for version 37.aszlig2014-10-14
| | | | | | | No longer needed, because Chromium version 37 is no longer the current stable version. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* chromiumStable 38.0.2125.101, chromiumBeta 39.0.2171.19, chromiumDev 40.0.2182.3Aristid Breitkreuz2014-10-10
|
* chromium: Update all channels to latest versions.aszlig2014-10-06
| | | | | | | | | | | | | | | | With this commit, the following new upstream versions are introduced: stable: 37.0.2062.94 -> 37.0.2062.120 beta: 38.0.2125.24 -> 38.0.2125.101 dev: 39.0.2138.3 -> 39.0.2171.7 All channels built fine on my machine and were tested against a few sites. The missing_alg_import.patch now is no longer needed for version 39, so we're not applying it there anymore. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* chromium: Update beta and dev to latest versions.aszlig2014-08-30
| | | | | | | | | beta: 37.0.2062.94 -> 38.0.2125.24 (builds fine, tested) dev: 38.0.2125.8 -> 39.0.2138.3 (builds fine, tested) Introduces the new version 39 and finally separates stable/beta again. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* Chromium patch, fixes missing headerCray Elliott2014-08-29
|
* chromium: Update all channels to latest versions.aszlig2014-08-27
| | | | | | | | | | | | | | | | | | | | | | | | | | With this commit, the following new upstream versions are introduced: stable: 36.0.1985.125 -> 37.0.2062.94 beta: 37.0.2062.58 -> 37.0.2062.94 dev: 38.0.2107.3 -> 38.0.2125.8 All channels built fine on my machine and were tested against a few sites. Stable and beta channel now contain the same release, because version 37 hit the stable channel. For release notes, please have a look at the announcement: http://googlechromereleases.blogspot.de/2014/08/stable-channel-update_26.html Of course we're also dropping all version 36 specific crap, such as the architecture-specific target suffix for builds, which now is no longer needed. The gyp flag use_mojo=0 is no longer needed, as it was a workaround concerning version 37.0.2054.3 only. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* Merge remote-tracking branch 'origin/master' into staging.Peter Simons2014-08-04
|\ | | | | | | | | Conflicts: pkgs/desktops/e18/enlightenment.nix
| * chromium: Update beta and dev to latest versions.aszlig2014-08-04
| | | | | | | | | | | | | | | | | | | | beta: 37.0.2062.44 -> 37.0.2062.58 (builds fine, tested) dev: 38.0.2101.0 -> 38.0.2107.3 (builds fine, tested) Drop patch for fixing angle build for the dev version, because it was applied upstream already. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
| * chromium: Update all channels to latest versions.aszlig2014-07-28
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | With this commit, the following new upstream versions are introduced: stable: 35.0.1916.153 -> 36.0.1985.125 beta: 36.0.1985.84 -> 37.0.2062.44 dev: 37.0.2054.3 -> 38.0.2101.0 All builds were successfully tested on my machine, however in order to update the beta and dev channels, a few additional modifications were necessary: * Don't update address_input_strings.grdp anymore because this has been done/fixed upstream and was relevant in version 37.0.2054.3 _only_. * No need to fix references to /usr/bin/gcc in version 38 anymore. * Constrain patch for Angle (introduced in 4cbedd7) to version 37 only, because it already has been applied upstream in version 38. * Drop user namespaces patch for version 31 up until version 35, because version 36 is already in stable. * Don't try to build bundled Clang and/or even build using Clang. * Remove obsolete patchPhase commands that are specific to version 35 and older. While testing the dev version 38 I came accross a font rendering issue which needs to be addressed ASAP (perhaps related to #3187), however the browser works otherwise. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
generated by cgit-pink 1.4.1 (git 2.36.1) at 2024-07-06 01:20:32 +0000