On Fri, 8 Nov 2019 at 18:20, Michael Halstead <[email protected]> wrote:
> > If you replace that with tigervnc (a modern, supported fork of > tightvnc), then the tests pass fine. > > https://tigervnc.org/ > > > > TigerVNC is now installed from the standard repos where available. > > > > > As Fedora has already obsoleted tightvnc in favor of tigervnc, I think > we should do the same on all debian machines (debian provides both tightvnc > and tigervnc, but treats them as equal). > > https://src.fedoraproject.org/rpms/tightvnc/blob/master/f/dead.package > > I also checked that tightvnc is not available for opensuse either. > > > Server components of TigerVNC are in xorg-x11-Xvnc package which is > installed on all the openSUSE workers so I expect the VNC server there to > work. Please let me know if they do not. > > > On Ubuntu 16.04 and Debian 8 workers I've installed from > https://bintray.com/tigervnc/stable/tigervnc/1.9.0. This should allow > tests to complete. Installing packages outside of the distribution's > package manager might invalidate these as sanity tested distros. I'd > appreciate feedback about this. > Thanks a lot! There are two things to check: 1. Old instances of vnc may still be running and should be shut down (via 'vncserver -kill :1') 2. vncserver executable should point to tigervnc (if both tigervnc and tightvnc are installed - I don't know if you removed the tightvnc packages). Otherwise everything should be ready for re-testing the patches. I can resend them if needed. Alex
-- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
