Your message dated Sun, 02 May 2021 18:03:34 +0000
with message-id <[email protected]>
and subject line Bug#987913: fixed in glib2.0 2.68.1-2
has caused the Debian Bug report #987913,
regarding libglib2.0-0: upgrade or reinstallation removes
/usr/lib/<triplet>/gio/modules/ if empty
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
987913: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987913
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libglib2.0-0
Version:
Severity: serious
User: [email protected]
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package misses two
directories after an upgrade. These directories are shipped by the
package.
Any easy way to reproduce this is in a minimal chroot with only
libglib2.0-0 but no gio modules installed:
apt-get install --reinstall libglib2.0-0
Piupart reports:
0m27.9s DEBUG: Starting command: ['chroot', '/srv/piuparts/tmp/tmpujqyat',
'tmp/scripts/pre_remove_40_find_missing_md5sums']
0m27.9s DUMP:
libglib2.0-0: MISSING OBJECT /usr/lib/x86_64-linux-gnu/gio
libglib2.0-0: MISSING OBJECT /usr/lib/x86_64-linux-gnu/gio/modules
0m27.9s DEBUG: Command ok: ['chroot', '/srv/piuparts/tmp/tmpujqyat',
'tmp/scripts/pre_remove_40_find_missing_md5sums']
This is caused by the postrm script which unconditionally deletes
giomodule.cache and the path to it. During upgrade (or
reinstallation), dpkg will call
old-postrm upgrade new-version
after the new package has been unpacked.
The two actions cleaning up (the path to) giomodule.cache
in postrm should probably be limited to 'remove' and 'purge'.
To properly recreate the missing directories after having
upgraded to a buggy version in the past, you need to mkdir -p
them in postinst. (The directories get deleted (again) by the
old postrm *after* the new package has been unpacked.)
Andreas
--- End Message ---
--- Begin Message ---
Source: glib2.0
Source-Version: 2.68.1-2
Done: Simon McVittie <[email protected]>
We believe that the bug you reported is fixed in the latest version of
glib2.0, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Simon McVittie <[email protected]> (supplier of updated glib2.0 package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Sun, 02 May 2021 14:45:36 +0100
Source: glib2.0
Architecture: source
Version: 2.68.1-2
Distribution: experimental
Urgency: medium
Maintainer: Debian GNOME Maintainers
<[email protected]>
Changed-By: Simon McVittie <[email protected]>
Closes: 987913
Changes:
glib2.0 (2.68.1-2) experimental; urgency=medium
.
* Fix maintainer scripts' handling of /usr/lib/MULTIARCH/gio/modules:
- postrm: Only delete GIO module cache on remove or purge.
Despite its name, the postrm can be invoked for reasons other than
package removal: in particular, the old version's postrm is run
during upgrades.
- postinst: Recreate GIO module directory if deleted by an older
postrm, to recover from the bug fixed here.
- postinst: Don't guard glib-compile-schemas or gio-querymodules with
a check for existence of a directory that is shipped in the .deb.
If such a directory has somehow gone missing, we want to see
a warning. This won't make the postinst fail, because we're ignoring
exit status anyway.
(Closes: #987913)
Checksums-Sha1:
ac899cd7f26655c09a3ba3f7644ba0ebb79060a6 3506 glib2.0_2.68.1-2.dsc
90b469ec6902ddf9297e31e8ef9f1e8746931924 99044 glib2.0_2.68.1-2.debian.tar.xz
7982e5261fd6339c0900924600a37b37c8605f2a 6945 glib2.0_2.68.1-2_source.buildinfo
Checksums-Sha256:
74872d04d28b087efd302f5b40f47bb8da2a43bafe9ca63f6eff322c09e4f489 3506
glib2.0_2.68.1-2.dsc
6da285543e08de55ff0c289f48b94e215686b4cb4ec20504dc545a8dc31c0372 99044
glib2.0_2.68.1-2.debian.tar.xz
7be2a74cf7f0e4ecd3928999122ad558ee98a9d5c3f1037f92fae7a4c9891d4e 6945
glib2.0_2.68.1-2_source.buildinfo
Files:
77ce178c5bd59d3d83b9af24fdb7b901 3506 libs optional glib2.0_2.68.1-2.dsc
65a30027989e51d33f953a0bc816ee6d 99044 libs optional
glib2.0_2.68.1-2.debian.tar.xz
812d5eace592a5edb97383a48e053150 6945 libs optional
glib2.0_2.68.1-2_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEENuxaZEik9e95vv6Y4FrhR4+BTE8FAmCO5WIACgkQ4FrhR4+B
TE/rUw/9FHD/XxZNDWyjTS4thKdlGsJ+bBur3N1Fifgk8j8RxaoJ1hoXnjIJhUwV
q9Vk1FyFuKT/Lizg69JXdO0CQ7UwWA4/So3y36PWyiJ3ZyGa98p3hRta6RZ91efG
1WtlilNu5xfqpFtxDPTmPKTbSqgzoB4+aC+0guszdRxiVIpyQF/Fpgy4DNw+6mqy
WoGN1zXkWawlTU+Mzlb9tkcaOnsYnzX5oW8GSjBqbj1K/T7cUvXllS8ozz2wQF6p
npVyhyOr6dhJaQ4vYC9Dyg2oUXMXv3H57Pwedwa5dAa1C0YmHjT7uRVSDWE8hsqd
PnQZaWrzykSnjIjRlIp2NnJrvCFuyx3m34PPke40UQyKLxRX6SqbnacuhocxxoWT
looFG7oPYQbLs9iVgwctAwVBGxIE4ajqVWGCvyFJPzhVbxsmcKD14wyWxDLNYQQO
E96KFixNmvzu5PJEcO0EQ5vpuIzrEhd9fITlA+nc1IMjeUylCy2Tdm1F8MH4CnhI
ahrXlDR0PXgw5cI0hOFG6c1gn2oT6HNucaf+8GKGISWlEqiClpW1NPjjrvyl6kky
/Zkc+TMDo8WU6zWiUl+5Odfo93OJ/KNnh6h7k7l3rH+8F2DLKxhYtG5zioB3JPBW
FRyoteWprkmqR4i+9p7GOfyv1pupJokNMNGW2SOSiv9HNkKO0lo=
=I6Bv
-----END PGP SIGNATURE-----
--- End Message ---
