Your message dated Sun, 28 Apr 2024 18:37:14 +0000
with message-id <e1s19ok-000mpg...@fasolo.debian.org>
and subject line Bug#1069222: fixed in purple-xmpp-carbons 0.2.3-1.1
has caused the Debian Bug report #1069222,
regarding purple-xmpp-carbons: debian/shlibs.local hardcodes dependency on 
libpurple0
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.)


-- 
1069222: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069222
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: purple-xmpp-carbons
Version: 0.2.3-1
Severity: serious
Tags: trixie sid

debian/shlibs.local hardcodes a dependency on libpurple0,
which makes the package uninstallable on armel/armhf due
to the 64-bit time_t rename to libpurple0t64.

--- End Message ---
--- Begin Message ---
Source: purple-xmpp-carbons
Source-Version: 0.2.3-1.1
Done: Boyuan Yang <by...@debian.org>

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

Debian distribution maintenance software
pp.
Boyuan Yang <by...@debian.org> (supplier of updated purple-xmpp-carbons 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: Sun, 28 Apr 2024 14:13:08 -0400
Source: purple-xmpp-carbons
Architecture: source
Version: 0.2.3-1.1
Distribution: unstable
Urgency: medium
Maintainer: DebianOnMobile Maintainers 
<debian-on-mobile-maintain...@alioth-lists.debian.net>
Changed-By: Boyuan Yang <by...@debian.org>
Closes: 1069222
Changes:
 purple-xmpp-carbons (0.2.3-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Merge downstream Ubuntu changes to fix compatibility after t64
     transition: (Closes: #1069222)
 .
   [ Matthias Klose ]
   * Fix shlibs.local file and dh_shlibdeps override for t64 transition.
Checksums-Sha1:
 efe92f90c28447a2383667551ae0e1878e4b1ef2 2131 purple-xmpp-carbons_0.2.3-1.1.dsc
 8cfcad90e6d26c811d54231f7612d67810536a0c 35409 
purple-xmpp-carbons_0.2.3.orig.tar.gz
 965df28fdb2ca337c6d4ea7be062e4495dd7f09d 2200 
purple-xmpp-carbons_0.2.3-1.1.debian.tar.xz
 42d30a6d51a2a8fcafa9901569f3ffc48e67c0a3 10415 
purple-xmpp-carbons_0.2.3-1.1_amd64.buildinfo
Checksums-Sha256:
 07f78ba71eaa3b563a6c5e2c39d21d9fc9012f71752519306b48113e96911fef 2131 
purple-xmpp-carbons_0.2.3-1.1.dsc
 7aa847cb121483b10677dd67ae401af94550d1a65311fc502600998d2ef67b64 35409 
purple-xmpp-carbons_0.2.3.orig.tar.gz
 c110a1a14fa3734e62ebc8bb7d810f9496f367dd30794704229a444530bb2c15 2200 
purple-xmpp-carbons_0.2.3-1.1.debian.tar.xz
 95fdff1fe17bad7a960ef0edc702a06f59cf4727f4bb4bf97a5f7e79c5f16c44 10415 
purple-xmpp-carbons_0.2.3-1.1_amd64.buildinfo
Files:
 a6326c9c351052b5b3c7a0eb72bc7919 2131 net optional 
purple-xmpp-carbons_0.2.3-1.1.dsc
 5a1787d8951c7faa333693ef08ab62f3 35409 net optional 
purple-xmpp-carbons_0.2.3.orig.tar.gz
 005ab224abf82d372c0ae73af501348e 2200 net optional 
purple-xmpp-carbons_0.2.3-1.1.debian.tar.xz
 007bcd5dbd62c19d510ef9e8159f4789 10415 net optional 
purple-xmpp-carbons_0.2.3-1.1_amd64.buildinfo

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

iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAmYukqsACgkQwpPntGGC
Ws4B2hAAkRbnHT5xkAeLqLM+/TSJdDqOKdcQ9HpAok9qqi2pli2VMu8RNJkq8b9s
POFgCj0Q8m0vOjVACgKDDeWSuap7WlDBhUrH71QVoGmhhmhC9ytGZdt0zYDXb8Kz
gIpnckUjE35WJpH1INowXh9REtMkDLIXsIWsPuFmKZgZGNi/5Oy36P3kk4gzzjaO
DD774fg6Gz19PtKrSDMeUTMEABG+g3c8UTTefCSUBB5kGgttn4Ke3K9URTNRO/E3
g8ccoRkOB+0M80818v8YU8enzYULMl+8RR9USIQ1uL741M9DRgCMtEVclJmM7ylw
C9zoqFrnmVakNmYp9lxxosq+wf4gIn4zE1yi5kPaMP4tuzDdAz9knyLl2nhUarv/
UR++zX6Pc++KTzYE2rP/SdiVwfBa6vnYYEMIdV0hUe18SgHEeCuIJH6kOgMZ3S24
2tVgenrRbJkmHSngbhoQoPrpS7d4Qd58t/fL1d8R2KTUqu5MQ5ikuFlIr80IysnN
Epz3zgRWsy+LxelpQtMMdupOUPeeGrJ67lCCrpjEdjAUxk0RWDPV3Qo63hF823YS
AgXbo12pzRpdkCbPhV6hKw9ACuaLPgXB3wEMiX8N+jrhSlvWdiXNFeqqWcVyyL6w
yxq/fKyNT/emTkikYYFmd9skPoxC5OJWflcnnWT3NwOSgMpnAlE=
=qSKk
-----END PGP SIGNATURE-----

Attachment: pgp9KrEKWiMMV.pgp
Description: PGP signature


--- End Message ---

Reply via email to