From: "Richard Freeman" <rich0@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-backup/duplicity/
Date: Sat, 9 May 2020 14:55:03 +0000 (UTC) [thread overview]
Message-ID: <1589036092.b036cdec177c998c5e2b6df2cacff8363b467df7.rich0@gentoo> (raw)
commit: b036cdec177c998c5e2b6df2cacff8363b467df7
Author: Richard Freeman <rich0 <AT> gentoo <DOT> org>
AuthorDate: Sat May 9 14:54:52 2020 +0000
Commit: Richard Freeman <rich0 <AT> gentoo <DOT> org>
CommitDate: Sat May 9 14:54:52 2020 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b036cdec
app-backup/duplicity: amd64 stable
Stabilizing revbump <30d due to python USE default changes, and
last-minute fix for python3 issues in previous revision.
Bug: https://bugs.gentoo.org/721432
Package-Manager: Portage-2.3.99, Repoman-2.3.22
Signed-off-by: Richard Freeman <rich0 <AT> gentoo.org>
app-backup/duplicity/duplicity-0.8.12.1612-r1.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/app-backup/duplicity/duplicity-0.8.12.1612-r1.ebuild b/app-backup/duplicity/duplicity-0.8.12.1612-r1.ebuild
index 7c75e96f148..223928555b8 100644
--- a/app-backup/duplicity/duplicity-0.8.12.1612-r1.ebuild
+++ b/app-backup/duplicity/duplicity-0.8.12.1612-r1.ebuild
@@ -12,7 +12,7 @@ SRC_URI="https://code.launchpad.net/${PN}/$(ver_cut 1-2)-series/$(ver_cut 1-3)/+
LICENSE="GPL-3"
SLOT="0"
-KEYWORDS="~amd64 ~x86 ~amd64-linux ~x86-linux ~x64-macos ~x86-macos"
+KEYWORDS="amd64 ~x86 ~amd64-linux ~x86-linux ~x64-macos ~x86-macos"
IUSE="s3 test"
CDEPEND="
next reply other threads:[~2020-05-09 14:55 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-09 14:55 Richard Freeman [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-04-29 20:22 [gentoo-commits] repo/gentoo:master commit in: app-backup/duplicity/ Sam James
2024-04-29 19:18 Richard Freeman
2023-12-25 19:17 Arthur Zamarin
2023-12-24 22:08 Richard Freeman
2023-12-24 22:06 Richard Freeman
2023-06-14 2:51 Sam James
2023-06-14 2:48 Sam James
2023-06-13 20:01 Richard Freeman
2023-01-10 14:37 Michał Górny
2022-12-27 12:41 Richard Freeman
2022-12-27 7:29 Sam James
2022-12-26 13:49 Richard Freeman
2022-10-14 1:26 Sam James
2022-10-14 1:21 Matt Turner
2022-09-30 12:05 Richard Freeman
2022-05-20 1:17 Sam James
2022-05-19 15:54 Richard Freeman
2022-05-19 14:09 Richard Freeman
2022-03-19 19:31 Richard Freeman
2022-01-07 15:29 Sam James
2022-01-07 14:03 Richard Freeman
2021-08-05 15:26 Richard Freeman
2021-08-05 13:25 Richard Freeman
2021-05-26 6:51 Agostino Sarubbo
2021-05-25 13:58 Richard Freeman
2021-02-26 15:18 Sam James
2021-02-25 19:46 Richard Freeman
2021-01-06 12:52 Fabian Groffen
2020-10-22 15:08 Richard Freeman
2020-10-01 19:06 Richard Freeman
2020-06-07 11:51 Richard Freeman
2020-06-02 20:34 Richard Freeman
2020-05-12 6:39 Agostino Sarubbo
2020-03-28 16:27 Michał Górny
2020-03-28 16:27 Michał Górny
2020-03-26 10:24 Agostino Sarubbo
2020-03-09 13:27 Richard Freeman
2020-02-22 21:12 David Seifert
2020-02-22 18:59 Richard Freeman
2020-01-20 2:26 Richard Freeman
2020-01-13 19:34 Richard Freeman
2019-11-19 15:55 Richard Freeman
2019-11-17 22:40 Tim Harder
2019-11-11 4:55 Tim Harder
2019-11-11 4:55 Tim Harder
2019-09-30 17:21 Richard Freeman
2018-08-20 15:01 Patrice Clement
2018-03-19 6:27 Tim Harder
2018-02-05 6:02 Tim Harder
2017-11-17 19:26 Tim Harder
2017-09-01 10:28 Tim Harder
2017-07-29 4:05 Tim Harder
2017-04-03 8:34 Tim Harder
2017-01-17 5:42 Tim Harder
2017-01-17 5:42 Tim Harder
2016-12-12 4:37 Tim Harder
2016-12-09 13:40 Richard Freeman
2016-08-22 2:46 Tim Harder
2016-05-12 4:38 Tim Harder
2016-05-12 4:38 Tim Harder
2016-01-05 8:41 Agostino Sarubbo
2016-01-05 8:40 Agostino Sarubbo
2015-12-31 14:55 Richard Freeman
2015-09-13 17:14 Robin H. Johnson
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=1589036092.b036cdec177c998c5e2b6df2cacff8363b467df7.rich0@gentoo \
--to=rich0@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