From: forest.eckhardt@docker.com   
      
   Source: chromium   
   Version: 145.0.7632.75-1~deb13u1   
   Severity: important   
   X-Debbugs-Cc: forest.eckhardt@docker.com,dilinger@debian.org,sec   
   rity@debian.org   
      
   Dear Maintainer,   
      
      * What led up to the situation?   
      	I was attempting to update chromium on an ARM and AMD images   
      * What exactly did you do (or not do) that was effective (or   
        ineffective)?   
        	I did not receive the same latest patched version of chromium on   
   	both images. I only received it on AMD.   
      * What was the outcome of this action?   
      	My ARM image was left vulnerable.   
      * What outcome did you expect instead?   
      	Both images to receive the same patch version of chromium   
      
   I noticed that there appeared to be some build error that has since been   
   patched   
   https://salsa.debian.org/chromium-team/chromium/-/commit/5a07797   
   b1fe019bcfee5069b8d6a9ae53a5a9c3   
   I was curious if the upload for ARM is pending or what the status of   
   getting an ARM version is? Thank you!   
      
      
   -- System Information:   
   Debian Release: 13.3   
     APT prefers stable-updates   
     APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500,   
   'stable')   
   Architecture: arm64 (aarch64)   
      
   Kernel: Linux 6.12.67-linuxkit (SMP w/14 CPU threads)   
   Kernel taint flags: TAINT_OOT_MODULE   
   Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set   
   Shell: /bin/sh linked to /usr/bin/dash   
   Init: unable to detect   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)