sync vm-memory 0.12.2

from Debian unstable

Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>

diff --git a/src/vm-memory/debian/changelog b/src/vm-memory/debian/changelog
index 2038330e4cb590abba98f7c1b405f052546a69dc..599147d722fd9d8347a6102cf45f99a5bb53b3a8 100644 (file)
--- a/src/vm-memory/debian/changelog
+++ b/src/vm-memory/debian/changelog
@@ -1,3 +1,11 @@
+rust-vm-memory (0.12.2-1) unstable; urgency=medium
+
+  * Team upload.
+  * Package vm-memory 0.12.2 from crates.io using debcargo 2.6.0
+  * CVE-2023-41051, Closes: #1051101
+
+ -- Blair Noctis <n@sail.ng>  Tue, 05 Sep 2023 20:20:09 +0300
+
 rust-vm-memory (0.12.0-2~bpo12+pve1) proxmox-rust; urgency=medium
 
   * Rebuild for Debian Bookworm / Proxmox
@@ -44,8 +52,8 @@ rust-vm-memory (0.10.0-2) unstable; urgency=medium
 
   * Team upload.
   * Package vm-memory 0.10.0 from crates.io using debcargo 2.6.0
-  * Fix tests/establish baseline. 
-    + Use let val = 1usize; instead of let val = 1u64; in test_bytes to 
+  * Fix tests/establish baseline.
+    + Use let val = 1usize; instead of let val = 1u64; in test_bytes to
       fix build failure on 32-bit.
     + Use a smaller value of REGION_SIZE in benches/mmap/mod.rs on 32-bit to
       avoid out of memory errors.