This is rather odd. openQA's test of KDE upgrades from F29 to F31 is failing on a conflict between ruby-irb-2.5.3-100.fc29 and rubygem-irb-1.0.0-117.fc31: https://openqa.fedoraproject.org/tests/368256#step/upgrade_run/16 "Error: Transaction check error: file /usr/share/ruby/irb from install of rubygem-irb-1.0.0-117.fc31.noarch conflicts with file from package ruby-irb-2.5.3-100.fc29.noarch" however, rubygem-irb-1.0.0-117.fc31 appears to specifically obsolete and provide ruby-irb - https://koji.fedoraproject.org/koji/rpminfo?rpmID=17078674 says: Provides irb = 1.0.0-117.fc31 ruby(irb) = 2.6.2-117.fc31 ruby-irb = 2.6.2-117.fc31 rubygem(irb) = 1.0.0-117.fc31 rubygem-irb = 1.0.0-117.fc31 Obsoletes ruby-irb < 2.6.2-117.fc31 so I'm really not sure what's going on here, yet. But it's definitely failing...
As it stands this should be an F31 Beta blocker, per criterion "For each one of the release-blocking package sets, it must be possible to successfully complete a direct upgrade from a fully updated, clean default installation of each of the last two stable Fedora releases with that package set installed."
Oh, forget comment #2, I was getting my versions mixed up - it affects upgrades from both *28* and *29* to 31. 28 to 31 is not a supported case, so we only really have to worry about 29->31.
This is directory -> symlink change refused by rpm transaction, ref: https://src.fedoraproject.org/rpms/ruby/c/5aa32e278d096a36ba0d8926d4891f1e0757d4e5?branch=master
ah, of course, good catch.
ruby-2.6.2-118.fc30 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-95681e73f2
ruby-2.6.2-118.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-95681e73f2
Successfully upgraded from F29 to F30. My bugreport: https://bugzilla.redhat.com/show_bug.cgi?id=1691950
Unfortunately, -118 creates file conflicts when updating in an existing F30 or Rawhide box. See https://bugzilla.redhat.com/show_bug.cgi?id=1691999 and https://bugzilla.redhat.com/show_bug.cgi?id=1692129 .
-117 was in testing but it was revoked, upgrading from -116 (already in stable) to -118 (in testing) should be okay.
*** Bug 1691950 has been marked as a duplicate of this bug. ***
(In reply to Andre Robatino from comment #9) > Unfortunately, -118 creates file conflicts when updating in an existing F30 > or Rawhide box. Sorry for troubles. This is the troubling directory -> symlink conversion :/ (In reply to Mamoru TASAKA from comment #10) > -117 was in testing but it was revoked, upgrading from -116 (already in > stable) to -118 (in testing) should be okay. I think that the upgrade issues from -117 to -118 has just limited impact, so I hope people can cope with the update. Downgrade to -116 and update to -118 is probably the best option.
ruby-2.6.2-118.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report.