So, from what I saw there indeed 4 dependtry with different semantics - see src/configure.c:deferred_configure comment. It seems that dpkg is trying to break a cycle but fails, and then hits the assert (which should, and will be, an internerr).
@Brian: The error tracker says it cannot find the problem.
I don't completely understand trigger looping, but maybe it's one of the situations again where some triggers are "interest" and can be made "interest-noawait"?
So, from what I saw there indeed 4 dependtry with different semantics - see src/configure. c:deferred_ configure comment. It seems that dpkg is trying to break a cycle but fails, and then hits the assert (which should, and will be, an internerr).
@Brian: The error tracker says it cannot find the problem.
I don't completely understand trigger looping, but maybe it's one of the situations again where some triggers are "interest" and can be made "interest-noawait"?