Arch Linux User Repository

Maybe as a workaround, the PKGBUILD can just patch the vncviewer binary (where patchelf becomes a build dependency)? It's not a great solution (because compatibility is a thing with shared objects), but it's a nice workaround for out-of-the-box support till RealVNC offers builds against newer libcrypt. Looks like libxcrypt-compat is no longer available on the AUR.

https://aur.archlinux.org/packages/libxcrypt-compat -> returns 404.

This is what I am doing as a workaround. I think patchelf is a better solution than creating a symlink just because the symlink suggests that libcrypt.so.1 is actually available (when it isn't/falsely pointing to libcrypt.so.2.0.0).

sudo patchelf --replace-needed libcrypt.so.1 libcrypt.so.2 /usr/bin/vncviewer

One can also install libxcrypt-compatin the meantime, I am looking for the best solution before amending the package.

With realvnc-vnc-viewer 6.21.1109-1 and recent updates, there will be an issue:

vncviewer 
vncviewer: error while loading shared libraries: libcrypt.so.1: cannot open shared object file: No such file or directory

Then search shows

find /usr -type f -iname "*libcrypt.so*"
/usr/lib32/libcrypt.so.2.0.0
/usr/lib/libcrypt.so.2.0.0

Solution:

sudo ln -s /usr/lib/libcrypt.so.2.0.0 /usr/lib/libcrypt.so.1

Hopefully it would be possible to update realvnc-vnc-viewer against newer library version in order to avoid such issue.

@allexj

isn't "i couldn't find the way to execute" and "i could open it .. searching in the apps" contradictory in fact? i do see .desktop file being included so.. are you trying to say that it did not appear in any of the app categories? what WM are you using?

I couldn't find the way to execute it. I found out that I could open it typing in terminal "vncviewer" or searching in the apps for "VNC Viewer"

aarch64 can be added as an architecture since RealVNC now has a build that is available in the raspbian-arm64 repos. http://archive.raspberrypi.org/debian/pool/main/r/realvnc-vnc/realvnc-vnc-viewer_6.20.530.42683_arm64.deb

Edit: Due to versioning and upstream conflicts I made my own package.

@jose1711 binary name is an upstream choice, then this seems like a good idea you can submit to tightvncviewer and/or realvnc. If they are ok with it it's fine, if it's too complicated or causes issues from their point of view it would be good to know. Also if you have examples of official packages changing binary names, I will follow the best practices from TUs.

hi, thanks for packaging. could you please consider removing conflicts array b/c the only reason i want to keep realvnc is raspberry pi, but otherwise i am quite happy with tightvncviewer.

the idea is to rename binary in order to avoid conflict:

--- PKGBUILD.orig       2020-12-17 22:37:45.966662008 +0100
+++ PKGBUILD    2020-12-17 22:33:47.953329984 +0100
@@ -11,7 +11,6 @@
 url='https://www.realvnc.com/'
 license=('custom')
 depends=('libsm' 'libxext')
-conflicts=('tightvnc' 'tigervnc' 'turbovnc')
 source_x86_64=("https://www.realvnc.com/download/file/viewer.files/VNC-Viewer-${pkgver}-Linux-x64.deb")
 source_i686=("https://www.realvnc.com/download/file/viewer.files/VNC-Viewer-${pkgver}-Linux-x86.deb")
 source_armv7h=("https://www.realvnc.com/download/file/viewer.files/VNC-Viewer-${pkgver}-Linux-ARM.deb")
@@ -22,5 +21,8 @@
 package() {
     bsdtar -xv -C "${pkgdir}" -f "${srcdir}/data.tar.xz"
     mkdir -p "${pkgdir}/usr/share/licenses/${pkgname}"
+    mv "${pkgdir}"/usr/bin/{vncviewer,realvncviewer}
+    mv "${pkgdir}"/usr/share/man/man1/{vncviewer,realvncviewer}.1.gz
+    sed -i '/Exec=/s/=vncviewer/=realvncviewer/' "${pkgdir}"/usr/share/applications/realvnc-vncviewer.desktop
     ln -s /usr/share/doc/${pkgname}/copyright "${pkgdir}/usr/share/licenses/${pkgname}/LICENSE"
 }

thank you, j

miss sha1sums_armv7h=('95bc648180924cb7b2105378a3ce7b2c41030e29')