jdouglass Posted August 3, 2017 Share Posted August 3, 2017 I'm on a debian 9 workstation. When I download the .deb and try to install via sudo apt install ./Synergy_2.0.0.beta3~b542+489f59a6_amd64.deb I get the following output: Reading package lists... Done Building dependency tree Reading state information... Done Note, selecting 'synergy' instead of './Synergy_2.0.0.beta3~b542+489f59a6_amd64.deb' Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: synergy : Depends: libssl1.0.0 (>= 1.0.0) but it is not installable E: Unable to correct problems, you have held broken packages. As the error notes, there's no libssl1.0.0 package, and if I bypass the error and install the package anyways, I get an error stating that the libssl.so shared object cannot be found. Would it be possible to provide a debian 9 version of the binaries or else the source code for the 2.0 beta so I can compile it myself? Thanks! Link to comment Share on other sites More sharing options...
Synergy Team Nick Bolton Posted August 4, 2017 Synergy Team Share Posted August 4, 2017 @Andrew Nelless We'll be shipping a Debian 9 version, right? Link to comment Share on other sites More sharing options...
swaziloo Posted August 25, 2017 Share Posted August 25, 2017 For what it's worth, you can install on debian 9 by adding the jessie backports to /etc/apt/sources.list: deb http://ftp.us.debian.org/debian/ jessie-backports main deb-src http://ftp.us.debian.org/debian/ jessie-backports main With those added to sources.list: > sudo apt-get update > sudo dpkg -i Synergy_2.0.0.beta3-b542+489f59a6_amd64.deb > sudo apt-get install -f Link to comment Share on other sites More sharing options...
jdouglass Posted August 25, 2017 Author Share Posted August 25, 2017 Hey @swaziloo, thanks for the info! After adding `jessie-backports`, Synergy does indeed install just fine. Link to comment Share on other sites More sharing options...
bitbox Posted September 9, 2017 Share Posted September 9, 2017 I added jessie-backports to etc/apt/sources.list when i sudo dpkg -i Synergy_2.0.0.beta3-b542+489f59a6_amd64.deb i get back : dpkg: error: cannot access archive 'Synergy_2.0.0.beta3-b542+489f59a6_amd64.deb': No such file or directory is it no longer in the repo? Link to comment Share on other sites More sharing options...
jdouglass Posted September 10, 2017 Author Share Posted September 10, 2017 Hi @bitbox, the .deb had come from the synergy download page (https://symless.com/synergy/downloads) instead of a repo. Link to comment Share on other sites More sharing options...
bitbox Posted September 10, 2017 Share Posted September 10, 2017 13 hours ago, jdouglass said: Hi @bitbox, the .deb had come from the synergy download page (https://symless.com/synergy/downloads) instead of a repo. Yes, I misunderstood. Was running dpkg in the wrong folder, and I hadn't realized the jessie backports repo was to get the libssl1.0.0 dependency. After adding the repo, updating and running sudo apt install ./Synergy_2.0.0.beta3~b542+489f59a6_amd64.deb in the correct folder, I was fine. 2.0 running on both of my Deb9 machines. Next...the windows-10 surface 3 tablet. Kill me now... Link to comment Share on other sites More sharing options...
Paul C Posted September 29, 2017 Share Posted September 29, 2017 Hi Personnaly I don't think that dynamic linking to security libs (ie: ssl) is a good idea... Regards Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.