Timeline for apt/aptitude - How can I display a package dependency tree for a collection of packages, taken as a whole?
Current License: CC BY-SA 4.0
Post Revisions
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 14, 2025 at 15:36 | answer | added | Alex | timeline score: 0 | |
| Apr 8, 2021 at 0:15 | answer | added | HippoMan | timeline score: 2 | |
| Apr 7, 2021 at 17:02 | comment | added | HippoMan |
I did the apt-cache depends procedure, and it isn't showing a common ancestor. However, I think I understand why. In trying to fix my original problem so I could continue to use my host, I converted all 1,400+ packages from "auto" to "manual". Now, there is no longer any common dependency ancestor. Is there a way to get the dependency ancestors which would be in place if I did a standard install of the package before making any changes?
|
|
| Apr 7, 2021 at 16:55 | comment | added | Stewart | Oh, by the way. That script I mention generates/updates this webpage: sandrotosi.me/debian/py2removal/index.html | |
| Apr 7, 2021 at 16:54 | comment | added | HippoMan | Yes, thank you. Doing this on a few of the packages should be able to narrow down the search pretty quickly. | |
| Apr 7, 2021 at 16:43 | comment | added | Stewart |
If you don't know the package, then you can recursively apt-cache depends <package> to build a dependency tree of what's needed for your package. Do this one a few packages at the same time and filter to only what's common for all packages.
|
|
| Apr 7, 2021 at 16:39 | answer | added | GAD3R | timeline score: 15 | |
| Apr 7, 2021 at 16:38 | comment | added | HippoMan | I'll look into this script. Thank you very much! I'm not sure whether or not this will help me, because I am searching for the base package, and I don't know it in advance. That script might be performing an inverse operation. But I'll look through that code and see if it can still help me. | |
| Apr 7, 2021 at 16:31 | comment | added | Stewart |
Not sure if this helps, but when the Debian Python team was planning the removal of python2, we had to figure out the order in which to remove packages (starting with leaf packages with 0 rdeps). One of the members came up with a pretty cool script for it here: github.com/sandrotosi/debian-tools. You could probably modify this script to build yourself a tree structure. But in short, it's a matter of choose a base package, then recursively parsing apt-cache rdepends <package>.
|
|
| Apr 7, 2021 at 16:10 | history | edited | HippoMan | CC BY-SA 4.0 |
edited body
|
| Apr 7, 2021 at 16:05 | history | asked | HippoMan | CC BY-SA 4.0 |