public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Jeroen Roovers" <jer@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-misc/openvpn/
Date: Sun, 10 Apr 2016 08:27:40 +0000 (UTC)	[thread overview]
Message-ID: <1460276858.9873edee95bd77cb6568ce239dcdb3a12b3c341f.jer@gentoo> (raw)

commit:     9873edee95bd77cb6568ce239dcdb3a12b3c341f
Author:     Jeroen Roovers <jer <AT> gentoo <DOT> org>
AuthorDate: Sun Apr 10 08:27:27 2016 +0000
Commit:     Jeroen Roovers <jer <AT> gentoo <DOT> org>
CommitDate: Sun Apr 10 08:27:38 2016 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=9873edee

net-misc/openvpn: Stable for HPPA PPC64 (bug #579260).

Package-Manager: portage-2.2.28
RepoMan-Options: --ignore-arches

 net-misc/openvpn/openvpn-2.3.10-r1.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/net-misc/openvpn/openvpn-2.3.10-r1.ebuild b/net-misc/openvpn/openvpn-2.3.10-r1.ebuild
index 8d18072..b9635cf 100644
--- a/net-misc/openvpn/openvpn-2.3.10-r1.ebuild
+++ b/net-misc/openvpn/openvpn-2.3.10-r1.ebuild
@@ -12,7 +12,7 @@ HOMEPAGE="http://openvpn.net/"
 
 LICENSE="GPL-2"
 SLOT="0"
-KEYWORDS="~alpha amd64 ~arm ~hppa ~ia64 ~mips ~ppc ~ppc64 ~s390 ~sh ~sparc ~x86 ~sparc-fbsd ~x86-fbsd ~x86-freebsd ~amd64-linux ~arm-linux ~x86-linux"
+KEYWORDS="~alpha amd64 ~arm hppa ~ia64 ~mips ~ppc ppc64 ~s390 ~sh ~sparc ~x86 ~sparc-fbsd ~x86-fbsd ~x86-freebsd ~amd64-linux ~arm-linux ~x86-linux"
 IUSE="examples down-root iproute2 libressl +lzo pam pkcs11 +plugins polarssl selinux socks +ssl static systemd userland_BSD"
 
 REQUIRED_USE="static? ( !plugins !pkcs11 )


             reply	other threads:[~2016-04-10  8:27 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-10  8:27 Jeroen Roovers [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-01-24 15:24 [gentoo-commits] repo/gentoo:master commit in: net-misc/openvpn/ Manuel Rüger
2017-01-24 15:19 Manuel Rüger
2017-01-05  1:02 Manuel Rüger
2017-01-05  1:02 Manuel Rüger
2016-12-16 21:35 Patrick McLean
2016-12-16 21:31 Patrick McLean
2016-12-04  5:37 Patrick McLean
2016-12-04  5:32 Patrick McLean
2016-12-03  2:48 Patrick McLean
2016-12-03  2:48 Patrick McLean
2016-11-17  2:04 Patrick McLean
2016-09-29 13:28 Agostino Sarubbo
2016-09-29 12:35 Agostino Sarubbo
2016-09-29  9:35 Agostino Sarubbo
2016-09-29  8:40 Agostino Sarubbo
2016-09-24 19:19 Markus Meier
2016-09-10 12:48 Agostino Sarubbo
2016-09-02 19:15 Tobias Klausmann
2016-08-25 20:08 Jeroen Roovers
2016-08-25 13:03 Manuel Rüger
2016-07-08 12:02 Agostino Sarubbo
2016-07-08 12:02 Agostino Sarubbo
2016-07-08 10:02 Agostino Sarubbo
2016-07-08 10:02 Agostino Sarubbo
2016-07-08  7:53 Agostino Sarubbo
2016-07-08  7:53 Agostino Sarubbo
2016-05-20 20:09 Tobias Klausmann
2016-05-19 19:14 Markus Meier
2016-05-18  8:56 Jeroen Roovers
2016-05-17  5:17 Jeroen Roovers
2016-05-14 22:23 Agostino Sarubbo
2016-05-14 22:22 Agostino Sarubbo
2016-05-13 21:46 Manuel Rüger
2016-05-13 21:46 Manuel Rüger
2016-05-13 21:46 Manuel Rüger
2016-04-19 15:47 Markus Meier
2016-04-11 10:39 Agostino Sarubbo
2016-04-08 12:21 Agostino Sarubbo
2016-02-17 21:50 Manuel Rüger
2016-02-06 17:08 Manuel Rüger
2016-02-06 17:08 Manuel Rüger
2015-12-26 10:47 Dirkjan Ochtman
2015-12-06 20:07 Dirkjan Ochtman
2015-12-06 20:07 Dirkjan Ochtman
2015-12-06 20:07 Dirkjan Ochtman
2015-11-12 10:37 Agostino Sarubbo
2015-10-10 14:53 Mikle Kolyada
2015-09-29 20:46 Markus Meier
2015-09-27 16:55 Mikle Kolyada
2015-09-26 17:22 Mikle Kolyada
2015-09-15  9:44 Tobias Klausmann
2015-09-08 19:16 Jeroen Roovers
2015-09-05 17:02 Mikle Kolyada
2015-08-26 15:58 Markus Meier
2015-08-24  5:16 Jeroen Roovers
2015-08-22  4:55 Jeroen Roovers
2015-08-09 14:10 Mikle Kolyada
2015-08-09 12:59 Mikle Kolyada

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=1460276858.9873edee95bd77cb6568ce239dcdb3a12b3c341f.jer@gentoo \
    --to=jer@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