|author||Joey Hess||2016-04-01 13:28:26 -0400|
|committer||Joey Hess||2016-04-01 13:28:26 -0400|
Diffstat (limited to 'doc/forum/chroot_issue_when_upgrading')
1 files changed, 21 insertions, 0 deletions
diff --git a/doc/forum/chroot_issue_when_upgrading/comment_8_d1c546c6f88035d40eca823d25d67e92._comment b/doc/forum/chroot_issue_when_upgrading/comment_8_d1c546c6f88035d40eca823d25d67e92._comment
new file mode 100644
@@ -0,0 +1,21 @@
+ subject="""comment 8"""
+ -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
+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.