py-pyparsing

[Richard PALO <richard%netbsd.org@localhost>]

With leot@ we noticed a difference in treating certain pytyon tarballs, notably py-pyparsing.
The gzip'ed tarball unfortunately has the egg info rw-rw-rw instead of rw-r-r.

This gives (for me, anyway, on SunOS)
> => Checking file permissions in py27-pyparsing-2.0.6
> warning: /tmp/pkgsrc/devel/py-pyparsing/work/.destdir/opt/local/lib/python2.7/site-packages/pyparsing-2.0.6-py2.7.egg-info/dependency_links.txt: group-writable file.
> error: /tmp/pkgsrc/devel/py-pyparsing/work/.destdir/opt/local/lib/python2.7/site-packages/pyparsing-2.0.6-py2.7.egg-info/dependency_links.txt: world-writable file.
> warning: /tmp/pkgsrc/devel/py-pyparsing/work/.destdir/opt/local/lib/python2.7/site-packages/pyparsing-2.0.6-py2.7.egg-info/PKG-INFO: group-writable file.
> error: /tmp/pkgsrc/devel/py-pyparsing/work/.destdir/opt/local/lib/python2.7/site-packages/pyparsing-2.0.6-py2.7.egg-info/PKG-INFO: world-writable file.
> warning: /tmp/pkgsrc/devel/py-pyparsing/work/.destdir/opt/local/lib/python2.7/site-packages/pyparsing-2.0.6-py2.7.egg-info/SOURCES.txt: group-writable file.
> error: /tmp/pkgsrc/devel/py-pyparsing/work/.destdir/opt/local/lib/python2.7/site-packages/pyparsing-2.0.6-py2.7.egg-info/SOURCES.txt: world-writable file.
> warning: /tmp/pkgsrc/devel/py-pyparsing/work/.destdir/opt/local/lib/python2.7/site-packages/pyparsing-2.0.6-py2.7.egg-info/top_level.txt: group-writable file.
> error: /tmp/pkgsrc/devel/py-pyparsing/work/.destdir/opt/local/lib/python2.7/site-packages/pyparsing-2.0.6-py2.7.egg-info/top_level.txt: world-writable file.
> 4 errors and 4 warnings.
> *** Error code 1
> 
> Stop.
> bmake[1]: stopped in /export/pub/src/pkgsrc/devel/py-pyparsing
> *** Error code 1

I have more or less the same with wip/py-wsgiref but that, I believe, is related to an already identified issue with
libarchive as already seen with py-keyring object of bin/49798...

what is strange is that this is apparently not seen on [many] other platforms than SunOS.

Furthermore, I tried as a workaround setting
> CHECK_PERMS_AUTOFIX=   yes
but that doesn't work, even though it corrects the files, it still returns error (1)... unfortunately.

Has anybody else seen this and perhaps has any observations as what may eventually remedy the situation?

cheers

-- 
Richard PALO