Hide Forgot
=> synergy-plus-1.3.4-8.fc17.src.rpm => synergy-plus-1.3.4-8.fc17.i686 in fedora-development-i386 File conflict with: synergy-1.3.7-4.fc17.i686 /usr/bin/synergyc /usr/bin/synergys [semi-automated bug report]
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
I ran into this problem today; I had synergy-plus installed in F18, then did a fedup upgrade. synergy-plus was no longer able to let me escape from my server screen to my clients. I then noticed that the upstream pages state that synergy+ has been merged back into synergy, at the new site synergy-foss.org [http://en.wikipedia.org/wiki/Synergy_%28software%29#Synergy.2B], and sure enough, synergy is at 1.4.10 while synergy-plus is stuck at 1.3.4. But because of the conflict between the two packages, I couldn't just upgrade or 'yum install synergy'; instead, I had to 'yum erase synergy-plus' first. It seems like adding an Obsoletes: tag in the synergy rpm would make it so that upgrading automatically replaces the old synergy-plus with newer synergy, without having to hit the conflicts manually.
With recent "fedpkg" tool changes, it has become very easy for package owner(s) to retire a package properly (because the tool also talks to pkgdb): https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life The synergy-plus package in dist git is dead already, and the Obsoletes tag has been corrected/increased once more to cover the F20 rebuild.
*** Bug 1018991 has been marked as a duplicate of this bug. ***
This bug appears to have been reported against 'rawhide' during the Fedora 23 development cycle. Changing version to '23'. (As we did not run this process for some time, it could affect also pre-Fedora 23 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 23 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora23
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. 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 '23'. 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 23 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 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.