projectatomic/rpm-ostree
1
0
Fork 0
mirror of https://github.com/projectatomic/rpm-ostree.git synced 2026-02-05 09:45:27 +01:00
Code Issues Releases Activity
Files
f7f498c8bd353dd3f15bd8b3e95fce3a3928f6f1
rpm-ostree/man/rpm-ostree.xml
Micah Abbott f7f498c8bd man: spelling corrections 
Found during Gemini review

Assisted-by: Gemini Code Assist
Signed-off-by: Micah Abbott <miabbott@redhat.com>
2025-10-23 14:17:25 -04:00

946 lines
34 KiB
XML
Raw Blame History

<?xml version='1.0'?> <!--*-nxml-*-->
<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
<!--
Copyright 2011,2013,2014 Colin Walters <walters@verbum.org>
This library is free software; you can redistribute it and/or
modify it under the terms of the GNU Lesser General Public
License as published by the Free Software Foundation; either
version 2 of the License, or (at your option) any later version.
This library is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
Lesser General Public License for more details.
You should have received a copy of the GNU Lesser General Public
License along with this library; if not, write to the
Free Software Foundation, Inc., 59 Temple Place - Suite 330,
Boston, MA 02111-1307, USA.
-->
<refentry id="rpm-ostree">
<refentryinfo>
<title>rpm-ostree</title>
<productname>rpm-ostree</productname>
<authorgroup>
<author>
<contrib>Developer</contrib>
<firstname>Jonathan</firstname>
<surname>Lebon</surname>
<email>jlebon@redhat.com</email>
</author>
</authorgroup>
<authorgroup>
<author>
<contrib>Developer</contrib>
<firstname>Colin</firstname>
<surname>Walters</surname>
<email>walters@redhat.com</email>
</author>
</authorgroup>
</refentryinfo>
<refmeta>
<refentrytitle>rpm-ostree</refentrytitle>
<manvolnum>1</manvolnum>
</refmeta>
<refnamediv>
<refname>rpm-ostree</refname>
<refpurpose>
Hybrid image/package system for host operating system updates
</refpurpose>
</refnamediv>
<refsynopsisdiv>
<cmdsynopsis>
<command>rpm-ostree</command>
<arg choice="req">COMMAND</arg>
<arg choice="opt" rep="repeat">OPTIONS</arg>
</cmdsynopsis>
</refsynopsisdiv>
<refsect1>
<title>Description</title>
<para>
rpm-ostree is a hybrid image and package system; as the name suggests, it
uses OSTree for the image side, and RPM for the package side. It supports
composing RPMs server-side into an OSTree commit (like an image), and
clients can replicate that bit-for-bit, with fast incremental updates.
Additionally, the hybrid nature comes to the fore with client-side package
layering and overrides.
</para>
<para>
On an rpm-ostree managed system, the traditional
<literal>yum</literal> (if installed) and <literal>rpm</literal>
tools operate in a read-only state; the RPM database is stored
in <literal>/usr/share/rpm</literal> which is underneath a
read-only bind mount.
</para>
<para>
Instead of live package-by-package upgrades, the underlying
OSTree layer replicates a complete filesystem tree from a
compose server into a new deployment, available on the next
reboot. One benefit of this is that there will always be a
previous deployment, available for rollback. This also
makes it easier to reliably "queue" an update without destabilizing
the running system at all. (Currently though there's an experimental
<literal>livefs</literal> command that supports changing the
running filesystem).
</para>
<para>
Note in this "pure replication" model, there is no per-client
packaging overhead. Dependency resolution, SELinux labeling,
all of the scripts etc. were run on the server side and captured
in the OSTree commit.
</para>
</refsect1>
<refsect1>
<title>Client side commands</title>
<variablelist>
<varlistentry>
<term><command>cancel</command></term>
<listitem>
<para>
Cancel a pending transaction. Exits successfully and does
nothing if no transaction is running. Note that it is fully
safe to cancel transactions such as <command>upgrade</command>
in general.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><command>db</command></term>
<listitem>
<para>
Gives information pertaining to <literal>rpm</literal> data
within the file system trees within the ostree commits.
There are three sub-commands:
</para>
<para>
<command>diff</command> to see how the packages are
different between the trees in two revs. If no revs are
provided, the booted commit is compared to the pending
commit. If only a single rev is provided, the booted commit
is compared to that rev. The
<option>--format=diff</option> option uses
<literal>-</literal> for removed packages,
<literal>+</literal> for added packages, and finally
<literal>!</literal> for the old version of an updated
package, with a following <literal>=</literal> for the new
version.
</para>
<para>
<command>list</command> to see which packages are within the
commit(s) (works like yum list). At least one commit must be
specified, but more than one or a range will also work.
</para>
<para>
<command>version</command> to see the rpmdb version of the
packages within the commit (works like yum version
nogroups). At least one commit must be specified, but more
than one or a range will also work.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><command>deploy</command></term>
<listitem>
<para>
Takes version, branch, or commit ID as an argument, and
creates a new deployment using it, setting it up as the
default for the next boot. Unlike most other commands, this
will automatically fetch and traverse the origin history to
find the target. By design, this has no effect on your
running filesystem tree. You must reboot for any changes to
take effect.
</para>
<para>This will also queue an update for any layered packages.</para>
<para>
<command>
--unchanged-exit-77
</command>
to exit status 77 to indicate that the system is already
on the specified commit. This tristate return model is
intended to support idempotency-oriented systems
automation tools like Ansible.
</para>
<para>
<command>--reboot</command> or <command>-r</command> to
initiate a reboot after the upgrade is prepared.
</para>
<para>
<command>--preview</command> download enough metadata to
inspect the RPM diff, but do not actually create a new
deployment.
</para>
<para>
<option>--cache-only</option> or <command>-C</command> to
perform the operation without trying to download the target
tree from the remote nor the latest packages.
</para>
<para>
<option>--download-only</option> to only download the target
ostree and layered RPMs without actually performing the
deployment. This can be used with a subsequent
<option>--cache-only</option> invocation to perform the
operation completely offline.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><command>install</command></term>
<listitem>
<para>
Takes one or more packages as arguments. The packages are
fetched from the enabled repositories in
<filename>/etc/yum.repos.d/</filename> and are overlayed on
top of a new deployment. It is also possible to specify a
local RPM package that resides on the host. Overlayed
packages can later be removed with the
<command>uninstall</command> command.
</para>
<para>
If this is the first time a machine-local change is made,
note that this will change rpm-ostree to operate in full
hybrid mode. Concretely, rpm-ostree will also start
fetching all enabled rpm-md (yum) repositories and use
those for package updates every time
<command>rpm-ostree upgrade</command> is invoked,
as well as during other operations such as <command>rebase</command>.
</para>
<para>
rpm-ostree remembers these requests even if a later host
update includes those packages already: if the packages are
subsequently dropped out again, rpm-ostree will go back to
layering them.
</para>
<para>
Note that by default, specifying a package that is already
in the base layer is an error unless the
<command>--allow-inactive</command> option is provided.
This can be useful when anticipating the removal of a base
package.
</para>
<para>
<command>--idempotent</command> to do nothing if a package
request is already present instead of erroring out.
</para>
<para>
<command>--reboot</command> or <command>-r</command> to
initiate a reboot after the deployment is prepared.
</para>
<para>
<command>--dry-run</command> or <command>-n</command> to
exit after printing the transaction rather than downloading
the packages and creating a new deployment.
</para>
<para>
<option>--allow-inactive</option> to allow requests for
packages that are already in the base layer.
</para>
<para>
<option>--cache-only</option> or <command>-C</command> to
perform the operation without trying to download the latest
packages.
</para>
<para>
<option>--download-only</option> to only download the target
layered RPMs without actually performing the deployment.
This can be used with a subsequent
<option>--cache-only</option> invocation to perform the
operation completely offline.
</para>
<para>
<option>--apply-live</option> will perform a subsequent <command>apply-live</command>
operation to apply changes to the booted deployment.
</para>
<para>
<option>--force-replacefiles</option> allows one package to overwrite files from another without having to rebuild the whole kernel package.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><command>uninstall</command></term>
<listitem>
<para>
Takes one or more packages as arguments. The packages are
removed from the set of packages that are currently
overlayed. The remaining packages in the set (if any) are
fetched from the enabled repositories in
<filename>/etc/yum.repos.d/</filename> and are overlayed on
top of a new deployment.
</para>
<para>
<command>--reboot</command> or <command>-r</command> to
initiate a reboot after the deployment is prepared.
</para>
<para>
<command>--dry-run</command> or <command>-n</command> to
exit after printing the transaction rather than downloading
the packages and creating a new deployment.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><command>search</command></term>
<listitem>
<para>
Takes one or more query terms as arguments. The packages are
searched within the enabled repositories in
<filename>/etc/yum.repos.d/</filename>. Packages can be
overlayed and removed using the <command>install</command>
and <command>uninstall</command> commands.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><command>rebase</command></term>
<listitem>
<para>
Switch to a different base image, while preserving all of the state that <command>upgrade</command>
does, such as <literal>/etc</literal> changes, any layered RPM
packages, etc.
</para>
<para>
For rebasing to container images, the syntax uses ostree container image references, which combine
container image transports (see <literal>man skopeo</literal>) along with a required integrity
scheme. The ostree model encourages container images to be signed, because they must be ultimately
trusted.
</para>
<para><literal>ostree-image-signed:docker://quay.io/exampleos/custom:latest</literal> - this will pull
from a remote registry, and error out if the container backend does not require signatures.</para>
<para><literal>ostree-unverified-registry:quay.io/exampleos/custom:latest</literal> - this will pull
from a remote registry, and no signature will be required. In practice, this is just a shorthand for
<literal>ostree-unverified-image:docker://quay.io/exampleos/custom:latest</literal>.</para>
<para><literal>ostree-unverified-image:oci:/path/to/dir.oci</literal> Fetch from a local unsigned OCI directory (integrity of this directory may have been verified out of band).</para>
<para>
For rebasing to OSTree branches, the full syntax is <literal>rebase REMOTENAME:BRANCHNAME</literal>.
Alternatively, you can use the <command>--branch</command> or
<command>--remote</command> options mentioned below. With the
argument syntax, specifying just <literal>BRANCHNAME</literal> will
reuse the same remote. You may also omit one of
<literal>REMOTENAME</literal> or <literal>BRANCHNAME</literal>
(keeping the colon). In the former case, the branch refers to a
local branch; in the latter case, the same branch will be used on a
different remote.
</para>
<para>This will also queue an update for any layered packages.</para>
<para>
<command>--branch</command> or <command>-b</command> to
pick a branch name.
</para>
<para>
<command>--remote</command> or <command>-m</command> to
pick a remote name.
</para>
<para>
<option>--cache-only</option> or <command>-C</command> to
perform the rebase without trying to download the target
tree from the remote nor the latest packages.
</para>
<para>
<option>--download-only</option> to only download the target
ostree and layered RPMs without actually performing the
deployment. This can be used with a subsequent
<option>--cache-only</option> invocation to perform the
operation completely offline.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><command>rollback</command></term>
<listitem>
<para>
OSTree manages an ordered list of bootloader entries, called
"deployments". The entry at index 0 is the default
bootloader entry. Each entry has a separate
<filename>/etc</filename>, but they all share a single
<filename>/var</filename>. You can use the bootloader to
choose between entries by pressing Tab to interrupt
startup.
</para>
<para>
This command then changes the default bootloader entry. If
the current default is booted, then set the default to the
previous entry. Otherwise, make the currently booted tree
the default.
</para>
<para>
<command>--reboot</command> or <command>-r</command> to
initiate a reboot after rollback is prepared.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><command>status</command></term>
<listitem>
<para>
Gives information pertaining to the current deployment in
use. Lists the names and refspecs of all possible
deployments in order, such that the first deployment in the
list is the default upon boot. The deployment marked with *
is the current booted deployment, and marking with 'r'
indicates the most recent upgrade (the newest deployment
version).
</para>
<para>
<command>--verbose</command> or <command>-v</command> to
display more information, such as package diff, advisories,
GPG signature user IDs, and StateRoot names.
</para>
<para>
<command>--advisories</command> or <command>-a</command> to
expand the advisories listing, if any.
</para>
<para>
<command>--booted</command> or <command>-b</command> to
only print information about the booted deployment.
</para>
<para>
<command>--pending-exit-77</command> to exit status 77 if
a pending deployment is available. This can be useful in
scripting.
</para>
<para>
<command>--json</command> to output the status information
in JSON format for easier scripting.
</para>
<para>
<command>--jsonpath=EXPRESSION</command> or
<command>-J</command> to filter JSON output by JSONPath
expression.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><command>upgrade</command></term>
<listitem>
<para>
Download the latest version of the current tree, and deploy
it, setting it up as the default for the next boot. By
design, this has no effect on your running filesystem tree.
You must reboot for any changes to take effect.
</para>
<para>
<command>
--unchanged-exit-77
</command>
to exit status 77 to indicate that the system is already
up to date. This tristate return model is intended to
support idempotency-oriented systems automation tools like
Ansible.
</para>
<para>
<command>--reboot</command> or <command>-r</command> to
initiate a reboot after upgrade is prepared.
</para>
<para>
<command>--allow-downgrade</command> to permit deployment of
chronologically older trees.
</para>
<para>
<option>--preview</option> to download only /usr/share/rpm
in order to do a package-level diff between the two
versions.
</para>
<para>
<option>--check</option> to just check if an upgrade is
available, without downloading it or performing a
package-level diff. Using this flag will force an update
of the RPM metadata from the enabled repos in
<filename>/etc/yum.repos.d/</filename>, if there are any
layered packages.
</para>
<para>
<option>--cache-only</option> or <command>-C</command> to
perform the upgrade without trying to download the latest
tree from the remote nor the latest packages.
</para>
<para>
<option>--download-only</option> to only download the target
ostree and layered RPMs without actually performing the
deployment. This can be used with a subsequent
<option>--cache-only</option> invocation to perform the
operation completely offline.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><command>override</command></term>
<listitem>
<para>
Provides subcommands for overriding (modifying) the base
OSTree layer. Such modifications should be done with care
and are normally not intended to be long-lasting. For
example, one might replace a base package with its older
version to avoid a regression. Overrides are automatically
carried over during new deployments. The subcommands are:
</para>
<para>
<command>remove</command> to remove base packages.
</para>
<para>
<command>replace</command> to replace base packages.
Requires explicitly specifying a set of RPMs to install via
HTTP or local file paths. On Fedora systems, it is also
supported to pull from the Fedora Koji/Bodhi systems.
For example,
<command>rpm-ostree override replace https://objstore.int.example.com/hotfixes/kernel.rpm</command>,
<command>rpm-ostree override replace ./podman.rpm</command>,
<command>rpm-ostree override replace https://bodhi.fedoraproject.org/updates/FEDORA-2020-XXXXXXX</command> or
<command>rpm-ostree override replace https://koji.fedoraproject.org/koji/buildinfo?buildID=XXXXXXX</command>
</para>
<para>
<command>reset</command> to reset previous overrides.
Currently, the full <literal>NEVRA</literal> of the target
packages must be specified.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><command>refresh-md</command></term>
<listitem>
<para>
Download the latest rpm repo metadata if necessary and generate the
cache.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><command>kargs</command></term>
<listitem>
<para>
Without options, display current default kernel arguments. Modify
arguments using the following parameters which will create a new
deployment with the modified kernel arguments. Previous deployments
are never changed.
</para>
<para>
<command>
--editor
</command>
to use an editor to modify the kernel arguments.
</para>
<para>
<command>
--append
</command>
to append a kernel argument. For example,
<command>--append=panic=1</command>.
</para>
<para>
<command>
--append-if-missing
</command>
to append a kernel argument if it is not present.
</para>
<para>
<command>
--delete
</command>
to delete a kernel argument. For example,
<command>--delete=panic=1</command>.
</para>
<para>
<command>
--delete-if-present
</command>
to delete a kernel argument if it is already present. For example,
<command>--delete-if-present=panic=1</command>.
</para>
<para>
<command>
--replace
</command>
to replace an existing kernel argument, it allows you to pass a
KEY=VALUE. Also, it supports "KEY=VALUE=NEWVALUE" to replace the
value of an argument only if one value exists for that argument.
For example, <command>--replace=panic=1</command>. or
<command>--replace=panic=1=0</command>.
</para>
<para>
<command>
--unchanged-exit-77
</command>
to exit status 77 to indicate that the kernel arguments have
not changed.
</para>
<para>
By default, modifications are applied to the kernel arguments of the
default deployment to get the final arguments. Use
<option>--deploy-index</option> or
<option>--import-proc-cmdline</option> to instead base them off of a
specific deployment or the current boot.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><command>cleanup</command></term>
<listitem>
<para>
Commands such as <command>upgrade</command> create new deployments,
which affect the next boot, and take up additional storage space. In
some cases, you may want to undo and clean up these operations. This
command supports both removing additional deployments such as the
"pending" deployment (the next boot) as well as the default rollback
deployment. Use <option>-p/--pending</option> to remove the pending
deployment, and <option>-r/--rollback</option> to remove the
rollback.
</para>
<para>
The <option>-b/--base</option> option does not affect finished
deployments, but will clean up any transient allocated space that
may result from interrupted operations. If you want to free up disk
space safely, use this option first.
</para>
<para>
The <option>-m/--repomd</option> option cleans up cached RPM
repodata and any partially downloaded (but not imported) packages.
</para>
<para>
NOTE: the <command>cleanup</command> will not affect any deployments
that have been "pinned" via the <command>ostree admin pin</command>
operation.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><command>reload</command></term>
<listitem>
<para>
Some configuration and state data such as
<literal>/etc/ostree/remotes.d</literal> changes may not be
reflected until a daemon reload is invoked. Use this command to
initiate a reload.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><command>usroverlay</command></term>
<listitem>
<para>
Mount a writable overlay filesystem on <literal>/usr</literal> which
is active only for the remainder of the system boot. This is
intended for development, testing, and debugging. Changes will not
persist across upgrades, or rebooting in general.
</para>
<para>
One important goal of this is to support traditional <command>rpm
-Uvh /path/to/rpms</command> or equivalent where changes are applied
live. However, an intended future feature for
<command>rpm-ostree</command> will be a variant of
<command>rpm-ostree override</command> which also supports applying
changes live, for the cases which one wants persistence as well.
</para>
<para>
This command is equivalent to <command>ostree admin unlock</command>.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><command>initramfs</command></term>
<listitem>
<para>
By default, the primary use case mode for rpm-ostree is to replicate
an initramfs as part of a base layer. However, some use cases
require locally regenerating it to add configuration or drivers. Use
<command>rpm-ostree initramfs</command> to inspect the current
status.
</para>
<para>
Use <command>--enable</command> to turn on client side initramfs
regeneration. This runs dracut to create the new initramfs. A new
deployment will be generated with this new initramfs, and after
reboot, further upgrades will continue regenerating. You must reboot
for the new initramfs to take effect.
</para>
<para>
To append additional custom arguments to the initramfs program
(currently dracut), use <command>--arg</command>. For example,
<command>--arg=-I --arg=/etc/someconfigfile</command>.
</para>
<para>
The <command>--disable</command> option will disable
regeneration. You must reboot for the change to take effect.
</para>
<para>
Note that for the simpler use case of adding a few files to the
initramfs, you can use <command>rpm-ostree initramfs-etc</command>
instead. It is more lightweight and does not involve running dracut.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><command>initramfs-etc</command></term>
<listitem>
<para>
Add configuration (<literal>/etc</literal>) files into the initramfs without
regenerating the entire initramfs. This is useful to be able to configure
services backing the root block device as well as early-boot services like
systemd and journald.
</para>
<para>
Use <command>--track</command> to start tracking a specific file. Can be
specified multiple times. A new deployment will be generated. Use
<command>--untrack</command> or <command>--untrack-all</command> to stop
tracking files.
</para>
<para>
When there are tracked files, any future created deployment (e.g. when doing an
upgrade) will ensure that they are synced. You can additionally use
<command>--force-sync</command> to simply generate a new deployment with the
latest versions of tracked files without upgrading.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><command>apply-live</command></term>
<listitem>
<para>
Given a target OSTree commit (defaults to the pending deployment), create a transient
<literal>overlayfs</literal> filesystem for the booted <literal>/usr</literal>, and synchronize
the changes from the source to the booted filesystem tree. By default, to ensure safety, only package additions
are allowed.
</para>
<para>
<option>--reset</option> to reset the filesystem tree to the booted commit.
</para>
<para>
<option>--target</option> may be used to target an arbitrary OSTree commit. This is an advanced feature, exposed mainly for testing.
</para>
<para>
<option>--allow-replacement</option> enables live updates and removals for existing packages.
</para>
<example>
<title>Install postgresql live</title>
<programlisting>$ rpm-ostree install postgresql-server
$ rpm-ostree apply-live
$ systemctl start postgresql # Some setup required
</programlisting>
<para>
This is also the same as:
</para>
<programlisting>$ rpm-ostree install -A postgresql-server</programlisting>
</example>
<para>
Currently, this just synchronizes the filesystem; no systemd units are restarted
for example.
</para>
<para>
A major implicit benefit of the <literal>overlayfs</literal> approach is that
if something goes wrong in the middle of a <literal>apply-live</literal> operation,
a system reboot will implicitly remove the overlay, restoring the system to
the pristine deployment state.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><command>ex</command></term>
<listitem>
<para>
This command offers access to experimental features; command line
stability is not guaranteed. The available subcommands will be listed
by invoking <command>rpm-ostree ex</command>.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><command>update</command></term>
<listitem>
<para>
Alias for the <command>upgrade</command> command.
</para>
</listitem>
</varlistentry>
</variablelist>
</refsect1>
<refsect1>
<title>Server side commands</title>
<variablelist>
<varlistentry>
<term><command>compose</command></term>
<listitem>
<para>
Entrypoint for tree composition; most typically used on servers to
prepare trees for replication by client systems. The
<literal>tree</literal> subcommand processes a treefile, installs
packages, and commits the result to an OSTree repository. There are
also split commands <literal>install</literal>,
<literal>postprocess</literal>, and <literal>commit</literal>.
</para>
</listitem>
</varlistentry>
</variablelist>
</refsect1>
<refsect1>
<title>Repository configuration and GPG keys</title>
<para>
rpm-ostree uses the libdnf shared library, which honors <literal>/etc/yum.repos.d</literal>.
Note that rpm-md (yum/dnf) repositories are only checked if client-side package layering is
enabled.
</para>
<para>
However, the behavior for GPG keys is slightly different from a traditional <command>rpm</command>
system. Essentially, all GPG keys in <literal>/etc/pki/rpm-gpg</literal> are loaded and trusted.
The <literal>.repo</literal> file should reference the file path in there.
</para>
<para>
The <literal>rpm --import /path/to/key.gpg</literal> command will not function today on a
live/booted system because rpm tries to write directly to the RPM database.
</para>
<para>
However, during a container build process, the RPM database is writable and such changes will
persist.
</para>
</refsect1>
<refsect1>
<title>See Also</title>
<para>
<citerefentry><refentrytitle>rpm-ostreed.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>
<citerefentry><refentrytitle>ostree</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
<citerefentry><refentrytitle>rpm</refentrytitle><manvolnum>8</manvolnum></citerefentry>
</para>
</refsect1>
</refentry>
View Git Blame Copy Permalink