From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.133]) by sourceware.org (Postfix) with ESMTPS id EEEA1385E006 for ; Fri, 27 Mar 2020 17:31:07 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org EEEA1385E006 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=towo.net Authentication-Results: sourceware.org; spf=none smtp.mailfrom=towo@towo.net Received: from [192.168.178.45] ([95.90.246.248]) by mrelayeu.kundenserver.de (mreue012 [212.227.15.167]) with ESMTPSA (Nemesis) id 1M1JJC-1jF7vm13rm-002kyX; Fri, 27 Mar 2020 18:31:04 +0100 Subject: Re: cygport upload To: Jon Turney , "cygwin-apps@cygwin.com" References: <3b855b82-cf0b-496c-c7b0-beb23c29b966@towo.net> <8c872bcb-3541-4016-094e-df7b8231513c@towo.net> <555ac0bb-0984-f320-c240-df9e165ca062@dronecode.org.uk> <5b590a04-3dbe-4210-a3da-93f58fc48621@dronecode.org.uk> From: Thomas Wolff X-Tagtoolbar-Keys: D20200327183104771 Message-ID: Date: Fri, 27 Mar 2020 18:31:04 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.6.0 MIME-Version: 1.0 In-Reply-To: <5b590a04-3dbe-4210-a3da-93f58fc48621@dronecode.org.uk> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K1:5PvYv9ZEMzFxXfOAL6yRTji1ec2wXJQwYO8imDLNX+QrrJLD85n dZ+yMU8w5Uz+A5AR9fCFB6y7eI2qzXvW6ePhnkhE4bPD1W+JD4eDJrwpEVNrewTf+lUpPVZ ePyIsnIXRk/lAw3rqfFvoqFj+Ei5IoZwMyfKgxVL8DUoBbMtV2niZq85ZOa3qv6J9WAVk4C SXNbcSA5IXpDvJZMv3+8w== X-UI-Out-Filterresults: notjunk:1;V03:K0:XHtueKv4t2c=:34RXPsDShnEznLF+6ZPB6t wGAIPhlhHRDzKJGMEEj10UUCeiWkgcFTxSpd3l9QB1fC3ll9K+/5VQzROchs5dRODdXzaXcLS seWSIJhF28vHDSJsNjhrftPGyLYGLMzrAHf3gvlQoc4r7Mt2TeRV39CGLKQ5F79UPKF5QV/Xe 5cxIEaIr0zp99tN6p3NjU2+sdTaEa6dpuG2T18i9js14VNzkW2Ao7E8dN+VUgb2Ll6Xyiqjaf qMrNSvHcBhY8EnLwSEWBzKG2vuE52e4SnIAWZ2rmMAUMBWy/moNqnzny/k5fgr/pUUh9CClKF +HPUvld8PKGxkBfStF935vqaHnY1WO1m//PVPqtqjSrbPK8HaCSzIyQGibN1LtrqfF9VO5+Ha s+5Id4CvmV1hULHw2qCET1mQjv/5kXnae9fqDlCwCY7DZsr9dZzmSeOriKv6jCdAV5SEQaV0E IZ3ks8Ovd3apLdAmdXlCABuwWcvghys9EN/0MtTZvYTJk5KDW1M8mfpnCUFml9cconWb4phmB rsHJZG6BpEAqjIf7F6iDSJFgoTqoBjUIxY9nv+Cm8z6H3BdMAJbrqaA9L2g0IP8XU31BEyryA hyhq/mGoTrF2fJbv9W6vuePWTYwMorklZV4unfRuAXoTRekhFA/Q3ictNuk4zCO7F4hgrvi1v V6xMq68cOpqGRLm0MA3izCvHlQg0geiI//4t/xKgxuJ+1hZKFriZrkInnkH7K2acYGOJq8Xso dPoCZdAnjN3QfVuknfVPzKAq/DJtvZrmfWxZw6PQZvb1OY4m25db43HVYLdoNk9yuOn+WThMM 9zGV9uNu+Puw2bFppTkK0/+2NkmRbzxo2Q74UW/4DFaajuW+pA= X-Spam-Status: No, score=1.7 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, KAM_LAZY_DOMAIN_SECURITY, RCVD_IN_BARRACUDACENTRAL, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_NONE, TXREP autolearn=no autolearn_force=no version=3.4.2 X-Spam-Level: * X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: cygwin-apps@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Cygwin package maintainer discussion list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Mar 2020 17:31:12 -0000 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