http://bugzilla.suse.com/show_bug.cgi?id=1169661 http://bugzilla.suse.com/show_bug.cgi?id=1169661#c6 --- Comment #6 from Simon Lees <simonf.lees@suse.com> --- Hi All, To start with it wasn't my intention to start migrating tumbleweed users from synergy to barrier yet, (My fault for not paying close enough attention to the new spec). My plan was to first do some testing (so far working really well, but today i'll aim to get a windows machine involved). But given i'm happy with the results so far i'm pretty much ready to move to the next stage which is as follows. I intend to only include barrier in Leap 15.2, and drop synergy from tumbleweed at the end of the 15.1 lifecycle. Synergy upstream no longer care about the 1.X branch and have long moved onto 2.0 which is an electron based app much of which is not open sourced. I will mention that someone can take over the package if they really really want to but i'd still prefer to migrate most users around 15.2 release time. Given that some users will have a combination of 15.1, 15.2 and tumbleweed adding the package via maintenance update does make sense so i'll do that as well. As for migrating configs, generally because synergy is run / configured by users the config files end up in there home directory which makes migration pretty much impossible from a packaging level. But there is a first run wizard and it is written in Qt which I know well so it wouldn't be a huge amount of effort to write another dialog page that checks for synergy configs and attempts to migrate them. I'll probably just need to find a day or to to implement and test it. -- You are receiving this mail because: You are on the CC list for the bug.