misc/48722: Source tarballs available in daily releng builds don't have correct permissions set on some files

[dhgutteridge%sympatico.ca@localhost]

>Number:         48722
>Category:       misc
>Synopsis:       Source tarballs available in daily releng builds don't have 
>correct permissions set on some files
>Confidential:   no
>Severity:       serious
>Priority:       low
>Responsible:    misc-bug-people
>State:          open
>Class:          support
>Submitter-Id:   net
>Arrival-Date:   Sun Apr 06 20:20:00 +0000 2014
>Originator:     David H. Gutteridge
>Release:        Current
>Organization:
Sometimes no semblance of organization whatsoever
>Environment:
n/a
>Description:
The source tarballs that are available in releng builds on the
nyftp.netbsd.org server have incorrect permissions applied to some
files, which results in build failures should someone download them
to use as the basis for a source tree. (Presumably there is some umask
issue involved when the files are being copied at some point.)

For example, there are two scripts in src/crypto/external/bsd/openssl
(openssl2netbsd and mkpc) that are missing execute permissions, which
means the build fails when it can't run mkpc.

I realize that it might not be very common for people to be using
these sets for anything, given one can grab the source from CVS using
other means, or simply download source tarballs in a different form
via the ftp.netbsd.org server, but presumably the idea is that these
files are provided so someone could indeed use them to build from.
(In my case, I was trying to debug build problems by creating a new
virtualized build environment with a snapshot of the source as of a
certain time, and these seemed one way to do it, until the build
broke.)
>How-To-Repeat:
Create a source tree from files available through releng builds and
then try to build it.
>Fix: