Package Details: borgmatic 1.3.17-1

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

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 ... Next › Last »

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.

nicoulaj commented on 2019-01-02 14:49

I sent a mail to the aur-general mailing list to clarify what check() should do in this case:

Feel free to give your two cents!

witten commented on 2019-01-02 04:02

@TheCraiggers The error borgmatic: error: unrecognized arguments: --init --encryption repokey suggests to me that borgmatic tests are somehow invoking an old version of borgmatic. That's because the --init option is relatively new.

TheCraiggers commented on 2019-01-02 03:43

Decided I'd test removing borgmatic and attempting reinstall with yay, as @aurelieng was wondering. Ended up getting the same failed two tests as before. I haven't dug into the problem to see if it's just a problem with yay, or if it has an accomplice in the PKGBUILD.

Looks to be the same output as previously reported by @evana here:

aurelieng commented on 2018-12-31 08:39

Same problem here too, even with the last PKGBUILD. Removing the previous borgmatic (1.2.4) prior to building the package manually (using makepkg -s) solved the problem. I haven't tried to install it with my favorite AUR helper (yay) after removing the previous version. It might work. There must be something odd with this PKBUILD, but at least there's a workaround. :)