Description of problem: Currently I have pymol and pymol-wxpython version 1.8.6. Upgraded version 1.9.0 just came out but the upgrade is blocked by a conflict. Version-Release number of selected component (if applicable): pymol-wxpython-1.8.6-4.20170314svn4170.fc27.x86_64 pymol-1.8.6-4.20170314svn4170.fc27.x86_64 How reproducible: every time Steps to Reproduce: 1. dnf -y update Actual results: Problem: cannot install both pymol-1.9.0-1.20180224svn4178.fc27.x86_64 and pymol-1.8.6-4.20170314svn4170.fc27.x86_64 - package pymol-wxpython-1.8.6-4.20170314svn4170.fc27.x86_64 requires pymol = 1.8.6-4.20170314svn4170.fc27, but none of the providers can be installed - cannot install the best update candidate for package pymol-1.8.6-4.20170314svn4170.fc27.x86_64 - problem with installed package pymol-wxpython-1.8.6-4.20170314svn4170.fc27.x86_64 Expected results: successful upgrade
dnf -y upgrade --refresh --best --allowerasing successfully updates pymol, by deleting the old version of pymol-wxpython Reinstalling pymol-wxpython is possible by downgrading pymol. I assume eventually there will be a new version of pymol-wxpython compatible with pymol 1.9.0, but it looks like it will not get automatically reinstalled after 1.8.6 was deleted. I wonder if this is a problem specifically with pymol* or a generic dnf dependency problem: it's good that --allowerasing allows package upgrade but I would argue that it should not delete other packages unless they are obsoleted and removed from Fedora.
This is clearly bug in pymol packaging. Either the pymol-wxpython disappearance was an oversight, or the packager removed it intentionally and then either pymol-wxpython files were merged into pymol binary package and then pymol binary package should RPM-provide pymol-wxpython, or pymol-wxpython was removed without a replacement and then such an update should have never gone to stable Fedora 27 release because it breaks API.
Yes, this is probably a fault on my end (removed it is no longer part of pymol) - how is this best clarified in future pymol releases/spec file?
If the removed files exist in a different project, then that project should be packaged and the new package should provide pymol-wxpython RPM symbol. If the removed files does not exist anymore, then "Obsolete: pymol-wxpython <= LATEST_PACKAGED_VERSION" should be added to fedora-obsolete-packages package as documented in <https://fedoraproject.org/wiki/Packaging:Guidelines?rd=Packaging/Guidelines#Renaming.2FReplacing_Existing_Packages>.
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '27'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 27 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.