From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: x11-misc/x11vnc/
Date: Mon, 12 Apr 2021 17:33:19 +0000 (UTC) [thread overview]
Message-ID: <1618248785.57f031f9dc51a4053b856aee5c27fecd2fd39d21.sam@gentoo> (raw)
commit: 57f031f9dc51a4053b856aee5c27fecd2fd39d21
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Mon Apr 12 17:33:05 2021 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Mon Apr 12 17:33:05 2021 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=57f031f9
x11-misc/x11vnc: Stabilize 0.9.16-r5 x86, #768039
Signed-off-by: Sam James <sam <AT> gentoo.org>
x11-misc/x11vnc/x11vnc-0.9.16-r5.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/x11-misc/x11vnc/x11vnc-0.9.16-r5.ebuild b/x11-misc/x11vnc/x11vnc-0.9.16-r5.ebuild
index cb039cefad7..a2c8ee4e8d1 100644
--- a/x11-misc/x11vnc/x11vnc-0.9.16-r5.ebuild
+++ b/x11-misc/x11vnc/x11vnc-0.9.16-r5.ebuild
@@ -11,7 +11,7 @@ SRC_URI="https://github.com/LibVNC/x11vnc/archive/${PV}.tar.gz -> ${P}.tar.gz"
LICENSE="GPL-2+-with-openssl-exception"
SLOT="0"
-KEYWORDS="~alpha amd64 arm ~arm64 ~hppa ~ia64 ~mips ~ppc ~ppc64 ~s390 sparc ~x86 ~amd64-linux ~x86-linux ~sparc-solaris ~x64-solaris ~x86-solaris"
+KEYWORDS="~alpha amd64 arm ~arm64 ~hppa ~ia64 ~mips ~ppc ~ppc64 ~s390 sparc x86 ~amd64-linux ~x86-linux ~sparc-solaris ~x64-solaris ~x86-solaris"
IUSE="crypt fbcon libressl ssl +xcomposite +xdamage +xfixes xinerama +xrandr zeroconf"
COMMON_DEPEND="
next reply other threads:[~2021-04-12 17:33 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-12 17:33 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-03-11 17:15 [gentoo-commits] repo/gentoo:master commit in: x11-misc/x11vnc/ Sam James
2021-06-22 22:38 Sam James
2021-04-30 16:58 Mikle Kolyada
2021-04-12 22:08 Sam James
2021-04-12 22:08 Sam James
2021-04-12 17:33 Sam James
2021-04-08 6:23 Sergei Trofimovich
2021-04-07 22:44 Sam James
2020-12-26 20:54 Andreas Sturmlechner
2020-12-21 9:36 Sergei Trofimovich
2020-12-15 10:37 Sam James
2020-12-11 23:10 Sergei Trofimovich
2020-12-11 23:07 Sergei Trofimovich
2020-12-11 22:12 Sam James
2020-12-10 21:41 Thomas Deutschmann
2020-12-09 22:38 Sergei Trofimovich
2019-06-01 8:15 Michał Górny
2019-06-01 8:15 Michał Górny
2019-06-01 8:15 Michał Górny
2019-06-01 8:15 Michał Górny
2019-05-26 11:36 Andreas Sturmlechner
2019-05-26 11:25 Mikle Kolyada
2019-05-26 11:25 Mikle Kolyada
2019-05-26 11:25 Mikle Kolyada
2019-05-26 11:25 Mikle Kolyada
2019-05-26 7:04 Sergei Trofimovich
2019-05-24 22:50 Sergei Trofimovich
2019-05-24 22:08 Sergei Trofimovich
2019-05-24 20:18 Sergei Trofimovich
2019-05-21 18:55 Sergei Trofimovich
2019-05-21 18:41 Andreas Sturmlechner
2019-05-21 18:41 Andreas Sturmlechner
2019-05-21 18:41 Andreas Sturmlechner
2019-05-16 16:38 Matt Turner
2019-01-19 11:57 Jonas Stein
2019-01-15 21:51 Sven Wegener
2017-05-28 7:34 Michał Górny
2017-01-24 6:46 Jeroen Roovers
2017-01-15 20:24 Markus Meier
2017-01-01 12:43 Agostino Sarubbo
2016-12-29 10:05 Agostino Sarubbo
2016-12-18 16:26 Göktürk Yüksek
2016-12-06 9:30 Tobias Klausmann
2016-12-05 16:10 Pacho Ramos
2016-10-02 12:37 Pacho Ramos
2015-10-18 9:39 Ian Delaney
2015-09-24 7:59 Agostino Sarubbo
2015-09-20 17:35 Julian Ospald
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=1618248785.57f031f9dc51a4053b856aee5c27fecd2fd39d21.sam@gentoo \
--to=sam@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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