Re: [ATTN maintainer] libunistring 1.3 needed
Brian Inglis via Cygwin-apps <[email protected]> Fri, 9 Jan 2026 15:59:38 -0700
| Newsgroups | gmane.os.cygwin.applications |
|---|---|
| Organization | Systematic Software |
| Message-ID | <[email protected]> |
On 2025-07-29 12:44, Brian Inglis wrote:
> Hi Erwin,
>
> Could you please package the latest libunistring 1.3 (available since last
> October) as it appears it should fix issues I have updating gettext, according
> to the upstream maintainer of both.
>
> I have successfully built a local copy and pushed an update to the CI playground
> repo:
> https://cygwin.com/cgi-bin2/jobs.cgi?srcpkg=libunistring&id=10200
>
> https://cygwin.com/cgit/cygwin-packages/libunistring/commit/?
> id=e3b60bdc62e0b271061159b42391f20606cdb90d
>
> also defining LICENSE (from README, COPYING.LIB, COPYING) and BUILD_REQUIRES
> (from DEPENDENCIES), adding ABI for SO/DLL version, and use in `declare`
> variable definitions, to make future updates easier (tip from Jon Turney).
>
> From what I have seen in recent builds, you may no longer need the CFLAGS you
> define, as they all seem to do that, possibly from using gnulib with autotools.
[BCC DM Erwin]
Hi folks,
With no response to this previous request, for a requirement to build gettext
under CI, and a new release 1.4.1 available upstream, would anyone have an issue
with my releasing an NMU?
With NMU perms, can I push to libunistring main branch and deploy?
--
Take care. Thanks, Brian Inglis Calgary, Alberta, Canada
La perfection est atteinte Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add
mais lorsqu'il n'y a plus rien à retrancher but when there is no more to cut
-- Antoine de Saint-Exupéry