On Sat, 01 May 2021 at 23:54:16 +0200, Andreas Beckmann wrote: > during a test with piuparts I noticed your package misses two > directories after an upgrade. These directories are shipped by the > package.
I agree this is a bug, but I'm not sure what its severity is. Are you aware of a user-visible impact to this bug, or is it (as far as you know) only a theoretical issue? >From the gio/giomodule.c source code, it looks as though a missing GIO modules directory should be exactly equivalent to a GIO modules directory that contains (no cache and) no modules. The only reason I can see for this to be a practical problem is if it prevented dpkg from triggering libglib2.0-0 after we install a package that contains at least one GIO module. Also, the cache is just a cache (unlike /usr/share/glib-2.0/schemas/gschemas.compiled, which is functionally necessary), and GIO should still successfully load GIO modules even if the cache was not regenerated - it will just be significantly higher-overhead. If there's little or no practical impact then I'm inclined to postpone fixing this until after bullseye. Thanks, smcv