$ poudriere testport -j 122amd64 lang/mono5.20 [...] ====> Checking for pkg-plist issues (check-plist) ===> Parsing plist ===> Checking for items in STAGEDIR missing from pkg-plist Error: Orphaned: lib/mono/xbuild/Microsoft/VisualStudio/v16.0/WebApplications/Microsoft.WebApplication.targets ===> Checking for items in pkg-plist which are not in STAGEDIR ===> Error: Plist issues found. *** Error code 1
If someone has a patch/fix, packaging fixes are: Approvd by portmgr (blanket: bugfix, jfi) MFH: <branch|No> <reason>
(In reply to Jan Beich from comment #0) What options are you using? It seems to build on the package builders: http://beefy6.nyi.freebsd.org/data/122amd64-default/463524251ec6/logs/mono5.20-5.20.1.34.log
(In reply to Mark Linimon from comment #2) "make check-plist" is only run by default when DEVELOPER=1 (advised by portlint) or via "poudriere testport" or "poudriere bulk -t". Packages on the cluster are built without DEVELOPER=1. Personally, I have the following in poudriere.conf: PORTTESTING=1 PORTTESTING_RECURSIVE=1 PORTTESTING_FATAL=no which allows to discover bugs without stopping at individual ports. The time spent doing the extra checks is negligible except in the most trivial ports (e.g., portlint itself) but the value is immense when investigating NEEDED vs. *_DEPENDS desync, runtime issues months later after several port updates or, more commonly, when testing consumers after an API-breaking update.
it's still an issue.
This has been fixed with https://cgit.freebsd.org/ports/commit/lang/mono5.20/pkg-plist?id=432bcd11d897d96334d6c6570775262ea9a44248 mono-5.20.1.34,1 had a clean plist for me (built manually w/o poudriere) using ===> The following configuration options are available for mono5.20-5.20.1.34_1: HEAPVIZ=off: Install mono-heapviz debug tool (requires py-pillow) NLS=on: Native Language Support X11=on: X11 (graphics) support