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: app-backup/rdiff-backup/
Date: Wed, 27 Jun 2018 22:15:03 +0000 (UTC)	[thread overview]
Message-ID: <1530137632.f4f19b3288191d3459b3b5625baa1b279f0d5311.slyfox@gentoo> (raw)

commit:     f4f19b3288191d3459b3b5625baa1b279f0d5311
Author:     Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
AuthorDate: Wed Jun 27 21:59:50 2018 +0000
Commit:     Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
CommitDate: Wed Jun 27 22:13:52 2018 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f4f19b32

app-backup/rdiff-backup: stable 1.3.3-r3 for ppc64, bug #658242

Bug: https://bugs.gentoo.org/658242
Package-Manager: Portage-2.3.40, Repoman-2.3.9
RepoMan-Options: --include-arches="ppc64"

 app-backup/rdiff-backup/rdiff-backup-1.3.3-r3.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/app-backup/rdiff-backup/rdiff-backup-1.3.3-r3.ebuild b/app-backup/rdiff-backup/rdiff-backup-1.3.3-r3.ebuild
index b7547764252..3a6f9bf04f5 100644
--- a/app-backup/rdiff-backup/rdiff-backup-1.3.3-r3.ebuild
+++ b/app-backup/rdiff-backup/rdiff-backup-1.3.3-r3.ebuild
@@ -14,7 +14,7 @@ SRC_URI="https://github.com/sol1/${PN}/archive/r${UPSTREAM_PV}.tar.gz -> ${P}.ta
 
 LICENSE="GPL-2"
 SLOT="0"
-KEYWORDS="alpha amd64 ~arm ~mips ppc ~ppc64 ~sh sparc x86 ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos"
+KEYWORDS="alpha amd64 ~arm ~mips ppc ppc64 ~sh sparc x86 ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos"
 IUSE="examples"
 
 DEPEND="


             reply	other threads:[~2018-06-27 22:15 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-27 22:15 Sergei Trofimovich [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-06-20 20:32 [gentoo-commits] repo/gentoo:master commit in: app-backup/rdiff-backup/ Arthur Zamarin
2024-06-20 20:32 Arthur Zamarin
2024-06-20 18:04 Arthur Zamarin
2024-06-20 10:16 Arthur Zamarin
2024-06-20  8:02 Sam James
2024-06-20  7:27 Sam James
2024-04-14 21:09 Bernard Cafarelli
2024-04-14 21:09 Bernard Cafarelli
2023-12-29 22:43 Sam James
2023-09-20 21:56 Bernard Cafarelli
2023-09-20 21:56 Bernard Cafarelli
2023-05-14 10:00 Bernard Cafarelli
2023-04-02 21:39 Sam James
2023-04-02 20:48 Bernard Cafarelli
2023-04-02 20:48 Bernard Cafarelli
2023-03-04 20:38 Bernard Cafarelli
2023-03-04 20:38 Bernard Cafarelli
2023-02-25 16:12 Bernard Cafarelli
2023-02-25 10:10 Bernard Cafarelli
2022-12-29 15:29 Bernard Cafarelli
2022-12-19 16:27 Bernard Cafarelli
2022-07-10 14:53 Bernard Cafarelli
2021-12-29 11:16 Bernard Cafarelli
2021-06-07 13:16 Agostino Sarubbo
2021-06-03  8:23 Sam James
2021-06-01 11:58 Sam James
2021-06-01  6:36 Agostino Sarubbo
2021-05-31 22:38 Sam James
2021-03-05  9:01 Bernard Cafarelli
2021-03-05  9:01 Bernard Cafarelli
2020-10-07 20:56 Bernard Cafarelli
2020-10-07 20:56 Bernard Cafarelli
2020-07-27 16:35 Bernard Cafarelli
2020-04-17 16:24 Sergei Trofimovich
2020-04-14 12:32 Agostino Sarubbo
2020-04-11 16:10 Agostino Sarubbo
2020-04-11 16:00 Agostino Sarubbo
2020-04-11 15:58 Agostino Sarubbo
2020-04-11 15:57 Agostino Sarubbo
2020-02-29 21:05 Bernard Cafarelli
2020-02-29 15:38 Bernard Cafarelli
2019-08-22 21:02 Bernard Cafarelli
2018-07-22 11:21 Andreas Sturmlechner
2018-07-22  0:39 Mikle Kolyada
2018-06-27 21:54 Sergei Trofimovich
2018-06-27  7:25 Tobias Klausmann
2018-06-26 18:08 Bernard Cafarelli
2018-06-23 17:48 Mikle Kolyada
2018-06-19 19:13 Sergei Trofimovich
2018-06-18 19:06 Andreas Sturmlechner
2018-06-18 18:48 Jonas Stein
2018-06-17 23:29 Thomas Deutschmann
2018-06-16 16:42 Andreas Sturmlechner
2018-06-16 16:42 Andreas Sturmlechner
2016-03-22  9:36 Sergei Trofimovich
2016-02-06 15:45 Alex Brandt
2016-01-02 21:15 Manuel Rüger
2015-12-22 15:32 Alex Brandt

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=1530137632.f4f19b3288191d3459b3b5625baa1b279f0d5311.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