Bug#650394: preliminary tigervnc 1.1.0 package

2012-01-23 Thread Yaroslav Halchenko
Yeay! Ola Lundqvist o...@inguza.com wrote: I'll see if I can find some time to get this one into Debian. // Ola On Tue, Jan 10, 2012 at 11:44:53AM -0500, Yaroslav Halchenko wrote: FWIW -- I have being running the same instance of VNC since then and had no issues whatsoever... it might be

Bug#650394: preliminary tigervnc 1.1.0 package

2012-01-22 Thread Ola Lundqvist
I'll see if I can find some time to get this one into Debian. // Ola On Tue, Jan 10, 2012 at 11:44:53AM -0500, Yaroslav Halchenko wrote: FWIW -- I have being running the same instance of VNC since then and had no issues whatsoever... it might be worth dropping all four for the sake of 1

Bug#650394: preliminary tigervnc 1.1.0 package

2012-01-10 Thread Yaroslav Halchenko
FWIW -- I have being running the same instance of VNC since then and had no issues whatsoever... it might be worth dropping all four for the sake of 1 which works reliably ;) On Thu, 01 Dec 2011, Ola Lundqvist wrote: Hi Laszlo Yes this is really good news. If you want some help on the

Bug#650394: preliminary tigervnc 1.1.0 package

2011-11-30 Thread Yaroslav Halchenko
Hi Laszlo, Great to see efforts going forward ;-) What about making packaging available in some public VCS (I would prefer/recommend GIT) so we could collaborate more efficiently. Few brief comments (can't look in detail atm): * have you considered dh-autoreconf to help with the pain of

Bug#650394: preliminary tigervnc 1.1.0 package

2011-11-30 Thread Ola Lundqvist
Hi Laszlo Yes this is really good news. If you want some help on the alternatives part and splitting the package I can probably do that. I sort of got the hang of it after doing that for four different Vnc suites. :-) // Ola On Wed, Nov 30, 2011 at 06:01:11PM -0500, Yaroslav Halchenko wrote:

Bug#650394: preliminary tigervnc 1.1.0 package

2011-11-29 Thread Laszlo Boszormenyi
Hi Yaroslav, I've made a preliminary tigervnc package[1]. It builds and seems to be working. However it has some problems, like debian/copyright is not DEP5 compatible and due to upstream issues it can't be build two times in a row. Even worse, upstream tarball contains embedded code of libjpeg