summaryrefslogtreecommitdiff
path: root/doc/forum/chroot_issue_when_upgrading/comment_8_d1c546c6f88035d40eca823d25d67e92._comment
blob: 9792a6241495de09f9af1472166b13f879b8a831 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
[[!comment format=mdwn
 username="joey"
 subject="""comment 8"""
 date="2016-04-01T17:26:15Z"
 content="""
       -f, --fix-broken
           Fix; attempt to correct a system with broken dependencies
           in place. This option, when used with install/remove, can
           omit any packages to permit APT to deduce a likely
           solution. If packages are specified, these have to
           completely correct the problem. The option is sometimes
           necessary when running APT for the first time; APT itself
           does not allow broken package dependencies to exist on a
           system.

So I don't see how you could get into this situation unless perhaps
your debootstrap configuration gets into a broken dependency situation somehow.

IIRC, apt-get -f install can decide to *remove* arbitrary packages as necessary
to get to a sane dependency tree. So I'm very dubious about doing it by default.
"""]]