Your details

[Ret]

Title: Horoscope Unknown



 
Thanks for your email. We don't monitor this email address, 

so this is an automatic response, but here are some tips for 

getting the most out of your relationship with Keen.


If you'd like to change your email address or adjust your subscription or 

horoscope preferences (e.g. sign, frequency of delivery, etc.), 

please visit your subscription update page at:

http://www.keen.com/registration/u.asp?id=0&ema= 


If you have any problems, questions, or requests, review the Keen Help section at:

http://www.keen.com/documents/help/menu.asp


Still have questions? Contact us at:

http://www.keen.com/documents/help/customersupport.asp 


Thanks, and we look forward to seeing you again at Keen!  

holding a package against upgrades

[United States Ret.]

I have been using sid and do not want iceweasel 29.

I have decided to revert to iceweasel 24.5 and have now put that on hold
(=) in dselect and worry that will override my decision and upgrade anyway.

Is there a better way to make sure apt never upgrades from iceweasel 24.5
like pin or priority or something. Here is my current apt.conf:

APT {
Install-Recommends "false";
Install-Suggests "false";
};

Re: holding a package against upgrades SOLVED

[United States Ret.]

The Wanderer replied:

>A package version pin is probably the way to go on this.
>
>Here's what I have in /etc/apt/preferences:
>
>
>Package: iceweasel
>Pin: version 24.*
>Pin-Priority: 1001
>
>
>I used something similar with 17.* until I was ready to upgrade (having
>tested first in a VM to make sure I knew how to fix anything that would
>break), and I expect to do it again with 31.* when the time comes.
>
>I used to use holds ("echo 'NAME hold' | dpkg --set-selections"), but
>that led to held-packages dependency breakage when dist-upgrading
>sometimes. I find that package version pinning works much better.


OK I can now to work on /etc/apt/preferences not apt.conf. Thanks.