X-Recipient: archive-cygwin AT delorie DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org DDCE038582B3 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1706708383; bh=ihvJwlhmjoHVrVsIJSMb0cJ1M5k9wb2C5Q5LcrBekKw=; h=Date:Subject:To:References:Cc:In-Reply-To:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From:Reply-To:From; b=sk49ISrFho8iWgP3aWqNxcNUd8ZOnPtcNXTzpuqUsKBmAjcxHpBjLnarqSflo+oCw 3NAT7pnEGNg1oq7eXaaYy3QBoG8GHeDiwKgzhJLc0t3HSsCB/Sm/lXiQ+qQx8SvkxX goajnUUv79reaqwPvxUaGJTGUs7KNODseWWMpsRU= X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 380B33858401 ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 380B33858401 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1706708363; cv=none; b=oV5smPuApCDqDoWrF34mHnG88spAAsWIBVpBdv1Q9brrg2sIAN8qM7QpE+7lxctgxVl9RHOQM8pM4cHNrKF0chTXVfDmi6xUbBxmdHCHdlYc5QHnKXScnHBaVzsou8zWX+8zcXKXfsh/1U2yOeVfzkNvt9Qk6YnTfVpy2s9BPVk= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1706708363; c=relaxed/simple; bh=jDmsRYyvX+B5OnVD7Ak3qFiRVz3BPR1BROm9u+Hkf48=; h=Message-ID:Date:MIME-Version:Subject:To:From; b=LYdktKeJ83NEjU7kjXdV8vtLnLuVk1VEgyC4paV/PaRpe1oKa5cCn9v1HwfDbZOC1Dp+UwFNRFrNymPqIdXLH43HJdlFl/OyUUZN5sRQ6zBD1cxx6gZQNnUr7HLfX2jp0Ymcslq5dvKjZO69HsImMBerNJ13sExSi9N7892K5Hg= ARC-Authentication-Results: i=1; server2.sourceware.org X-SNCR-Rigid: 6577B87C06467372 X-Originating-IP: [86.140.193.68] X-OWM-Source-IP: 86.140.193.68 X-OWM-Env-Sender: jon DOT turney AT dronecode DOT org DOT uk X-VadeSecure-score: verdict=clean score=0/300, class=clean X-RazorGate-Vade: gggruggvucftvghtrhhoucdtuddrgedvkedrfedtledghedvucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuueftkffvkffujffvgffngfevqffopdfqfgfvnecuuegrihhlohhuthemuceftddunecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjughrpefkffggfgfuvfhfhfevjggtgfesthejredttddvjeenucfhrhhomheplfhonhcuvfhurhhnvgihuceojhhonhdrthhurhhnvgihsegurhhonhgvtghouggvrdhorhhgrdhukheqnecuggftrfgrthhtvghrnhepheetveeviedtgffgvdefhefgheeiheejuedtjefgheehgfejffdtueeujefhtdefnecuffhomhgrihhnpehrvghpohhlohhghidrohhrghenucfkphepkeeirddugedtrdduleefrdeikeenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhephhgvlhhopegludelvddrudeikedruddruddtlegnpdhinhgvthepkeeirddugedtrdduleefrdeikedpmhgrihhlfhhrohhmpehjohhnrdhtuhhrnhgvhiesughrohhnvggtohguvgdrohhrghdruhhkpdhnsggprhgtphhtthhopedupdhrtghpthhtoheptgihghifihhnsegthihgfihinhdrtghomhdprhgvvhfkrfephhhoshhtkeeiqddugedtqdduleefqdeikedrrhgrnhhgvgekiedqudegtddrsghttggvnhhtrhgrlhhplhhushdrtghomhdprghuthhhpghushgvrhepjhhonhhtuhhrnhgvhiessghtihhnthgvrhhnvghtrdgtohhmpdhgvghokffrpefiuedp offvtefjohhstheprhgvqdhprhguqdhrghhouhhtqddttdeg X-RazorGate-Vade-Verdict: clean 0 X-RazorGate-Vade-Classification: clean Message-ID: Date: Wed, 31 Jan 2024 13:39:18 +0000 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Tmux crashes on copy Content-Language: en-GB To: Brian Inglis via Cygwin References: <20240118 DOT 163759 DOT 544696899534989142 DOT yasu AT utahime DOT org> <20240118172431 DOT 8308e15fc705d96fc39410d7 AT nifty DOT ne DOT jp> <35eb821c-5270-406c-985f-b6107b43be9a AT SystematicSW DOT ab DOT ca> <87bk9eie5x.fsf@> <2016e573-7282-4fa3-bee4-e54d36ac0c2d AT SystematicSW DOT ab DOT ca> Cc: cygwin AT cygwin DOT com In-Reply-To: <2016e573-7282-4fa3-bee4-e54d36ac0c2d@SystematicSW.ab.ca> X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00, JMQ_SPF_NEUTRAL, KAM_DMARC_STATUS, RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H4, RCVD_IN_MSPIKE_WL, SPF_HELO_PASS, SPF_PASS, 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.30 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Jon Turney via Cygwin Reply-To: Jon Turney 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 21/01/2024 22:13, Brian Inglis via Cygwin wrote: > On 2024-01-21 14:12, ASSI via Cygwin wrote: >> Brian Inglis via Cygwin writes: >>> Previous maintainer added some artificial single digit release >>> prefixes (in a few packages), but we decided to drop those and use the >>> release date directly as used in the package. > >> That is the upstream versioning scheme for patch releases or beta >> versions, which can't be used directly on Cygwin without losing the >> release part of the package version. >> You might want to go for something like 6.4+20240120-1 instead. I'm not sure that's the right solution Ideally, V should be the upstream version label. If upstream really is making multiple releases called '6.4', which we're supposed to distinguish by some other means, then there aren't really any good answers... See the mess that is https://repology.org/project/ncurses/information, where everyone makes up there own scheme. > Good point, but I figured we could add the suffix .1 or something if we > could not get a change merged upstream: the snapshots are weekly or > better in ncurses, although others not so often, and I have no idea how > they decide when to release a new GNU version 6.5? > > What happens if we change versioning from 6.4-yyyymmdd to 6.4+yyyymmdd-1? -- 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