https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=249255
Kubilay Kocak <ko...@freebsd.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |needs-qa
Severity|Affects Only Me |Affects Many People
Flags| |maintainer-feedback?(python
| |@FreeBSD.org)
Status|New |Open
Assignee|pyt...@freebsd.org |arr...@freebsd.org
CC| |pyt...@freebsd.org
Summary|Python autoplist generates |devel/tortoisehg: Python
|invalid items |autoplist generates invalid
| |items
--- Comment #1 from Kubilay Kocak <ko...@freebsd.org> ---
autoplist uses setuptools --record output to produce the pkg-plist. This can be
verified by looking at the various plist files in the $WRKDIR post-install
All else being equal, it's very likely these files aren't packaged correctly
upstream, in the sense that they aren't in the --record output, due to being
'specially handled' in some way.
The usual method this takes place is custom build* or install* methods in
setup.py, that override or replace the defaults in setuptools, which fail to
add the files being processed to setuptools output files list that's used in
--record output.
Workaround: pkg-plist entries can be used in combination (complementary to)
autoplist, so put those "missing" pkg-plist entries there, if they arent
already, until the root cause is identified and resolved.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
_______________________________________________
freebsd-python@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-python
To unsubscribe, send any mail to "freebsd-python-unsubscr...@freebsd.org"
