From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-backup/btrbk/
Date: Sun, 3 Dec 2023 03:37:41 +0000 (UTC) [thread overview]
Message-ID: <1701574645.5bcbe12d0d6500b22e7db14c1119e76990c6095b.sam@gentoo> (raw)
commit: 5bcbe12d0d6500b22e7db14c1119e76990c6095b
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sun Dec 3 03:37:25 2023 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sun Dec 3 03:37:25 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=5bcbe12d
app-backup/btrbk: Keyword 0.32.6-r2 ppc64, #917506
Signed-off-by: Sam James <sam <AT> gentoo.org>
app-backup/btrbk/btrbk-0.32.6-r2.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/app-backup/btrbk/btrbk-0.32.6-r2.ebuild b/app-backup/btrbk/btrbk-0.32.6-r2.ebuild
index 0ea41f1b4d65..66e00dd28638 100644
--- a/app-backup/btrbk/btrbk-0.32.6-r2.ebuild
+++ b/app-backup/btrbk/btrbk-0.32.6-r2.ebuild
@@ -11,7 +11,7 @@ if [[ ${PV} == "9999" ]] ; then
SRC_URI=""
else
SRC_URI="https://digint.ch/download/btrbk/releases/${P}.tar.xz"
- KEYWORDS="~amd64 ~arm ~arm64 ~ppc ~sparc ~x86"
+ KEYWORDS="~amd64 ~arm ~arm64 ~ppc ~ppc64 ~sparc ~x86"
fi
DESCRIPTION="Tool for creating snapshots and remote backups of btrfs subvolumes"
next reply other threads:[~2023-12-03 3:37 UTC|newest]
Thread overview: 78+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-03 3:37 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-12-05 12:29 [gentoo-commits] repo/gentoo:master commit in: app-backup/btrbk/ Sam James
2024-12-01 22:36 Jakov Smolić
2024-12-01 19:02 Arthur Zamarin
2024-12-01 19:02 Arthur Zamarin
2023-12-01 20:36 Arthur Zamarin
2023-11-18 2:29 Sam James
2023-08-21 6:29 Sam James
2023-07-10 3:55 Sam James
2023-07-10 3:55 Sam James
2023-05-29 20:35 Sam James
2023-05-26 20:06 Arthur Zamarin
2023-05-26 14:38 Sam James
2023-05-26 14:38 Sam James
2023-03-27 13:38 Craig Andrews
2023-03-27 13:38 Craig Andrews
2022-12-27 10:19 Sam James
2022-12-27 10:12 Sam James
2022-12-27 1:30 Craig Andrews
2022-10-24 14:47 Craig Andrews
2022-10-24 14:47 Craig Andrews
2022-08-23 0:21 Craig Andrews
2022-08-09 13:12 Craig Andrews
2022-06-27 13:51 Craig Andrews
2022-02-27 2:36 Craig Andrews
2022-02-06 15:22 Craig Andrews
2021-10-17 20:39 John Helmert III
2021-08-11 6:43 Agostino Sarubbo
2021-08-09 0:38 Sam James
2021-08-09 0:35 Sam James
2021-08-08 7:45 Agostino Sarubbo
2021-08-07 0:48 Craig Andrews
2021-03-22 14:35 Craig Andrews
2021-03-22 14:35 Craig Andrews
2021-03-08 13:56 Craig Andrews
2021-01-11 15:08 Craig Andrews
2020-09-30 15:25 Craig Andrews
2020-09-30 15:25 Craig Andrews
2020-09-23 15:38 Craig Andrews
2020-07-03 7:45 Lars Wendler
2020-06-30 6:34 Agostino Sarubbo
2020-06-29 6:22 Agostino Sarubbo
2020-06-26 17:43 Agostino Sarubbo
2020-05-09 8:47 Mart Raudsepp
2020-05-08 20:58 Mart Raudsepp
2020-02-10 15:46 Craig Andrews
2019-10-29 0:05 Craig Andrews
2019-10-27 19:05 Craig Andrews
2019-07-29 15:00 Craig Andrews
2019-05-23 13:21 Craig Andrews
2019-05-16 17:35 Craig Andrews
2019-04-26 20:26 Craig Andrews
2019-03-26 20:08 Craig Andrews
2019-03-25 15:26 Craig Andrews
2019-01-23 13:41 Mikle Kolyada
2018-12-13 20:55 Mikle Kolyada
2018-12-13 12:48 Thomas Deutschmann
2018-12-06 15:32 Craig Andrews
2018-10-16 19:20 Craig Andrews
2018-10-16 14:04 Craig Andrews
2018-10-16 14:04 Craig Andrews
2018-03-15 15:28 Mikle Kolyada
2018-03-05 14:44 Craig Andrews
2017-10-29 21:08 Thomas Deutschmann
2017-10-12 18:22 Craig Andrews
2017-10-12 18:22 Craig Andrews
2017-10-12 18:22 Craig Andrews
2017-07-31 18:45 David Seifert
2017-07-31 18:45 David Seifert
2017-07-31 18:45 David Seifert
2017-03-20 20:49 Göktürk Yüksek
2017-02-10 1:56 Michael Weber
2016-12-29 10:05 Agostino Sarubbo
2016-11-17 14:30 Göktürk Yüksek
2016-11-17 7:35 David Seifert
2016-07-22 17:38 Patrice Clement
2016-07-21 4:00 Göktürk Yüksek
2016-07-14 1:35 Göktürk Yüksek
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=1701574645.5bcbe12d0d6500b22e7db14c1119e76990c6095b.sam@gentoo \
--to=sam@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