From: smcv@debian.org 
  
 On Tue, 12 Aug 2025 at 16:51:54 +0200, Guillem Jover wrote: 
 >dpkg will automatically turn a remove into a purge if the package 
 >has no conffile and no postrm: 
 > 
 >  https://git.dpkg.org/cgit/dpkg/dpkg.git/tree/src/main/remove.c#n639 
  
 Thanks, I wondered whether something like that might have happened. 
 libglib2.0-0 doesn't have any conffiles, so the postrm is indeed the only 
 reason to distinguish between remove and purge. 
  
 If the package "officially" has a postrm, but we went behind dpkg's back 
 and deleted it from the filesystem to avoid it doing damage (which is 
 what's happening here unfortunately), does that count as "no postrm" 
 from dpkg's point of view? 
  
 And is it plausible that dpkg only notices that situation has happened 
 in libglib2.0-0:amd64 as a side-effect of starting work on purging 
 libglib2.0-0:i386? 
  
 >But from the attached log files in the bug report, I see there was an 
 >explicit purge request for libglib2.0-0:i386. 
  
 I think that might have been explicitly done by the user in this case, 
 yes, but perhaps only for the i386 flavour. 
  
      smcv 
  
 --- SoupGate-Win32 v1.05 
  * Origin: you cannot sedate... all the things you hate (1:229/2)