Is unison removal from Leap 16 permanent?
No idea, it is still in TW, but it’s also available as a flatpak
When using unison from a remote machine flatpak packaged version doesn’t cut it; the incoming ssh unison connection attempts to invoke “unison”; some sort of alias needs to be set-up somewhere (?) for:
“flatpak run io.github.bcpierce00.unison”
Context: I have installed a flatpak version of unison on the “server” machine.
From a remote machine, if a select a unison profile that uses ssh to connect to the “server” machine; the remote machine outputs an error message indicating that unison command not found.
I have tried setting up an alias in .bashrc and .profile:
alias unison='flatpak run io.github.bcpierce00.unison'
The alias appears to not be expanded for the incoming ssh unison command scenario, as I still get the unison command not found error.
Question: how do I attach an alias to the incoming ssh unison command such that the flatpak unison command gets invoked.
Aliases as well as both those scripts are only used by the interactive shell.
Create an executable script that does whatever you need and place it in the /usr/local/bin. Defining function in ~/.bashrc may work too.
inserting scripts outside of the home directory feels kind of wrong.
What are your thought about placing script inside /usr/local/sbin ? I have previously placed two systemd scripts inside that directory and neither have been overwritten so far.
I have placed a unison bash script in /usr/local/bin to invoke the flatpak version; I have now encountered a new issue, neither DISPLAY or WAYLAND_DISPLAY environment variables are set for remote ssh command causing unison to abort. From a normal login they are set as follows:
$ echo $DISPLAY
:1
$ echo $WAYLAND_DISPLAY
wayland-0
I have added a couple of variable exports and now have a connection; if there are other graphical apps that can be invoked remotely through ssh to act in a server mode, then they may also need an associated script to set-up DISPLAY and/or WAYLAND_DISPLAY as things stand.
Any back to unison, now get error:
Timed out negotiating connection with the server
The client machine is a laptop with Arch installed.
unison version 2.53.8 (0caml 5.4.0)
The flatpak repo version on the openSUSE server:
unison version 2.53.7 (ocaml 5.2.0)
Looking online, unison version 2.52 or later should allow negotiation of protocol to overcome interoperability issues. Thwarted at every turn.
There is one for 16.0 in OBS Archiving:
https://software.opensuse.org/package/unison
unison-2.53.8, submitted just 21 hours ago.
Do you mean it worked when your application was not flatpak?
Yes (last 15 release 15.7 ?), and I was running Wayland session at login on the SUSE box receiving the ssh command connection request.
Apparently there are text and GUI variants of Unison binaries. Are you sure it did not try to use the text variant? Did you try to follow instructions on the https://flathub.org/ru/apps/io.github.bcpierce00.unison how to run the flatpak remotely via SSH?
I can see it opening the unison GUI on the SUSE server.
I removed all the flatpak install and installed a version from one of the unsupported repositories; now unison works OK through ssh. Looks like the lack of DISPLAY and WAYLAND_DISPLAY environment variables is a flatpak thing.