commit:     753f5081372d7d31b23a58a56ce5f36b311cb255
Author:     Marek Szuba <marecki <AT> gentoo <DOT> org>
AuthorDate: Sat Nov 21 21:53:06 2020 +0000
Commit:     Marek Szuba <marecki <AT> gentoo <DOT> org>
CommitDate: Sat Nov 21 22:05:22 2020 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=753f5081

app-backup/borgmatic: bump to 1.5.11

Signed-off-by: Marek Szuba <marecki <AT> gentoo.org>

 app-backup/borgmatic/Manifest                |  1 +
 app-backup/borgmatic/borgmatic-1.5.11.ebuild | 71 ++++++++++++++++++++++++++++
 2 files changed, 72 insertions(+)

diff --git a/app-backup/borgmatic/Manifest b/app-backup/borgmatic/Manifest
index e4c21c5e949..1760b0e2d71 100644
--- a/app-backup/borgmatic/Manifest
+++ b/app-backup/borgmatic/Manifest
@@ -1 +1,2 @@
 DIST borgmatic-1.5.10.tar.gz 71743 BLAKE2B 
b2b5f9135a15730ca7ddddeaa7f621f82207f1dcf383c3be7459eb39dbffc85a310184a4ddce3fb0bd47aa213cb588eb3f3e2f73418659330a421b7da5b87698
 SHA512 
52436535810ce42f5ab30ae8a4705005e8c7a5d91d52520aab4160320215196cdc088dfae1a21a0d65d0161fb2bb3c9b984cfe2cb5204f7b9bd0ed27c3a38c5b
+DIST borgmatic-1.5.11.tar.gz 72985 BLAKE2B 
fac7e403a4338fc46955d3b82e12e0fc983a11edbb51dc74dcfb6c28818a655b50f7445b28033a966e7e27e2998b062967df97a51f4c362f0d7eac83a19386de
 SHA512 
a945d19bf2fbd617e7de5827d75c8a69f5902c6dfa5d33344b61e680e97636c4a5337d759a372a70b6d2c792a1e7fbc168eedef5e1ae64cac702d313329bca9e

diff --git a/app-backup/borgmatic/borgmatic-1.5.11.ebuild 
b/app-backup/borgmatic/borgmatic-1.5.11.ebuild
new file mode 100644
index 00000000000..7ded25f08aa
--- /dev/null
+++ b/app-backup/borgmatic/borgmatic-1.5.11.ebuild
@@ -0,0 +1,71 @@
+# Copyright 1999-2020 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=7
+
+PYTHON_COMPAT=( python3_{7..9} )
+DISTUTILS_SINGLE_IMPL=1
+DISTUTILS_USE_SETUPTOOLS="rdepend"
+
+inherit distutils-r1 systemd
+
+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"
+
+# Fails due to problems with dev-python/flexmock-0.10.4; see Bug #740128
+RESTRICT="test"
+
+# borg is called as an external tool, hence no pythonic stuff
+RDEPEND="app-backup/borgbackup
+       $(python_gen_cond_dep '
+               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}]
+       ')"
+#BDEPEND="
+#      test? (
+#              $(python_gen_cond_dep '
+#                      dev-python/flexmock[${PYTHON_USEDEP}]
+#              ')
+#      )"
+
+PATCHES=(
+       "${FILESDIR}"/${PN}-1.5.1-systemd_service_bin_path.patch
+       "${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 by the time we execute src_test will
+       # not have been created yet. distutils_install_for_testing would likely
+       # take care of this - but between the aforementioned behaviour 
inconsistency
+       # and the fact the only test run from this file as of version 1.5.11 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
+       systemd_dounit sample/systemd/borgmatic.{service,timer}
+       keepdir /etc/borgmatic
+}
+
+pkg_postinst() {
+       if [[ -z "${REPLACING_VERSIONS}" ]]; then
+               elog "To generate a sample configuration file, run:"
+               elog "    generate-borgmatic-config"
+       fi
+       elog
+       elog "Systemd users wishing to periodically run borgmatic can use the 
provided timer and service units."
+}

Reply via email to