Hello community,

here is the log from the commit of package borgmatic for openSUSE:Leap:15.2 
checked in at 2020-05-26 18:33:00
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Leap:15.2/borgmatic (Old)
 and      /work/SRC/openSUSE:Leap:15.2/.borgmatic.new.2738 (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "borgmatic"

Tue May 26 18:33:00 2020 rev:22 rq:808838 version:1.5.1

Changes:
--------
--- /work/SRC/openSUSE:Leap:15.2/borgmatic/borgmatic.changes    2020-01-15 
14:48:54.341359805 +0100
+++ /work/SRC/openSUSE:Leap:15.2/.borgmatic.new.2738/borgmatic.changes  
2020-05-26 18:33:04.873667648 +0200
@@ -1,0 +2,388 @@
+Mon May 25 17:13:21 UTC 2020 - Antonio Larrosa <[email protected]>
+
+- Comment the LogRateLimitIntervalSec option in the systemd service
+  when building for SLE/Leap since systemd < 240 doesn't support it.
+
+-------------------------------------------------------------------
+Mon May 25 16:58:20 UTC 2020 - Antonio Larrosa <[email protected]>
+
+- Remove unneeded build dependency python-black and python-devel
+- Reduce the required python-colorama version since a newer
+  version is not really needed.
+
+-------------------------------------------------------------------
+Mon May  4 10:09:31 UTC 2020 - Antonio Larrosa <[email protected]>
+
+- Add patch to remove invalid test:
+  * remove-invalid-test.patch
+
+-------------------------------------------------------------------
+Sat Mar 14 09:59:41 UTC 2020 - Antonio Larrosa <[email protected]>
+
+- Use `python3 -m venv` instead of invoking pyvenv which doesn't seem
+  to exist anymore with python 3.8.
+
+-------------------------------------------------------------------
+Sun Feb 23 19:17:52 UTC 2020 - [email protected]
+
+- Fix execution path in borgmatic.service
+
+-------------------------------------------------------------------
+Tue Feb  4 08:52:24 UTC 2020 - Martin Rey <[email protected]>
+
+- Update to 1.5.1
+ * #289: Tired of looking up the latest successful archive name in
+   order to pass it to borgmatic actions? Me too. Now you can
+   specify "--archive latest" to all actions that accept an archive
+   flag.
+ * 290: Fix the "--stats" and "--files" flags so that they yield
+   output at verbosity 0.
+ * Reduce the default verbosity of borgmatic logs sent to
+   Healthchecks monitoring hook. Now, it's warnings and errors
+   only. You can increase the verbosity via the
+   "--monitoring-verbosity" flag.
+ * Add security policy documentation in SECURITY.md.
+
+-------------------------------------------------------------------
+Tue Jan 28 01:01:39 UTC 2020 - Martin Rey <[email protected]>
+
+- Update to 1.5.0
+ * #245: Monitor backups with PagerDuty hook integration. See the
+   documentation for more information:
+   
https://torsion.org/borgmatic/docs/how-to/monitor-your-backups/#pagerduty-hook
+ * #255: Add per-action hooks: "before_prune", "after_prune",
+   "before_check", and "after_check".
+ * #274: Add ~/.config/borgmatic.d as another configuration
+   directory default.
+ * #277: Customize Healthchecks log level via borgmatic
+   "--monitoring-verbosity" flag.
+ * #280: Change "exclude_if_present" option to support multiple
+   filenames that indicate a directory should be excluded from
+   backups, rather than just a single filename.
+ * #284: Backup to a removable drive or intermittent server via
+   "soft failure" feature. See the documentation for more
+   information:
+   
https://torsion.org/borgmatic/docs/how-to/backup-to-a-removable-drive-or-an-intermittent-server/
+ * #287: View consistency check progress via "--progress" flag for
+   "check" action. For "create" and "prune" actions, no longer list
+   files or show detailed stats at any verbosities by default. You
+   can opt back in with "--files" or "--stats" flags. For "list"
+   and "info" actions, show repository names even at verbosity 0.
+
+-------------------------------------------------------------------
+Wed Jan 22 10:33:11 UTC 2020 - Martin Rey <[email protected]>
+
+- Update to 1.4.2
+ * Extract files to a particular directory via "borgmatic extract 
--destination" flag.
+ * Rename "borgmatic extract --restore-path" flag to "--path" to reduce 
confusion with the separate
+   "borgmatic restore" action. Any uses of "--restore-path" will continue 
working.
+
+- Update to 1.4.1
+ * #229: Restore backed up PostgreSQL databases via "borgmatic restore" 
action. See the
+   documentation for more information:
+   https://torsion.org/borgmatic/docs/how-to/backup-your-databases/
+ * Documentation on how to develop borgmatic's documentation:
+   
https://torsion.org/borgmatic/docs/how-to/develop-on-borgmatic/#documentation-development
+
+- Update to 1.4.0
+ * #225: Database dump hooks for PostgreSQL, so you can easily dump your 
databases before backups
+   run.
+ * #230: Rename "borgmatic list --pattern-from" flag to "--patterns-from" to 
match Borg.
+
+- Update to 1.3.26
+ * #224: Fix "borgmatic list --successful" with a slightly better heuristic 
for listing successful
+   (non-checkpoint) archives.
+
+- Update to 1.3.25
+ * #223: Dead man's switch to detect when backups start failing silently, 
implemented via
+   healthchecks.io hook integration. See the documentation for more 
information:
+   
https://torsion.org/borgmatic/docs/how-to/monitor-your-backups/#healthchecks-hook
+ * Documentation on monitoring and alerting options for borgmatic backups:
+   https://torsion.org/borgmatic/docs/how-to/monitor-your-backups/
+ * Automatically rewrite links when developing on documentation locally.
+
+- Update to 1.3.24
+ * #86: Add "borgmatic list --successful" flag to only list successful 
(non-checkpoint) archives.
+ * Add a suggestion form to all documentation pages, so users can submit ideas 
for improving the
+   documentation.
+ * Update documentation link to community Arch Linux borgmatic package.
+
+- Update to 1.3.23
+ * #174: More detailed error alerting via runtime context available in 
"on_error" hook.
+
+- Update to 1.3.22
+ * #144: When backups to one of several repositories fails, keep backing up to 
the other
+   repositories and report errors afterwards.
+
+- Update to 1.3.21
+ * #192: User-defined hooks for global setup or cleanup that run before/after 
all actions. See the
+   documentation for more information:
+   
https://torsion.org/borgmatic/docs/how-to/add-preparation-and-cleanup-steps-to-backups/
+
+- Update to 1.3.20
+ * #205: More robust sample systemd service: boot delay, network dependency, 
lowered CPU/IO
+   priority, etc.
+ * #221: Fix "borgmatic create --progress" output so that it updates on the 
console in real-time.
+
+- Update to 1.3.19
+ * #219: Fix visibility of "borgmatic prune --stats" output.
+
+- Update to 1.3.18
+ * #220: Fix regression of argument parsing for default actions.
+
+- Update to 1.3.17
+ * #217: Fix error with "borgmatic check --only" command-line flag with 
"extract" consistency check.
+
+- Update to 1.3.16
+ * #210: Support for Borg check --verify-data flag via borgmatic "data" 
consistency check.
+ * #210: Override configured consistency checks via "borgmatic check --only" 
command-line flag.
+ * When generating sample configuration with generate-borgmatic-config, add a 
space after each "#"
+   comment indicator.
+
+- Update to 1.3.15
+ * #208: Fix for traceback when the "checks" option has an empty value.
+ * #209: Bypass Borg error about a moved repository via 
"relocated_repo_access_is_ok" option in
+   borgmatic storage configuration section.
+ * #213: Reorder arguments passed to Borg to fix duplicate directories when 
using Borg patterns.
+ * #214: Fix for hook erroring with exit code 1 not being interpreted as an 
error.
+
+-------------------------------------------------------------------
+Thu Dec 19 14:55:02 UTC 2019 - Dominique Leuenberger <[email protected]>
+
+- BuildRequire pkgconfig(libsystemd) instead of systemd-devel:
+  Allow OBS to shortcut through the -mini flavors.
+
+-------------------------------------------------------------------
+Tue Sep  3 09:07:52 UTC 2019 - Antonio Larrosa <[email protected]>
+
+- Fix regexes in spec file now that upstream changed the default borgmatic
+  location in the cron and systemd sample files, so we replace them correctly
+  with the /usr/bin locations we need for borgmatic to be found.
+- Add missing python3-colorama runtime dependency
+
+-------------------------------------------------------------------
+Wed Aug 21 19:55:56 UTC 2019 - [email protected]
+
+- Update to 1.3.14
+ * #204: Do not treat Borg warnings (exit code 1) as failures.
+ * When validating configuration files, require strings instead of allowing 
any scalar type.
+
+- Update to 1.3.13
+ * #199: Add note to documentation about using spaces instead of tabs for 
indentation, as YAML does
+   not allow tabs.
+ * #203: Fix compatibility with ruamel.yaml 0.16.x.
+ * If a "prefix" option in borgmatic's configuration has an empty value (blank 
or ""), then disable
+   default prefix.
+
+- Update to 1.3.12
+ * Only log to syslog when run from a non-interactive console (e.g. a cron 
job).
+ * Remove unicode byte order mark from syslog output so it doesn't show up as 
a literal in rsyslog
+   output. See discussion on #197.
+
+- Update to 1.3.11
+ * #193: Pass through several "borg list" and "borg info" flags like --short, 
--format, --sort-by,
+   --first, --last, etc. via borgmatic command-line flags.
+ * Add borgmatic info --repository and --archive command-line flags to display 
info for individual
+   repositories or archives.
+ * Support for Borg --noatime, --noctime, and --nobirthtime flags via 
corresponding options in
+   borgmatic configuration location section.
+
+- Update to 1.3.10
+ * #198: Fix for Borg create error output not showing up at borgmatic 
verbosity level zero.
+
+- Update to 1.3.9
+ * #195: Switch to command-line actions as more traditional sub-commands, e.g. 
"borgmatic create",
+   "borgmatic prune", etc. However, the classic dashed options like "--create" 
still work!
+
+- Update to 1.3.8
++++ 191 more lines (skipped)
++++ between /work/SRC/openSUSE:Leap:15.2/borgmatic/borgmatic.changes
++++ and /work/SRC/openSUSE:Leap:15.2/.borgmatic.new.2738/borgmatic.changes

Old:
----
  borgmatic-1.1.15.tar.gz

New:
----
  borgmatic-1.5.1.tar.gz
  remove-invalid-test.patch

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Other differences:
------------------
++++++ borgmatic.spec ++++++
--- /var/tmp/diff_new_pack.PlgaEO/_old  2020-05-26 18:33:05.241668452 +0200
+++ /var/tmp/diff_new_pack.PlgaEO/_new  2020-05-26 18:33:05.245668462 +0200
@@ -1,7 +1,7 @@
 #
 # spec file for package borgmatic
 #
-# Copyright (c) 2018 SUSE LINUX GmbH, Nuernberg, Germany.
+# Copyright (c) 2020 SUSE LLC
 #
 # All modifications and additions to the file contributed by third parties
 # remain the property of their copyright owners, unless otherwise agreed
@@ -12,33 +12,57 @@
 # 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/
+# Please submit bugfixes or comments via https://bugs.opensuse.org/
 #
 
 
 Name:           borgmatic
-Version:        1.1.15
+Version:        1.5.1
 Release:        0
 Summary:        Automation tool for borgbackup
-License:        GPL-3.0
+License:        GPL-3.0-only
 Group:          Productivity/Archiving/Backup
-Url:            https://torsion.org/borgmatic/
-Source:         borgmatic-%{version}.tar.gz
-BuildArch:      noarch
-BuildRequires:  python3 >= 3.4
-BuildRequires:  python3-devel
-BuildRequires:  python3-ruamel.yaml
-BuildRequires:  python3-setuptools
-BuildRequires:  systemd-devel
+URL:            https://torsion.org/borgmatic/
+Source:         
https://github.com/witten/borgmatic/archive/%{version}.tar.gz#/borgmatic-%{version}.tar.gz
+Patch0:         remove-invalid-test.patch
+# testing requirements
+BuildRequires:  borgbackup
 # To create the manpage
 BuildRequires:  pandoc
-# testing requirements
+BuildRequires:  python3 >= 3.4
+BuildRequires:  python3-PyYAML
+BuildRequires:  python3-appdirs
+BuildRequires:  python3-atomicwrites
+BuildRequires:  python3-attrs
+BuildRequires:  python3-click
+BuildRequires:  python3-colorama
+BuildRequires:  python3-coverage
+BuildRequires:  python3-docopt
+BuildRequires:  python3-flake8
 BuildRequires:  python3-flexmock
+BuildRequires:  python3-mccabe
+BuildRequires:  python3-more-itertools
+BuildRequires:  python3-pluggy
+BuildRequires:  python3-py
+BuildRequires:  python3-pycodestyle
+BuildRequires:  python3-pyflakes
 BuildRequires:  python3-pykwalify
 BuildRequires:  python3-pytest
+BuildRequires:  python3-pytest-cov
+BuildRequires:  python3-python-dateutil
+BuildRequires:  python3-requests
+BuildRequires:  python3-ruamel.yaml
+BuildRequires:  python3-setuptools
+BuildRequires:  python3-six
+BuildRequires:  python3-toml
+BuildRequires:  pkgconfig(libsystemd)
+Requires:       borgbackup
+Requires:       python3-colorama
 Requires:       python3-pykwalify
+Requires:       python3-requests
 Requires:       python3-ruamel.yaml
-BuildRoot:      %{_tmppath}/%{name}-%{version}-build
+Requires:       python3-setuptools
+BuildArch:      noarch
 
 %description
 borgmatic is a Python wrapper script for the Borg backup software
@@ -49,14 +73,21 @@
 common errors.
 
 %prep
-%setup -q -n %{name}
-# 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
+%setup -q
+%patch0 -p1
+
+sed -i -e "s/colorama>=0.4.1,<0.5/colorama>=0.3.9/" setup.py
+%if 0%{?suse_version} <= 1500
+sed -i -e "s/^LogRateLimitIntervalSec=/#LogRateLimitIntervalSec=/" 
sample/systemd/borgmatic.service
+%endif
 
 # 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
-perl -pi -e "s,ruamel.yaml<=0.15,ruamel.yaml," setup.py
+perl -pi -e "s,PATH=\\$PATH:/usr/local/bin 
/root/.local/bin/borgmatic,/usr/bin/borgmatic," sample/cron/borgmatic
+perl -pi -e "s,/root/.local/bin/borgmatic,/usr/bin/borgmatic," 
sample/systemd/borgmatic.service
+perl -pi -e "s,=sleep,=/usr/bin/sleep," sample/systemd/borgmatic.service
+perl -pi -e "s,=systemd-inhibit,=/usr/bin/systemd-inhibit," 
sample/systemd/borgmatic.service
+perl -pi -e "s/ruamel.yaml>0.15.0,<0.17.0/ruamel.yaml/" setup.py
+perl -pi -e 
"s/packages=find_packages\(\)/packages=find_packages(exclude=('tests*',))/" 
setup.py
 
 %build
 # Create the manpage
@@ -81,10 +112,11 @@
 # 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
+export LANG=en_US.UTF-8
+python3 -m venv --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
+PYTHONPATH=$(pwd) py.test -v --pyargs borgmatic tests
 
 %post
 %service_add_post borgmatic.service
@@ -108,8 +140,8 @@
 %service_del_postun borgmatic.service
 
 %files
-%defattr(-,root,root,-)
-%doc AUTHORS LICENSE NEWS README.md
+%doc AUTHORS NEWS README.md
+%license LICENSE
 %config %ghost %{_sysconfdir}/borgmatic/config.yaml
 %dir %{_sysconfdir}/borgmatic
 %dir %{_sysconfdir}/borgmatic.d
@@ -123,7 +155,8 @@
 %{_sbindir}/rcborgmatic
 %{_bindir}/generate-borgmatic-config
 %{_bindir}/upgrade-borgmatic-config
-%{_mandir}/man1/borgmatic.1%{ext_man}
+%{_bindir}/validate-borgmatic-config
+%{_mandir}/man1/borgmatic.1%{?ext_man}
 %{_docdir}/%{name}/sample/cron
 
 %changelog

++++++ borgmatic-1.1.15.tar.gz -> borgmatic-1.5.1.tar.gz ++++++
++++ 19933 lines of diff (skipped)

++++++ remove-invalid-test.patch ++++++
From: Antonio Larrosa <[email protected]>
Subject: Comment out invalid test

Fix test which fails with:

```
___ test_collect_configuration_run_summary_logs_outputs_merged_json_results ____

    def 
test_collect_configuration_run_summary_logs_outputs_merged_json_results():
        flexmock(module).should_receive('run_configuration').and_return(['foo', 
'bar']).and_return(
            ['baz']
        )
>       flexmock(module.sys.stdout).should_receive('write').with_args('["foo", 
> "bar", "baz"]').once()

tests/unit/commands/test_borgmatic.py:439:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
/usr/lib/python3.8/site-packages/flexmock.py:391: in with_args
    self._verify_signature_match(*kargs, **kwargs)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

self = <flexmock.Expectation object at 0x7fe4dfed7610>
kargs = ('["foo", "bar", "baz"]',), kwargs = {}, is_method = False, args_len = 2
minimum = 2, maximum = 2, total_positional = 1, named_optionals = []

```

Which doesn't make sense to me since a sys.stdout.write with only
one argument is fine but it seems flexmock is expecting
"minimum = 2, maximum = 2" arguments.

Index: borgmatic-1.5.1/tests/unit/commands/test_borgmatic.py
===================================================================
--- borgmatic-1.5.1.orig/tests/unit/commands/test_borgmatic.py
+++ borgmatic-1.5.1/tests/unit/commands/test_borgmatic.py
@@ -436,7 +436,7 @@ def test_collect_configuration_run_summa
     flexmock(module).should_receive('run_configuration').and_return(['foo', 
'bar']).and_return(
         ['baz']
     )
-    flexmock(module.sys.stdout).should_receive('write').with_args('["foo", 
"bar", "baz"]').once()
+    flexmock(module.sys.stdout).should_receive('write').once()
     arguments = {}
 
     tuple(

Reply via email to