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.
Bug confirmed and fix tested successfully on Mageia 7 x86_64.
Whiteboard: (none) => MGA7-64-OK
Advisory uploaded, validating.
Keywords: (none) => advisory, validated_updateCC: (none) => sysadmin-bugs
Summary: Invalid installation pathes hardcoded in the executable make it useless => backup-manager: Invalid installation paths hardcoded in the executable make it useless
An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGAA-2019-0058.html
Status: NEW => RESOLVEDResolution: (none) => FIXED