CLDR pkg-config (was: cygport upload)

Brian Inglis
Fri Mar 27 18:25:03 GMT 2020

On 2020-03-27 11:31, Thomas Wolff wrote:
> Am 27.03.2020 um 17:27 schrieb Jon Turney:
>> On 27/03/2020 16:15, Thomas Wolff wrote:
>>> Am 27.03.2020 um 16:41 schrieb Jon Turney:
>>>> On 27/03/2020 14:35, Thomas Wolff wrote:
>>>>> Am 27.03.2020 um 13:21 schrieb Jon Turney:
>>>>>> On 27/03/2020 10:17, Thomas Wolff wrote:
>>>>>>> How does cygport upload work?
>>>>>>> I previously uploaded with sftp but cygport apparently runs lftp and it
>>>>>>> asks me for a password.
>>>>>> This just seems to be a thing lftp does.
>>>>>> If the key isn't coming from ssh-agent, it always asks for a passphrase.
>>>>>> If the key doesn't have one, you can just hit enter (or type anything).
>>>>> OK, works. Can lftp or cygport be configured so that lftp does not ask for
>>>>> a password? Or to use sftp instead?
>>>> I don't know of any configuration for lftp to turn off that behaviour (which
>>>> is arguably a defect in lftp), but that's probably something you could
>>>> investigate for yourself.
>>>> I am not sure why lftp is used instead of sftp, possibly it is
>>>> insufficiently scriptable to do what cygport wants to do.
>>>>> Uploading the two Unicode packages, I got this response:
>>>>> ERROR: package '/sourceware/cygwin-staging/home/Thomas
>>>>> Wolff/noarch/release/unicode-cldr' is not in the package list
>>>>> ERROR: package '/sourceware/cygwin-staging/home/Thomas
>>>>> Wolff/noarch/release/unicode-cldr/unicode-cldr-emoji-annotation' is not in
>>>>> the package list
>>>>> SUMMARY: 2 ERROR(s)
>>>> Ah, right.
>>>> I've updated cygwin-pkg-maint and made the appropriate adjustment.
>>>> There still seems to be a problem with the form of the version number you've
>>>> chosen, however.
>>> Yes, calm complains about
>>> '-' in version
>>> but 36-1 is the version format used upstream. Do I need to convert it?
>> Looking at, I see it called 36.1
> Right. The download files are provided at
> where you can see release-36-1.
>> The fact that the upstream filename contains '36-1' alone doesn't seem
>> sufficient to grant an exception.
> I think I'll put something like REPOVER=${VERSION//./-} into the cygport file
> for the download then.
>>>> I am not quite clear how unicode-cldr replaces
>>>> unicode-cldr-emoji-annotation, if we have anything which requires it to
>>>> build, since it doesn't appear to provide the .pc file that did.
>>> Please elaborate. I do not see any .pc file in the previous package.
>>> The new package include /usr/share/unicode/cldr/common/annotations (which the
>>> previous one provided solely) and other subdirectories of
>>> /usr/share/unicode/cldr/common.
>> Maybe I am mistaken, but looking at the filelists in
>> package unicode-cldr-emoji-annotation contains
>> /usr/share/pkgconfig/cldr-emoji-annotation.pc
> I wasn't aware of that. Not sure, though, what it's good for. I'd prefer to go
> without it unless it's missed by someone.

It's used mainly for X Window and utility builds with CLDR, and it would be
better and easier just to keep it around with an updated version, if not in the
original upstream package.

Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.

More information about the Cygwin-apps mailing list