Add support for a new-compression idiom that does not compress all the
matching data in a transfer. This can help rsync to use less cpu when a
transfer has a lot of matching data,
Switch to bundled zlib in order to support both old and new compression.
ok sthen@, espie@
starting with "installer". Since I don't think this is possible with the
implementation for apache-httpd-openbsd just comment out the rule for now,
kirby@ agrees.
belongs.
BTW: there seems to be a snapshot newer than stable available again
(2.45.28), so if anyone is interested in reviving the snapshot
version, just give it a try.
Plasma developers choosed to have 4.11.x releases. Yes, you'll have, say,
kde-workspace-4.10.10 among KDE 4.13 packages.
No-op for now, will matter in the near future.
Over 20 bugs were fixed in this release, including the following CVEs:
CVE-2014-3981, CVE-2014-0207, CVE-2014-3478, CVE-2014-3479, CVE-2014-3480,
CVE-2014-3487, CVE-2014-4049, CVE-2014-3515.
'Fixed a potential integer overflow condition in the "safe" decompressor
variants which could result in a possible buffer overrun when processing
maliciously crafted compressed input data.
As this issue only affects 32-bit systems and also can only happen if
you use uncommonly huge buffer sizes where you have to decompress more
than 16 MiB (2^24 bytes) compressed bytes within a single function call,
the practical implications are limited.'
See http://www.openwall.com/lists/oss-security/2014/06/26/20 for more
details, there are also some embedded copies of "minilzo" from the same
source in various other programs which are also affected by this
this as -j$(J) to child processes, so if undefined this results in "gmake -j".
As gmake(1) says, "If the -j option is given without an argument, gmake
will not limit the number of jobs that can run simultaneously."
Hopefully this fixes a weird build failure that naddy saw and I was able
to replicate after a bunch of build attempts.
in 30.0, see https://bugzilla.mozilla.org/show_bug.cgi?id=1028827.
Remove some "if build machine has SSE2/SSSE3 then don't bother with cpuid
feature checks at runtime" pieces.
ok jasper@ (landry is away for a few days).
