From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: [PR PATCH] turbovnc: update to 2.2.2.
Date: Tue, 04 Jun 2019 18:04:15 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-12133@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 360 bytes --]
There is a new pull request by xtraeme against master on the void-packages repository
https://github.com/xtraeme/void-packages turbovnc-2.2.2
https://github.com/void-linux/void-packages/pull/12133
turbovnc: update to 2.2.2.
Signed-off-by: Juan RP <xtraeme@gmail.com>
A patch file from https://github.com/void-linux/void-packages/pull/12133.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-turbovnc-2.2.2-12133.patch --]
[-- Type: application/text/x-diff, Size: 2267 bytes --]
From 9e0521995f3cb0431914eb3e4f16d8916078078c Mon Sep 17 00:00:00 2001
From: Juan RP <xtraeme@gmail.com>
Date: Tue, 4 Jun 2019 18:03:35 +0200
Subject: [PATCH] turbovnc: update to 2.2.2.
Signed-off-by: Juan RP <xtraeme@gmail.com>
---
srcpkgs/turbovnc/patches/fix-libressl.patch | 18 +++++++-----------
srcpkgs/turbovnc/template | 6 +++---
2 files changed, 10 insertions(+), 14 deletions(-)
diff --git a/srcpkgs/turbovnc/patches/fix-libressl.patch b/srcpkgs/turbovnc/patches/fix-libressl.patch
index bdfc3094c20..0584ff6a858 100644
--- a/srcpkgs/turbovnc/patches/fix-libressl.patch
+++ b/srcpkgs/turbovnc/patches/fix-libressl.patch
@@ -1,17 +1,13 @@
-diff --git a/unix/Xvnc/programs/Xserver/hw/vnc/rfb.h b/unix/Xvnc/programs/Xserver/hw/vnc/rfb.h
-index 9b82d2f..8c35061 100644
---- unix/Xvnc/programs/Xserver/hw/vnc/rfb.h
-+++ unix/Xvnc/programs/Xserver/hw/vnc/rfb.h
-@@ -81,6 +81,11 @@
- the CPU count */
- #define MAX_ENCODING_THREADS 8
+--- unix/Xvnc/programs/Xserver/hw/vnc/rfb.h.orig 2019-06-04 18:00:21.482107165 +0200
++++ unix/Xvnc/programs/Xserver/hw/vnc/rfb.h 2019-06-04 18:00:37.826303493 +0200
+@@ -29,6 +29,10 @@
+ #ifndef __RFB_H__
+ #define __RFB_H__
+/* Fix for libressl */
+#ifndef OPENSSL_INIT_SETTINGS
+#define OPENSSL_INIT_SETTINGS void
+#endif
-+
- extern const char *display;
-
-
+ #ifdef HAVE_DIX_CONFIG_H
+ #include <dix-config.h>
diff --git a/srcpkgs/turbovnc/template b/srcpkgs/turbovnc/template
index 07e9326488a..01909c6c917 100644
--- a/srcpkgs/turbovnc/template
+++ b/srcpkgs/turbovnc/template
@@ -1,6 +1,6 @@
# Template file for 'turbovnc'
pkgname=turbovnc
-version=2.2.1
+version=2.2.2
revision=1
build_style=cmake
configure_args="-DTJPEG_LIBRARY=/usr/lib/libturbojpeg.so -DTVNC_BUILDJAVA=0
@@ -14,9 +14,9 @@ maintainer="Juan RP <xtraeme@voidlinux.org>"
license="GPL-2.0-or-later"
homepage="http://virtualgl.org"
distfiles="${SOURCEFORGE_SITE}/turbovnc/${pkgname}-${version}.tar.gz"
-checksum=d8c710dcf2128c235f8f203ec77b306c56b25d61134b47aeb55acaab4c2d3a61
+checksum=7f1593a3db88dc800d0f82091252ca293b1980a28417b9834ce713eb7e0d09bc
-conf_files="/etc/turbovncserver.conf /etc/turbovncserver-security.conf"
+conf_files="/etc/*.conf"
archs="i686* x86_64* ppc64*"
conflicts="tigervnc>=0"
next reply other threads:[~2019-06-04 16:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-04 16:04 voidlinux-github [this message]
2019-06-04 17:50 ` [PR PATCH] [Merged]: " voidlinux-github
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-12133@inbox.vuxu.org \
--to=voidlinux-github@inbox.vuxu.org \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).