From: "Richard Freeman" <rich0@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-backup/duplicity/, app-backup/duplicity/files/
Date: Thu, 3 Oct 2024 15:12:34 +0000 (UTC) [thread overview]
Message-ID: <1727968312.100851998b22da78d127696b73fca89a21045ed0.rich0@gentoo> (raw)
commit: 100851998b22da78d127696b73fca89a21045ed0
Author: Richard Freeman <rich0 <AT> gentoo <DOT> org>
AuthorDate: Thu Oct 3 15:09:16 2024 +0000
Commit: Richard Freeman <rich0 <AT> gentoo <DOT> org>
CommitDate: Thu Oct 3 15:11:52 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=10085199
app-backup/duplicity: add 3.0.2
Signed-off-by: Richard Freeman <rich0 <AT> gentoo.org>
app-backup/duplicity/Manifest | 1 +
app-backup/duplicity/duplicity-3.0.2.ebuild | 51 ++++++++++++++++++++++
.../files/duplicity-3.0.2-fix-docs-cmd.patch | 21 +++++++++
3 files changed, 73 insertions(+)
diff --git a/app-backup/duplicity/Manifest b/app-backup/duplicity/Manifest
index a2145990b46a..73b9b4a8e8ac 100644
--- a/app-backup/duplicity/Manifest
+++ b/app-backup/duplicity/Manifest
@@ -1,3 +1,4 @@
DIST duplicity-2.1.4.tar.gz 1556341 BLAKE2B d8302a7097519fd593fc05c8390101e615eaf11333e9d15e1ba7756b8ed9764709db80df41c741ee39eda0fa6de22c910b53db32d558c1ab09867c66724a056c SHA512 91804c6f4dc13d700cbe4747317f9611f530996de8a22a0907d714fb6f8a7fadc3371c270a2257c24324c0233bb4501a4b7d33aea7631862568c8530f7173ef1
DIST duplicity-2.2.3.tar.gz 1978008 BLAKE2B 29a88eb059c3dd6faa7d08d52216cd0f9d96255eae1e613e2c5432bf8f36ad014484953e20b4a0dfaa2704dd6ac426a3285ff40a8cc82f287a8a89199df5a2c5 SHA512 b667092317899674c5e9d4b221815f24a7eae177d3d2b6d298f07d3e2d4a7badd6c976a6317331b7c6cea940a7885a3da397ab7197d5fd671d33278316f86916
DIST duplicity-3.0.0.tar.gz 1943808 BLAKE2B 880f3944de7599c6e730f8b37f40d086d7332e7c8f5885e8477bf46b00832675eb89cbf58944f1134f8ab40ecadc4ae7b159131ebca0a910be4975f0510620da SHA512 59c19ffd46057b519f73f6e3715d6d8790d435966da66c1ea368e35217244fa478f9f1b8be96edbe081f7844d0dd497ec2b55efc1b8b4c6ca5a8d2c5e78a1a44
+DIST duplicity-3.0.2.tar.gz 1933597 BLAKE2B 690d55e7e83d9834d2772be3845b88f9cde0d2190dbd78090661d5aeeaaa7f30a240c59187a74a1feb4f9167936a0fc63c5b13d0b13eecdbcd2d7175b416e5a1 SHA512 b174fdb793b8d6c1ba99a0e77d8c9cb2cbba6000d2a230be9cd894042d62be76ffe1fa5088121932abba394f03681318de6c906baf7383cb1b7e39e321c9f6fc
diff --git a/app-backup/duplicity/duplicity-3.0.2.ebuild b/app-backup/duplicity/duplicity-3.0.2.ebuild
new file mode 100644
index 000000000000..71908351c86d
--- /dev/null
+++ b/app-backup/duplicity/duplicity-3.0.2.ebuild
@@ -0,0 +1,51 @@
+# Copyright 1999-2024 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=8
+PYTHON_COMPAT=( python3_10 python3_11 python3_12 )
+DISTUTILS_USE_PEP517=setuptools
+DISTUTILS_EXT=1
+
+inherit distutils-r1 pypi
+
+DESCRIPTION="Secure backup system using gnupg to encrypt data"
+HOMEPAGE="https://duplicity.gitlab.io/"
+
+LICENSE="GPL-3"
+SLOT="0"
+KEYWORDS="~amd64 ~x86 ~amd64-linux ~x86-linux ~x64-macos"
+IUSE="s3 test"
+
+CDEPEND="
+ net-libs/librsync
+ app-crypt/gnupg
+ dev-python/fasteners[${PYTHON_USEDEP}]
+"
+DEPEND="${CDEPEND}
+ dev-python/setuptools[${PYTHON_USEDEP}]
+ dev-python/setuptools-scm[${PYTHON_USEDEP}]
+ test? (
+ app-arch/par2cmdline
+ dev-python/mock[${PYTHON_USEDEP}]
+ dev-python/pexpect[${PYTHON_USEDEP}]
+ )
+"
+RDEPEND="${CDEPEND}
+ dev-python/paramiko[${PYTHON_USEDEP}]
+ s3? ( dev-python/boto3[${PYTHON_USEDEP}] )
+"
+
+RESTRICT="test"
+
+PATCHES=(
+ "${FILESDIR}/${P}-fix-docs-cmd.patch"
+)
+
+python_test() {
+ esetup.py test
+}
+
+pkg_postinst() {
+ elog "Duplicity has many optional dependencies to support various backends."
+ elog "Currently it's up to you to install them as necessary."
+}
diff --git a/app-backup/duplicity/files/duplicity-3.0.2-fix-docs-cmd.patch b/app-backup/duplicity/files/duplicity-3.0.2-fix-docs-cmd.patch
new file mode 100644
index 000000000000..42003d2f2f1b
--- /dev/null
+++ b/app-backup/duplicity/files/duplicity-3.0.2-fix-docs-cmd.patch
@@ -0,0 +1,21 @@
+--- a/setup.py 2024-10-03 10:39:20.802411576 -0400
++++ b/setup.py 2024-10-03 10:39:52.055847504 -0400
+@@ -113,18 +113,6 @@
+ "man/duplicity.1",
+ ],
+ ),
+- (
+- f"share/doc/duplicity-{Version}",
+- [
+- "CHANGELOG.md",
+- "AUTHORS.md",
+- "COPYING",
+- "README.md",
+- "README-LOG.md",
+- "README-REPO.md",
+- "README-TESTING.md",
+- ],
+- ),
+ ]
+
+ # short circuit fot READTHEDOCS
next reply other threads:[~2024-10-03 15:12 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-03 15:12 Richard Freeman [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-06-24 13:48 [gentoo-commits] repo/gentoo:master commit in: app-backup/duplicity/, app-backup/duplicity/files/ Richard Freeman
2024-06-24 13:48 Richard Freeman
2024-03-29 11:19 Richard Freeman
2023-12-12 14:47 Richard Freeman
2023-12-12 14:47 Richard Freeman
2023-09-14 12:38 Richard Freeman
2023-08-30 18:16 Richard Freeman
2023-05-01 20:38 Richard Freeman
2022-05-19 14:06 Richard Freeman
2022-03-19 19:31 Richard Freeman
2021-12-07 19:32 Richard Freeman
2021-08-05 13:25 Richard Freeman
2021-05-25 14:28 Richard Freeman
2021-02-25 19:54 Richard Freeman
2020-11-25 0:40 Richard Freeman
2020-09-01 20:20 Richard Freeman
2020-05-07 16:53 Richard Freeman
2020-03-29 15:57 Richard Freeman
2020-03-28 16:27 Michał Górny
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=1727968312.100851998b22da78d127696b73fca89a21045ed0.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