X-Recipient: archive-cygwin AT delorie DOT com X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 26EDA3857432 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=SystematicSw.ab.ca Authentication-Results: sourceware.org; spf=none smtp.mailfrom=systematicsw.ab.ca X-Authority-Analysis: v=2.4 cv=Z8n/oVdA c=1 sm=1 tr=0 ts=628a55c5 a=oHm12aVswOWz6TMtn9zYKg==:117 a=oHm12aVswOWz6TMtn9zYKg==:17 a=IkcTkHD0fZMA:10 a=94nOnFI1EgyDtX4ev68A:9 a=QEXdDO2ut3YA:10 Message-ID: <628ba81b-a07b-9ee1-05cb-2dcdadc43d3d@SystematicSw.ab.ca> Date: Sun, 22 May 2022 09:24:53 -0600 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.9.0 From: Brian Inglis Subject: Re: Updated: coreutils 8.32 To: cygwin AT cygwin DOT com References: Content-Language: en-CA Organization: Systematic Software In-Reply-To: X-CMAE-Envelope: MS4xfLdIZnuNAZ7fa7RxtYI1MMsXj3v1EeQ/9KzkFHIuIO670FrbNGF4n5vj33jMSGjY1Hbn59rzxAsLAQL5fgnDXnw+6B3qK7FEE7GsanAByyHvakFPq71g fPekmCl0UEoU4aqCVRXYIrxUTg+fVuhI+eJ+uLWBFI+sabMlz+vaEVJ0CKqxlUoy9pg+GzwTGZ6E1vLNK1Aab2OR+TS3k2UZpEs= X-Spam-Status: No, score=-1164.2 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, KAM_LAZY_DOMAIN_SECURITY, KAM_NUMSUBJECT, NICE_REPLY_A, SPF_HELO_NONE, SPF_NONE, TXREP, T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org X-BeenThere: cygwin AT cygwin DOT com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: cygwin AT cygwin DOT com Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Errors-To: cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com Sender: "Cygwin" On 2022-05-21 23:54, Fergus Daly wrote: > I've just updated coreutils. I don't use test versions. So I have > $ uname --version > uname (GNU coreutils) 8.32 > Packaged by Cygwin (8.32-1) > Now on 32-bit Cygwin I get > $ uname -s > CYGWIN_NT-10.0-19044-WOW64 [ previously CYGWIN_NT-10.0-WOW ] > And on 64-bit Cygwin I get > $ uname -s > CYGWIN_NT-10.0-19044 [ previously CYGWIN_NT-10.0 ] > Packaging error? That build is a value we have said for years we would make visible for easier determination of Windows version used (21H2 for you and I), previously only visible in /proc/version: $ head /proc/version CYGWIN_NT-10.0-19044 version 3.3.5-341.x86_64 (corinna AT calimero) (gcc version 11.2.0 20210728 (Fedora Cygwin 11.2.0-2) (GCC) ) 2022-05-13 12:27 UTC What products or processes does it affect negatively, and are there arguments for suppression, other than backward compatibility? -- 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.] -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple