Created attachment 525144 [details, diff] Patch cherry picked from upstream fixes the reported bug. app-arch/afio-2.5.1 introduced a bug in their control file handling. (Control files are a feature of afio that allow metadata to be included in an archive. Users can write a "control script" to react to that metadata when the archive is unpacked.) If control files are added to an archive, afio-2.5.1-r1 erroneously displays a warning (ASX no fsname for this name ??) and eventually returns a non-zero result, even though the archive is correctly built. flexbackup (and probably other tools that use afio) interprets this as a backup that cannot be trusted. The attached patch was cherry picked from the afio upstream where the bug was already fixed (but not yet released). A patch to the afio-2.5.1-r1 ebuild to apply the new patch is also included.
Created attachment 525146 [details, diff] Patch to ebuild to apply the new patch.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a2b84ee1004c92153ab3d9feda7185d51eb2ebd8 commit a2b84ee1004c92153ab3d9feda7185d51eb2ebd8 Author: Pacho Ramos <pacho@gentoo.org> AuthorDate: 2018-10-20 15:21:17 +0000 Commit: Pacho Ramos <pacho@gentoo.org> CommitDate: 2018-10-20 16:35:34 +0000 app-arch/afio: Fix control file handling (#651294 by John R. Graham) Closes: https://bugs.gentoo.org/651294 Signed-off-by: Pacho Ramos <pacho@gentoo.org> Package-Manager: Portage-2.3.51, Repoman-2.3.11 app-arch/afio/afio-2.5.1-r2.ebuild | 34 ++++++++++++++++++++++ .../afio-2.5.1-control-file-warning-fix.patch | 29 ++++++++++++++++++ 2 files changed, 63 insertions(+)
