Summary says it all. Users will get conflicting files output if they attempt to update from libsmbios-bin-0.13.13-1.fc9
Fixed in 2.0.1-2, which was just tagged and built in rawhide.
*** Bug 435708 has been marked as a duplicate of this bug. ***
I still get yum errors similar to bug #435708 updating from libsmbios-bin-0.13.13-1.fc8.i386 on rawhide. Is there a workaround for this? Do you have to manually remove the old package?
i.e. they mention libsmbios-bin-0.13.13-1.fc8.i386 rather than libsmbios-bin-0.13.13-1.fc9.i386 as I had originally installed F-8 then yum updated to rawhide: Transaction Check Error: file /usr/sbin/assetTag from install of smbios-utils-2.0.1-1.fc9.i386 conflicts with file from package libsmbios-bin-0.13.13-1.fc8.i386 file /usr/sbin/dellBiosUpdate from install of smbios-utils-2.0.1-1.fc9.i386 conflicts with file from package libsmbios-bin-0.13.13-1.fc8.i386 file /usr/sbin/dellLcdBrightness from install of smbios-utils-2.0.1-1.fc9.i386 conflicts with file from package libsmbios-bin-0.13.13-1.fc8.i386 file /usr/sbin/dellWirelessCtl from install of smbios-utils-2.0.1-1.fc9.i386 conflicts with file from package libsmbios-bin-0.13.13-1.fc8.i386 file /usr/sbin/getSystemId from install of smbios-utils-2.0.1-1.fc9.i386 conflicts with file from package libsmbios-bin-0.13.13-1.fc8.i386 file /usr/sbin/propertyTag from install of smbios-utils-2.0.1-1.fc9.i386 conflicts with file from package libsmbios-bin-0.13.13-1.fc8.i386 file /usr/sbin/serviceTag from install of smbios-utils-2.0.1-1.fc9.i386 conflicts with file from package libsmbios-bin-0.13.13-1.fc8.i386 file /usr/sbin/verifySmiPassword from install of smbios-utils-2.0.1-1.fc9.i386 conflicts with file from package libsmbios-bin-0.13.13-1.fc8.i386 file /usr/sbin/wakeupCtl from install of smbios-utils-2.0.1-1.fc9.i386 conflicts with file from package libsmbios-bin-0.13.13-1.fc8.i386
Alex, workaround (for today's repo, before the fix is there), run: rpm -e --nodeps libsmbios-bin; yum install smbios-utils libsmbios; yum --skip-broken update
The other workaround would be to wait until the next rawhide compose, as this has been built and should be fixed as soon as the new build is pushed to rawhide.
OK, rawhide build has now been pushed and "yum update" proceeds as expected.