I made a new release 1.1.15b1 for testing, see there:

https://github.com/borgbackup/borg/releases/tag/1.1.15b1

As you see, the borg code is pretty much the same as in 1.1.14, but especially the binary building got some updates. Thus, primarily the binaries should get some testing, to find issues before I make the final 1.1.15 release later this year.

As they were made on debian stretch wi

I thought we had an issue for this but couldn't find it.

Currently, the Velero CLI uses the velero namespace in the current context, unless otherwise specified. This means that if you are operating under a namespace other than velero, you have to specify the namespace with every single command.

As it is common with other tools, invert things and make it so Velero recognizes and uses the

What went wrong?

I'm getting deprecation warnings with openSSL encryption.

[2019/09/05 08:38:52][info] Using Encryptor::OpenSSL to encrypt the archive.
[2019/09/05 08:40:22][warn] Pipeline STDERR Messages:
[2019/09/05 08:40:22][warn] (Note: may be interleaved if multiple commands returned error messages)
[2019/09/05 08:40:22][warn]
[2019/09/05 08:40:22][warn] *** WARNING : depre

Is your feature request related to a problem? Please describe.
I've setted automatic-backups in a standard folder on every change. The problem is, that this feature keeps generating "endless" backups with every change. The other option (only backups on add totp) is not an option for me, as it will turn my restore-libary into a mess with outdated totp (because remove). As I sync with nextcloud