Merge version 8.9.0-2+rpi1 and 8.9.0-3 to produce 8.9.0-3+rpi1

diff --cc debian/changelog
index a991b973f2496b2fd46cc073b67ca3db693a2c3d,b41f78ff80188069f39a67db263da0a54663e495..d2ec8a184fb3da85bdb2e81f8e67bfceb0087cce
--- 1/debian/changelog
--- 2/debian/changelog
+++ b/debian/changelog
@@@ -1,14 -1,10 +1,22 @@@
- libcrypto++ (8.9.0-2+rpi1) trixie-staging; urgency=medium
++libcrypto++ (8.9.0-3+rpi1) forky-staging; urgency=medium
 +
 +  [changes brought forward from 8.6.0-3+rpi1 by Peter Michael Green <plugwash@raspbian.org> at Sat, 19 Mar 2022 22:09:41 +0000]
 +  * Upload to raspbian despite detection of armv7 contaimination,
 +    investigation of the code shows that the armv7/neon code seems
 +    to be safely behind runtime CPU testection.
 +  * Pass -march=armv7+fp instead of -march=armv7 when building "armv4"
 +    assembler files. Despite the names these files only seem to be used
 +    on armv7.
 +
-  -- Raspbian forward porter <root@raspbian.org>  Sun, 11 May 2025 02:57:31 +0000
++ -- Raspbian forward porter <root@raspbian.org>  Fri, 24 Jul 2026 02:45:20 +0000
++
+ libcrypto++ (8.9.0-3) unstable; urgency=medium
+ 
+   * Backport upstream fix for ChaCha SIMD feed-forward carry.
+   * Remove now redundant Rules-Requires-Root value.
+   * Update Standards-Version to 4.7.2 .
+ 
+  -- Laszlo Boszormenyi (GCS) <gcs@debian.org>  Tue, 14 Jul 2026 18:40:33 +0200
  
  libcrypto++ (8.9.0-2) unstable; urgency=high
  

diff --cc debian/patches/series
index beed83c9372f8821d3bcf8f85d310c428b1ab926,d7a9ff1dc70e92a280fbb575d517374f4f1b3124..5e23de05413b5806a91b25a95a4b7589a67f5aa2
--- 1/debian/patches/series
--- 2/debian/patches/series
+++ b/debian/patches/series
@@@ -1,4 -1,4 +1,5 @@@
  fix_library_name.patch
  update_gf2n_docs.patch
  CVE-2023-50980.patch
+ fix_ChaCha_SIMD_feed-forward_carry.patch
 +use-fp-with-march.patch