THE FIELD GUIDE / PATCHING

Repositories, trust & mirrors

Signed metadata, source configuration and scoped access.

Mr Patchy documentation · 2 min read

Manage native sources

Inspect, add, edit and disable APT .list, Deb822 .sources and RPM .repo definitions. Upload signing keys, restore reviewed source backups and inspect source-level fetch diagnostics. Structured credential and mirror editors keep access configuration explicit.

Private repository access

Configure scoped HTTPS credentials, private CA bundles, proxies, release preferences and exact-URI mirrors. Secrets are encrypted and staged privately for native repository tools. Repository transport includes administrator-provisioned media mirrors, native read-only local/media index acquisition, vendor entitlement and token-refresh integrations.

Keep trust explicit

Authenticated package artifacts and signed metadata support central resolution and integrity comparisons. Ambiguous source definitions, missing signing material and unsupported executable transport hooks fail closed. A repository’s trust does not establish that every package is harmless.

Go deeper

Open the application reference for capability scope and technical details.

Open Open RPM_SUPPORT.md on GitHub ↗

Actual application interface with illustrative documentation data.