Hi, I'm on Debian stretch with libss-4 v.0.8.0 installed from stretch-backports due to Remmina requirements. Installed x2goclient is v. 4.1.2.1, from you release builds repo. Now Remmina asks me to update but that would update libssh4 to v.0.8.1 (https://packages.debian.org/stretch-backports/libssh-4) that is unsupported by x2goclient.
Would you consider updating it?
Greetings.
On Tue, 20 Nov 2018 09:28:30 +0000, xalloc <xalloc@protonmail.com> wrote:
Hi, I'm on Debian stretch with libss-4 v.0.8.0 installed from stretch-backports due to Remmina requirements. Installed x2goclient is v. 4.1.2.1, from you release builds repo. Now Remmina asks me to update but that would update libssh4 to v.0.8.1 (https://packages.debian.org/stretch-backports/libssh-4) that is unsupported by x2goclient.
Would you consider updating it?
There is a similar problem for RPM-based distributions -- see Bug #1338 at <https://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=1338> for my report and for my solution. This can probably be adapted to .deb-based distributions.
Regards, Tristan
--
Tristan MillerFree Software developer, ferret herder, logologist https://logological.org/
Thanks Miller for the answer.
"However, updating the dependency to a modern libssh requires changing not only the RPM spec file but also the x2goclient source code." That is something x2go devs will be forced to do sooner or later, if distros don't distribute anymore that libssh version.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ Il martedì 20 novembre 2018 11:03, Tristan Miller <psychonaut@nothingisreal.com> ha scritto:
Greetings.
On Tue, 20 Nov 2018 09:28:30 +0000, xalloc xalloc@protonmail.com wrote:
Hi, I'm on Debian stretch with libss-4 v.0.8.0 installed from stretch-backports due to Remmina requirements. Installed x2goclient is v. 4.1.2.1, from you release builds repo. Now Remmina asks me to update but that would update libssh4 to v.0.8.1 (https://packages.debian.org/stretch-backports/libssh-4) that is unsupported by x2goclient. Would you consider updating it?
There is a similar problem for RPM-based distributions -- see Bug #1338 at https://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=1338 for my report
and for my solution. This can probably be adapted to .deb-based distributions.
Regards, Tristan
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Tristan Miller Free Software developer, ferret herder, logologist https://logological.org/
Greetings.
On Tue, 20 Nov 2018 14:06:07 +0000, xalloc <xalloc@protonmail.com> wrote:
"However, updating the dependency to a modern libssh requires changing not only the RPM spec file but also the x2goclient source code." That is something x2go devs will be forced to do sooner or later, if distros don't distribute anymore that libssh version.
"Forced" might be too strong a word. Plenty of distributions apply their own patches to fix bugs and dependency issues that various software package developers leave unfixed for years, or even decades.
I'd like to hope that the X2Go developers would not be so negligent as to let their Debian and openSUSE packages languish in an essentially unusable state. (In fact, the problem must also affect those building from source on modern systems.) But being a volunteer developer of other projects, I know that time is often in short supply.
I've included a patch with my bug report so hopefully this has taken most of the work out of solving the problem.
Regards, Tristan
--
Tristan MillerFree Software developer, ferret herder, logologist https://logological.org/
On Tue, Nov 20, 2018 at 3:36 PM Tristan Miller <psychonaut@nothingisreal.com> wrote:
I'd like to hope that the X2Go developers would not be so negligent as to let their Debian and openSUSE packages languish in an essentially unusable state. (In fact, the problem must also affect those building from source on modern systems.) But being a volunteer developer of other projects, I know that time is often in short supply.
Mihai is doing a great job in doing all that packaging stuff! Mike even is a Debian maintainer. So I am really astounded that there are problems with Debian packages.
Uli
- On 11/20/18 8:01 PM, Ulrich Sibiller wrote:
So I am really astounded that there are problems with Debian packages.
There aren't any problems with released packages. So far, only nightly packages for newer/unstable distro versions were affected.
The problem is that stretch-backports has a newer version of libssh which is incompatible to the old one (well, more or less, definitely shipping one library less), so X2Go Client needs to be rebuilt.
We're not building with backports enabled, so even a new version of X2Go Client won't fix this issue for those users that pull in libssh through stable-backports. Since this is a build-time check and feature, the only way to make this work correctly is to rebuild X2Go Client from source (after the next release, anyway).
Mihai
Hi,
On Di 20 Nov 2018 15:06:07 CET, xalloc wrote:
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ Il martedì 20 novembre 2018 11:03, Tristan Miller
<psychonaut@nothingisreal.com> ha scritto:Greetings.
On Tue, 20 Nov 2018 09:28:30 +0000, xalloc xalloc@protonmail.com wrote:
Hi, I'm on Debian stretch with libss-4 v.0.8.0 installed from stretch-backports due to Remmina requirements. Installed x2goclient is v. 4.1.2.1, from you release builds repo. Now Remmina asks me to update but that would update libssh4 to v.0.8.1 (https://packages.debian.org/stretch-backports/libssh-4) that is unsupported by x2goclient. Would you consider updating it?
There is a similar problem for RPM-based distributions -- see Bug #1338 at https://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=1338 for my report
and for my solution. This can probably be adapted to .deb-based distributions.
Thanks Miller for the answer.
"However, updating the dependency to a modern libssh requires changing not only the RPM spec file but also the x2goclient source code." That is something x2go devs will be forced to do sooner or later, if
distros don't distribute anymore that libssh version.
The reasons for this issue are two:
When mixing X2Go upstream DEBs for Debian stable with packages from
stretch-backports, you are on your own. Not recommended.X2Go Client's master branch has the required patch for libssh4 0.8.x
(and 0.8.0 was buggy in the first place). But a release of X2Go Client
has not happened for the last 4 months. It's overdue.
Your interim solution: use X2Go Client upstream DEBs from the heuler
repo hero (nightly builds). Same probably applies for the RPM builds
of X2Go Client.
Hope this helps, Mike
--
DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby mobile: +49 (1520) 1976 148 landline: +49 (4354) 8390 139
GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
Dear Mike,
On Wed, 21 Nov 2018 19:31:38 +0000, Mike Gabriel <mike.gabriel@das-netzwerkteam.de> wrote:
Same probably applies for the RPM builds
of X2Go Client.
I don't think the same applies to the RPM builds for openSUSE Tumbleweed. Tumbleweed is a rolling release that tends to package the latest stable release of all packages, including libssh, whereas the package in the heuler X2Go repository (contrary to what you write about the master branch having been patched) depends on a much older version of libssh. Or at least, it did at the time that I filed my bug report. Unless this has since changed, all Tumbleweed users will still be unable to install the heuler packages even if they haven't added any other repositories.
Regards, Tristan
--
Tristan MillerFree Software developer, ferret herder, logologist https://logological.org/
Thanks everyone for the answers, I ended installing the version from heuler nightly builds. Then launching it gave the error "x2goclient: error while loading shared libraries: libssh_threads.so.4: cannot open shared object file: No such file or directory" It was enough a "sudo ln -s /usr/lib/x86_64-linux-gnu/libssh.so.4.5.1 /usr/lib/x86_64-linux-gnu/libssh_threads.so.4", everything works.
Thanks again
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ Il mercoledì 21 novembre 2018 20:31, Mike Gabriel <mike.gabriel@das-netzwerkteam.de> ha scritto:
Hi,
On Di 20 Nov 2018 15:06:07 CET, xalloc wrote:
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ Il martedì 20 novembre 2018 11:03, Tristan Miller > psychonaut@nothingisreal.com ha scritto:
Greetings. On Tue, 20 Nov 2018 09:28:30 +0000, xalloc xalloc@protonmail.com wrote:
Hi, I'm on Debian stretch with libss-4 v.0.8.0 installed from stretch-backports due to Remmina requirements. Installed x2goclient is v. 4.1.2.1, from you release builds repo. Now Remmina asks me to update but that would update libssh4 to v.0.8.1 (https://packages.debian.org/stretch-backports/libssh-4) that is unsupported by x2goclient. Would you consider updating it?
There is a similar problem for RPM-based distributions -- see Bug #1338 at https://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=1338 for my report and for my solution. This can probably be adapted to .deb-based distributions.
Thanks Miller for the answer. "However, updating the dependency to a modern libssh requires changing not only the RPM spec file but also the x2goclient source code." That is something x2go devs will be forced to do sooner or later, if > distros don't distribute anymore that libssh version.
The reasons for this issue are two:
When mixing X2Go upstream DEBs for Debian stable with packages from stretch-backports, you are on your own. Not recommended.
X2Go Client's master branch has the required patch for libssh4 0.8.x (and 0.8.0 was buggy in the first place). But a release of X2Go Client has not happened for the last 4 months. It's overdue.
Your interim solution: use X2Go Client upstream DEBs from the heuler repo hero (nightly builds). Same probably applies for the RPM builds of X2Go Client.
Hope this helps, Mike
DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby mobile: +49 (1520) 1976 148 landline: +49 (4354) 8390 139
GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
-
Mihai Moldovan -
Mike Gabriel -
Tristan Miller -
Ulrich Sibiller -
xalloc