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.
Alberto Garcia [Mon, 27 Apr 2020 12:55:16 +0000 (13:55 +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 [Sun, 19 Apr 2020 23:50:19 +0000 (00:50 +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 [Sun, 19 Apr 2020 23:50:19 +0000 (00:50 +0100)]
webkit2gtk (2.28.1-2) unstable; urgency=high
* The WebKitGTK security advisory WSA-2020-0004 lists the following
security fixes in the latest versions of WebKitGTK:
+ CVE-2020-11793 (fixed in 2.28.1).
* fix-ftbfs-mips64el.patch:
+ Fix a FTBFS in mipsel64.
Alberto Garcia [Thu, 12 Mar 2020 19:35:21 +0000 (19:35 +0000)]
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 [Thu, 12 Mar 2020 19:35:21 +0000 (19:35 +0000)]
webkit2gtk (2.28.0-2) unstable; urgency=high
* The WebKitGTK security advisory WSA-2020-0003 lists the following
security fixes in the latest versions of WebKitGTK:
+ CVE-2020-10018 (fixed in 2.28.0).
* debian/rules:
+ Disable the WPE renderer on Ubuntu since the required backend is in
universe (thanks, Sebastien Bacher).
* debian/gbp.conf:
+ Update upstream branch name.
Since WebKitGTK 2.26 the single-process mode is considered a security
risk and the process limiting APIs have been completely disabled.
This change is transparent for most applications, but Geary and
particularly Evolution (see upstream bug #587) are known to have
problems in multi-process mode. This has already been fixed in Geary
3.33.91 and in Evolution 3.34.1.
Although the API to set the single-process model is no longer
available, it is still possible to do it internally. This patch does
that for Evolution and Geary.
This is a temporary workaround and it is especially meant for stable
distributions and security updates, where patching or updating the
affected apps is not an option.
===================================================================
Alberto Garcia [Mon, 17 Feb 2020 10:02:17 +0000 (10:02 +0000)]
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.
===================================================================
* Rebuild for buster-backports.
* debian/patches/force-single-process.patch:
+ Force the single-process mode in Evolution and Geary
* debian/control:
+ Remove Breaks for Evolution < 3.34.1.
+ Remove build dependency on libwpebackend-fdo-1.0-dev.
+ Switch build dependency from libenchant-2-dev to libenchant-dev.
Alberto Garcia [Fri, 14 Feb 2020 13:55:40 +0000 (13:55 +0000)]
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, 14 Feb 2020 13:55:40 +0000 (13:55 +0000)]
webkit2gtk (2.26.4-1) unstable; urgency=high
* New upstream release.
* The WebKitGTK security advisory WSA-2020-0001 lists the following
security fixes in the latest versions of WebKitGTK:
+ CVE-2019-8835, CVE-2019-8844, CVE-2019-8846 (fixed in 2.26.3)
* The WebKitGTK security advisory WSA-2020-0002 lists the following
security fixes in the latest versions of WebKitGTK:
+ CVE-2020-3862, CVE-2020-3864, CVE-2020-3865, CVE-2020-3867,
CVE-2020-3868 (fixed in 2.26.4)
* debian/rules:
+ Don't use the Gold linker on powerpc (Closes: #949618).
+ Run dh with --builddirectory=build. Some source files are generated
inside this directory and are later referenced from the .gir files
so their path names should be independent from the architecture.
* debian/control:
+ Mark libwebkit2gtk-4.0-doc and libwebkit2gtk-4.0-37-gtk2 as
Multi-Arch: foreign.
+ Update Standards-Version to 4.5.0 (no changes).
* debian/patches/reduce-memory-overheads.patch:
+ Reduce memory usage when not using the Gold linker
(Closes: #949621).
* debian/patches/fix-ftbfs-m68k.patch:
+ Update to make it work with the current release (Closes: #949660).
* debian/patches/detect-woff.patch:
+ Refresh.
* Add debian/upstream/metadata.
Since WebKitGTK 2.26 the single-process mode is considered a security
risk and the process limiting APIs have been completely disabled.
This change is transparent for most applications, but Geary and
particularly Evolution (see upstream bug #587) are known to have
problems in multi-process mode. This has already been fixed in Geary
3.33.91 and in Evolution 3.34.1.
Although the API to set the single-process model is no longer
available, it is still possible to do it internally. This patch does
that for Evolution and Geary.
This is a temporary workaround and it is especially meant for stable
distributions and security updates, where patching or updating the
affected apps is not an option.
===================================================================
projects / webkit2gtk.git / log