Blacklisting packages from installing

I’m currently running 10.10 with a package removed.

I’m concerned that when it comes time to upgrade, synaptic may well install that package again. Is there way to blacklist a package that works even through distribution upgrades?

In my case, the package is mono.

Here is Solutions:

We have many solutions to this problem, But we recommend you to use the first solution because it is tested & true solution that will 100% work for you.

Solution 1

The answer is simple:

Remove the packages you don’t want using apt-get, synaptic package manager or the Software Center.
open APT’s 01autoremove file by issuing the command

sudo -H gedit /etc/apt/apt.conf.d/01autoremove

Navigate to the bottom of the section titled Never-MarkAuto-Sections and add an entry to the section. In my case to block GRUB I entered grub.*;. The contents of the modified file is at the bottom of this page.

You will enter the package name or portion of package names, including using .* to mean any characters. In my case grub.* blocks all packages that start with the word grub.

When you next open the update utility it will not show the option to upgrade or update the software that you chose to block.

My /etc/apt/apt.conf.d/01autoremove file:

 NeverAutoRemove  {
  "^linux-image.*";   "^linux-restricted-modules.*";
 {   "metapackages";

Solution 2

You could make your own mono package that is empty and set the version crazy high.

Sometimes this creates dep-solving issues though

Solution 3

I’m not sure what APT::NeverMarkAuto really does, whether it stops it from being considered for dependency resolution.

edit /etc/apt/preferences and put in:

Package: mono
Pin: version *
Pin-Priority: -10

(warning, I didn’t test this. Even if it does work, this might stop you from even installing it manually.)

More docs in the apt_preferences(5) man page.

Comment lines by prefixing with Explanation:. The Package: field doesn’t support wildcards; Package: * used in some examples is a special case.

I haven’t used preferences since I stopped trying to mix some packages from intrepid-backports with other packages from karmic (before it was released), or from Debian repos or from Medibuntu vs. Ubuntu-shipped. Pinning with preferences could make apt / aptitude /etc. decide that some version other than the highest version-numbered version was the best one to install, or that it didn’t need upgrading.

Anyway, I just use aptitude for all my package management, it’s SO much better than any of the simplistic GUIs I’ve seen come up on liveCDs or default installs. After marking something to be installed, if there’s a crapload of stuff it’s going to pull in via recommends:, I go and unmark that stuff before giving the final go-ahead.

Note: Use and implement solution 1 because this method fully tested our system.
Thank you 🙂

All methods was sourced from or, is licensed under cc by-sa 2.5, cc by-sa 3.0 and cc by-sa 4.0

Leave a Reply