From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 51135 invoked by alias); 18 Feb 2016 15:55:11 -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 51126 invoked by uid 89); 18 Feb 2016 15:55:11 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.3 required=5.0 tests=AWL,BAYES_20,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.2 spammy=H*MI:sk:56C5DF8, H*f:sk:56C5DF8, H*i:sk:56C5DF8, installeddb X-HELO: sender153-mail.zoho.com Received: from sender153-mail.zoho.com (HELO sender153-mail.zoho.com) (74.201.84.153) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-SHA encrypted) ESMTPS; Thu, 18 Feb 2016 15:55:09 +0000 Received: from [192.168.11.171] (rrcs-98-103-118-100.central.biz.rr.com [98.103.118.100]) by mx.zohomail.com with SMTPS id 1455810907233633.9703196940188; Thu, 18 Feb 2016 07:55:07 -0800 (PST) Subject: Re: Freeze package To: cygwin@cygwin.com References: <56C5D679.1010604@zoho.com> <56C5DE9E.4020103@gmail.com> <56C5DF85.4060104@zoho.com> From: Byron Boulton Message-ID: <56C5E959.1030406@zoho.com> Date: Thu, 18 Feb 2016 15:55:00 -0000 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1 MIME-Version: 1.0 In-Reply-To: <56C5DF85.4060104@zoho.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Zoho-Virus-Status: 1 X-IsSubscribed: yes X-SW-Source: 2016-02/txt/msg00291.txt.bz2 On 2/18/2016 10:13 AM, Byron Boulton wrote: > On 2/18/2016 10:09 AM, Marco Atzeri wrote: >> On 18/02/2016 15:34, Byron Boulton wrote: >>> Is there a way to freeze a cygwin package to prevent upgrade? >>> >>> Byron >>> >> >> only manually selecting skip for that specifically package. >> >> Why ? >> >> >> >> -- >> 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 >> > There is a very annoying small bug in the hamster package from > cygwin-ports. It's a very simple fix in the python code, but I was > thinking I would freeze the package to keep from overwriting it. I've > had bad luck with installing from source on my linux machines, so I > don't have high hopes for installing it from source on cygwin. I realize > it's a bad idea to manually edit files that are under the control of the > package manager. Freezing the package is just a workaround. > > Byron > > > -- > 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 > On 2/18/2016 10:34 AM, Achim Gratz wrote: > 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. Thanks for your info on the installed.db. As I replied to another mailing list member, I recognize the problems of editing files under the package manager's control. If installing from source weren't buggy (that I *should* report upstream) I would do that rather than edit the files installed by cygwin. The bug is fixed upstream, but only in a release candidate. It would be nice if cygwin had a real way to freeze a package. For example, when you freeze a package in Arch Linux, everytime you update your packages it prints a warning listing packages you have frozen. This way, each time you run an update you see the warning and can consider again if you need to have the packages frozen, or if something starts acting funny you can ask yourself, "I wonder if the problem is caused by these packages I have frozen". Byron -- 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