Graphite - Apt package dependency visualization tool

1

I just stumbled across a reference to this very interesting tool on Reddit:

Thought others might be interested. I don't know enough to judge the extent of usefulness.

4 Likes
2

I get this when I attempt to install it via apt:
Err:15 https://ppa.launchpadcontent.net/cache-use-only/ppa/ubuntu jammy Release 404 Not Found [IP: 2620:2d:4000:1::81 443]

2 Likes
3

I got the same. :frowning:

I tried to compile the code from source, but I don't have the required version of meson, because I am only at 22.04.5 .

So, I guess, I can't actually try it.

1 Like
4

this ppa does not have jammy, contact maintainer.

image
image1920×869 27.4 KB

4 Likes
5

WOW, never knew about that ,this is absolutely cool :+1:

Thanks to your links I almost instantly came across another way to display a dependency graph that I never heard of:
debtree -v --max-depth=2 --rdeps-depth=2 debhelper | dot -Tpng > debhelper.png
where in this example debhelper can be replaced by any app whose dependencies you want to know.

4 Likes
6

Thank you, Pavlos! I don't know if I went to the right place, but I tried looking under Launchpad and couldn't see where to go.

Could you tell me where I can go to

  • see what you just listed (for future self-service), and
  • find the channel for contacting the maintainer ?
1 Like
7

I logged on to launchpad.net, searched for graphite. There are graphite admins, (top right) you can ask a question. But, it seems different from the graphite to show apt deps.

shows a signoff person

3 Likes
8

I think you can get any version of meson via pip: see Getting Meson

Best bet would be to create a virtual environment first (from the source code folder python -m venv .virtualenv then source .virtualenv/bin/activate); then use pip to get the specific version with meson==0.1.2 (with the version number you need).

4 Likes
9

This is the other reason why I hate Python :laughing:

4 Likes
10

:laughing: more ppl liked this than my attempt to help!

2 Likes
11

oops. :face_with_hand_over_mouth:

Well, I've tried the .virtualenv route before and I still ended up with

  1. either conflicts between regularly installed python apps and the .virtualenv python apps
  2. or the system did only run apps from the regular install or from the .virtualenv, not both.

It was a massive headache, and that was after reading the docs extensively. :face_with_spiral_eyes:

It might be that some other people encountered the same. :thinking:

Setting up a working .virtenv beside a standard install can be quite a pain in the butt and gets messy real fast if one (like me) doesn't know exactly what's going on behind the scenes. :woozy_face:

2 Likes
12

Like the recent issue with the linux-firmware update, which has now been resolved, I'm just going to wait until the developer gets it all figured out and releases an update. I can live without seeing a dependency map for that much longer...

1 Like