portsdb -Uu failes at ismail, BUG w/ fix

[blancolado]

Environment:
FreeBSD VANHALEN.EDDIE 6.3-STABLE FreeBSD 6.3-STABLE #1: Wed Jul 2 14:19:02 UTC 2008
Also repeated problem on multpile freebsd 5.4 and 6.2 servers. Th

Description:
portsdb fails after cvsup.

Here is the error message I received before fixing the Makefile:

portsdb -Uu
Updating the ports index ... Generating INDEX.tmp - please wait.."/usr/ports/chinese/links/../../www/links/Makefile", line 75: warning: duplicate script for target "pre-configure" ignored
"Makefile", line 32: Could not find bsd.port.options.mk
make: fatal errors encountered -- cannot continue
===> www/ismail failed
*** Error code 1
1 error

************************************************** ******************
Before reporting this error, verify that you are running a supported
version of FreeBSD (see http://www.FreeBSD.org/ports/) and that you
have a complete and up-to-date ports collection. (INDEX builds are
not supported with partial or out-of-date ports collections -- in
particular, if you are using cvsup, you must cvsup the "ports-all"
collection, and have no "refuse" files.) If that is the case, then
report the failure to ports@FreeBSD.org together with relevant
details of your ports configuration (including FreeBSD version,
your architecture, your environment, and your /etc/make.conf
settings, especially compiler flags and WITH/WITHOUT settings).

Note: the latest pre-generated version of INDEX may be fetched
automatically with "make fetchindex".
************************************************** ******************

*** Error code 1

Stop in /usr/ports.
*** Error code 1

Stop in /usr/ports.
failed to generate INDEX!
portsdb: index generation error

How-To-Repeat:
1. Run cvsup and update to latest ports tree (as of: 07/07/08 11:00pmCST)
2. Update portsdb with portsdb -Uu

Fix:
To fix the problem I had to modify /usr/ports/www/ismail/Makefile to
include the full path on the makefile includes. Possibly the make files
have been moved? Why would this makefile cause portsdb to fail when the ismail port is not even installed?

Is anyone else experiencing this issue? I have seen this on 4 or 5 computers ranging from freebsd 4.5 to 6.3. All where working fine until a cvsup on the latest version. No changes, no refuse files, no mergemaster, just used cvsup and then ran portsdb -Uu.