[Bug 264657] security/libpwquality: broken python bindings

From: <bugzilla-noreply_at_freebsd.org>
Date: Sat, 15 Oct 2022 18:14:37 UTC

--- Comment #19 from alt2600@icloud.com ---
(In reply to Chad Jacob Milios from comment #18)

applying the Fix Packaging Stage attachment: the post-stage hooks do not work,
and it still throws errors about installing using setup.py during the normal
staging of the port. I cannot even get to checking orphans. I don't think
adding setuptools to the dependency will help, this port seemingly cannot use
them at all to stage properly. Thinking we have too old a version of
setuptools, it seems the version we have is marked deprecated and slated for
removal at python 3.12 if I'm reading things right online and in the logs. We
are on and they are on upstream. its presence is the issue,
as it works fine without it under a clean poudriere jail. Not sure if gnome
wants python bindings or not, but I sure don't care to have my password
critiqued so I might just get rid of the python bindings to keep going. I might
also see if I can bump my py-setuptools version without too much hassle, but I
would imagine that could be a huge ordeal for all the dependent modules if they
are version locked instead of minimally chosen as done in your patch. And not
sure if they would like the new version, and not looking to brick my desktop
testing, nor having to roll back zfs snapshots. I'll surely continue to help
testing, to the extent it doesn't put my production system at risk. time for
more scotch, and I'll look into if bumping setuptools resolves this issue at
least, it seemingly will be needed for ports in the long run as python 3
marches on minor revs. fortunately i have a wide number of py-setuptools
dependent py- ports I can test in poudriere without risk to my production
system if the bump process goes smooth.

cp -f -R
No such file or directory
*** Error code 1

when I delete the post-stage hooks in the there are now more orphans, there are
no orphans or plist issues if setuptools is not installed at all. so I don't
think the plist has issue, its the inability to easily disable/exclude
site-packages from build environments that is the problem. Reading about
suggest no one in the python project ever considered needing to do anything but
add modules, not delete/block them from pythons execution scope, as there are
only include and similar directives, no excludes. python alone might be what
drives me to full time poudriere instead of just for i386 wine, and occasional
aarch64 cross compiling... :^)

====> Checking for pkg-plist issues (check-plist)
===> Parsing plist
===> Checking for items in STAGEDIR missing from pkg-plist
Error: Orphaned:
Error: Orphaned:
Error: Orphaned:
Error: Orphaned:
Error: Orphaned:
Error: Orphaned:
Error: Orphaned:
Error: Orphaned:
Error: Orphaned:
===> Checking for items in pkg-plist which are not in STAGEDIR
Error: Missing:
Error: Missing:
Error: Missing:
Error: Missing:
Error: Missing:
Error: Missing:
Error: Missing: %%PYTHON_SITELIBDIR%%/pwquality%%PYTHON_EXT_SUFFIX%%.so
===> Error: Plist issues found.
*** Error code 1

You are receiving this mail because:
You are the assignee for the bug.