Evince built with the "lite" flavor fails during packaging step, looking for backends that were not included: pkg-static: Unable to access file /wrkdirs/usr/ports/graphics/evince/work-lite/stage/usr/local/lib/evince/4/backends/comicsdocument.evince-backend:No such file or directory pkg-static: Unable to access file /wrkdirs/usr/ports/graphics/evince/work-lite/stage/usr/local/lib/evince/4/backends/libcomicsdocument.so:No such file or directory pkg-static: Unable to access file /wrkdirs/usr/ports/graphics/evince/work-lite/stage/usr/local/lib/evince/4/backends/libxpsdocument.so:No such file or directory pkg-static: Unable to access file /wrkdirs/usr/ports/graphics/evince/work-lite/stage/usr/local/lib/evince/4/backends/xpsdocument.evince-backend:No such file or directory
This can probably be reproduced by building graphics/evince@lite with the options COMICS and XPS turned off. Because pkg-plist switches to pkg-plist-lite when FLAVOR is lite. pkg-plist-lite does not add %%COMICS%% and %%XPS%% to those missing files.
A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/ports/commit/?id=793bdb42523e8d9ef10ad2d1eeb9be22b59efe2b commit 793bdb42523e8d9ef10ad2d1eeb9be22b59efe2b Author: Tobias C. Berner <tcberner@FreeBSD.org> AuthorDate: 2022-04-26 14:58:54 +0000 Commit: Tobias C. Berner <tcberner@FreeBSD.org> CommitDate: 2022-04-26 16:57:01 +0000 graphics/evince: reinstate PDF backend The PDF backend was dropped, as evince was updated to 42.2 which requires poppler >=22.02 while that one still being at 22.01 in fe838ad373e26eb5880b1f3450af1350cf9b5904. While here, add missing plist-subs to the @lite plist PR: 263009 PR: 263536 PR: 263577 graphics/evince/Makefile | 1 + graphics/evince/pkg-plist | 3 +++ graphics/evince/pkg-plist-lite | 15 +++++++++------ 3 files changed, 13 insertions(+), 6 deletions(-)
Moin moin should be fixed now. mfg Tobias
(In reply to Tobias C. Berner from comment #3) Sorry, my reply is a bit late. I tried the following command. make -C /usr/ports/graphics/evince/ FLAVOR=lite clean deinstall install And I tried two options config, default and all off. As a result, no logs were found as reported. However, I don't know if I have tried the same conditions as reporter.