public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sergei Trofimovich" <slyfox@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-perl/Config-AutoConf/
Date: Wed,  2 Sep 2020 06:33:36 +0000 (UTC)	[thread overview]
Message-ID: <1599028397.17d9b8a7cf0232db50f28f9e728fe9da5dad045b.slyfox@gentoo> (raw)

commit:     17d9b8a7cf0232db50f28f9e728fe9da5dad045b
Author:     Rolf Eike Beer <eike <AT> sf-mail <DOT> de>
AuthorDate: Wed Sep  2 04:22:01 2020 +0000
Commit:     Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
CommitDate: Wed Sep  2 06:33:17 2020 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=17d9b8a7

dev-perl/Config-AutoConf: keyworded 0.318.0 for hppa, bug #738394

Package-Manager: Portage-3.0.4, Repoman-2.3.23
RepoMan-Options: --include-arches="hppa"
Signed-off-by: Rolf Eike Beer <eike <AT> sf-mail.de>
Signed-off-by: Sergei Trofimovich <slyfox <AT> gentoo.org>

 dev-perl/Config-AutoConf/Config-AutoConf-0.318.0.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-perl/Config-AutoConf/Config-AutoConf-0.318.0.ebuild b/dev-perl/Config-AutoConf/Config-AutoConf-0.318.0.ebuild
index c331a139651..4d03de99a0c 100644
--- a/dev-perl/Config-AutoConf/Config-AutoConf-0.318.0.ebuild
+++ b/dev-perl/Config-AutoConf/Config-AutoConf-0.318.0.ebuild
@@ -11,7 +11,7 @@ inherit perl-module
 DESCRIPTION="A module to implement some of AutoConf macros in pure perl"
 
 SLOT="0"
-KEYWORDS="~amd64 ~arm ~arm64 ~ppc64 ~sparc ~x86"
+KEYWORDS="~amd64 ~arm ~arm64 ~hppa ~ppc64 ~sparc ~x86"
 IUSE="test"
 RESTRICT="!test? ( test )"
 


             reply	other threads:[~2020-09-02  6:33 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-02  6:33 Sergei Trofimovich [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-07-18 19:26 [gentoo-commits] repo/gentoo:master commit in: dev-perl/Config-AutoConf/ Fabian Groffen
2023-06-22  2:49 Sam James
2022-02-22  9:30 Arthur Zamarin
2022-02-19 12:02 Arthur Zamarin
2022-02-19 12:02 Arthur Zamarin
2022-02-19  8:52 Arthur Zamarin
2022-02-19  8:00 Arthur Zamarin
2022-02-19  5:20 Sam James
2022-02-19  3:41 Sam James
2022-02-19  3:02 Sam James
2021-12-27 12:57 Fabian Groffen
2021-11-19 11:56 Sam James
2021-10-12 20:18 Andreas K. Hüttel
2021-10-12 20:18 Andreas K. Hüttel
2021-10-07  6:37 Sam James
2021-09-01 18:32 Sam James
2021-08-04 15:34 Joshua Kinard
2021-07-24 20:23 Matt Turner
2021-07-23 22:40 Sergei Trofimovich
2021-07-23 14:56 Marek Szuba
2021-06-07  6:28 Sergei Trofimovich
2021-06-07  6:25 Sergei Trofimovich
2021-06-02 14:33 Sergei Trofimovich
2021-05-04 22:25 Sam James
2021-05-04  7:01 Agostino Sarubbo
2020-12-12  6:46 Kent Fredric
2020-10-01  8:04 Kent Fredric
2020-09-07  7:31 Sergei Trofimovich
2020-09-01  3:02 Sam James
2020-08-31  4:32 Sam James
2020-06-27  7:01 Kent Fredric
2018-04-05 18:29 Thomas Deutschmann
2018-04-05 14:11 Aaron Bauman
2017-10-05  5:08 Kent Fredric
2017-06-15 16:27 Markus Meier
2017-04-28 21:16 Manuel Rüger
2017-04-23 10:27 Agostino Sarubbo
2017-04-02 18:32 Kent Fredric
2017-03-11 21:46 Andreas Hüttel
2016-08-06 15:53 Kent Fredric
2016-04-19 22:25 Manuel Rüger
2015-12-30 12:29 Andreas Hüttel

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=1599028397.17d9b8a7cf0232db50f28f9e728fe9da5dad045b.slyfox@gentoo \
    --to=slyfox@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