From: Lemures Lemniscati <lemures.lemniscati@gmail.com>
To: cygwin-announce@cygwin.com
Subject: libiconv-1.16-2 (promoted to current)
Date: Sat, 01 Aug 2020 13:31:45 +0900 [thread overview]
Message-ID: <20200801133142.0420.50F79699@gmail.com> (raw)
In-Reply-To: <announce.20200713224250.0EEA.50F79699@gmail.com>
Version 1.16-2 of "libiconv" has been promoted to current.
- libiconv-1.16-2.tar.xz
- libiconv2-1.16-2.tar.xz
- libcharset1-1.16-2.tar.xz
- libiconv-devel-1.16-2.tar.xz
The following files are packaged again, since they are necessary [1]:
- usr/lib/libcharset.a
- usr/lib/libiconv.a
which are removed in libiconv-devel-1.16-1
[1] https://cygwin.com/pipermail/cygwin-apps/2020-July/040302.html
Please, report any issues.
--
GNU LIBICONV - character set conversion library
This library provides an iconv() implementation, for use on systems which
don't have one, or whose implementation cannot convert from/to Unicode.
For more details, see https://www.gnu.org/software/libiconv/ .
--
Lemures Lemniscati
parent reply other threads:[~2020-08-01 4:32 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <announce.20200713224250.0EEA.50F79699@gmail.com>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200801133142.0420.50F79699@gmail.com \
--to=lemures.lemniscati@gmail.com \
--cc=cygwin-announce@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).