--- ../glib2.0_trixie/debian/libglib2.0-0t64.postrm	2025-08-17 14:57:54.492848319 +0100
+++ ../glib2.0_bookworm/debian/libglib2.0-0.postrm.in	2025-08-17 22:16:40.609558126 +0100
@@ -8,7 +8,7 @@
 
 clean_up_giomodule_cache ()
 {
-    local multiarch="#DEB_HOST_MULTIARCH#"
+    local multiarch="#MULTIARCH#"
     local modules="/usr/lib/${multiarch}/gio/modules"
     local iter
 
@@ -16,10 +16,10 @@
         return 0
     fi
 
-    # Don't remove giomodule.cache if libglib2.0-0t64 has been replaced
+    # Don't remove giomodule.cache if libglib2.0-0 is replaced
     # by some other ABI variant of essentially the same library
-    # (for example libglib2.0-0xyz), if that ever happens, to
-    # avoid causing an equivalent of <https://bugs.debian.org/1065022>.
+    # (for example libglib2.0-0t64 in trixie), to avoid causing
+    # <https://bugs.debian.org/1065022>.
     #
     # This implementation is based on the assumption that any GLib
     # version that still uses ${libdir}/gio/modules/giomodule.cache
@@ -52,8 +52,7 @@
 
     # Similarly, instead of using $DPKG_MAINTSCRIPT_PACKAGE_REFCOUNT, only
     # remove gschemas.compiled if GLib has completely gone away - not just
-    # libglib2.0-0 and libglib2.0-0t64, but any possible future ABI variant
-    # like libglib2.0-0xyz.
+    # libglib2.0-0, but any future ABI variant like libglib2.0-0t64.
     #
     # This implementation is based on the assumption that any GLib
     # version that still uses ${datadir}/glib-2.0/schemas