Your message dated Fri, 27 Sep 2024 17:34:04 +0000
with message-id <e1sueqy-00ft2t...@fasolo.debian.org>
and subject line Bug#1079950: fixed in chafa 1.14.4-1
has caused the Debian Bug report #1079950,
regarding chafa: Fails to build on some architectures with glibc 2.40
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.)
--
1079950: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1079950
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: chafa
Version: 1.14.2-1
Severity: serious
Tags: ftbfs
Based on the Ubuntu build logs, I suspect that chafa fails to build on
some architectures with glibc 2.40. Note that although chafa was
uploaded a few days ago, the new version of glibc was uploaded to
Unstable for the first time after that date.
Feel free to close this bug if it's verified that chafa does build on
all Debian release architectures.
Build log excerpt
------
/usr/bin/ld: chafa-svg-loader.o: undefined reference to symbol
'lrint@@GLIBC_2.4'
/usr/bin/ld: /lib/arm-linux-gnueabihf/libm.so.6: error adding symbols:
DSO missing from command line
Full build logs
----
https://launchpad.net/ubuntu/+source/chafa/1.14.2-1
Thank you,
Jeremy Bícha
--- End Message ---
--- Begin Message ---
Source: chafa
Source-Version: 1.14.4-1
Done: Mo Zhou <lu...@debian.org>
We believe that the bug you reported is fixed in the latest version of
chafa, 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 1079...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Mo Zhou <lu...@debian.org> (supplier of updated chafa 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: Fri, 27 Sep 2024 13:22:35 -0400
Source: chafa
Architecture: source
Version: 1.14.4-1
Distribution: unstable
Urgency: medium
Maintainer: Mo Zhou <lu...@debian.org>
Changed-By: Mo Zhou <lu...@debian.org>
Closes: 1079950
Changes:
chafa (1.14.4-1) unstable; urgency=medium
.
* New upstream version 1.14.4 (Closes: #1079950)
Checksums-Sha1:
80533ca55d9a88fc9162994d7e9aed42d93c709b 2111 chafa_1.14.4-1.dsc
7c825bf8b1235f98894bebd801b5206fcb1bee5c 1861126 chafa_1.14.4.orig.tar.gz
24d94d32aad89dce78e08d1682b64824fd3e8dbd 6756 chafa_1.14.4-1.debian.tar.xz
0fe47fe3fee72c87311570afa400d78305baf8d0 8027 chafa_1.14.4-1_source.buildinfo
Checksums-Sha256:
8ee4c4008024762bcdcbe1f484cb582ce58621009a59a2299531267e9cf0bfd1 2111
chafa_1.14.4-1.dsc
65b084173eb904c3e0b4eafd561cf0f676a17fe19b0d47b98118808f0646c92e 1861126
chafa_1.14.4.orig.tar.gz
15aba0dc66a1ad5df3f22c177c8726494700fdee8101cff97768cb8330e1ab38 6756
chafa_1.14.4-1.debian.tar.xz
bad22b4e274c91d06313bf45ed90f2bbc01a0cc21a804f4325e45216e355c5f7 8027
chafa_1.14.4-1_source.buildinfo
Files:
19312ada91abdbfd6bff950eae43b999 2111 graphics optional chafa_1.14.4-1.dsc
2e7d54befab78a7b46d419360e93673a 1861126 graphics optional
chafa_1.14.4.orig.tar.gz
3e9bfdcc4d36fa5e17e8962e77a26e22 6756 graphics optional
chafa_1.14.4-1.debian.tar.xz
fdc86f403d723702a6850e97b5073e43 8027 graphics optional
chafa_1.14.4-1_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJFBAEBCgAvFiEEY4vHXsHlxYkGfjXeYmRes19oaooFAmb26fcRHGx1bWluQGRl
Ymlhbi5vcmcACgkQYmRes19oaorPuxAAoL1GfTs/qjRDG/9qQUgo/tV1UeLLdekh
O1gwDKdTSnWXpELRbfYgEsEpHoevt+R7cje5Pba6YpLZHONGumjHMfAbywyOVJHg
WtgMn5S19QTtE8rT8ox/l0CHx6FsF+NffWM0JIoTffKTGoxh2JgAb2pQuqn63UAw
ATtukHw4W7e4DP2AMGCl00AWAk7CYFCqR3vfaDr6CUYgUPzsQvHGl2unqBgXRHQv
uvb5La5jXUcoT1+scxmkF34furt9QgTdMu0t7YO19mHBFRKEK5H2sbVKCQPWi8qC
6cUWl4FeUph/HAhsA41hozodkVzSRinMxp1P/yiEnnqiXpa3z/I7rpnhZzNQSkKj
QhFjwT/4QYd0zWnzlIPZICkVXQgwWDDPx4Mf4D8ElmJlBpiTMEE5lKzrYRb8a9Kj
lcPd4XnUPpU6EzP1yj07ODLq41DhXG8NvhHptJpMreMvNnEj8roPAo9AGOXXT0M3
cV5LLTpbCkjBGgO6TwJ1kUmTb4Oe44+c4hSFvXdSQNPHESqFaEvWMjacbK2p1w3b
aYZis2Cx2/GhvaBmXwMzLecNfqhC7J2zbHaW4Ga25Ep5+bMiWVQeLrh2McG+hIWM
Giu+bVkd+FHayCrl1Ygx1WQEANhjYooMHTAr9kA5rd04ayAW65HSsYnckj6vPc+R
+1DNTeZ7wZI=
=uViy
-----END PGP SIGNATURE-----
pgpQtqiJU7yxm.pgp
Description: PGP signature
--- End Message ---
