Skip to content
Commit edeed569 authored by Guillem Jover's avatar Guillem Jover
Browse files

dpkg: Make sure to always switch to the next dependtry after no progress

We might get into a situation where we are making no progress, and
dependencies_ok() is still telling us that we can make progress by
fixing some triggers awaited package, but if those packages require
a dependency cycle to be broken we will get stuck and not progress to
the next dependtry.

Add an additional hard limit where we will jump dependtry, in case we
are not making any progress. This is a safety net that was removed when
triggers got introduced, but that only became active when adding the
dependency checks to trigproc(), although it was never future-proof.

Regression introduced in commit 10440009
and commit e121d882.

Closes: #766242, #766322
parent e65a01f2
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment