Bug 25570

Thank you for reporting :)

As you provide the src rpm for Mageia 7, I presume it is Mageia 7 you run, so I set version to 7.

Assigning to packager per https://madb.mageia.org/

CC: (none) => fri
Version: Cauldron => 7
Assignee: bugsquad => makowski.mageia

should be fixed in borgbackup-1.2.0-0.a4.2.mga7
from borgbackup-1.2.0-0.a4.2.mga7.src.rpm  
in core/updates_testing

Assignee: makowski.mageia => qa-bugs

Thank you Philippe
Curiously: why not updating to later version, like .a9 ?
https://github.com/borgbackup/borg/releases/tag/1.2.0a9
All 1.2.0.a versions have the message "alpha quality, for testing only!"...

MGA7_64 MATE on PEAQ C1011
Installed current version borgbackup-1.2.0-0.a4.1.mga7 and run
$ borg --version 
borg 1.2.0a4
Checked python3-setuptools, it was already installed.
Removed both python3-setuptools and borgbackup, reinstalled borgbackup
and 
$ borg --version 
borg 1.2.0a4
So, only thing I can test is that the new version does not blow up the current result.

CC: (none) => herman.viaene

Installing orgbackup-1.2.0-0.a4.2.mga7 draws in python3-setuptools and 

$ borg --version 
borg 1.2.0a4

So, this update is OK, if Philippe and Morgan can agree to let this one thru.

(In reply to Morgan Leijström from comment #3)
> Thank you Philippe
> Curiously: why not updating to later version, like .a9 ?
> https://github.com/borgbackup/borg/releases/tag/1.2.0a9
> All 1.2.0.a versions have the message "alpha quality, for testing only!"...

Totally agree: As far I can see, this "Alpha" release has been introduced in M7 to resolve this Bug 24529. But WHY an alpha release?

Upstream is at version 1.1.14.

Keywords: (none) => feedback
CC: (none) => ouaurelien

We have already for over a year been serving an early alpha of 1.2.
I think we may break some operation for users using features not available in 1.1.
Breaking a backup functionality is really bad.

I think the correct way is to serve latest possible - most bugfixed 1.2.
But only if there are no new bugs, or removed features.

I do not know this program, so would like input from users and packager.

yes, the first mistake was to update this to 1.2 series, but we serve 1.2, so I aggree we should certainly update mga7 and cauldron to 1.2.0a9

CC: (none) => makowski.mageia

(In reply to Philippe Makowski from comment #8)
> yes, the first mistake was to update this to 1.2 series, but we serve 1.2,
> so I aggree we should certainly update mga7 and cauldron to 1.2.0a9

We should do. Cauldron is "a8", today.

Giving you the ball again then :)

Keywords: feedback => (none)
Assignee: qa-bugs => makowski.mageia

"practical testing of what will become borg 1.2"
https://github.com/borgbackup/borg/issues/4360

Changelog
https://github.com/borgbackup/borg/blob/1.2.0a9/docs/changes.rst#version-120a9-2020-10-05

borgbackup-1.2.0-0.a9.1.mga7 and borgbackup-1.2.0-0.a9.1.mga8
are available

Status: NEW => ASSIGNED
Assignee: makowski.mageia => qa-bugs

Suggested Advisory:
========================

Updated borbackup package fixes missing dependency.

The package borgbackup has been updated to fix some dependencies
errors among other improvements.

See upstream release-notes.

References:
 - https://github.com/borgbackup/borg/blob/1.2.0a9/docs/changes.rst#version-120a9-2020-10-05

========================

Updated packages in core/updates_testing:
========================
borgbackup-1.2.0-0.a9.1.mga7

from borgbackup-1.2.0-0.a9.1.mga7.mga7.src.rpm

CC: (none) => sysadmin-bugs
Keywords: (none) => validated_update
Whiteboard: (none) => MGA7-64-OK
Status comment: Update to latest 1.2 alpha => Update to latest 1.2

MGA7-64-OK
Installs well borgbackup-1.2.0-0.a9.1.mga7 with python3-setuptools and 

$ borg --version 
borg 1.2.0a9

Give this OK.
Validating.
Advisory pushed to SVN.


Typo:
s/borgbackup-1.2.0-0.a9.1.mga7.mga7.src.rpm/borgbackup-1.2.0-0.a9.1.mga7.src.rpm

An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGAA-2020-0235.html

Status: ASSIGNED => RESOLVED
Resolution: (none) => FIXED