On 28/02/2022 13:50, Miguel A. Vallejo wrote:
I have never seen this behaviour in 20+ years of using Debian [15 of them with SID]. Closest thing I have seen is something about "broken packages" but that is before it starts to do any actual work. What is the message you getting when this happens?The question is: Why is APT not smart enough to see that the proposed upgrade will fail? It always starts to install packages and at some point fails because some package needs another package with a specific version. Why does it not detect these cases after starting upgrading packages? It knows the versions available for every package so it should prevent these problems. Is it a bug or a missing APT feature?
alexd