Hello community, here is the log from the commit of package borgmatic for openSUSE:Factory checked in at 2016-11-25 12:28:20 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/borgmatic (Old) and /work/SRC/openSUSE:Factory/.borgmatic.new (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "borgmatic" Changes: -------- New Changes file: --- /dev/null 2016-10-27 01:54:32.792041256 +0200 +++ /work/SRC/openSUSE:Factory/.borgmatic.new/borgmatic.changes 2016-11-25 12:28:21.000000000 +0100 @@ -0,0 +1,10 @@ +------------------------------------------------------------------- +Sun Oct 30 23:35:27 UTC 2016 - [email protected] + +- Trim and wrap description + +------------------------------------------------------------------- +Thu Oct 13 07:35:01 UTC 2016 - [email protected] + +- version 1.0.3-dev: initial build + New: ---- README.md _service borgmatic-1.0.3hg.135.tar.xz borgmatic.changes borgmatic.spec ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ borgmatic.spec ++++++ # # spec file for package borgmatic # # Copyright (c) 2016 SUSE LINUX GmbH, Nuernberg, Germany. # # All modifications and additions to the file contributed by third parties # remain the property of their copyright owners, unless otherwise agreed # upon. The license for this file, and modifications and additions to the # file, is the same license as for the pristine package itself (unless the # license for the pristine package is not an Open Source License, in which # case the license is the MIT License). An "Open Source License" is a # license that conforms to the Open Source Definition (Version 1.9) # published by the Open Source Initiative. # Please submit bugfixes or comments via http://bugs.opensuse.org/ # %define version_unconverted 1.0.3hg.135 Name: borgmatic Version: 1.0.3hg.135 Release: 0 Summary: Automation tool for borgbackup License: GPL-3.0 Group: Productivity/Archiving/Backup Url: https://torsion.org/borgmatic/ Source: borgmatic-%{version}.tar.xz Source1: README.md BuildArch: noarch BuildRequires: python3 >= 3.4 BuildRequires: python3-devel BuildRequires: python3-setuptools BuildRequires: systemd-devel # To create the manpage BuildRequires: pandoc Requires: borgmatic # testing requirements BuildRequires: python3-pytest BuildRequires: python3-flexmock BuildRoot: %{_tmppath}/%{name}-%{version}-build %description borgmatic is a Python wrapper script for the Borg backup software that initiates a backup, prunes any old backups according to a retention policy, and validates backups for consistency. The script supports specifying your settings in a declarative configuration file rather than having to put them all on the command-line, and handles common errors. %prep %setup -q # test_version.py fails because of assert '1.0.3.dev0\n' == '1.0.3-dev\n', so we just remove it rm borgmatic/tests/integration/test_version.py # Make sample files use the borgmatic command on /usr/bin, not /usr/local/bin perl -pi -e "s,PATH=\\$PATH:/usr/local/bin /usr/local/bin/borgmatic,/usr/bin/borgmatic," sample/cron/borgmatic perl -pi -e "s,/usr/local/bin/borgmatic,/usr/bin/borgmatic," sample/systemd/borgmatic.service %build # Create the manpage pandoc -s -f markdown -t man %{S:1} -o borgmatic.1 %install python3 setup.py install --prefix=%{_prefix} --root=%{buildroot} install -d %{buildroot}%{_sysconfdir}/borgmatic install -m 0644 sample/config sample/excludes %{buildroot}%{_sysconfdir}/borgmatic/ install -d %{buildroot}%{_docdir}/%{name}/sample/cron install -m 0644 sample/cron/borgmatic %{buildroot}%{_docdir}/%{name}/sample/cron/ install -d %{buildroot}%{_unitdir}/ install -m 0644 sample/systemd/borgmatic* %{buildroot}%{_unitdir}/ install -D -m 0644 borgmatic.1 %{buildroot}%{_mandir}/man1/borgmatic.1 %check # testing the build is a little awkward, since the original testsuite is based on tox and # tox tries to create a virtual environment, that we need tight control on in order to get # it to behave in our build system (offline mode, use site packages). OTOH, without the # venv, we face problems with setuptools (borg uses pkg_resources to locate the installed # package), while py.test relies on the usual module handling. <[email protected]> pyvenv --system-site-packages --without-pip borgmatic-env source borgmatic-env/bin/activate python3 setup.py install LANG=en_US.UTF-8 PYTHONPATH=$(pwd) py.test -v --pyargs borgmatic %post %service_add_post borgmatic.service %pre %service_add_pre borgmatic.service %preun %service_del_preun borgmatic.service %postun %service_del_postun borgmatic.service %files %defattr(-,root,root,-) %doc AUTHORS LICENSE NEWS README.md %config %{_sysconfdir}/borgmatic/config %config %{_sysconfdir}/borgmatic/excludes %dir %{_sysconfdir}/borgmatic %{python3_sitelib}/borgmatic/ %{python3_sitelib}/borgmatic-1.0.3.dev0-py%{py3_ver}.egg-info %{_unitdir}/borgmatic.service %{_unitdir}/borgmatic.timer %{_bindir}/borgmatic %{_mandir}/man1/borgmatic.1%{ext_man} %changelog ++++++ README.md ++++++ % borgmatic(1) Automation tool for borgbackup # NAME borgmatic - Automation tool for borgbackup # SYNOPSIS borgmatic # DESCRIPTION borgmatic (formerly atticmatic) is a simple Python wrapper script for the [Borg](https://borgbackup.readthedocs.org/en/stable/) backup software that initiates a backup, prunes any old backups according to a retention policy, and validates backups for consistency. The script supports specifying your settings in a declarative configuration file rather than having to put them all on the command-line, and handles common errors. You can run borgmatic and start a backup simply by invoking it without arguments. This will also prune any old backups as per the configured retention policy, and check backups for consistency problems due to things like file damage. By default, the backup will proceed silently except in the case of errors. But if you'd like to to get additional information about the progress of the backup as it proceeds, use the verbosity option: borgmatic --verbosity 1 Or, for even more progress spew: borgmatic --verbosity 2 If you'd like to see the available command-line arguments, view the help: borgmatic --help # GENERAL ## Overview Here's an example config file: ```INI [location] # Space-separated list of source directories to backup. # Globs are expanded. source_directories: /home /etc /var/log/syslog* # Path to local or remote backup repository. repository: user@backupserver:sourcehostname.borg [retention] # Retention policy for how many backups to keep in each category. keep_daily: 7 keep_weekly: 4 keep_monthly: 6 [consistency] # Consistency checks to run, or "disabled" to prevent checks. checks: repository archives ``` Additionally, exclude patterns can be specified in a separate excludes config file, one pattern per line. borgmatic is hosted at <https://torsion.org/borgmatic> with [source code available](https://torsion.org/hg/borgmatic). It's also mirrored on [GitHub](https://github.com/witten/borgmatic) and [BitBucket](https://bitbucket.org/dhelfman/borgmatic) for convenience. ## Setup To get up and running, follow the [Borg Quick Start](https://borgbackup.readthedocs.org/en/latest/quickstart.html) to create a repository on a local or remote host. Note that if you plan to run borgmatic on a schedule with cron, and you encrypt your Borg repository with a passphrase instead of a key file, you'll need to set the borgmatic `encryption_passphrase` configuration variable. See the repository encryption section of the Quick Start for more info. If the repository is on a remote host, make sure that your local root user has key-based ssh access to the desired user account on the remote host. You can find example configuration files to run borgmatic automatically from cron or systemd at /usr/share/doc/packages/borgmatic/sample/cron and /usr/share/doc/packages/borgmatic/sample/systemd. Lastly, modify the /etc/borgmatic files with your desired configuration. ## Upgrading from atticmatic borgmatic only supports Borg now and no longer supports Attic. So if you're an Attic user, consider switching to Borg. See the [Borg upgrade command](https://borgbackup.readthedocs.io/en/stable/usage.html#borg-upgrade) for more information. Then, follow the instructions above about setting up your borgmatic configuration files. ## Autopilot If you want to run borgmatic automatically, say once a day, the you can configure a job runner to invoke it periodically. ### systemd If you're using systemd instead of cron to run jobs, the service files are already installed and all you have to do is enable and start the borgmatic service: sudo systemctl enable borgmatic.timer sudo systemctl start borgmatic.timer Feel free to modify the timer file based on how frequently you'd like borgmatic to run. ### cron If you prefer to use cron, copy the sample file to the cron directory: sudo cp /usr/share/doc/packages/borgmatic/sample/cron /etc/cron.d/borgmatic You can modify the cron file if you'd like to run borgmatic more or less frequently. ## Troubleshooting ### Broken pipe with remote repository When running borgmatic on a large remote repository, you may receive errors like the following, particularly while "borg check" is validating backups for consistency: Write failed: Broken pipe borg: Error: Connection closed by remote host This error can be caused by an ssh timeout, which you can rectify by adding the following to the ~/.ssh/config file on the client: Host * ServerAliveInterval 120 This should make the client keep the connection alive while validating backups. ## Issues and feedback Got an issue or an idea for a feature enhancement? Check out the [borgmatic issue tracker](https://tree.taiga.io/project/witten-borgmatic/issues?page=1&status=399951,399952,399955). In order to create a new issue or comment on an issue, you'll need to [login first](https://tree.taiga.io/login). Other questions or comments? Contact <mailto:[email protected]>. ++++++ _service ++++++ <services> <service name="tar_scm" mode="localonly"> <param name="scm">hg</param> <param name="url">https://torsion.org/hg/borgmatic/</param> <param name="filename">borgmatic</param> <param name="versionformat">1.0.3hg.{rev}</param> </service> <service name="recompress" mode="localonly"> <param name="file">*.tar</param> <param name="compression">xz</param> </service> <service name="set_version" mode="localonly"/> </services>
