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

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

What steps did you take and what happened:
[A clear and concise description of what the bug is, and what commands you ran.)

Installed Velero with the following (as per documentation - note the --generate-name)

helm install vmware-tanzu/velero --namespace velero
--set-file credentials.secretContents.cloud=/Users/rbrito/OneDrive/migrator/credentials-velero
--set configuration.provid

If you don't configure the destination disk properly, it will be very hard to understand what's happening because this message:

"Endpoints must be full URIs and include a scheme and host"

Is hidden by the exception handler:

public static function create(string $diskName, string $backupName): self
{
    try {
        $disk = app(Factory::class)->disk($diskName);

        

General information

• App version: 0.8.0-play
• App source: Google Play
• Android Version: 9
• Custom ROM:

Expected result

What is expected?

That I can edit the time or digits after importing an account in case it is wrong.

What does happen instead?

It is greyed out.

Steps to reproduce

• Create an account
• Try to edit it