Bug 78428

Summary:	dev-python/imaging emerges with incorrect permissions
Product:	Gentoo Linux	Reporter:	Dan Margolis (RETIRED) <krispykringle>
Component:	New packages	Assignee:	Python Gentoo Team <python>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	marienz
Priority:	High
Version:	unspecified
Hardware:	All
OS:	All
Whiteboard:
Package list:		Runtime testing required:	---

Description Dan Margolis (RETIRED) gentoo-dev

2005-01-17 14:46:04 UTC

ebuild uses doinst, rather than dobin, which apparently results in the module files being installed with the default umask. 

Reproduce: emerge dev-python/imaging, ls -ld /usr/lib/python2.3/site-packages/PIL

Comment 1 Marien Zwart (RETIRED) gentoo-dev

2005-02-04 15:39:54 UTC

I set umask to 077 both in my running shell and in /etc/profile, then emerged imaging (1.1.4-r1, x86 stable version). The permissions on /usr/lib/python${PYVER}/site-packages/PIL after this were 755, contents were 644.

Also this dir or its contents are not installed by doinst (or doins) (nor should they be imho, these files shouldn't be executable), they are installed through distutils (python setup.py install). The 3 headers that go into /usr/include/python${PYVER} that *are* installed by doins also had proper (644) permissions.

In other words, how do I reproduce this?

Comment 2 Alastair Tse (RETIRED) gentoo-dev

2005-04-20 08:37:43 UTC

unable to reproduce either.