Bug 73910 - Does not work when installed with an umask of 077 and messes filesystem
Summary: Does not work when installed with an umask of 077 and messes filesystem
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: perl-DateManip
Version: 8.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Warren Togami
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-09-13 13:46 UTC by Enrico Scholz
Modified: 2007-04-18 16:46 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-09-11 11:33:29 UTC
Embargoed:


Attachments (Terms of Use)

Description Enrico Scholz 2002-09-13 13:46:34 UTC
Description of Problem:

Because this package contains unowned directories, they will be created
with the current umask. When having restrictive administrator settings
(umask 077) ordinary user will not have access to them and can not use
them.

Another problem occurs when removing packages. Then orphaned directories
are remaining.

| $ rpm -qf /usr/lib/perl5/vendor_perl/5.8.0/Date /usr/lib/perl5/vendor_perl/5.8.0/Date/Manip.pm
| file /usr/lib/perl5/vendor_perl/5.8.0/Date is not owned by any package
| perl-DateManip-5.40-27


Version-Release number of selected component (if applicable):

perl-DateManip-5.40-27


How Reproducible:

100%


Steps to Reproduce:
1. umask 077
2. make sure that perl-DateManip is uninstalled completely
   (rm -rf /usr/lib/perl5/vendor_perl/5.8.0/Date)
3. rpm -U perl-DateManip-5.40-27.*
4. ls -l /usr/lib/perl5/vendor_perl/5.8.0/Date
5. start perl script using this module
6. rpm -e perl-DateManip-5.40-27

Actual Results:

| drwx------    2 root     root         4096 Sep 13 10:21 /usr/lib/perl5/vendor_perl/5.8.0/Date

at 4; script can not find package at 5 and
/usr/lib/perl5/vendor_perl/5.8.0/Date
still exists after 6.

Comment 1 Warren Togami 2005-09-11 11:33:29 UTC
Spec has since been rewritten so assuming fixed.  If this is not fixed in
rawhide then please open a new bug.


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