Can you provide a complete (preferably real) example of what output you
would expect?

Honestly, I don't see this working as in the general case the reason is
not simple – its at least my experience from staring at debug output for
hours to figure such things out in the development branches of a
distribution. That is because a package is seldomly held back because it
is itself "misconstructed" (and never because its "corrupt, or otherwise
junk"), it is usually the state of the universe at large (so to speak)
who is at 'fault'.

Happy to be proven wrong through. Ideally with a tool who can deduce
these things which could be used in apt & elsewhere.

Also, but that comes down to user attitude I guess, is that as a user I
am trusting the tools I am using. So it justifying all its decisions in
detail for me to review feels way too micro-managing to me.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960727

Title:
  When apt holds back updates, it fails to inform the user of the reason

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1960727/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to