public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Byron Boulton <daytonb@zoho.com>
To: cygwin@cygwin.com
Subject: Re: Freeze package
Date: Thu, 18 Feb 2016 15:13:00 -0000	[thread overview]
Message-ID: <56C5DF85.4060104@zoho.com> (raw)
In-Reply-To: <56C5DE9E.4020103@gmail.com>

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

  reply	other threads:[~2016-02-18 15:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-18 14:34 Byron Boulton
2016-02-18 15:09 ` Marco Atzeri
2016-02-18 15:13   ` Byron Boulton [this message]
2016-02-18 15:55     ` Byron Boulton
2016-02-18 15:34 ` Achim Gratz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=56C5DF85.4060104@zoho.com \
    --to=daytonb@zoho.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).