--- /srv/reproducible-results/rbuild-debian/r-b-build.fLoE9ZpM/b1/dnf-plugins-core_4.9.0-1_i386.changes +++ /srv/reproducible-results/rbuild-debian/r-b-build.fLoE9ZpM/b2/dnf-plugins-core_4.9.0-1_i386.changes ├── Files │ @@ -1,2 +1,2 @@ │ │ - 190b26d1552650f6e88258f68a595635 244252 admin optional dnf-plugins-core_4.9.0-1_all.deb │ + 882896ff6e89342e547c8214b38a7394 245060 admin optional dnf-plugins-core_4.9.0-1_all.deb ├── dnf-plugins-core_4.9.0-1_all.deb │ ├── file list │ │ @@ -1,3 +1,3 @@ │ │ -rw-r--r-- 0 0 0 4 2024-08-22 14:02:01.000000 debian-binary │ │ -rw-r--r-- 0 0 0 4284 2024-08-22 14:02:01.000000 control.tar.xz │ │ --rw-r--r-- 0 0 0 239776 2024-08-22 14:02:01.000000 data.tar.xz │ │ +-rw-r--r-- 0 0 0 240584 2024-08-22 14:02:01.000000 data.tar.xz │ ├── control.tar.xz │ │ ├── control.tar │ │ │ ├── ./md5sums │ │ │ │ ├── ./md5sums │ │ │ │ │┄ Files differ │ ├── data.tar.xz │ │ ├── data.tar │ │ │ ├── file list │ │ │ │ @@ -170,15 +170,15 @@ │ │ │ │ -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 │ │ │ │ -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 │ │ │ │ -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 │ │ │ │ -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 │ │ │ │ -rw-r--r-- 0 root (0) root (0) 1292 2024-08-22 14:02:01.000000 ./usr/share/man/man1/yum-utils.1.gz │ │ │ │ -rw-r--r-- 0 root (0) root (0) 1289 2024-08-22 14:02:01.000000 ./usr/share/man/man1/yumdownloader.1.gz │ │ │ │ drwxr-xr-x 0 root (0) root (0) 0 2024-08-22 14:02:01.000000 ./usr/share/man/man5/ │ │ │ │ --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 │ │ │ │ +-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 │ │ │ │ drwxr-xr-x 0 root (0) root (0) 0 2024-08-22 14:02:01.000000 ./usr/share/man/man8/ │ │ │ │ -rw-r--r-- 0 root (0) root (0) 1190 2024-08-22 14:02:01.000000 ./usr/share/man/man8/dnf4-builddep.8.gz │ │ │ │ -rw-r--r-- 0 root (0) root (0) 887 2024-08-22 14:02:01.000000 ./usr/share/man/man8/dnf4-changelog.8.gz │ │ │ │ -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 │ │ │ │ -rw-r--r-- 0 root (0) root (0) 1619 2024-08-22 14:02:01.000000 ./usr/share/man/man8/dnf4-copr.8.gz │ │ │ │ -rw-r--r-- 0 root (0) root (0) 1269 2024-08-22 14:02:01.000000 ./usr/share/man/man8/dnf4-debug.8.gz │ │ │ │ -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 │ │ │ │ @@ -194,11 +194,11 @@ │ │ │ │ -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 │ │ │ │ -rw-r--r-- 0 root (0) root (0) 1021 2024-08-22 14:02:01.000000 ./usr/share/man/man8/dnf4-repoclosure.8.gz │ │ │ │ -rw-r--r-- 0 root (0) root (0) 1202 2024-08-22 14:02:01.000000 ./usr/share/man/man8/dnf4-repodiff.8.gz │ │ │ │ -rw-r--r-- 0 root (0) root (0) 767 2024-08-22 14:02:01.000000 ./usr/share/man/man8/dnf4-repograph.8.gz │ │ │ │ -rw-r--r-- 0 root (0) root (0) 1294 2024-08-22 14:02:01.000000 ./usr/share/man/man8/dnf4-repomanage.8.gz │ │ │ │ -rw-r--r-- 0 root (0) root (0) 1897 2024-08-22 14:02:01.000000 ./usr/share/man/man8/dnf4-reposync.8.gz │ │ │ │ -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 │ │ │ │ --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 │ │ │ │ --rw-r--r-- 0 root (0) root (0) 2292 2024-08-22 14:02:01.000000 ./usr/share/man/man8/dnf4-versionlock.8.gz │ │ │ │ +-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 │ │ │ │ +-rw-r--r-- 0 root (0) root (0) 2278 2024-08-22 14:02:01.000000 ./usr/share/man/man8/dnf4-versionlock.8.gz │ │ │ │ -rw-r--r-- 0 root (0) root (0) 1626 2024-08-22 14:02:01.000000 ./usr/share/man/man8/yum-copr.8.gz │ │ │ │ --rw-r--r-- 0 root (0) root (0) 2301 2024-08-22 14:02:01.000000 ./usr/share/man/man8/yum-versionlock.8.gz │ │ │ │ +-rw-r--r-- 0 root (0) root (0) 2286 2024-08-22 14:02:01.000000 ./usr/share/man/man8/yum-versionlock.8.gz │ │ │ ├── ./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’s necessary to skip a │ │ │ │ │ +package version to exclude from updates, e.g. for when it\(aqs 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’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 │ │ │ │ │ +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 │ │ │ │ │ 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 ‘!’ │ │ │ │ │ +It can also work in the opposite way, like a fast exclude, by prefixing a \(aq!\(aq │ │ │ │ │ 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 ‘!’ for │ │ │ │ │ +The file takes entries in the format of \fB\fP (optionally prefixed with \(aq!\(aq 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 @@ │ │ │ │ │ │ -utf-8 │ │ │ │ │ │ +us-ascii │ │ │ ├── ./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 “System Upgrade” boot item. The │ │ │ │ │ +\fBdnf system\-upgrade reboot\fP does not create a \(dqSystem Upgrade\(dq 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’s best if you report that to │ │ │ │ │ +words: if (for example) KDE stops working, it\(aqs 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’s necessary to skip a │ │ │ │ │ +package version to exclude from updates, e.g. for when it\(aqs 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’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 │ │ │ │ │ +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 │ │ │ │ │ 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 ‘!’ │ │ │ │ │ +It can also work in the opposite way, like a fast exclude, by prefixing a \(aq!\(aq │ │ │ │ │ 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 ‘!’ for │ │ │ │ │ +The file takes entries in the format of \fB\fP (optionally prefixed with \(aq!\(aq 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 @@ │ │ │ │ │ │ -utf-8 │ │ │ │ │ │ +us-ascii │ │ │ ├── ./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’s necessary to skip a │ │ │ │ │ +package version to exclude from updates, e.g. for when it\(aqs 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’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 │ │ │ │ │ +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 │ │ │ │ │ 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 ‘!’ │ │ │ │ │ +It can also work in the opposite way, like a fast exclude, by prefixing a \(aq!\(aq │ │ │ │ │ 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 ‘!’ for │ │ │ │ │ +The file takes entries in the format of \fB\fP (optionally prefixed with \(aq!\(aq 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 @@ │ │ │ │ │ │ -utf-8 │ │ │ │ │ │ +us-ascii