if one creates a src rpm from a tar file, e.g.:

rpmbuild -ta foo.tar.gz

then foo-x.x-x.src.rpm will contain a spec file whose permissions are 0600
despite the spec file in the tar ball having different permissions (e.g. 0644).

If one then runs rpmlint on the resulting foo-x.x-x.src.rpm it will complain the
mode of the spec file is 0600 and suggest it be 0644 instead (but the spec file
did have 0644 in the input tarball!)

I tracked down the reason this happens. The relevant code is in ./build.c in the
function buildForTarget(). The code creates a temp file for the spec file it is
going to read from the tarball:

	tmpSpecFile = rpmGetPath("%{_specdir}/", "rpm-spec.XXXXXX", NULL);
#if defined(HAVE_MKSTEMP)
	(void) close(mkstemp(tmpSpecFile));
#else
	(void) mktemp(tmpSpecFile);
#endif

then the spec file is extracted to the temp file by calling tar and redirecting
stdout to the temp file:

	sprintf(cmd, "%s < %s | tar xOvf - Specfile 2>&1 > %s",
-or-
	sprintf(cmd, "%s < %s | tar xOvf - --wildcards \\*.spec 2>&1 > %s",


then the temp file is renamed to the spec file in _specdir.

The problem arises because of the use of mkstemp() which enforces 0600
permissions. The file is renamed to be foo.spec and retains its 0600
permissions. This file is then copied into the resulting .src.rpm with the 0600
permissions mkstemp() gave it.

The expected behavior would be for the spec file to retain the permissions it
had in the tar file or for it to be given 0644 permissions to stay in alignment
with the expectations of rpmlint.