The original history for this bug is in https://bugs.debian.org/985916
and this bug is caused by fixing that one... though it really stands as
it's own issue.

This of course, only happens if you install packages into your profile
that conflict with what is installed via dpkg, so setting this bug as
important severity.

I suspect that is tricker...

I *think* so.


live well,
  vagrant