This is behaving as designed; the package will be unpacked if possible
but not configured unless dependencies can be satisfied. (If pre-
dependencies cannot be satisfied, then the package will not even be
unpacked.) Changing this general rule would almost certainly render full
upgrades impossible since in such situations packages often need to be
unpacked before their dependencies are configured; similarly if you
supply multiple packages to 'dpkg -i' on the command line.
dpkg does not consider the state in which it leaves the system in this
case to be broken or "crashed"; it is a perfectly well-defined state
which just happens to include unconfigured packages. A user of an apt
frontend can easily recover by removing the offending package, or often
by using 'apt-get -f install' or similar. If your frontend does not
provide this kind of facility, then you should file a bug against the
frontend.
Otherwise, this is just dpkg doing what it was asked to do, completely
reasonably. Users who have trouble dealing with this should really be
using higher-level tools.
** Changed in: dpkg (Ubuntu)
Assignee: (unassigned) => Colin Watson (kamion)
Status: New => Won't Fix
--
dpkg installs too easily some packages
https://bugs.launchpad.net/bugs/269568
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
