From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21150 invoked by alias); 18 Feb 2016 15:34:17 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 20947 invoked by uid 89); 18 Feb 2016 15:34:16 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=0.8 required=5.0 tests=AWL,BAYES_00,FSL_HELO_BARE_IP_2,RCVD_IN_DNSWL_LOW,RCVD_NUMERIC_HELO,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=no version=3.3.2 spammy=Hx-languages-length:715, road X-HELO: plane.gmane.org Received: from plane.gmane.org (HELO plane.gmane.org) (80.91.229.3) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-SHA encrypted) ESMTPS; Thu, 18 Feb 2016 15:34:15 +0000 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1aWQap-00083V-Hi for cygwin@cygwin.com; Thu, 18 Feb 2016 16:34:11 +0100 Received: from 217.10.52.10 ([217.10.52.10]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 18 Feb 2016 16:34:11 +0100 Received: from Stromeko by 217.10.52.10 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 18 Feb 2016 16:34:11 +0100 To: cygwin@cygwin.com From: Achim Gratz Subject: Re: Freeze package Date: Thu, 18 Feb 2016 15:34:00 -0000 Message-ID: References: <56C5D679.1010604@zoho.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit User-Agent: Loom/3.14 (http://gmane.org/) X-IsSubscribed: yes X-SW-Source: 2016-02/txt/msg00290.txt.bz2 Byron Boulton zoho.com> writes: > Is there a way to freeze a cygwin package to prevent upgrade? This is a "if you have to ask, you shouldn't be doing it" type of question. Keeping that in mind, you can edit /etc/setup/installed.db and give any package a high enough version number so that setup thinks there's a more recent version installed than what is available in the repo. You have to remember that yourself or you'll start wondering a few months down the road why things break in mysterious ways, though. But you should really report the problem to the maintainer so that it can be solved at its root, rather than trying to point-fix a local installation. Regards, Achim. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple