Your message dated Tue, 19 Mar 2024 21:06:26 +0000
with message-id <e1rmgfc-004faq...@fasolo.debian.org>
and subject line Bug#1067193: fixed in meld 3.22.1-2
has caused the Debian Bug report #1067193,
regarding meld: hard-coded dependency on libgtk-3-0 will become uninstallable 
on armel/armhf
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.)


-- 
1067193: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067193
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: meld
Version: 3.22.1-1
Severity: serious
Justification: blocker for 64-bit time_t transition
User: debian-...@lists.debian.org
Usertags: time-t
Control: block 1036884 by -1

meld is an Architecture: all package, but has a direct dependency on
libgtk-3-0, as well as an indirect dependency on libgtk-3-0t64 via
gir1.2-gtksource-4 and gir1.2-gtk-3.0.

On the architectures affected by the 64-bit time_t transition (notably
armel and armhf), this is an impossible dependency, because libgtk-3-0 and
libgtk-3-0t64 conflict.

Please remove the explicit dependency on libgtk-3-0, and replace it
with gir1.2-gtk-3.0 if appropriate. For Python code that uses GTK via
GObject-Introspection, it is sufficient to depend on gir1.2-gtk-3.0.

More information about this transition is available on
<https://wiki.debian.org/ReleaseGoals/64bit-time>.

Thanks,
    smcv

--- End Message ---
--- Begin Message ---
Source: meld
Source-Version: 3.22.1-2
Done: Jeremy Bícha <jbi...@ubuntu.com>

We believe that the bug you reported is fixed in the latest version of
meld, 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 1067...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jeremy Bícha <jbi...@ubuntu.com> (supplier of updated meld 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: SHA512

Format: 1.8
Date: Tue, 19 Mar 2024 16:52:04 -0400
Source: meld
Built-For-Profiles: noudeb
Architecture: source
Version: 3.22.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 
<pkg-gnome-maintain...@lists.alioth.debian.org>
Changed-By: Jeremy Bícha <jbi...@ubuntu.com>
Closes: 1067193
Changes:
 meld (3.22.1-2) unstable; urgency=medium
 .
   * Replace Depends: libgtk-3-0 with gir1.2-gtk-3.0 (Closes: #1067193)
Checksums-Sha1:
 589228d5742294ab00cf01a6ecb2d605605afd3c 2082 meld_3.22.1-2.dsc
 ec2fb5508f2e5dae76945b4f81af51d24e9726ac 12824 meld_3.22.1-2.debian.tar.xz
 b009554d37fe6031822b5dcb525d8f68f1090601 18134 meld_3.22.1-2_source.buildinfo
Checksums-Sha256:
 1d6ebb2bffa48fb40909b44949e2d26e93d87dee1654d2516e9487729f6daec7 2082 
meld_3.22.1-2.dsc
 350e9089acfa51b8d0b462b3873dbde7c8c713eb7d9325fbf5fc9680a516a65d 12824 
meld_3.22.1-2.debian.tar.xz
 a5a27f9e01c95cab82cd69ce8c5757ecc6dd377365117f1ce9ab6776c3aa47fc 18134 
meld_3.22.1-2_source.buildinfo
Files:
 40b116df971d2cda9b9712cb2379674f 2082 gnome optional meld_3.22.1-2.dsc
 a1eebfd004058cc02ceccf4a27bf7820 12824 gnome optional 
meld_3.22.1-2.debian.tar.xz
 4ff90c3f7cf635f03a6dbe50aecfc3f5 18134 gnome optional 
meld_3.22.1-2_source.buildinfo

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

iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAmX5+xEACgkQ5mx3Wuv+
bH0IbhAArOJN8H8a/60j/YU+TnSz1GiVCh5uBn/jhKxwjckW5hqK59JzMQwwylES
cKtp23xrbLADlLkrV1oGRp8IX1ezc4cE0Y+oOAce+Z/mC0wcJ+lej1EPsQmpxic8
b26/a7MQMTmGvqu0ptjQglLORixRd7DrAKQ6KqwnvHQeimQ+82DPwrrL/B3h7u5N
/IZMdqnJyPYUNjiwL/nrKxHhOykOZLC2wtvixsvw2Izs/6u7N6TkzHTkNiev+43C
aEQrJrywg7gKh5aLRuJkZgHWO1HufycwKiVsa6w63sowSoM70DNwGuff/AT4K6F5
9HwJpK6FmFZwbbCgY7kq9FUqapUiger0YahWDJ7bUi2uZ5ToWQBqxnWQbPwPNhfx
bFb1QLvC7HE1J4Pdh0XUE9DNTTSvTmAw0BvVOLl1ximF6V0SxJYAOrtnsV1nBGq7
q2VKwZvElEf0mWJVoib6nQJPAONfAYkIv/DhzpJ5pcQY5V2ji6CvLXbQwRakdv/Y
xfYRc+ipEuJOiXlQKZ8NJRkgaLd/h+fr2A+sfVOKbi40+j4H3qrpCS4mm4foMiD9
WDdEWcgHEH8lhsKlJnXL/ITJszMQjMMqAYjt3/EH11D3HS6G4E0iKFDqWsC8bSbP
JLpmU8gjdJhQIr799TwED4i8+JQiqVY4BdsbJRtBNxZ7PI4klso=
=z5JA
-----END PGP SIGNATURE-----

Attachment: pgp3DDlBz9Afi.pgp
Description: PGP signature


--- End Message ---

Reply via email to