public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Aaron Bauman" <bman@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-apps/etckeeper/
Date: Mon, 23 Apr 2018 14:50:44 +0000 (UTC)	[thread overview]
Message-ID: <1524495031.d11e8e20cb5b0ced09310c50958b4f019a0ac1cb.bman@gentoo> (raw)

commit:     d11e8e20cb5b0ced09310c50958b4f019a0ac1cb
Author:     Luke Dashjr <luke-jr+git <AT> utopios <DOT> org>
AuthorDate: Wed Apr 18 03:21:30 2018 +0000
Commit:     Aaron Bauman <bman <AT> gentoo <DOT> org>
CommitDate: Mon Apr 23 14:50:31 2018 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=d11e8e20

sys-apps/etckeeper: Keyword 1.18.6 ~ppc64

 sys-apps/etckeeper/etckeeper-1.18.6.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/sys-apps/etckeeper/etckeeper-1.18.6.ebuild b/sys-apps/etckeeper/etckeeper-1.18.6.ebuild
index 036e3fa29f9..59f27252629 100644
--- a/sys-apps/etckeeper/etckeeper-1.18.6.ebuild
+++ b/sys-apps/etckeeper/etckeeper-1.18.6.ebuild
@@ -12,7 +12,7 @@ HOMEPAGE="https://etckeeper.branchable.com/"
 SRC_URI="https://github.com/joeyh/etckeeper/archive/${PV}.tar.gz -> ${P}.tar.gz"
 
 LICENSE="GPL-2"
-KEYWORDS="amd64 ~arm x86"
+KEYWORDS="amd64 ~arm ~ppc64 x86"
 SLOT="0"
 IUSE="bazaar cron"
 REQUIRED_USE="bazaar? ( ${PYTHON_REQUIRED_USE} )"


             reply	other threads:[~2018-04-23 14:50 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-23 14:50 Aaron Bauman [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-06-04 17:49 [gentoo-commits] repo/gentoo:master commit in: sys-apps/etckeeper/ Viorel Munteanu
2024-05-19 17:49 Arthur Zamarin
2024-05-19 17:09 Sam James
2024-05-19 17:09 Sam James
2024-05-19 17:06 Arthur Zamarin
2024-05-19 17:02 Arthur Zamarin
2023-11-30  3:07 Sam James
2023-07-08  3:39 Sam James
2023-07-07 10:14 Sam James
2023-07-07  4:40 Sam James
2023-07-07  4:40 Sam James
2023-07-07  4:40 Sam James
2023-07-07  3:36 Sam James
2022-11-01 15:47 Arthur Zamarin
2022-11-01  8:44 Agostino Sarubbo
2022-11-01  8:29 Agostino Sarubbo
2022-11-01  8:28 Agostino Sarubbo
2022-11-01  8:26 Agostino Sarubbo
2022-11-01  6:51 Georgy Yakovlev
2022-10-01  5:36 Sam James
2022-06-05 23:03 Conrad Kostecki
2022-05-20  4:01 Georgy Yakovlev
2022-05-05 12:01 Jakov Smolić
2022-03-27  2:33 Sam James
2022-03-18 12:26 Arthur Zamarin
2022-03-15 16:27 Sam James
2021-11-20  7:32 Georgy Yakovlev
2021-11-20  7:28 Agostino Sarubbo
2021-11-19  8:10 Agostino Sarubbo
2021-11-19  6:18 Arthur Zamarin
2021-11-19  2:43 Sam James
2021-07-22 22:25 Marek Szuba
2021-07-10  2:12 Georgy Yakovlev
2020-11-24  6:06 Georgy Yakovlev
2020-03-31 10:01 Agostino Sarubbo
2020-03-31  7:23 Georgy Yakovlev
2020-03-31  7:18 Agostino Sarubbo
2020-01-08 11:27 Georgy Yakovlev
2018-10-13 22:02 Patrice Clement
2018-10-03  5:15 Georgy Yakovlev
2018-10-01  3:54 Benda XU
2018-09-24 18:48 Mikle Kolyada
2018-04-05 21:33 Michał Górny
2018-04-05 21:33 Michał Górny
2018-04-05 21:33 Michał Górny
2017-11-21 18:00 Manuel Rüger
2017-05-28 21:18 Manuel Rüger
2016-08-06 13:34 Manuel Rüger
2016-08-06 13:27 Manuel Rüger
2016-07-16 22:31 Manuel Rüger
2016-03-15 15:27 Agostino Sarubbo
2016-03-06 12:58 Agostino Sarubbo
2016-02-15 23:22 Manuel Rüger

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=1524495031.d11e8e20cb5b0ced09310c50958b4f019a0ac1cb.bman@gentoo \
    --to=bman@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