Applets don't work anymore so remove everything that has to do
with serving them.

See issue #534

Fixes issue #408

Fixes #360

Fixes #349

OpenJDK 7u111 on el6 now throws an exception if the TSA URL scheme
is https.

Debian patches libtool so that the default value of
link_all_deplibs is set to 'no' rather than 'unknown',
causing transitive dependencies in shared objects to
be lost.

The package is based on the contrib ubuntu-trusty debian package. The
following modifications have been made:

The current tigervnc sources can be used unmodified as the .orig
tarball for the debian package, so get-orig-source.sh is gone.

The ubuntu xorg-server-sources package provides the xorg sources used
to build tigervnc. The two small patches which where in the trusty
quilt series are now applied to the xorg sources after they have been
extracted. There is no quilt series anymore at this point.

Fltk 1.3.3 is available in the xenial repositories and it is used to build
xtigervncviewer. No need to get the fltk sources. patch_fltk.sh is gone.

Fixed some dependencies to reflect changes between trusty and xenial.

Removed configure options not recognized by configure.

The install target is not called a second time for the viewer package,
but the viewer files are moved from the server installation. (Eliminate
file conflicts during binary package installation.)

Note: Some dependencies (including libfltk1.3 and xorg-server-source) are
found in the xenial universe repository only.

Patch taken directly from f22 nettle package

NASM 2.01 can be rebuilt from el6 spec file

Additional change need for dynamic build of libX11

Building libX11 statically causes problems with libpthread, however
the version of libX11 that ships with el5 is too old to build libXext.
So we have to build a dynamic version of libX11 and link against that
while building.  The resulting binary will actually be linked against
the system libX11, which should be ABI compatible as far as Xvnc is
concerned.

These files are not Red Hat or Ubuntu specific, so install them
on all Unix systems where the viewer is installed.

Adds missing build dependencies and fixes java compile issues
caused by non-ascii characters in comments.

Adds missing build dependencies and fixes java compile issues
caused by non-ascii characters in comments.

Updating control file per suggestion in #258

[re #258] Add missing build-deps and allow deb to build on any arch

Obsoleted by 7461517

Obsoleted by 7461517

This makes it easier to handle common exceptions. I was motivated
because the Mesa URL is currently broken and wasn't handled well.

Implementation mostly copied from here:
  http://stackoverflow.com/questions/22676/how-do-i-download-a-file-over-http-using-python

Old UTF-8 resulted in this error from GNU Emacs:
  Warning (mule): Invalid coding system `UTF-8' is specified
  for the current buffer/file by the :coding tag.
  It is highly recommended to fix it before writing to a file.

Split the static library pre-reqs into a static-devel package
so that they don't need to be rebuilt everytime tigervnc's
sources change.

Several of the pre-requisites have outstanding CVEs.

Build with rpath link so that Xvnc finds our libGL even if
it's not installed in "/".  Also applied dridir and xkbcompdir
patches so that the correct DRI driver gets loaded.

Added patches for the following upstream CVEs: 2013-7439,
2015-0255, 2015-1802, 2015-1803, 2015-1804.  Also updated the
versions of gnutls, libtasn1, and libjpeg-turbo used to build
static libraries to their latest respective upstream versions.

Bump spec version to match changelog.

Patch file had different extension than what was specified in spec

Added patches for the following upstream CVEs: 2013-7439,
2015-0255, 2015-1802, 2015-1803, 2015-1804.  Also updated the
versions of gnutls, libtasn1, and libjpeg-turbo used to build
static libraries to their latest respective upstream versions.

The patch sources were removed but the %patch commands were
left in the spec files.

The patch sources were removed but the %patch commands were
left in the spec files.

This workaround is no longer needed as we've fixed the bad interaction
with libtool.