<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Nov 8, 2019 at 9:56 AM Alexander Kanavin <<a href="mailto:alex.kanavin@gmail.com">alex.kanavin@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr">On Fri, 8 Nov 2019 at 18:20, Michael Halstead <<a href="mailto:mhalstead@linuxfoundation.org" target="_blank">mhalstead@linuxfoundation.org</a>> wrote:<br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">> If you replace that with tigervnc (a modern, supported fork of tightvnc), then the tests pass fine.<br>> <a href="https://tigervnc.org/" target="_blank">https://tigervnc.org/</a><br>><br><br>TigerVNC is now installed from the standard repos where available.<br> <br>><br>> 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).<br>> <a href="https://src.fedoraproject.org/rpms/tightvnc/blob/master/f/dead.package" target="_blank">https://src.fedoraproject.org/rpms/tightvnc/blob/master/f/dead.package</a><br>> I also checked that tightvnc is not available for opensuse either.<br><br><br>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.<br><br><br>On Ubuntu 16.04 and Debian 8 workers I've installed from <a href="https://bintray.com/tigervnc/stable/tigervnc/1.9.0" target="_blank">https://bintray.com/tigervnc/stable/tigervnc/1.9.0</a>. 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.<br></div></blockquote><div><br></div><div>Thanks a lot! There are two things to check:</div><div>1. Old instances of vnc may still be running and should be shut down (via 'vncserver -kill :1')</div><div>2. vncserver executable should point to tigervnc (if both tigervnc and tightvnc are installed - I don't know if you removed the tightvnc packages).</div></div></div></blockquote><div><br></div><div>I removed tightvnc and all workers have been rebooted so we are good to go.</div><div><br></div><div>Any comment on using packages from outside of the distro's official packaging?</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_quote"><div><br></div><div>Otherwise everything should be ready for re-testing the patches. I can resend them if needed.</div><div><br></div><div>Alex<br></div></div></div>
</blockquote></div></div>