From: "Agostino Sarubbo" <ago@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: mail-filter/opendmarc/
Date: Tue, 10 Aug 2021 06:43:27 +0000 (UTC) [thread overview]
Message-ID: <1628577797.21c88d2f351259284e06f48e8c4517a45bda11be.ago@gentoo> (raw)
commit: 21c88d2f351259284e06f48e8c4517a45bda11be
Author: Agostino Sarubbo <ago <AT> gentoo <DOT> org>
AuthorDate: Tue Aug 10 06:43:17 2021 +0000
Commit: Agostino Sarubbo <ago <AT> gentoo <DOT> org>
CommitDate: Tue Aug 10 06:43:17 2021 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=21c88d2f
mail-filter/opendmarc: ppc64 stable wrt bug #797214
Package-Manager: Portage-3.0.20, Repoman-3.0.2
RepoMan-Options: --include-arches="ppc64"
Signed-off-by: Agostino Sarubbo <ago <AT> gentoo.org>
mail-filter/opendmarc/opendmarc-1.4.1.1-r2.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/mail-filter/opendmarc/opendmarc-1.4.1.1-r2.ebuild b/mail-filter/opendmarc/opendmarc-1.4.1.1-r2.ebuild
index c6e98a8f17a..3777c1d40d4 100644
--- a/mail-filter/opendmarc/opendmarc-1.4.1.1-r2.ebuild
+++ b/mail-filter/opendmarc/opendmarc-1.4.1.1-r2.ebuild
@@ -11,7 +11,7 @@ SRC_URI="https://github.com/trusteddomainproject/OpenDMARC/archive/rel-${PN}-${P
LICENSE="BSD"
SLOT="0/3" # 1.4 has API breakage with 1.3, yet uses same soname
-KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~hppa ~ia64 ppc ~ppc64 ~sparc ~x86"
+KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~hppa ~ia64 ppc ppc64 ~sparc ~x86"
IUSE="spf +reports static-libs"
DEPEND="reports? ( dev-perl/DBI )
next reply other threads:[~2021-08-10 6:43 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-10 6:43 Agostino Sarubbo [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-08 2:49 [gentoo-commits] repo/gentoo:master commit in: mail-filter/opendmarc/ Sam James
2024-11-03 18:02 Sam James
2024-11-03 18:02 Sam James
2024-11-03 17:47 Arthur Zamarin
2024-11-03 17:47 Arthur Zamarin
2024-11-03 8:45 Fabian Groffen
2024-01-26 20:25 Fabian Groffen
2022-08-04 1:45 Sam James
2022-04-22 6:34 Fabian Groffen
2022-03-10 21:12 Sam James
2021-08-20 7:31 Fabian Groffen
2021-08-20 6:26 Fabian Groffen
2021-08-19 1:08 Sam James
2021-08-11 6:39 Agostino Sarubbo
2021-08-11 0:04 Sam James
2021-08-10 6:43 Agostino Sarubbo
2021-08-10 6:42 Agostino Sarubbo
2021-05-08 8:23 Fabian Groffen
2021-03-05 20:27 Sam James
2020-10-16 6:29 Fabian Groffen
2020-10-15 18:40 Sergei Trofimovich
2020-10-03 15:13 Sam James
2020-10-02 22:31 Sam James
2020-10-02 21:36 Sam James
2020-10-01 22:55 Sergei Trofimovich
2020-09-29 11:42 Sam James
2020-09-28 17:41 Sergei Trofimovich
2020-05-12 17:50 Mart Raudsepp
2020-04-28 5:57 Fabian Groffen
2019-11-13 16:09 Agostino Sarubbo
2019-11-01 10:48 Mikle Kolyada
2019-10-17 11:23 Agostino Sarubbo
2019-10-17 10:32 Agostino Sarubbo
2019-10-17 10:29 Agostino Sarubbo
2019-10-17 10:25 Agostino Sarubbo
2019-10-17 9:53 Agostino Sarubbo
2019-05-11 12:16 Mikle Kolyada
2019-05-06 15:25 Tobias Klausmann
2019-05-03 7:11 Sergei Trofimovich
2019-04-14 11:12 Agostino Sarubbo
2019-04-11 19:15 Sergei Trofimovich
2019-04-10 17:04 Thomas Deutschmann
2019-03-16 15:15 Fabian Groffen
2018-12-10 10:56 Fabian Groffen
2018-03-08 20:01 Markus Meier
2017-12-22 11:04 Fabian Groffen
2017-06-27 13:30 Fabian Groffen
2017-05-16 6:35 Fabian Groffen
2017-03-29 7:24 Fabian Groffen
2016-02-22 10:25 Patrice Clement
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=1628577797.21c88d2f351259284e06f48e8c4517a45bda11be.ago@gentoo \
--to=ago@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