78428 – dev-python/imaging emerges with incorrect permissions

Bug 78428 - dev-python/imaging emerges with incorrect permissions

Summary: dev-python/imaging emerges with incorrect permissions

Status:	RESOLVED WORKSFORME

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	New packages (show other bugs)
Hardware:	All All

Importance:	High normal (vote)
Assignee:	Python Gentoo Team

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2005-01-17 14:46 UTC by Dan Margolis (RETIRED)
Modified:	2005-04-20 08:37 UTC (History)
CC List:	1 user (show)

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

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.