X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=GzTpp+XgKM+UdMDG
	76mXb2la65mB6mD9o+Kf4IeKVew+EGjSH8c5RxrXr5bOjUrrIITqJkBbUxqT5sHo
	tc1Bg8MyLZI0ZsWqZt3hi4uxFlSGZPkhxbx/o7hXYKtYC5LYyoJA39nql3VzV3dG
	l4g93RpJfnXbb22CnFokUEH02xw=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=5v3doZEL7g3Agf+Ktq/MXc
	uwdZI=; b=x/J0/ChteqbGC54DvC9A6tMVyGFr7341Wfn0d+g/Htl7ukWGkWgd7C
	mBPIAPBgUvmD4KW46uhqoiu6O9yr2WpXHl3XlTBHhTmwRNIU1GxaTvdihpKceF29
	Q2wmi8lU3pJMxlKn6HUQTHCwfDGr8bV6ykZaYV8wT1au2YhVBGjN0=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
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
Subject:	Re: Freeze package
To:	cygwin AT cygwin DOT com
References:	<56C5D679 DOT 1010604 AT zoho DOT com> <56C5DE9E DOT 4020103 AT gmail DOT com> <56C5DF85 DOT 4060104 AT zoho DOT com>
From:	Byron Boulton <daytonb AT zoho DOT com>
Message-ID:	<56C5E959.1030406@zoho.com>
Date:	Thu, 18 Feb 2016 10:55:05 -0500
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>
X-Zoho-Virus-Status:	1
X-IsSubscribed:	yes

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 <daytonb <at> 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

- Raw text -