{"id":48938,"date":"2025-05-20T14:48:30","date_gmt":"2025-05-20T14:48:30","guid":{"rendered":"https:\/\/ubuntuhandbook.org\/?p=48938"},"modified":"2025-05-20T14:50:05","modified_gmt":"2025-05-20T14:50:05","slug":"apt-3-1-option-exclude-app-repository","status":"publish","type":"post","link":"https:\/\/ubuntuhandbook.org\/index.php\/2025\/05\/apt-3-1-option-exclude-app-repository\/","title":{"rendered":"Apt 3.1 Added New Option to Exclude App Packages from A Repository"},"content":{"rendered":"

\"\"<\/a><\/p>\n

apt, the default command line package manager for Debian and Ubuntu based Linux Distributions, released new version 3.1.0 on Monday.<\/p>\n

As you may know, apt 3.0 introduced new package dependency resolver with more efficient and clean output. Now, the resolver 3 is enabled by default in the new 3.1 release<\/b>.<\/p>\n

\"\"<\/a><\/p>\n

<\/p>\n

As you see in the screenshot above, it’s enabled for both apt<\/code> and apt-get<\/code> by the rules in the 01-vendor-ubuntu<\/code> configuration file for Ubuntu, though Ubuntu 25.10 has already enabled this feature for current default apt 3.0.<\/p>\n

why and why-not sub-commands<\/h3>\n

Similar to aptitude<\/code>, apt<\/code> now has new why<\/code> and why-not<\/code> sub-commands<\/b>, allowing to find out why a certain package was installed, or why a package is not installable. And, here’s the description about them in the man page:<\/p>\n

These commands print the reasoning path from the solver. They are similar to the equivalent aptitude commands for many use cases, but are different in that they print the actual reason the solver picked rather than the potential strongest path.<\/i><\/p>\n

The why command determines why an installed package is installed. This provides reasonable feedback as to why an automatically installed package is installed; for a manually installed package no other reason is given. If the package is not installed, no reason can be determined.<\/i><\/p>\n

The why-not command determines why a package was determined to not be installable. This may not always yield a result, even if a package is uninstallable.<\/i><\/p>\n

Both commands take a single argument, the name of a package.<\/i><\/p><\/blockquote>\n

For example, run the command below to determine why libheif1<\/code> package was installed in system:<\/p>\n

apt why libheif1<\/pre>\n
In my case, it told me user selected to install libm17n-0<\/code>. The package depends libgd3<\/code>, and libgd3<\/code> depends libheif1<\/code>, so it was installed along-with as dependency.<\/p>\n
\"\"<\/a><\/p>\n
Include and Exclude options<\/h3>\n
Besides that, apt 3.1 introduced new Include<\/code> and Exclude<\/code> options<\/b>, allowing to set allow-list or remove packages from a repository.<\/p>\n
This is useful when a repository (e.g., Ubuntu PPA) contains many app packages, but you need only one or some of them, and want to block all others. Previously, we can add a rule under \/etc\/apt\/preferences.d<\/code> to set package priority. Now, the new method is way stronger, as it excludes the packages from being parsed into the cache.<\/p>\n
For example, assume that you added ppa:ubuntuhandbook1\/apps PPA, but only need the converseen<\/code> package, then you may edit the corresponding .sources file under \/etc\/apt\/sources.list.d<\/code> directory, then add:<\/p>\n
Include: converseen<\/pre>\n
After that, save file and run sudo apt update<\/code> to refresh cache. Finally, only converseen<\/code> package from that PPA is available to install, while all others are excluded.<\/p>\n
NOTE: “include” and “exclude” do not handle dependencies. You need to add them all if they are also available in the repository. For example, include audacious<\/code> and all its dependencies via:<\/b><\/p>\n
Include: audacious libaudcore5 libaudgui5 libaudqt2 libaudtag3 audacious-plugins audacious-plugins-data<\/pre>\n
\"\"<\/a><\/p>\n
For choice, Softare & Updates<\/b> utility offers a graphical way to include\/exclude packages.<\/p>\n
Just launch the tool and navigate to “Other Software” tab, then highlight and edit the source repository, finally click Add<\/b> button under “Additional Fields”, set Key to either Include<\/code> or Exclude<\/code> and input package names as value.<\/p>\n
\"\"<\/a>
Exclude a package for a repository<\/p><\/div>\n
How to Get apt 3.1.0<\/h3>\n
apt 3.1.0 has been made into Debian experimental<\/a> repository. It will be backported to latest Ubuntu development release once migrated to Debian Unstable (Sid) repository.<\/p>\n
If you can’t wait for the update, then you may grab the source code<\/a> and build it by yourself.<\/p>","protected":false},"excerpt":{"rendered":"
apt, the default command line package manager for Debian and Ubuntu based Linux Distributions, released new version 3.1.0 on Monday. As you may know, apt 3.0 introduced new package dependency resolver with more efficient and clean output. Now, the resolver 3 is enabled by default in the new 3.1 release.<\/p>\n","protected":false},"author":1,"featured_media":48939,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[6],"tags":[2022,773],"class_list":["post-48938","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-news","tag-apt","tag-debian"],"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/ubuntuhandbook.org\/index.php\/wp-json\/wp\/v2\/posts\/48938","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/ubuntuhandbook.org\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/ubuntuhandbook.org\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/ubuntuhandbook.org\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/ubuntuhandbook.org\/index.php\/wp-json\/wp\/v2\/comments?post=48938"}],"version-history":[{"count":0,"href":"https:\/\/ubuntuhandbook.org\/index.php\/wp-json\/wp\/v2\/posts\/48938\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/ubuntuhandbook.org\/index.php\/wp-json\/wp\/v2\/media\/48939"}],"wp:attachment":[{"href":"https:\/\/ubuntuhandbook.org\/index.php\/wp-json\/wp\/v2\/media?parent=48938"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/ubuntuhandbook.org\/index.php\/wp-json\/wp\/v2\/categories?post=48938"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/ubuntuhandbook.org\/index.php\/wp-json\/wp\/v2\/tags?post=48938"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}