ports/171893: [BUG] sysutils/ezjail: ezjail_admin update -b (Cannot find your copy of the FreeBSD source tree)

[Matthias Petermann]

>Number:         171893
>Category:       ports
>Synopsis:       [BUG] sysutils/ezjail: ezjail_admin update -b (Cannot find your copy of the FreeBSD source tree)
>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 23 14:00:26 UTC 2012
>Closed-Date:
>Last-Modified:
>Originator:     Matthias Petermann
>Release:        9.0-p3
>Organization:
>Environment:
FreeBSD compaq 9.0-RELEASE-p3 FreeBSD 9.0-RELEASE-p3 #0: Tue Jun 12 02:52:29 UTC 2012     root at amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC  amd64

>Description:
The command:

	ezjail_admin update -b

responds with an error message on my system:

	Error: Cannot find your copy of the FreeBSD source tree in .
  	  Consider using 'ezjail-admin install' to create the base jail from
          an ftp server.

Opposite to the message, the FreeBSD source tree is installed under /usr/src
and the respective path is set in /usr/local/etc/ezjail.conf (ezjail_sourcetree).

Another system with ezJail 3.1 works fine with the same settings. I drilled
down the problem with diff of ezjail_admin version 3.1 vs. 3.2.2. It looks
like that 3.2.2 within the  #### ezjail-admin UPDATE ##### section unsets a
couple of variables but never assigns them again. Thats why later in the code: 

	# Bump the user for some of the most common errors
    [ -d "${ezjail_sourcetree}" ] || exerr "Error: Cannot find your
    copy of the FreeBSD source tree in ${ezjail_sourcetree}.\n  
    Consider using '${ezjail_admin} install' to create the base 
    jail from an ftp server."

exits with the error.

The problem was already reported to ezjail at erdgeist.org (the ezJail
mailing list). This PR is for informational purpose.
>How-To-Repeat:
After the installation of ezjail, try to update the basejail with:

ezjail_admin update -b
>Fix:
I could fix the problem in 3.2.2 temporarely by changing the line:
	unset ezjail_provideports ezjail_installaction ezjail_osversion_source
	ezjail_osversion_destination ezjail_sourcetree
to:
	unset ezjail_provideports ezjail_installaction ezjail_osversion_source 
	ezjail_osversion_destination 

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