help-libidn
[Top][All Lists]
Advanced

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

Bug#999510: marked as done (libidn2 FTBFS for musl-linux-any: broken get


From: Debian Bug Tracking System
Subject: Bug#999510: marked as done (libidn2 FTBFS for musl-linux-any: broken gettext check)
Date: Wed, 31 Jan 2024 10:54:07 +0000

Your message dated Wed, 31 Jan 2024 10:51:56 +0000
with message-id <E1rV8CC-00FQG2-As@fasolo.debian.org>
and subject line Bug#999510: fixed in libidn2 2.3.7-2
has caused the Debian Bug report #999510,
regarding libidn2 FTBFS for musl-linux-any: broken gettext check
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 owner@bugs.debian.org
immediately.)


-- 
999510: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999510
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- Subject: libidn2 FTBFS for musl-linux-any: broken gettext check Date: Fri, 12 Nov 2021 07:39:11 +0100
Source: libidn2
Version: 2.3.2-2
Tags: patch upstream
User: helmutg@debian.org
Usertags: rebootstrap

libidn2 cannot be built for musl, because its gettext check is broken.
That's fixed in the macro now, but libidn2 needs to opt into the fix.
Please consider applying the attached patch.

Helmut

Attachment: musl.patch
Description: Text Data


--- End Message ---
--- Begin Message --- Subject: Bug#999510: fixed in libidn2 2.3.7-2 Date: Wed, 31 Jan 2024 10:51:56 +0000
Source: libidn2
Source-Version: 2.3.7-2
Done: Simon Josefsson <simon@josefsson.org>

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

Debian distribution maintenance software
pp.
Simon Josefsson <simon@josefsson.org> (supplier of updated libidn2 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 ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Wed, 31 Jan 2024 10:51:13 +0100
Source: libidn2
Architecture: source
Version: 2.3.7-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Libidn team <help-libidn@gnu.org>
Changed-By: Simon Josefsson <simon@josefsson.org>
Closes: 999510
Changes:
 libidn2 (2.3.7-2) unstable; urgency=medium
 .
   * Last upload should fix musl.  Closes: #999510.
   * tests: Fix build-dependency for standalone.
   * Run wrap-and-sort -satbk.
Checksums-Sha1:
 fa0896e670e394a5481952706381482d9f22f51d 1963 libidn2_2.3.7-2.dsc
 7bf1515c4ed8d2b0637dbfc8ce55c2aed98638c6 16276 libidn2_2.3.7-2.debian.tar.xz
 c4ea243456fdb8dcbb3b5f7cabfb358c0b882206 11296 libidn2_2.3.7-2_amd64.buildinfo
Checksums-Sha256:
 ba763f71c75847be4c68557a937484ff9e676c0af8be9a6796c914dab1363a5f 1963 
libidn2_2.3.7-2.dsc
 1f0ca3a2bb2c745056933cb41d212965b6571c9a436f83d33cba15e932d88d29 16276 
libidn2_2.3.7-2.debian.tar.xz
 2b22f8e1164ab88dc8cc5d31ddd4e32dadbf9d81a0acea97c71cabb7ba6fc74e 11296 
libidn2_2.3.7-2_amd64.buildinfo
Files:
 f4e5ede114c75981bef1a5749f6f97c9 1963 libs optional libidn2_2.3.7-2.dsc
 194283ec73de50b183525eee932ba3f6 16276 libs optional 
libidn2_2.3.7-2.debian.tar.xz
 b811a8b6848248b6464a9668aacf15af 11296 libs optional 
libidn2_2.3.7-2_amd64.buildinfo

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

iIoEARYIADIWIQSjzJyHC50xCrrUzy9RcisI/kdFogUCZbofEhQcc2ltb25Aam9z
ZWZzc29uLm9yZwAKCRBRcisI/kdFopThAQCDk2BwDPDT/xIXvtDP6gF+pp/52xxr
Ij2ih0PvxvwKMwEA1tJolmunl6kSehJ23UiiUCYYULBloozFbcrJFnpcCQM=
=mi4H
-----END PGP SIGNATURE-----

--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]