FYI, this was documented in the NetBSD 1.3 "LAST_MINUTE" file, has
already been fixed in NetBSD-current, and will be fixed in the NetBSD
1.3.1 patch release.  (From messages on current-users, the source
diffs for 1.3.1 (from 1.3) are already available, at
ftp.netbsd.org:pub/NetBSD/NetBSD-1.3.1/source.)

For the record, as far as I'm concerned, none of those facts excuse
the problem showing up in the release.  Many simple tests, including
building X -- which was supposed to be part of the release process --
would have showed the problem.  (In fact, if I recall correctly,
building X was how the problem was discovered.)



cgd