ports/103421: java/javavmwrapper: /usr/local/bin/k{init, list} may conflict with /usr/bin/k{init, list} from base system

Vasily Korytov deskpot at jah.pp.ru
Wed Sep 20 14:40:41 UTC 2006


>Number:         103421
>Category:       ports
>Synopsis:       java/javavmwrapper: /usr/local/bin/k{init,list} may conflict with /usr/bin/k{init,list} from base system
>Confidential:   no
>Severity:       serious
>Priority:       low
>Responsible:    freebsd-ports-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Sep 20 14:40:27 GMT 2006
>Closed-Date:
>Last-Modified:
>Originator:     Vasily Korytov
>Release:        FreeBSD 5.5-STABLE i386
>Organization:
Good morning, Jah!
>Environment:
System: FreeBSD filesrv.moscow.flexpro.ru 5.5-STABLE FreeBSD 5.5-STABLE #0: Thu Jun 15 16:40:12 MSD 2006 root at hub.flexpro.ru:/usr/src/sys/i386/compile/FILESRV i386

javavmwrapper-2.3 from ports.
	
>Description:

In the base system there are two Kerberos-essential binaries:

filesrv% whereis kinit
kinit: /usr/bin/kinit /usr/share/man/man1/kinit.1.gz
filesrv% whatis kinit
kinit(1), kinit kauth(1) - acquire initial tickets
filesrv% whereis klist
klist: /usr/bin/klist /usr/share/man/man1/klist.1.gz
filesrv% whatis klist
klist(1)                 - list Kerberos credentials

But the javavmwrapper port does install two binaries with same names:

filesrv% pkg_which /usr/local/bin/kinit
javavmwrapper-2.0_7 javavmwrapper-2.3
filesrv% pkg_which /usr/local/bin/klist
javavmwrapper-2.0_7 javavmwrapper-2.3

In fact, having /usr/local/bin before /usr/bin in path (a rather
innocent action, that may be preferred, keeps users from using Kerberos.

	
>How-To-Repeat:
PATH=/bin:/usr/local/bin:/usr/bin:/usr/X11R6/bin:/usr/games
And try to use Kerberos (e.g. kinit -f).
	
>Fix:

If kinit and klist from javawmwrapper should be in path
(/usr/local/bin), that duplicate k{init,list}situation breaks either
javawrapper, or klist.

If they have to be there, they should be renamed -- say, to
jk{init,list}. If not -- they have to be moved to some other directory,
outside of the default path.
	


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



More information about the freebsd-ports-bugs mailing list