Merge version 2.38.2-1~deb11u1+rpi1 and 2.38.3-1~deb11u1 to produce 2.38.3-1~deb11u1...

diff --cc debian/changelog
index e3bef28b0dd8cf8942bb26f052566ed4f8de0f40,b48e5b8aed9f47eeeeb038ec8bbe254c162379d8..a50e651d9b5c2349f42420c951f86543f66f5deb
--- 1/debian/changelog
--- 2/debian/changelog
+++ b/debian/changelog
@@@ -1,14 -1,12 +1,20 @@@
- webkit2gtk (2.38.2-1~deb11u1+rpi1) bullseye-staging; urgency=medium
++webkit2gtk (2.38.3-1~deb11u1+rpi1) bullseye-staging; urgency=medium
 +
 +  [changes brought forward from 2.6.2+dfsg1-3+rpi1 by Peter Michael Green <plugwash@raspbian.org> at Sun, 25 Jan 2015 02:14:50 +0000]
 +  * Disable javascript JIT as it doesn't appear to be armv6 compatible
 +    (at least I assume that is the cause of the assembler errors)
 +
-  -- Raspbian forward porter <root@raspbian.org>  Tue, 08 Nov 2022 23:12:50 +0000
++ -- Raspbian forward porter <root@raspbian.org>  Sat, 31 Dec 2022 23:24:26 +0000
 +
- webkit2gtk (2.38.2-1~deb11u1) bullseye-security; urgency=medium
+ webkit2gtk (2.38.3-1~deb11u1) bullseye-security; urgency=medium
  
    * Rebuild for bullseye-security.
+   * The WebKitGTK security advisory WSA-2022-0011 lists the following
+     security fixes in the latest versions of WebKitGTK:
+     - CVE-2022-42863 (fixed in 2.38.0).
+     - CVE-2022-46691 (fixed in 2.38.1).
+     - CVE-2022-42852, CVE-2022-42856, CVE-2022-42867, CVE-2022-46692,
+       CVE-2022-46698, CVE-2022-46699, CVE-2022-46700 (fixed in 2.38.3).
    * gcc 10 segfaults when building webkit in amd64 (see #1008098) so use
      clang instead. Keep using gcc in other architectures because clang has
      problems in at least i386, arm64 and mipsel (see #1010329 and