Important information
-- Information on torrent hosting changes
-- Information on MX15/16 GPG Keys
-- Spectre and Meltdown vulnerabilities

-- Introducing our new Website
-- MX Linux on social media: here

Current releases
-- MX-18.1 Point Release release info here
-- Migration Information to MX-18 here
-- antiX-17.4 release info here

New users
-- Please read this first, and don't forget to add system and hardware information to posts!
-- Here are the Forum Rules

How to refuse new package?

Help for Current Versions of MX
User avatar
Forum Regular
Forum Regular
Posts: 314
Joined: Sat Mar 31, 2018 6:39 pm

Re: How to refuse new package?


Post by rich » Fri Jun 08, 2018 11:46 am

fehlix wrote:
Fri Jun 08, 2018 11:42 am
Pinning or "hold a package" is certainly not recommended
for mail-clients or web-browsers as one would not get any security fixes.
Pinning shall be regarded as a temp solution to keep a non-security crititcal
application runninng until a better working upgraded package is provided.
Oh, absolutely. I'm not saying it's always a good idea, just that it can be done. I personally don't use pinning whatsoever.

Looks like you could, if you ever really need to, pin a package to "-1" priority to block it's installation. For example,

Code: Select all

root@mx17:/home/rich/Documents# cat /etc/apt/preferences
Package: feh
Pin: release *
Pin-Priority: -1

root@mx17:/home/rich/Documents# sudo apt install feh
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Package feh is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'feh' has no installation candidate
This would block installation of the package in question along with anything that depended on it.
I read a book about Narcissism
And I loved it cuz
It was all about me.

Post Reply

Return to “MX Help”