Your message dated Sun, 03 Mar 2024 18:04:32 +0000
with message-id <e1rgqco-00c1nw...@fasolo.debian.org>
and subject line Bug#1065280: fixed in glib2.0 2.78.4-3
has caused the Debian Bug report #1065280,
regarding glib2.0: missing dpkg-dev (>= 1.22.5) build dependency for time_t
transition
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 ow...@bugs.debian.org
immediately.)
--
1065280: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065280
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: glib2.0
Version: 2.78.4-2.1
Severity: serious
X-Debbugs-Cc: sramac...@debian.org
Thank you for uploading the changes required for the time_t transition.
Unfortunately, the upload was missing dpkg-dev (>= 1.22.5) in
Build-Depends. This leads to two potential issues:
* The package is built with the wrong ABI.
* The package migrates to testing before the change is enabled in
testing and builds there would be produced against the wrong ABI.
Please add dpkg-dev (>= 1.22.5) to Build-Depends and upload the new
version ASAP.
Cheers
--
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: glib2.0
Source-Version: 2.78.4-3
Done: Simon McVittie <s...@debian.org>
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 1065...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Simon McVittie <s...@debian.org> (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 ftpmas...@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Sun, 03 Mar 2024 13:30:12 +0000
Source: glib2.0
Architecture: source
Version: 2.78.4-3
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers
<pkg-gnome-maintain...@lists.alioth.debian.org>
Changed-By: Simon McVittie <s...@debian.org>
Closes: 1065022 1065280
Changes:
glib2.0 (2.78.4-3) unstable; urgency=medium
.
* 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/libglib2.0-0t64.preinst: Remove libglib2.0-0 postrm to avoid file loss
(Closes: #1065022)
* d/tests: Add a manual reproducer for #1065022
* 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/libglib2.0-0t64.postrm: Only clean up giomodule.cache during purge.
This matches the behaviour that we have had for gschemas.compiled
since 2012.
* 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.
* 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.
* d/control: libglib2.0-dev Suggests gir1.2-glib-2.0-dev in preference
to libgirepository1.0-dev, for multi-arch co-installability.
* 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:
95ff673e0e875d5e6e19cd0937c491021d75835c 3765 glib2.0_2.78.4-3.dsc
81121d5a8a8d5bc74ded000ab034a41caad1c1d3 123424 glib2.0_2.78.4-3.debian.tar.xz
6869bb3c70ded6ee994ce23b1c398f9d2c9794fd 7494 glib2.0_2.78.4-3_source.buildinfo
Checksums-Sha256:
6c6dd2ba30deefd46c8b5a28beb1f4fc41ab8b68690c5e161705d042bbf4f156 3765
glib2.0_2.78.4-3.dsc
72361967d752796fec3a6f1d56298e250198b1d08fc446eb309d527df8e6ef00 123424
glib2.0_2.78.4-3.debian.tar.xz
96c6883a196381948121e8fd3e6e8b2684b412d2d83154c323c6bc640d7bd060 7494
glib2.0_2.78.4-3_source.buildinfo
Files:
acba48a04d14018102d1e3debc80faec 3765 libs optional glib2.0_2.78.4-3.dsc
bde1d7669b3492f0759125b8a4e056ae 123424 libs optional
glib2.0_2.78.4-3.debian.tar.xz
5511421b20f7ebf540ddf8384a4f53df 7494 libs optional
glib2.0_2.78.4-3_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEENuxaZEik9e95vv6Y4FrhR4+BTE8FAmXkupYACgkQ4FrhR4+B
TE+XFQ/+PCDeLeppmd+Q1mx54MrMqqpgxjHcSrJc+V7hF88R0aJZpPiecwAGzijV
DQf+AX+iy8XJwbxE+0xgYQPpwvCZNzt+GYc14oNcxDgMx7TEpUW5JTwuN+QGp4L1
Tk0SveO8MZRI0HcOWC6JTsUfJ38Us7ocoznlxDk9EpLKJ48B/38iFYCo73xafewq
QLj5psdnXpzF+gl3TSXj1ny4xljWR4q67ljaM7jpV2Y//LGaleEyPwlpG6UheNa0
MD8+zJMaRFRGkQLsHhSSNATuJwaZfO/DX3QKzPjFayb8irb1kLhNzJJR+1dtuAWn
BIanJXmCTuCngbZ1fwfhjqv6J/ICZo75MBBsPvt+TmioCutgFDL8H4ynUdenHwMZ
VGQLfwYnCjAzizWFlkBmqorNOeg1s/SsPOAs/MCmcAhzW+4vhSxE6JNSS1saVHD0
3q1QjElMXNpCFZ9GgfnXk7crg4j4DfUq3v8oR/ZH5eInVKkWGOkgZtLk9FP8iCc/
56Cv8k7CYAr+EB8QsdNNGeB6LEvmjWC/luQl3eqtYyFraDHBIsBJUFf7JKjKNLF0
gWkfm6oQm+/bRkd5ENvdt1rwly6xANxNzNGCgK8WQkYRPoN3lyQq2xHsr4wuoDDL
fnLse73Tqn5oldFeTz8xaLhThCepdoKj6Y7Jmjr/pFRlnOSvq/4=
=vnqd
-----END PGP SIGNATURE-----
pgpbVTks1f9dE.pgp
Description: PGP signature
--- End Message ---