glib2.0_2.80.0-8_source.changes ACCEPTED into unstable

Debian FTP Masters ftpmaster at ftp-master.debian.org
Sat May 4 17:35:58 BST 2024


Thank you for your contribution to Debian.



Accepted:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Sat, 04 May 2024 12:19:49 -0400
Source: glib2.0
Built-For-Profiles: noudeb
Architecture: source
Version: 2.80.0-8
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers <pkg-gnome-maintainers at lists.alioth.debian.org>
Changed-By: Jeremy Bícha <jbicha at ubuntu.com>
Closes: 1062134 1065022 1065280 1066904
Launchpad-Bugs-Fixed: 2063221
Changes:
 glib2.0 (2.80.0-8) unstable; urgency=medium
 .
   * Upload to unstable
 .
 glib2.0 (2.80.0-7) experimental; urgency=medium
 .
   [ Simon McVittie ]
   * Revert addition of libglib2.0-0 transitional package. (LP: #2063221)
     Because it didn't have a Pre-Depends on the replacement, it resulted
     in GLib libraries being absent for an extended period, which is
     problematic. Thanks to Julian Andres Klode.
 .
 glib2.0 (2.80.0-6) experimental; urgency=medium
 .
   * Bump Breaks/Replaces older libglib2.0-0 since some people used 2.79.3
 .
 glib2.0 (2.80.0-5) experimental; urgency=medium
 .
   * Merge packaging from unstable
     - Reinstate tests on 32-bit non-x86.
       The required packages have become available now.
   * Build with sysprof instrumentation on architectures that have it.
     This currently means release architectures, plus the powerpc and ppc64
     ports. Make it possible to disable this with a (non-reproducible)
     build profile, to facilitate re-bootstrapping.
 .
 glib2.0 (2.80.0-4) experimental; urgency=medium
 .
   * d/emulated-g-ir-tool.in: Rename from cross-g-ir-tool.in.
     This makes it consistent with the template of the same name in
     gobject-introspection.
   * d/emulated-g-ir-tool.in: Fix qemu-user invocation.
     Previously, the gi- tools generated from this template only worked on
     systems that could run the tool directly via binfmt_misc. Now they invoke
     qemu-user explicitly, as intended.
 .
 glib2.0 (2.80.0-3) experimental; urgency=medium
 .
   * Merge packaging from unstable
     - d/control: libglib2.0-0t64 Breaks/Replaces a constant version of
       libglib2.0-0
     - d/control: Bring back libglib2.0-0 as a transitional package
   * d/p/girparser-Don-t-assume-sizeof-size_t-sizeof-void.patch,
     d/p/girparser-Allow-time_t-off_t-etc.-to-appear-in-GIR-XML.patch,
     d/p/girparser-Make-sizes-in-integer_aliases-more-obviously-co.patch,
     d/p/girparser-Adjust-signedness-to-avoid-compiler-warnings.patch,
     d/p/girparser-Add-a-pseudo-doc-comment-for-signedness.patch:
     Add patches to make gi-compile-repository compatible with versions of
     g-ir-scanner where #1066032 has been fixed
   * Bump build-dependency on gobject-introspection to ensure that our
     typelibs are generated with #1066032 fixed
 .
 glib2.0 (2.80.0-2) experimental; urgency=medium
 .
   * Use host-architecture gi-compile-repository, etc. when cross-compiling.
     When setting up the cross wrappers for gi-compile-repository, etc. I had
     assumed that gi-compile-repository was a simple transformation from
     GIR XML into binary, which varied only by its endianness. Unfortunately,
     it is not: it also transforms abstract types such as size_t into
     equivalent fixed-size types such as guint64, which requires knowledge
     of the size of each type.
     Instead of running the build architecture gi-compile-repository and
     telling it to use the host architecture search path, install upstream's
     gi-compile-repository etc. into ${pkglibdir}, and set up cross wrappers
     that will automatically detect whether we can run them directly or
     whether we must use qemu-user. This is not "pure" cross-compilation,
     but it's the best we can do.
     This means that the build and host OS must match, but it does have the
     side benefit that we no longer require the build and host endianness to
     be the same, because everything that interacts the typelib is now a
     host binary (possibly running under qemu). (Closes: #1066904)
   * Temporarily skip all tests on 32-bit non-x86 architectures, to avoid
     circular dependencies during the t64 transition
 .
 glib2.0 (2.80.0-1) experimental; urgency=medium
 .
   [ Jeremy Bícha ]
   * New upstream release
   * Don't build installed tests when we're not building installed tests
 .
   [ Steve Langasek ]
   * Don't call makeshlibs for a package that isn't built
 .
   [ Simon McVittie ]
   * Merge packaging from unstable
     - d/control: libglib2.0-dev Suggests gir1.2-glib-2.0-dev in preference
       to libgirepository1.0-dev, for multi-arch co-installability.
 .
 glib2.0 (2.79.3-3) experimental; urgency=medium
 .
   * Merge pending packaging from unstable
     - Mention #1065280 in 2.79.3-1 changelog entry
   * d/libglib2.0-0t64.preinst: Remove libglib2.0-0 postrm to avoid file loss
     during the time64 transition (Closes: #1065022)
   * d/tests/manual/1065022.sh: Add a manual reproducer for #1065022
   * d/libglib2.0-0t64.postrm: Only clean up giomodule.cache during purge.
     This matches the behaviour that we have had for gschemas.compiled
     since 2012, with similar reasoning: if we remove this file during
     remove, then during upgrades there is a window between old-postrm
     and new-postinst during which giomodule.cache is missing.
   * d/libglib2.0-0t64.postrm: Avoid recurrence of #1065022 in the future.
     If at some point in the future we have another transition as extensive
     as time64, then libglib2.0-0t64 could conceivably be replaced by
     some other package, for example libglib2.0-0xyz. If that happens,
     we need to avoid deletion of gschemas.compiled and giomodule.cache,
     otherwise we will have another bug similar to #1065022.
   * d/tests/1065022-futureproofing: Add a test for recurrence of #1065022.
     This test-case depends on several implementation details which
     might cause it to regress for reasons that are not genuinely
     release-critical, so it is marked as flaky.
 .
 glib2.0 (2.79.3-2) experimental; urgency=medium
 .
   [ Gianfranco Costamagna ]
   * Fix shlibs to fix installability on armhf
 .
 glib2.0 (2.79.3-1) experimental; urgency=medium
 .
   * New upstream development release
   * d/copyright: Update
   * d/patches: Drop patches that were included in the upstream release
   * d/patches/workarounds: Unfuzz a patch whose context changed slightly
   * d/libgirepository-2.0-dev.install: libgirepository-2.0.a is now provided
   * d/libglib2.0-dev-bin.install: Install new man pages for gi- tools
   * Use d/*.manpages to install upstream man pages.
     This ensures that they're skipped if building with nodoc.
   * d/rules: Create cross-prefixed symlinks to gi- tools' man pages
   * d/patches: Mention the cross-prefixed gi- tool names in their man pages
   * d/libglib2.0-0t64.post*: Stop generating from a template.
     dh_installdeb will substitute #DEB_HOST_MULTIARCH# for us since
     debhelper 12.2 (2019).
   * d/rules: Generate libglib2.0-0t64.triggers just before the command
     that uses it
   * d/libglib2.0-0t64.postinst: Remove workarounds that are no longer needed.
     As noted in their comments, now that Debian 12 and Ubuntu 22.04 were
     both released with these workarounds included, the workarounds can
     safely be removed from newer distro branches.
   * Merge packaging from unstable (Closes: #1062134)
   * Build-depend on dpkg-dev (>= 1.22.5), to ensure that we are on the
     64-bit time_t side of the transition (Closes: #1065280).
     If this version gets backported, then the whole t64 package rename
     (including this change) will need to be reverted in the backport.
   * d/clean: Update for the time64 transition
   * Fix filename of README.Debian for libglib2.0-0t64.
     This regressed during the t64 transition, presumably renamed with the
     help of a script that didn't take multiple extensions into account.
Checksums-Sha1:
 4d58dcfa301cfa5d0a7646db400c424a32f37b96 4532 glib2.0_2.80.0-8.dsc
 2776a9485f00d83c2a763f94108018b49a998df3 133104 glib2.0_2.80.0-8.debian.tar.xz
 ed8bb586aab2f494d29f7cf5694245b2c7771cc6 11653 glib2.0_2.80.0-8_source.buildinfo
Checksums-Sha256:
 6f8f8b8b0c238c6eefede91ea79be7476d8649b22f11dc4475687ad01fe4f48a 4532 glib2.0_2.80.0-8.dsc
 d6f880d823f0f5d714315caca8893efaf3b30fbe54e5ec5cb310586c25b57d1c 133104 glib2.0_2.80.0-8.debian.tar.xz
 dba0cae762487298e6434dd653b6bcf1b0ccef6d48938d89460e9f75aa7826e5 11653 glib2.0_2.80.0-8_source.buildinfo
Files:
 883c404c862c13e1a5fdd23249b30fa0 4532 libs optional glib2.0_2.80.0-8.dsc
 c9f54e85f1e03d89c86fd48625a354ed 133104 libs optional glib2.0_2.80.0-8.debian.tar.xz
 d3366971cf25c8b4709b32fcd221472e 11653 libs optional glib2.0_2.80.0-8_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAmY2YHsACgkQ5mx3Wuv+
bH0XwRAAqAAIqWJ2GAnpTnNNKpgpwxOl66BxVzHMsRbxGJyfrDoWFBYFKziZF7yH
vpRTeUaBSks0q4Q+PTsSryiNjW7cKuQS/9XVFHemGYeZ9IrYjOptqm5fjN8tVkOT
jpUOLYLK8RIQsbcEx4VSG9e0uySeUpJ3a1Vmrk6h753CWRcATy3KSbdRhZVdzYC8
ChLDxL5KKMuyjHEH/zQveF/HiQwPXa8bb4NcJr4aX6k9aUDHnHlo30fz0YVmvpPA
UFJcFicNzH1OpeduARXCgJmVexEkF/2TvP0JybnWJGmS7LS/sq8aQ7+Yjav6CQAf
4B1nDBf4WQR9OsRxOw0+RHah+eRtVK/0ASl912sEqohPbEvCSzvkWyiHPfo5YUCF
cAJKBlUhD5uokxbbbcEFjOrq69DaiUNvh6SLOzPQhnarocY2GyXKymFHXv1y1hPE
j5w4oVXCxsPVoF3flx1dhectTPkgKUv+kOX5kxzGUi/fgvCaNQoKydi4y6u1bMFT
/FfMZozMAlJ3m1NpkFP36hN0yuoRgFcqYveMAAGE+ACMnItZ3lcE6fLPstxCWO0N
e2P8+HazahVrsKrJVJZifdIHgvrb2CLO79Xz/10o1GQmLgLx0LFFv14J+u31Uvtz
KSUpAZGp+Vc69E7sCTYK1LxTh7Iqg6KEJoDdgH+4x0ijBQs1LoE=
=uUfc
-----END PGP SIGNATURE-----

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 228 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-gnome-maintainers/attachments/20240504/2faf85a4/attachment.sig>


More information about the pkg-gnome-maintainers mailing list