public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Mikle Kolyada" <zlogene@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-perl/Mail-DKIM/
Date: Mon, 23 Jul 2018 00:43:34 +0000 (UTC)	[thread overview]
Message-ID: <1532306603.10d8b8064a2bfffc2b18df4c7a8e08125294cd8e.zlogene@gentoo> (raw)

commit:     10d8b8064a2bfffc2b18df4c7a8e08125294cd8e
Author:     Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
AuthorDate: Mon Jul 23 00:39:22 2018 +0000
Commit:     Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
CommitDate: Mon Jul 23 00:43:23 2018 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=10d8b806

dev-perl/Mail-DKIM: arm stable wrt bug #661196

Package-Manager: Portage-2.3.40, Repoman-2.3.9

 dev-perl/Mail-DKIM/Mail-DKIM-0.440.0.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-perl/Mail-DKIM/Mail-DKIM-0.440.0.ebuild b/dev-perl/Mail-DKIM/Mail-DKIM-0.440.0.ebuild
index 440fce058fb..da33b43dbbd 100644
--- a/dev-perl/Mail-DKIM/Mail-DKIM-0.440.0.ebuild
+++ b/dev-perl/Mail-DKIM/Mail-DKIM-0.440.0.ebuild
@@ -11,7 +11,7 @@ inherit perl-module
 DESCRIPTION="Signs/verifies Internet mail using DKIM message signatures"
 
 SLOT="0"
-KEYWORDS="alpha amd64 ~arm ~hppa ia64 ppc ppc64 s390 ~sh sparc x86 ~x86-fbsd"
+KEYWORDS="alpha amd64 arm ~hppa ia64 ppc ppc64 s390 ~sh sparc x86 ~x86-fbsd"
 IUSE="test"
 
 RDEPEND=">=dev-perl/Crypt-OpenSSL-RSA-0.24


             reply	other threads:[~2018-07-23  0:43 UTC|newest]

Thread overview: 67+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-23  0:43 Mikle Kolyada [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-07-07 11:02 [gentoo-commits] repo/gentoo:master commit in: dev-perl/Mail-DKIM/ Sam James
2024-06-14  0:43 Sam James
2024-06-10  2:18 Sam James
2024-06-09 21:18 Sam James
2024-06-09 21:18 Sam James
2024-06-09 21:12 Sam James
2024-05-01  3:59 Sam James
2024-01-24  4:57 Ionen Wolkens
2024-01-18  8:06 Florian Schmaus
2024-01-18  8:06 Florian Schmaus
2023-12-31  3:49 Sam James
2023-12-08  9:54 Sam James
2023-12-08  8:51 Arthur Zamarin
2023-09-12  0:43 Sam James
2023-08-20 18:10 Arthur Zamarin
2023-08-20 17:37 Arthur Zamarin
2023-08-20  6:40 Sam James
2023-08-20  6:20 Sam James
2023-08-20  6:20 Sam James
2023-08-05 12:42 Arthur Zamarin
2023-07-27 10:22 WANG Xuerui
2023-06-30  6:25 Sam James
2023-06-30  4:24 Sam James
2023-06-01  6:22 Sam James
2023-06-01  6:22 Sam James
2023-06-01  5:27 Sam James
2023-06-01  5:22 Sam James
2023-06-01  5:22 Sam James
2023-03-20  8:29 Sam James
2022-12-15  4:57 Sam James
2021-11-12  0:25 Andreas K. Hüttel
2021-10-11 15:25 Sam James
2021-10-11 12:17 Agostino Sarubbo
2021-10-11  8:10 Agostino Sarubbo
2021-10-11  5:12 Sam James
2021-10-11  4:20 Sam James
2021-09-06  0:15 Sam James
2021-07-28  1:08 Sam James
2021-07-24 20:23 Matt Turner
2021-07-08  7:11 Sergei Trofimovich
2021-07-08  7:09 Sergei Trofimovich
2021-07-07  2:16 Sam James
2021-07-06 17:59 Sam James
2021-06-30 23:20 Sergei Trofimovich
2021-06-29 18:59 Sergei Trofimovich
2021-06-28 20:58 Andreas K. Hüttel
2021-06-28 20:29 Andreas K. Hüttel
2020-08-17  8:41 Fabian Groffen
2020-04-15  9:53 Kent Fredric
2019-07-29 18:42 Aaron Bauman
2019-04-01 19:33 Andreas Sturmlechner
2018-07-23 19:00 Sergei Trofimovich
2018-07-22 21:36 Mikle Kolyada
2018-07-21 11:50 Tobias Klausmann
2018-07-20 23:18 Sergei Trofimovich
2018-07-20 22:48 Sergei Trofimovich
2018-07-20  8:08 Sergei Trofimovich
2018-07-16  6:54 Sergei Trofimovich
2017-12-25 11:42 Markus Meier
2017-11-26 12:17 Sergei Trofimovich
2017-11-23 22:31 Matt Turner
2017-11-02  8:44 Sergei Trofimovich
2017-11-01 14:29 Kent Fredric
2017-11-01  4:15 Kent Fredric
2017-04-17  2:34 Kent Fredric
2016-08-16  5:05 Kent Fredric

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=1532306603.10d8b8064a2bfffc2b18df4c7a8e08125294cd8e.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