Bug 239255

Summary:	net/nss-pam-ldapd-sasl: install failure: Error: '/usr/bin/env python' is an invalid shebang you need USES=shebangfix
Product:	Ports & Packages	Reporter:	O. Hartmann <ohartmann>
Component:	Individual Port(s)	Assignee:	Ryan Steinmetz <zi>
Status:	Closed Not A Bug
Severity:	Affects Some People	Flags:	bugzilla: maintainer-feedback? (zi)
Priority:	---
Version:	Latest
Hardware:	Any
OS:	Any

Description O. Hartmann 2019-07-16 17:31:11 UTC

Port net/nss-pam-ldapd-sasl fails to install due to the error shown below:

[...]
Making install in tests
====> Compressing man pages (compress-man)
===> Staging rc.d startup script(s)
====> Running Q/A tests (stage-qa)
Error: '/usr/bin/env python' is an invalid shebang you need USES=shebangfix for 'share/nslcd-utils/chsh.py'
Error: '/usr/bin/env python' is an invalid shebang you need USES=shebangfix for 'share/nslcd-utils/getent.py'
Warning: Bad symlink '/usr/local/bin/getent.ldap' pointing to an absolute pathname '/usr/local/share/nslcd-utils/getent.py'
Warning: Bad symlink '/usr/local/bin/chsh.ldap' pointing to an absolute pathname '/usr/local/share/nslcd-utils/chsh.py'
Warning: /usr/ports/net/nss-pam-ldapd-sasl/work/stage/usr/local/lib/pam_ldap.so.1 doesn't have a SONAME.
Warning: pkg(8) will not register it as being provided by the port.
Warning: If another port depend on it, pkg will not be able to know where it comes from.
Warning: It is directly in /usr/local/lib, it is probably used by other ports.
*** Error code 1

Comment 1 Ryan Steinmetz freebsd_committer

2019-07-16 19:01:58 UTC

I'm unable to reproduce this.  We don't install any python scripts with this port.

Can you please share your OS version (uname -r), verify that you have a current ports tree and that you are trying to install 0.9.10_1.

Comment 2 O. Hartmann 2019-07-17 04:28:37 UTC

OS revision:

 FreeBSD 13.0-CURRENT #188 r350050: Tue Jul 16 18:09:54 CEST 2019 amd64

The ports tree is at

r506787.

Comment 3 Ryan Steinmetz freebsd_committer

2019-07-17 13:48:44 UTC

Can you share your make.conf and any other build-related settings?  In digging through the Makefile, it looks like something is defining ENABLE_UTILS.

Comment 4 O. Hartmann 2019-10-09 19:53:50 UTC

*** Bug 238679 has been marked as a duplicate of this bug. ***

Comment 5 O. Hartmann 2019-11-16 10:28:59 UTC

(In reply to Ryan Steinmetz from comment #3)

I checked make.conf on the remaining failing machine and realised that on that specific machine, gloabl option

DEVELOPER=yes

was set, causing the error. I have overlooked that point. My apology.