Alberto Garcia [Thu, 7 Jan 2021 13:23:52 +0000 (13:23 +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, 7 Jan 2021 13:23:52 +0000 (13:23 +0000)]
webkit2gtk (2.30.5-1) unstable; urgency=high
* New upstream release (Closes: #978042).
* Remove some obsolete build dependencies (Closes: #979170):
+ gawk is not needed since WebKitGTK switched from autotools to CMake.
+ libgeoclue-2-dev and geoclue-2.0 are not required since WebKitGTK
2.25.1 (upstream bug 195994).
+ libupower-glib-dev is not required since WebKitGTK 2.19.92 (upstream
bug 181825).
+ libfile-copy-recursive-perl is not required since WebKitGTK 2.19.3
(upstream bug 180479).
+ mesa-common-dev used to provide GL/gl.h but this header is now in
libgl-dev.
+ libgles2-mesa-dev used to provide GLES3/gl3.h but this header is now
in libgles-dev.
+ libgl1-mesa-dev and libgles2-mesa-dev are now dummy packages.
+ libpango1.0-dev is not checked for any specific version at build
time so there's no need to list it.
* Update the minimum required versions of some packages:
+ cmake from 3.3 to 3.10
+ libglib2.0-dev from 2.36.0 to 2.44.0
+ libgtk-3-dev from 3.10.0 to 3.22.0
+ libcairo2-dev from 1.10.2 to 1.14.0
+ libsoup2.4-dev from 2.42.0 to 2.54.0.
* debian/patches/fix-mips-page-size.patch:
+ Increase the page size from 4KB to 16KB on MIPS, this fixes a crash
with Loongson CPUs that don't support 4KB pages (Closes: #977779).
* debian/copyright:
+ Update copyright years.
* debian/watch:
+ Set version to 4 (fixes older-debian-watch-file-standard).
* debian/control:
+ Update Standards-Version to 4.5.1 (no changes).
Alberto Garcia [Tue, 15 Dec 2020 14:23:01 +0000 (14:23 +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 [Tue, 15 Dec 2020 14:23:01 +0000 (14:23 +0000)]
webkit2gtk (2.30.4-1) unstable; urgency=high
* New upstream release.
* The WebKitGTK security advisory WSA-2020-0008 lists the following
security fixes in the latest versions of WebKitGTK:
+ CVE-2020-9952 (fixed in 2.28.3).
+ CVE-2020-9948, CVE-2020-9951 (fixed in 2.30.0).
+ CVE-2020-9983, CVE-2020-13584 (fixed in 2.30.3).
Alberto Garcia [Fri, 20 Nov 2020 14:24:07 +0000 (14:24 +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, 23 Oct 2020 10:18:03 +0000 (11:18 +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 [Mon, 21 Sep 2020 13:34:07 +0000 (14:34 +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 [Tue, 28 Jul 2020 15:12:20 +0000 (16:12 +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 [Tue, 28 Jul 2020 15:12:20 +0000 (16:12 +0100)]
webkit2gtk (2.28.4-1) unstable; urgency=high
* New upstream release.
* Enable OpenGL ES in arm:
+ debian/patches/use-gles-on-arm.patch:
- Set ENABLE_GLES2_DEFAULT to ON on arm.
+ debian/control:
- Always depend on libgl1-mesa-dev.
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.
projects / webkit2gtk.git / log