ports/91001: Portupgrade fails to detect failure of pre-build command

Loren M. Lang lorenl at alzatex.com
Wed Dec 28 07:20:04 UTC 2005


>Number:         91001
>Category:       ports
>Synopsis:       Portupgrade fails to detect failure of pre-build command
>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:   Wed Dec 28 07:20:02 GMT 2005
>Closed-Date:
>Last-Modified:
>Originator:     Loren M. Lang
>Release:        FreeBSD 6.0-RC1 i386
>Organization:
>Environment:
System: FreeBSD enterprise.ddns.alzatex.cc 6.0-RC1 FreeBSD 6.0-RC1 #2: Tue Oct 25 17:22:19 PDT 2005 root@:/usr/obj/usr/src/sys/IPSEC-NG-SC i386


$ ruby --version
ruby 1.8.2 (2004-12-25) [i386-freebsd6]
$ portupgrade -v
portupgrade rev.1049 (2004-12-26)

>Description:
	Portupgrade does not always detect a failure of a pre-build command
and sometimes will go ahead and build a port anyways.  I had about 6
packages out of 675 build even though the pre-build command failed.

>How-To-Repeat:
	The following script will eventually build the port www/libwww even
though the pre-build failed, but it may fail 10 or 20 times before that will
happen.  This can be done with any port, not just www/libwww.

while true; do
	sudo portupgrade -B 'false' -fw www/libwww
done

>Fix:

	


>Release-Note:
>Audit-Trail:
>Unformatted:



More information about the freebsd-ports-bugs mailing list