Overview of the updated versions:
stable: 49.0.2623.87 -> 49.0.2623.110
beta: 50.0.2661.26 -> 50.0.2661.49
dev: 50.0.2661.18 -> 51.0.2693.2
Most notably, this includes a series of urgent security fixes:
* CVE-2016-1646: Out-of-bounds read in V8. Credit to Wen Xu from
Tencent KeenLab.
* CVE-2016-1647: Use-after-free in Navigation. Credit to anonymous.
* CVE-2016-1648: Use-after-free in Extensions. Credit to anonymous.
* CVE-2016-1649: Buffer overflow in libANGLE. Credit to lokihardt
working with HP's Zero Day Initiative / Pwn2Own.
* CVE-2016-1650: Denial of service in PageCaptureSaveAsMHTMLFunction
The official release announcement with details about these fixes can be
found here:
http://googlechromereleases.blogspot.de/2016/03/stable-channel-update_24.html
Beta and stable could be also affected, although I didn't do a detailed
check whether that's the case.
As this introduces Chromium 51 as the dev version, I had to make the
following changes to make it build:
* libexif got removed, so let's do that on our end as well.
See https://codereview.chromium.org/1803883002 for details.
* Chromium doesn't seem to compile with our version of libpng, so let's
resort to the bundled libpng for now.
* site_engagement_ui.cc uses isnan outside of std namespace, so
we're fixing that in postPatch using sed.
I have successfully built all versions on i686-linux and x86_64-linux
and tested it using the VM tests.
Test reports can be found at the following evaluation of my Hydra:
https://headcounter.org/hydra/eval/314584
Thanks to @grahamc for reporting this.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Reported-by: Graham Christensen <graham@grahamc.com>
Fixes: #14299
We were using a version years old.
I picked the git version instead of the last release because the git version
has fixes not released for almost one year.
I updated the erlang esdl lib, added the erlang cl lib,
added opencl-headers and ocl-icd to make wings build and run.
I have not tested its opencl part; I only added dependencies so
it builds.
I originally wanted to do this a long time (a31301d) but IIRC back then
it didn't compile. Nowadays with the splitup of the gold linking flags
and the binutils integration, it's merely just a switch to flip, so
let's do that.
Only tested it by building against the current Chromium stable version
on 64bit, because right now builds on Hydra seem to time out (because of
this?) anyway so we have nothing to lose here.
The linking time was hereby reduced from >30 minutes (I didn't measure
it exactly but looked half an hour later to the build progress and it
was *still* linking) to about a few seconds, which I guess is even
though the measurement is quite bogus a tremendous improvement
nonetheless.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
The openimageio dependency doesn't build on i686. But probably nobody
cares about running Blender on 32-bit anymore.
http://hydra.nixos.org/build/33602734
Note: the 1.2.9 GitHub tarball's sha256 has changed.
Changes:
- Fixed an issue introduced by the fix for 1196 that had the "Upload
to SD" button stop working correctly.
- Fixed an issue causing an error on disconnect after or cancelling of
an SD print, caused by the unsuccessful attempt to record print
recovery data for the file on the printer's SD card.
- Only add bed temperature line to temperature management specific
start gcode in CuraEngine invocation if a bed temperature is actually
set in the slicing profile.
- If a communication timeout occurs during an active resend request,
OctoPrint will now not send an M105 with an increased line number
anymore but repeat the last resent command instead.
- Don't add an extra ok for M28 response.
- Add an extra ok for M29 response, but only if configured such in
"Settings" > "Serial" > "Advanced options" > "Generate additional ok
for M29"
- Trigger M20 only once after finishing uploading to SD
- Prevent M105 "cascade" due to communication timeouts
- Fixed wrong tracking of extruder heating up for M109 Tn commands in
multi-extruder setups.
- Fixed start of SD file uploads not sending an M110.
- Fixed job data not being reset when disconnecting while printing.
