Alberto Garcia [Fri, 10 Jul 2020 11:26:49 +0000 (12:26 +0100)]
Use WTF_CPU_UNKNOWN when building for X32
Forwarded: no
WebKitGTK doesn't build on X32 even with the JIT disabled.
Treating the CPU as unknown is perhaps a bit severe, but it allows us
to get the build done until someone steps up to maintain this
properly.
===================================================================
When building for x86 in a x86_64 host (e.g. with pbuilder) CMake
will set CMAKE_SYSTEM_PROCESSOR to x86_64, and WebKit will assume
that it's a 64-bit build. Let's use the C++ compiler architecture as
a temporary solution to detect x86 correctly.
===================================================================
Alberto Garcia [Fri, 10 Jul 2020 11:26:49 +0000 (12:26 +0100)]
webkit2gtk (2.28.3-2) unstable; urgency=high
* The WebKitGTK security advisory WSA-2020-0006 lists the following
security fixes in the latest versions of WebKitGTK:
+ CVE-2020-9802, CVE-2020-9803, CVE-2020-9805, CVE-2020-9806,
CVE-2020-9807, CVE-2020-9843, CVE-2020-9850, CVE-2020-13753 (fixed
in 2.28.3).
* Don't build the documentation in binary-arch builds and with the nodoc
build profile (Closes: #962616).
+ debian/control:
- Move gtk-doc-tools and *-doc to Build-Depends-Indep.
- Add Build-Profiles: <!nodoc> to libwebkit2gtk-4.0-doc
+ debian/rules:
- Use dh_listpackages to decide whether to build the documentation.