Description of problem:
For example, " file /usr/bin/freetype-config conflicts between attempted installs of freetype-devel-2.9.1-2.fc29.i686 and freetype-devel-2.9.1-2.fc29.x86_64"
There are lots of other examples. Do try this at home.
Version-Release number of selected component (if applicable):
dnf system-upgrade download --best --refresh --releasever=29 --allowerasing
How reproducible:
dnf system-upgrade download --best --refresh --releasever=29 --allowerasing
Steps to Reproduce:
1.dnf system-upgrade download --best --refresh --releasever=29 --allowerasing
Actual Error:
Transaction check error:
file /usr/bin/freetype-config conflicts between attempted installs of freetype-devel-2.9.1-2.fc29.i686 and freetype-devel-2.9.1-2.fc29.x86_64
esults:
Expected results:
success
Additional info:
Is it not the case that the same human beings maintain i686 and x86_64 versions? How hard is it to make your packages not collide? How hard is it to understand that some packages only run under 1686 *cough*wine*cough* and have requirements? Pass the blame to them, then. Which part of "--allowerasing" is unclear?
OK, yes, today's system upgrade is better than sucking redhat 4 through a 1440k straw and compiling everything by hand. Today's system upgrade process is also better than getting poked in the eye with a sharp stick. F28 was do-able. I had hoped that F29 would be visible to my remaining eyeball. (Raise hands if you too saw the original in the Laser Lab. Plus points if you also got there over the roof. Prove it: name the building.)