summaryrefslogtreecommitdiff
path: root/doc/forum/chroot_issue_when_upgrading/comment_2_eea48d51f241651935f695ea1dc7dd87._comment
blob: 654ea40ce08892e02cc6228c8f0672586c0007ee (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
[[!comment format=mdwn
 username="joey"
 subject="""comment 2"""
 date="2016-02-29T21:44:19Z"
 content="""
There are several ways this could happen, along the lines of a power
failure or ctrl-c at the wrong time. A failing postinst may also cause
apt to leave other packages un-configured, although `dpkg configure -a`
probably won't recover from that case.

I think it makes sense for Apt.upgrade to run `dpkg --configure -a`
in case the last upgrade got into this state. I don't think it makes sense
for Apt.install to do that (too much overhead to do it every time,
and I don't think that unconfigured packages normally prevent installing
of an unrelated package anyway). I've made a change along these lines.
"""]]