-"Defaults to on which will cause APT to install essential and important "
-"packages as fast as possible in the install/upgrade operation. This is done "
-"to limit the effect of a failing &dpkg; call: If this option is disabled APT "
-"does treat an important package in the same way as an extra package: Between "
-"the unpacking of the important package A and his configuration can then be "
-"many other unpack or configuration calls, e.g. for package B which has no "
-"relation to A, but causes the dpkg call to fail (e.g. because maintainer "
-"script of package B generates an error) which results in a system state in "
-"which package A is unpacked but unconfigured - each package depending on A "
-"is now no longer guaranteed to work as their dependency on A is not longer "
-"satisfied. The immediate configuration marker is also applied to all "
-"dependencies which can generate a problem if the dependencies e.g. form a "
-"circle as a dependency with the immediate flag is comparable with a "
-"Pre-Dependency. So in theory it is possible that APT encounters a situation "
-"in which it is unable to perform immediate configuration, errors out and "
-"refers to this option so the user can deactivate the immediate configuration "
-"temporarily to be able to perform an install/upgrade again. Note the use of "
-"the word \"theory\" here as this problem was only encountered by now in real "
-"world a few times in non-stable distribution versions and was caused by "
-"wrong dependencies of the package in question or by a system in an already "
-"broken state, so you should not blindly disable this option as the mentioned "
-"scenario above is not the only problem immediate configuration can help to "
-"prevent in the first place. Before a big operation like "
-"<literal>dist-upgrade</literal> is run with this option disabled it should "
-"be tried to explicitly <literal>install</literal> the package APT is unable "
-"to configure immediately, but please make sure to report your problem also "
-"to your distribution and to the APT team with the buglink below so they can "
-"work on improving or correcting the upgrade process."
-msgstr ""
-
-#. type: Content of: <refentry><refsect1><variablelist><varlistentry><listitem><para>
-#: apt.conf.5.xml:209
-msgid ""
-"Never Enable this option unless you -really- know what you are doing. It "
-"permits APT to temporarily remove an essential package to break a "
-"Conflicts/Conflicts or Conflicts/Pre-Depend loop between two essential "
-"packages. SUCH A LOOP SHOULD NEVER EXIST AND IS A GRAVE BUG. This option "
-"will work if the essential packages are not tar, gzip, libc, dpkg, bash or "
-"anything that those packages depend on."
-msgstr ""
-
-#. type: Content of: <refentry><refsect1><variablelist><varlistentry><listitem><para>
-#: apt.conf.5.xml:218
-msgid ""
-"APT uses since version 0.7.26 a resizable memory mapped cache file to store "
-"the 'available' information. <literal>Cache-Start</literal> acts as a hint "
-"to which size the Cache will grow and is therefore the amount of memory APT "
-"will request at startup. The default value is 20971520 bytes (~20 MB). Note "
-"that this amount of space needs to be available for APT otherwise it will "
-"likely fail ungracefully, so for memory restricted devices this value should "
-"be lowered while on systems with a lot of configured sources it should be "
-"increased. <literal>Cache-Grow</literal> defines in bytes with the default "
-"of 1048576 (~1 MB) how much the Cache size will be increased in the event "
-"the space defined by <literal>Cache-Start</literal> is not enough. These "
-"value will be applied again and again until either the cache is big enough "
-"to store all information or the size of the cache reaches the "
-"<literal>Cache-Limit</literal>. The default of "
-"<literal>Cache-Limit</literal> is 0 which stands for no limit. If "
-"<literal>Cache-Grow</literal> is set to 0 the automatic grow of the cache is "
-"disabled."
+"Generate debug messages describing which packages are marked as "
+"keep/install/remove while the ProblemResolver does his work. Each addition "
+"or deletion may trigger additional actions; they are shown indented two "
+"additional spaces under the original entry. The format for each line is "
+"<literal>MarkKeep</literal>, <literal>MarkDelete</literal> or "
+"<literal>MarkInstall</literal> followed by <literal>package-name <a.b.c "
+"-> d.e.f | x.y.z> (section)</literal> where <literal>a.b.c</literal> "
+"is the current version of the package, <literal>d.e.f</literal> is the "
+"version considered for installation and <literal>x.y.z</literal> is a newer "
+"version, but not considered for installation (because of a low pin "
+"score). The later two can be omitted if there is none or if it is the same "
+"as the installed version. <literal>section</literal> is the name of the "
+"section the package appears in."
projects / apt.git / blobdiff