public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Thomas Deutschmann" <whissi@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-php/pecl-ssh2/
Date: Mon,  1 Oct 2018 21:47:39 +0000 (UTC)	[thread overview]
Message-ID: <1538430403.0d11999a9a012d09bb2be0b15500f9b8d7f1af11.whissi@gentoo> (raw)

commit:     0d11999a9a012d09bb2be0b15500f9b8d7f1af11
Author:     Thomas Deutschmann <whissi <AT> gentoo <DOT> org>
AuthorDate: Mon Oct  1 21:36:20 2018 +0000
Commit:     Thomas Deutschmann <whissi <AT> gentoo <DOT> org>
CommitDate: Mon Oct  1 21:46:43 2018 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=0d11999a

dev-php/pecl-ssh2: x86 stable (bug #667086)

Signed-off-by: Thomas Deutschmann <whissi <AT> gentoo.org>
Package-Manager: Portage-2.3.50, Repoman-2.3.11

 dev-php/pecl-ssh2/pecl-ssh2-1.1.2.ebuild | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/dev-php/pecl-ssh2/pecl-ssh2-1.1.2.ebuild b/dev-php/pecl-ssh2/pecl-ssh2-1.1.2.ebuild
index 09e08c19122..946604614a2 100644
--- a/dev-php/pecl-ssh2/pecl-ssh2-1.1.2.ebuild
+++ b/dev-php/pecl-ssh2/pecl-ssh2-1.1.2.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2018 Gentoo Foundation
+# Copyright 1999-2018 Gentoo Authors
 # Distributed under the terms of the GNU General Public License v2
 
 EAPI=6
@@ -15,7 +15,7 @@ DESCRIPTION="PHP bindings for the libssh2 library"
 LICENSE="PHP-3.01"
 SLOT="7"
 IUSE=""
-KEYWORDS="~amd64 ~x86"
+KEYWORDS="~amd64 x86"
 # Upstream notes say there are errors with gcrypt backend
 DEPEND=">=net-libs/libssh2-1.2[-gcrypt]"
 RDEPEND="${DEPEND}


             reply	other threads:[~2018-10-01 21:47 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-01 21:47 Thomas Deutschmann [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-03-14  6:35 [gentoo-commits] repo/gentoo:master commit in: dev-php/pecl-ssh2/ Sam James
2025-02-14  5:02 Sam James
2025-01-19  7:04 Arthur Zamarin
2025-01-19  7:04 Arthur Zamarin
2024-11-25  0:02 Sam James
2024-11-25  0:02 Sam James
2023-12-28  2:00 Conrad Kostecki
2023-12-28  2:00 Conrad Kostecki
2023-07-04 10:25 Sam James
2023-07-04 10:15 Sam James
2023-03-08 18:08 Brian Evans
2022-06-30 14:04 Brian Evans
2021-09-23 13:58 Agostino Sarubbo
2021-09-23  6:40 Agostino Sarubbo
2021-04-05 20:32 Thomas Deutschmann
2021-01-11 16:23 Brian Evans
2020-01-23 18:38 Brian Evans
2019-12-06 14:17 Thomas Deutschmann
2019-11-28 22:48 Thomas Deutschmann
2019-09-24 13:47 Thomas Deutschmann
2018-10-04 14:02 Brian Evans
2018-10-02 21:13 Mikle Kolyada
2018-04-10 15:07 Brian Evans
2018-03-22  1:29 Brian Evans
2017-10-19 18:50 Brian Evans
2017-10-19 18:50 Brian Evans
2017-10-09 23:28 Thomas Deutschmann
2017-07-27 13:49 Brian Evans
2017-07-05  2:28 Brian Evans
2017-07-05  2:28 Brian Evans
2017-04-08 19:27 Michael Orlitzky
2017-04-08 19:27 Michael Orlitzky
2016-12-07 15:05 Brian Evans
2016-12-07 15:05 Brian Evans
2016-11-15 14:44 Brian Evans
2016-08-23 20:58 Brian Evans
2016-07-25 14:54 Brian Evans
2016-01-02 16:11 Michael Orlitzky
2015-11-03 16:18 Agostino Sarubbo
2015-11-03 15:19 Agostino Sarubbo
2015-09-27 13:31 Michael Orlitzky

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=1538430403.0d11999a9a012d09bb2be0b15500f9b8d7f1af11.whissi@gentoo \
    --to=whissi@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