Your message dated Sat, 21 Sep 2024 16:15:58 +0000
with message-id <[email protected]>
and subject line Bug#987802: fixed in glib2.0 2.82.1-1
has caused the Debian Bug report #987802,
regarding libglib2.0-dev: /usr/share/glib-2.0/gdb/*.pyc not removed if created
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.)
--
987802: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987802
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libglib2.0-dev
Version: 2.66.8-1
Severity: normal
Hi.
Upon puring there were some leftovers:
Removing libglib2.0-dev:amd64 (2.66.8-1) ...
dpkg: warning: while removing libglib2.0-dev:amd64, directory
'/usr/share/glib-2.0/gdb' not empty so not removed
l /usr/share/glib-2.0/gdb/
total 25k
drwxr-xr-x 1 root root 38 Apr 30 00:44 .
drwxr-xr-x 1 root root 76 Apr 30 00:44 ..
-rw-r--r-- 1 root root 9,8k May 31 2015 glib.pyc
-rw-r--r-- 1 root root 11k May 31 2015 gobject.pyc
Cheers,
Chris.
--- End Message ---
--- Begin Message ---
Source: glib2.0
Source-Version: 2.82.1-1
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: Sat, 21 Sep 2024 14:10:44 +0100
Source: glib2.0
Architecture: source
Version: 2.82.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers
<[email protected]>
Changed-By: Simon McVittie <[email protected]>
Closes: 987802 1070773 1071246 1078929
Changes:
glib2.0 (2.82.1-1) unstable; urgency=medium
.
* New upstream stable release
* d/copyright: Update
* Move gdb integration hooks (/usr/share/gdb) back to libglib2.0-dev.
This is not essential functionality of libgio-2.0-dev, and having
it in the larger package gives us more flexibility about which of
the dependency packages contain supporting Python libraries.
* Move supporting code for gdb integration hooks into libgio-2.0-dev-bin.
This lets us byte-compile the Python modules with the primary
architecture's Python interpreter, and ensures that the Python
packaging infrastructure will automatically clean up their associated
bytecode files on uninstallation. (Closes: #987802)
* d/libgio-2.0-dev.install: Be more specific about what is installed.
If files with a different purpose are added to one of these
directories, we will not necessarily want to install them in the
same binary package.
* Replace temporary substvar ${local:SplitGiRepositoryVersion} with a
hard-coded version
* d/control, d/tests/control, d/*.install: Normalize formatting
(wrap-and-sort -ast)
* Release to unstable, now that NEW processing has been done and
architecture-properties is ready to migrate
.
glib2.0 (2.82.0-2) experimental; urgency=medium
.
* Improve ability to bootstrap new architectures.
The versions of libglib2.0-dev and -dev-bin in Debian testing/unstable
and Ubuntu 24.04 depend on either python3 from the host architecture
or qemu-user from the build architecture (for the wrapped gi-*
tools), which is problematic for bootstrapping.
Separate out the rest, so that packages that participate in
bootstrapping can be compiled with only libgio-2.0-dev{,-bin},
possibly using the nogir build-profile to disable a dependency on
girepository-tools.
This converts libglib2.0-dev into a pure metapackage, with no
functionally significant content of its own, except for the gi-*
symlinks to the primary architecture's GObject-Introspection-related
tools.
libglib2.0-dev continues to be appropriate to use as a
build-dependency in most cases. For low-level packages that are
involved in architecture bootstrapping, consider depending directly
on libgio-2.0-dev{,-bin} instead, and guarding any dependencies on
girepository-tools with a suitable build-profile such as <!nogir>.
(Closes: #1078929)
- Move the headers and libraries from libglib2.0-dev to a new
libgio-2.0-dev package
- Also move Autoconf macros and gettext rules to libgio-2.0-dev
- Move libglib2.0-dev-bin, except gi-*, to libgio-2.0-dev-bin
- Move ${multiarch}-gi-* tools to girepository-tools
* d/tests: Assert that each -dev package that was split out from
libglib2.0-dev provides its intended interface:
- libgio-2.0-dev: ability to include headers and link to shared and
static libraries
- libgio-2.0-dev-bin: GLib, GObject and GIO development CLI tools
- girepository-tools: ${multiarch}-gi-* tools
- libglib2.0-dev: all of the above plus the non-multiarch gi-*
* d/control, d/rules: Drop the local:DEB-HOST-ARCH-OS substvar.
This isn't actually needed any more: girepository-tools is independent
of the non-architecture-prefixed symlinks, because the actual
executables are installed into the ${libdir}.
* d/rules: Don't require host and build endianness to match.
This was necessary with the approach we used before fixing #1066904,
but not any more.
* d/rules: Set gir_dir_prefix even if we are building with nogir.
It affects the contents of the gi-* tools.
* d/control, d/rules, d/emulated-g-ir-tool.in:
Use the new cross-exe-wrapper from src:architecture-properties to run
foreign-architecture executables, instead of using qemu directly.
This centralizes knowledge of how to run binaries of any given
architecture into the architecture-properties source package. It also
has the right special cases to avoid needing to install qemu in common
situations, for example when running i386 binaries on amd64.
(Closes: #1070773, #1071246)
* d/emulated-g-ir-tool.in: Simplify and rewrite from Python into shell
* d/source/lintian-overrides: Remove obsolete overrides for nogir
* d/copyright: Update
* Upload to experimental for NEW processing
Checksums-Sha1:
d79433592662c1c74c1fce9728af9823afe83f8e 4895 glib2.0_2.82.1-1.dsc
5243c0e79a4a194915db726c27271d27b0cc3200 262908
glib2.0_2.82.1.orig-unicode-data.tar.xz
bd14e6968e0b33ff03b353342cc510bde28699ff 5554132 glib2.0_2.82.1.orig.tar.xz
c5e068b369eb473f193fe014e86dae8b6304496d 133856 glib2.0_2.82.1-1.debian.tar.xz
2ef38752cf45a7225e271e24a434c99259e9881a 7612 glib2.0_2.82.1-1_source.buildinfo
Checksums-Sha256:
3ec4fc5f8cf0d84298c457337ae48f959a572544d1405df56af3944ec6923cb8 4895
glib2.0_2.82.1-1.dsc
9bf66a7e9f2f18cbd7a72f561dc1f997990b53243435008777109c823cd7e1ea 262908
glib2.0_2.82.1.orig-unicode-data.tar.xz
478634440bf52ee4ec4428d558787398c0be6b043c521beb308334b3db4489a6 5554132
glib2.0_2.82.1.orig.tar.xz
eec8688cd7d7f1a434cb84f3a88b5136131b1bf4bf7fcf4f3e8d767c1917f35e 133856
glib2.0_2.82.1-1.debian.tar.xz
0fd70357d830fae129ed95096a3b26a6abc68666d62a8569c3c1ea89a77f5b50 7612
glib2.0_2.82.1-1_source.buildinfo
Files:
cc749f2ce0736b14c44f48d08d717f41 4895 libs optional glib2.0_2.82.1-1.dsc
6ad3c10daf51ca9e9810841d267e7451 262908 libs optional
glib2.0_2.82.1.orig-unicode-data.tar.xz
d101f1acab6805d4d6d3104e9634b8e3 5554132 libs optional
glib2.0_2.82.1.orig.tar.xz
e1eb3baa99cbbd0a876e7f0ceb82e14c 133856 libs optional
glib2.0_2.82.1-1.debian.tar.xz
cd637f9f7ac642cefa7daac60005c039 7612 libs optional
glib2.0_2.82.1-1_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEENuxaZEik9e95vv6Y4FrhR4+BTE8FAmbu7/UACgkQ4FrhR4+B
TE/d8xAAgR/TWgp7NysmhcP37zepLIrGGGbqfGtP8eRjDh8+5FcGJ+68QIB4Vn2y
6wTV/qvlsyQh4iH1Phf3a9zvWt2C3PH2m4iTIbkkxDpK9MpChQCuE5xZspDCA4KG
+18NqvEGq2ghRlEvZpNQtKcjO1InIlt+GuQRW6FN0tOHb7V5J7gwzXwB68h3OMYw
eufsy0ZNxysrI/ZwA6ZR8CPWYqj8h+cHu+V/dJQ9+GqBK33ZlfjuytNUy47lsvpv
L4in+IWzJ40CJjo/kkr6mQLf+OkYMyPEUwkMNxJFUXrQnB95+r1bMhaLz/L/EQvw
/6/rrLNjiWBZJynT/DofsgEfbzS1tS+K6/KzYTX5GuUOuBEVlDjNA41rf+YbG9Ww
KVB9LSu93x5eiRIyfC3SO0I+5SqLYxVSierSasBvz0Qnpwe38QU8xUZaWkgTOBiD
H+rpUZLtC2OoE/1QSUjTpNeHR0dAuNaZs0y13TXTDPB6ubvpdzdgxHq8DRPcz3+b
1JKi5BNWpPK7iiRsQy4b8watH2di3pRF7Sjmpbb+fKUcV+kGLVI3gFux9epc6lNV
LoxYtWHjY+KdXYOoLvzDDRV0HqLv3J3CniRAtz5fSCaIf8hps8sUENybl3ePq9st
6ERep5s8Yc2b3rc+eXwPvO1GMB6GEN/xDxkMYKoU+H+8iu1svPc=
=2x97
-----END PGP SIGNATURE-----
pgpethtXd6bdV.pgp
Description: PGP signature
--- End Message ---
