Bug 255857 - lang/mono5.20: Fails to package: Orphaned: lib/mono/.../WebApplications/Microsoft.WebApplication.targets
Summary: lang/mono5.20: Fails to package: Orphaned: lib/mono/.../WebApplications/Micro...
Status: Open
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-mono (Nobody)
Keywords: needs-patch
Depends on:
Reported: 2021-05-14 04:37 UTC by Jan Beich
Modified: 2021-05-14 13:38 UTC (History)
1 user (show)

See Also:
bugzilla: maintainer-feedback? (mono)
koobs: merge-quarterly?


Note You need to log in before you can comment on or make changes to this bug.
Description Jan Beich freebsd_committer 2021-05-14 04:37:58 UTC
$ 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
Comment 1 Kubilay Kocak freebsd_committer freebsd_triage 2021-05-14 06:27:28 UTC
If someone has a patch/fix, packaging fixes are:

Approvd by portmgr (blanket: bugfix, jfi)
MFH: <branch|No> <reason>
Comment 2 Mark Linimon freebsd_committer freebsd_triage 2021-05-14 13:10:45 UTC
(In reply to Jan Beich from comment #0)
What options are you using?  It seems to build on the package builders:

Comment 3 Jan Beich freebsd_committer 2021-05-14 13:38:11 UTC
(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:


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.