From beba93baede04835687e1caeefead24f173d9048 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Fri, 1 Apr 2016 13:28:26 -0400 Subject: comment --- ...ment_8_d1c546c6f88035d40eca823d25d67e92._comment | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) create mode 100644 doc/forum/chroot_issue_when_upgrading/comment_8_d1c546c6f88035d40eca823d25d67e92._comment (limited to 'doc/forum/chroot_issue_when_upgrading') 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 index 00000000..9792a624 --- /dev/null +++ b/doc/forum/chroot_issue_when_upgrading/comment_8_d1c546c6f88035d40eca823d25d67e92._comment @@ -0,0 +1,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. +"""]] -- cgit v1.2.3