public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Kent Fredric" <kentnl@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-perl/Crypt-OpenSSL-Guess/
Date: Sat,  5 Dec 2020 04:20:07 +0000 (UTC)	[thread overview]
Message-ID: <1607140771.78eaf8cbf729af5635d38b62ddf463135507827e.kentnl@gentoo> (raw)

commit:     78eaf8cbf729af5635d38b62ddf463135507827e
Author:     Kent Fredric <kentnl <AT> gentoo <DOT> org>
AuthorDate: Sat Dec  5 02:42:10 2020 +0000
Commit:     Kent Fredric <kentnl <AT> gentoo <DOT> org>
CommitDate: Sat Dec  5 03:59:31 2020 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=78eaf8cb

dev-perl/Crypt-OpenSSL-Guess: Keyword ~m68k re bug #737594

- Build/Test OK on m68k-user
- Relevant Revdeps Build/Test OK on m68k-user
- NB: USE="libressl" not tested as globally use.masked for m68k

Required by:
- dev-perl/Crypt-OpenSSL-RSA (older versions keyworded)
- dev-perl/Crypt-OpenSSL-Random (older versions keyworded)
  - via dev-perl/Crypt-OpenSSL-RSA
   - via dev-perl/Net-DNS-SEC (historically keyworded)

Bug: https://bugs.gentoo.org/737594
Package-Manager: Portage-3.0.8, Repoman-3.0.1
Signed-off-by: Kent Fredric <kentnl <AT> gentoo.org>

 dev-perl/Crypt-OpenSSL-Guess/Crypt-OpenSSL-Guess-0.110.0.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-perl/Crypt-OpenSSL-Guess/Crypt-OpenSSL-Guess-0.110.0.ebuild b/dev-perl/Crypt-OpenSSL-Guess/Crypt-OpenSSL-Guess-0.110.0.ebuild
index 4e814106052..c14b0b5bf62 100644
--- a/dev-perl/Crypt-OpenSSL-Guess/Crypt-OpenSSL-Guess-0.110.0.ebuild
+++ b/dev-perl/Crypt-OpenSSL-Guess/Crypt-OpenSSL-Guess-0.110.0.ebuild
@@ -9,7 +9,7 @@ inherit perl-module
 
 DESCRIPTION="Guess OpenSSL include path"
 SLOT="0"
-KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~hppa ~ia64 ~mips ~ppc ~ppc64 ~riscv ~s390 ~sparc ~x86 ~x64-macos"
+KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~hppa ~ia64 ~m68k ~mips ~ppc ~ppc64 ~riscv ~s390 ~sparc ~x86 ~x64-macos"
 IUSE="libressl test"
 RESTRICT="!test? ( test )"
 


             reply	other threads:[~2020-12-05  4:20 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-05  4:20 Kent Fredric [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-12-18 11:41 [gentoo-commits] repo/gentoo:master commit in: dev-perl/Crypt-OpenSSL-Guess/ Sam James
2022-12-18 11:41 Sam James
2022-11-15  8:46 Sam James
2022-11-15  8:46 Sam James
2021-10-16 10:43 Andreas K. Hüttel
2021-08-03 11:03 Sam James
2021-07-31  6:23 Sam James
2021-07-29  6:40 Agostino Sarubbo
2021-07-28  3:12 Sam James
2021-05-13  4:35 Sam James
2021-05-13  4:35 Sam James
2021-05-13  4:35 Sam James
2021-05-13  4:35 Sam James
2021-05-13  4:35 Sam James
2021-05-13  4:32 Sam James
2021-05-13  4:31 Sam James
2021-05-11 19:48 Andreas K. Hüttel
2021-05-03 10:21 Mikle Kolyada
2020-11-28  9:57 Sam James
2020-10-22  5:11 Joshua Kinard
2020-09-26 19:44 Matt Turner
2020-09-03  4:26 Yixun Lan
2020-07-12  0:10 Sam James
2020-07-09 13:23 Sam James
2020-07-07  6:58 Sergei Trofimovich
2020-07-06 16:43 Sergei Trofimovich
2020-07-06 11:57 Michał Górny
2020-07-05 11:37 Sergei Trofimovich
2020-07-05 11:35 Sergei Trofimovich
2020-07-04  8:56 Sergei Trofimovich
2020-07-01 18:02 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=1607140771.78eaf8cbf729af5635d38b62ddf463135507827e.kentnl@gentoo \
    --to=kentnl@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