Bug 25064 - backup-manager: Invalid installation paths hardcoded in the executable make it useless
Summary: backup-manager: Invalid installation paths hardcoded in the executable make i...
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 7
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: QA Team
QA Contact:
URL:
Whiteboard: MGA7-64-OK
Keywords: advisory, validated_update
Depends on:
Blocks:
 
Reported: 2019-07-06 18:38 CEST by Guillaume Rousse
Modified: 2019-07-10 12:45 CEST (History)
1 user (show)

See Also:
Source RPM: backup-manager
CVE:
Status comment:


Attachments

Description Guillaume Rousse 2019-07-06 18:38:19 CEST
The officiel release tarball for backup-manager 0.7.15 is incorrect, and uses a broken install logic. As a consequences, the backup-manager executable looks for its component in non-existing places, as shown by the following error:

[guillaume@host ~]$ sudo backup-manager
/sbin/backup-manager: line 62: /home/iurt/rpmbuild/BUILDROOT/backup-manager-0.7.15-2.mga7.i386//usr/lib/backup-manager/externals.sh: No such file or directory

The backup-manager-0.7.15-2.1.mga7 release, submitted to 7/updates_testing, fix this issue by using another source tarball, directly created from upstream git repository.
Comment 1 Rémi Verschelde 2019-07-10 10:55:43 CEST
Bug confirmed and fix tested successfully on Mageia 7 x86_64.

Whiteboard: (none) => MGA7-64-OK

Comment 2 Rémi Verschelde 2019-07-10 10:58:13 CEST
Advisory uploaded, validating.

Keywords: (none) => advisory, validated_update
CC: (none) => sysadmin-bugs

Rémi Verschelde 2019-07-10 10:58:29 CEST

Summary: Invalid installation pathes hardcoded in the executable make it useless => backup-manager: Invalid installation paths hardcoded in the executable make it useless

Comment 3 Mageia Robot 2019-07-10 12:45:42 CEST
An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGAA-2019-0058.html

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


Note You need to log in before you can comment on or make changes to this bug.