On Sun, Dec 25, 2016 at 11:08:58AM +0000, Pedro Ribeiro wrote: > severity 849164 critical
To issue a command, you need to either CC control@b.d.o or prefix the pseudoheader with "Control: ". > critical as the package cannot be installed Nope, "critical" applies if the bug: * breaks the whole system the package is installed on * introduces a severe security hole * breaks _unrelated_ software A plugin such as -ext-pack is definitely not unrelated. The proper severity for "the package is not installable" is merely "grave". Not that this matters, all RC severities bring the same practical consequences. > after upgrading virtualbox I cannot start previously suspended VM's Just discard the saved state. This is identical to pulling the power plug on a physical machine. Yeah, a hard power cycle is not nice but virtualbox fails this way for most unexpected configuration changes, even blase ones like a disk being inaccessible (RAID testing anyone?). Alternatively, you can use dpkg --force-depends and pray the dependency mismatch is just a mistake (which, judging from upstream versions being the same, it's quite likely). Gianfranco can give you a real answer, but AFAIK he's off to the family (such a surprise during Xmas!) thus might not respond immediately -- that's why I'm telling you about the "pull the plug" workaround. Meow! -- Autotools hint: to do a zx-spectrum build on a pdp11 host, type: ./configure --host=zx-spectrum --build=pdp11