Bug 1614674 - Synergy 1 is replaced by incompatible version when running "dnf update"
Summary: Synergy 1 is replaced by incompatible version when running "dnf update"
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: synergy
Version: 29
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Christian Krause
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2018-08-10 08:05 UTC by Zdenek Sedlak
Modified: 2019-03-14 10:00 UTC (History)
4 users (show)

Clone Of:
Last Closed:

Attachments (Terms of Use)

Description Zdenek Sedlak 2018-08-10 08:05:26 UTC
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-1.10.0-40 (Symless)
synergy-2.0.0-3.fc28 (Fedora official repo)

How reproducible:

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

Actual results:
Synergy gets updated to an incompatible version

Expected results:
Synergy won't get updated

Additional info:
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

Comment 1 Perry Gagne 2018-08-22 15:09:14 UTC
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.

Comment 2 orion0205 2018-09-28 17:59:55 UTC
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.

Comment 3 Perry Gagne 2019-01-04 20:20:08 UTC
Seems that Synergy 2 is now considered Beta and unstable, an the 1.x versions are the only stable ones, see this thread:

Comment 4 Antti Nilakari 2019-03-14 10:00:53 UTC
Synergy 1 and 2 are incompatible license-wise and should be considered two separate pieces of software.

Note You need to log in before you can comment on or make changes to this bug.