[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Accepted glib2.0 2.80.0-9 (source) into unstable



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

Format: 1.8
Date: Sat, 04 May 2024 12:35:50 -0400
Source: glib2.0
Built-For-Profiles: noudeb
Architecture: source
Version: 2.80.0-9
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers <pkg-gnome-maintainers@lists.alioth.debian.org>
Changed-By: Jeremy Bícha <jbicha@ubuntu.com>
Closes: 1062134 1065022 1065280 1066904
Launchpad-Bugs-Fixed: 2063221
Changes:
 glib2.0 (2.80.0-9) unstable; urgency=medium
 .
   * Really upload to unstable
 .
 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:
 7245554815b20682e36279d839547e3016f75d85 4532 glib2.0_2.80.0-9.dsc
 e0932591db6919b556845613fb9384dc5765f040 133096 glib2.0_2.80.0-9.debian.tar.xz
 c01d60452b144689d7cb62fc48ae17384a243229 11653 glib2.0_2.80.0-9_source.buildinfo
Checksums-Sha256:
 7e99c38b128f98c9f6ba9b83620960b4f9b9318c7b52517736cf11407086c17f 4532 glib2.0_2.80.0-9.dsc
 c9ea88d81d3701ad140c846dac9bbb2a16c47dcc3c4628ca64b6f636e966eef3 133096 glib2.0_2.80.0-9.debian.tar.xz
 5c1e666f0d914247af4e4f6a2a5e0f1ab320805754eba7a7532c7b9bb137f18d 11653 glib2.0_2.80.0-9_source.buildinfo
Files:
 bdc9fc3bb5b5682c50bcdd62bef7982c 4532 libs optional glib2.0_2.80.0-9.dsc
 bdf73bf7748d93d65139fdfc3df14df9 133096 libs optional glib2.0_2.80.0-9.debian.tar.xz
 9d142d8edd5d3bed2059d54ca24497b1 11653 libs optional glib2.0_2.80.0-9_source.buildinfo

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

iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAmY2ZK4ACgkQ5mx3Wuv+
bH0+Lw//S3jdhyY7wjCcFWF7wTmQc7oTjeHIw28Tf0vV7kdu3iUfu4quXX44gtb7
oF8GGs0ScDAn26sQTcjWIqvsYStxXcm3tLrfBPQ35LamAROcsuSCNq0gL9oZROgZ
hhy+Y2CtVgdt2pon8VV832sP4TlmRqciCf1a6gTfQv2Smi+9U+vNTxawET1HEiOl
6PckPbi0gYJodx8EXGdcqajqOS+Xsl/Lsw1oS1pdzefb/dUtgQft3oUYSxkDcqOj
KRrE5CLgaHoKQB+BTYhX7q/iABYluLLtbbzaA6CxoSJ/wd54TFyKJjpHtx0Z03lr
TM09Oj5iHFhhq6NVOsissqk+MRRi+d4JhuReRPMoQJ2cWuZ8lDqLVQeCP1fUNasT
DIHidvCqB8JNfF/UdQDjBMpmCb3D9Q6gvlV0fPR5/Khj38GFtzj25vZ97gbsc+g6
4Krt5XzM9OmaxAZ9be1cNC1sj8mzPsuBpN1y5ZXKOC95RLQX/6+9sSxdYDNU6OTz
9wHTabl2ApjI0pABoJtMXOn3nAuNao7J65GF1ICXKzXBheFPUSeAfjKd7sNSE3rE
IoT/jSUsSXahaa/IcgrIX30JJtEE6RmqoEehb7m1zRoyz/azTnLtymCK9z/vnfLh
CZbxLUUs95QOyWI6fmCq4hF0DaDC+BveS1Cq4YgvGBQmYH3kKJ8=
=5q0S
-----END PGP SIGNATURE-----

Attachment: pgpXMRq2UgQMJ.pgp
Description: PGP signature


Reply to: