{"diffoscope-json-version": 1, "source1": "/srv/reproducible-results/rbuild-debian/r-b-build.ntANyAPQ/b1/dnf-plugins-core_4.9.0-1_armhf.changes", "source2": "/srv/reproducible-results/rbuild-debian/r-b-build.ntANyAPQ/b2/dnf-plugins-core_4.9.0-1_armhf.changes", "unified_diff": null, "details": [{"source1": "Files", "source2": "Files", "unified_diff": "@@ -1,2 +1,2 @@\n \n- 4748c5ae2abacb5605f65401a299bfc6 245472 admin optional dnf-plugins-core_4.9.0-1_all.deb\n+ 190b26d1552650f6e88258f68a595635 244252 admin optional dnf-plugins-core_4.9.0-1_all.deb\n"}, {"source1": "dnf-plugins-core_4.9.0-1_all.deb", "source2": "dnf-plugins-core_4.9.0-1_all.deb", "unified_diff": null, "details": [{"source1": "file list", "source2": "file list", "unified_diff": "@@ -1,3 +1,3 @@\n -rw-r--r-- 0 0 0 4 2024-08-22 14:02:01.000000 debian-binary\n--rw-r--r-- 0 0 0 4288 2024-08-22 14:02:01.000000 control.tar.xz\n--rw-r--r-- 0 0 0 240992 2024-08-22 14:02:01.000000 data.tar.xz\n+-rw-r--r-- 0 0 0 4284 2024-08-22 14:02:01.000000 control.tar.xz\n+-rw-r--r-- 0 0 0 239776 2024-08-22 14:02:01.000000 data.tar.xz\n"}, {"source1": "control.tar.xz", "source2": "control.tar.xz", "unified_diff": null, "details": [{"source1": "control.tar", "source2": "control.tar", "unified_diff": null, "details": [{"source1": "./md5sums", "source2": "./md5sums", "unified_diff": null, "details": [{"source1": "./md5sums", "source2": "./md5sums", "comments": ["Files differ"], "unified_diff": null}]}]}]}, {"source1": "data.tar.xz", "source2": "data.tar.xz", "unified_diff": null, "details": [{"source1": "data.tar", "source2": "data.tar", "unified_diff": null, "details": [{"source1": "file list", "source2": "file list", "unified_diff": "@@ -159,26 +159,26 @@\n -rw-r--r-- 0 root (0) root (0) 904 2024-08-22 14:02:01.000000 ./usr/share/man/man1/debuginfo-install.1.gz\n -rw-r--r-- 0 root (0) root (0) 1291 2024-08-22 14:02:01.000000 ./usr/share/man/man1/dnf-utils.1.gz\n -rw-r--r-- 0 root (0) root (0) 1649 2024-08-22 14:02:01.000000 ./usr/share/man/man1/needs-restarting.1.gz\n -rw-r--r-- 0 root (0) root (0) 883 2024-08-22 14:02:01.000000 ./usr/share/man/man1/package-cleanup.1.gz\n -rw-r--r-- 0 root (0) root (0) 773 2024-08-22 14:02:01.000000 ./usr/share/man/man1/repo-graph.1.gz\n -rw-r--r-- 0 root (0) root (0) 1024 2024-08-22 14:02:01.000000 ./usr/share/man/man1/repoclosure.1.gz\n -rw-r--r-- 0 root (0) root (0) 1205 2024-08-22 14:02:01.000000 ./usr/share/man/man1/repodiff.1.gz\n--rw-r--r-- 0 root (0) root (0) 1278 2024-08-22 14:02:01.000000 ./usr/share/man/man1/repomanage.1.gz\n--rw-r--r-- 0 root (0) root (0) 1882 2024-08-22 14:02:01.000000 ./usr/share/man/man1/reposync.1.gz\n+-rw-r--r-- 0 root (0) root (0) 1293 2024-08-22 14:02:01.000000 ./usr/share/man/man1/repomanage.1.gz\n+-rw-r--r-- 0 root (0) root (0) 1896 2024-08-22 14:02:01.000000 ./usr/share/man/man1/reposync.1.gz\n -rw-r--r-- 0 root (0) root (0) 1199 2024-08-22 14:02:01.000000 ./usr/share/man/man1/yum-builddep.1.gz\n -rw-r--r-- 0 root (0) root (0) 896 2024-08-22 14:02:01.000000 ./usr/share/man/man1/yum-changelog.1.gz\n -rw-r--r-- 0 root (0) root (0) 1522 2024-08-22 14:02:01.000000 ./usr/share/man/man1/yum-config-manager.1.gz\n -rw-r--r-- 0 root (0) root (0) 1285 2024-08-22 14:02:01.000000 ./usr/share/man/man1/yum-debug-dump.1.gz\n -rw-r--r-- 0 root (0) root (0) 1289 2024-08-22 14:02:01.000000 ./usr/share/man/man1/yum-debug-restore.1.gz\n -rw-r--r-- 0 root (0) root (0) 1588 2024-08-22 14:02:01.000000 ./usr/share/man/man1/yum-groups-manager.1.gz\n -rw-r--r-- 0 root (0) root (0) 1292 2024-08-22 14:02:01.000000 ./usr/share/man/man1/yum-utils.1.gz\n -rw-r--r-- 0 root (0) root (0) 1289 2024-08-22 14:02:01.000000 ./usr/share/man/man1/yumdownloader.1.gz\n drwxr-xr-x 0 root (0) root (0) 0 2024-08-22 14:02:01.000000 ./usr/share/man/man5/\n--rw-r--r-- 0 root (0) root (0) 2292 2024-08-22 14:02:01.000000 ./usr/share/man/man5/yum-versionlock.conf.5.gz\n+-rw-r--r-- 0 root (0) root (0) 2307 2024-08-22 14:02:01.000000 ./usr/share/man/man5/yum-versionlock.conf.5.gz\n drwxr-xr-x 0 root (0) root (0) 0 2024-08-22 14:02:01.000000 ./usr/share/man/man8/\n -rw-r--r-- 0 root (0) root (0) 1190 2024-08-22 14:02:01.000000 ./usr/share/man/man8/dnf4-builddep.8.gz\n -rw-r--r-- 0 root (0) root (0) 887 2024-08-22 14:02:01.000000 ./usr/share/man/man8/dnf4-changelog.8.gz\n -rw-r--r-- 0 root (0) root (0) 1513 2024-08-22 14:02:01.000000 ./usr/share/man/man8/dnf4-config-manager.8.gz\n -rw-r--r-- 0 root (0) root (0) 1619 2024-08-22 14:02:01.000000 ./usr/share/man/man8/dnf4-copr.8.gz\n -rw-r--r-- 0 root (0) root (0) 1269 2024-08-22 14:02:01.000000 ./usr/share/man/man8/dnf4-debug.8.gz\n -rw-r--r-- 0 root (0) root (0) 900 2024-08-22 14:02:01.000000 ./usr/share/man/man8/dnf4-debuginfo-install.8.gz\n@@ -191,14 +191,14 @@\n -rw-r--r-- 0 root (0) root (0) 1481 2024-08-22 14:02:01.000000 ./usr/share/man/man8/dnf4-modulesync.8.gz\n -rw-r--r-- 0 root (0) root (0) 1653 2024-08-22 14:02:01.000000 ./usr/share/man/man8/dnf4-needs-restarting.8.gz\n -rw-r--r-- 0 root (0) root (0) 1790 2024-08-22 14:02:01.000000 ./usr/share/man/man8/dnf4-post-transaction-actions.8.gz\n -rw-r--r-- 0 root (0) root (0) 1787 2024-08-22 14:02:01.000000 ./usr/share/man/man8/dnf4-pre-transaction-actions.8.gz\n -rw-r--r-- 0 root (0) root (0) 1021 2024-08-22 14:02:01.000000 ./usr/share/man/man8/dnf4-repoclosure.8.gz\n -rw-r--r-- 0 root (0) root (0) 1202 2024-08-22 14:02:01.000000 ./usr/share/man/man8/dnf4-repodiff.8.gz\n -rw-r--r-- 0 root (0) root (0) 767 2024-08-22 14:02:01.000000 ./usr/share/man/man8/dnf4-repograph.8.gz\n--rw-r--r-- 0 root (0) root (0) 1280 2024-08-22 14:02:01.000000 ./usr/share/man/man8/dnf4-repomanage.8.gz\n--rw-r--r-- 0 root (0) root (0) 1879 2024-08-22 14:02:01.000000 ./usr/share/man/man8/dnf4-reposync.8.gz\n+-rw-r--r-- 0 root (0) root (0) 1294 2024-08-22 14:02:01.000000 ./usr/share/man/man8/dnf4-repomanage.8.gz\n+-rw-r--r-- 0 root (0) root (0) 1897 2024-08-22 14:02:01.000000 ./usr/share/man/man8/dnf4-reposync.8.gz\n -rw-r--r-- 0 root (0) root (0) 522 2024-08-22 14:02:01.000000 ./usr/share/man/man8/dnf4-show-leaves.8.gz\n--rw-r--r-- 0 root (0) root (0) 2600 2024-08-22 14:02:01.000000 ./usr/share/man/man8/dnf4-system-upgrade.8.gz\n--rw-r--r-- 0 root (0) root (0) 2278 2024-08-22 14:02:01.000000 ./usr/share/man/man8/dnf4-versionlock.8.gz\n+-rw-r--r-- 0 root (0) root (0) 2608 2024-08-22 14:02:01.000000 ./usr/share/man/man8/dnf4-system-upgrade.8.gz\n+-rw-r--r-- 0 root (0) root (0) 2292 2024-08-22 14:02:01.000000 ./usr/share/man/man8/dnf4-versionlock.8.gz\n -rw-r--r-- 0 root (0) root (0) 1626 2024-08-22 14:02:01.000000 ./usr/share/man/man8/yum-copr.8.gz\n--rw-r--r-- 0 root (0) root (0) 2286 2024-08-22 14:02:01.000000 ./usr/share/man/man8/yum-versionlock.8.gz\n+-rw-r--r-- 0 root (0) root (0) 2301 2024-08-22 14:02:01.000000 ./usr/share/man/man8/yum-versionlock.8.gz\n"}, {"source1": "./usr/share/man/man1/repomanage.1.gz", "source2": "./usr/share/man/man1/repomanage.1.gz", "unified_diff": null, "details": [{"source1": "repomanage.1", "source2": "repomanage.1", "unified_diff": "@@ -33,30 +33,30 @@\n .sp\n Manage a repository or a simple directory of rpm packages.\n .SH SYNOPSIS\n .sp\n \\fBdnf repomanage [] [] \\fP\n .SH DESCRIPTION\n .sp\n-\\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.\n-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.\n+\\fIrepomanage\\fP prints newest or older packages in a repository specified by for easy piping to xargs or similar programs. In case doesn\u2019t contain a valid repodata, it is searched for rpm packages which are then used instead.\n+If the repodata are present, \\fIrepomanage\\fP uses them as the source of truth, it doesn\u2019t verify that they match the present rpm packages. In fact, \\fIrepomanage\\fP can run with just the repodata, no rpm packages are needed.\n .sp\n 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.\n .SS Options\n .sp\n All general DNF options are accepted, see \\fIOptions\\fP in \\fBdnf(8)\\fP for details.\n .sp\n 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.\n .INDENT 0.0\n .TP\n .B \\fB\\-\\-old\\fP\n Show older packages (for a package or a stream show all versions except the newest one).\n .TP\n .B \\fB\\-\\-oldonly\\fP\n-Show older packages (same as \\-\\-old, but exclude the newest packages even when it\\(aqs included in the older stream versions).\n+Show older packages (same as \u2013old, but exclude the newest packages even when it\u2019s included in the older stream versions).\n .TP\n .B \\fB\\-\\-new\\fP\n Show newest packages.\n .UNINDENT\n .sp\n The following options control how packages are displayed in the output:\n .INDENT 0.0\n@@ -75,15 +75,15 @@\n .sp\n .EX\n dnf repomanage \\-\\-new .\n .EE\n .UNINDENT\n .UNINDENT\n .sp\n-Display 2 newest versions of each package in \\(dqhome\\(dq directory:\n+Display 2 newest versions of each package in \u201chome\u201d directory:\n .INDENT 0.0\n .INDENT 3.5\n .sp\n .EX\n dnf repomanage \\-\\-new \\-\\-keep 2 ~/\n .EE\n .UNINDENT\n", "details": [{"source1": "encoding", "source2": "encoding", "unified_diff": "@@ -1 +1 @@\n-us-ascii\n+utf-8\n"}]}]}, {"source1": "./usr/share/man/man1/reposync.1.gz", "source2": "./usr/share/man/man1/reposync.1.gz", "unified_diff": null, "details": [{"source1": "reposync.1", "source2": "reposync.1", "unified_diff": "@@ -47,16 +47,16 @@\n Download only packages of given architectures (default is all architectures). Can be used multiple times.\n .TP\n .B \\fB\\-\\-delete\\fP\n Delete local packages no longer present in repository.\n .TP\n .B \\fB\\-\\-download\\-metadata\\fP\n Download all repository metadata. Downloaded copy is instantly usable as a repository, no need to run createrepo_c\n-on it. When the option is used with \\fI\\-\\-newest\\-only\\fP, only latest packages will be downloaded, but metadata will\n-still contain older packages. It might be useful to update metadata using \\fIcreaterepo_c \\-\\-update\\fP to remove\n+on it. When the option is used with \\fI\u2013newest\\-only\\fP, only latest packages will be downloaded, but metadata will\n+still contain older packages. It might be useful to update metadata using \\fIcreaterepo_c \u2013update\\fP to remove\n the packages with missing RPM files from metadata. Otherwise, DNF ends with an error due to the missing files\n whenever it tries to download older packages.\n .TP\n .B \\fB\\-g, \\-\\-gpgcheck\\fP\n Remove packages that fail GPG signature checking after downloading. Exit code is \\fB1\\fP if at least one package was removed.\n Note that for repositories with \\fBgpgcheck=0\\fP set in their configuration the GPG signature is not checked even with this option used.\n .TP\n@@ -66,42 +66,42 @@\n .B \\fB\\-\\-metadata\\-path\\fP\n Root path under which the downloaded metadata are stored. It defaults to \\fB\\-\\-download\\-path\\fP value if not given.\n .TP\n .B \\fB\\-n, \\-\\-newest\\-only\\fP\n Download only newest packages per\\-repo.\n .TP\n .B \\fB\\-\\-norepopath\\fP\n-Don\\(aqt add the reponame to the download path. Can only be used when syncing a single repository (default is to add the reponame).\n+Don\u2019t add the reponame to the download path. Can only be used when syncing a single repository (default is to add the reponame).\n .TP\n .B \\fB\\-p , \\-\\-download\\-path=\\fP\n 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.\n .TP\n .B \\fB\\-\\-safe\\-write\\-path\\fP\n-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.\n+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. \u201c../packages_store/foo.rpm\u201d). Use with care, any file under the \\fBsafe\\-write\\-path\\fP can be overwritten. Can be only used when syncing a single repository.\n .TP\n .B \\fB\\-\\-remote\\-time\\fP\n Try to set the timestamps of the downloaded files to those on the remote side.\n .TP\n .B \\fB\\-\\-source\\fP\n Download only source packages.\n .TP\n .B \\fB\\-u, \\-\\-urls\\fP\n-Just print urls of what would be downloaded, don\\(aqt download.\n+Just print urls of what would be downloaded, don\u2019t download.\n .UNINDENT\n .SH EXAMPLES\n .INDENT 0.0\n .TP\n .B \\fBdnf reposync \\-\\-repoid=the_repo\\fP\n-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.\n+Synchronize all packages from the repository with id \u201cthe_repo\u201d. The synchronized copy is saved in \u201cthe_repo\u201d subdirectory of the current working directory.\n .TP\n .B \\fBdnf reposync \\-p /my/repos/path \\-\\-repoid=the_repo\\fP\n-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.\n+Synchronize all packages from the repository with id \u201cthe_repo\u201d. In this case files are saved in \u201c/my/repos/path/the_repo\u201d directory.\n .TP\n .B \\fBdnf reposync \\-\\-repoid=the_repo \\-\\-download\\-metadata\\fP\n-Synchronize all packages and metadata from \\(dqthe_repo\\(dq repository.\n+Synchronize all packages and metadata from \u201cthe_repo\u201d repository.\n .UNINDENT\n .sp\n Repository synchronized with \\fB\\-\\-download\\-metadata\\fP option can be directly used in DNF for example by using \\fB\\-\\-repofrompath\\fP option:\n .sp\n \\fBdnf \\-\\-repofrompath=syncedrepo,the_repo \\-\\-repoid=syncedrepo list \\-\\-available\\fP\n .SH SEE ALSO\n .INDENT 0.0\n", "details": [{"source1": "encoding", "source2": "encoding", "unified_diff": "@@ -1 +1 @@\n-us-ascii\n+utf-8\n"}]}]}, {"source1": "./usr/share/man/man5/yum-versionlock.conf.5.gz", "source2": "./usr/share/man/man5/yum-versionlock.conf.5.gz", "unified_diff": null, "details": [{"source1": "yum-versionlock.conf.5", "source2": "yum-versionlock.conf.5", "unified_diff": "@@ -31,29 +31,29 @@\n .SH NAME\n yum-versionlock.conf \\- redirecting to DNF versionlock Plugin\n .SH DESCRIPTION\n .sp\n \\fIversionlock\\fP is a plugin that takes a set of names and versions for packages and\n excludes all other versions of those packages. This allows you to protect\n packages from being updated by newer versions. Alternately, it accepts a specific\n-package version to exclude from updates, e.g. for when it\\(aqs necessary to skip a\n+package version to exclude from updates, e.g. for when it\u2019s necessary to skip a\n specific release of a package that has known issues.\n .sp\n The plugin provides a command \\fIversionlock\\fP which allows you to view and edit the\n list of locked packages easily.\n .sp\n The plugin will walk each line of the versionlock file, and parse out the name and\n version of the package. It will then exclude any package by that name that\n-doesn\\(aqt match one of the versions listed within the file. This is basically\n-the same as using \\fIdnf \\-\\-exclude\\fP for the package name itself (as you cannot exclude\n+doesn\u2019t match one of the versions listed within the file. This is basically\n+the same as using \\fIdnf \u2013exclude\\fP for the package name itself (as you cannot exclude\n installed packages), but dnf will still see the versions you have\n installed/versionlocked as available so that \\fIdnf reinstall\\fP will still\n work, etc.\n .sp\n-It can also work in the opposite way, like a fast exclude, by prefixing a \\(aq!\\(aq\n+It can also work in the opposite way, like a fast exclude, by prefixing a \u2018!\u2019\n character to the version recorded in the lock list file. This specifically\n excludes a package that matches the version exactly.\n .sp\n Note the versionlock plugin does not apply any excludes in non\\-transactional\n operations like \\fIrepoquery\\fP, \\fIlist\\fP, \\fIinfo\\fP, etc.\n .SH SYNOPSIS\n .sp\n@@ -156,15 +156,15 @@\n .INDENT 0.0\n .TP\n .B \\fBlocklist\\fP\n This option is a string that points to the file which has the versionlock\n information in it. Note that the file has to exist (or the versionlock plugin\n will make dnf exit). However, it can be empty.\n .sp\n-The file takes entries in the format of \\fB\\fP (optionally prefixed with \\(aq!\\(aq for\n+The file takes entries in the format of \\fB\\fP (optionally prefixed with \u2018!\u2019 for\n excludes).\n See \\fISpecifying packages\\fP in \\fBdnf(8)\\fP for details.\n .UNINDENT\n .SH NOTES\n .sp\n A specified package does not have to exist within the available cache of repository data\n to be considered valid for locking or exclusion. This is by design, to accommodate use\n", "details": [{"source1": "encoding", "source2": "encoding", "unified_diff": "@@ -1 +1 @@\n-us-ascii\n+utf-8\n"}]}]}, {"source1": "./usr/share/man/man8/dnf4-repomanage.8.gz", "source2": "./usr/share/man/man8/dnf4-repomanage.8.gz", "unified_diff": null, "details": [{"source1": "dnf4-repomanage.8", "source2": "dnf4-repomanage.8", "unified_diff": "@@ -33,30 +33,30 @@\n .sp\n Manage a repository or a simple directory of rpm packages.\n .SH SYNOPSIS\n .sp\n \\fBdnf repomanage [] [] \\fP\n .SH DESCRIPTION\n .sp\n-\\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.\n-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.\n+\\fIrepomanage\\fP prints newest or older packages in a repository specified by for easy piping to xargs or similar programs. In case doesn\u2019t contain a valid repodata, it is searched for rpm packages which are then used instead.\n+If the repodata are present, \\fIrepomanage\\fP uses them as the source of truth, it doesn\u2019t verify that they match the present rpm packages. In fact, \\fIrepomanage\\fP can run with just the repodata, no rpm packages are needed.\n .sp\n 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.\n .SS Options\n .sp\n All general DNF options are accepted, see \\fIOptions\\fP in \\fBdnf(8)\\fP for details.\n .sp\n 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.\n .INDENT 0.0\n .TP\n .B \\fB\\-\\-old\\fP\n Show older packages (for a package or a stream show all versions except the newest one).\n .TP\n .B \\fB\\-\\-oldonly\\fP\n-Show older packages (same as \\-\\-old, but exclude the newest packages even when it\\(aqs included in the older stream versions).\n+Show older packages (same as \u2013old, but exclude the newest packages even when it\u2019s included in the older stream versions).\n .TP\n .B \\fB\\-\\-new\\fP\n Show newest packages.\n .UNINDENT\n .sp\n The following options control how packages are displayed in the output:\n .INDENT 0.0\n@@ -75,15 +75,15 @@\n .sp\n .EX\n dnf repomanage \\-\\-new .\n .EE\n .UNINDENT\n .UNINDENT\n .sp\n-Display 2 newest versions of each package in \\(dqhome\\(dq directory:\n+Display 2 newest versions of each package in \u201chome\u201d directory:\n .INDENT 0.0\n .INDENT 3.5\n .sp\n .EX\n dnf repomanage \\-\\-new \\-\\-keep 2 ~/\n .EE\n .UNINDENT\n", "details": [{"source1": "encoding", "source2": "encoding", "unified_diff": "@@ -1 +1 @@\n-us-ascii\n+utf-8\n"}]}]}, {"source1": "./usr/share/man/man8/dnf4-reposync.8.gz", "source2": "./usr/share/man/man8/dnf4-reposync.8.gz", "unified_diff": null, "details": [{"source1": "dnf4-reposync.8", "source2": "dnf4-reposync.8", "unified_diff": "@@ -47,16 +47,16 @@\n Download only packages of given architectures (default is all architectures). Can be used multiple times.\n .TP\n .B \\fB\\-\\-delete\\fP\n Delete local packages no longer present in repository.\n .TP\n .B \\fB\\-\\-download\\-metadata\\fP\n Download all repository metadata. Downloaded copy is instantly usable as a repository, no need to run createrepo_c\n-on it. When the option is used with \\fI\\-\\-newest\\-only\\fP, only latest packages will be downloaded, but metadata will\n-still contain older packages. It might be useful to update metadata using \\fIcreaterepo_c \\-\\-update\\fP to remove\n+on it. When the option is used with \\fI\u2013newest\\-only\\fP, only latest packages will be downloaded, but metadata will\n+still contain older packages. It might be useful to update metadata using \\fIcreaterepo_c \u2013update\\fP to remove\n the packages with missing RPM files from metadata. Otherwise, DNF ends with an error due to the missing files\n whenever it tries to download older packages.\n .TP\n .B \\fB\\-g, \\-\\-gpgcheck\\fP\n Remove packages that fail GPG signature checking after downloading. Exit code is \\fB1\\fP if at least one package was removed.\n Note that for repositories with \\fBgpgcheck=0\\fP set in their configuration the GPG signature is not checked even with this option used.\n .TP\n@@ -66,42 +66,42 @@\n .B \\fB\\-\\-metadata\\-path\\fP\n Root path under which the downloaded metadata are stored. It defaults to \\fB\\-\\-download\\-path\\fP value if not given.\n .TP\n .B \\fB\\-n, \\-\\-newest\\-only\\fP\n Download only newest packages per\\-repo.\n .TP\n .B \\fB\\-\\-norepopath\\fP\n-Don\\(aqt add the reponame to the download path. Can only be used when syncing a single repository (default is to add the reponame).\n+Don\u2019t add the reponame to the download path. Can only be used when syncing a single repository (default is to add the reponame).\n .TP\n .B \\fB\\-p , \\-\\-download\\-path=\\fP\n 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.\n .TP\n .B \\fB\\-\\-safe\\-write\\-path\\fP\n-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.\n+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. \u201c../packages_store/foo.rpm\u201d). Use with care, any file under the \\fBsafe\\-write\\-path\\fP can be overwritten. Can be only used when syncing a single repository.\n .TP\n .B \\fB\\-\\-remote\\-time\\fP\n Try to set the timestamps of the downloaded files to those on the remote side.\n .TP\n .B \\fB\\-\\-source\\fP\n Download only source packages.\n .TP\n .B \\fB\\-u, \\-\\-urls\\fP\n-Just print urls of what would be downloaded, don\\(aqt download.\n+Just print urls of what would be downloaded, don\u2019t download.\n .UNINDENT\n .SH EXAMPLES\n .INDENT 0.0\n .TP\n .B \\fBdnf reposync \\-\\-repoid=the_repo\\fP\n-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.\n+Synchronize all packages from the repository with id \u201cthe_repo\u201d. The synchronized copy is saved in \u201cthe_repo\u201d subdirectory of the current working directory.\n .TP\n .B \\fBdnf reposync \\-p /my/repos/path \\-\\-repoid=the_repo\\fP\n-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.\n+Synchronize all packages from the repository with id \u201cthe_repo\u201d. In this case files are saved in \u201c/my/repos/path/the_repo\u201d directory.\n .TP\n .B \\fBdnf reposync \\-\\-repoid=the_repo \\-\\-download\\-metadata\\fP\n-Synchronize all packages and metadata from \\(dqthe_repo\\(dq repository.\n+Synchronize all packages and metadata from \u201cthe_repo\u201d repository.\n .UNINDENT\n .sp\n Repository synchronized with \\fB\\-\\-download\\-metadata\\fP option can be directly used in DNF for example by using \\fB\\-\\-repofrompath\\fP option:\n .sp\n \\fBdnf \\-\\-repofrompath=syncedrepo,the_repo \\-\\-repoid=syncedrepo list \\-\\-available\\fP\n .SH SEE ALSO\n .INDENT 0.0\n", "details": [{"source1": "encoding", "source2": "encoding", "unified_diff": "@@ -1 +1 @@\n-us-ascii\n+utf-8\n"}]}]}, {"source1": "./usr/share/man/man8/dnf4-system-upgrade.8.gz", "source2": "./usr/share/man/man8/dnf4-system-upgrade.8.gz", "unified_diff": null, "details": [{"source1": "dnf4-system-upgrade.8", "source2": "dnf4-system-upgrade.8", "unified_diff": "@@ -128,15 +128,15 @@\n upgrades are completed, instead of restarting.\n .TP\n .B \\fB\\-\\-number\\fP\n Applied with \\fBlog\\fP subcommand will show the log specified by the number.\n .UNINDENT\n .SH NOTES\n .sp\n-\\fBdnf system\\-upgrade reboot\\fP does not create a \\(dqSystem Upgrade\\(dq boot item. The\n+\\fBdnf system\\-upgrade reboot\\fP does not create a \u201cSystem Upgrade\u201d boot item. The\n upgrade will start regardless of which boot item is chosen.\n .sp\n The \\fBDNF_SYSTEM_UPGRADE_NO_REBOOT\\fP environment variable can be set to a\n non\\-empty value to disable the actual reboot performed by \\fBsystem\\-upgrade\\fP\n (e.g. for testing purposes).\n .sp\n Since this is a DNF plugin, options accepted by \\fBdnf\\fP are also valid here,\n@@ -182,15 +182,15 @@\n \\fBdnf system\\-upgrade log \\-\\-number=\\-1\\fP (if applicable) in your bug reports.\n .sp\n Problems with dependency solving during download are best reported to the\n maintainers of the package(s) with the dependency problems.\n .sp\n Similarly, problems encountered on your system after the upgrade completes\n should be reported to the maintainers of the affected components. In other\n-words: if (for example) KDE stops working, it\\(aqs best if you report that to\n+words: if (for example) KDE stops working, it\u2019s best if you report that to\n the KDE maintainers.\n .SH SEE ALSO\n .sp\n \\fBdnf(8)\\fP,\n \\fBdnf.conf(5)\\fP,\n \\fBjournalctl(1)\\fP\\&.\n .SS Project homepage\n"}]}, {"source1": "./usr/share/man/man8/dnf4-versionlock.8.gz", "source2": "./usr/share/man/man8/dnf4-versionlock.8.gz", "unified_diff": null, "details": [{"source1": "dnf4-versionlock.8", "source2": "dnf4-versionlock.8", "unified_diff": "@@ -31,29 +31,29 @@\n .SH NAME\n dnf4-versionlock \\- DNF versionlock Plugin\n .SH DESCRIPTION\n .sp\n \\fIversionlock\\fP is a plugin that takes a set of names and versions for packages and\n excludes all other versions of those packages. This allows you to protect\n packages from being updated by newer versions. Alternately, it accepts a specific\n-package version to exclude from updates, e.g. for when it\\(aqs necessary to skip a\n+package version to exclude from updates, e.g. for when it\u2019s necessary to skip a\n specific release of a package that has known issues.\n .sp\n The plugin provides a command \\fIversionlock\\fP which allows you to view and edit the\n list of locked packages easily.\n .sp\n The plugin will walk each line of the versionlock file, and parse out the name and\n version of the package. It will then exclude any package by that name that\n-doesn\\(aqt match one of the versions listed within the file. This is basically\n-the same as using \\fIdnf \\-\\-exclude\\fP for the package name itself (as you cannot exclude\n+doesn\u2019t match one of the versions listed within the file. This is basically\n+the same as using \\fIdnf \u2013exclude\\fP for the package name itself (as you cannot exclude\n installed packages), but dnf will still see the versions you have\n installed/versionlocked as available so that \\fIdnf reinstall\\fP will still\n work, etc.\n .sp\n-It can also work in the opposite way, like a fast exclude, by prefixing a \\(aq!\\(aq\n+It can also work in the opposite way, like a fast exclude, by prefixing a \u2018!\u2019\n character to the version recorded in the lock list file. This specifically\n excludes a package that matches the version exactly.\n .sp\n Note the versionlock plugin does not apply any excludes in non\\-transactional\n operations like \\fIrepoquery\\fP, \\fIlist\\fP, \\fIinfo\\fP, etc.\n .SH SYNOPSIS\n .sp\n@@ -156,15 +156,15 @@\n .INDENT 0.0\n .TP\n .B \\fBlocklist\\fP\n This option is a string that points to the file which has the versionlock\n information in it. Note that the file has to exist (or the versionlock plugin\n will make dnf exit). However, it can be empty.\n .sp\n-The file takes entries in the format of \\fB\\fP (optionally prefixed with \\(aq!\\(aq for\n+The file takes entries in the format of \\fB\\fP (optionally prefixed with \u2018!\u2019 for\n excludes).\n See \\fISpecifying packages\\fP in \\fBdnf(8)\\fP for details.\n .UNINDENT\n .SH NOTES\n .sp\n A specified package does not have to exist within the available cache of repository data\n to be considered valid for locking or exclusion. This is by design, to accommodate use\n", "details": [{"source1": "encoding", "source2": "encoding", "unified_diff": "@@ -1 +1 @@\n-us-ascii\n+utf-8\n"}]}]}, {"source1": "./usr/share/man/man8/yum-versionlock.8.gz", "source2": "./usr/share/man/man8/yum-versionlock.8.gz", "unified_diff": null, "details": [{"source1": "yum-versionlock.8", "source2": "yum-versionlock.8", "unified_diff": "@@ -31,29 +31,29 @@\n .SH NAME\n yum-versionlock \\- redirecting to DNF versionlock Plugin\n .SH DESCRIPTION\n .sp\n \\fIversionlock\\fP is a plugin that takes a set of names and versions for packages and\n excludes all other versions of those packages. This allows you to protect\n packages from being updated by newer versions. Alternately, it accepts a specific\n-package version to exclude from updates, e.g. for when it\\(aqs necessary to skip a\n+package version to exclude from updates, e.g. for when it\u2019s necessary to skip a\n specific release of a package that has known issues.\n .sp\n The plugin provides a command \\fIversionlock\\fP which allows you to view and edit the\n list of locked packages easily.\n .sp\n The plugin will walk each line of the versionlock file, and parse out the name and\n version of the package. It will then exclude any package by that name that\n-doesn\\(aqt match one of the versions listed within the file. This is basically\n-the same as using \\fIdnf \\-\\-exclude\\fP for the package name itself (as you cannot exclude\n+doesn\u2019t match one of the versions listed within the file. This is basically\n+the same as using \\fIdnf \u2013exclude\\fP for the package name itself (as you cannot exclude\n installed packages), but dnf will still see the versions you have\n installed/versionlocked as available so that \\fIdnf reinstall\\fP will still\n work, etc.\n .sp\n-It can also work in the opposite way, like a fast exclude, by prefixing a \\(aq!\\(aq\n+It can also work in the opposite way, like a fast exclude, by prefixing a \u2018!\u2019\n character to the version recorded in the lock list file. This specifically\n excludes a package that matches the version exactly.\n .sp\n Note the versionlock plugin does not apply any excludes in non\\-transactional\n operations like \\fIrepoquery\\fP, \\fIlist\\fP, \\fIinfo\\fP, etc.\n .SH SYNOPSIS\n .sp\n@@ -156,15 +156,15 @@\n .INDENT 0.0\n .TP\n .B \\fBlocklist\\fP\n This option is a string that points to the file which has the versionlock\n information in it. Note that the file has to exist (or the versionlock plugin\n will make dnf exit). However, it can be empty.\n .sp\n-The file takes entries in the format of \\fB\\fP (optionally prefixed with \\(aq!\\(aq for\n+The file takes entries in the format of \\fB\\fP (optionally prefixed with \u2018!\u2019 for\n excludes).\n See \\fISpecifying packages\\fP in \\fBdnf(8)\\fP for details.\n .UNINDENT\n .SH NOTES\n .sp\n A specified package does not have to exist within the available cache of repository data\n to be considered valid for locking or exclusion. This is by design, to accommodate use\n", "details": [{"source1": "encoding", "source2": "encoding", "unified_diff": "@@ -1 +1 @@\n-us-ascii\n+utf-8\n"}]}]}]}]}]}]}