Bug 124822
Summary: | Docs of postgresql-python have bad permissions | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Troels Arvin <troels> |
Component: | postgresql | Assignee: | Tom Lane <tgl> |
Status: | CLOSED ERRATA | QA Contact: | David Lawrence <dkl> |
Severity: | low | Docs Contact: | |
Priority: | medium | ||
Version: | 2 | CC: | hhorak, jlaska |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-06-23 23:02:08 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Troels Arvin
2004-05-30 19:39:31 UTC
It looks like the problem is unreasonably tight file permissions in the upstream PyGreSQL-3.4 package. The RPM installation is relabeling the files with root/root ownership but not changing the permissions. I'll see what I can do about this for the next release. I'm not sure about your suggestion that the .py files ought not be executable --- they are so labeled (at least some of 'em) in the upstream package, and I would assume that's intentional. I'll ask. *** Bug 125783 has been marked as a duplicate of this bug. *** Fixed in postgresql 7.4.3-1. |