DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:to:from:subject:date:message-id:references
	:mime-version:content-type:content-transfer-encoding; q=dns; s=
	default; b=pCW85Qo3SuPI9bAPNPBuJUGjPG1mcmnreVARXhS6wuNhJxbfvXR5E
	qoVeGc0iyeaurdaI+ugEeMqbnJ/3xQsw3o3K2swze/HD7ZBvwl69gNFpsf6FcP6C
	mcYB1ba4ej3ZfuCus2OJMMaq6qsvQeNfMD3mLVcYkXLYMWgvQDXvXI=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
To: cygwin@cygwin.com
From: Achim Gratz <Stromeko@NexGo.DE>
Subject: Re: Freeze package
Date: Thu, 18 Feb 2016 15:34:02 +0000 (UTC)
Lines: 17
Message-ID: <loom.20160218T162803-534@post.gmane.org>
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/)

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.


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