DNF4-REPOSYNC(8)
β¨ DNF4-REPOSYNC β¨
okay bestie, gather round π this one's from the dnf-plugins-core fam, and it's literally called dnf4-reposync β the DNF reposync Plugin. And what does it do? It synchronizes the packages of a remote DNF repository to a local directory. That's it. That's the whole vibe. Mirroring, but make it cute πͺβ¨
πΈ SYNOPSIS πΈ
dnf reposync [options]
π¦ DESCRIPTION π¦
reposync makes local copies of remote repositories. And here's the iconic part: if a package is already sitting there in your local directory, it does not get downloaded again. No double-dipping, no wasted bandwidth, we love an efficient queen π
π OPTIONS π
All general DNF options are accepted, bestie. Namely, the --repoid option can be used to specify the repositories to synchronize. See Options in dnf(8) for details. Go look, it's right there π«Ά
-a<architecture>,--arch=<architecture>β Download only packages of given architectures (the default is all architectures, greedy girl). Can be used multiple times.--deleteβ Delete local packages that are no longer present in the repository. Bye bitch π--download-metadataβ Download all repository metadata. The downloaded copy is instantly usable as a repository, so you do not need to runcreaterepo_con it. When the option is used withβnewest-only, only latest packages will be downloaded, but the metadata will still contain older packages. It might be useful to update metadata usingcreaterepo_c βupdateto remove the packages with missing RPM files from metadata. Otherwise, DNF ends with an error due to the missing files whenever it tries to download older packages. π-g,--gpgcheckβ Remove packages that fail GPG signature checking after downloading. Exit code is1if at least one package was removed. Note that for repositories withgpgcheck=0set in their configuration the GPG signature is not checked even with this option used β οΈ-m,--downloadcompsβ Also download and uncompresscomps.xml. Consider using the--download-metadataoption instead, which will download all available repository metadata. Just saying, that one eats harder π--metadata-pathβ Root path under which the downloaded metadata are stored. It defaults to the--download-pathvalue if not given.-n,--newest-onlyβ Download only newest packages per-repo. Out with the old β¨--norepopathβ Don't add the reponame to the download path. Can only be used when syncing a single repository (the default is to add the reponame).-p<download-path>,--download-path=<download-path>β Root path under which the downloaded repositories are stored, relative to the current working directory. Defaults to the current working directory. Every downloaded repository has a subdirectory named after its ID under this path. The way it nests like thatβ¦ iconic π--safe-write-pathβ Specify the filesystem path prefix under which the reposync is allowed to write. If not specified it defaults to the download path of the repository. Useful for repositories that use relative locations of packages out of the repository directory (e.g."../packages_store/foo.rpm"). Use with care, any file under the safe-write-path can be overwritten π¨ Can be only used when syncing a single repository.--remote-timeβ Try to set the timestamps of the downloaded files to those on the remote side. Time travel but legal β°--sourceβ Download only source packages.-u,--urlsβ Just print urls of what would be downloaded, don't download. Window shopping only, no cap ποΈ
π EXAMPLES π
dnf reposync --repoid=the_repo
Synchronize all packages from the repository with id "the_repo". The synchronized copy is saved in the "the_repo" subdirectory of the current working directory. cute, self-contained, effortless β¨
dnf reposync -p /my/repos/path --repoid=the_repo
Synchronize all packages from the repository with id "the_repo". In this case the files are saved in the "/my/repos/path/the_repo" directory. Full custom placement, main character energy π
dnf reposync --repoid=the_repo --download-metadata
Synchronize all packages and metadata from the "the_repo" repository. Metapilled π
A repository synchronized with the --download-metadata option can be directly used in DNF, for example by using the --repofrompath option:
dnf --repofrompath=syncedrepo,the_repo --repoid=syncedrepo list
--available
π SEE ALSO π
dnf(8), DNF Command Reference
π Author π
See AUTHORS in your Core DNF Plugins distribution.
π Copyright π
2014, Red Hat, Licensed under GPLv2+
okay that's the whole page bestie, go forth and sync π§π
this was version 4.10.1, dated Sep 27, 2025 β mwah, periodt π πΈ
π¦ where this page comes from
- ubuntu resolute: dnf-plugins-core 4.10.1-5 Β· GPL-2.0-or-later
- ubuntu stonking: dnf-plugins-core 4.10.1-5 Β· GPL-2.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms