Package Details: borgmatic 1.3.11-2

Git Clone URL: (read-only)
Package Base: borgmatic
Description: Simple, configuration-driven backup software for servers and workstations
Upstream URL:
Licenses: GPL3
Submitter: nylocx
Maintainer: devopsdeluxe (witten, nicoulaj)
Last Packager: witten
Votes: 25
Popularity: 0.800961
First Submitted: 2016-02-18 13:48
Last Updated: 2019-06-25 19:45

Latest Comments

1 2 3 4 5 6 ... Next › Last »

witten commented on 2019-06-25 19:47

@jhenson Thanks for reporting. I think I just fixed it by adding a colorama dependency.

jhenson commented on 2019-06-25 19:05

The latest version needs a dependency to python-colorama added to the pkgbuild.

Traceback (most recent call last):
  File "/usr/bin/borgmatic", line 6, in <module>
    from pkg_resources import load_entry_point
  File "/usr/lib/python3.7/site-packages/pkg_resources/", line 3241, in <module>
  File "/usr/lib/python3.7/site-packages/pkg_resources/", line 3225, in _call_aside
    f(*args, **kwargs)
  File "/usr/lib/python3.7/site-packages/pkg_resources/", line 3254, in _initialize_master_working_set
    working_set = WorkingSet._build_master()
  File "/usr/lib/python3.7/site-packages/pkg_resources/", line 583, in _build_master
  File "/usr/lib/python3.7/site-packages/pkg_resources/", line 900, in require
    needed = self.resolve(parse_requirements(requirements))
  File "/usr/lib/python3.7/site-packages/pkg_resources/", line 786, in resolve
    raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'colorama<0.5,>=0.4.1' distribution was not found and is required by borgmatic

devopsdeluxe commented on 2019-05-03 21:58

the dependency patch is missing:

That's intentional. As for why it's not included, see the note at the end of the linked section:

Stunkymonkey commented on 2019-05-03 19:30

the dependency patch is missing:

it is beeing used in the PKGBUILD.

witten commented on 2019-01-06 22:22

@anponteg Please report any issues with borgmatic itself (rather than AUR packaging) upstream. See

It'd also be helpful to include your config file there with anything sensitive redacted. Thanks!

anponteg commented on 2019-01-06 14:59

Hi! If I uncomment compression: lz4 in /etc/borgmatic/config.yaml I get this error when I run borgmatic:

 --- All found errors ---
["Key 'compression' was not defined. Path: '/location'"]
Errors found but will not raise exception...
/etc/borgmatic/config.yaml: Error running configuration file
An error occurred while parsing a configuration file at /etc/borgmatic/config.yaml:
Key 'compression' was not defined. Path: '/location'

Need some help?

witten commented on 2019-01-05 22:10

This package currently installs a tests directory into site-packages which should be avoided to prevent conflicts.

Note that upstream does not do this if pip installed directly. Instead, it installs tests into site-packages/borgmatic/tests.

jematee commented on 2019-01-05 09:32

This package currently installs a tests directory into site-packages which should be avoided to prevent conflicts.

TheCraiggers commented on 2019-01-02 19:24

I agree with @eschwartz. I don't think I can say what was already said any better, so I'll just leave it at that.

eschwartz commented on 2019-01-02 15:02

Using tox to run the testsuite for a python package "because that is what upstream CI does" is no different from using a Ubuntu Docker container to run make check on a C/C++ project again because that is what upstream does.

Upstream already runs tox in order to check that the code as uploaded to PyPI is well-formed and runs okay under optimally predictable circumstances. But the PKGBUILD check() function is part of the packaging process for packaging software with Arch Linux, and as such, it is pointless if the check() function does not check that which will actually be getting run on Arch Linux systems.

I've added a warning at to clarify this.