From: "Richard Freeman" <rich0@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-backup/duplicity/files/, app-backup/duplicity/
Date: Tue, 18 Mar 2025 16:49:40 +0000 (UTC) [thread overview]
Message-ID: <1742316545.0cd257f099f772e5b13f2994adb739342e23f9b8.rich0@gentoo> (raw)
commit: 0cd257f099f772e5b13f2994adb739342e23f9b8
Author: Richard Freeman <rich0 <AT> gentoo <DOT> org>
AuthorDate: Tue Mar 18 16:48:23 2025 +0000
Commit: Richard Freeman <rich0 <AT> gentoo <DOT> org>
CommitDate: Tue Mar 18 16:49:05 2025 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=0cd257f0
app-backup/duplicity: add 3.0.4.0
Signed-off-by: Richard Freeman <rich0 <AT> gentoo.org>
app-backup/duplicity/Manifest | 1 +
app-backup/duplicity/duplicity-3.0.4.0.ebuild | 51 ++++++++++++++++++++++
.../files/duplicity-3.0.4.0-fix-docs-cmd.patch | 21 +++++++++
3 files changed, 73 insertions(+)
diff --git a/app-backup/duplicity/Manifest b/app-backup/duplicity/Manifest
index f3c47640d441..ced147807e37 100644
--- a/app-backup/duplicity/Manifest
+++ b/app-backup/duplicity/Manifest
@@ -2,3 +2,4 @@ DIST duplicity-2.2.3.tar.gz 1978008 BLAKE2B 29a88eb059c3dd6faa7d08d52216cd0f9d96
DIST duplicity-3.0.0.tar.gz 1943808 BLAKE2B 880f3944de7599c6e730f8b37f40d086d7332e7c8f5885e8477bf46b00832675eb89cbf58944f1134f8ab40ecadc4ae7b159131ebca0a910be4975f0510620da SHA512 59c19ffd46057b519f73f6e3715d6d8790d435966da66c1ea368e35217244fa478f9f1b8be96edbe081f7844d0dd497ec2b55efc1b8b4c6ca5a8d2c5e78a1a44
DIST duplicity-3.0.2.tar.gz 1933597 BLAKE2B 690d55e7e83d9834d2772be3845b88f9cde0d2190dbd78090661d5aeeaaa7f30a240c59187a74a1feb4f9167936a0fc63c5b13d0b13eecdbcd2d7175b416e5a1 SHA512 b174fdb793b8d6c1ba99a0e77d8c9cb2cbba6000d2a230be9cd894042d62be76ffe1fa5088121932abba394f03681318de6c906baf7383cb1b7e39e321c9f6fc
DIST duplicity-3.0.3.2.tar.gz 1929330 BLAKE2B 00c33519edca5eb4f4468cf510381b8177a042d86eb1256105c61b42a7e712bad7b57f4a23997d1c85d0ccddb758f53e88fa0d1725fc8fe054a1a54f82cb64c8 SHA512 6c7917fede2b049ef1c6c49778a38dd8bb100cece2f66e49b311057400bca6dc3396ae0598176ec478ad9f0fbc6c896f06fe46b90e3ac0469fb6d5d2ad8bcaab
+DIST duplicity-3.0.4.0.tar.gz 1925286 BLAKE2B 99c8b6e9d2d5f6f14254cbbf7f4cbeee097ab258915af1847ab1d6ad18b6a6a66f0db1dc3fc4a1ac6829f3a4019666208f3211bcdf60323370f52cc1ba46236b SHA512 c40f29a38863903f0e0f1930bf44ffcbc0333a94016c5345f28dec146a6a4b9cfa31662cd6cc66690afef0ce611d7cfaaaf245be47cc9f719d8dca7dc7f3f2c5
diff --git a/app-backup/duplicity/duplicity-3.0.4.0.ebuild b/app-backup/duplicity/duplicity-3.0.4.0.ebuild
new file mode 100644
index 000000000000..5ff648d48381
--- /dev/null
+++ b/app-backup/duplicity/duplicity-3.0.4.0.ebuild
@@ -0,0 +1,51 @@
+# Copyright 1999-2025 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=8
+PYTHON_COMPAT=( python3_10 python3_11 python3_12 python3_13 )
+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.4.0-fix-docs-cmd.patch b/app-backup/duplicity/files/duplicity-3.0.4.0-fix-docs-cmd.patch
new file mode 100644
index 000000000000..11ef262ccfd4
--- /dev/null
+++ b/app-backup/duplicity/files/duplicity-3.0.4.0-fix-docs-cmd.patch
@@ -0,0 +1,21 @@
+--- a/setup.py 2025-03-18 12:35:14.931331106 -0400
++++ b/setup.py 2025-03-18 12:35:48.122815701 -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:[~2025-03-18 16:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-18 16:49 Richard Freeman [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-12-22 13:23 [gentoo-commits] repo/gentoo:master commit in: app-backup/duplicity/files/, app-backup/duplicity/ Richard Freeman
2024-10-03 15:12 Richard Freeman
2023-12-25 19:49 Richard Freeman
2023-05-20 6:22 Michał Górny
2023-05-11 16:51 Richard Freeman
2022-10-05 14:34 Richard Freeman
2022-09-30 12:05 Richard Freeman
2022-05-22 0:51 Richard Freeman
2022-03-19 19:34 Richard Freeman
2021-08-05 13:25 Richard Freeman
2021-05-10 17:43 Richard Freeman
2021-02-25 19:56 Richard Freeman
2020-10-12 17:53 Richard Freeman
2020-06-02 20:34 Richard Freeman
2020-03-05 14:29 Richard Freeman
2020-01-20 2:25 Richard Freeman
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=1742316545.0cd257f099f772e5b13f2994adb739342e23f9b8.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