On 7 March 2018 at 05:40, Jaroslav Mracek <jmracek@xxxxxxxxxx> wrote: > Recently, several users report problems with system upgrade due to rich dependencies that are not supported by RPM in Fedora 25, and not fully supported by RPM in Fedora 26 (statement 'with'). Rich dependencies are allowed and supported from Fedora 26, but during the System Upgrade from Fedora 25 the transaction is checked by RPM that doesn't support rich dependencies, therefore the transaction check performed by RPM fails. A similar situation can be experienced for System Upgrade from Fedora 26 where RPM is unable to handle rich dependency using "with" statement (https://bugzilla.redhat.com/show_bug.cgi?id=1551543). In future we can expect that more and more users will be affected by the problem due to increase of rich dependencies in Fedora 26-28. I realize that there were similar issue discussed in https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx/thread/Q5LMMPVEORM76IOPGKYS4XJ6VZ2WLAAX/#7JWQ2TFDFYNCQFJBMOAQFIPDP4XCYLVC, but it does not cover user point o > f view. > > Possible solution: > 1. Back-port support of "with" key word in rich dependencies into Fedora 26 (solves only upgrades from 26 to 27, and 26 to 28.) > 2. Ban rich dependencies in Fedora 26, and 27, and in 28 only rich deps using "with" statement (solves all issues) > 3. Provide a copr repo with RPM for Fedora 25, and 26 that support all rich dependencies (user unfriendly) > 4. Disable rich dependency check in RPM release for Fedora 26 (solves only upgrades from 26 to 27, and 26 to 28.) > I don't know if this is useful but in the RHL and early Fedora days, the way to do inplace upgrades was to first update just the 'core' tools needed by rpm. Then you would normally need to do an rpmrebuild to make everything correct. Then the install would be restarted and completed with the new in place tools. However every now and then a 'flag' day would happen which meant that past updates could not be done with an inplace update and an external one was needed. This sounds like this is the case with rich dependencies which would have been a reason to move rpm4 to rpm5 but ahem that wasn't possible. Is there a way to get either a minimal update installer or a scripted set of commands to allow for the above? > The issue can be experienced in following system upgrade combinations: 25 to 26, 25 to 27, 26 to 27, 26 to 28. > The list of Fedora 27 and 28 packages with incompatible rich deps - https://bugzilla.redhat.com/show_bug.cgi?id=1552547 > > Best regards > > Jaroslav > _______________________________________________ > devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx -- Stephen J Smoogen. _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
