--- /srv/reproducible-results/rbuild-debian/r-b-build.SH0Tl2hj/b1/dnf-plugins-core_4.10.0-1_amd64.changes +++ /srv/reproducible-results/rbuild-debian/r-b-build.SH0Tl2hj/b2/dnf-plugins-core_4.10.0-1_amd64.changes ├── Files │ @@ -1,2 +1,2 @@ │ │ - 2252f4c2b9ccab80d80126b1eb0e1ce8 244464 admin optional dnf-plugins-core_4.10.0-1_all.deb │ + e485a0593b98dd9c27fbd2d3cb469233 245020 admin optional dnf-plugins-core_4.10.0-1_all.deb ├── dnf-plugins-core_4.10.0-1_all.deb │ ├── file list │ │ @@ -1,3 +1,3 @@ │ │ -rw-r--r-- 0 0 0 4 2025-02-12 10:03:18.000000 debian-binary │ │ --rw-r--r-- 0 0 0 4288 2025-02-12 10:03:18.000000 control.tar.xz │ │ --rw-r--r-- 0 0 0 239984 2025-02-12 10:03:18.000000 data.tar.xz │ │ +-rw-r--r-- 0 0 0 4284 2025-02-12 10:03:18.000000 control.tar.xz │ │ +-rw-r--r-- 0 0 0 240544 2025-02-12 10:03:18.000000 data.tar.xz │ ├── control.tar.xz │ │ ├── control.tar │ │ │ ├── ./md5sums │ │ │ │ ├── ./md5sums │ │ │ │ │┄ Files differ │ ├── data.tar.xz │ │ ├── data.tar │ │ │ ├── file list │ │ │ │ @@ -158,27 +158,27 @@ │ │ │ │ drwxr-xr-x 0 root (0) root (0) 0 2025-02-12 10:03:18.000000 ./usr/share/man/man1/ │ │ │ │ -rw-r--r-- 0 root (0) root (0) 906 2025-02-12 10:03:18.000000 ./usr/share/man/man1/debuginfo-install.1.gz │ │ │ │ -rw-r--r-- 0 root (0) root (0) 1292 2025-02-12 10:03:18.000000 ./usr/share/man/man1/dnf-utils.1.gz │ │ │ │ -rw-r--r-- 0 root (0) root (0) 1689 2025-02-12 10:03:18.000000 ./usr/share/man/man1/needs-restarting.1.gz │ │ │ │ -rw-r--r-- 0 root (0) root (0) 883 2025-02-12 10:03:18.000000 ./usr/share/man/man1/package-cleanup.1.gz │ │ │ │ -rw-r--r-- 0 root (0) root (0) 774 2025-02-12 10:03:18.000000 ./usr/share/man/man1/repo-graph.1.gz │ │ │ │ -rw-r--r-- 0 root (0) root (0) 1025 2025-02-12 10:03:18.000000 ./usr/share/man/man1/repoclosure.1.gz │ │ │ │ --rw-r--r-- 0 root (0) root (0) 1198 2025-02-12 10:03:18.000000 ./usr/share/man/man1/repodiff.1.gz │ │ │ │ --rw-r--r-- 0 root (0) root (0) 1280 2025-02-12 10:03:18.000000 ./usr/share/man/man1/repomanage.1.gz │ │ │ │ --rw-r--r-- 0 root (0) root (0) 1883 2025-02-12 10:03:18.000000 ./usr/share/man/man1/reposync.1.gz │ │ │ │ +-rw-r--r-- 0 root (0) root (0) 1206 2025-02-12 10:03:18.000000 ./usr/share/man/man1/repodiff.1.gz │ │ │ │ +-rw-r--r-- 0 root (0) root (0) 1295 2025-02-12 10:03:18.000000 ./usr/share/man/man1/repomanage.1.gz │ │ │ │ +-rw-r--r-- 0 root (0) root (0) 1899 2025-02-12 10:03:18.000000 ./usr/share/man/man1/reposync.1.gz │ │ │ │ -rw-r--r-- 0 root (0) root (0) 1200 2025-02-12 10:03:18.000000 ./usr/share/man/man1/yum-builddep.1.gz │ │ │ │ -rw-r--r-- 0 root (0) root (0) 896 2025-02-12 10:03:18.000000 ./usr/share/man/man1/yum-changelog.1.gz │ │ │ │ -rw-r--r-- 0 root (0) root (0) 1522 2025-02-12 10:03:18.000000 ./usr/share/man/man1/yum-config-manager.1.gz │ │ │ │ -rw-r--r-- 0 root (0) root (0) 1286 2025-02-12 10:03:18.000000 ./usr/share/man/man1/yum-debug-dump.1.gz │ │ │ │ -rw-r--r-- 0 root (0) root (0) 1290 2025-02-12 10:03:18.000000 ./usr/share/man/man1/yum-debug-restore.1.gz │ │ │ │ -rw-r--r-- 0 root (0) root (0) 1590 2025-02-12 10:03:18.000000 ./usr/share/man/man1/yum-groups-manager.1.gz │ │ │ │ -rw-r--r-- 0 root (0) root (0) 1293 2025-02-12 10:03:18.000000 ./usr/share/man/man1/yum-utils.1.gz │ │ │ │ -rw-r--r-- 0 root (0) root (0) 1291 2025-02-12 10:03:18.000000 ./usr/share/man/man1/yumdownloader.1.gz │ │ │ │ drwxr-xr-x 0 root (0) root (0) 0 2025-02-12 10:03:18.000000 ./usr/share/man/man5/ │ │ │ │ --rw-r--r-- 0 root (0) root (0) 2292 2025-02-12 10:03:18.000000 ./usr/share/man/man5/yum-versionlock.conf.5.gz │ │ │ │ +-rw-r--r-- 0 root (0) root (0) 2307 2025-02-12 10:03:18.000000 ./usr/share/man/man5/yum-versionlock.conf.5.gz │ │ │ │ drwxr-xr-x 0 root (0) root (0) 0 2025-02-12 10:03:18.000000 ./usr/share/man/man8/ │ │ │ │ -rw-r--r-- 0 root (0) root (0) 1191 2025-02-12 10:03:18.000000 ./usr/share/man/man8/dnf4-builddep.8.gz │ │ │ │ -rw-r--r-- 0 root (0) root (0) 887 2025-02-12 10:03:18.000000 ./usr/share/man/man8/dnf4-changelog.8.gz │ │ │ │ -rw-r--r-- 0 root (0) root (0) 1514 2025-02-12 10:03:18.000000 ./usr/share/man/man8/dnf4-config-manager.8.gz │ │ │ │ -rw-r--r-- 0 root (0) root (0) 1619 2025-02-12 10:03:18.000000 ./usr/share/man/man8/dnf4-copr.8.gz │ │ │ │ -rw-r--r-- 0 root (0) root (0) 1269 2025-02-12 10:03:18.000000 ./usr/share/man/man8/dnf4-debug.8.gz │ │ │ │ -rw-r--r-- 0 root (0) root (0) 901 2025-02-12 10:03:18.000000 ./usr/share/man/man8/dnf4-debuginfo-install.8.gz │ │ │ │ @@ -189,16 +189,16 @@ │ │ │ │ -rw-r--r-- 0 root (0) root (0) 969 2025-02-12 10:03:18.000000 ./usr/share/man/man8/dnf4-leaves.8.gz │ │ │ │ -rw-r--r-- 0 root (0) root (0) 784 2025-02-12 10:03:18.000000 ./usr/share/man/man8/dnf4-local.8.gz │ │ │ │ -rw-r--r-- 0 root (0) root (0) 1481 2025-02-12 10:03:18.000000 ./usr/share/man/man8/dnf4-modulesync.8.gz │ │ │ │ -rw-r--r-- 0 root (0) root (0) 1693 2025-02-12 10:03:18.000000 ./usr/share/man/man8/dnf4-needs-restarting.8.gz │ │ │ │ -rw-r--r-- 0 root (0) root (0) 1792 2025-02-12 10:03:18.000000 ./usr/share/man/man8/dnf4-post-transaction-actions.8.gz │ │ │ │ -rw-r--r-- 0 root (0) root (0) 1789 2025-02-12 10:03:18.000000 ./usr/share/man/man8/dnf4-pre-transaction-actions.8.gz │ │ │ │ -rw-r--r-- 0 root (0) root (0) 1022 2025-02-12 10:03:18.000000 ./usr/share/man/man8/dnf4-repoclosure.8.gz │ │ │ │ --rw-r--r-- 0 root (0) root (0) 1195 2025-02-12 10:03:18.000000 ./usr/share/man/man8/dnf4-repodiff.8.gz │ │ │ │ +-rw-r--r-- 0 root (0) root (0) 1204 2025-02-12 10:03:18.000000 ./usr/share/man/man8/dnf4-repodiff.8.gz │ │ │ │ -rw-r--r-- 0 root (0) root (0) 768 2025-02-12 10:03:18.000000 ./usr/share/man/man8/dnf4-repograph.8.gz │ │ │ │ --rw-r--r-- 0 root (0) root (0) 1281 2025-02-12 10:03:18.000000 ./usr/share/man/man8/dnf4-repomanage.8.gz │ │ │ │ --rw-r--r-- 0 root (0) root (0) 1882 2025-02-12 10:03:18.000000 ./usr/share/man/man8/dnf4-reposync.8.gz │ │ │ │ +-rw-r--r-- 0 root (0) root (0) 1296 2025-02-12 10:03:18.000000 ./usr/share/man/man8/dnf4-repomanage.8.gz │ │ │ │ +-rw-r--r-- 0 root (0) root (0) 1898 2025-02-12 10:03:18.000000 ./usr/share/man/man8/dnf4-reposync.8.gz │ │ │ │ -rw-r--r-- 0 root (0) root (0) 524 2025-02-12 10:03:18.000000 ./usr/share/man/man8/dnf4-show-leaves.8.gz │ │ │ │ --rw-r--r-- 0 root (0) root (0) 2601 2025-02-12 10:03:18.000000 ./usr/share/man/man8/dnf4-system-upgrade.8.gz │ │ │ │ --rw-r--r-- 0 root (0) root (0) 2278 2025-02-12 10:03:18.000000 ./usr/share/man/man8/dnf4-versionlock.8.gz │ │ │ │ +-rw-r--r-- 0 root (0) root (0) 2609 2025-02-12 10:03:18.000000 ./usr/share/man/man8/dnf4-system-upgrade.8.gz │ │ │ │ +-rw-r--r-- 0 root (0) root (0) 2293 2025-02-12 10:03:18.000000 ./usr/share/man/man8/dnf4-versionlock.8.gz │ │ │ │ -rw-r--r-- 0 root (0) root (0) 1626 2025-02-12 10:03:18.000000 ./usr/share/man/man8/yum-copr.8.gz │ │ │ │ --rw-r--r-- 0 root (0) root (0) 2287 2025-02-12 10:03:18.000000 ./usr/share/man/man8/yum-versionlock.8.gz │ │ │ │ +-rw-r--r-- 0 root (0) root (0) 2301 2025-02-12 10:03:18.000000 ./usr/share/man/man8/yum-versionlock.8.gz │ │ │ ├── ./usr/share/man/man1/repodiff.1.gz │ │ │ │ ├── repodiff.1 │ │ │ │ │ @@ -46,15 +46,15 @@ │ │ │ │ │ .B \fB\-\-repo\-old=, \-o \fP │ │ │ │ │ Add a \fB\fP as an old repository. It is possible to be used in conjunction with \fB\-\-repofrompath\fP option. Can be specified multiple times. │ │ │ │ │ .TP │ │ │ │ │ .B \fB\-\-repo\-new=, \-n \fP │ │ │ │ │ Add a \fB\fP as a new repository. Can be specified multiple times. │ │ │ │ │ .TP │ │ │ │ │ .B \fB\-\-archlist=, \-a \fP │ │ │ │ │ -Add architectures to change the default from just comparing source packages. Note that you can use a wildcard \(dq*\(dq for all architectures. Can be specified multiple times. │ │ │ │ │ +Add architectures to change the default from just comparing source packages. Note that you can use a wildcard “*” for all architectures. Can be specified multiple times. │ │ │ │ │ .TP │ │ │ │ │ .B \fB\-\-size, \-s\fP │ │ │ │ │ Output additional data about the size of the changes. │ │ │ │ │ .TP │ │ │ │ │ .B \fB\-\-compare\-arch\fP │ │ │ │ │ Normally packages are just compared based on their name, this flag makes the comparison also use the arch. So foo.noarch and foo.x86_64 are considered to be a different packages. │ │ │ │ │ .TP │ │ │ │ │ ├── encoding │ │ │ │ │ │ @@ -1 +1 @@ │ │ │ │ │ │ -us-ascii │ │ │ │ │ │ +utf-8 │ │ │ ├── ./usr/share/man/man1/repomanage.1.gz │ │ │ │ ├── repomanage.1 │ │ │ │ │ @@ -33,30 +33,30 @@ │ │ │ │ │ .sp │ │ │ │ │ Manage a repository or a simple directory of rpm packages. │ │ │ │ │ .SH SYNOPSIS │ │ │ │ │ .sp │ │ │ │ │ \fBdnf repomanage [] [] \fP │ │ │ │ │ .SH DESCRIPTION │ │ │ │ │ .sp │ │ │ │ │ -\fIrepomanage\fP prints newest or older packages in a repository specified by for easy piping to xargs or similar programs. In case doesn\(aqt contain a valid repodata, it is searched for rpm packages which are then used instead. │ │ │ │ │ -If the repodata are present, \fIrepomanage\fP uses them as the source of truth, it doesn\(aqt verify that they match the present rpm packages. In fact, \fIrepomanage\fP can run with just the repodata, no rpm packages are needed. │ │ │ │ │ +\fIrepomanage\fP prints newest or older packages in a repository specified by for easy piping to xargs or similar programs. In case doesn’t contain a valid repodata, it is searched for rpm packages which are then used instead. │ │ │ │ │ +If the repodata are present, \fIrepomanage\fP uses them as the source of truth, it doesn’t verify that they match the present rpm packages. In fact, \fIrepomanage\fP can run with just the repodata, no rpm packages are needed. │ │ │ │ │ .sp │ │ │ │ │ In order to work correctly with modular packages, has to contain repodata with modular metadata. If modular content is present, \fIrepomanage\fP prints packages from newest or older stream versions in addition to newest or older non\-modular packages. │ │ │ │ │ .SS Options │ │ │ │ │ .sp │ │ │ │ │ All general DNF options are accepted, see \fIOptions\fP in \fBdnf(8)\fP for details. │ │ │ │ │ .sp │ │ │ │ │ The following options set what packages are displayed. These options are mutually exclusive, i.e. only one can be specified. If no option is specified, the newest packages are shown. │ │ │ │ │ .INDENT 0.0 │ │ │ │ │ .TP │ │ │ │ │ .B \fB\-\-old\fP │ │ │ │ │ Show older packages (for a package or a stream show all versions except the newest one). │ │ │ │ │ .TP │ │ │ │ │ .B \fB\-\-oldonly\fP │ │ │ │ │ -Show older packages (same as \-\-old, but exclude the newest packages even when it\(aqs included in the older stream versions). │ │ │ │ │ +Show older packages (same as –old, but exclude the newest packages even when it’s included in the older stream versions). │ │ │ │ │ .TP │ │ │ │ │ .B \fB\-\-new\fP │ │ │ │ │ Show newest packages. │ │ │ │ │ .UNINDENT │ │ │ │ │ .sp │ │ │ │ │ The following options control how packages are displayed in the output: │ │ │ │ │ .INDENT 0.0 │ │ │ │ │ @@ -75,15 +75,15 @@ │ │ │ │ │ .sp │ │ │ │ │ .EX │ │ │ │ │ dnf repomanage \-\-new . │ │ │ │ │ .EE │ │ │ │ │ .UNINDENT │ │ │ │ │ .UNINDENT │ │ │ │ │ .sp │ │ │ │ │ -Display 2 newest versions of each package in \(dqhome\(dq directory: │ │ │ │ │ +Display 2 newest versions of each package in “home” directory: │ │ │ │ │ .INDENT 0.0 │ │ │ │ │ .INDENT 3.5 │ │ │ │ │ .sp │ │ │ │ │ .EX │ │ │ │ │ dnf repomanage \-\-new \-\-keep 2 ~/ │ │ │ │ │ .EE │ │ │ │ │ .UNINDENT │ │ │ │ │ ├── encoding │ │ │ │ │ │ @@ -1 +1 @@ │ │ │ │ │ │ -us-ascii │ │ │ │ │ │ +utf-8 │ │ │ ├── ./usr/share/man/man1/reposync.1.gz │ │ │ │ ├── reposync.1 │ │ │ │ │ @@ -47,16 +47,16 @@ │ │ │ │ │ Download only packages of given architectures (default is all architectures). Can be used multiple times. │ │ │ │ │ .TP │ │ │ │ │ .B \fB\-\-delete\fP │ │ │ │ │ Delete local packages no longer present in repository. │ │ │ │ │ .TP │ │ │ │ │ .B \fB\-\-download\-metadata\fP │ │ │ │ │ Download all repository metadata. Downloaded copy is instantly usable as a repository, no need to run createrepo_c │ │ │ │ │ -on it. When the option is used with \fI\-\-newest\-only\fP, only latest packages will be downloaded, but metadata will │ │ │ │ │ -still contain older packages. It might be useful to update metadata using \fIcreaterepo_c \-\-update\fP to remove │ │ │ │ │ +on it. When the option is used with \fI–newest\-only\fP, only latest packages will be downloaded, but metadata will │ │ │ │ │ +still contain older packages. It might be useful to update metadata using \fIcreaterepo_c –update\fP to 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. │ │ │ │ │ .TP │ │ │ │ │ .B \fB\-g, \-\-gpgcheck\fP │ │ │ │ │ Remove packages that fail GPG signature checking after downloading. Exit code is \fB1\fP if at least one package was removed. │ │ │ │ │ Note that for repositories with \fBgpgcheck=0\fP set in their configuration the GPG signature is not checked even with this option used. │ │ │ │ │ .TP │ │ │ │ │ @@ -66,42 +66,42 @@ │ │ │ │ │ .B \fB\-\-metadata\-path\fP │ │ │ │ │ Root path under which the downloaded metadata are stored. It defaults to \fB\-\-download\-path\fP value if not given. │ │ │ │ │ .TP │ │ │ │ │ .B \fB\-n, \-\-newest\-only\fP │ │ │ │ │ Download only newest packages per\-repo. │ │ │ │ │ .TP │ │ │ │ │ .B \fB\-\-norepopath\fP │ │ │ │ │ -Don\(aqt add the reponame to the download path. Can only be used when syncing a single repository (default is to add the reponame). │ │ │ │ │ +Don’t add the reponame to the download path. Can only be used when syncing a single repository (default is to add the reponame). │ │ │ │ │ .TP │ │ │ │ │ .B \fB\-p , \-\-download\-path=\fP │ │ │ │ │ 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. │ │ │ │ │ .TP │ │ │ │ │ .B \fB\-\-safe\-write\-path\fP │ │ │ │ │ -Specify the filesystem path prefix under which the reposync is allowed to write. If not specified it defaults to download path of the repository. Useful for repositories that use relative locations of packages out of repository directory (e.g. \(dq../packages_store/foo.rpm\(dq). Use with care, any file under the \fBsafe\-write\-path\fP can be overwritten. Can be only used when syncing a single repository. │ │ │ │ │ +Specify the filesystem path prefix under which the reposync is allowed to write. If not specified it defaults to download path of the repository. Useful for repositories that use relative locations of packages out of repository directory (e.g. “../packages_store/foo.rpm”). Use with care, any file under the \fBsafe\-write\-path\fP can be overwritten. Can be only used when syncing a single repository. │ │ │ │ │ .TP │ │ │ │ │ .B \fB\-\-remote\-time\fP │ │ │ │ │ Try to set the timestamps of the downloaded files to those on the remote side. │ │ │ │ │ .TP │ │ │ │ │ .B \fB\-\-source\fP │ │ │ │ │ Download only source packages. │ │ │ │ │ .TP │ │ │ │ │ .B \fB\-u, \-\-urls\fP │ │ │ │ │ -Just print urls of what would be downloaded, don\(aqt download. │ │ │ │ │ +Just print urls of what would be downloaded, don’t download. │ │ │ │ │ .UNINDENT │ │ │ │ │ .SH EXAMPLES │ │ │ │ │ .INDENT 0.0 │ │ │ │ │ .TP │ │ │ │ │ .B \fBdnf reposync \-\-repoid=the_repo\fP │ │ │ │ │ -Synchronize all packages from the repository with id \(dqthe_repo\(dq. The synchronized copy is saved in \(dqthe_repo\(dq subdirectory of the current working directory. │ │ │ │ │ +Synchronize all packages from the repository with id “the_repo”. The synchronized copy is saved in “the_repo” subdirectory of the current working directory. │ │ │ │ │ .TP │ │ │ │ │ .B \fBdnf reposync \-p /my/repos/path \-\-repoid=the_repo\fP │ │ │ │ │ -Synchronize all packages from the repository with id \(dqthe_repo\(dq. In this case files are saved in \(dq/my/repos/path/the_repo\(dq directory. │ │ │ │ │ +Synchronize all packages from the repository with id “the_repo”. In this case files are saved in “/my/repos/path/the_repo” directory. │ │ │ │ │ .TP │ │ │ │ │ .B \fBdnf reposync \-\-repoid=the_repo \-\-download\-metadata\fP │ │ │ │ │ -Synchronize all packages and metadata from \(dqthe_repo\(dq repository. │ │ │ │ │ +Synchronize all packages and metadata from “the_repo” repository. │ │ │ │ │ .UNINDENT │ │ │ │ │ .sp │ │ │ │ │ Repository synchronized with \fB\-\-download\-metadata\fP option can be directly used in DNF for example by using \fB\-\-repofrompath\fP option: │ │ │ │ │ .sp │ │ │ │ │ \fBdnf \-\-repofrompath=syncedrepo,the_repo \-\-repoid=syncedrepo list \-\-available\fP │ │ │ │ │ .SH SEE ALSO │ │ │ │ │ .INDENT 0.0 │ │ │ │ │ ├── encoding │ │ │ │ │ │ @@ -1 +1 @@ │ │ │ │ │ │ -us-ascii │ │ │ │ │ │ +utf-8 │ │ │ ├── ./usr/share/man/man5/yum-versionlock.conf.5.gz │ │ │ │ ├── yum-versionlock.conf.5 │ │ │ │ │ @@ -31,29 +31,29 @@ │ │ │ │ │ .SH NAME │ │ │ │ │ yum-versionlock.conf \- redirecting to DNF versionlock Plugin │ │ │ │ │ .SH DESCRIPTION │ │ │ │ │ .sp │ │ │ │ │ \fIversionlock\fP is a plugin that takes a set of names and versions for packages and │ │ │ │ │ excludes all other versions of those packages. This allows you to protect │ │ │ │ │ packages from being updated by newer versions. Alternately, it accepts a specific │ │ │ │ │ -package version to exclude from updates, e.g. for when it\(aqs necessary to skip a │ │ │ │ │ +package version to exclude from updates, e.g. for when it’s necessary to skip a │ │ │ │ │ specific release of a package that has known issues. │ │ │ │ │ .sp │ │ │ │ │ The plugin provides a command \fIversionlock\fP which allows you to view and edit the │ │ │ │ │ list of locked packages easily. │ │ │ │ │ .sp │ │ │ │ │ The plugin will walk each line of the versionlock file, and parse out the name and │ │ │ │ │ version of the package. It will then exclude any package by that name that │ │ │ │ │ -doesn\(aqt match one of the versions listed within the file. This is basically │ │ │ │ │ -the same as using \fIdnf \-\-exclude\fP for the package name itself (as you cannot exclude │ │ │ │ │ +doesn’t match one of the versions listed within the file. This is basically │ │ │ │ │ +the same as using \fIdnf –exclude\fP for the package name itself (as you cannot exclude │ │ │ │ │ installed packages), but dnf will still see the versions you have │ │ │ │ │ installed/versionlocked as available so that \fIdnf reinstall\fP will still │ │ │ │ │ work, etc. │ │ │ │ │ .sp │ │ │ │ │ -It can also work in the opposite way, like a fast exclude, by prefixing a \(aq!\(aq │ │ │ │ │ +It can also work in the opposite way, like a fast exclude, by prefixing a ‘!’ │ │ │ │ │ character to the version recorded in the lock list file. This specifically │ │ │ │ │ excludes a package that matches the version exactly. │ │ │ │ │ .sp │ │ │ │ │ Note the versionlock plugin does not apply any excludes in non\-transactional │ │ │ │ │ operations like \fIrepoquery\fP, \fIlist\fP, \fIinfo\fP, etc. │ │ │ │ │ .SH SYNOPSIS │ │ │ │ │ .sp │ │ │ │ │ @@ -156,15 +156,15 @@ │ │ │ │ │ .INDENT 0.0 │ │ │ │ │ .TP │ │ │ │ │ .B \fBlocklist\fP │ │ │ │ │ This option is a string that points to the file which has the versionlock │ │ │ │ │ information in it. Note that the file has to exist (or the versionlock plugin │ │ │ │ │ will make dnf exit). However, it can be empty. │ │ │ │ │ .sp │ │ │ │ │ -The file takes entries in the format of \fB\fP (optionally prefixed with \(aq!\(aq for │ │ │ │ │ +The file takes entries in the format of \fB\fP (optionally prefixed with ‘!’ for │ │ │ │ │ excludes). │ │ │ │ │ See \fISpecifying packages\fP in \fBdnf(8)\fP for details. │ │ │ │ │ .UNINDENT │ │ │ │ │ .SH NOTES │ │ │ │ │ .sp │ │ │ │ │ A specified package does not have to exist within the available cache of repository data │ │ │ │ │ to be considered valid for locking or exclusion. This is by design, to accommodate use │ │ │ │ │ ├── encoding │ │ │ │ │ │ @@ -1 +1 @@ │ │ │ │ │ │ -us-ascii │ │ │ │ │ │ +utf-8 │ │ │ ├── ./usr/share/man/man8/dnf4-repodiff.8.gz │ │ │ │ ├── dnf4-repodiff.8 │ │ │ │ │ @@ -46,15 +46,15 @@ │ │ │ │ │ .B \fB\-\-repo\-old=, \-o \fP │ │ │ │ │ Add a \fB\fP as an old repository. It is possible to be used in conjunction with \fB\-\-repofrompath\fP option. Can be specified multiple times. │ │ │ │ │ .TP │ │ │ │ │ .B \fB\-\-repo\-new=, \-n \fP │ │ │ │ │ Add a \fB\fP as a new repository. Can be specified multiple times. │ │ │ │ │ .TP │ │ │ │ │ .B \fB\-\-archlist=, \-a \fP │ │ │ │ │ -Add architectures to change the default from just comparing source packages. Note that you can use a wildcard \(dq*\(dq for all architectures. Can be specified multiple times. │ │ │ │ │ +Add architectures to change the default from just comparing source packages. Note that you can use a wildcard “*” for all architectures. Can be specified multiple times. │ │ │ │ │ .TP │ │ │ │ │ .B \fB\-\-size, \-s\fP │ │ │ │ │ Output additional data about the size of the changes. │ │ │ │ │ .TP │ │ │ │ │ .B \fB\-\-compare\-arch\fP │ │ │ │ │ Normally packages are just compared based on their name, this flag makes the comparison also use the arch. So foo.noarch and foo.x86_64 are considered to be a different packages. │ │ │ │ │ .TP │ │ │ │ │ ├── encoding │ │ │ │ │ │ @@ -1 +1 @@ │ │ │ │ │ │ -us-ascii │ │ │ │ │ │ +utf-8 │ │ │ ├── ./usr/share/man/man8/dnf4-repomanage.8.gz │ │ │ │ ├── dnf4-repomanage.8 │ │ │ │ │ @@ -33,30 +33,30 @@ │ │ │ │ │ .sp │ │ │ │ │ Manage a repository or a simple directory of rpm packages. │ │ │ │ │ .SH SYNOPSIS │ │ │ │ │ .sp │ │ │ │ │ \fBdnf repomanage [] [] \fP │ │ │ │ │ .SH DESCRIPTION │ │ │ │ │ .sp │ │ │ │ │ -\fIrepomanage\fP prints newest or older packages in a repository specified by for easy piping to xargs or similar programs. In case doesn\(aqt contain a valid repodata, it is searched for rpm packages which are then used instead. │ │ │ │ │ -If the repodata are present, \fIrepomanage\fP uses them as the source of truth, it doesn\(aqt verify that they match the present rpm packages. In fact, \fIrepomanage\fP can run with just the repodata, no rpm packages are needed. │ │ │ │ │ +\fIrepomanage\fP prints newest or older packages in a repository specified by for easy piping to xargs or similar programs. In case doesn’t contain a valid repodata, it is searched for rpm packages which are then used instead. │ │ │ │ │ +If the repodata are present, \fIrepomanage\fP uses them as the source of truth, it doesn’t verify that they match the present rpm packages. In fact, \fIrepomanage\fP can run with just the repodata, no rpm packages are needed. │ │ │ │ │ .sp │ │ │ │ │ In order to work correctly with modular packages, has to contain repodata with modular metadata. If modular content is present, \fIrepomanage\fP prints packages from newest or older stream versions in addition to newest or older non\-modular packages. │ │ │ │ │ .SS Options │ │ │ │ │ .sp │ │ │ │ │ All general DNF options are accepted, see \fIOptions\fP in \fBdnf(8)\fP for details. │ │ │ │ │ .sp │ │ │ │ │ The following options set what packages are displayed. These options are mutually exclusive, i.e. only one can be specified. If no option is specified, the newest packages are shown. │ │ │ │ │ .INDENT 0.0 │ │ │ │ │ .TP │ │ │ │ │ .B \fB\-\-old\fP │ │ │ │ │ Show older packages (for a package or a stream show all versions except the newest one). │ │ │ │ │ .TP │ │ │ │ │ .B \fB\-\-oldonly\fP │ │ │ │ │ -Show older packages (same as \-\-old, but exclude the newest packages even when it\(aqs included in the older stream versions). │ │ │ │ │ +Show older packages (same as –old, but exclude the newest packages even when it’s included in the older stream versions). │ │ │ │ │ .TP │ │ │ │ │ .B \fB\-\-new\fP │ │ │ │ │ Show newest packages. │ │ │ │ │ .UNINDENT │ │ │ │ │ .sp │ │ │ │ │ The following options control how packages are displayed in the output: │ │ │ │ │ .INDENT 0.0 │ │ │ │ │ @@ -75,15 +75,15 @@ │ │ │ │ │ .sp │ │ │ │ │ .EX │ │ │ │ │ dnf repomanage \-\-new . │ │ │ │ │ .EE │ │ │ │ │ .UNINDENT │ │ │ │ │ .UNINDENT │ │ │ │ │ .sp │ │ │ │ │ -Display 2 newest versions of each package in \(dqhome\(dq directory: │ │ │ │ │ +Display 2 newest versions of each package in “home” directory: │ │ │ │ │ .INDENT 0.0 │ │ │ │ │ .INDENT 3.5 │ │ │ │ │ .sp │ │ │ │ │ .EX │ │ │ │ │ dnf repomanage \-\-new \-\-keep 2 ~/ │ │ │ │ │ .EE │ │ │ │ │ .UNINDENT │ │ │ │ │ ├── encoding │ │ │ │ │ │ @@ -1 +1 @@ │ │ │ │ │ │ -us-ascii │ │ │ │ │ │ +utf-8 │ │ │ ├── ./usr/share/man/man8/dnf4-reposync.8.gz │ │ │ │ ├── dnf4-reposync.8 │ │ │ │ │ @@ -47,16 +47,16 @@ │ │ │ │ │ Download only packages of given architectures (default is all architectures). Can be used multiple times. │ │ │ │ │ .TP │ │ │ │ │ .B \fB\-\-delete\fP │ │ │ │ │ Delete local packages no longer present in repository. │ │ │ │ │ .TP │ │ │ │ │ .B \fB\-\-download\-metadata\fP │ │ │ │ │ Download all repository metadata. Downloaded copy is instantly usable as a repository, no need to run createrepo_c │ │ │ │ │ -on it. When the option is used with \fI\-\-newest\-only\fP, only latest packages will be downloaded, but metadata will │ │ │ │ │ -still contain older packages. It might be useful to update metadata using \fIcreaterepo_c \-\-update\fP to remove │ │ │ │ │ +on it. When the option is used with \fI–newest\-only\fP, only latest packages will be downloaded, but metadata will │ │ │ │ │ +still contain older packages. It might be useful to update metadata using \fIcreaterepo_c –update\fP to 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. │ │ │ │ │ .TP │ │ │ │ │ .B \fB\-g, \-\-gpgcheck\fP │ │ │ │ │ Remove packages that fail GPG signature checking after downloading. Exit code is \fB1\fP if at least one package was removed. │ │ │ │ │ Note that for repositories with \fBgpgcheck=0\fP set in their configuration the GPG signature is not checked even with this option used. │ │ │ │ │ .TP │ │ │ │ │ @@ -66,42 +66,42 @@ │ │ │ │ │ .B \fB\-\-metadata\-path\fP │ │ │ │ │ Root path under which the downloaded metadata are stored. It defaults to \fB\-\-download\-path\fP value if not given. │ │ │ │ │ .TP │ │ │ │ │ .B \fB\-n, \-\-newest\-only\fP │ │ │ │ │ Download only newest packages per\-repo. │ │ │ │ │ .TP │ │ │ │ │ .B \fB\-\-norepopath\fP │ │ │ │ │ -Don\(aqt add the reponame to the download path. Can only be used when syncing a single repository (default is to add the reponame). │ │ │ │ │ +Don’t add the reponame to the download path. Can only be used when syncing a single repository (default is to add the reponame). │ │ │ │ │ .TP │ │ │ │ │ .B \fB\-p , \-\-download\-path=\fP │ │ │ │ │ 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. │ │ │ │ │ .TP │ │ │ │ │ .B \fB\-\-safe\-write\-path\fP │ │ │ │ │ -Specify the filesystem path prefix under which the reposync is allowed to write. If not specified it defaults to download path of the repository. Useful for repositories that use relative locations of packages out of repository directory (e.g. \(dq../packages_store/foo.rpm\(dq). Use with care, any file under the \fBsafe\-write\-path\fP can be overwritten. Can be only used when syncing a single repository. │ │ │ │ │ +Specify the filesystem path prefix under which the reposync is allowed to write. If not specified it defaults to download path of the repository. Useful for repositories that use relative locations of packages out of repository directory (e.g. “../packages_store/foo.rpm”). Use with care, any file under the \fBsafe\-write\-path\fP can be overwritten. Can be only used when syncing a single repository. │ │ │ │ │ .TP │ │ │ │ │ .B \fB\-\-remote\-time\fP │ │ │ │ │ Try to set the timestamps of the downloaded files to those on the remote side. │ │ │ │ │ .TP │ │ │ │ │ .B \fB\-\-source\fP │ │ │ │ │ Download only source packages. │ │ │ │ │ .TP │ │ │ │ │ .B \fB\-u, \-\-urls\fP │ │ │ │ │ -Just print urls of what would be downloaded, don\(aqt download. │ │ │ │ │ +Just print urls of what would be downloaded, don’t download. │ │ │ │ │ .UNINDENT │ │ │ │ │ .SH EXAMPLES │ │ │ │ │ .INDENT 0.0 │ │ │ │ │ .TP │ │ │ │ │ .B \fBdnf reposync \-\-repoid=the_repo\fP │ │ │ │ │ -Synchronize all packages from the repository with id \(dqthe_repo\(dq. The synchronized copy is saved in \(dqthe_repo\(dq subdirectory of the current working directory. │ │ │ │ │ +Synchronize all packages from the repository with id “the_repo”. The synchronized copy is saved in “the_repo” subdirectory of the current working directory. │ │ │ │ │ .TP │ │ │ │ │ .B \fBdnf reposync \-p /my/repos/path \-\-repoid=the_repo\fP │ │ │ │ │ -Synchronize all packages from the repository with id \(dqthe_repo\(dq. In this case files are saved in \(dq/my/repos/path/the_repo\(dq directory. │ │ │ │ │ +Synchronize all packages from the repository with id “the_repo”. In this case files are saved in “/my/repos/path/the_repo” directory. │ │ │ │ │ .TP │ │ │ │ │ .B \fBdnf reposync \-\-repoid=the_repo \-\-download\-metadata\fP │ │ │ │ │ -Synchronize all packages and metadata from \(dqthe_repo\(dq repository. │ │ │ │ │ +Synchronize all packages and metadata from “the_repo” repository. │ │ │ │ │ .UNINDENT │ │ │ │ │ .sp │ │ │ │ │ Repository synchronized with \fB\-\-download\-metadata\fP option can be directly used in DNF for example by using \fB\-\-repofrompath\fP option: │ │ │ │ │ .sp │ │ │ │ │ \fBdnf \-\-repofrompath=syncedrepo,the_repo \-\-repoid=syncedrepo list \-\-available\fP │ │ │ │ │ .SH SEE ALSO │ │ │ │ │ .INDENT 0.0 │ │ │ │ │ ├── encoding │ │ │ │ │ │ @@ -1 +1 @@ │ │ │ │ │ │ -us-ascii │ │ │ │ │ │ +utf-8 │ │ │ ├── ./usr/share/man/man8/dnf4-system-upgrade.8.gz │ │ │ │ ├── dnf4-system-upgrade.8 │ │ │ │ │ @@ -128,15 +128,15 @@ │ │ │ │ │ upgrades are completed, instead of restarting. │ │ │ │ │ .TP │ │ │ │ │ .B \fB\-\-number\fP │ │ │ │ │ Applied with \fBlog\fP subcommand will show the log specified by the number. │ │ │ │ │ .UNINDENT │ │ │ │ │ .SH NOTES │ │ │ │ │ .sp │ │ │ │ │ -\fBdnf system\-upgrade reboot\fP does not create a \(dqSystem Upgrade\(dq boot item. The │ │ │ │ │ +\fBdnf system\-upgrade reboot\fP does not create a “System Upgrade” boot item. The │ │ │ │ │ upgrade will start regardless of which boot item is chosen. │ │ │ │ │ .sp │ │ │ │ │ The \fBDNF_SYSTEM_UPGRADE_NO_REBOOT\fP environment variable can be set to a │ │ │ │ │ non\-empty value to disable the actual reboot performed by \fBsystem\-upgrade\fP │ │ │ │ │ (e.g. for testing purposes). │ │ │ │ │ .sp │ │ │ │ │ Since this is a DNF plugin, options accepted by \fBdnf\fP are also valid here, │ │ │ │ │ @@ -182,15 +182,15 @@ │ │ │ │ │ \fBdnf system\-upgrade log \-\-number=\-1\fP (if applicable) in your bug reports. │ │ │ │ │ .sp │ │ │ │ │ Problems with dependency solving during download are best reported to the │ │ │ │ │ maintainers of the package(s) with the dependency problems. │ │ │ │ │ .sp │ │ │ │ │ Similarly, problems encountered on your system after the upgrade completes │ │ │ │ │ should be reported to the maintainers of the affected components. In other │ │ │ │ │ -words: if (for example) KDE stops working, it\(aqs best if you report that to │ │ │ │ │ +words: if (for example) KDE stops working, it’s best if you report that to │ │ │ │ │ the KDE maintainers. │ │ │ │ │ .SH SEE ALSO │ │ │ │ │ .sp │ │ │ │ │ \fBdnf(8)\fP, │ │ │ │ │ \fBdnf.conf(5)\fP, │ │ │ │ │ \fBjournalctl(1)\fP\&. │ │ │ │ │ .SS Project homepage │ │ │ ├── ./usr/share/man/man8/dnf4-versionlock.8.gz │ │ │ │ ├── dnf4-versionlock.8 │ │ │ │ │ @@ -31,29 +31,29 @@ │ │ │ │ │ .SH NAME │ │ │ │ │ dnf4-versionlock \- DNF versionlock Plugin │ │ │ │ │ .SH DESCRIPTION │ │ │ │ │ .sp │ │ │ │ │ \fIversionlock\fP is a plugin that takes a set of names and versions for packages and │ │ │ │ │ excludes all other versions of those packages. This allows you to protect │ │ │ │ │ packages from being updated by newer versions. Alternately, it accepts a specific │ │ │ │ │ -package version to exclude from updates, e.g. for when it\(aqs necessary to skip a │ │ │ │ │ +package version to exclude from updates, e.g. for when it’s necessary to skip a │ │ │ │ │ specific release of a package that has known issues. │ │ │ │ │ .sp │ │ │ │ │ The plugin provides a command \fIversionlock\fP which allows you to view and edit the │ │ │ │ │ list of locked packages easily. │ │ │ │ │ .sp │ │ │ │ │ The plugin will walk each line of the versionlock file, and parse out the name and │ │ │ │ │ version of the package. It will then exclude any package by that name that │ │ │ │ │ -doesn\(aqt match one of the versions listed within the file. This is basically │ │ │ │ │ -the same as using \fIdnf \-\-exclude\fP for the package name itself (as you cannot exclude │ │ │ │ │ +doesn’t match one of the versions listed within the file. This is basically │ │ │ │ │ +the same as using \fIdnf –exclude\fP for the package name itself (as you cannot exclude │ │ │ │ │ installed packages), but dnf will still see the versions you have │ │ │ │ │ installed/versionlocked as available so that \fIdnf reinstall\fP will still │ │ │ │ │ work, etc. │ │ │ │ │ .sp │ │ │ │ │ -It can also work in the opposite way, like a fast exclude, by prefixing a \(aq!\(aq │ │ │ │ │ +It can also work in the opposite way, like a fast exclude, by prefixing a ‘!’ │ │ │ │ │ character to the version recorded in the lock list file. This specifically │ │ │ │ │ excludes a package that matches the version exactly. │ │ │ │ │ .sp │ │ │ │ │ Note the versionlock plugin does not apply any excludes in non\-transactional │ │ │ │ │ operations like \fIrepoquery\fP, \fIlist\fP, \fIinfo\fP, etc. │ │ │ │ │ .SH SYNOPSIS │ │ │ │ │ .sp │ │ │ │ │ @@ -156,15 +156,15 @@ │ │ │ │ │ .INDENT 0.0 │ │ │ │ │ .TP │ │ │ │ │ .B \fBlocklist\fP │ │ │ │ │ This option is a string that points to the file which has the versionlock │ │ │ │ │ information in it. Note that the file has to exist (or the versionlock plugin │ │ │ │ │ will make dnf exit). However, it can be empty. │ │ │ │ │ .sp │ │ │ │ │ -The file takes entries in the format of \fB\fP (optionally prefixed with \(aq!\(aq for │ │ │ │ │ +The file takes entries in the format of \fB\fP (optionally prefixed with ‘!’ for │ │ │ │ │ excludes). │ │ │ │ │ See \fISpecifying packages\fP in \fBdnf(8)\fP for details. │ │ │ │ │ .UNINDENT │ │ │ │ │ .SH NOTES │ │ │ │ │ .sp │ │ │ │ │ A specified package does not have to exist within the available cache of repository data │ │ │ │ │ to be considered valid for locking or exclusion. This is by design, to accommodate use │ │ │ │ │ ├── encoding │ │ │ │ │ │ @@ -1 +1 @@ │ │ │ │ │ │ -us-ascii │ │ │ │ │ │ +utf-8 │ │ │ ├── ./usr/share/man/man8/yum-versionlock.8.gz │ │ │ │ ├── yum-versionlock.8 │ │ │ │ │ @@ -31,29 +31,29 @@ │ │ │ │ │ .SH NAME │ │ │ │ │ yum-versionlock \- redirecting to DNF versionlock Plugin │ │ │ │ │ .SH DESCRIPTION │ │ │ │ │ .sp │ │ │ │ │ \fIversionlock\fP is a plugin that takes a set of names and versions for packages and │ │ │ │ │ excludes all other versions of those packages. This allows you to protect │ │ │ │ │ packages from being updated by newer versions. Alternately, it accepts a specific │ │ │ │ │ -package version to exclude from updates, e.g. for when it\(aqs necessary to skip a │ │ │ │ │ +package version to exclude from updates, e.g. for when it’s necessary to skip a │ │ │ │ │ specific release of a package that has known issues. │ │ │ │ │ .sp │ │ │ │ │ The plugin provides a command \fIversionlock\fP which allows you to view and edit the │ │ │ │ │ list of locked packages easily. │ │ │ │ │ .sp │ │ │ │ │ The plugin will walk each line of the versionlock file, and parse out the name and │ │ │ │ │ version of the package. It will then exclude any package by that name that │ │ │ │ │ -doesn\(aqt match one of the versions listed within the file. This is basically │ │ │ │ │ -the same as using \fIdnf \-\-exclude\fP for the package name itself (as you cannot exclude │ │ │ │ │ +doesn’t match one of the versions listed within the file. This is basically │ │ │ │ │ +the same as using \fIdnf –exclude\fP for the package name itself (as you cannot exclude │ │ │ │ │ installed packages), but dnf will still see the versions you have │ │ │ │ │ installed/versionlocked as available so that \fIdnf reinstall\fP will still │ │ │ │ │ work, etc. │ │ │ │ │ .sp │ │ │ │ │ -It can also work in the opposite way, like a fast exclude, by prefixing a \(aq!\(aq │ │ │ │ │ +It can also work in the opposite way, like a fast exclude, by prefixing a ‘!’ │ │ │ │ │ character to the version recorded in the lock list file. This specifically │ │ │ │ │ excludes a package that matches the version exactly. │ │ │ │ │ .sp │ │ │ │ │ Note the versionlock plugin does not apply any excludes in non\-transactional │ │ │ │ │ operations like \fIrepoquery\fP, \fIlist\fP, \fIinfo\fP, etc. │ │ │ │ │ .SH SYNOPSIS │ │ │ │ │ .sp │ │ │ │ │ @@ -156,15 +156,15 @@ │ │ │ │ │ .INDENT 0.0 │ │ │ │ │ .TP │ │ │ │ │ .B \fBlocklist\fP │ │ │ │ │ This option is a string that points to the file which has the versionlock │ │ │ │ │ information in it. Note that the file has to exist (or the versionlock plugin │ │ │ │ │ will make dnf exit). However, it can be empty. │ │ │ │ │ .sp │ │ │ │ │ -The file takes entries in the format of \fB\fP (optionally prefixed with \(aq!\(aq for │ │ │ │ │ +The file takes entries in the format of \fB\fP (optionally prefixed with ‘!’ for │ │ │ │ │ excludes). │ │ │ │ │ See \fISpecifying packages\fP in \fBdnf(8)\fP for details. │ │ │ │ │ .UNINDENT │ │ │ │ │ .SH NOTES │ │ │ │ │ .sp │ │ │ │ │ A specified package does not have to exist within the available cache of repository data │ │ │ │ │ to be considered valid for locking or exclusion. This is by design, to accommodate use │ │ │ │ │ ├── encoding │ │ │ │ │ │ @@ -1 +1 @@ │ │ │ │ │ │ -us-ascii │ │ │ │ │ │ +utf-8