Re: [ATTN maintainer] libunistring 1.3 needed

On 10/01/2026 04:51, Marco Atzeri via Cygwin-apps wrote:
> On 09/01/2026 23:59, Brian Inglis via Cygwin-apps wrote:
>> 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?
>>
> 
> Not at all.
> 
>> With NMU perms, can I push to libunistring main branch and deploy?
>>
> 
> No idea.

Yes.

This probably needs better documenting, but for the moment [1].

[1] https://cygwin.com/pipermail/cygwin-apps/2023-May/042910.html