From: "Marek Szuba" <marecki@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-backup/borgmatic/, app-backup/borgmatic/files/
Date: Wed, 25 Mar 2020 16:57:02 +0000 (UTC) [thread overview]
Message-ID: <1585155280.5c190b0b3b75919c10a38707b7252b42d5b1c323.marecki@gentoo> (raw)
commit: 5c190b0b3b75919c10a38707b7252b42d5b1c323
Author: Marek Szuba <marecki <AT> gentoo <DOT> org>
AuthorDate: Wed Mar 25 16:26:22 2020 +0000
Commit: Marek Szuba <marecki <AT> gentoo <DOT> org>
CommitDate: Wed Mar 25 16:54:40 2020 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=5c190b0b
app-backup/borgmatic: new package
Nominally works with python3_8 to but not all of its dependencies handle
this version in Gentoo yet.
Signed-off-by: Marek Szuba <marecki <AT> gentoo.org>
app-backup/borgmatic/Manifest | 1 +
app-backup/borgmatic/borgmatic-1.5.1.ebuild | 62 ++++++++++++++++++++++
.../files/borgmatic-1.5.1-no_test_coverage.patch | 11 ++++
app-backup/borgmatic/metadata.xml | 12 +++++
4 files changed, 86 insertions(+)
diff --git a/app-backup/borgmatic/Manifest b/app-backup/borgmatic/Manifest
new file mode 100644
index 00000000000..e6ae1752a42
--- /dev/null
+++ b/app-backup/borgmatic/Manifest
@@ -0,0 +1 @@
+DIST borgmatic-1.5.1.tar.gz 67401 BLAKE2B c11f4b9f9acc7d7bf4e482953968dbaabc33f1513ec8f20868518bca22ffcafee90569c06ec603be919d47d724dd4a3a904e44fbb40c2309d8cb78e9277b5cc7 SHA512 9ded9bd5d6db866d196fedee88737f3d3eef6cb0e61c5f55ac543602c4429adcb57608d7f6c798edfd6ac1ecd14aadd9a88fdf94ef1f0eab4c26a9d2a29c5e38
diff --git a/app-backup/borgmatic/borgmatic-1.5.1.ebuild b/app-backup/borgmatic/borgmatic-1.5.1.ebuild
new file mode 100644
index 00000000000..754e0f063c9
--- /dev/null
+++ b/app-backup/borgmatic/borgmatic-1.5.1.ebuild
@@ -0,0 +1,62 @@
+# Copyright 1999-2020 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=7
+
+PYTHON_COMPAT=( python3_{6,7} )
+
+DISTUTILS_USE_SETUPTOOLS="rdepend"
+inherit distutils-r1
+
+DESCRIPTION="Automatically create, prune and verify backups with borgbackup"
+HOMEPAGE="https://torsion.org/borgmatic/"
+SRC_URI="mirror://pypi/${PN:0:1}/${PN}/${P}.tar.gz"
+
+LICENSE="GPL-3"
+SLOT="0"
+KEYWORDS="~amd64"
+
+DEPEND="${PYTHON_DEPS}
+ dev-python/colorama[${PYTHON_USEDEP}]
+ >=dev-python/pykwalify-1.6.0[${PYTHON_USEDEP}]
+ dev-python/requests[${PYTHON_USEDEP}]
+ <dev-python/ruamel-yaml-0.17.0"[${PYTHON_USEDEP}]
+RDEPEND="${DEPEND}
+ app-backup/borgbackup"
+BDEPEND="test? (
+ ${DEPEND}
+ dev-python/flexmock[${PYTHON_USEDEP}]
+ )"
+
+PATCHES=(
+ "${FILESDIR}"/${PN}-1.5.1-no_test_coverage.patch
+)
+
+distutils_enable_tests pytest
+
+src_prepare() {
+ distutils-r1_src_prepare
+
+ # Unlike the other two test files in integration/commands, which use the
+ # relevant modules' respective APIs, test_borgmatic.py tries to call the
+ # 'borgmatic' executable - which has not even been created by now.
+ # Seeing as the only test run from this file as of 2020-03-25 is the
+ # parsing of contents of 'borgmatic --version', just skip it for now.
+ rm -f "${S}"/tests/integration/commands/test_borgmatic.py
+}
+
+src_install() {
+ distutils-r1_src_install
+ keepdir /etc/borgmatic
+ # TODO: install systemd units (and explain them in postinst); need patching
+}
+
+pkg_postinst() {
+ if [[ -z "${REPLACING_VERSIONS}" ]]; then
+ elog "To generate a sample configuration file, run:"
+ elog " generate-borgmatic-config"
+ else
+ elog "To upgrade your configuration file to the current version, run:"
+ elog " upgrade-borgmatic-config"
+ fi
+}
diff --git a/app-backup/borgmatic/files/borgmatic-1.5.1-no_test_coverage.patch b/app-backup/borgmatic/files/borgmatic-1.5.1-no_test_coverage.patch
new file mode 100644
index 00000000000..28562398a40
--- /dev/null
+++ b/app-backup/borgmatic/files/borgmatic-1.5.1-no_test_coverage.patch
@@ -0,0 +1,11 @@
+--- a/setup.cfg
++++ b/setup.cfg
+@@ -3,7 +3,7 @@
+
+ [tool:pytest]
+ testpaths = tests
+-addopts = --cov-report term-missing:skip-covered --cov=borgmatic --ignore=tests/end-to-end
++addopts = --ignore=tests/end-to-end
+ filterwarnings =
+ ignore:Coverage disabled.*:pytest.PytestWarning
+
diff --git a/app-backup/borgmatic/metadata.xml b/app-backup/borgmatic/metadata.xml
new file mode 100644
index 00000000000..e69f4b798a4
--- /dev/null
+++ b/app-backup/borgmatic/metadata.xml
@@ -0,0 +1,12 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
+<pkgmetadata>
+<maintainer type="person">
+ <email>marecki@gentoo.org</email>
+ <name>Marek Szuba</name>
+</maintainer>
+<upstream>
+ <remote-id type="github">witten/borgmatic</remote-id>
+ <remote-id type="pypi">borgmatic</remote-id>
+</upstream>
+</pkgmetadata>
next reply other threads:[~2020-03-25 16:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-25 16:57 Marek Szuba [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-07-27 17:29 [gentoo-commits] repo/gentoo:master commit in: app-backup/borgmatic/, app-backup/borgmatic/files/ Marek Szuba
2021-10-12 23:03 Marek Szuba
2022-10-13 9:31 Marek Szuba
2023-05-11 12:30 Marek Szuba
2023-05-19 8:37 Marek Szuba
2023-06-07 21:59 Marek Szuba
2023-08-22 11:05 Marek Szuba
2024-07-03 14:47 Petr Vaněk
2024-11-05 13:46 Petr Vaněk
2024-11-25 22:07 Petr Vaněk
2024-11-28 11:31 Petr Vaněk
2025-01-13 11:11 Petr Vaněk
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=1585155280.5c190b0b3b75919c10a38707b7252b42d5b1c323.marecki@gentoo \
--to=marecki@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