From: "Mikle Kolyada" <zlogene@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-perl/LWP-Protocol-https/
Date: Sun, 15 Jul 2018 23:57:46 +0000 (UTC) [thread overview]
Message-ID: <1531699047.d69029fba3f1bdd55fe0a8b3f478d42df93a7f7d.zlogene@gentoo> (raw)
commit: d69029fba3f1bdd55fe0a8b3f478d42df93a7f7d
Author: Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
AuthorDate: Sun Jul 15 23:49:28 2018 +0000
Commit: Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
CommitDate: Sun Jul 15 23:57:27 2018 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=d69029fb
dev-perl/LWP-Protocol-https: amd64 stable wrt bug #661190
Package-Manager: Portage-2.3.40, Repoman-2.3.9
dev-perl/LWP-Protocol-https/LWP-Protocol-https-6.70.0.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-perl/LWP-Protocol-https/LWP-Protocol-https-6.70.0.ebuild b/dev-perl/LWP-Protocol-https/LWP-Protocol-https-6.70.0.ebuild
index bf7a6ad7a93..48bd6dd015a 100644
--- a/dev-perl/LWP-Protocol-https/LWP-Protocol-https-6.70.0.ebuild
+++ b/dev-perl/LWP-Protocol-https/LWP-Protocol-https-6.70.0.ebuild
@@ -11,7 +11,7 @@ DESCRIPTION="Provide https support for LWP::UserAgent"
SLOT="0"
IUSE="test"
-KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~hppa ~ia64 ~m68k ~mips ppc ~ppc64 ~s390 ~sh ~sparc x86 ~ppc-aix ~x64-cygwin ~amd64-fbsd ~amd64-linux ~arm-linux ~x86-linux ~ppc-macos ~x64-macos ~x86-macos ~sparc-solaris ~sparc64-solaris ~x64-solaris ~x86-solaris"
+KEYWORDS="~alpha amd64 ~arm ~arm64 ~hppa ~ia64 ~m68k ~mips ppc ~ppc64 ~s390 ~sh ~sparc x86 ~ppc-aix ~x64-cygwin ~amd64-fbsd ~amd64-linux ~arm-linux ~x86-linux ~ppc-macos ~x64-macos ~x86-macos ~sparc-solaris ~sparc64-solaris ~x64-solaris ~x86-solaris"
RDEPEND="
app-misc/ca-certificates
next reply other threads:[~2018-07-15 23:57 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-15 23:57 Mikle Kolyada [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-06-14 0:43 [gentoo-commits] repo/gentoo:master commit in: dev-perl/LWP-Protocol-https/ Sam James
2024-06-09 21:18 Sam James
2024-06-09 21:18 Sam James
2024-06-09 21:08 Sam James
2024-05-02 1:36 Sam James
2023-08-19 7:23 Sam James
2023-08-19 6:33 Sam James
2023-08-19 6:07 Sam James
2023-08-19 6:03 Sam James
2023-08-19 5:58 Sam James
2023-08-19 5:58 Sam James
2023-07-09 23:02 Sam James
2022-05-14 6:54 WANG Xuerui
2021-12-27 12:57 Fabian Groffen
2021-11-11 18:48 Andreas K. Hüttel
2021-09-28 13:59 James Le Cuirot
2021-08-06 0:30 Sam James
2021-08-03 12:38 Agostino Sarubbo
2021-08-03 10:54 Sam James
2021-08-02 4:56 Sam James
2021-08-02 2:19 Sam James
2021-08-01 7:24 Sam James
2021-06-26 21:47 Andreas K. Hüttel
2021-01-08 16:18 Fabian Groffen
2020-07-23 11:11 Kent Fredric
2020-07-18 7:04 Kent Fredric
2020-07-18 3:42 Kent Fredric
2019-05-04 18:53 Andreas K. Hüttel
2018-10-19 18:15 Fabian Groffen
2018-08-20 3:41 Mikle Kolyada
2018-07-23 0:33 Mikle Kolyada
2018-07-22 9:01 Sergei Trofimovich
2018-07-21 11:50 Tobias Klausmann
2018-07-20 22:48 Sergei Trofimovich
2018-07-20 8:08 Sergei Trofimovich
2018-07-16 6:54 Sergei Trofimovich
2018-07-15 10:25 Sergei Trofimovich
2018-07-09 22:43 Mikle Kolyada
2018-02-24 21:19 Michał Górny
2017-11-09 0:49 Matt Turner
2017-10-16 21:27 Kent Fredric
2016-03-26 20:06 Andreas Hüttel
2016-03-26 15:22 Agostino Sarubbo
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=1531699047.d69029fba3f1bdd55fe0a8b3f478d42df93a7f7d.zlogene@gentoo \
--to=zlogene@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