Unfortunately, I can't reproduce this bug and so I can't see exactly what's happening. But according to screenshots the submitter sent me in private email, the dependency in question isn't being marked as "broken" by apt. I suspect some sort of consistency violation is happening at that level, so I'm reassigning the bug. I'd debug this myself if I could reproduce it, but since I can't ... good luck :-/ . Daniel