[SRU] Update to new maintenance release

[Remco]

[Impact]
The package currently provided in Ubuntu 16.04 LTS has a bug that causes backups to fail:
https://github.com/borgbackup/borg/issues/2994

[Test Case]
* Try to save and restore a backup with a different timedate

[Regression potential]
Minimal, borgbackup has a huge testsuite that is ran during build and autopkgtests

[Other info]
It has been fixed upstream in a new maintenance release:

https://github.com/borgbackup/borg/blob/1.0.12/docs/changes.rst#version-1012-2018-04-08

Since it is a maintenance release, it should be safe to update the package.

Current version of package: 1.0.11
Request update to version: 1.0.12

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Sjoerd Job Postmus (sjoerdjob)]

Based on https://wiki.ubuntu.com/SecurityTeam/UpdateProcedures, which states

```
Issues that warrant a security update

We only fix bugs in our stable releases which truly affect overall system security, i. e. which enable an attacker to circumvent the permissions configured on the system, or are a threat to the user's data in any way. Most common examples:

    Buffer overflow in a server process which allows to crash it (denial of service) and/or to execute attacker provided code (privilege escalation).
    Insecure temporary file handling which allows race condition and symlink attacks to delete unrelated files with the invoker's privileges.
    Non-working security-relevant configuration options (e. g. iptables would allow packets which should be blocked, or a server's ACL option does not do the right thing).
    Less critical bugs (like Denial of Service vulnerabilities in instant messengers or email applications) are also fixed usually, but with lower priority.
```

it might be argumented that this is a security issue: "or are a threat to the user's data in any way" and "Non-working security-relevant configuration options".

Of course, that's only one way of reading it, but a backup tool that starts failing to backup does not sound very secure.

[Brian Murray (brian-murray)]

Hello Remco, or anyone else affected,

Accepted borgbackup into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/borgbackup/1.0.12-0ubuntu1.16.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Gianfranco Costamagna (costamagnagianfranco)]

The testsuite passed correctly, and this bug has a replication rate of 1/1*10^6... so I presume we are safe to go :)

[Łukasz Zemczak (sil2100)]

It's hard for me to dig into that, but I assume that this fix is present in the borgbackup versions present in bionic+. Releasing.

[Launchpad Janitor (janitor)]

This bug was fixed in the package borgbackup - 1.0.12-0ubuntu1.16.04.1

---------------
borgbackup (1.0.12-0ubuntu1.16.04.1) xenial; urgency=medium

  * New upstream release, fixing backup issues (LP: #1788829).

 -- Gianfranco Costamagna <email address hidden> Mon, 17 Dec 2018 17:56:28 +0100

[Łukasz Zemczak (sil2100)]

The verification of the Stable Release Update for borgbackup has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.