From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from re-prd-fep-041.btinternet.com (mailomta20-re.btinternet.com [213.120.69.113]) by sourceware.org (Postfix) with ESMTPS id 308BB385C320 for ; Mon, 11 Apr 2022 13:50:21 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 308BB385C320 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=dronecode.org.uk Authentication-Results: sourceware.org; spf=none smtp.mailfrom=dronecode.org.uk Received: from re-prd-rgout-001.btmx-prd.synchronoss.net ([10.2.54.4]) by re-prd-fep-041.btinternet.com with ESMTP id <20220411135019.HUAA24157.re-prd-fep-041.btinternet.com@re-prd-rgout-001.btmx-prd.synchronoss.net>; Mon, 11 Apr 2022 14:50:19 +0100 Authentication-Results: btinternet.com; auth=pass (PLAIN) smtp.auth=jonturney@btinternet.com; bimi=skipped X-SNCR-Rigid: 613A8CC31DC37FF5 X-Originating-IP: [86.139.167.41] X-OWM-Source-IP: 86.139.167.41 (GB) X-OWM-Env-Sender: jonturney@btinternet.com X-VadeSecure-score: verdict=clean score=0/300, class=clean X-RazorGate-Vade: gggruggvucftvghtrhhoucdtuddrgedvvddrudekiedgjedtucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuueftkffvkffujffvgffngfevqffopdfqfgfvnecuuegrihhlohhuthemuceftddunecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjughrpefkffggfgfuvfhfhfgjtgfgsehtjeertddtfeejnecuhfhrohhmpeflohhnucfvuhhrnhgvhicuoehjohhnrdhtuhhrnhgvhiesughrohhnvggtohguvgdrohhrghdruhhkqeenucggtffrrghtthgvrhhnpeehudeuveeujeeujeegueefhedttdekvedtudeileefteetfeefjeejudekfefggfenucffohhmrghinheptgihghifihhnrdgtohhmnecukfhppeekiedrudefledrudeijedrgedunecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehhvghloheplgduledvrdduieekrddurddutdehngdpihhnvghtpeekiedrudefledrudeijedrgedupdhmrghilhhfrhhomhepjhhonhdrthhurhhnvgihsegurhhonhgvtghouggvrdhorhhgrdhukhdpnhgspghrtghpthhtohepvddprhgtphhtthhopegthihgfihinhdqrghpphhssegthihgfihinhdrtghomhdprhgtphhtthhopehstghhuhhlmhgrnhdrrghnughrvgifsegvphgrrdhgohhv X-RazorGate-Vade-Verdict: clean 0 X-RazorGate-Vade-Classification: clean Received: from [192.168.1.105] (86.139.167.41) by re-prd-rgout-001.btmx-prd.synchronoss.net (5.8.716.04) (authenticated as jonturney@btinternet.com) id 613A8CC31DC37FF5; Mon, 11 Apr 2022 14:50:19 +0100 Message-ID: <9a47b168-d3c1-ab9a-6bd2-6c4b9eef00ea@dronecode.org.uk> Date: Mon, 11 Apr 2022 14:49:51 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.7.0 Subject: Re: replacing a previous package verson Content-Language: en-GB To: "cygwin-apps@cygwin.com" , "Schulman, Andrew" References: From: Jon Turney In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1194.2 required=5.0 tests=BAYES_00, FORGED_SPF_HELO, KAM_DMARC_STATUS, KAM_LAZY_DOMAIN_SECURITY, NICE_REPLY_A, RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H5, RCVD_IN_MSPIKE_WL, SPF_HELO_PASS, SPF_NONE, TXREP, T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) 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: Mon, 11 Apr 2022 13:50:23 -0000 On 11/04/2022 14:02, Andrew Schulman via Cygwin-apps wrote: > After all this time I feel that I should know the answer to this, but here > goes. > > I have fish-3.4.1-1, a bugfix release. I want it to replace fish-3.4.0-1, > leaving fish-3.3.1-1 as the previous release. > > What's the best way to do this? Should I create override.hint, with > keep: 3.3.1-1 This alone means 'keep 3.3.1-1 as well as anything else you would keep'. Since that seems to be what you really want ('keep previous major version around '), I'd suggest just doing that. If you really feel the presence of 3.4.0-1 is unhelpful and want to remove it, you can use the 'deleting' instructions at [1] to remove 3.4.0-1. You can create the dash-prefixed files in cygport's staging directory (${PN}-${PVR}.${ARCH}/dist/) before a 'cygport upload', if you want to make both changes at once. Since that mechanism is not terribly easy to use, it's also ok to ask here for someone with shell access to remove the files for you. (The script which does this is named 'vault', so this is sometimes referred to as 'vaulting'). But I'd suggest just focusing on specifying what you want to keep, and allow calm to manage cleaning up stuff that's surplus to requirements for you. [1] https://cygwin.com/package-upload.html#deleting > replace-versions: 3.4.0-1 This isn't what you want. 'replace-versions' is an instruction to setup, that those versions should always be replaced, even by non-superseding (lower) versions. This is to intended to handle the case when a broken package is released, and we want to withdraw that package without releasing a later version, and downgrade it anywhere it's installed. That's the idea the final paragraph after [2] is meant to communicate. [2] https://cygwin.com/packaging-hint-files.html#override.hint > ? This seems as though it might be right, but one question I have is, will > override.hint persist in future releases unless I replace it? Yes, override.hint persists until changed or removed (but note that it's contents don't currently apply recursively).