From: Thomas Wolff <towo@towo.net>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: libunistring 1.1-1
Date: Sun, 13 Nov 2022 22:17:20 +0100 [thread overview]
Message-ID: <55b4fd3d-dba0-33f0-a9eb-7baedfd99914@towo.net> (raw)
In-Reply-To: <16d54060-30eb-b694-8407-93a6749d39ab@SystematicSw.ab.ca>
Am 13.11.2022 um 21:43 schrieb Brian Inglis:
> On Sat, 12 Nov 2022 13:50:58 +0100, Achim Gratz wrote:
>> Erwin Waterlander via Cygwin-announce writes:
>>> libunistring (source package)
>>> libunistring5 (runtime library)
>>> libunistring-devel (development library and include files)
>>> libunistring-doc (documentation)
>
>> The packages for x86 seem to be missing, however it seems Brian still
>> managed to release an x86 gettext with a dependency on nonexistent
>> libraries…
>
> See also message subject "Error after updating gettext, missing
> libunistring5"
> https://cygwin.com/pipermail/cygwin/2022-November/252446.html
> https://inbox.sourceware.org/cygwin/CADt9575LdQPZpVivfSFkwjytmDJgOu_WEZ=FdLMXynfg_oyrtQ@mail.gmail.com/
>
> as both arches built without any libunistring dependencies included,
> and deployed as such.
>
> Rebuilding and redeploying release 2 with expected dependencies when
> available and valid.
>
By the way, on cygwin 32-bit the dependency does not resolve as
libunistring5 is not available...
next prev parent reply other threads:[~2022-11-13 21:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-11 8:56 Error after updating gettext, missing libunistring5 Carlo B.
2022-11-13 20:43 ` [ANNOUNCEMENT] Updated: libunistring 1.1-1 Brian Inglis
2022-11-13 21:17 ` Thomas Wolff [this message]
2022-11-14 13:28 ` Erwin Waterlander
2022-11-14 13:33 ` Thomas Wolff
2022-11-14 21:21 ` Brian Inglis
2022-11-15 9:14 ` Erwin Waterlander
-- strict thread matches above, loose matches on Subject: below --
2022-10-28 6:41 Erwin Waterlander via Cygwin-announce
2022-11-12 12:50 ` Achim Gratz
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=55b4fd3d-dba0-33f0-a9eb-7baedfd99914@towo.net \
--to=towo@towo.net \
--cc=cygwin@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).