Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1499512 - borgbackup 1.1.0 is available
Summary: borgbackup 1.1.0 is available
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: borgbackup
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Benjamin Pereto
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-10-08 08:07 UTC by Felix Schwarz
Modified: 2017-11-07 22:14 UTC (History)
3 users (show)

Fixed In Version: borgbackup-1.1.0-1.fc26 borgbackup-1.1.0-1.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-11-01 00:02:05 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Felix Schwarz 2017-10-08 08:07:26 UTC 
borg 1.1.0 is available: https://github.com/borgbackup/borg/releases/tag/1.1.0

Changelog: https://www.borgbackup.org/releases/borg-1.1.html

This is a major release. From the changelog it seems as if upgrading should be pretty simple and mostly backwards compatible (no need to explicitely upgrade the repo). Still some CLI flags did change so there might be some breakage for existing users.

Personally I hope you can ship 1.1.0 in F27+. If everything goes well maybe push the upgrade to EPEL? Not sure about F26 but maybe update it there at the same time the package lands in EPEL?
Comment 1 Fedora Update System 2017-10-12 15:44:17 UTC 
borgbackup-1.1.0-1.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2017-10e95a8d1f
Comment 2 Fedora Update System 2017-10-12 15:44:50 UTC 
borgbackup-1.1.0-1.el7 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-f2d9488b45
Comment 3 Benjamin Pereto 2017-10-12 15:56:13 UTC 
I builded it for all 3 supported versions.

Also I agree that is backwards compatible, and the changed cli options showing now a deprecated flag.
In the favor of bringing new functionality of a young and fast developed project, I suggest to push 1.1.0 not only to f27+.

I will let the packages longer in testing and if a regression is detected, stop from pushing to stable.

F25 will be end of life soon (end of this year?), so I revoked the update
Comment 4 Fedora Update System 2017-10-13 22:22:59 UTC 
borgbackup-1.1.0-1.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-763e7bdf41
Comment 5 Fedora Update System 2017-10-13 23:47:06 UTC 
borgbackup-1.1.0-1.el7 has been pushed to the Fedora EPEL 7 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-f2d9488b45
Comment 6 Felix Schwarz 2017-10-24 14:52:16 UTC 
Btw: borg 1.1.1 is already available ( https://github.com/borgbackup/borg/releases/tag/1.1.1 ).
Comment 7 Benjamin Pereto 2017-10-31 06:08:34 UTC 
I submit an update to 1.1.1 if the minor update 1.1.0 slips to stable.
Comment 8 Fedora Update System 2017-11-01 00:02:05 UTC 
borgbackup-1.1.0-1.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.
Comment 9 Fedora Update System 2017-11-07 22:14:57 UTC 
borgbackup-1.1.0-1.el7 has been pushed to the Fedora EPEL 7 stable repository. If problems still persist, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.