Since this is what dpkg has been revamped to do.
Signed-off-by: Manoj Srivastava <srivasta@debian.org>
</example>
If this works, then the old-version is
"Installed", if not, the old version is in a
</example>
If this works, then the old-version is
"Installed", if not, the old version is in a
+ "Half-Configured" state.
</item>
</enumlist>
</item>
</item>
</enumlist>
</item>
If this fails, the package is left in a
"Half-Installed" state, which requires a
reinstall. If it works, the packages is left in
If this fails, the package is left in a
"Half-Installed" state, which requires a
reinstall. If it works, the packages is left in
- a "Config Files" state.
+ a "Config-Files" state.
</item>
<item>
Otherwise (i.e., the package was completely purged):
</item>
<item>
Otherwise (i.e., the package was completely purged):
<var>new-postrm</var> abort-install
</example>
If the error-unwind fails, the package is in a
<var>new-postrm</var> abort-install
</example>
If the error-unwind fails, the package is in a
- "Half Installed" phase, and requires a
+ "Half-Installed" phase, and requires a
reinstall. If the error unwind works, the
package is in a not installed state.
</item>
reinstall. If the error unwind works, the
package is in a not installed state.
</item>
<var>old-preinst</var> abort-upgrade <var>new-version</var>
</example>
If this fails, the old version is left in a
<var>old-preinst</var> abort-upgrade <var>new-version</var>
</example>
If this fails, the old version is left in a
- "Half Installed" state. If it works, dpkg now
+ "Half-Installed" state. If it works, dpkg now
calls:
<example compact="compact">
<var>new-postrm</var> abort-upgrade <var>old-version</var>
</example>
If this fails, the old version is left in a
calls:
<example compact="compact">
<var>new-postrm</var> abort-upgrade <var>old-version</var>
</example>
If this fails, the old version is left in a
- "Half Installed" state. If it works, dpkg now
+ "Half-Installed" state. If it works, dpkg now
calls:
<example compact="compact">
<var>old-postinst</var> abort-upgrade <var>new-version</var>
calls:
<example compact="compact">
<var>old-postinst</var> abort-upgrade <var>new-version</var>
- If this fails, the package is in a "Failed-Config"
+ If this fails, the package is in a "Half-Configured"
state, or else it remains "Installed".
</p>
</item>
state, or else it remains "Installed".
</p>
</item>
be <em>unpacked</em> the pre-dependency can be
satisfied if the depended-on package is either fully
configured, <em>or even if</em> the depended-on
be <em>unpacked</em> the pre-dependency can be
satisfied if the depended-on package is either fully
configured, <em>or even if</em> the depended-on
- package(s) are only unpacked or in the "Failed-Config"
+ package(s) are only unpacked or in the "Half-Configured"
state, provided that they have been configured
correctly at some point in the past (and not removed
or partially removed since). In this case, both the
previously-configured and currently unpacked or
state, provided that they have been configured
correctly at some point in the past (and not removed
or partially removed since). In this case, both the
previously-configured and currently unpacked or
- "Failed-Config" versions must satisfy any version
+ Half-Configured versions must satisfy any version
clause in the <tt>Pre-Depends</tt> field.
</p>
clause in the <tt>Pre-Depends</tt> field.
</p>
<p>
A package will not be regarded as causing breakage merely
because its configuration files are still installed; it must
<p>
A package will not be regarded as causing breakage merely
because its configuration files are still installed; it must
- be at least half-installed.
+ be at least Half-Installed.
<p>
A package will not cause a conflict merely because its
configuration files are still installed; it must be at least
<p>
A package will not cause a conflict merely because its
configuration files are still installed; it must be at least