Description of problem:
Synergy 2 has been marked as beta by their creators (see https://symless.com/blog/synergy-2-back-beta) and that means Synergy 1.10 should be used. In Fedora 28, there is a synergy package which contains Synergy 2. The package name is the same as the Synergy 1 provided by Symless.
After installing the stable version 1 manually, it gets updated to Synergy 2 after running "dnf update". It is possible to exclude the synergy package, but for a better user experience would be better to have a system solution.
Version-Release number of selected component (if applicable):
synergy-2.0.0-3.fc28 (Fedora official repo)
Steps to Reproduce:
1. Install Synergy 1 by dnf install path/to/synergy-1.10.0-40*
2. Run dnf update
3. Synergy gets updated to version 2.0.0-3
Synergy gets updated to an incompatible version
Synergy won't get updated
I would propose to have two packages, synergy and synerge2, which are mutually exclusive, so the "synergy" package will deploy version 1.x and synergy2 will deploy version 2.x
Yes please. 100 times this. Not everyone is ready to switch to the more cloud based synergy 2.
As for the user experience, the Software Update tool uses PackageKit which does not honor dnf excludes, and there doesn't seem to be anyway to exclude it with PackageKit.
It looks like this issue was already dealt with in F26 and F27 in Bug 1542286. The same clearly needs to be done for F28 here.
Seems that Synergy 2 is now considered Beta and unstable, an the 1.x versions are the only stable ones, see this thread:
Synergy 1 and 2 are incompatible license-wise and should be considered two separate pieces of software.