Please package new upstream release

http://www.tightvnc.com/download.php

I vote for this bug.
v2.0.4 is already available.

Current one is known to have various issue (and just now crashed on me
again ... grrr)

yikes... 2.x series seems to be windows only but 1.3 series has got
1.3.10 which hopefully addressed some issues... here is an excerpt from
ChangeLog until it mentions 1.3.9

[Bugfixes] Fixes for 64-bit Linux issues, a patch from Russel Miranda
[Build fix] Updated built-in Java viewer to the latest version.
Made colorPath configurable via tightvncserver.conf, provided a better example of setting fontPath.
[Packaging] Version-specific information updated, version 1.3.10.
[Build fix] Updated built-in Java viewer to the latest version.
[Development] Reading configuration from files in the vncserver script.
Set SVN project language to English.
Updated the patch. Now it should create much better initial .vnc/xstartup file on first execution of the vncserver script. New xstartup script solves the problem with empty screen under Fedora Core 6, and provides an example of setting up desktop environment manually.
Xvnc's built-in Java viewer updated to its current version.

and patches do not apply cleanly now:

patching file vncserver
Hunk #1 FAILED at 1.
Hunk #2 succeeded at 19 with fuzz 2 (offset -4 lines).
Hunk #3 succeeded at 39 with fuzz 1 (offset -4 lines).
Hunk #4 FAILED at 58.
...

but these are benign...   ok -- building now and testing either those few fixes
solve my crash issues ;)

FWIW -- it builds fine across various debian / ubuntu releases BUT fails on
wheezy and sid on amd64 (full build, while on i386 I did -B) builds fails due
to failure of cleaning (see below)... myself is trying out tigervnc atm since
anyways that seems to be the way to go

 fakeroot debian/rules clean
dh_testdir
dh_testroot
rm -f build-arch-stamp build-indep-stamp config-stamp
rm -f debian/faq.txt debian/start.txt
xmkmf
mv -f Makefile Makefile.bak
imake -DUseInstalled -I/usr/lib/X11/config
(cd Xvnc; xmkmf)
mv -f Makefile Makefile.bak
imake -DUseInstalled -I/usr/lib/X11/config
# Add here commands to clean up after the build process.
rm -f config.log config.status config.cache config.guess config.sub
[ -f Makefile ] || /usr/bin/make distclean
[ -f Makefile ] || /usr/bin/make clean
test -r /usr/share/misc/config.sub && \
          cp -f /usr/share/misc/config.sub config.sub
make: [clean] Error 1 (ignored)
test -r /usr/share/misc/config.guess && \
          cp -f /usr/share/misc/config.guess config.guess
make: [clean] Error 1 (ignored)
(cd Xvnc; /usr/bin/make clean)
make[1]: Entering directory `/tmp/buildd/tightvnc-1.3.10/Xvnc'
rm -f -r ./exports/include
rm -f -r ./exports/lib
rm -f -r ./exports/bin
rm -f *.CKP *.ln *.BAK *.bak *.o core errs ,* *~ *.a .emacs_* tags TAGS make.log MakeOut   "#"*
cleaning in ./include...
make[2]: Entering directory `/tmp/buildd/tightvnc-1.3.10/Xvnc/include'
make[2]: *** No rule to make target `clean'.  Stop.
make[2]: Leaving directory `/tmp/buildd/tightvnc-1.3.10/Xvnc/include'
make[1]: *** [clean] Error 2
make[1]: Leaving directory `/tmp/buildd/tightvnc-1.3.10/Xvnc'
make: [clean] Error 2 (ignored)
(cd Xvnc/programs/Xserver; /usr/bin/make clean)

Hi Yaroslav

As you may know I'm looking for a new maintainer.
See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=586413

Ben and Timo have been interested before but have not yet taken over the
maintenance yet. So if you could help them or take it over entirelly I
would be happy.

Best regards,

// Ola

Hi,

Ola Lundqvist <opal@debian.org> writes:

I have recently migrated almost all my VNC usage scenarios to xpra. It
is not entirely stable yet but the upstream is very active so I'll
rather spend my time helping xpra at the moment.

Hi Timo

Thanks for letting us know. Xpra seems to be an interesting project.

Do you intend to package it for Debian?

// Ola

Hi,

Ola Lundqvist <ola@inguza.com> writes:

It is already in debian but I am currently following svn to help with
upstream development. Maybe in a year it will be so stable that I can
recommend the debian packages :-)

I could still participate in some way as a team member, but the time and
incentive just aren't there for me to lead this effort. So Yaroslav, by
all means, if you see something you want to do with this package, just
go ahead and do it.

Ben

oh dear... ;-)

well -- I guess I might upload (eventually) that 1.3.10; but altogether
I am not seeking for taking over these VNCs -- just check my QA page --
my plate is quite full.  Altogether it seems that optimally it
would be to package tigervnc (and virtualgl) -- it is actively developed
and surpasses in performance (seems to lack minor conveniences and
-via).

Hi Yaroslav
You are very welcome to do so. You have my blessing. As I understand both
Ben and Timo is no longer that interested in taking over VNC I'm looking
for more volonteers. :-) Any help is appriciated.

I have got rid of quite a few packages so maybe I will have some more time
for vnc in the future. The problem with vnc is that it takes so damn long
time to build...

Yes this would really be the optimal thing. There are lot of preferred things
with this approach, such as:
 - maintained actively developed
 - better features

However last time I tried (it is quite some time though) I did not get the
server part to work and things crashed very often, at least when
using the wrapper scripts making things convenient. But if you have successfully
get things to work well I'm interested in what version you used and how
you built it.

Best regards,

// Ola

PS. I'm trying to step down as Debian maintainer. Maintaining about 80
packages as I did in the past at the same time as a full time work and
a side buisness has been too much. :-)
DS.

even with ccache? ;) does it parallelize ok?

I went lazy way -- just grabbed binary tarball from their website which
installs under /opt.  For the 3rd day of intensive use -- not a single
complaint

I also got some binary deb build notes from  Antoine Martin -- may be they
would have some interesting bit so citing below (haven't looked through them
yet)

#magic to set DISTRIB_CODENAME
DISTRIB_CODENAME="wheezy"
VNC_VERSION="1.0.90-r4628"
ARCH=`uname -m | sed 's/x86_64/amd64/' | sed 's/i686/i386/'`

tar -zxvf tigervnc-${VNC_VERSION}.tar.gz
cd tigervnc-${VNC_VERSION}/

#CLIENT:
autoreconf -fiv
./configure --prefix=/usr
make
cd unix
rm -fr deb
cp vncviewer/vncviewer deb/usr/bin/
gzip -c vncviewer/vncviewer.man > deb/usr/share/man/man1/vncviewer.1.gz
mkdir -p deb/DEBIAN
cp tigervnc-viewer-${VNC_VERSION}.dsc deb/DEBIAN/control
cp vncviewer/vncviewer deb/usr/bin/
gzip -c vncviewer/vncviewer.man > deb/usr/share/man/man1/vncviewer.1.gz
mkdir -p deb/DEBIAN
cp tigervnc-viewer-${VNC_VERSION}.dsc deb/DEBIAN/control

SIZE=`du -sm deb | awk '{print $1}'`
echo "Architecture: ${ARCH}" >> deb/DEBIAN/control
#echo "Distribution: ${DISTRIB_CODENAME}" >> deb/DEBIAN/control
echo "Installed-Size: ${SIZE}" >> deb/DEBIAN/control
echo "Version: ${VNC_VERSION}" >> deb/DEBIAN/control
#echo "Filename: ${PKG_FILE_PATH}/${PKG}" >> deb/DEBIAN/control
echo "" >> deb/DEBIAN/control

sed "s/DISTRIBUTION/${DISTRIB_CODENAME}/g" <
./tigervnc-viewer-${VNC_VERSION}.changelog > deb/DEBIAN/changelog
echo "-- Antoine Martin <antoine@nagafix.co.uk>  `date -R`" >>
deb/DEBIAN/changelog
echo "" >> deb/DEBIAN/changelog

PKG="tigervnc-viewer-${VNC_VERSION}.${ARCH}.deb"
dpkg -b deb ${PKG}

#SERVER deb:
./build-xorg-7.4 init
./build-xorg -version 7.4 build --enable-glx --enable-glx-tls
--disable-config-hal --disable-config-udev                                                                                                                                                                                   
--with-default-font-path=/usr/share/fonts/X11/misc                                                                                                                                                                           
rm -fr deb
mkdir -p "deb/usr/share/man/man1"
mkdir -p "deb/usr/bin"
gzip -c "./xserver/hw/vnc/Xvnc.man" > "deb/usr/share/man/man1/Xvnc.1.gz"
for vnc_file in vncconfig vncserver x0vncserver vncpasswd; do
    VNC_BIN="${vnc_file}/${vnc_file}"
    if [ ! -e "${VNC_BIN}" ]; then
        VNC_BIN="./${vnc_file}"
        if [ ! -e "${VNC_BIN}" ]; then
            echo "Error: could not find ${vnc_file}"
            exit 1
        fi
    fi
    cp "${VNC_BIN}" "deb/usr/bin/"
    gzip -c "${VNC_BIN}.man" > "deb/usr/share/man/man1/${vnc_file}.1.gz"
done

mkdir -p deb/DEBIAN
cp tigervnc-server-${VNC_VERSION}.dsc deb/DEBIAN/control
SIZE=`du -sm deb | awk '{print $1}'`
echo "Architecture: ${ARCH}" >> deb/DEBIAN/control
#echo "Distribution: ${DISTRIB_CODENAME}" >> deb/DEBIAN/control
echo "Installed-Size: ${SIZE}" >> deb/DEBIAN/control
echo "Version: ${FULL_VERSION}" >> deb/DEBIAN/control
#echo "Filename: ${PKG_FILE_PATH}/${PKG}" >> deb/DEBIAN/control
echo "" >> deb/DEBIAN/control
sed "s/DISTRIBUTION/${DISTRIB_CODENAME}/g" <
./tigervnc-server-${VNC_VERSION}.changelog > deb/DEBIAN/changelog
echo "-- Antoine Martin <antoine@nagafix.co.uk>  `date -R`" >>
deb/DEBIAN/changelog
echo "" >> deb/DEBIAN/changelog

PKG="tigervnc-server-${FULL_VERSION}.${ARCH}.deb"
dpkg -b deb ${PKG}

yeah -- 80 alone sounds a bit too much ;)
Thanks for all your work you have done though!

Dear Maintainer,

it would be really great to have the latest upstream release (version
2.7.10 from 2013-07-24) packaged. Besides tons of other changes
compared to 1.3.9, it supposedly fixes sending "Option" key presses
("Windows" key on the local side) to remote native (i.e. built-in) Mac
OS X VNC servers.

(Sorry, can't help with packaging — completely booked out myself. I'd
be happy to test the package if somebody else prepares one, though).

Thanks for taking care of TightVNC in Debian for so long; it's been of
great help!

Sascha

Hi Sascha

I'll see what I can do. The package is up for adoption as I have little
spare time (kids...), but I'll see if I can get some free time some day.

// Ola

Hi

Thanks for the additional information. Yes tigervnc is probably the best
option. It is on my todo list, but it has been there for at least three
years now so I guess it will not happen (by me) anytime soon. :-(

// Ola

Dear Ola,

Ola Lundqvist <ola@inguza.com> writes:
       non-Apple VNC viewer to the built-in Mac OS X VNC server.

When trying to install TightVNC 2.7.10 locally for the time being, we
noticed that there actually is no TightVNC for Unix anymore, despite
what the home page says. There is TightVNC 2.7.10 for Windows and there
is the TightVNC Java Viewer 2.7.2. That's it. :-/

We got TigerVNC installed locally, but couldn't get the Option key to
work at all using any of the key symbols that were mentioned anywhere
related to VNC on Mac OS X or that might have made sense in this context
(Meta_L/R, Alt_L/R, Hyper_L/R, ISO_Level3_Shift, Mode_switch,
Menu). Even if we send the same sequence ("xte 'keydown Shift_L'
'keydown Meta_L' 'sleep 1' 'keyup Shift_L' 'keyup Alt_L'") the built-in
Mac OS X VNC client sends when connected to vnc4server running on Linux,
it doesn't work. So AFAICT there's no way for a non-Apple VNC viewer
that will make the built-in VNC server of Mac OS X trigger an Option key
press (it does work using the built-in Apple VNC viewer). Anyone who got
the Option key to work probably is using a third-party VNC server on the
Mac OS X side.

We've given up on controlling the Mac via VNC for now as there were
other issues as well (dragging something in Xcode didn't work and there
were no apparent other ways of achieving the same result). Might try
again using a third party VNC server some other time.

So while having TigerVNC (not TightVNC as there is no Unix version
anymore) in Debian would be great, it doesn't really solve the Option
key issue. The fix in TightVNC 2.7.10 is probably for the Windows
TightVNC viewer to properly send the "Windows" key (Super_L). The VNC
viewers available in Debian already send the key presses as-is, it's the
server side that doesn't handle them correctly.

Sascha

To all whom it may concern:

Upstream does not maintain Thightvnc on Linux any more. Tightvnc 1.3.10
is the latest available version.

I recommend to try tigervnc or gnome-remote-desktop.

Sven