public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Thomas Wolff <towo@towo.net>
To: Jon Turney <jon.turney@dronecode.org.uk>,
	"cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: cygport upload
Date: Fri, 27 Mar 2020 18:31:04 +0100	[thread overview]
Message-ID: <b81f6e6b-774a-065c-e28e-917cc6c0f9a0@towo.net> (raw)
In-Reply-To: <5b590a04-3dbe-4210-a3da-93f58fc48621@dronecode.org.uk>

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 http://cldr.unicode.org/index/download, I see it called 36.1
Right. The download files are provided at 
https://github.com/unicode-org/cldr 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 
> https://cygwin.com/packages/summary/unicode-cldr-emoji-annotation.html, 
> 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.
Thomas

  reply	other threads:[~2020-03-27 17:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-27 10:17 Thomas Wolff
2020-03-27 12:21 ` Jon Turney
2020-03-27 14:35   ` Thomas Wolff
2020-03-27 15:41     ` Jon Turney
2020-03-27 16:15       ` Thomas Wolff
2020-03-27 16:27         ` Jon Turney
2020-03-27 17:31           ` Thomas Wolff [this message]
2020-03-27 18:25             ` CLDR pkg-config (was: cygport upload) Brian Inglis
2020-03-29 12:08       ` cygport upload Andrew Schulman

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=b81f6e6b-774a-065c-e28e-917cc6c0f9a0@towo.net \
    --to=towo@towo.net \
    --cc=cygwin-apps@cygwin.com \
    --cc=jon.turney@dronecode.org.uk \
    /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).