On Sun, 9 Feb 2020 09:36:54 -0500 John Mellor <john.mellor(a)gmail.com&gt; wrote: TLDR; seeing it too, but don't know the cause. I've started seeing this recently as well. In the same update that contains the error though, many other drpms will rebuild just fine. So, my guess is that the local version is somehow different from the version the drpm was created against, so when it rebuilds, the md5 is different. That is, I don't think it is a bug in either the repo or the drpm builder. But the fact that it only started happening recently argues against that opinion.

On Sun, 2020-02-09 at 09:36 -0500, John Mellor wrote: This is not a repo bug, but rather a (small) bug in how selinux-policy- targeted is packaged. A drpm is assembled by taking the parts of the old installed rpm that haven't changed from the local system and then only downloading the parts that have changed. The problem is that a file in selinux-policy-targeted changes *after* it's installed, but dnf doesn't detect that the old installed rpm has changed until after downloading and attempting to apply the drpm. As you can see on my local system, there are four files that have changed after selinux-policy-targeted was installed: $ sudo rpm -V selinux-policy-targeted S.5....T. c /etc/selinux/targeted/contexts/files/file_contexts.local ..5....T. /var/lib/selinux/targeted/active/commit_num S.5....T. /var/lib/selinux/targeted/active/file_contexts .......T. /var/lib/selinux/targeted/active/homedir_template S.5....T. /var/lib/selinux/targeted/active/policy.kern .M....... g /var/lib/selinux/targeted/active/policy.linked .......T. /var/lib/selinux/targeted/active/seusers .......T. /var/lib/selinux/targeted/active/users_extra The file in /etc is marked as a config file, so won't cause the deltarpm to fail, but the changes to the other three will. Arguably, any files that may change on the local system should be marked as config files. Jonathan