From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp-out-so.shaw.ca (smtp-out-so.shaw.ca [64.59.136.137]) by sourceware.org (Postfix) with ESMTPS id D9132385803C for ; Fri, 28 May 2021 23:18:58 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org D9132385803C Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=SystematicSw.ab.ca Authentication-Results: sourceware.org; spf=none smtp.mailfrom=brian.inglis@systematicsw.ab.ca Received: from [192.168.1.104] ([68.147.0.90]) by shaw.ca with ESMTP id mlkmlvIMX7YjPmlknlvV9g; Fri, 28 May 2021 17:18:57 -0600 X-Authority-Analysis: v=2.4 cv=fPVaYbWe c=1 sm=1 tr=0 ts=60b17a61 a=T+ovY1NZ+FAi/xYICV7Bgg==:117 a=T+ovY1NZ+FAi/xYICV7Bgg==:17 a=IkcTkHD0fZMA:10 a=8AHkEIZyAAAA:8 a=yBR9Qs6oAAAA:8 a=94nOnFI1EgyDtX4ev68A:9 a=QEXdDO2ut3YA:10 a=7C5qix1daMSKwVux_nGC:22 Reply-To: cygwin-apps@cygwin.com To: cygwin-apps@cygwin.com References: <59806a9c-a0f4-1868-e763-4dca35e6e3a2@gmail.com> From: Brian Inglis Organization: Systematic Software Subject: Re: [ITA] nghttp2, mingw64-{x86_64,i686}-nghttp2 Message-ID: <1e51a907-b7cb-3961-db13-3f4b74a8ddff@SystematicSw.ab.ca> Date: Fri, 28 May 2021 17:18:56 -0600 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.10.2 MIME-Version: 1.0 In-Reply-To: <59806a9c-a0f4-1868-e763-4dca35e6e3a2@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-CA Content-Transfer-Encoding: 8bit X-CMAE-Envelope: MS4xfDPrsh6aCTXn1vJVZhk5B+f/YGnmRLbwCJktmOMsFD0tOaeFuxlBMz3Vz0X/PZXsm9Kg1oB2aPv+LFSM6KSxBcHlUeuqLkPSAS06LlLkNFc1t8JWtFVb FNA/nEmEuQpxxzE1s2COgK2FddWKfV29Q/VlsSwfijKPlKRwCb3wVs9Kb5/s100JzN3XL8x/KlyoDo01TstgbAPln8kU+Xt4vbA= X-Spam-Status: No, score=-3487.7 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, KAM_LAZY_DOMAIN_SECURITY, KAM_NUMSUBJECT, NICE_REPLY_A, RCVD_IN_BARRACUDACENTRAL, RCVD_IN_DNSWL_LOW, SPF_HELO_NONE, SPF_NONE, TXREP autolearn=no autolearn_force=no version=3.4.2 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-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 May 2021 23:19:00 -0000 On 2021-05-28 12:33, Marco Atzeri via Cygwin-apps wrote: > On 28.05.2021 19:06, Brian Inglis wrote: >> Noticing some more libraries used by curl and wget/2 that were outdated >> and orphaned, I decided to take a look at building updates and would now >> like to adopt them. >> >> The list below shows the distributed packages, links to the Git Cygwin >> Package repos (see playground branches), Appveyor CI builds and logs >> for those who prefer looking at those, and links to Google drive folders >> with all the usual files and archives for others. >> >> I have issues building python2/27/3/36 modules, and/or which to obsolete. > > you can drop all. > Python2.7 is dead upstream and Python3.6 will be at end of 2021 > > https://www.python.org/downloads/ I would appreciate advice on how to structure obsoleting the existing packages: python-nghttp2 python2-nghttp2 python27-nghttp2 python3-nghttp2 python36-nghttp2 given replacement packages python37-nghttp2 and python38-nghttp2. I can define all those as empty packages for the proposed release, but which should obsolete what to get the appropriate replacements? Should I define the following packages e.g.: python2-nghttp2 dummy obsoletes python-nghttp2 python27-nghttp2 dummy obsoletes python2-nghttp2 python3-nghttp2 dummy obsoletes python27-nghttp2 python36-nghttp2 dummy obsoletes python3-nghttp2 python37-nghttp2 real obsoletes python36-nghttp2 python38-nghttp2 real stands alone for now? > Changed maintainership to you (only for them this time) Thank you very much - appreciate that! Repology.org dropped the extraneous maintainership adds/removes ;^> -- 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. [Data in binary units and prefixes, physical quantities in SI.]