ports/102813: bsd.port.mk/BROKEN current usage hurts unnesseccary

Eugene Grosbein eugen at kuzbass.ru
Sun Sep 3 12:00:48 UTC 2006


>Number:         102813
>Category:       ports
>Synopsis:       bsd.port.mk/BROKEN current usage hurts unnesseccary
>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:   Sun Sep 03 12:00:43 GMT 2006
>Closed-Date:
>Last-Modified:
>Originator:     Eugene Grosbein
>Release:        FreeBSD 4.11-STABLE i386
>Organization:
Svyaz Service JSC
>Environment:
System: FreeBSD www.svzserv.kemerovo.su 4.11-STABLE FreeBSD 4.11-STABLE #13: Sun Jul 2 16:11:30 KRAST 2006 eu at www.svzserv.kemerovo.su:/home4/obj/home/src/sys/WWW i386

>Description:
	
	One of our servers keeps complete Ports Collection and
	the collection of distfiles in /usr/ports/distfiles,
	it exports /usr/ports (read-only) using NFS and others
	servers of network mount /usr/ports over NFS.

	Sometimes a port become marked as BROKEN due to MASTER_SIZE downtime.
	This prevents our FreeBSD installations from installing port
	despite the fact its distfile is here in /usr/ports/distfiles.

>How-To-Repeat:

	Try to install ports/net-mgmt/ng_ipacct now when its Makefile
	has 'BROKEN=	Unfetchable' line (its MASTER_SITE is down)
	when port's distfile is already in /usr/ports/distfiles. 

>Fix:

	bsd.port.mk should not prevent user from building/installing
	a port when BROKEN contains the word 'Unfetchable' and
	distfile is accessible localy.

	Alternatively, use some other directive instead of BROKEN
	to mark (possibly temporary) unfetchable ports and first
	check distfile availability in CD_MOUNTPTS/DISTDIR.
>Release-Note:
>Audit-Trail:
>Unformatted:



More information about the freebsd-ports-bugs mailing list