The preparation stage fails with message: patchelf: getting info about 'librsyncffi.compiled._librsyncffi*.so': No such file or directory The corresponding line in the ebuild is: if use librsync-bundled ; then patchelf --set-rpath '$ORIGIN' librsyncffi.compiled._librsyncffi*.so || die else rm -vf librsync.so.1 || die fi There is no 'librsyncffi.compiled._librsyncffi*.so' in the $WORKDIR. The most closest names are: librsyncffi_native.cpython-37m-x86_64-linux-gnu.so librsync.so.1
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=19c764714e11692e25b91e2e9b8411c3e14fc9d6 commit 19c764714e11692e25b91e2e9b8411c3e14fc9d6 Author: Ben Kohler <bkohler@gentoo.org> AuthorDate: 2020-01-09 00:40:59 +0000 Commit: Ben Kohler <bkohler@gentoo.org> CommitDate: 2020-01-09 00:41:20 +0000 net-misc/dropbox: adjust patchelf target to fix USE=librsync-bundled Closes: https://bugs.gentoo.org/705016 Package-Manager: Portage-2.3.84, Repoman-2.3.20 Signed-off-by: Ben Kohler <bkohler@gentoo.org> net-misc/dropbox/dropbox-88.4.172.ebuild | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
Thanks for catching that, the librsyncffi naming scheme had gone unchanged for so long that I took it for granted
*** Bug 705070 has been marked as a duplicate of this bug. ***