ports/178373: ports error in ncurses dependency script ncurses.mt causing "grep: /var/db/pkg/ncurses-5.9_1/+CONTENTS : No such file or directory" error
Andrew Wright
ahamiltonwright at mta.ca
Mon May 6 18:50:00 UTC 2013
>Number: 178373
>Category: ports
>Synopsis: ports error in ncurses dependency script ncurses.mt causing "grep: /var/db/pkg/ncurses-5.9_1/+CONTENTS : No such file or directory" error
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: freebsd-ports-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Mon May 06 18:50:00 UTC 2013
>Closed-Date:
>Last-Modified:
>Originator: Andrew Wright
>Release: 9.1-RELEASE-p3
>Organization:
Mount Allison University
>Environment:
FreeBSD qemg.org 9.1-RELEASE-p3 FreeBSD 9.1-RELEASE-p3 #0: Mon Apr 29 18:27:25 UTC 2013 root at amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64
>Description:
As of today (May 6, 2013) the portupgrade script reports errors when trying to determine ncurses dependencies. These errors appear:
grep: /var/db/pkg/ncurses-5.9_1/+CONTENTS : No such file or directory
grep: /var/db/pkg/ncurses-5.9_1/+CONTENTS : No such file or directory
"/usr/ports/Mk/Uses/ncurses.mk", line 80: warning: "grep -m 1 "^lib/libncurses.so." "/var/db/pkg/ncurses-5.9_1/+CONTENTS "" returned non-zero status
grep: /var/db/pkg/ncurses-5.9_1/+CONTENTS : No such file or directory
grep: /var/db/pkg/ncurses-5.9_1/+CONTENTS : No such file or directory
"/usr/ports/Mk/Uses/ncurses.mk", line 80: warning: "grep -m 1 "^lib/libncurses.so." "/var/db/pkg/ncurses-5.9_1/+CONTENTS "" returned non-zero status
Examining /usr/ports/Mk/Uses/ncurses.mk shows that there is a spurious whitespace character at the end of the variable ${NCURSES_INSTALLED} as used when attempting to set up the variable NCURSES_SHLIBFILE.
I am not sure why the previous line does not produce an error, therefore it is clear that someone with more understanding of what this file is supposed to do should look at this.
>How-To-Repeat:
Update ports (I used portsnap) and run portupgrade -a
>Fix:
I assume that some recent change to the file introduced the extra space when this variable was instantiated -- it should be trimmed.
>Release-Note:
>Audit-Trail:
>Unformatted:
More information about the freebsd-ports-bugs
mailing list