Packages & repositories
Resolve repository configuration, inspect packages, and understand signature checks.
Start with your distribution's repository format, then check which archive and key the package manager actually uses. A Debian source stanza, an RPM signature, and repository metadata describe different parts of the trust chain.
For an APT configuration error, read sources.list first. For an authentication failure, follow apt-secure. Use DNF5 and Zypper references for their own distributions; their options are not interchangeable.
No matching references. Try a broader term or clear the filters.
Resolve repository configuration, inspect packages, and understand signature checks.
-
APT source definitions
Compare .list lines and Deb822 .sources stanzas when a repository appears twice or its options disagree.
APT 2.6.1 · Debian 12 · Distribution reference · Selection reviewed -
APT archive authentication
Understand the archive trust chain and distinguish source configuration errors from failed signature verification.
APT 2.6.1 · Debian 12 · Distribution reference · Selection reviewed -
Debian package management handbook
Choose the right package-management tool and investigate package states, dependencies, upgrades, and repository priorities.
Maintained Debian Reference · Distribution reference · Selection reviewed -
RPM reference manual
Look up package queries, file ownership checks, and verification options before manipulating installed RPM packages.
RPM 6.0 · compare installed version · Project documentation · Selection reviewed -
DNF5 command reference
Find repository, dependency, history, and transaction commands for Fedora systems using DNF5.
DNF5 · upstream latest · Project documentation · Selection reviewed -
Zypper manual
Check repository refresh, package selection, and solver options on openSUSE; verify options against the installed Zypper manual.
Zypper · upstream development manual · Project documentation · Selection reviewed
How this library is selected
References are selected for a concrete operational task, with preference for project and distribution documentation. Annotations describe when to use a source; version labels make its scope explicit.
Selection reviewed means the destination, subject, and version scope were checked. It is not a claim that every upstream command has been tested. Original guides identify their own test environment. Platform filters also include references that apply across distributions.